Downgrade from oreo to nougat - ZTE Axon 7 Questions & Answers

can anyone help me , am trying to downgrade from oreo to nougat. am currently : Axon7 A2017UV2.1.OB20 bootloader unlocked , latest twrp , rooted with magisk. have searched xda and www without a clear guide.
** am doing this all from my phone , do not have a p.c.** i read something at www about an extsdcard method (lost the link) but had no download links in the post. any/all help/advice/warnings apprexiated.
[emoji106]
p.s. have to keep twrp as i want to root again.
edit: nevermind. [emoji1]
err on the side of kindness

Sir, i just read your post and saw you are on Oreo with bootloader unlocked.
I tried unlocking my bootloader but coudnt successful. Can you please help me how to unlock bootoader of my A2017U with stock Orero B20

teji007 said:
Sir, i just read your post and saw you are on Oreo with bootloader unlocked.
I tried unlocking my bootloader but coudnt successful. Can you please help me how to unlock bootoader of my A2017U with stock Orero B20
Click to expand...
Click to collapse
sorry. a friend unlocked mine. but i'm sure there is a guide here somewhere. if i can find i will link you to it. [emoji1]
maybe here : https://forum.xda-developers.com/showthread.php?t=3704595
err on the side of kindness

Downgrading to Nougat is simple. You need a Nougat ROM and a bootstack for Nougat on your SD card. You should also replace your TWRP recovery with Oki's recovery, because it can help you better.
Both are available on these forums, but it is better to search for them by yourself to get familiarized to some extent.
Backup your internal storage, because there is a strong chance that it gets wiped.
Reboot to recovery, do a backup (better to the SD card), wipe cache, dalvik cache, data, system.
Get rid of the vendor partition using the Oki's Advanced features (Party Tools).
Next flash the Nougat bootstack, then the Nougat ROM. Reboot system. If everything is ok, your phone should be in the Nougat ROM.
Be aware that if things go wrong, you might brick your phone, and restoring it could be even harder.

Related

Axon 7 A2017U B29 Root, BL unlock, and TWRP

Can someone walk me through how to Unlock the bootloader, root, and install TWRP? I'm so confused. I tried to do the newbie way, even though I'm not a newbie, and I lost my B29 Stock Recovery and can't find the download for it.
Sent from my ZTE A2017U using Tapatalk
I haven't done it yet but I've done a lot of reading and this seems to me the best guide.
Head over to this link which is the TWRP thread. https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
Once you're in there go to bootloader unlock section. Download all the necessary files and on the bottom of the guide there will be instructions link which will take you here https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
Follow that and that should do it.
When i get a weekend off ill be using this method to get the Lineage OS 14.1 on my device.
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
amphi66 said:
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
Click to expand...
Click to collapse
greatzt said:
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
Click to expand...
Click to collapse
This was back last Nov, but I followed the guide, using the recommended files (was on B29, but used the B27 OK, then reflashed B29 at the end).
The warning involved backing up and then restoring the EFS partiton with tenfar's tool. DON'T! If you stick with system, data, and boot partitions you should be fine.
Good luck. You may want to check with @nolimit78. He has done this much more recently.
Yes, I agree with you @amphi66 that there is a lot of different places to get information about how to root/flash recovery for A2017U B29. Here's what I've done with two different A7's and both have worked each time.
1. Boot the phone to EDL Mode (Both Vol+Power on boot it'll quick flash the red notification light and then act like it's off.. it's not)
2. Use tenfar's tool to flash the recovery. (I renamed the updated TWRP img and named it "recovery". This used tenfar's tool to flash the updated TWRP on your device.
3. Once in TWRP, run the command (reboot disemmcwp and relaunch TWRP) and flash the package to use modifiable bootloader from B20.
4. Once that flashes now you can send the command in Fastboot "fastboot oem unlock" which will unlock the bootloader that doesn't trip anything notifying ZTE
5. At this point you can flash a B29 rom and have a grand ol' time. However, I would recommend using the LineageOS Rom that's available. Trumps everything else out there IMHO.
6. To do that You'll need to flash the Nougat Bootstacks for that rom to boot prior to flashing the Rom itself. I would recommend flashing the nougat bootstacks, reboot to TWRP, flash LineageOS, reboot.
Like I said, I've done with this with two different devices (Thanks ZTE) and both worked out just fine. I did this method with a device with b27 and b29, both ended up updated and flashed with CM/LineageOS with ZERO issues. This post here should also be pinned as the one true guide (THE KING OF THE NORTH) for unlocking/rooting a stock Axon 7. I spent probably about 4-5 hours working, trying to figure out how to get my device unlocked/rooted. However.. at the very end I wrote out instructions trying to help those who would come after me.. I searched the threads to make sure there wasn't already a thread out there.. and then.. it turns out there was.
Someone have the 5 files to unlock the bootloader 2017u on drive

b25 Update

I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
2CanSan said:
I have a new (3 day) that updated to b25. Was and is totally stock. Not happy.
Mar was way better on battery and performance. I have downloaded and renamed
b15 factory ota and placed in the sdcard. System update reports a valid update but before I
commit to doing this I wanted to verify with the community that it is safe to do.
After I do this update I am wondering if I can find a factory ota of mar if I can do the same thing again.
Thanks in advance
Click to expand...
Click to collapse
It's really simple actually: if you install B15 your data will be wiped, after that just skip everything and update to B29 (is B29 the latest? I have a G, dunno) and then use it. What you describe is not the actual performance that it should have, it's your specific case obviously.
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
tabletalker7 said:
I know what you want to do - if you want to remain TOTALLY STOCK I think you are out of options as I don't know anywhere that you can still download the stock ZTE B29 marshmallow. If you are willing to unlock your bootloader and install TWRP then somewhere in here DrakenFX has a B29 rollback that works great - it just won't work with stock recovery
Click to expand...
Click to collapse
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
2CanSan said:
All I really want is to remain stock but rooted and with TWRP for recovery for Nandroid backups. The B25 will not let me unlock the bootloader with Fastboot and when running MiFlash the phone is visible but getting "Hello packet error" I have read another method with fastboot but have not tried it yet (below). Somewhere I read that B25 was the problem and you had to downgrade and the MiFlash method was recommended.
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot reboot
I did everything but the first entry.
Thanks for any suggestions.
Click to expand...
Click to collapse
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
tabletalker7 said:
Go ahead with your rollback to B15 - that will let you unlock and install TWRP. Once you have TWRP go to this thread https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 and in post #2 you will find A2017UV1.0.0B29_RollBackModded.zip. Flash that, then flash TWRP again (you have to flash TWRP again ONLY if you want to keep TWRP as this flash file will automatically reinstall stock recovery). Also note on B29 I had to use SuperSU 2.65 (not the current one) for root.
Click to expand...
Click to collapse
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
2CanSan said:
By the system update.zip method?
Thanks
Also I would be happy to stay at b15 with TWRP and root.
Click to expand...
Click to collapse
Choose an username... said:
Wait - you wanted to stay stock? You didn't actually have to unlock if you wanted to. Just by using the update.zip method with some Marshmallow zip you could get to MM, and then you can update to N and you surely won't get the same problems that you've been having...
For example my G is on 7.1.1 and I get 6h+ of battery (right now, 3h36m with 41% left) so your problem is just that your installation was bad. If you unlocked you might as well just do the process that the guy above described though.
Click to expand...
Click to collapse
OK on the A2017U units you need the official marshmallow B29 package to roll back, and that only works with stock recovery on a clean B15 N install. The Rollback package I told you to use earlier will roll you back to B29 marshmallow NO MATTER WHAT YOU ARE USING (I have used this a lot, and OBVIOUSLY there are differences between the the A2017U version in North America and the A2017G version in Europe). If you want stock and rooted, I personally recommend B29 marshmallow over B15 Nougat, but either way go for it (I think the marshmallow had a much better radio than any of the Nougat packages). If you are interested in TWRP and root, I found B29 marshmallow much easier for both, and the marshmallow version of android also gives you Xposed, but back to your first post, you mentioned wanting marshmallow, and this is the best way to get it.
Step by Step method
1. Roll back to B15. Use the update.zip method. It will factory reset your device so backup everything you can't lose
2. Use MiFlash to unlock and install TWRP - check that thread on XDA for instructions.
3. (If desired) In TWRP, install the B29 marshmallow rollback. Do not reboot into system afterwards.
4. (If step 3 is done) In TWRP, flash TWRP. The marshmallow rollback will overwrite recovery with stock recovery
If you do this you will have exactly what you wanted in your original post. I can personally tell you this works, as I have tried every custom rom on here and always wind up back at B29 marshmallow when all is said and done. It has never failed me, and it will never fail you either.

4.1.14 to oreo, unlocked.

Hi, can someone point me to the official guide/tutorial to move from 4.1.14 to oreo.
I'm unlocked and using twrp. Not sure which version.
I don't can about data loss...so a complete wipe and install is fine by me.
I see an official guide that keeps data, and refers to the official guide that doesn't...but I can't find it!
Oh, and I'm defo encrypted when I go into twrp, as it asks for my pin.
If you don't care bout data
flash Full OS zip from Codeworxx TWRP
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003

Help with Flashing a custom ROM ( absolute first time )

Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
The toolkit guide is probably the easiest one.
Read the whole thread and try again.
Sent from my ZTE A2017U using Tapatalk
runninghamster said:
Hey guys, I wanted some help on flashing LineageOS 14.1 to my Axon 7 A2017G.
I've looked at a bunch of guides but they all seem outdated or way too confusing.
I tried to follow the guide under the "Axon 7 Toolkit " thread where there were some instructions on how to flash a rom for noobs and when going to test for fastboot, it says I don't have fastboot.
Tried to get fastboot by following some guide and using miflash but ended up doing something to my device where android asked for a password when i booted up, where as I didn't have a password and had to end up factory resetting my device. LOST ALL MY DATA
If someone could please give me a simple, easy to follow guide on how to unlock bootloader, and flash custom rom, I would be immensely grateful.
Also if there is a guide on how to restore back to stock rom and factory settings in case I need to send phone back to ZTE at any point that would also be helpful.
:good:
Click to expand...
Click to collapse
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
I will try this today, thank you for your time in typing this
runninghamster said:
I will try this today, thank you for your time in typing this
Click to expand...
Click to collapse
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
raystef66 said:
Or try this tool to unlock your bootloader....way more advanced by the way thnx @djkuz
Just install the axon 7 drivers, this tool and....UNLOCK with ease :good:
Also all files to revert back to stock, flashing modem, recovery... etc are well discribed there. Just take a peek there...
Just another advice : do read all threads carefully, no matter what you're doing, do backup regularly and all will be OK :good:
Click to expand...
Click to collapse
Thank you so much, will try today!
Choose an username... said:
LOSING ALL YOUR DATA will be something normal actually. If you want to go to LineageOS you will probably lose it a bunch of times...
Well it turns out the toolkit is not the easiest way. Do this:
You didn't seem to search. Use "Unlock bootloader easily" by WesTD. After that simply go to the LOS thread, and download the ROM, the Universal Bootloader, and the modem file for your phone (for the G). Get Magisk too. and GApps for arm64. ) Then enter TWRP, ensure that it's 3.2.1-0 or more, else update it (get the newer .img for ailsa_ii or axon7 and Install - Install image - Recovery partition). Format data, and make sure that it formatted with ext4 (it'll say -formatting with make-ext4fs or sth). flash the bootloader, then the modem, then ROM, then Magisk, then GApps. After that boot.
Click to expand...
Click to collapse
Followed your steps and managed to unlock the bootloader successfully. Afterwards I tried to flash TWRP using the Axon Toolkit and this error appears. Have 0 clue why. A little help please.
View attached >>>
EDIT: nevermind, tried to boot into recovery and twrp booted, not sure why the error appeared though. thanks for the help!

flash potter on xt1687 retus?

Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
itcanbdone said:
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
Click to expand...
Click to collapse
What firmware? 7.0 or 8.1? If you are on 8.1 it's as safe as it ever is to flash a custom ROM.
If you're still on 7.0 you should update first and in any case make a full nandroid backup incl. Persist and EFS before you flash anything.
Sent from my Moto G5 Plus using XDA Labs
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
itcanbdone said:
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
Click to expand...
Click to collapse
Yes. If you can update via OTA that should be the way to go. If you can't flash full Motorola signed fastboot 8.1 firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Unlock the BL on Motorola website, boot to or flash TWRP and make a full nandroid incl. persist.
After that you shoud be good to go and flash custom ROMS. Check whether the selected ROM needs 7.0 or 8.1 as base, almost all of them need stock Oreo.
Sent from my Moto G5 Plus using XDA Labs
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
itcanbdone said:
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
Click to expand...
Click to collapse
You wrote you're on the retus channel and model is 1687. Here are the firmwares for your device, the second one ( OPS28.85-17-6-2) is the latest and last build, flash that one and everything should be fine:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETUS/
You still know how to fastboot flash? Unzip firmware to ADB/Fastboot folder etc.?
Here's a post I made for someone else, it includes a link to a flashall.bat, put in in there too so you don't have to manually flash all partitions, just double-click it and it'll run all the commands for you.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
itcanbdone said:
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
Click to expand...
Click to collapse
I'm not sure that I understand everything. After flashing (official) TWRP and making a nandroid you weren't able to boot to system, only to bootloader?
Have you updated to 8.1 stock Oreo before?
Havoc needs that definitely:
https://forum.xda-developers.com/g5-plus/development/rom-havoc-os-v2-2-t3906282/post79018816
It won't make any sense to revert to stock and root it because after flashing havoc root will be lost anyway. What do you mean with "the two su & Magisk aren't cuttin it in TWRP"? (English is not my native language)
Why two? There should be magisk only to flash.
So the goal seems to be making TWRP work correctly when running havoc to be able to flash magisk.zip and boot to system.
Can you post a recovery log after the attempt to flash magisk from TWRP (the function is in TWRP/ advanced/log.)
Can you boot to havoc directly now?
Are you able to reach TWRP?
I need the error message that appears when you try to flash magisk, should be in the log.
And what is it about two things, su AND magisk?
Magisk.zip is the su binary.
Please provide some more information and sorry if it's me who don't understand something.
Sent from my Moto G5 Plus using XDA Labs
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
itcanbdone said:
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
Click to expand...
Click to collapse
Never use SuperSU alongside with magisk but I think you know that now.
To remove encryption: It's not enough to wipe data in TWRP, you have to format it (the option where you have to confirm with "Yes" and not just wipe). That will wipe your internal storage too.
Only formatting data in TWRP will remove the encryption and the Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip will keep it decrypted. Make sure usb debugging is enabled.
Boot to TWRP and flash ROM and Gapps (both in one action without a reboot in between).
Now flash the no verity-force encryption.zip.
You can reboot to system now but you can also flash the magisk.zip directly afterwards, it helps to keep the data partition encrypted too.
I flash everything in a row.
Check that thread: https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-remove-device-encryption-t3863586
(page 2)
Sent from my Moto G5 Plus using XDA Labs
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
itcanbdone said:
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
Click to expand...
Click to collapse
I decrypt my device, for example to have access to /data in case of a bootloop because of a magisk module. I don't like the idea of not physically seeing parts of my partitions or even not being able to edit it.
From the sight of security it's better to encrypt naturally. It depends a bit how old your device is and what you want to do with it.
I never lost my device or it was getting stolen so as long it's in my pocket I don't need encryption.
But that's just my personal opinion.
Sent from my Moto G5 Plus using XDA Labs
Hey so I found a really cool way to decrypt but ROM after it's already been encrypted and you have all your stuff in it, I figured it out on accident. What I did was simply did a backup through TWRP and formatted the drive. When I restored the drive it was decrypted! And all this time everyone ever told me that you cannot decrypt. Pretty cool. Actually found this out by switching to a ROM and then going back anyway maybe people should know this? Hope it helps thanks for all the pointers

Categories

Resources