Bootstack or boot.img? - ZTE Axon 7 Questions & Answers

Hey guys, i'm new on this forum, i got this device 2 days ago and i already unlocked bootloader and flashed twrp. What is the difference between bootstack and boot.img? I'm trying to flash stock boot.img (ot bootstack) to change SuperSU for Magisk.
I have A2017G model with Nougat B09 update December Security Patch.
Edit: I flashed Magisk successfully with stock boot.img, btw what is bootstack?

SkaboXD said:
Hey guys, i'm new on this forum, i got this device 2 days ago and i already unlocked bootloader and flashed twrp. What is the difference between bootstack and boot.img? I'm trying to flash stock boot.img (ot bootstack) to change SuperSU for Magisk.
I have A2017G model with Nougat B09 update December Security Patch.
Edit: I flashed Magisk successfully with stock boot.img, btw what is bootstack?
Click to expand...
Click to collapse
Bootstack and boot.img are completely unrelated things; while the boot.img is basically the kernel, the bootstack is usually a modem file bundled with the bootloader (what makes your phone initialize)

Related

Use Magisk with Nougat

Hey everyone.
I try to install magisk on a European moto g4 (nougat, unlocked bootloader, stock). When I flashed magisk, the phone doesn't start. I can only boot into Fastboot. When I flash the stock boot.img there, the phone starts as normal. How can I flash magisk? Thanks in advance.
Magisk With Nougat
Using Custom ROM or Stock?? Resurrection Remix 5.8.2-20170414 offers magisk in itself.. U must try it out!
If you are in stock, install the ElementalX kernel
einhuman197 said:
Hey everyone.
I try to install magisk on a European moto g4 (nougat, unlocked bootloader, stock). When I flashed magisk, the phone doesn't start. I can only boot into Fastboot. When I flash the stock boot.img there, the phone starts as normal. How can I flash magisk? Thanks in advance.
Click to expand...
Click to collapse
You can't install magisk over the stock kernel. You have to flash TWRP first. I recommend twrp 3.1... by oadam11 You'll find it here https://forum.xda-developers.com/mo...7-1-1-ground-zero-roms-validus-tesla-t3553036 in the 2. post of the first page.
After that, you can install elementalx-kernel.
Then you're ready to install magisk.
It worked, thanks for the help everyone.

Root and update firmware from 6.0.1

I rooted the phone (XT1642) using this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
I'm on 6.0.1 and have been getting the install system update prompt (NPJ25.93-14) every time I turn WiFi on.
Can I just install this or will it remove the rooting I did?
If it removes the root, how do I update to the latest firmware safely and root it?
Alternatively, how do I get rid of the prompt each time I turn WiFi on?
Can I take an image of my phone as it is and revert back to it at any time, and if so, how?
I really don't know what I'm doing and help would be appreciated.
If you're looking to update to NPJ25.93-14 via OTA, you'll need to unroot and flash a stock recovery (and stock logo.bin if you hid your bootloader warning), else the OTA will not install. Of course, this will remove root and TWRP until you've updated. Also, bear in mind after the update there's 2 more security patches (March and June 2017)
Before attempting anything though, ensure you've got a backup of your data (including a TWRP backup of your device as it is) and move them off your device until you're completed.
If you don't have access to a stock recovery/logo.bin, you could use a stock fastboot ROM to bring you up to date - this will remove root and TWRP however. The latest fastboot ROM we have is the March 2017 build: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
If you wish to update with the fastboot ROM (so bringing you up to the March 2017 build), you may wish to use the following fastboot commands, which will replace your recovery and remove root, but should not affect your data (however as with anything that affects your system, ensure you have backups regardless)
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
This fastboot ROM will formally update your device completely to NPJS25.93-14-4 (March 2017), but using these commands you will not have locked your bootloader. You may wish to wait for the June security patch (since OTA updates require a stock recovery, stock kernel and stock system) or proceed to rooting.
If you wish to root on Nougat, follow either: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 or https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270 Please ensure that you flash a custom kernel before rooting on stock - Motorola - Nougat on Moto G4/Plus devices.
If you do not wish to fastboot a stock ROM, you could flash a TWRP flashable of the March build. This will not update your bootloader, or GPT partitions (so will not completely update your device to the March build), but is a nice shortcut. Again, this will remove root (but not TWRP) and so you will have to re-root as for Nougat. https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 for the TWRP flashable. This will also require you to flash the modem TWRP flashable file (included in the thread) as your fingerprint sensor may not work properly otherwise.
If you don't wish to update, and just want to disable the notification, have a look here: https://forum.xda-developers.com/mo...ble-notification-update-t3459587/post73005893
Thank you very much for the detailed answer. I have tried my best to understand the scene as best I can, but remain unfamiliar with the various approaches.
I have made a backup of my SD Card and used TWRP to create a backup of partitions: System (1983MB), Data (3459MB) and Boot (16MB) and transferred them to my PC
I am able to restore to my old 6.01 configuration with this backup I made provided I have an unlocked bootloader right?
To follow the guide you linked for rooting Android 7.0: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Am I correct in saying I would need to unroot my 6.0.1, re-lock the bootloader and then update to the latest firmware via OTA updates? You say to "flash a custom kernel before rooting" but I don't know what this means or how I would do it.
Alternatively, I see the June security patch came out today. Would this be an easier or better way to update than the above method?
I don't know if you'll be able to revert back to your old 6.0.1 TWRP backup once you've updated to Nougat, as the modem and other firmware would be newer than 6.0.1. Additionally, if you've updated to the June update, be very careful about downgrading by flashing a stock ROM as the bootloader has been updated in this update, and attempts to downgrade the bootloader and GPT seem to result in bricking of devices (though TWRP flashes do not care about the bootloader and GPT usually, so you may be okay in that regard).
As for the procedure for updating, you do not have to re-lock your bootloader if you desire root later. Bootloader lock status does not appear to affect OTA updates/installations - only the presence of a non-stock recovery, system or kernel will cause the update to abort. Re-locking for your purpose, unless you're wanting to send your device for service or to sell it, is unnecessary so leave it unlocked. The unlocking instructions in the guide are only there if you're coming from a device with a locked bootloader. If you're going down the OTA route, a general guide would be:
1)Unroot your root manager (following the root manager's uninstall instructions).
2)Flash a stock recovery (and stock kernel) from a stock ROM. Ensure the stock ROM you're using is the same build as what you're currently on. If you've flashed a custom logo.bin to hide the bootloader warning, you'll need a stock logo.bin.
3)Download and flash the OTA update in your stock recovery (should happen automatically).
4)Reboot into Nougat NPJ25.93-14.
5)Accept and download the March update, repeat the install.
6)Accept the June update if it's arrived for you (I've only seen the June update deployed in Brazil and India at the moment, other territories may have to wait), or download and flash the OTA update in stock recovery. The June security patch appears to only flash over the March update.
7)Once you're updated, flash TWRP and back up your entire system again (you may wish to flash a newer TWRP).
8)Flash ElementalX and your root manager as directed in the guides. Ensure the root manager you flash is quite recent - either SuperSU 2.79 SR3 or newer (2.82 SR1 is the latest) or magisk v12 or newer should be okay.
NOTE - you could skip steps 1-5 if you use fastboot and the commands in my previous post with the March 2017 fastboot ROM. You'll be flashing stock copies of the partitions to your device and bring it up to the March 2017 update in one go.
With 6.0.1, you could root after you flashed TWRP - on stock Nougat, the anti-rooting security is much stricter, and attempts to root with the stock (i.e. Motorola, hudsoncm) kernel may cause your device to bootloop. Thus, to get around those security measures, we can flash a custom kernel (i.e. a 3rd party kernel) that doesn't have that security. We have ElementalX v1.04 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 and vegito v6.08 https://forum.xda-developers.com/mo...ernel-vegito-kernel-1-0-13-september-t3461021 as custom kernels. To flash a custom kernel:
Download the stock version of the kernel (the LineageOS versions are for Lineage-based custom ROMs).
Reboot to TWRP.
Backup your boot partition (this contains your stock kernel)
Go back to 'Install' and tap the kernel zip
Follow the installer instructions to flash (e.g. with ElementalX, I've got stock 1561 MHz, no double tap to wake and none of the options selected on the installer screens).
Wipe cache/Dalvik
Reboot.
After flashing the custom kernel, then you can proceed to rooting on a Moto G4/Plus.
Here's what I ended up doing:
Updated using the March 2017 fastboot ROM and the instructions you provided.
Flashed the June OTA update files
Flashed the latest TWRP (3.1.1.0) over the stock recovery mode
Flashed ElementalX
Flashed Magisk 13.2
So I now have root access and my apps are still there. Unfortunately trying to install any modules in Magisk via the download section result in a "... has stopped working" message. I flashed the uninstaller and installed 13.1 but still no dice. The benefits of Magisk sounded great but I might just install SuperSU tomorrow instead.
I really appreciated your help, thank you very much
tekwarfare said:
Here's what I ended up doing:
Updated using the March 2017 fastboot ROM and the instructions you provided.
Flashed the June OTA update files
Flashed the latest TWRP (3.1.1.0) over the stock recovery mode
Flashed ElementalX
Flashed Magisk 13.2
So I now have root access and my apps are still there. Unfortunately trying to install any modules in Magisk via the download section result in a "... has stopped working" message. I flashed the uninstaller and installed 13.1 but still no dice. The benefits of Magisk sounded great but I might just install SuperSU tomorrow instead.
I really appreciated your help, thank you very much
Click to expand...
Click to collapse
No worries - if you're looking to switch to SuperSU, you'll need to uninstall magisk, then flash your clean stock kernel from your Nougat TWRP backup (flashing just the boot partition from the TWRP backup you made before flashing ElementalX should be okay). Then, you'll have unrooted and have a clean stock kernel - then flash ElementalX and SuperSU.
You'll need a clean stock kernel to remove traces of the previous root - you may have issues with SuperSU otherwise.
I think it was a problem with the way the zip files Magisk downloads are packaged, I can get them to install if I repackage the zip file.
Unfortunately, I never realised the xposed framework isn't supported on Nougat yet. I had a lot of quality of life tweaks that are greatly missed. Do you know if it's possible to safely downgrade back to Marshmallow at all?
I found this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
But comments mention about future OTA updates maybe bricking the phone and "When come back from nougat to marshmallow don't flash gpt and bootloader , and flash everything else.".
Yeah, it might be that the modules haven't been updated for the latest magisk v13.2 yet.
Honestly, I do not know if it's safe to downgrade - with the June update, a critical security vulnerability was patch, and from what I've observed, attempts to downgrade have resulted in bricks. From what I understand, this seemed to result from users downgrading their GPT and bootloaders. You may be able to downgrade from Nougat to MM if you omit flashing the GPT and bootloader partitions (as mentioned in the guide you found), but there'll be a mismatch between your bootloader (Nougat) and your system (Marshmallow). Thus, for that reason, I'd suggest to not accept OTAs whatsoever. Again, I do not know if this is safe since the June update and I do not want to suggest things that might damage or ruin your device - it's your device, however.

Few questions about lg v20 H910 with magisk and rom

Hi people, two days ago i've rooted my lg v20 H910 and after few problems with the modem partition i resolved it. Now i have the superv20 1.1 rom and mk2000 1.5 kernel. I want install magisk 16 instaed of supersu but i can't flash it. During the flash it says that is impossible to flash why the the boot image is already patched. I tried also to flash arise viper4android but it didn't work...
How can i risolve it?
My phone is unlocked and i'm in 10t
If my memory serves me correctly in order to flash magisk you have to be on a stock boot image, as far as arise check their thread for support, good luck.
You need to uninstall SuperSU, and flash an unmodified mk2000 kernel. Then you can flash Magisk
-- Brian

Oreo rooting method?

On one of my Moto G5 Plus phones, I had rooted it prior, so couldn't install OTA updates, but I found some twrp flashable packages to get to NPNS25.137-93-14 on retus, and then I installed a twrp flashable oreo (both found here on XDA), but in the process, since it flashed new system partition and all, I lost root. Is there a working method to root on Oreo? Preferably without having to lose data since my bootloader is still unlocked and I have TWRP installed.
Can't you just flash Magisk?
Nothing about rooting deletes your data, unlocking the bootloader does that...
MineMasterHD said:
On one of my Moto G5 Plus phones, I had rooted it prior, so couldn't install OTA updates, but I found some twrp flashable packages to get to NPNS25.137-93-14 on retus, and then I installed a twrp flashable oreo (both found here on XDA), but in the process, since it flashed new system partition and all, I lost root. Is there a working method to root on Oreo? Preferably without having to lose data since my bootloader is still unlocked and I have TWRP installed.
Click to expand...
Click to collapse
Just flash latest magisk.zip through TWRP as usual. If the Magisk Manager isn't installed after that download and install the latest one from Magisk thread.
Sent from my Moto G5 Plus using XDA Labs

Struggling with Oneplus 5

So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
That's exactly how to do it. Use an Oreo era Codeworkx TWRP to flash a full OOS ROM. You have to have used 5.1.4 to create the Vendor partition so flash that. Let it overwrite TWRP with the stock recovery, and then OTA up to latest OOS. Fastboot flash latest Codeworkx TWRP and you're done.
Uninstall Magisk before you begin.
strongst said:
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
Click to expand...
Click to collapse
Exactly this was my plan. Thanks for the help. I struggled with this for literally months!

Categories

Resources