Related
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
nigelhealy said:
i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
Click to expand...
Click to collapse
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
hp420 said:
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
Click to expand...
Click to collapse
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
rafaelrgi said:
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
Click to expand...
Click to collapse
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
rafaelrgi said:
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
Click to expand...
Click to collapse
sorry, didn't see you were asking about fastboot. no, I didn't flash the factory image. I didn't want to go that far and didn't really care enough to do a full wipe
Have you tried Magisk? Could potentially work
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
apply OTA to rooted phone
Could someone please give me this zip ota moto g4 play I need this file since I thank you.
VR25 said:
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
Click to expand...
Click to collapse
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
hamelg said:
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
Click to expand...
Click to collapse
You only need to restore SYSTEM, OEM, BOOT AND RECOVERY images. That's all you'll ever need. NEVER touch other partitions, unless you are upgrading.
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
adb shell
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This command will give you the names of the SYSTEM and OEM partitions of your device, Moto G4 Plus. For example, for Moto Z Play (my device), they are mmcblk0p53 and mmcblk0p51 respectively.
So, the commands would be (again, that's an example for MOTO Z PLAY):
Backup
dd if=/dev/block/mmcblk0p53 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p51 of=/sdcard/oem.img
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Thanks much VR25.
With your help, I have successfully applied the latest OTA
hamelg said:
Thanks much VR25.
With your help, I have successfully applied the latest OTA
Click to expand...
Click to collapse
Confused. The VR25 guidance is when you had taken a full backup when stock, how to restore back to stock to then apply the OTA. You are describing how to apply the OTA on a rooted device without a pre-rooted backup?
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
nigelhealy said:
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
Click to expand...
Click to collapse
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
TheEvilVirus said:
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
Click to expand...
Click to collapse
Yeah, others were just saying too high a level to not actually helpful. As I did this last week I'll tell you now is as step by step as I can to actually try to be helpful.
Firstly you need to know you will wipe data, there's no avoiding it, that I could find so backup everything, that can be a mix of TWRP backup of data to SDCARD external, USB OTG, or Titanium backup to online / SD / OTG. In my case I prefer to simply install everything and configure everything from scratch.
Follow this guide to return to stock.
In my case I'm on Ubuntu Linux desktop, fastboot got a "no permissions" type message so I had to sudo in front.
The stock for your device, well look at your device Status page now before you start, Settings -> About Phone -> it says Software Channel "retus" so when I go to the list of ROMs in the above guide go to mirrors.lolinet.com - firmware - moto - harpia - official - then I went to Retus, you'd go to a different one probably.
Note these are old stock ROMs I think from September so there have been one or two updates since then.
Follow the step by step guide, basically lots of fastboot commands.
The step where it says fastboot oem lock it bawks and say fastboot oem lock begin and that will do another wipe, so given a later fastboot oem unlock would do a 3rd wipe I didn't do the oem lock, I left mine unlocked and that worked fine.
Let it boot, setup, you will then be in an old stock ROM, then if it doesn't offer to do an update, go into Settings, System Updates, and trigger it to look. It will then download and apply a stock OTA ontop of the stock ROM. In my case it was 1 OTA, 1 update, then that that complete. You then are on stock current ROMs.
Then root and whatever you want.
But note, to get to the impending N OTA, you'll probably have to right back to the top here because your rooted Moto G4 Play will likely refuse the future OTA as the system is modified, so you'd have to repeat, return to an old stock ROM and then let it go through the 1 or 2 or 3 OTAs to get to that future release.
Hence you'd be doing the return to stock twice.
If the mirrors could be updated to newer stocks it would bypass the OTA. My other phone - the OnePlus3T they offer mirrors of full ROMs, they are far easier to use because if you are rooted you download the full ROM not just the delta incremental of the change of the OTA, and then you can flash in recovery the full ROM and it ignores the system state, and no wiping of data. The fact the mirror site is out of date is causing the need to wipe so the OTAs work on an unmodified system.
Fortunately I have multiple phones so I can use another for the few hours this all takes.
works great, I just flash it and without wiping data
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
works great and finally my phone can upgrade the OTA updates:laugh::good:
VR25 said:
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
...
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Click to expand...
Click to collapse
Here is time to apply the may OTA MPIS24.241-15.3-21.
I restored the vanilla system.img MPIS24.241-15.3-16 with dd, but it didn't work. The OTA failed with the error "system partition has unexpected content" because the sha1sum was incorrect.
Here is the solution :
Before restoring with dd, you must check "Mount System partition read only" is enable in the MOUNT menu of TWRP.
With TWRP 3.1, you need no more to use dd. Now, the feature "system image backup" is available
OK Please note (4-25-17) this message is a work in progress, as I slowly restore my system.
This is a listing and hopefully helpful listing of what I did (right and wrong)
in upgrading my Systemless-rooted (suuser) phone from 6.01 to 7.00 (nougat)
# 1. it did not work, and I went back to 6.01 successfully using the twrp recovery
I have previously used Bender's guid (here) to get the system-less root on 6.01.
essentailly, here's the best plan. Use the Minimal ADB and Fastboot package (MADB &F) (here)
(Explanation: the MADB&FB package will allow you do do LOTS of stuff related to updating your phone, with very little grief.)
it also includes the ability to automatically "push" a package over your usb connection if the ZIP file doesnt load right. **THIS will come in handy later!
Once MADB&F is installed, make note of your directory, and then make sure you start your dos window (for pc users) as an administrator!
BTW, if I HADN'T made the "TWRP backup" of my system, I'd be Sh*t out of luck right now...", because I screwed up the 7.0 upgrade.
the technical problem was that I had no data, no modem, no way of getting data/voice in/out.
SIMPLY using the TWRP restore fixed me!!!
(so far, we have MADB&FB, downloaded and bender's (chainfire) rootless guide.
Next you want to download the current firmware image for your phone. This will be a lifesaver, I promise!
3) Download a TWRP image (this will MAGICALLY load on your pc when you tell it you need help! Look HERE
(Athene is the Motorola Codename for the motoG4+)
3) copy the athene TWRP image into your madb&FB directory to make it easy to load
4) next, (you still haven't touched your phone yet, you realize: (skipping some basics here, you can search here on XDA to find more info)
a) plug your phone into your pc
b) make sure you are a developer
c) make sure your phone shows you are connected to your pc for file transfers, NOT for charging
5) in your MADB&FB directory, (aka a dos/(admin) window) type the following:
all commands at this point will take place in whatever directory you installed Minimal ADB & Fast boot (MADB&FB)
Connect your phone to your PC and open MADB&FB, check the connection with:
adb devices
return should include your "serial-no" and "device".
6) next, on pc, tell the system to reboot your phone to the bootloader!
Reboot into bootloader with:
adb reboot-bootloader
and check again with:
fastboot devices
7) Next you are going to download TWRP to your phone (not permanently, just for a bit!)
fastboot. flash recovery twrp-3.0.2-0-athene.img
Now you have TWRP (Team Windows RECOVERY PROJECT) loaded.
SO.. THIS is where you create a backup of your current stuff using the backup options.
NEXT:
take the suUser2.78 (stateless rooting), and once your backup is done, install it from TWRP
Then (I was) back to 6.01 rooted.
NEXT: 7.0 and then rooting... (will update tomorrow)
did a successful upgrade to 7.0,
then unsuccessfully tried to sideload supersu2.78, which bricked loader
then downgraded again to 6.01 (and rooted again, ok)
will continue tomorrow.
need working phone for now..
cheers to all, and to all, a happy spelunking!
You can't root factory Nougat as is, it is well encrypted.
You need to replace first the kernel with the ElementalX one, or you will end up with bootloops.
Only after that you can do SuperSU, but only with the latest beta.
A few pointers from your story:
1)As you've found out the hard way, you won't be able to update to Nougat if you have root and/or TWRP, because the update requires a stock system - stock recovery, system and no modifications (bootloader status doesn't matter). In other words, you'll need to unroot and restore your stock recovery - might be easier to reflash the stock system, probably the quickest way to flash a stock ROM (and update to Nougat) is to use the fastboot ROM. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this will remove root and TWRP, as well as potentially wipe your data, so back up accordingly. This should flash the NPJ25.93-14 build on your device, which appears to be the latest global build.
1a)Also, if you flash Nougat this way, your bootloader and GPT partitions will be updated, so if you wish to downgrade to Marshmallow at any point, when flashing do not flash these partitions from the Marshmallow ROM. Fastboot should stop you, but a brick may occur if these get flashed.
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
2) As SoNic67 has already mentioned, the stock kernel security will cause your device to bootloop should you choose to try to root following the Marshmallow method. If you wish to use SuperSU, follow this guide: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You may wish to use a more up to date TWRP than the official 3.0.2 (I recommend shrep's TWRP 3.0.3 n4 here:https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337) Whatever you do, ensure you flash first the ElementalX kernel before you flash the SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133), or apply the systemless fix with earlier SuperSU versions as directed in the aforementioned rooting with SuperSU guide. Else you'll be having bootloops or your device will not boot whatsoever. Here's my steps in successfully rooting Nougat: https://forum.xda-developers.com/showpost.php?p=71817346&postcount=225. Good luck either way.
echo92 said:
A few pointers from your story:
[...]
1b) You may find in the Guides section TWRP backups of Nougat builds, I don't recommend using these to update your system with. Granted, they have most of the Nougat system in a TWRP backup, but some crucial firmware (e.g. the baseband) is not included, and may cause you issues if your device is not formally flashed to Nougat.
[...]
Click to expand...
Click to collapse
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shreps' unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
After updating my US retail xt1644 to nougat, by restoring totally-stock marshmallow then taking the OTA, I wiped data and made a *complete* TWRP backup using @Shrep's unofficial 3.1 TWRP build (https://moto.shreps.fr/Moto G4 (athene)/recovery/twrp-3.1.0-athene_shreps.img).
This version of TWRP allows backup/restore of the full set of firmware partitions including baseband, DSP, etc.
In other words, I believe the TWRP backup folder in the following .zip file provides a one-stop path to the latest xt1644 USRET firmware by doing a restore from TWRP 3.1.0.
https://drive.google.com/file/d/0B4XobQzgZVHyRTlmSDMtYkdZeUU/view?usp=drivesdk
My only uncertainly is if the ota process modified the partition table in a way that might make this backup image incompatible with the xt1644 still in the marshmallow state.
I've often wondered if I (or a more skilled enthusiast) couldn't build a TWRP-flashable .zip that would setup the partition table, update the baseband, etc. This is what I've grown used to from devs on other phones I've had, but perhaps there's something about the way moto does things that makes this problematic.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Nice one, hopefully that'll help more XT 1644 users I'm still not sure if TWRP can backup/flash the baseband by itself, but I don't have a XT 1644 to test. I imagine your backup will need a clean flash (wipe data/cache/Dalvik) to work?
The OTA process does update the partition table, but as far as I know, that should not prevent you from flashing back to Marshmallow/Nougat as you wish, so long as you did not try to downgrade the GPT/bootloader.
There was an effort to create TWRP flashables of the stock ROMs a little while ago (you can see the thread here: https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147) which if I understood it created flashable radios and ROMs from the firmware files we have. We can't touch the GPT/bootloader since, as I recall, you need a signed stock firmware to do so (and besides, downgrading GPT might be asking for a brick). I recall some users mention they were able to run Nougat TWRP flashes on the MM bootloader/GPT without issue.
There were issues with simply flashing the Nougat 93-14 radio baseband files for some US users, losing LTE in the process and appears the only resolution was to flash the stock ROM - I don't know what the cause was (perhaps no/incorrect CDMA support in the radio files?). Your TWRP flash is from a US based phone so may have better luck in that department, and will likely behave on your device since that OTA has updated all the firmware on your device that TWRP isn't able to touch. I still am not sure if we can use this TWRP backup to update on a MM device without issue, but only one way to find out...
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.
My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
bornheim2 said:
My phone (XT1926-3) offered the July 2018 OTA today. I followed the advice at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md and did the following:
- Magisk Manager > Uninstall > Restore Images
- Settings > System > System Update
The phone started to download the OTA (about 300 MB), but afterwards said something like "sorry, that didn't work out".
I then did:
- Magisk Manager > Install > Install
and then phone is fine for now.
I can probably catch the download URL for the OTA by using the logcat method. But what would I do with an OTA zip? The OTA is significantly smaller than a complete firmware (about 2 GB).
Click to expand...
Click to collapse
I'm not sure if that's possible, but I wouldn't try it. The best way is to reflash stock and then accept the OTA. Afterwards, you can reinstall Magisk.
See if the firmware update has been posted here. In either case do a backup with Titanium Backup first. If the complete firmware update has been posted, flash it with fastboot in the bootloader. If it had not been posted, flash the latest version available and then Ota. After your up to date reflash magisk in twrp.
Sent from my moto g(6) plus using Tapatalk
Hi,
At time, is no solution to update with OTA with a rooted MotoG6+ with Magisk.
I'm working on a workaround.
Regards.
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
New OTA update arrived today. Is there already a solution for this? I thought that the new systemless Magisk would "fix" this, but OTA update still fails. No clue why. I even ended up in a bootloop, but switching active partition back to b fixed that...
I don't get why we should be excluded from updates, just because we want to be root on the devices we own. It just doesn't make sense.
This time I tried removing Magisk and restoring boot and system partition (from backup before installing Magisk) before starting the OTA because someone said that when you start the OTA it switches A_B partitions and restoring from backup doen't restore them in the right place and thats why it might fail (or something like that) BUT same result. OTA fails! I guest every month I'll have to flash stock (losing everything on the phone in the process) -> install OTA -> reinstall everything.
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
ivailogeimara said:
You can also use Lenovo Moto Smart Assistant and "Rescue" your device. It basically downloads the firmware and flashes it for you (wiping everything on the device (excluding External SD). That's what I did.
Click to expand...
Click to collapse
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
joris1977 said:
I have XT1926-3 and Lenovo Moto Smart Assistant says that my device is not supported. Do you have the same device?
Click to expand...
Click to collapse
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example:
Code:
fastboot flash boot boot.img
or
Code:
fastboot flash system system.img_sparsechunk.0
tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The annoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
ivailogeimara said:
I used LMSA when I was running OPW113.89 to update to OPW113.89-2 (via the Recovery option). It asked me to select the product and model of the phone. I selected "Moto G Plus (6th Gen)" for the product and for the "Model Name" I had XT1926-2,XT1926-3,XT1926-5,XT1926-6,XT1926-7,XT1926-8,XT1926-9. The new version of the LMSA has 3 buttons at the top of the rescue screen: "Lenovo Phone", "Lenovo Tablet", "MOTO Phone". Make sure that you select "MOTO Phone"
I'll try it again because I just tried to recover system partition backup (made with TWRP) with TWRP and bricked my phone. And for some reason I can't flash the images from the firmware with fastboot. For some of the images that have A and B partitions it tries to flash them to non existent partitions. For example: or tries to flash them to boot__b or boot__a or system__b or system__a (with double '_')
The anoying thing is that I don't have Windows outside VM so every time I need to run LMSA I have to create WINTOGO usb just to run LMSA.
Click to expand...
Click to collapse
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Coldstream said:
Why did you try to update with lenovo assist? Was your rom clean as in no Magisk?
What TWRP did you use, and was your device encrypted?
Need much more info to be able to help, also what is your main OS because you don't need windows for fastboot.
Have you tried booting original boot.img through fastboot?
Maybe changed active slot?
Click to expand...
Click to collapse
Uninstalled Magisk from Magisk manager. Device is encrypted. The TWRP I use is from this thread.
The previous time I used LMSA was because uninstalling Magisk (which flashed boot partition backup) didn't help with installing the OTA (it still failed). And flashing the images from firmware with fastboot gave error. It tried to flash them to boot__a or boot__b, system__a or system__b (with double underscore). I was gonna try updating with LMSA again but decided to try flashing images from the firmware manually with mfastboot this time and it worked. It'll be good if in the guide for "how to return to stock" it said that the included fastboot is mfastboot.
I just flashed the stock images (without data,cache) with mfastboot and I'm trying to update again via OTA.
Update: OTA installed successfully!
PS: Can I check if some partition is modified in some way like OTA does?
ivailogeimara said:
WHY exactly the OTA fails? It shouldn't detect that the partitions are modified because they're not (restored from backup before Magisk).
Click to expand...
Click to collapse
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
joris1977 said:
Yeah I am asking myself the same question. I grabbed a log file and it shows a lot of:
Code:
/system/bin/update_engine: [libfs_mgr]Error finding 'slot' in device tree
I am clueless, but it seems that Magisk somehow disabled the ability for the phone to see slot A. An error that stays even after Magisk is fully removed; I even flashed the untouched boot.img back. But that made no difference.
I also tried sideloading the OTA with ADB on the recovery screen, but that fails too & I see the same error on the screen.
BTW You can grab the OTA with help of this website: http://erfanoabdi.000webhostapp.com/
I am always a bit hesitant in posting log files with a lot of stuff that I don't understand, but as an attachment I add here the lines of the log that contain messages about the update_engine.
Click to expand...
Click to collapse
I think this:
Code:
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1099)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
12-20 13:31:48.480 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1104)] Expected: sha256|hex = 66305C30BC5570791036FFC5B57E620D516B35664C3EE5B27F97FBFD5E288817
12-20 13:31:48.481 1134 1134 E update_engine: [1220/133148:ERROR:delta_performer.cc(1107)] Calculated: sha256|hex = E2D46DB42162711333E99BF1CBD0224F5867F6E7387FA276D30EC54755AF454B
is where the update fails. I'm not sure though what partitions is the OTA checking.
I flashed every partition listed in servicefile.xml (in the stock firmware files that you can flash) and after that I was able to install the OTA. Next I made backups/images (not restorable though) with dd of all the partitions that are listed in servicefile.xml because clearly one or multiple of those get changed after installing Magisk and that's why the OTA fails. After that I installed magisk and made backups with dd again and compared the two to see what changes after installing Magisk. These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check. Probably oem_b.
PS: Well I guess for now the solution will be to flash everything listed in servicefile.xml (except system and system_b) via mfastboot before each OTA.
Thanks for your informative post @ivailogeimara
Lenovo fixed their Lenovo MOTO smart assistance, so now you can reflash your device. with the help of this app. I just reflashed my device and everything is working as expected.
If you use LMSA it downloads a zip file with the full OS where the new OTA is already included. Probably you can cut off the rescue operation after the full zip has arrived and you can just use that zip to flash the boot partition and that oem_b. partition I didn't try that, because I had limited time, had already backed up all my data and I needed a working phone. This is probably what I will try next time an OTA arrives.
Maybe we should make the magister developers aware about the troubles with the Moto G6 plus. It is probably I bug somewhere that uninstalling Magister does not fully restore the old install.
ivailogeimara said:
These are the partitions that were changed after Magisk and are in servicefile.xml:
Code:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
I guess uninstalling Magisk only restores the boot partition and one of the others fails the check.
Click to expand...
Click to collapse
This is exactly what I get on my phone. For the last two OTAs these are the partitions that fail the checksum verification. As you mentioned this is fixed by flashing the partitions from a known good source.
I used TWRP via "mfastboot boot twrp.img" to dump boot.img, modify it via Magisk-Manger and then flash it using mfastboot. I don't see any way how I would modify the other partitions (except boot, of course) this way.
I looked into the oem-partition and it has its "last mounted" timestamp changed to something very, very recent. This is why I rule out TWRP. My best guess is that Magisk mounts those partitions shortly as rw maybe on boot? That would already be enough to make the hash fail
So basically to be able to install the OTA:
1. after clean stock reinstall (before magisk installation) backup the above mentioned partitions
2. install magisk, etc.
3. later when an OTA update comes restore the backed up partitions + remove magisk and then install the OTA
4. back to step 1
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
axsdenied1 said:
I suppose the partitions can also be restored if you find the firmware that is identical to what the phone is currently running.
Or???
Click to expand...
Click to collapse
Yes, that's what I did. Never thought to pull a backup of a partition that would only "ever" be changed by the OTA process I googled a bit for my version number until I found a matching stock ROM.
Moto g6 + rooted with twrp and magisk. I have an OTA update.
The OTA gets errored out right after I download the update and it tries to install it.
Phone version: XT1926-7
Using latest twrp 3.2.3
Magisk v18.0 installed.
Successfully enabled root just the other day.
Now I get the OTA update ppw29.116-11 wanting there pie update to rollout, was so happy. Except it keeps saying unsuccessful right after it's done downloading and tries to install I guess.
Has anyone found a safe workout for this?
It is outlined in the post just before the one you made...
So
before installing Magisk you should have made a backup from the following partitions:
bluetooth_b
boot_b
dsp_b
modem_b
oem_b
when an OTA update comes, remove magisk and restore the backed up partitions.
then install the OTA
make a backup again.
This should work, but I didn't test it yet.