Related
For stock rooted/TWRP users, this is a step-by-step process of manually updating your Moto involving flashing stock firmware, updating, and restoring TWRP, root, and apps afterwards.
Benefits:
**It's really simple- once you get familiar with this process, you can do it fairly quickly.
**Take the time to read through and get everything set up and you'll be set for future updates.
**No begging the internet for flashable zips.
Preface:
So my situation is i'm running stock, bootloader unlocked, rooted, and xposed on my US XT1540 2GB Moto G. I went through the process this morning of updating to the new 23.46.4 update. Thought I'd share what I did for anyone out there wanting to update with questions ; hopefully some can be answered here. I'm familiar with flashing firmware files from my previous Moto X's '13 & '14 so trust me it's not a big deal to flash back stock firmware to update. This process should be applicable to any variant of the Moto G and and to any future updates as well, not just the one mentioned here as of 09/19/15. Just be mindful of your phone's version and use the appropriate firmware.
1) BACKUP
First, make sure everything worth keeping is on your microSD. Flashing stock firmware will wipe your phones internal memory so pictures, music, downloads, SMS, etc need to migrate. Also make sure you have SuperSU and Xposed on your microSD for re-installation. This might be obvious for some and you might have everything going to your microSD (sdcard1, EXTsdcard) already, but one thing you might miss is Titanium Backup...
Save apps in Titanium to microSD: Menu>Preferences>Backup folder location>Click to change>Ext. SD card>Create a new folder>Use current folder
Nandroid in TWRP to microSD: toward the bottom click on "Storage: Internal storage" and choose "Micro SDcard"
If you're super smart, after making that backup you'll copy that to your pc.
2) DOWNLOADS
Get the most recent firmware for your device from lost101's firmware thread (thank him threads like this are so helpful)- http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download and install the drivers for you phone, I believe the generic android driver will work but you can also get them from Motorola Device Manager: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download mini-sdk.zip, attached to the the bottom of this post. Useful light weight sdk containing adb & fastboot which should cover all your flashing needs. If you're not developing apps, full blown android sdk is bloatware
3) SETTING UP ADB/FASTBOOT
Enable USB debugging in Developer options
Extract mini-sdk.zip to a folder. Extract and add the contents of your firmware to that folder.
Open a cmd prompt on the mini-sdk folder (shift + right click, "Open Command Window Here")
Let's verify that adb sees the device:
Code:
adb devices
Should see "XXserial#XX device". If you get "offline", be sure to check your phone for the adb authorization dialog.
We're ready to flash firmware so reboot into fastboot:
Code:
adb reboot bootloader
4) STOCK FIRMWARE INSTALLATION
Once phone is in fastboot, enter the following commands in the cmd prompt (open on the mini-sdk folder containing the firmware files) one at a time. Let the current flash command finish before entering the next, especially at the img_sparsechunck steps because they take a 10-15 sec each. Also make sure all of the filenames match what you have; substitute accordingly.
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 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
5) UPDATE
When you reboot, if you don't get prompted for update check for it- About phone>System updates
Download & install update
When update is finished and phone boots back up, enable Android debugging in developer options.
6) FLASH BACK TWRP/ROOT/XPOSED
Place TWRP img file in mini-sdk folder. Boot back into fastboot and flash TWRP.
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-osprey-2.8.7-test1.img
Vol up/down in bootloader to boot recovery.
Once in recovery flash Supersu & xposed (optional of course) from your microSD and reboot.
Install Titanium from play store, go back into preferences and point to backup folder on the microSD and restore apps.
When xposed and modules are reinstalled through Titanium, you will need to reboot to enable. After that you'll need to tweak your preferences in system options like notifications or display, but any settings in modules (like gravity box) will be restored as long as you backed up app+data in TB. Easier than a custom rom clean flash in that aspect.
So that's it, with that you should be back up and running. Let me know if I missed some steps or if you have questions about the process.
*****
BTW, Installing xposed from scratch for those confused on what files to do what with: http://forum.xda-developers.com/show....php?t=3034811
Flash this one in recovery: xposed-v74-sdk22-arm.zip (or most current)
Install this apk after you reboot: XposedInstaller_3.0_alpha4.apk (or most current)
Please Delete
agleroy said:
Thanks for the guide. Still gonna wait for a flashable zip though.
Click to expand...
Click to collapse
You're better than that. Trying to empower you here...
Please Delete
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
a.cid said:
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
Click to expand...
Click to collapse
I took all the color out and tweaked it a bit. I was using the dark theme and everything looked pretty good, but when I switched to the light theme... yeah annoying.
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Why does every single guide say to erase the userdata partition??? This is totally unnecessary. Instead, boot into twrp and wipe your userdata. The difference is in your internal storage. If you follow the guide you wipe your internal storage in the very last command. My way, you just do a factory reset on the data partition which doesn't wipe the storage
Also, flashing stock recovery is an unnecessary step when it's being immediately replaced by twrp again.
Selmak said:
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
This isn't a custom rom...it's the official motorola firmware update
Thanks for this guide , it's good to know, but I would have to wait for a flasheable UPDATE.zip because my phone's configuration (XT1543, dual sim, 16gb storage, 1gb ram) doesn't have a stock firmware download link in the main thread... and also I don't want to reinstall my apps , haha.
If it works like the other 2 generations of moto g, and at least with the first moto x (all from my personal experience) just skip the erase userdata part and you'll keep your personnal data.
Ota update will go smoothly, no need to restore anything afterwards except root and recovery, indeed.
A backup is always a good thing, sure just in case, but i never used mine on all the ota's I installed on those 3 phones (moto g 2013 16gb, moto g 2014 and moto x 2013)
I don't own a moto g 2015 but my gf does, a 16gb/2gb ram one, she just got it so she installed the update before rooting. If nobody tries it before I'll try it with the next update .
cannot access filehost to get xt1541 5.1.1 any alternative link?
after I updated to 6.0 my computer is not recognising the device? any solutions?
Please add "fastboot flash system system.img_sparsechunk.6" to the top post. This could prevent idiots from sitting in a boot loop for an hour, while they try furiously to find a way out, an error in the download, revert to a previous firmware... Yeah, that was stressful.
Is this the same for the XT1548 virgin mobile 1G of ram and 8G of memory. I understand that it's probably not the same file I just don't really want to wait for the flashable .Zip. But I also don't want to mess up my only device as of now.
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
csumanth16 said:
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
Click to expand...
Click to collapse
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
acejavelin said:
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
Click to expand...
Click to collapse
MrTooPhone said:
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
Click to expand...
Click to collapse
No... If your rooted the /boot partition has been modified.
acejavelin said:
No... If your rooted the /boot partition has been modified.
Click to expand...
Click to collapse
And does it remain notably changed even after going through a full unroot via SuperSU?
MrTooPhone said:
And does it remain notably changed even after going through a full unroot via SuperSU?
Click to expand...
Click to collapse
No, doing a full unroot will return the original /boot partition, but be aware this will not undo any changes you made to /system with root access (such as debloating or Xposed modules), and even if you undo those changes, the Android system has already marked the /system partition as tampered so a check will fail.
I was on indian_mm_deodexed_rooted then flashed TruPureXMM as one of my friends suggested trying it out as it is smooth etc.
I didn't knew that it is Pure single sim version and after flashing no network and then i checked only single sim showed :crying: then i again formated and flashed back indian_mm_deodexed_rooted and modem_indian_mm_fixed but this time it shows two sims with no network atall and Emergency calls on both... In settings SIM cards its SIM 1 emty and SIM 2 empty :crying::crying: tried flashing with indian modem again and also tried lp modem but nothing is working, please help :crying::crying:
Both IMEI Unknown status.
I didn't even took back of my stock as i didn't knew about it before
Bootloader is unlocked and TWRP is installed.
Note: My x style came with lollipop and then i did official update with marshmallow and then i wanted to root so flashed.
Please help me get back dual sim with network if possible
EDIT: Solved the issue now and here is the solution:
Download Stockrom from this link according to your exact model and follow the commands exactly:
[Firmware] Moto X Style/Pure Stock Software by lAndroXl
I just ignored command fastboot oem lock begin as told by @dj_ooms so boot loader is still unlocked and also i have installed TWRP and rooted by flashing SuperSu.
Also very important thing is take nandroid backup after installing TWRP i.e backup your stock rom by selecting backup in TWRP... please also take backup your EFS partition also, thanks
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies and thanks to lAndroXl uploader and thread... really helped :angel:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
bw03 said:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
Click to expand...
Click to collapse
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
desiaddict said:
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
Click to expand...
Click to collapse
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.
bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
bw03 said:
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
Click to expand...
Click to collapse
I will try it out... downloading now and will let you know later when dl and flashing finishes and hope i get it working this time, fingers crossed.
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
You may need to do the Indian LP modem from the first linked thread too.
http://forum.xda-developers.com/mot...-eu-single-t3297051/post64888714#post64888714
I have posted up more DUAL Sim modems for you to try. Hope it helps and you get it sorted
Unicornzz said:
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
Click to expand...
Click to collapse
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
bw03 said:
You may need to do the Indian LP modem from the first linked thread too.
Click to expand...
Click to collapse
Yes i will LP modem flash.
Just one question to all : when i got moto x style in dec it was having Lollipop then i did marshmallow update and then flashed for rooting so now if i again flash to lP stock rom will it get bricked or work?? As i am not getting signals so i will try it later when nothing else works
desiaddict said:
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
Click to expand...
Click to collapse
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Unicornzz said:
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Click to expand...
Click to collapse
Guys still no luck... nothing worked. I tried both DS modem but did not got sim detection.
I hope somehow who might have faced same issue and got solved will see and reply the thread and save me.
You guys tried to solve my problem... Thank you to both.
Stock ROMs
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
dj_ooms said:
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Did you backup your efs partition? Your imei is inside that partition...
desiaddict said:
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Click to expand...
Click to collapse
To be honest, I left the lock bit out. These are the commands I used when I did it:
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 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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
dj_ooms said:
To be honest, I left the lock bit out. These are the commands I used when I did it:
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Oh GOD that totaly worked out great :good::good:
Everything is working fine now
Also rooted again without any problem :cyclops:
Thank you buddy.
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies... really helped :angel:
Hello xda community,
I've rooted my G4+ successfully and i can use my phone normally.
But from time to time i ran into bootloops after powering it up at the morning. Sometimes it took some loops at the “oem unlock warning” and then the boot animation shows up.
Sometimes the loop end up by booting automatically into the TWRP.
I am using the “ElementalX 1.04” kernel.
And sometimes my phone powers on by plugging in the charger….
Anyone got a clue or solution
BlackBull said:
Hello xda community,
I've rooted my G4+ successfully and i can use my phone normally.
But from time to time i ran into bootloops after powering it up at the morning. Sometimes it took some loops at the “oem unlock warning” and then the boot animation shows up.
Sometimes the loop end up by booting automatically into the TWRP.
I am using the “ElementalX 1.04” kernel.
And sometimes my phone powers on by plugging in the charger….
Anyone got a clue or solution
Click to expand...
Click to collapse
Try reflashing the stock ROM by fastboot..
It'll most probably solve the problem.
Swapney Raul said:
Try reflashing the stock ROM by fastboot..
It'll most probably solve the problem.
Click to expand...
Click to collapse
Hello Swapney Raul,
I´ve done that before. Everything works fine untill i root the device.
BlackBull said:
Hello Swapney Raul,
I´ve done that before. Everything works fine untill i root the device.
Click to expand...
Click to collapse
Which version of stock are you using?
Swapney Raul said:
Which version of stock are you using?
Click to expand...
Click to collapse
7.0
Buid:
NPJ25.93-11
BlackBull said:
7.0
Buid:
NPJ25.93-11
Click to expand...
Click to collapse
Try upgrading to 93-14
BlackBull said:
7.0
Buid:
NPJ25.93-11
Click to expand...
Click to collapse
Also, what rooting manager are you using? Check if it's SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133) or the latest Magisk v12 (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) - I'm not sure what the latest version of phhsuperuser is (https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394). You may wish to update to the latest rooting manager, see if that resolves your issue.
echo92 said:
Also, what rooting manager are you using? Check if it's SuperSU v2.79 SR3 beta (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133) or the latest Magisk v12 (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) - I'm not sure what the latest version of phhsuperuser is (https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394). You may wish to update to the latest rooting manager, see if that resolves your issue.
Click to expand...
Click to collapse
@BlackBull you'd also like to flash the 93-14 version of the stock rom via fastboot and then proceed with rooting and follow what @echo92 has mentioned. Updating to 93-14 will ensure stability as per the release notes.
I am rooted by magisk su.. Have not faced any such issue! I am on latest 14-4..
U can even try that..
abhi212b said:
I am rooted by magisk su.. Have not faced any such issue! I am on latest 14-4..
U can even try that..
Click to expand...
Click to collapse
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
Xt 1643, 3 gb, 32gb ROM... even i use EX... I flashed the EX 1st, magisk! Never faced any bootloops!
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
No its not the kernel problem ...
Its something eles..
Swapney Raul said:
No its not the kernel problem ...
Its something eles..
Click to expand...
Click to collapse
If i flash the unrooted stock boot again, my phone acts normal.
BlackBull said:
If i flash the unrooted stock boot again, my phone acts normal.
Click to expand...
Click to collapse
So, on the stock kernel, custom recovery and stock system, you don't experience any bootloops or powering on whilst charging?
I'd suggest, like others have already, to flash/update your device to NPJ25.93-14, as that newer update may fix issues that you're encountering. Of course, this will remove root, TWRP and though not certain, may remove your data too, so back up accordingly.
Perhaps one thing to try, if you're not willing to update, is to download a fresh copy of ElementalX 1.0.4 directly onto your device (either over Wi-Fi/mobile data). You may wish to use a file browser (e.g. Amaze) to inspect the properties of the ElementalX file and check that the downloaded file has the same md5 checksum and same/similar file size to that reported on Android File Host.
Reboot to TWRP (what TWRP version are you running, btw?).
Flash ElementalX as directed.
Wipe cache/Dalvik
Reboot.
Check your system is running, you may wish to try to see if you experience any of those odd behaviours.
If your system looks stable, download a fresh copy of magisk or SuperSU (depending on what root manager you had before, I don't think you can mix root managers without properly unrooting them via their respective root methods! You may run into odd issues, though I think magisk will install over SuperSU...)
Reboot. Back up your device in TWRP.
Flash the root manager of choice.
Reboot.
If you still face bootloops after fresh installs of both ElementalX/your root manager, then a re-flash of the stock ROM might be in order, to bring you up to date and also to remove traces of previous rooting from your ramdisk/kernel (which may be conflicting with later attempts to root, possibly). https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 for the Nougat NPJ25.93-14 fastboot ROM.
@BlackBull : I have faced no such issues after rooting my stock firmware. But "phh" SuperSu doesn't seem to be as efficient as the "chainfire's" SuperSu. Especially felt the difference while using apps like Servicely and Greenify. Both those apps worked perfectly with chainfire's SU but inefficiently with phh SU.
Probably the bootloops you experienced could be due to corrupted SU zip or flashing the wrong SU zip.
BlackBull said:
On which phone?
I have an 4GB RAM / 64 GB ROM XT1642 G4 Plus.
I rooted it now with Magiks. But i Can only start the phone with "ElementalX 1.04" installed.
But the wiered bootloops still happend.
Maybe its the kernel....
Click to expand...
Click to collapse
Having Elemental-X installed is pretty much required to successfully root Nougat stock. And it was always stable and solid for me when on rooted stock. But I have found the best way to root it is with SuperSU-2.79-SR3. Magisk has always been a pain in the a-- for me and for the life of me I can't see why everybody raves about it so much. I've tried it on 3 different devices and always disliked it. If the method of rooting for a custom ROM is Magisk, I will avoid that ROM.
Just my opinion (you know what they say about those) based on my own experiences. I know many others will disagree and that's okay too. But I have yet to find a a more stable way to root than SuperSU.
So I´ve tried differend combinations.
twrp-3.0.2-0-athene.img & ElementalX-G4-1.04 & SuperSU
twrp-3.0.3-n4-athene_shreps.img & ElementalX-G4-1.04 & SuperSU
twrp-3.0.2-0-athene.img & ElementalX-G4-1.04 & Magiks
twrp-3.0.3-n4-athene_shreps.img & ElementalX-G4-1.04 & Magiks
Boot only into TWRP with stock recovery and then root……
Every time I flash something, my phone gets weird…...
I have those bootloops witch ends up booting the system after a minute or so or by booting into recovery….
Even by only flashing TWRP without rooting running stock i have those problems.
But if i flash the stock data the phone acts normaly:
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 erase customize
fastboot erase clogo
fastboot reboot
I am running on "Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock"
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
mohitzr said:
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
Click to expand...
Click to collapse
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
barbaroja said:
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
Click to expand...
Click to collapse
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
barbaroja said:
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
Click to expand...
Click to collapse
i get baseband
[email protected] said:
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
Click to expand...
Click to collapse
Thanks for sharing. Very interesting, indeed.
In my particular case, it happened for no apparent reason. Quick reboots being a suspect here. It seems some got baseband and no imei, others no baseband at all... Any ideas on this?
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
This a dump of an untouched XT1686 92-8 firmware.
rachitrawat said:
This a dump of an untouched XT1686 92-8 firmware.
Click to expand...
Click to collapse
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
akshu2697 said:
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
Click to expand...
Click to collapse
There isn't one as there is no 92-8 firmware out there.
Sent from my Moto G5 Plus using XDA Labs
did it worked ? .. im having the same problem .. cant get my network signal and imei
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Repiix said:
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Click to expand...
Click to collapse
I haven't tried it yet,
I will tell you if this work.
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
I'm on an oreo rom(no volte). Will i be able to flash stock when the oreo rom is officially released? And hopefully get volte?
Arunxyz said:
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
Click to expand...
Click to collapse
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Arunxyz said:
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Click to expand...
Click to collapse
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
akshu2697 said:
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
system.img is a bit perfect backup of /system which will not break dm-verity.
akshu2697 said:
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
Click to expand...
Click to collapse
you can restore via twrp or fastboot flash
Edit: fastboot won't work. Need to compress into sparse chunks. Try motofastboot
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.