Related
Hello
I am not a hope in TWRP.
And I wonder if TWRP for nougat can install .img file as it is written install image.
Is it possible to install cust.img, product.img, etc .....?
and how?
Thank you
Chisetdel31260 said:
Hello
I am not a hope in TWRP.
And I wonder if TWRP for nougat can install .img file as it is written install image.
Is it possible to install cust.img, product.img, etc .....?
and how?
Thank you
Click to expand...
Click to collapse
i tried to flash stock boot.img by twrp and it doesn't work, my phone stucks at your bootloader is unlocked ...
simo255 said:
i tried to flash stock boot.img by twrp and it doesn't work, my phone stucks at your bootloader is unlocked ...
Click to expand...
Click to collapse
OK,
I wanted to be on.
Because twrp revolution rc3 shows install image boot and recovery.
And twrp 3.1.0.2 shows boot, recovery, cust, misc, oeminfo, system, vendor, product, version.
But nothing goes. I thought I was hurting him. thank you
Chisetdel31260 said:
OK,
I wanted to be on.
Because twrp revolution rc3 shows install image boot and recovery.
And twrp 3.1.0.2 shows boot, recovery, cust, misc, oeminfo, system, vendor, product, version.
But nothing goes. I thought I was hurting him. thank you
Click to expand...
Click to collapse
yes but they aren't working well
simo255 said:
yes but they aren't working well
Click to expand...
Click to collapse
As you see I am still trying to install b380.
What I managed to do is;
Since rom revolution rc4,
Installs root v5.2 because boot is b380.
Adb flash system.img from b380
Reboot.
It is not broken everything works, but it does not write b380.
Chisetdel31260 said:
As you see I am still trying to install b380.
What I managed to do is;
Since rom revolution rc4,
Installs root v5.2 because boot is b380.
Adb flash system.img from b380
Reboot.
It is not broken everything works, but it does not write b380.
Click to expand...
Click to collapse
trying to install b380? first go back to mm, then upgrade to b380
mjz2cool said:
trying to install b380? first go back to mm, then upgrade to b380
Click to expand...
Click to collapse
Yes, I have already tried, since MM, it started but it writes nrd90m, and the parameters do not go anymore. And it lacks significant appl.
Datafull public installs but it is not complete.
And datafull hw eu does not install error 7.
Not serious I will test again tonight to the calm.
And tomorrow huawei will publish LOL
Chisetdel31260 said:
Yes, I have already tried, since MM, it started but it writes nrd90m, and the parameters do not go anymore. And it lacks significant appl.
Datafull public installs but it is not complete.
And datafull hw eu does not install error 7.
Not serious I will test again tonight to the calm.
And tomorrow huawei will publish LOL
Click to expand...
Click to collapse
if you follow the instructions closely and have the correct oeminfo and firmware all should be fine
So, here, what I could find and install nougat.
Firmware full-ota-mf not pv.
For, full ota mf, there are three files.
_ Update.zip.
_file public.zip.
_file datafull.zip.
Uses huawei extractor to unpack update.app of update.zip and file datafull.zip.
You can find and install.
With adb and flash fastboot
_boot.img
_system.img
With twrp edit hassan install image.
_vendor.img
_ Cust.img
_ Version.img.
On nougat the device works correctly.
Now I am looking for a solution to install product.img
Any help or advice, would be welcome.
thank you
Hi all,
I currently have a P9 Lite with VNS-L31C432B371 firmware installed.
Recently, I received the VNS-L31C432B381 update via OTA. Unfortunately, when the phone reboots into recovery mode, the update does not even start; instead, I get redirected to the custom recovery (TWRP 3.1.0.-2, system partition read-only) "homescreen".
Is there a way to update to B381 without wiping the entire phone?
Thank you for your time.
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
SALVO9 said:
The OTA update system uses the EMUI stock recovery so no, there is no way you can update your phone through the updater by using the custom recovery
Click to expand...
Click to collapse
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
_n0153_ said:
Ok, thank you!
Another question: is there a way to obtain the stock EMUI recovery and flash it to execute the update?
Click to expand...
Click to collapse
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
JHD94 said:
Yes.
Download your build's update.zip, extract the zip to desktop, you'll then have an update.app (you probably need the full ~2GB build, not OTA, e.g I use B370);
Extract recovery.img from the update.app via HuaweiUpdateExtractor;
boot to bootloader;
fastboot flash recovery recovery.img.
Done.
Click to expand...
Click to collapse
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
_n0153_ said:
Thank you!
I succeeded in extracting and installing the recovery from the update.zip. Unfortunately the OTA failed anyway.
At this point, I think I should just wipe the phone and install the complete update from here.
Click to expand...
Click to collapse
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
okaar said:
Well I , like you, had a custom recovery. The 3-button method didn't work for me and even after restoring the stock recovery I was unable to install the update.
I unpacked the Update.APP file and flashed through fastboot the BOOT, RECOVERY, VENDOR and SYSTEM .img files and I was succesful but now I have the Model number as generic_a15 and Build number NRD90M test-keys. I can only assume some of the other img files carry the information about my phone. At the moment is stable enough but I can't open the Security menu.
If someone has any idea on how to flash the other img files, please let me know
Click to expand...
Click to collapse
well, if you flash your oeminfo zip, you should get it back
mjz2cool said:
well, if you flash your oeminfo zip, you should get it back
Click to expand...
Click to collapse
I only have old oeminfo.img packages, do you know how I can build one? There is a PRODUCT.img but it is considerably bigger than the oeminfo package that I have seen.
I flashed all the old B370 files, update.zip and update...hw_eu.zip, with DC Phoneix (a non free tool but saved me from.a bricked phone). After that, I flashed the new package and got the Security settings and Developer Options to work again.
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.
Hi all
So it was all running nice and stable, before the evil b25 update that destroyed my axon 7 completely and made it useless, I'll tell how
so after updating I figured out I can't access fastboot to flash anything, and I figured out I wasn't the only one with this "meme" that zte made.
so I decided to roll back to b19 using Miflash and b19 edl package, I thought my problem would end here.
Then I flashed twrp via fastboot, and upgraded to b25 using b25 bootstack + b25 zip by drakenfx, all good.
then I tried to root b25 the good ol' way by flashing supersu zip, only to find that I'd end up with this newer meme, "unable to find su binary"
seems like the sort of thing you'd get if you had a locked bootloader, which is suspicious, judging that no one was able to get fastboot on b25
I also figured out I wans't the only one as people from "root b25" threads know that you can't root b25 even if you had twrp
so I rolled back again to b19 using miflash....you know the story
now here comes the interesting part, the meme, didn't go away, I tried to root my b19 a2017u by flashing supersu
I tried everything, flashing b19 bootstack, formatting data flashing different supersu versions etc.
, either ended up with a bootloop, or the famous "su binary is not installed"
I never had this before updating to b25 and now I can't get rid of it even without b25
can someone guide me to root stock b19 properly and get rid of this meme? (bonus if you know how to root b25 properly because I liked b25 more, there is a7x kernel for b25 so I guess we can root b25? maybe not? )
note that I don't want magisk, I just want the good ol' supersu, nothing more nothing less.
My opinion is the new b25 somehow messes the bootloader and now it's locked again, but this time you can't unlock it even if you downgrade and flash edl bootloader unlock via miflash.
guys, I think zte is just trolling us atm, you would not believe how much time I wasted flashing, I think my axon 7's nand is going to die soon.
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
Holding power and both volume keys at the same time for ~15 seconds (until the LED flashes) restarts EDL without actually having to get out y'kno.
Just saying
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
buksua said:
First of all is your bootloader unlocked? if so than try this out.
1. go into EDL and flash B19-NOUGAT_FULL, after that don't reboot yet put it in EDL mode again and yes you have to put in EDL again
2. now in EDL flash B19-NOUGAT_TWRP, once you done flashing it just boot into TWRP
3. in TWRP click on mount and make sure that MOUNT SYSTEM PARTITION READ-ONLY is check
4. now flash A2017UV1.1.0B25_bootstack_by_DrakenFX.zip
5. flash A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip DO NOT REBOOT
6. flash superSU 2.79
Click to expand...
Click to collapse
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
J0nhy said:
I had exact same problem you having right now bro, what i did was miflash to b19, then system update to b25, after all that i rooted my phone with this
https://mega.nz/#!AMw1mKyK!RWXjynVEGle4JGoSpvJoq5cOCI3q3EPlTCXM48Mn4F8
Hope this works for you man, good luck
Click to expand...
Click to collapse
UPDATE ON THE SITUATION:
It didn't... *sigh*
but...it worths to mention 1 thing I noticed after booting (regardless of supersu version flashed)
That su permissions get granted, but for a limited periods/times only, and then I get the "root undetected/su binary not found" error afterwords.
which was suspicious, so I ran "su" command in terminal emulator with the supersu you provided and this is what I got
ailsa_ii:/ $ su
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e054ffff68 arg 0xaa1403e2d2800081
Basically a bunch of warnings like the one above, like a dozen of this line ending up with this specific note:
CANNOT LINK EXECUTABLE "sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Im losing hope, but at the same time I think I found a thread, only need a dev to help me currently
I'll post this in supersu thread and see, maybe I get a helpful reply
I will also try changing to ext4 because I'm heavily doubting that the reason for all this is my use of f2fs on data partition only.
Ghostface009 said:
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
buksua said:
just like I said on the instruction you MUST check the mount system partition read-only before you flash
A2017UV1.1.0B25_bootstack_by_DrakenFX and A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip
If you when to keep TWRP after flashing Stock System, install SuperSU v.279
(reference)
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
maybe you didn't check the mount system partition read-only before you flash b25 was the problem in the first place.
If you can get your bootloader unlock again just try the method I've mention.
just read the instruction carefully step by step.
(note)
I've been going back and forth flashing different roms but ultimately I always have to come back to stock using the method I've mention. I have never use magisk unless it come with the rom.
I've always flash SuperSU after installing A2017UV1.1.0B25_StockSystem_by_DrakenFX.zip with no problem.
Click to expand...
Click to collapse
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
Ghostface009 said:
I can't 100% confirm that I tried this before, but I assure you I
tried most of possibilities like this, including step by step follow up of drakenfx's guide.
I may try later, but not now, that takes a lot of time and my a2017u's nand is dying of repeated flash :crying:
but lemme ask you, can/could you access fastboot on b25 stock??
Click to expand...
Click to collapse
no fastboot on b25 but fastboot on b19
remember to flash B19-NOUGAT_FULL (Nougat 7.1.1) first than VERY IMPORTANT part is to flash B19-NOUGAT_TWRP (Nougat 7.1.1) right after.
just do step 1 and 2.
don't flash b25 yet if you want fastboot
if you want b25 and b25 root just follow step 3
buksua said:
no fastboot on b25
Click to expand...
Click to collapse
Yeah, not a big surprise
and I'll try everything later when I get enough time, but for now I look for a firmware flash-free method because I don't want to kill the ufs.
UPDATE FOR EVERYONE:
I FINALLY GOT SUPERSU WORKING (atleast this far)
sadly f2fs was the reason behind this error
Special thanks for @J0nhy
for providing the correct supersu version to flash :3
Ghostface009 said:
Are you sure this would work?? can you confirm by reading my post again?? I just can't believe the whole solution to this would be this simple plus I don't like to have another brick to waste my mind on, Im currently busy with the 2nd term in college :crying: please confirm this asap by re-reading the 1st post.
(100% will try anyways because I have everything backed up )
I clearly mentioned that I tried all this, to be more clear I tried the whole drakenfx method with all possibilities including the method you mentioned, and yes my bootloader was unlocked before all this.
Just for clarification as your post may misguide some people, because you don't mount read only when doing this, because if you do you can't use your system partition at all, you only mount read only after flashing twrp for the first time or when you don't want to flash supersu/no verity (something no one wants to do)
I appreciate your help anyways.
Click to expand...
Click to collapse
The file is no longer available through this link... is there another source?
zachstarmer said:
The file is no longer available through this link... is there another source?
Click to expand...
Click to collapse
wew, It's been a long time since my last login here.
afaik it was 2.79 su.
But why you're still on b25 when you can flash newer firmware? when I flashed b32 via edl, I got rid of all these probs (except f2fs, because zte decided that their stock firmware only supports ext4 )
I got fastboot and everything, root xposed etc, if you want the edl package you can search it in drakenfx's androidfilehost account :good:
make sure to backup internal storage manually and backup apps with TB for restoring after edl-flashing b32. I also suggest updating to b35 before rooting and restore since b32 was helluva buggy update
This is exactly why I won't run ZTE's stock ROM, it seems that only Magisk works on B32 and beyond. I have grown to hate Magisk over the years, due to a number of bad experiences with it on various ROMs/devices. On stock, Magisk makes my exFAT SD appear as corrupt, I refuse to format to vfat, fat32. I tried Phh's Superuser and SuperSU, either the device won't boot or I get errors about su not being available. So it's custom AOSP-based ROMs only for me. Which are far superior to stock in most ways.
TL;DR
About two years back I upgraded from Marshmallow to Nougat then downgraded back to Marshmallow but didn't flash GPT or bootloader partitions (full details at the bottom)
I want to upgrade to the latest official stock firmware which I believe is this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-g4-oreo-soak-test-update-t3871136
But I don't know where to begin.
If I backup my phone with TWRP can I restore back to it (Marhsmallow) if I decide I don't like Oreo?
Appreciate any help
History:
A while back I upgraded from Marshmallow to Nougat using this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I then Flashed the June (2017) OTA update files
Xposed framework wasn't available for Nougat at the time so I downgraded back to Marshmallow; I believe I used the file XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
I THINK I followed this downgrade guide: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
But I vaguely remember not flashing the GPT and bootloader partitions (based on the advice of the wonderful echo92 here: https://forum.xda-developers.com/showpost.php?p=73031946&postcount=8) but I can't say for sure
I have a few backups from TWRP (https://imgur.com/a/QzgQNbh) from that time with this file structure: https://i.imgur.com/B2cxQvL.png
I blurred out the 10-character 0KB file - it seems unique but I can't remember what it's for
If you're wanting to downgrade back to Marshmallow at some point in the future, I would recommend you flash the TWRP flashable of OPJ28.111-22 https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 This TWRP flashable should update your device mostly to Oreo, but not update your GPT/bootloader partitions (your GPT/bootloader would stay on the same version as you are now). Also, you should be able to roll back using your TWRP backup (though I do not know if you'll have issues with the Oreo modem on your Marshmallow device, so you might want to find the modem/fsg files too for Marshmallow)
We found out subsequently that downgrading firmware does not downgrade your GPT/bootloader (fastboot will complain of security downgrade errors otherwise). This poses a big problem when downgrading and using old OTA updates - old OTA updates corrupt your newer bootloader and hard brick your device. By not updating your GPT/bootloader further, you reduce the number of updates that can damage your device, but again, if you roll back to Marshmallow from your TWRP back up, make sure you do not use OTA updates at all.
you might want to find the modem/fsg files too for Marshmallow
Click to expand...
Click to collapse
Not entirely sure what this means or how I do that.
I have XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which contains NON-HLOS.bin and fsg.mbn which I believe are the modem/baseband firmware. I don't really know what to do with them though.
Since I can flash the firmware (zip) directly on the device (and the lack of a recovery.img in the zip) I assume that TWRP stays intact and remains the default recovery?
So, as I understand it, my steps are simply:
Flash TWRP-athene-8.1.0-OPJ28.111-22.zip in TWRP
Flash Magisk stable in TWRP
We found out subsequently that downgrading firmware does not downgrade your GPT/bootloader (fastboot will complain of security downgrade errors otherwise). This poses a big problem when downgrading and using old OTA updates - old OTA updates corrupt your newer bootloader and hard brick your device. By not updating your GPT/bootloader further, you reduce the number of updates that can damage your device, but again, if you roll back to Marshmallow from your TWRP back up, make sure you do not use OTA updates at all.
Click to expand...
Click to collapse
The first part lost me a bit. Are you just saying, "Do not use OTA updates."?
Oh, and thank you very much for the help
tekwarfare said:
Not entirely sure what this means or how I do that.
I have XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which contains NON-HLOS.bin and fsg.mbn which I believe are the modem/baseband firmware. I don't really know what to do with them though.
Since I can flash the firmware (zip) directly on the device (and the lack of a recovery.img in the zip) I assume that TWRP stays intact and remains the default recovery?
So, as I understand it, my steps are simply:
Flash TWRP-athene-8.1.0-OPJ28.111-22.zip in TWRP
Flash Magisk stable in TWRP
The first part lost me a bit. Are you just saying, "Do not use OTA updates."?
Oh, and thank you very much for the help
Click to expand...
Click to collapse
1) Pretty much - keep the non-HLOS.bin, and FSG images from your fastboot zip handy. The TWRP flashable of the Oreo firmware contains the modem updates, whilst your TWRP backup likely does not have the modem partition. Thus, if you do downgrade and you get signal issues (don't know of anyone who downgraded from Oreo to Marshmallow, you'd be one of the first) you might have to flash the non-HLOS.bin and FSG via fastboot to downgrade your modem back to Marshmallow. The fastboot commands would be:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Failing that, you could flash this 64 bit TWRP and back up your EFS from both your Marshmallow and Oreo firmwares: https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Then if you do have signal issues, you could try to restore your EFS. Or check out this guide if you have IMEI issues: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
2)With the TWRP flashable - yes, your TWRP should stay intact and those steps sound good. Backup your existing installation beforehand.
3)If you downgrade your device stock Motorola firmware, do not use OTA updates. Else, you may hard brick your device.
Failing that, you could flash this 64 bit TWRP and back up your EFS from both your Marshmallow and Oreo firmwares: https://forum.xda-developers.com/mot...oject-t3842903
Click to expand...
Click to collapse
I've got TWRP 3.1.1-0, that looks like it has new features including the ability to do EFS backups now so I'm fine to overwrite my existing Recovery with the one you linked?
I see there's apps that can do EFS backups too. Why TWRP over them?
Thank you very much for your help with this
tekwarfare said:
I've got TWRP 3.1.1-0, that looks like it has new features including the ability to do EFS backups now so I'm fine to overwrite my existing Recovery with the one you linked?
I see there's apps that can do EFS backups too. Why TWRP over them?
Thank you very much for your help with this
Click to expand...
Click to collapse
Should be okay to overwrite your existing TWRP with the 64 bit version - you can either install in TWRP or flash TWRP via fastboot.
Alternatively, if you want to keep TWRP 3.1.1, then you can boot the 64 bit TWRP from fastboot (using the fastboot command 'fastboot boot <name of TWRP>', without quotes and where <name of TWRP> is the full file name of the 64 bit TWRP, without the arrows), then back up your EFS with the 64 bit TWRP. When you next reboot, you should still have your TWRP 3.1.1.
Not used those apps, so I can't comment, be up to you which approach to use. I've seen members use this TWRP for EFS backup without issue.
Do I need to wipe before flashing this?
Notes for myself in the future:
Updated my phones recovery partition to TWRP 3.2.3-0:
Installed MotorolaDeviceManager_2.5.4.exe
Copied recovery.img to the same directory as fastboot.exe and ran the line:
fastboot flash recovery recovery.img
I did a factory reset in TWRP
Downloaded and copied the zip across a few times but I'm just getting "zip signature verification failed".
tekwarfare said:
I did a factory reset in TWRP
Downloaded and copied the zip across a few times but I'm just getting "zip signature verification failed".
Click to expand...
Click to collapse
Hmm, which TWRP zip did you download? You could always go into TWRP settings and turn off signature verification.
Not sure if you needed to do a factory reset, though always useful when updating (hope you had a backup).
TWRP-athene-8.1.0-OPJ28.111-22.zip like you said. It's the one where AFH is crossed out but GDrive is up
Edit: I disabled zip signature verification (even though I didn't want to) and installed it. Setting things up so will see what works and what doesn't.
Thank you very much for the help
tekwarfare said:
TWRP-athene-8.1.0-OPJ28.111-22.zip like you said. It's the one where AFH is crossed out but GDrive is up
Click to expand...
Click to collapse
That's the right zip - I'd double check the download went okay, though under TWRP settings there should be an option to turn off zip verification. After that, the zip should flash okay.
Installing magisk via TWRP aslo failed the zip signature verification (just disabled the verification to install things from now on)
Managed to get a few things up and running like ViperFX.
Xposed is constantly causing bootloops (soft brick) and I can't seem to fix it. I managed to get EdXposed working with Sand Hook but it slows the system down noticeably; all I want is gravitybox.