Related
So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device
You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta
A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade
Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app
u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378
Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.
Hello all!
I am currently running triforce rom on my s4, i really like the rom it just doesn't work with some apps i use. For example Ent online banking app and nfl fantasy football app. But my question is, if i restore my phone back to stock rooted rom, will i still be able to use the wifi tether app? without sprint finding out that is?
Thank You
you should as long as you retain root
and if wifi tether doesn't run properly, you can just flash the hotspot mod instead. That bypasses the carrier check as well.
jj14 said:
and if wifi tether doesn't run properly, you can just flash the hotspot mod instead. That bypasses the carrier check as well.
Click to expand...
Click to collapse
What/which is and how do you flash the hotspot mod. Please teach me, I am on MDL and have other oxdex method and have failed. Thanks...
sprintomatic said:
What/which is and how do you flash the hotspot mod. Please teach me, I am on MDL and have other oxdex method and have failed. Thanks...
Click to expand...
Click to collapse
Assuming you are rooted, and have a custom recovery installed, it should be a quick update.
Are you planning to install MF9? or stay on MDL?
Regardless, download the appropriate version from the thread below (check your settings -> More -> About device, and look at the build number. Also, check and make sure you download the right odex/deodex version (the thread below has detailed instructions on how to identify the right version)
Download the right version to your phone's internal storage, and boot into your custom recovery, and flash it from there. (I assume you have a nandroid backup of your current software - if not, you should make one before you flash anything)
http://forum.xda-developers.com/showthread.php?t=2256950
(again, I cannot stress this enough - make sure you download the right version - there are a LOT of folks who downloaded the wrong version, and then start a thread asking "Why is my phone stuck at the yellow Sprint screen?" etc. It is still recoverable, but adds unnecessary headache)
jj14 said:
Assuming you are rooted, and have a custom recovery installed, it should be a quick update.
Are you planning to install MF9? or stay on MDL?
Regardless, download the appropriate version from the thread below (check your settings -> More -> About device, and look at the build number. Also, check and make sure you download the right odex/deodex version (the thread below has detailed instructions on how to identify the right version)
Download the right version to your phone's internal storage, and boot into your custom recovery, and flash it from there. (I assume you have a nandroid backup of your current software - if not, you should make one before you flash anything)
http://forum.xda-developers.com/showthread.php?t=2256950
(again, I cannot stress this enough - make sure you download the right version - there are a LOT of folks who downloaded the wrong version, and then start a thread asking "Why is my phone stuck at the yellow Sprint screen?" etc. It is still recoverable, but adds unnecessary headache)
Click to expand...
Click to collapse
Thank you for the reply! The farthest i have gone on this and other phones just is to root as I got wifi tether on it and was a happy camper. But with that said, I am open to going further and doing all these flashes. Also, I downloaded the correct version and made sure I m going the right path and did the replacing odex.bak files and all the other ones, But nothing happened. I will prob maybe update for 4.3 but for now MDL will do. I Just need a good guide for a noob on how to do a nandroid backup. Thanks for all the tips.
Update: just did the flash method and it still does not show up, any help would be appreciated it. As a side note dont know if this can help, but my phone has been unlocked for international use, it was manually activated and sprint apps not installed. on MDL stock rom.
What recovery do you have? (TWRP? CWM? something else?)
Are you sure you are rooted?
Are you on the Stock MDC ROM?
When you flashed the MDC hotspot mod, did you see any errors in recovery? Or did it indicate successful flash?
After flashing the mod, do you see the hotspot icon under settings-connections? What happens if you turn it on?
Also, I noticed that you said "it was manually activated and sprint apps not installed"
What is the manual activation that you referred to? Typically, after activation, the phone downloads the Sprint network updates etc, and I believe it is at that time, that it downloads the necessary files for the regular hotspot. These are the files that then get modified by the hotspot mod that I had linked to. Are you saying that you skipped the part where it would have downloaded the Sprint updates? If so, that may be why the hotspot mod isn't working (since it doesn't have anything to modify).
Unlocking for international use (assuming it was done by Sprint) should not cause any issues. I'm unlocked as well.
jj14 is right, without the sprint apps installed there is no hotspot to mod. You will have to find an alternative wifi tether app or redo the activation process and let the Sprint apps install.
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
MAGICEA_EA said:
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
Click to expand...
Click to collapse
From what I understand, you will still be able to get updates thru OTA.
hd-renegade said:
From what I understand, you will still be able to get updates thru OTA.
Click to expand...
Click to collapse
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
So i can update rooted lg g2 over the air when a new update comes out
liorra3 said:
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
Click to expand...
Click to collapse
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
ota
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
Im new to this, so if you have rooted lg g2, will ota still work. Everything is stock on the phone
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
you right.
if you use stock recovery you will get OTAs
if its stock and merely rooted then OTA should work
For the OTA to be accepted, you'll need the stock recovery for your device. Rename it to recovery.img (if it already isn't named that) and then move it to sdcard root (/sdcard).
Now, use a terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en) and open a command prompt. The command we're using has two parameters. The the "if" parameter refers to your input file, in this case, this is the recovery.img file you moved to your sdcard root to flash. This could be any recovery (TWRP, CWM, stock, etc). The "of" parameter is the output file and is the actual physical path to the recovery image your device uses. At the command prompt type this:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you already have the stock recovery then all you need to do is press "Accept" or "OK" or whatever the dialog asks when it pops up letting you know about the update. I'm not sure if the stock recoveries are different for each carrier, so you'll have to find that yourself.
Edit: By the time I finished typing this I see that you already are on stock recovery, so you should be good to go
Idk mines flashed to stock and rooted
Sent from my LG-D800 using Tapatalk
Just bought a g2 and am thinking of rooting to enable the auto hide of the on screen menu buttons. So correct me if im wrong but if all i do is root, leave the stock rom and do nothing apart from root i will still get ota updates.
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
SuperSU Pro has an OTA survival Mode. You can try it out, it should work
o0adam0o said:
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Try the above or remove/freeze whatever the apk your carrier uses for the OTA. There's a couple threads around with more info.
Sent from my LG-D800
Another question: (don't want to start a thread for this)
If you have custom recovery (In my case TWRP) when an OTA lands, obviously I won't be able to accept it.
I'll need to flash it through TWRP correct?
If this is the case will this simply apply as OTA's do and not delete any of my data on the phone etc?
Also is there a stock recovery I can download just to make things easier??
First time I've had a phone rooted and with recoverybefore it's update cycle is over, and Google isn't really being all that helpful
How to backup stock recovery?
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
Nice to see you here dude.. may remember me from the rocket? Anyways, i'd just skip the OTA. It's nothing life changing. I'm still stock/rooted on 10d. Waiting for bugs to get squashed on 4.4.2 before I start flashing. Rather enjoying stock for the time being. Not really sure why 10o won't take. Haven't seen anyone else mention this. The only thing that has been brought up repeatedly is bootloops in twrp after taking the 10o OTA.
m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Sent from my VS980 4G using Tapatalk
thricerocks86 said:
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Click to expand...
Click to collapse
I am still investigating. I've unrooted via Voodoo OTA Rootkeeper and a little extra housekeeping, and the Rooting Status does show "unrooted" in the About Phone section. However I still get 0x1117008 when trying to install the OTA. So perhaps the "unrooted" in About Phone may be a prerequisite, but is not sufficient for a successful OTA update. Maybe either the update is doing more checks for rooting evidence than the RCT daemon, or perhaps there is some other change that is triggering the error.
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
mikeprius said:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
Click to expand...
Click to collapse
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
cruise350 said:
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
Click to expand...
Click to collapse
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
mikeprius said:
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
Click to expand...
Click to collapse
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
cruise350 said:
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
Click to expand...
Click to collapse
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
mikeprius said:
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
Click to expand...
Click to collapse
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
cruise350 said:
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
Click to expand...
Click to collapse
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
mikeprius said:
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
Click to expand...
Click to collapse
Every thing in the data partition(titanium backup) will remain and everything in the system partition (SuperSU & stuff modified via xposed installer) will be gone and replaced with the bloatware.
Sent from my SPH-L720 using Tapatalk
Ok, so it appears to have worked. I flashed the 4.3 prior version however it was hooked up to wifi and automatically downloaded the new version and removed root (not a big deal). My status says custom still, but I am assuming that I can OTA after the flash b/c it updated to the most recent 4.3 in Dec 2013. I re-rooted so it is back to prior, but I know now how to do it.
Is there anything that I may delete or uninstall that cannot be replaced by flashing the stock firmware ? For example I was thinking about getting rid of the 'help' on the phone and Titanium Back up said it is odexed or something to that extent and can only be replaced by using Titanium Backup and the exact same copy ?
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Being able to flash the stock .tar through ODIN gives me peace of mind from screw ups, even if it removes root and takes time.
mikeprius said:
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Click to expand...
Click to collapse
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
nobody291 said:
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
Click to expand...
Click to collapse
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
mikeprius said:
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
Click to expand...
Click to collapse
To me, one of the hardest parts of this whole thing is getting to the point where the basic terms make sense. I've been at this for a couple of years with an HTC Evo and now the GS4 since October, and sometimes it still makes my head spin. Here is an attempt to explain my understanding of a few things:
1. Booting...you can boot into Download mode, recovery, or system. Download mode is what you use with ODIN, you need the correct drivers on your computer (which can be found lots of places), so that ODIN and your phone can communicate. In download mode, the phone just accepts whatever ODIN sends it, so it's the easiest way to totally brick your phone. Don't mess with partitions and follow the instructions for whatever you're doing very carefully, because I think this is the only way to "hard brick" your phone.
2. Recovery - something you use to create images of your phone's ROM (nandroids), flash ROMs and mods, and restore past nandroids. The stock recovery will only flash approved updates from the carrier, so to do any of the things I listed you need a custom recovery. Most people use Philz (which is based on the ClockworkMod recovery) or TWRP. To flash the custom recovery, use ODIN and follow the instructions in the thread exactly. There is a way to flash recoveries without ODIN, but I've never done it. I was using TWRP, and switched to Philz to flash the rooted stock 4.3 update because the thread suggested it. They both seem to do the same thing, and I have been happy with both. I'm sure there are technical differences, but I couldn't explain what they are. You can switch back and forth as much as you'd like between the recoveries with ODIN. Recoveries can flash a complete ROM or just partial changes (like the hotspot mod). In a custom recovery (or the stock) you can also do factory resets and cache cleaning (most ROMs suggest you do this before flashing). Factory reset doesn't return the ROM to the factory original, it just clears out all of the user data (including user apps). A nandroid is the fastest way to restore a phone if you screw it up...I always make one before making significant changes to the phone. It takes several minutes to do, but I think it's well worth it. The operating system can't be running when you make one, that's why you need to boot into recovery mode. You create a Nandroid in Philz by selecting "backup and restore" then "backup to" which will allow backup to the internal storage or external SD card.
3. ROM - the actual operating system used by the phone when you actually use it as a smartphone. There are 2 basic flavors for the GS4...touchwiz and AOSP (Android Open Source Project). Touchwiz is Samsung's "flavor" of Android, AOSP is the "pure Google" version of Android. A lot of the things the GS4 will do rely on touchwiz (multiwindow is one example...but there are several). Some people really like the AOSP ROMs (Cyanogen is AOSP), but make sure you understand their limitations. I've never used one on the GS4. There are several touchwiz custom ROMs which have various features. I've tried a few and just settled on the stock rooted touchwiz ROM, but there are lots of options from great developers. I think most custom ROMs require you to use a custom recovery to flash them, but there might be ways to do it using ODIN. I like having a custom recovery, so I've only used ODIN for flashing modems and recoveries.
4. Firmware - as far as I can tell, there are two important parts of the firmware...the modem (sometimes called "radios" or "baseband"...find your version by looking in "about device"->"Baseband version"...the different modems are described by the last 3 letters you see) and the bootloader. The modem and the version of the ROM you flash need to match or you'll have problems with the radios in the phone (wifi seems to be the biggest problem if you have a mismatch). MF9 was the last modem version based on 4.2.2, and 4.3 has had MJA and MK2 (MK2 is the latest). The bootloader is what the phone uses to initially decide how to boot up. If you have the 4.3 version of the bootloader it will include "Knox", which will prevent you from flashing older versions of the modem, so you'll have to use a 4.3 ROM. Knox also "trips" a counter if you flash a custom ROM and Samsung claims they won't honor the warranty on a phone with the "Knox flag" tripped. If you have the 4.3 bootloader you're stuck with it (for now at least). I still have the 4.2.2 bootloader, so I don't have much more to offer on this subject. There are ways to get the 4.3 modem and ROM without the 4.3 bootloader. There is a lot here (and lots on youtube) on how to navigate the Knox minefield if you care about it. If you still have the 4.2.2 bootloader you can flash older (and newer) modems as much as you'd like without getting the updated bootloader using ODIN.
Hopefully this helps...this is a great place with lots of great people. Sometimes the scale of the amount of information here is overwhelming. But, search is your friend along with lots of time! Feel free to keep asking questions.
thanks for explaining this nobody-
The information does help quite a bit and I am still learning, however; I do enjoy the process of messing with the phone. My GS4 now runs the RAM at 750-800mg instead of a bloated 1.2GB which was happening quite a bit. I had to originally not use a lot of apps I wanted to like Facebook bc the programs themselves bloated up to accomidate the existing bloatware which was also running. I did flash my phone back with the stock firmware today and it looks like it installed all the stock software. My status said 'custom' when I looked at it however I was already connected to wifi and it went from 4.3 (Oct 2013 version which I flashed) to Dec 2013 version automatically so it appears that the OTA feature works.
I assumed if I accidently delete something from the phone that I really need to affects the phone, I can always flash the stock ROM to fix it. Losing the root is not that big of an issue, but I did lose Superuser and had to re-root the phone. I suppose I do have a few more questions, one was when I was reading another carrier provider thread.
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
mikeprius said:
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
Click to expand...
Click to collapse
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
Click to expand...
Click to collapse
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
nobody291 said:
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
Click to expand...
Click to collapse
It was good that you mentioned the Knox bootloader issue with the 4.3 upgrade. When I purchased my cell phone back in Nov, I believe it had the 4.3 (1st) version loaded, but it already had Knox features as I do recall seeing them. If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ? This may have been the error I read about due to the new Knox feature.
I think since my phone is currently rooted and I altered some of the bloatware system files that the update if it were made available OTA should not update anyway due to the root. Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ? With that, if I were to load 4.4 and not like it, could I flash back 4.3 ? I am guessing this is the part where you mentioned that the carrier may decide differently later on.....I suppose I will just keep an eye out in the meantime.
Good good............, I'm picking up this pretty well so far.............
mikeprius said:
If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ?
Click to expand...
Click to collapse
I'm not sure what symptoms you'd see if you installed 4.2.2 with the 4.3 bootloader. Most likely the phone would fail to boot. ODIN will flash whatever you tell it to, I don't believe it does any compatibility checking on its own. You can still get the wifi hotspot feature to work even with Knox and the 4.3 bootloader, I don't think that was what they were trying to do with the update. There are threads discussing 4.3 and what changed, but there wasn't much obvious to the user. For now you can't go back if you're on 4.3, but there might be an exploit discovered down the road that lets you get the old bootloader and go back.
Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ?
Click to expand...
Click to collapse
Yes, they won't be available immediately though. It can take some time for the community to re-obtain root too, depending on how big the changes are.
With that, if I were to load 4.4 and not like it, could I flash back 4.3 ?
Click to expand...
Click to collapse
I think you alluded to the answer already, but it depends. It took a month or two before you could flash the stock 4.3 without the 4.3 bootloader. There were custom ROMs available that used custom kernels sooner, but there was a problem trying to use the stock kernel with the 4.2.2 bootloader. So, always read and read and read some more before flashing updates.
So far i think i got the hang of it. I have been modifying the phones original touchwhiz. I ended up freezing alot of files instead of deleting them so the ability to turn them back on is there. Some of the files while there are not meant to be frozen/disabled/turned off. I tried a few methods for keeping SuperSU over an ODIN with no luck. I do have a question though. If i turned off (but did not delete) alot of system files and were to run ODIN again will all of them including the bloatware be turned back on and restored? That would be bad if i flashed, lost root, then simultaneously had all the system files disabled with no way to turn them back on......
This also a dumb question but what exactly am i flashing with ODIN? Its a 1.5 GB file with Sprint and it is a tar that restores all bloatware and turns the phone status back to official so i can get OTA updates. Am i flashing the entire stock ROM or just the firmware? Its nice that i have not lost any existing apps or data. It just restores the bloatware and removes root
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
mikeprius said:
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
Click to expand...
Click to collapse
The .tar you are flashing from sprint is what we would call stock firmware image. This is the image that shipped on the phone from the factory. I'm an avid flasher and would highly recommend installing twrp or philz touch, creating a nandroid backup and giving some debloated touchwiz roms a shot. You'll see some significant improvement in battery life and performance and some really cool upstream features. I use odin as a last resort, when I need to go back to stock for whatever reason (ie domestic sim unlock) or have fubar'd my current setup past a point of no return.
I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
You know, I have been meaning to freeze the update app, thats always kinda been SOP with modded phones, though I know how much everyone loves their OTAs
I know I searched once before and couldn't find the name, as most don't seem to do it; which app do I need to freeze?
I think I am planning to wait for the official to drop, then try it for a bit hopefully from a TWRP backup before updating my bootloader and what not via fastboot (assuming Moto gives the dev editions an SBF again...)
I googled for FXZ... Which means Full XML Zip, but didnt seem to find what it does and, how it is important..??
Any xplanation wud really be helpfull...
Thank you..!
rohitdna said:
I googled for FXZ... Which means Full XML Zip, but didnt seem to find what it does and, how it is important..??
Any xplanation wud really be helpfull...
Thank you..!
Click to expand...
Click to collapse
It is the full ROM, so if you wanted to go back to stock, you would flash it, wipe user data, and be ready to go.
So, whn 5.1 is released, if i update it using Motorola device manager, the previous operating system which is 4.4.4 will be backed up, using FXZ...??
rohitdna said:
So, whn 5.1 is released, if i update it using Motorola device manager, the previous operating system which is 4.4.4 will be backed up, using FXZ...??
Click to expand...
Click to collapse
No, it's the full 5.1 so that when/if you screw up your phone you can fastboot flash the stock 5.1. Once you update fully, you can't ever go back. This just gives you the safety net of being able to restore a stock 5.1 system.
scryan said:
I know I searched once before and couldn't find the name, as most don't seem to do it; which app do I need to freeze?
Click to expand...
Click to collapse
MotorolaOTA.
tcrews said:
No, it's the full 5.1 so that when/if you screw up your phone you can fastboot flash the stock 5.1. Once you update fully, you can't ever go back. This just gives you the safety net of being able to restore a stock 5.1 system.
Click to expand...
Click to collapse
Stock 5.1 system and recovery!
You can NEVER* safely downgrade the bootloader and partition table of a Moto X!!!!!!!
* there was 1 exception to this that jcase and found and was able to use it to root 4.4.4 - if you are not jcase though, you should not try to downgrade motoboot.img or gpt.bin!!!!!!
JulesJam said:
MotorolaOTA.
Click to expand...
Click to collapse
Doh. Yeah stupid me, used to other phones with more cryptic updater apps... Guess thats what I get for not just trying to find it on my own. Thanks.
bump
JulesJam said:
I have pointed this out in several places, but I wanted to make a thread about it so that it gets more widespread attention.
When the 5.1 update is released, if instead of taking the OTA you use Motorola Device Manager to update, you will have a copy of the 5.1 fxz for your device on your computer. It will be in the folder c:\programdata\motorola\SUE\firmwares if you have a PC.
If the OTA has already begun to download on your device, then MDM won't update you b/c it will say there is an update in progress. So if you are rooted, you must delete or freeze the MotorolaOTA app. If you are not rooted, I think there may be some way to avoid the OTA but idk, you would have to read up on it. I think you may be able to wipe your data partition and/or cache if the download has begun in order to erase it, idk.
Click to expand...
Click to collapse
What's the difference between an FXZ versus an SBF? Now that the official 5.1 OTA is out for the XT1053, I need it to update my phone from the 5.0.2 soak
Sent from my XT1058 using Tapatalk
I tried to use mdm on the small 4.4.4 update. When I plugged my phone in it said my device was already in the middle of upgrading even though I did not install it yet. So once you are prompted by OTA how to get mdm to work? Mfastboot seems much easier. But yes, I want the file.
---------- Post added at 02:48 AM ---------- Previous post was at 02:38 AM ----------
I am pretty sure it won't be long for someone to release the image files once they are officially released. It usually doesn't take long.
Travisdroidx2 said:
I tried to use mdm on the small 4.4.4 update. When I plugged my phone in it said my device was already in the middle of upgrading even though I did not install it yet. So once you are prompted by OTA how to get mdm to work?
Click to expand...
Click to collapse
Back up the device then do a factory reset. Then put it in bootloader mode and start MDM.
If that doesn't work, take out the SIM card and after the factory reset, activate the phone but don't put in a google account or let it connect to Wifi and then go to settings and enable developer options and USB debugging and then connect it to your computer and start MDM.
demifalcon said:
What's the difference between an FXZ versus an SBF?
Click to expand...
Click to collapse
i use those terms synonmously although there may be a difference idk.
JulesJam said:
Back up the device then do a factory reset. Then put it in bootloader mode and start MDM.
If that doesn't work, take out the SIM card and after the factory reset, activate the phone but don't put in a google account or let it connect to Wifi and then go to settings and enable developer options and USB debugging and then connect it to your computer and start MDM.
Click to expand...
Click to collapse
demifalcon said:
What's the difference between an FXZ versus an SBF? Now that the official 5.1 OTA is out for the XT1053, I need it to update my phone from the 5.0.2 soak
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
JulesJam said:
i use those terms synonmously although there may be a difference idk.
Click to expand...
Click to collapse
Doing a quick google search told me this -
FXZ = Full XML Zip
SBF = System Binary File
I guess SBF cant be extracted by winrar etc but FXZ can be
Now that 5.1 is being officially released and rolled out, can we start this back up?
do i actually have to do the update to gt the fxz?
hey i tried to flash back to stock and run the MDM, but it said that i already have the newest version (KK)
and then i tried to install the new motorola update service, and run the MDM again.. but still it said that i already have the newest version (KK)
and now i run the OTA update because i dont know how to make it using MDM, i really want the FXZ file because i want back it up for me
sorry for my super bad english
I'm on mac.
Got the 5.1 Retail.en.GB update notice OTA. But i want to use MDM to capture the FXZ.
I connect and say check and it says no updates.
Any ideas??
Put your phone into airplane mode, reboot to recovery, erase cache, reboot normally (make sure you're still in airplane mode), connect to MDM, and it should see the update.