Related
Hello friends i was trying to root moto x style but first it got stuck in bootloader so i by mistake formatted every thing even the system etc and here i am now "No OS Installed! Are you sure you wish to reboot"
I unlocked bootloader by unlock key successfully, then flashed TWRP 2.8 and then installed SU file but as it did not worked i formatted fully including OS :crying::crying:
Now i can go to TWRP and boot loader is still unlocked so can some one please help me for from where and how i can get stock rom and flash it... i tried searching but only found Trupure rom but i am afraid to use it.
Please how can i get stock rom again and also wanted to get it root without runining everything... i am very much upset :crying: need real help now.
Note: i got it with lollipop rom then i updated via update from wifi and then i was on marshmallow.
I am Indian and using dual sim version moto x style XT1572.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
You can use the rom from the link. Put on sdcard and flash away. The one you want is Deodexed rooted ROM: indian_mm_deodexed_rooted.zip
bw03 said:
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
You can use the rom from the link. Put on sdcard and flash away. The one you want is Deodexed rooted ROM: indian_mm_deodexed_rooted.zip
Click to expand...
Click to collapse
Hey buddy thank you so much for the reply and link. I will flash the zip from twrp and check and will reply again.
Also should i also flash Indian MM radio.zip etc??
@bw03
Buddy i flashed it with indian_mm_deodexed_rooted.zip and it worked. Also wifi was creating issue of switiching to off when trying to turn on so i flashed it with Indian MM radio.zip and it got fixed and working great.
I hope this will also benefit to other issues who are around same issues.
Thank you so much for the reply and help.
Hello i have the same problem I am stuck in twrp and i tried several rom but in every section i had error message. Are there any one could help me to open my phone?
Thanks.
UPDATE: This is now unneeded because threr is a faster way ro unlock bootloader on official MM here, he updated for official MM
Hi, I discovered an unlock method for official MM!! This maybe long but's it totally safe
You need:
Adb and fastboot environment ready PC
LP RAW File
Android 6.0 Beta Unlock tool
Android 5.0 One-Click Unlock tool
First version of beta MM (Z00A) (Z008)
Official MM zip (find it on Asus site)
Thanks to all people upload these links
Just do the following:
Flash the lastest LP via AFT (using raw file given above), wipe all data. If you already on MM, you have to downgrade
Unlock your bootloader using 1 click tool given above
Boot to stock recovery and sideload the first version of beta MM
Unlock the bootloader using MM beta unlock tool above
Boot to stock recovery
Two case here:
Case 1: You can't boot stock recovery
Normally boot your phone (to Android)
Setup it as a new phone
If it shows there is a new firmware, don't update!!!
Enable Developer options, then enable usb debugging
Copy the official MM zip to external sd card
Open command prompt, run adb reboot recovery, accept the adb permission if prompted
After it boots to recovery, select Apply update from SD, then choose the zip file you've copied before
Wait for it to update, it may stuck at flashing splashcreen, don't worry, it's trolling you, may be Asus forgot to update the script
Goto step 7
Case 2: You can boot stock recovery
Sideload the official MM zip (adb sideload <filename>.zip)
Goto step 7
7. Flash this TWRP (fastboot flash recovery <twrp>.img)
8. Root your phone using this method
9. Reboot, if it shows "Your phone has failed verification bla bla..", then you've success. It may reset loop like note 7 in the first time start, don't worry.
9. Enjoy :highfive:
Note: If you're facing with battery problems on MM, factory reset it in Settings > Backup and Reset > Factory Reset > Erase everything
Successfully on my ZE550ML
The warning screen is normal so don't worry and there is no way to fix it for now
Reverse
Reverse #2
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
NiTesh said:
Please answer this I have a unlocked Bootloader + twrp Intalled + root, now I am really confused that after upgrading to MM will my Bootloader get automatically lock or what
Sent from my ASUS_Z00A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, BL will be relocked once you upgrade to MM.
If you want to unlock MM BL(6.0), refer to this thread.
Or you can downgrade to Lollipop referring to this thread. Then your BL(5.0) is unlocked.
Upgrade to MM
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
R3D SoX F4N said:
Hello folks!
2 week before MM was released i'ved opted to unlock my ZE551ML BL and therefore install twrp and a MM custom ROM..
so here´s the thing i stayed with the ROM for about 3 weeks and honestly..it works very well..but when i knew that 6.0 official was coming out i decided to go back to stock..i did it following manny tuturials avaliable for me to get my BL Re-Locked..but unsuccessfully..so i followed mr_gourav2000 tuturial (http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526) and reverted to the WW_Z00A-2.20.40.183-to-2.20.40.184 (hopefully i can get the sshot in this post) version...since my BL is unlocked i can´t get no updates..my question is:
Is there anyway to go to MM 6.0 by ASUS with the current status of my phone?
is there anything i can do to revert this??
Cheers to everyone
https://www.dropbox.com/sc/xue7iuqfyvgdvo3/AAATR4mYtcHzM1IhfKbx2a1oa
Click to expand...
Click to collapse
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
can anyone please upload official recovery for Zenfone 2 ZE551ML, currenty i have twrp installed on Android version 5.0 LP Stock
HungNgocPhat said:
Just download the update package and rename it to mofd_sdupdate.zip, copy it to internal storage. Then reboot to stock recovery, the update will automatically start. This should work if you have lastest stock recovery
Click to expand...
Click to collapse
i have twrp recovery at the moment cause i followed mr_gouvad2000 tuturial..
what do you sugest?
flash WW_ZE551ML_2.20.40.196_20160815.raw?
WW_ZE551ML_2.20.40.194_20160713.raw?
and then go and do what you told?
cheers
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
tridet18 said:
hello, i cant find first mm beta for ml551...can you help me? thank you and sorry for my english
Click to expand...
Click to collapse
someone correct me if i am worng but....
https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Look for this version WW-4.21.40.134
Hello, thank you but this version is official, i need de first beta 6.0
R3D SoX F4N said:
someone correct me if i am worng but....
Look for this version WW-4.21.40.134
Click to expand...
Click to collapse
that version...i can´t find it anywere..maybe someone here knows were to find it?
Updated the first MM beta link in OP
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
tridet18 said:
hello , thanks to your tutorial I managed to unlock the bootloader , I have TWRP version 3.0.0.2 with stock installed but when I wanted to install CM13 and gapps I restarted the phone and automatically returns to recovery again. some help?
Click to expand...
Click to collapse
Have you downloaded the correct build? There are build for MM bootloader, if you flash the normal builds, it will fail and reboot to recovery again. Gapps is the same for all builds
After you install that special build, do not update to newer nightlies, it will fail. For updates, check the link i give you and see if there is a new MMBL build.
About that, here is the post: http://forum.xda-developers.com/showpost.php?p=68542370&postcount=8551
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
tridet18 said:
hello friend, I tried to install the CM13 ROM that indicated me and I get Error 7 in TWRP 3.0.2.0, I have Android 6.0 (.134) official and if I can change kernel and flash rom SuperSU but change with a new MM Blows I can not (CM13, AICP, beanstalk ....) thanks for your help!
Click to expand...
Click to collapse
Run the script again (i gave you in above post). Download the CM13 in that link, not in the OP of CM13 thread. Flash that CM13 and Gapps (Gapps is universal for MMBL and LPBL).
May be you have corrupt download, I'm currently running CM13 on MMBL
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
hlp
tridet18 said:
Hello, I have finally found the solution, the problem is the recovery, the TWRP 3.0.0.2 da failure with new builds, I Flashed next on the link you put me through adb and now it works, thank you very much for everything .
Click to expand...
Click to collapse
how u unlocked bootloader
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Adarsh balu said:
Hey...Help me with this..
I tried to root my moto g4 plus using temporary twrp so that i get system updates,It is not working out.
I have used moto g3.. and used this same method for rooting and is successful..
In g4 plus till the last step i.e untill u need to flash supersu it works but there comes error.
Every data is lost and i have to boot into my custom rom backup...
Please suggest something to help me...please
Click to expand...
Click to collapse
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
EDIT - I understand you're desperate for help resolving this, please don't post the same thing in 3 places if you can.
echo92 said:
Can I request some more details please?
OS version?
TWRP version?
Did you unlock your bootloader and enabled OEM unlocking in Developer Settings?
Which rooting method did you use (e.g. did you flash ElementalX kernel https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 or the superboot method https://forum.xda-developers.com/mo...-how-to-root-n-firmware-npj25-93-11-t3532556) ?
What error do you get?
Click to expand...
Click to collapse
Here it is
I did not use kernel
Oem done
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
All steps are followed until flashing of supersu..The error comes there..is there any xt 1643 users who could suggest a correct reliable and error free method for this
Adarsh balu said:
twrp-3.0.2-0-athene
SuperSU-v2.66
My error was that I could not get booted back on...
It would not turn on..
Then i downloaded another stock rom from xda and got back...im xt1643
Click to expand...
Click to collapse
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
echo92 said:
Couple of things:
Try installing the newer TWRP from here: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
I don't think TWRP 3.0.2 is supported that well.
SuperSU - use the SuperSU 2.78 or the beta https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I think if you desire root, you'll need a modified kernel (so far, it appears that the stock kernel security prevents rooting, someone correct me if I'm wrong), which may explain the bootloops. Try with the ElementalX kernel method as linked above, seems that people have had luck with it. https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672 You may need phh's Superuser instead.
Click to expand...
Click to collapse
Thanks..let me test it....
Any way thnq for the suggestions...:good:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Adarsh balu said:
Tell me will i be able to update if android O comes for g4 plus..please reply fast
Click to expand...
Click to collapse
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
echo92 said:
If android o does arrive, I imagine you'll have to revert back to the stock ROM to update, so removing root and flashing your stock boot image over your existing installation. Alternatively you could fast boot a stock ROM to restore a stock install.
What's the rush anyway, no announcements have even been made for android o...?
Click to expand...
Click to collapse
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Adarsh balu said:
Im using stock rom..with nougat update....
So if o arrives i will need to do what exactly...please share
Click to expand...
Click to collapse
Again, Android O hasn't been formally announced yet...
I see you've already gotten an answer from tywinlannister regarding this question https://forum.xda-developers.com/showpost.php?p=71265934&postcount=249
I don't see much to add to his well thought out reply except if you're staying with stock (assuming you're using temporary TWRP):
1) Unroot completely using the SuperSU settings panel or follow the unrooting instructions for your superuser app.
2) Reboot into temporary TWRP, restore your boot.img (if you flashed ElementalX kernel) from within TWRP (if I recall, it's Restore >Select image and then assign it as a boot image). If you did not make a backup of your boot.img, there are images around (e.g. https://forum.xda-developers.com/moto-g4-plus/how-to/1643-indian-version-stock-boot-modem-t3460615 - i don't know if this is for nougat or marshmallow - download and extract the rar file, copy the extracted boot.img to your device and boot into temporary TWRP, then flash the boot.img).
3) Reboot and you should be fully stock - with stock kernel/boot.img, recovery and no root.
1a) As tywinlannister linked, you could just reflash the latest fastboot image which would remove root and give you a stock boot, which would be the best for reliability (which as of this post is this: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369)
Thus, when/if Android O does arrive, you should be able to update via OTA. It's gonna be at least 6-12 months away for the update, if previous Android updates have been anything to go by.
Hey guys, I tried flashing the stock moto oreo rom (october patch) through 1. flashing via fastboot and 2. twrp flashable rom.
Both methods worked but I lost my IMEI, regardless of which method I flashed the rom with.
I had made two EFS & Persist backups (one from resurrection remix rom and one from a twrp nougat june patch rom) and tried to restore them after flashing the moto oreo rom, but no success.
Can anyone help me with this? I really want to use the stock oreo rom!
Please help guys!
What version of twrp?
twrp which error during restore?
Ever flashed someone else's persist file when you were on stock?
I too am in the same boat, I upgraded to 8with the smart assist no isshes. and when trying to restore my efs and persits (backed up from android 7) with twrp it just doesnt work, hope someone has a fix
twrp-3.2.3-1-potter
for me
my imei also shows up in my settings but doenst work
vonwap said:
I too am in the same boat, I upgraded to 8with the smart assist no isshes. and when trying to restore my efs and persits (backed up from android 7) with twrp it just doesnt work, hope someone has a fix
twrp-3.2.3-1-potter
for me
my imei also shows up in my settings but doenst work
Click to expand...
Click to collapse
Refer to this post - https://forum.xda-developers.com/showpost.php?p=77359949&postcount=2
And the FAQ "On soak test 2 or later, I have my IMEI but no signal. What can I do?"
NZedPred said:
Refer to this post - https://forum.xda-developers.com/showpost.php?p=77359949&postcount=2
And the FAQ "On soak test 2 or later, I have my IMEI but no signal. What can I do?"
Click to expand...
Click to collapse
Thank you
I installed the twrp flashable stock and I got my 3g back, i did the OTA update and now I think its bricked, It will only boot to twrp :crying:
vonwap said:
Thank you
I installed the twrp flashable stock and I got my 3g back, i did the OTA update and now I think its bricked, It will only boot to twrp :crying:
Click to expand...
Click to collapse
Try flashing one of the full flashable zips from that thread, get the last one. But in the installer, do not select firmware.
Hopefully that will get you going again. And no, don't ever install an ota.
NZedPred said:
Try flashing one of the full flashable zips from that thread, get the last one. But in the installer, do not select firmware.
Hopefully that will get you going again. And no, don't ever install an ota.
Click to expand...
Click to collapse
Thanks for all your help is there any way to fix OTA updates? like relocking bootloader? or should I just leave that unlocked ?
I just installed \POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and am getting a 3g \ H signal now but its a different sim card and service from original card, seems to be working now
Is it just oreo that screws everything up , I know this is all over but its not very straight forward
im no android expert clearly
vonwap said:
Thanks for all your help is there any way to fix OTA updates? like relocking bootloader? or should I just leave that unlocked ?
I just installed \POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and am getting a 3g \ H signal now but its a different sim card and service from original card, seems to be working now
Is it just oreo that screws everything up , I know this is all over but its not very straight forward
im no android expert clearly
Click to expand...
Click to collapse
Bootloader doesn't matter, can stay unlocked.
And the IMEI/4g problem is Nougat only, never heard of someone who lost something on Oreo or when updating to it.
If you flash latest Oreo firmware for your region (endings with 17-xx are US, 13-xx is for the rest as far as I know) you should be good to go.
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