hi guys.i have nexus 9 with unlock bootloader, rooted mmb29s lte and twrp installed.do i need to flash all mmb29r stock rom or there are another method how to flash update from google.
thanks in advance
Sent from my Nexus 9 using Tapatalk
As no one else replied.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image/
Can be done without wiping data if needed.
Also checkout Chainfire's Flashfire App, if you have systemless root and an unmodified system, which can update by ota.
Can also be used to flash factory images.
Alternatively just flash boot, system and vendor images.
Reboot to recovery, wipe cache and dalvik cache, flash, reboot system = dirty flash.
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
TheMuffnMan said:
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
Click to expand...
Click to collapse
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are you hoping to update by OTA or using it to flash factory images?
corkiejp said:
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are hoping to update by OTA or using it to flash factory images?
Click to expand...
Click to collapse
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
TheMuffnMan said:
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
corkiejp said:
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
Click to expand...
Click to collapse
I say brick, I actually mean like boot loop - where I'd need to do a full erase and rebuild. Not an actual creation of a paperweight.
it hard to flash whole rom for every update.and i once have brick my tab.twrp not recognise internal storage,it state internal storage 0mb.
Sent from my Nexus 9 using Tapatalk
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Then I just did my usual process, extracted each file, flashed each - except recovery which I flashed with TWRP 3.0.0.2 and then rebooted into Recovery where I flashed SuperSU 2.6.6 Beta, wiped Dalvik/cache and then booted tablet.
Retained all my data and it seems to be running fine.
TheMuffnMan said:
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Click to expand...
Click to collapse
Any chance you still have access to the logs? Try posting to the linked thread.
Chainfire said:
In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.
Click to expand...
Click to collapse
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
corkiejp said:
Any chance you still have access to the logs? Try posting to the linked thread.
Click to expand...
Click to collapse
I'm sure I could probably dig them up!
corkiejp said:
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
Click to expand...
Click to collapse
Didn't know about the 2.67! Already had the 2.66 Beta on the device so I just flashed that guy.
Related
This CWM/TWRP flashable zip is 4.4.4 from my dump of 212.44.26.ghost_att.ATT.en.US (ATT xt1058).
The stock ATT 4.4.4 kernel is within the zip and must be flashed manually.
Safestrap and root are 'baked in', but the rom is otherwise stock.
I am using the modem from 4.4.2 without issue, and I plan to create a new zip when the official sbf is available.
The instructions below are mostly for rooted, locked ATT phones using safestrap.
This zip does not alter your bootloader.
I was able to upgrade from 4.4.2 without a wipe/factory reset.
This rom installs Safestrap. (I welcome exact instructions on removing this from the rom.)
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
Instructions for ATT locked phones:
If you can still get permanent root (pre 4.4.2 bootloader), then you can use safestrap to install this zip of ATT 4.4.4 and get root again.
Prerequisite:
Rootable Moto x (not temporary root)
Have fastboot (motorola version for this phone) and PC drivers installed and working
BACKUP ANYTHING YOU DON'T WANT TO LOSE.
Instructions:
root (thanks jcase)
install safestrap (thanks Hashcode and Team Win)
Make a nandroid and copy it off the phone!?
download zip to sdcard (motox-444-212.44.26.ghost_att-from-dump-ss.zip, link below)
extract boot.img to the fastboot directory of your PC
enter safestrap recovery (twrp) and activate the stock-slot
twrp: flash rom (motox-444-212.44.26.ghost_att-from-dump-ss.zip) to the stock-slot
twrp: reboot to bootloader (home -> reboot -> bootloader)
on pc: execute fastboot commands (below) then power on normally.
install supersu (thanks chainfire) from play store
Fastboot command to flash the kernel:
Code:
fastboot flash boot boot.img
Fastboot command for locked phones not using MotoWPNoMo with pre 4.4 bootloaders:
Code:
fastboot flash recovery boot.img
Thanks to touchpro247 for making the raw OTA available. Also thanks to iKrYpToNiTe for his safestrap selinux metadata code.
Download:
motox-444-212.44.26.ghost_att-from-dump-ss.zip: http://www.androidfilehost.com/?fid=23622183712458373
anyone try this one yet?
Installed this on my DE. Works perfectly. I actually have better reception. I'm on ATT btw.
Thanks a lot!
Sent from my XT1058 using XDA Free mobile app
bahhh now all I need is one from VZW
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
goonigoogoo said:
Thanks! This seems to work fine for my unlocked Brazil XT1058 using TWRP. The only thing is now that whenever I start the phone there's a 2-3 second screen saying Safestrap disabled (I've never installed Safestrap). Is there a logo flash that will remove this?
Click to expand...
Click to collapse
Because this came from my /system dump, it has safestrap there. I'm not sure of the easiest way to perfectly remove it, and I welcome input on the issue.
I'll update the op.
hey guys i have a 1053 rooted i am a noob sorry how can i get this to work for me
g4ess said:
would this work on 1053 on att or nah
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Yep. Works well. I now have visual voicemail.
Sent from my XT1058 using XDA Free mobile app
can't get it to install how to u manually flash kernel
Sent from my XT1053 using XDA Free mobile app
Weapondrift said:
bahhh now all I need is one from VZW
Click to expand...
Click to collapse
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Has anyone seen if Faux's kernel will work? I'm waiting for my phone to charge before I flash. I'll report whether or not if no one else does.
Edit: So far, it's working great on my 1053 DE with Faux's latest kernel on AT&T.
nice
Thanks Ctrl-Freak for this. I appreciate you putting it together. I just upgraded from 4.4.2 to 4.4.4.
C:\>adb shell getprop ro.boot.write_protect
0
Click to expand...
Click to collapse
Sorry if this question is aggravating but if I flash this on my rooted XT1053 will it wipe my internal? Just trying to be sure, never flashed anything carrier specific. I flash and reboot right? Or do I also need the kernel? I read the OP but I'm wondering if I do all of that and or need safestrap.
Edit: I think I got it.
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely. Installed under stock slot with root from 4.2 android and Safestrap. Went through like a charm. Still have root, had to reboot to write protect off mode and install Xposed again, but otherwise everything is as it was...except that I'm on 4.4.4 now! I didn't even lose my original bootloader (the globe one that looks so sexy) that I had to manually install after their damn PlayStore update replaced. Not sure if this will stick for others that haven't done that already.Thanks!!!
Click to expand...
Click to collapse
I should clarify. I had the old root from 4.2 that was on the phone when I purchased it. Updating to 4.4.4 was coming from 4.4.2 previously.
Apollo_316 said:
I did this update as instructed on my AT&T, locked bootloader XT1058 but I skipped the fastboot commands entirely.
...
Click to expand...
Click to collapse
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
iSecks said:
This one doesn't work? http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
Click to expand...
Click to collapse
nope. That didn't do anything
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
beefgoat said:
I'll have to agree with you on the 4.4.4 kernal and the android is bug. I was using Faux's 4.4.3 kernal with this ROM and still had the os bug. Now, it's all gone after I manually flashed the new kernel.
Click to expand...
Click to collapse
Ctrl-Freak said:
If possible, I recommend that you go ahead with the official att 4.4.4 kernel packaged within the zip (boot.img via fastboot). It is likely that this latest kernel includes important fixes. (For example, the Android OS battery issue seems fixed.)
(I skipped the modem because I don't know how to package the modem partition into a flashable image.)
Click to expand...
Click to collapse
You were quite right. I'm having battery issues (now) and my WiFi/Bluetooth won't turn on at all, even in safe mode. Was getting 52 hours consistently on battery, now I'm down to 36 hours tops! Phone started being 'awake' while the screen was off. I went back and flashed the boot, all good now. I'll report back on the battery issue. Thank you guys for setting me strait! :highfive:
Possible anyone knows how to disable the annoying OTA updates permanently? Remedied for now, being on 4.4.4, but I was trying to avoid 4.4.4 for now and the update notification that I couldn't kill, greenify, stop on boot, etc., is what drove me to this post. I'd love to turn these off and upgrade at my leisure in the future.
This is what I've been waiting for. Android OS is where it's supposed to be. Thank you Ctrl Freak for the upload.
OK, the pic didn't upload.
Is this even possible if my device is rooted and running custom kernel?
Thank you!
Short Answer ----- No!
Long answer, you need to be completely stock, with an untouched system partition, stock recovery and boot images to accept OTA.
Even with systemless root, if something has modified the system OTA's will fail.
corkiejp said:
Short Answer ----- No!
Long answer, you need to be completely stock, with an untouched system partition, stock recovery and boot images to accept OTA.
Even with systemless root, if something has modified the system OTA's will fail.
Click to expand...
Click to collapse
Thanks. I appreciate quick response.
dirtblade said:
Is this even possible if my device is rooted and running custom kernel?
Thank you!
Click to expand...
Click to collapse
if you're bootloader is unlocked you can manually flash the updated images via fastboot
Flashfire App is an option.
If your system partition is completely stock, untouched by root file manager/twrp and you have systemless root.
Chainfire Flashfire app should be able to apply the OTA even with a modified kernel, as it restores the stock boot and recovery images.
Chainfire said:
Release notes: https://plus.google.com/+Chainfire/posts/FjWwBm9vGyj
Changelogs: http://forum.xda-developers.com/showpost.php?p=59962696&postcount=8
Enjoy, and remember to re-report any issues, even if previously reported for an older version.
Click to expand...
Click to collapse
Chainfire said:
v0.27 released - https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Click to expand...
Click to collapse
I'll try and keep this short and to the point. If you unlocked your bootloader and flashed TWRP and SuperSU, theirs a Good chance your phone will not return to stock and take OTA updates. Many of us have tried but for some reason the updates just fail.
Well we are lucky and someone captured and posted the 3 known updates and I'm going to show you how to flash them
New ~ All in One ~ update Instructions in Post 2
We now have a new way to do this, So the information below is just for information sake So bare with me while I get the Guide updated...
Other Files you may need
H1611.TWRP.New.img <<- This is the New Twrp by yuweng I Highly recommend everyone use this Version
minimal_adb_fastboot_v1.4.1_setup.exe
Huawei_Android_phone_drivers(1).rar
I have been working on this for some time and I now have an ALL in One Flash solution
This will allow you to flash a Single Rom to Update or Downgrade your firmware and Rom
As with any firmware update or downgrade I'm not responsible to what happens to your phone you do this at your own risk
(rest assured I have tested all these files and my phone is fine)
The Flash instructions are the same as any rom flash on this phone
Step one is to Boot to the bootloader and boot H1611.TWRP.New.img
fastboot boot H1611.TWRP.New.img
Swipe to allow modifications to System
then choose Mount and check system and cust
Select Storage Micro SDcard
Next is install and choose your Bxxx_Full_Update.zip
Swipe to flash
Reboot
That's really all their is too it, Just choose the File below that you want to update or downgrade too
Note: The phone always loads the AT&T logo and reboots the first time and then loads normally
First boot will take you to the setup screen if you formatted data
Another thing i noticed while test flashing these files is that the Data partition becomes Encrypted after the flash
This means before you can restore a data backup or flash a Rom like CleanRom (it includes data) you'll need to Format Data to UN-encrypt it
Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade.
AS Always make a complete backup of your phone before you start any flashing
Downloads
~New~ B180_Full_Update.zip
Note about B180 - If you have no wifi or the phone won't boot simply extract the boot.img from the rom and flash it with TWRP (Install Image) or fastboot (fastboot flash boot boot.img) also the AT&T Logo is missing for now but everything else works
Thanks To @madvane20 Download >> B170 Stock Full Update with Firmware
B160_Full_Update.v2.zip
B150_Full_Update.zip
I had to make B140 into 2 flashes but it works the same just copy both files to your phone and Flash A then B
B140_Full_Update.A.zip
B140_Full_Update.B.zip
B130_Full_Update.zip
Huge thanks to @madvane20 for helping with the partition layouts and testing and to @worstenbrood for the Huawei Update Extractor tool
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
divineBliss said:
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
Click to expand...
Click to collapse
You start at the 2nd half of the updated guide B140 to B150
the process is the same no matter what version your on
So I should start with B130 stock files even though I'm in B140 rooted right now?
clsA said:
You still start at the top and substitute the B150 files where their needed
the process is the same no matter what version your on
Click to expand...
Click to collapse
divineBliss said:
So I should start with B130 stock files even though I'm in B140 rooted right now?
Click to expand...
Click to collapse
... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We have the B150 files and the guide is updated
If I can get back to B140 stock and take the B150 OTA, which files do you need?
clsA said:
The guide is not complete ... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We don't have the B150 files yet so it's hard to complete the guide
Click to expand...
Click to collapse
divineBliss said:
If I can get back to B140 stock and take the B150 OTA, which files do you need?
Click to expand...
Click to collapse
is that a trick question ? if you could get back to stock and take the OTA this post wouldn't be necessary now would it ?
The whole point of the thread is that no one who rooted has been able to return to stock and take an OTA
Why bother updating? Isn't someone working in Lineage for this phone?
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
no one has posted any threads about it
you should still try and be on the latest security patch while you phone is stock
@RN_ReFlux Thank You ! for getting the B150 backup and /cust.img
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
Yes, someone is working on it but it is best to have your ROM up to date. You may not see a need for it but a lot of others see a need.
clsA said:
@RN_ReFlux any luck getting the B150 backup and /cust.img ?
Click to expand...
Click to collapse
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
Thanks ... I'll post the files to my AFH account if you can share them through google or dropbox ..etc
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
divineBliss said:
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
Click to expand...
Click to collapse
Requested it about 12 hours ago
Uploading to drive now.
Sent from my SM-T530 using Tapatalk
divineBliss said:
...
Click to expand...
Click to collapse
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
flash your stock B140 system/boot/recovery and stock b140 /cust
force flash the dload/update.app for b150 with the dialer code
boot TWRP restore stock B150 system and dd the B150 /cust
Flash SuperSU and Factory Reset (< optional)
reboot system and it boots to a clean B150
Click to expand...
Click to collapse
Guide is updated !
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
clsA said:
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
Guide is updated !
Click to expand...
Click to collapse
divineBliss said:
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
Click to expand...
Click to collapse
Yeah me
Sent from my Nexus 6P using Tapatalk
Be careful upgrading from B130 to B140. Went from stock non-rooted B130 to B140 using the SD card update method and hidden menu. While it went through the update process without reporting an error but after auto reboot it still showed the same version but lost WIFI functionality, mac address showed mostly 00s and can't restore full backup from TWRP without errors on /data, etc.
Anyone know if there are .img equivalent of 2017-01-26-H1611.B130.stock.complete to attempt restore from either fastboot flash or dd?
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse