Related
I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?
you could always root after updating since it obviously doesn't stop you from rooting
jonnybueno said:
you could always root after updating since it obviously doesn't stop you from rooting
Click to expand...
Click to collapse
I know, but I had a hell of a time getting done so I don't want to go though it again. It took a long time to get adb running in recovery, after that it was cake.
Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip
TNS201 said:
Think I found it, did its like the droid. Dunno if it will stop the updates yet, but still need to find the file it downloaded.
Went to
/system/etc/security/
renamed otacerts.zip to otacerts.bak
Anyone install the OTA update after doing root? Did it break it?
I would do it but, I already done this twice now and it was hard as hell to get shell in recovery
Damn whenever I reboot it goes back to .zip
Click to expand...
Click to collapse
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC
xcsdm said:
Unfortunately, even if it stuck, renaming otacerts.zip causes horrible battery life. It will continuously download the update, over, and over. It will download it, check the certs to see if its good. See its bad, go again, and again...
XC
Click to expand...
Click to collapse
Yea well it doesnt stop it anyway, it already downloaded the file.
I wonder if theres any other way to stop it from nagging.
Much simpler to do the update and then reroot.
via my dinc...
krelvinaz said:
Much simpler to do the update and then reroot.
via my dinc...
Click to expand...
Click to collapse
Will it kill my root, I got superuser.apk installed already and that functions properly, will the OTA mess up anything?
don't know. I don't know anyone else that is doing what you are doing.
Re-rooting isn't that hard. I've done it 10-12 times before there was a way to make it stick. Just a little typing assuming you get access.
Chances are you may re-root again anyways as they come out with better packages to do it.
TNS201 said:
I figured I'd start a post for this since some people probably don't want to update after doing the root process, or maybe it would break root.
Is there a way to delete the OTA update off your phone and stop it from downloading it again and nagging you to update?
Click to expand...
Click to collapse
I'm not rooted yet so I can't say for certain, but you can almost certainly shut down auto-OTA check by editing the build.prop and or userinit.sh in /system. Those two files control most of the automation on your Droid! Good luck, and if I helped you, send me a 16gig SDcard so I can root too
i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.
I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.
crappypunk said:
i just deleted the otacerts.zip in /system/etc/security/ and now it says my system is up to day in about phone.
Click to expand...
Click to collapse
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
I tried rooting my phone since the day root was achieved using a few different sd cards I have and failed every time. Last night I decided to downgrade and got my phone rooted on the first try. I'm no noob. I've established ADB on my HTC Vogue which is a WinMo phone running Android, I've rooted a My Touch 3G and a Hero but until I downgraded my phone I couldn't get root. At least not with my sd cards so for me running the OTA then rooting is just not an option. I will just deal with it until NAND write access is achieved.
krelvinaz said:
Still not sure why you went this way.
Unless you installed Superuser recently, you don't have that much "root" and will need to do it all over eventually again anyways.
It would be a lot simpler, if you did the OTA first, then re-root your phone using the newer instructions which give you a more rooted SAFER setup.
If you didn't do the newer Superuser, you now have a potentially vulnerable phone that an app can exploit because they can do su and not need approval first.
Click to expand...
Click to collapse
Some of us are not able to easily get into adb shell, often taking days of trying (hundreds of reboots). I was finally able to get in, and don't ever want to have to do it again. I have wifi tether working, and that is plenty for me until they come up with an easier way to get into adb shell in recovery. I am assuming this guy is in the same boat (as far as how hard it is to get into adb shell).
It won't matter soon. Wait until the Unrevoked custom recovery comes out in a few days and then you can find a nice custom rom that won't bug you.
-------------------------------------
Sent via the XDA Tapatalk App
I have pre order version and so far its been great. When the ota came to me I clicked install and it errored out...it has Not prompted me a single time since and everything has been perfect and I'm rooted...any thoughts on this?
-------------------------------------
Sent via the XDA Tapatalk App
askwhy said:
I can confirm that running the OTA after rooting will temporarily break root. You *will* have to redo the adb in recovery > payload before your root apps or superuser.apk will work again.
The good news is that you *can* simply redo it. No big deal once you are comfortable getting into adb in recovery.
Click to expand...
Click to collapse
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?
PDAnuby said:
Yeah if it were only true, but cannot get back into adb recovery unless i down grade, now what?
Click to expand...
Click to collapse
Doesn't matter now. You should be able to start flashing ROMs soon with the Recovery Reflash tool from Unrevoked http://unrevoked.com/recovery/
Those Unrevoked guys are really hooking us up
I too had an incredibly hard time getting into the shell... I finally down graded, was able to get in (I don't' think that got me in, as it all ended up in being timing that I just had to get).
anyways, i've now installed the unrevoked recovery tool and updated to the latest clockwork via rom manager.
Anyways... that nag screen is getting old, so which rom are people installing on their systems that's getting rid of the nag / is an updated one?
I do NOT want to have to go through the root process again, what a pain it was for me...
First apologies if this is in the wrong area. Cant post in the android development thread.
I have a desire HD, which I have already updated the ROM, "Android revoultion HD 5.2.6" (Great work and thanks to all the devs for that). So in order for me to have done that I have basically rooted my phone etc and followed the instructions on how to go about installing roms. It was a while ago.
Q1.
What I cant understand is why is my phone not allowing me to update system files (trying to update gps.conf file)? It wont save the file, because its read only. Thus meaning I dont have S - Off. BUt I must have done that in order to have updated my rom in the first place right?. HOw did it go back to S Off (unless I did that specifically and forgot).
Q2.
Now I need to be S Off in order to edit this file, looking at the thread it said that I need to go back to an earlier version of the rom and radio (somethign I am reluctant to do, as it was pretty stressfull the first time round). If I already went through that process do i need to go back to an earlier version or can I just do the s -off http://forum.xda-developers.com/showthread.php?t=857537
without going back to an earlier version of the radio and rom.
Again apologies if this has already been asked, stupid question or in the wrong place (probably all three).
Reza
hey dude, under my experience, for a beginner, Radio-off is more than enough, no need to be s-off( too risky). with radio-off you already are able to flash rom, change radion, edit system files.....the only thing different with s-off is that you can use fastboot but not for radio-off, however there are a few different ways around that let u do those same thing without using fastboot.
to edit your system file, download ROOT EXPLORER, and got the root, on the top, there is an option that u can change from read only to write
hope this will help
rezasblade1 said:
First apologies if this is in the wrong area. Cant post in the android development thread.
I have a desire HD, which I have already updated the ROM, "Android revoultion HD 5.2.6" (Great work and thanks to all the devs for that). So in order for me to have done that I have basically rooted my phone etc and followed the instructions on how to go about installing roms. It was a while ago.
Q1.
What I cant understand is why is my phone not allowing me to update system files (trying to update gps.conf file)? It wont save the file, because its read only. Thus meaning I dont have S - Off. BUt I must have done that in order to have updated my rom in the first place right?. HOw did it go back to S Off (unless I did that specifically and forgot).
Q2.
Now I need to be S Off in order to edit this file, looking at the thread it said that I need to go back to an earlier version of the rom and radio (somethign I am reluctant to do, as it was pretty stressfull the first time round). If I already went through that process do i need to go back to an earlier version or can I just do the s -off http://forum.xda-developers.com/showthread.php?t=857537
without going back to an earlier version of the radio and rom.
Again apologies if this has already been asked, stupid question or in the wrong place (probably all three).
Reza
Click to expand...
Click to collapse
hey dude, under my experience, for a beginner, Radio-off is more than enough, no need to be s-off( too risky). with radio-off you already are able to flash rom, change radion, edit system files.....the only thing different with s-off is that you can use fastboot but not for radio-off, however there are a few different ways around that let u do those same thing without using fastboot.
to edit your system file, download ROOT EXPLORER, and got the root, on the top, there is an option that u can change from read only to write
hope this will help
DDFF said:
hey dude, under my experience, for a beginner, Radio-off is more than enough, no need to be s-off( too risky). with radio-off you already are able to flash rom, change radion, edit system files.....the only thing different with s-off is that you can use fastboot but not for radio-off, however there are a few different ways around that let u do those same thing without using fastboot.
to edit your system file, download ROOT EXPLORER, and got the root, on the top, there is an option that u can change from read only to write
hope this will help
Click to expand...
Click to collapse
+1 ten characters
Thanks you very much that worked. I had already tried installing root explorer and doing that, but never managed to set it as rw. it was always ro. Thanks for the help.
If anything I hope this has helped someone else.
Appreciate it.
rezasblade1 said:
Thanks you very much that worked. I had already tried installing root explorer and doing that, but never managed to set it as rw. it was always ro. Thanks for the help.
If anything I hope this has helped someone else.
Appreciate it.
Click to expand...
Click to collapse
enjoy ur new ROM
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol
The problem is with 6.0, Google made changes so that the only way to achieve root is to modify the boot image instead of the System image. Since the VS986 has a locked bootloader, the phone will refuse to boot if you modify it from stock, potentially bricking it.
6.0 + locked bootloader = no root.
As I said above, I'm not wanting to push root to the image, I realize it's blocked now. What I'm proposing is to modify the image to achieve 2 main things, ad blocking and tethering. If we push the 2 files needed for that, then flash the image, root will not be needed for those to continue to work. It won't work if the system is somehow checked for modifications, but kdz should fix that if it don't work.. Anyone willing to try it?
I can't help you with root but Verizon is no longer charging for tethering on most of their plans. I use it all the time on my G4 using stock tethering. Double check with Verizon.
People who still have unlimited data don't have tethering included so we need the modified hotspot. And like I already said, I'm not looking to have root, what I'm wanting to try is a little different. I haven't taken the plunge to 6.0 yet, but I'm looking for someone who has but kinda regrets out cuz they lost root.
jweber228 said:
I haven't took the plunge to 6.0 yet because I'm not ready to part with root yet but what if we were to modify the system.img and re-flash it? I mean similar to injecting root, but don't inject root. We could at least bock ads with a hosts file, push the file to enable tethering, and debloat. Once done, none of those things require root other then to maybe update the hosts file. Anyone that has updated willing to try? I can help by getting files and commands together. Anyway, just thinking out loud here, thanks for reading lol
Click to expand...
Click to collapse
That is exactly what i would like to do. A little debloating, updating hosts and add cerberus as a system app.
this is a step in the right direction : http://forum.xda-developers.com/g4/general/guide-how-to-modify-img-partition-t3196994
This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.
I guess we have to use a fully fledged kitchen. I was hoping to circumvent that
Gesendet von meinem LG-H815 mit Tapatalk
fr4nk1yn said:
This has been asked a few times in the "Root Injection" thread, once by me, with no answer.
It appears the main problem is the download mode exploit may be closed. Entering commands in the send-command app returns "fail".
I once got the command to backup entered without failing but it ran for almost an hour without generating the system.img.
Click to expand...
Click to collapse
In addition that exploit getting patched, Android 6.0 was changed by Google so that you can only achieve root by modifying the boot.img and kernel, not just the system partition. Since the bootloader is locked, if you do manage to modify the system img, you would at best see no results, or at worst brick your phone.
Yes, yes, I know... from the factory!
No, what I really mean is, these RETEU, RETIN, RETLA, etc. zip files hosted on lolinet, or passed around in other forum threads. Are they all just leaked by helpful Moto/Lenovo employees? Or is there some way to extract the firmware
1) off of a pristine Moto Z Play, or
2) by intercepting the OTA process somehow?
The question is relevant because I have a brand-new Z Play that I'd like to unlock and flash LineageOS on. But obviously, I'd like to preserve the option of wiping everything clean and going back to stock, including OTAs, if I change my mind later. (I know that the bootloader cannot be re-locked; that's ok.) After spending almost a whole day slogging through the MANY threads here, I think I have a pretty good understanding of how to restore stock from a factory image file---the ones with all of the sparsechunks. But my phone is RETUS, and most of what you can find online is from other world regions. Of course there is also RETAIL, but nobody has ever explained (and perhaps nobody knows) how that differs from the region-specific images, and what consequences there could be to using RETAIL instead of a proper RETUS image. Random "it works for me" testimonials are always encouraging to hear, but hardly the basis for real confidence! So, obviously, it would be great if there were some way to extract the firmware off of my own phone prior to unlocking. Otherwise, it does seem a little bit crazy to be flashing factory images provided by strangers on dodgy file-sharing sites.
(There are NANDroid backups, of course, but if I am understanding the situation correctly, you need much lower level than that for a proper reversion to stock. I.e. you need to replace the original recovery, and probably other stuff too.)
Please, enlighten me
https://motoota.lolinet.com/index.php?model=XT1635-02&sv=Blur_Version.26.201.1.addison.retail.en.US&carrier=retin&sn=
it come from motorola rsdsecure, for instance : https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (it is not the last version)
Seems to be an IP filter, and some countries are not able to download the same last versions than others. so there is some shared files on afh or others to help, but for me i prefer to DL directly from motorola
Interesting.
After the OTA updater has downloaded an update, but before the upgrade process is started, does the zip file exist "in the clear" on the phone? And could it be retrieved with adb pull before saying yes to the update?
Ok, I think I answered my own question. There is a difference between the OTA update files and factory image files. OTA updates are the ones with "Blur" at the beginning... maybe an acronym for something-something-update-something? So @talktosam, your link is not applicable because those are OTA files; you can try to sideload them if your phone is already running stock firmware, but you can't use them to restore a fully wiped phone back to stock. The factory images I'm asking about are the ones with all of those "sparsechunk" files inside. (Please correct me if any of this is wrong.)
So that Motorola rsdsecure site probably does not exist for the OTA updater, as I'd initially thought, but for service personnel?
mark04 said:
Interesting.
After the OTA updater has downloaded an update, but before the upgrade process is started, does the zip file exist "in the clear" on the phone?
Click to expand...
Click to collapse
Yes, somewhere in /cache.
mark04 said:
And could it be retrieved with adb pull before saying yes to the update?
Click to expand...
Click to collapse
Of course. It is for instance easily possible to move away or rename before installation using eg total Commander if it has root rights.
Blur...something...zip is right.
yes u are correct, but any way to download factory image, its a life saver for some users also (mine search these files bcz am on stock bootloader unlocked)
tag68 said:
Blur...something...zip is right.
Click to expand...
Click to collapse
But just to confirm, those zips you can only use with adb sideload; you cannot use them to flash over a different ROM and return to stock. Correct?
I never sideload. There is the possibility to apply it to the wrong channel. You can put it to the original place to apply and let OTA do its work.
Afaik you also can sideload that blur.