Few questions before rooting/twrp - Essential Phone Questions & Answers

I just purchased the ph1 and plan on rooting the device and also flashing twrp. I've found the guides and everything seems pretty straight forward. The phone should be arriving tomorrow so at this point I'm unsure of the build it will have when I receive the device. I noticed a thread regarding the February update not working with twrp. Has this issue been resolved or will I need to flash to the January version to complete the task? Is the February and January builds mentioned the most recent updates for the device? I've found the links to the essential website but it gives me a error that its server IP cannot be found so I've been unable to check it. Is the site going to be down indefinitely due to no longer supporting the device? Does anyone have a link to the updates hosted elsewhere? The device was listed as GSM unlocked and did not mention any carrier tied to it so I'm assuming it's a factory unlocked device but will have to verify upon receiving it. Is the updates carrier dependant or do they all utilize the same files? Whats the consensus on roms/kernals on this device as opposed to rooting and using twrp on the most recent stock builds? Which Rom would you recommend if I do decide to go that route? Thanks for any advice you can offer, it's greatly appreciated.

Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?

SirDigitalKnight said:
Count me in as needing to know this information. I am planning on installing the Android 11 release when it comes out this month and I am currently running 10 Build number QQ1A.200105.032 with February 5 2020 security patch level. Will I need to install the January build to install Android 11?
Click to expand...
Click to collapse
I ended up receiving the device and it had Android 8 out of the box. I received a update that took me to Android 9 which was roughly 1100mb and another to Android 10 which was a little over 1000mb. The second update automatically included the February security patch. Rather than downgrade to January, I simply patched a February boot image with magisk and flashed with fastboot. I also flashed ElementalX kernel via fastboot. As far as I can tell they are not carrier specific. I am considering going to January now so I can use twrp to test some custom roms. For downgrading to January do I simply flash the January boot image which shows to be about 65mb or do I need to find the firmware in it's entirety? Also rather than down grade and use twrp can I just flash custom roms via fastboot? I would say you might have to downgrade to January to use twrp to flash Android 11 unless it's possible to flash the roms on fastboot, hopefully someone chimes in bc I'm unsure at this point.

Noob question, but what's the advantage to changing just the kernel?

Coming back to XDA after over a year. Realized Google Play Store update ruined my Magisk status, and evetually root (SafetyNet stuff). Here are some notes I took while I flashed in 2019, hope it helps.
1. DISABLE Security (PIN/Pattern/Fingerprint)
2. Backup Internal Storage
3. Boot to recovery TWRP, and backup nandroid.
(must go to bootloader and change slot to boot twrp.img flashed on that boot partition slot)
4. Normal boot and drag drop nandroid backup to PC.
5. Syncthing/Resilio for extra measure.
Have latest OTA.zip, boot.img (same version as OTA.zip), and latest Magisk.zip in root internal phone storage.
Have twrp.img in platform-tools adb root for flashing in fastboot.
twrp.zip is optional stored in root internal phone storage.
Flash OTA.zip update in TWRP. (assuming system is under slot_b)
This will flash to opposite slot, _a.
(I flashed under slot_b and new OTA went to slot_a, I booted back to _b and
old system version remained with broken Wifi becasue I accidentally flashed new boot.img in TWRP image over older system image
in slot_b, without the image flash, I suspect the old slot_b would have been perfectly untouched and rooted, as OTA applied to slot_a)
(Went back to A and new OTA was perfectly fine, although unrooted).
Boot to slot_a (system_a), make sure it runs good and verify version within settings, should be unrooted.
Boot to bootloader (under same OTA slot_a), default recovery should be stock recovery (droid logo) after OTA flash.
fastboot flash boot twrp.img (this will replace stock recovery to twrp recovery, deleting stock boot img as well, breaking OTA slot)
Reboot to recovery twrp (remain on same slot and will run off of RAM, leaving boot partition open to flash back stock boot.img)
Install boot.img (make sure version is correct) boot partition should be back to working condition although unrooted OTA system.
Try booting back to recovery on same slot, and stock droid recovery is back. (you cannot edit partitions from fastboot, hence twrp flip flop)
Try booting to system, it will boot but broken, no wifi. How? Not sure, maybe used old boot partition .img in slot_b to boot to system_a
Then flash latest magisk zip to patch stock boot.img for root.
(if you flashed twrp.img and magisk, then you're patching twrp, which is incorrect.
You want to boot to twrp, then flash boot.img back to boot_a partition, then run magisk.zip to patch stock boot.img in that boot_a partition)
Magisk.zip flash log:
Current boot slot: _a
Mounting system
Mounting vendor
Device is system-as-root
System-as-root, keep dm/avb-verity
Encrypted data, keep forceencrypt
Target image: /dev/block/sde11
Device platform: arm64
Constructing environment
Boot image is signed with AVB 1.0
Unpacking boot image
Checking ramdisk status
Stock boot image detected
Backing up stock boot image
Patching ramdisk
Repacking boot image
Flashing new boot image
Sign image with test keys
Unmounting partitions
Done
Updating partition details...
...done
Wipe cache/dalvik
In TWRP, tap reboot button and switch slot_a to other slot_b (older system version).
Reboot to bootloader_b in TWRP.
Flash twrp.img in that other old slot_b (For backup purposes and to have twrp at hand because boot_a has patched rooted boot.img and not twrp anymore)
Done!
Click to expand...
Click to collapse

Related

Flashing stock images problem.

I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
If you jst flash recovery via fastboot then flash latest supersu and you'll be good. 2.67. When twrp asks to root select no and reboot and you will be good or you could use a custom kernel and su or I came across this
http://forum.xda-developers.com/showthread.php?t=3306684 I think it's what your looking for.
Edit
DoUknoGREG said:
I was systemless-rooted, with xposed installed on 6.0.1 with the December security patch.
I went ahead and tried to flash the February Security patch through Fastboot (Followed the steps in order to not get my data wiped)
Tried to boot, and was told encryption failed, so I basically had to wipe my phone completely.
Now I have a problem. Since I am on the latest build number (mmb29q) I don't know which custom boot image it is that I have to use in order to flash a custom recovery and root my phone again.
Click to expand...
Click to collapse
I'm not sure what the problem is here, you don't need a custom boot.img to install TWRP, just flash it. You don't need a custom boot.img for root either, systemless SuperSU patches the boot.img for you. It's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

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.

Issue with Magisk and OTA version 7.1.2

I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
I didn't get a reply here. Mod, please delete this post. I will add it at Magisk thread.
Oh, wow. I have also installed magisk in the way you have. I hope it hasn't messed with your system. However I'm fully updated so have no way of trying your method of OTA.
Please update me if you do solve your issue incase I also have similar difficulties.
It is no major issue, it is just a pain in the butt to have to flash the fastboot rom to update... It take 15 minutes and a PC if you can't get OTA...
I'm just lazy.
ludditefornow said:
I am having issues getting an OTA with Magisk 15.2 installed. MAgisk Manager is 5.5.3.
1. I did a flash of fastboot rom for the first december update of 7.1.2 without overwriting storage.
2. I unlocked the bootloader
3. I booted (did not flash) to 3.1.1 of TWRP and loaded Magisk 15.2. Everything worked fine.
4. I followed this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips and went Magisk Manager → Uninstall → Restore Stock Boot. I received a confirmation that the stock boot was restored. However, at this point, my google camera still works. This seems illogical if the stock boot is replaced.
5. When I download the second december OTA update I get a failure to install error at step 2 of 2.
Has anyone had similar issues or have solution? If I post to the Magisk threads, what logs will they require and how specifically must I create the logs and where will they be stored?
Click to expand...
Click to collapse
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot).
5. failed update could be due to tampered system partition (it is enough to mount it as RW in TWRP). Reflash fastboot images without data erase and do not modify system in any way afterwards.
_mysiak_ said:
4. restore boot image function will reflash stock boot.img to boot partition, but until reboot you are still using patched_boot.img which is loaded in memory. So you will not lose root access and all Magisk modules work (until reboot)
Click to expand...
Click to collapse
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
ludditefornow said:
Thanks for the detailed reply.. this is the thing that confuses me. The Magical guide clear states to not reboot the phone after uninstalling the patched boot.. so how can the ota possibly pass?
Click to expand...
Click to collapse
OTA updater verifies system and boot partition (possibly other partitions too) - if they are intact, it applies the OTA patch to unused, secondary partitions. OTA updator doesn't care if your currently running boot image is patched or not, because it's not using files from RAM, but from ROM. Once update finishes its thing (stage 2/2), you install Magisk in backup boot partition, which after reboot becomes active. This is why it's possible to apply OTA while you're rooted with Magisk and you have A/B partition system (as long as you follow the guide).

Strange OTA behaviour after installing Magisk

After a long time I finally decided to upgrade to PIE (stock).
The latest official Fastboot ROM I could find is from May (V10.0.9.0) - so this is what I used to install.
Everything went fine, and as expected I was prompted for an OTA upgrade to August which I performed. The Build number become ...V10.0.12.0
Afterwards I installed Magsik (V19.3) via Boot to TWRP - also with no problem.
But surprise: I was prompted for another OTA-upgrade this time to July2019, and the Build number shows V10.0.9.0 !
Ok, I uninstalled Magisk to get this upgrade done, but the upgrade failed..
Went back to re-flash the Fastboot ROM for May and .. and ... and the story repeated.
Any idea what's going on?
I would reflash whole ROM with the latest official Fastboot ROM again (do not forget to remove bootloader lock command from the flashing script or you'll lose your data) and flash Magisk from TWRP. For the OTA update follow this guide, you don't really need to mess up with TWRP more than once https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md.
One thing to keep in mind - do NOT allow system modifications in TWRP as it will mount system partition as R/W and prevent future OTA updates to install. If you allowed it somewhere in the past (or you don't remember) - delete TWRP settings from /sdcard/TWRP and pay attention on the first boot of TWRP.

So how to root Android 10?

If we don't have TWRP,
How do we root the device?
Magisk has the option to patch a boot.img file. Technically, you could:
1. pull the boot.img file from the A10 OB1 zip
2. copy it to the phone's internal storage
3. install latest magisk manager, click on install - patch boot.img - choose the boot.img
4. copy the patched boot.img to a pc with ADB and USB drivers
5. put the phone in fastboot mode, sideload the boot.img
I have no idea if this would work, but you could give it a go. I believe that someone else already made a guide for exactly this here in the OP6T forum.
Refer to the twrp thread for OB 10.
https://forum.xda-developers.com/oneplus-6t/help/how-to-flash-twrp-android-10-beta-1-t3986345
Either do the OTA local upgrade and magisk uninstall then install to inactive slot method, or use the boot patch which there is another thread on that on the ROM Dev section.
I used the first, worked fine. But there is no supported twrp yet. Only magisk root is officially supported on Q.
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
g4seb said:
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
Click to expand...
Click to collapse
Yes, likely because the update flashed to the inactive, and there is no recovery now. So...if you want recovery, only way is to full wipe and do a MSM or flash all and wipe with older stable.
OP support/forums made announcements on their thread on what will happen with upgrading, or rolling back.
They have a rollback file you can download if you want it all working again including recovery. But you will get wiped as mentioned, and be back on the last stable and firmware. Then you can twrp and root all over again.
That is Beta testing for you!!

Categories

Resources