I'm wondering if you have an unlocked bootloader can you install a captured image of OTA update via custom recovery?
I just saw a post on here (and received the update myself to Motorola OTA services) about the potential for 5.1.1 update on Moto E 2015.
I really don't want to revert back to stock recovery to flash the update....
crazynapkinman said:
I'm wondering if you have an unlocked bootloader can you install a captured image of OTA update via custom recovery?
I just saw a post on here (and received the update myself to Motorola OTA services) about the potential for 5.1.1 update on Moto E 2015.
I really don't want to revert back to stock recovery to flash the update....
Click to expand...
Click to collapse
OTA does not work with custom recovery. You can try but it ends with error.
I realize that. Im wondering about a captured image of it.
Or are you saying that even manually flashing a captured update won't work via custom recovery?
crazynapkinman said:
I realize that. Im wondering about a captured image of it.
Or are you saying that even manually flashing a captured update won't work via custom recovery?
Click to expand...
Click to collapse
Dunno sure. But with Moto G even manualy captured update needs stock recovery with Lollipop system.
@devs
Is it possible to take said captured OTA images and make them flashable with custom recovery?
crazynapkinman said:
@devs
Is it possible to take said captured OTA images and make them flashable with custom recovery?
Click to expand...
Click to collapse
Perhaps if we can figure out where this is stored. Any idea what the file looks like / is named? I am actually attempting this at the moment, but I have no idea what to look for, and its needle-haystack here.
perhaps the file in /data/backup/pending/ "journal116651998.tmp"?
nm, think i found it.
/data/data/com.motorola.ccc.ota/app_download/
contains
Blur_Version.22.36.1.surnia_retus.retus.en.US.zip
Will upload shortly
Related
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
I've been thinking about reversing the CM12 install so I can play with the B320 or B321 updates. The problem is, I'm not certain of the reversal process. Do I have this right?
flash B148 via the dload method
FLash B309 via the dload method
Flash the B320 via the dload method
I'm sure I must be missing interim steps. Could someone list out the necessary steps?
After flashing stock recovery. Flash 309. Don't really need 148.
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Bill R said:
I'm going to ask a stupid question so brace yourself. :laugh: Isn't b148 the stock recovery?
Click to expand...
Click to collapse
B148 is the rom itself. Recovery can be stock. Or twrp.
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
robertbarber said:
If you did a backup of you Hauwei's stock rom couldn't you just restore from that using TWRP?
Click to expand...
Click to collapse
Yep.
Ok, now I understand. I went through three pages and could not find a download for the stock recovery. Is there a link?
Never mind. Found the stock recovery here:
http://forum.xda-developers.com/showpost.php?p=55617080&postcount=7
Then remembered I had made a backup prior to loading CM so it should be at least 309. I'll still have to flash the stock recovery to get from B309 to B320 correct?
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
xordos said:
yes, if its b309, I think you have to install b320 pkg locally using stock recovery. last time for me, I cannot see b321 ota when mine is b309, i must first 'bring' it to b320 in order to see b321 ota.
Click to expand...
Click to collapse
That's what I ended up doing. TWRP restore to B309 then flashed the stock recovery, then flashed B320. I haven't registered my EMIE number yet as I'm not sure if I'm going to stay with the stock lollipop.
One interesting note; when I flashed B320, I had to facotroy reset 3 times because every time when it came to restoring my apps, it would, like, time out and flash past it. The fourth time I was ready for it.
I was at work so I never got a chance to capture the D/L. It was small, around 4MB. Anyone else see it?
Probably the Nov security update posted here
McChen147 said:
november security update:
https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
Click to expand...
Click to collapse
Can install with root?
TWRP Failed to install
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
When I flashed Marshmallow, I went back to unrooted. So the OTA worked fine, but not sure if you can stall with Root.
No.
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
OTA Update
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
ImzTinoz said:
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
Click to expand...
Click to collapse
This is normal. The warning is displayed because you have modified your device. It means nothing for the functionality of your tablet.
You cannot use the OTA update if your system is modified. You must be stock unrooted, unless you used the systemless root method in which case you need to restore stock recovery and kernel, then OTA will work.
This zip is not meant to be flashed in TWRP, it's the official OTA update which needs the stock recovery and completely unmodified /system partition.
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
harryspar said:
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
1) Will I lose functions such as the fingerprint reader if the device is rooted?
if you install the stock rom you will keep this functionality otherwise you need to wait concerning CM13 build
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
there is always a risk but minor
harryspar said:
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
wickedesires said:
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
Click to expand...
Click to collapse
Right, I remember this happening with other devices, as the OTA uses a recovery script.
I wonder if there will be nag screens for OTA's. This rendered my wife's S4 so annoying to use, with a persistent notification, until I found a block method (disallowing notifications didn't work since I'd have had to disable notifications for the entire Android System UI...)
harryspar said:
I wonder if there will be nag screens for OTA's.
Click to expand...
Click to collapse
I went about 5 days before I installed the b140 update and I don't recall any annoying notifications. I know exactly what you mean though my s5 active did the same thing because I didn't want to update and lose root. I finally found a way to disable it but like you said it was very irritating.
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Paisley Pirate said:
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Click to expand...
Click to collapse
For those wondering about updating to B180.....
See this post and links in it for how we updated before if the phone was already unlocked bootloader/rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
reloaded 170 full version on and it worked fine. Need to clean it up, as it threw the bloat back on - but didn't lose anything. Unfortunately, between 2 jobs, and moving (working on new house now, move in a couple weeks, then work on old house to sell it) I'm not seeing much time in my future to play with it much.
Is B180 rootable?
I imagine like the other version so far, it should be.
Ad86shwks said:
Is B180 rootable?
Click to expand...
Click to collapse
I have B170 installed. But I have it debloated, rooted, and custom recovery on it. I want to update to B180. Anyway someone can make it a standalone update? Like B170?
im waiting on the files from someone and i will release a b180 stock update as well as update my rom to b180 once i get the b180 files
b180 uploaded stock preroot atm will do full stock soon b180
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
hi5five said:
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
Click to expand...
Click to collapse
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Did you previously have B170, then used your zip to update to B180?
madvane20 said:
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Click to expand...
Click to collapse
i flashed b170 stock then flashed my b180 stock if wifi is broke i can redo it but it worked on mine just let me know
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
Click to expand...
Click to collapse
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Thanks for that detail. I wonder which partitions aside from the boot partition get modified after rooting that then breaks OTA from working.
dabadguycr said:
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Click to expand...
Click to collapse
---------- Post added at 10:50 PM ---------- Previous post was at 10:35 PM ----------
I don't think there's any way to put your phone back to the state where an OTA will work - at least nothing we currently have on the XDA forums here that I've seen.
You could always try what you wrote below - I expect OTA will fail. If it fails, you could flash B180 - which I believe is unrooted from what I recall @clsA writing about his method to flash B180 in the B170/B180 thread by @madvane20 - but please double check on that before doing it since you want to be able to remain unrooted.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Click to expand...
Click to collapse
hi thanks for this advice buy my device does not have this directory or files. I am in the same boat on 170 slim and fast, got AT&T update and now in force reboot update and fail loop. i really want to find a way to make it stop force rebooting? surely something i can do in twrp terminal. any advice? but alas I might just have to reflash.
make sure u mount system in twrp that folder and file should be there and make sure to clear cache like the other post said