Related
Hello,
I am a happy owner of OnePlus 3 and at the beginning when I got this Smartphone and run it, I had to set-up a Pin which was also used for Encryption,
due to the decision that I wanted to change it, I have tried numerous things to do this, either via System -> Security, System -> Lock Screen or TWRP Recovery.
Then I have stumbled upon a wiping feature in TWRP. (TWRP Menu -> Wipe) where there was a couple of options like Advanced Wipe, Format Data and Swipe to Factory Reset. So I have
decided to see what Format Data does which showed me the following statement before I continued with it "Format Data will wipe all of your apps, backups, pictures, videos, media and
removes encryption on internal storage". Well when it said it removes the encryption I have proceeded because at this point where all of the methods failed I wanted to remove and
re-encrypt my OnePlus 3 again in order to change my encrypting pin. Ok, cool this worked perfectly except that now I can't restore my original rom or encrypt my OnePlus 3 again ....
Then I have flashed CyanogenMod 13 Nightly from August (The latest one on the CyanogenMod website) and when I went into System -> Security there was Encrypt button instead of saying
Encrypted at the top of the menu then I have played around with setting up a new Pin/Password and when I went throug all the process at the end the following happens within a few
seconds: a green dissasembled android shows then screen turns black and returns to lock screen. I checked if OnePlus 3 is encrypted and is not. This is not the normal as usually
encrypting takes some time.
Also, I have tried to restore my original rom which came with my smartphone and was encrypted, when I restored it, OnePlus 3 stucks on the first screen showing OnePlus logo on the
middle of the screen and text "Powered by Android" on the bottom of the screen.
I presume that CyanogenMod 13 encryption is broken or that I shouldn't have format Data ?
Is there any way that I can encrypt my smartphone again ?
P.S I know that OnePlus 3 encryption is handled by Hardware.
You can try downloading the official OxygenOS ROM, flashing it and trying to encrypt again. Last I tried doing it on Sultan's CM13, it didn't work, so it might be a CM problem.
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
abhibnl said:
As per my knowledge, if you flash stock OxygenOS rom and also be on stock oneplus recovery. Performing a Factory Reset will automatically encrypt your device again. But you must be on stock recovery + stock kernel + stock rom in order for it to work.
Click to expand...
Click to collapse
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
formating data with TWRP -28 will decrypt your phone, it's madethis way so it can work on beta 9 and f2fs ...
that said i had encrypted device before on CM
so if you're not using beta 9 and your data partition is not f2fs, you can have an ecrypted device, the easiest way is to sideload official rom 3.2.8 (make sure you're on stock recovery and start adb sideload from there) , after the sideload the phone will be encrypted, if you're staying at MM, fastboot TWRP .22 or 23 or just the official in case .28 decrypts the phone.
Gliop022 said:
Why do I need to be on stock recovery ?
Won't TWRP work just fine ?
Click to expand...
Click to collapse
Well man i want you be on as much safe side as possible. When you perform factory data reset on stock recovery, it will wipe and reformat your internal memory as well. TWRP only wipes data partition, and you need to format whole internal memory manually. But stock is recommended for full compatibility.
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Gliop022 said:
Ok, I have finally re-encrypted my smartphone.
So for the future people who have the same problem as I have, do the following:
SIDE NOTE: You don't need to unroot anything, just re-flash original Oxygen OS and go forwards from there
1) Download Oxygen OS from official website (downloads.oneplus.net)
2) Copy it over to internal storage
3) Enter Recovery Mode => Volume Down + Power Button
4) Flash downloaded .zip file via Recovery Mode (SIDE NOTE: The flashing progress might look like it have a loop but it takes a little bit of time to flash it, more than CyanogenMod anyway).
5) Now, after you have flashed the system .zip file and rebooted your smarpthone, it will take some time to load so don't panic that you have stuck in bootloop as it again, takes some time to load the first time.
SIDE NOTE: My suspicions are that it takes some time to flash and run the first time because it needs to set-up some encryption parameters or something like that but I might be wrong.
6) Then when you finally get to the wizard screen and go through the initial setup like wi-fi, sim card etc, the system will ask you if you want to protect device before it turns on, you choose yes and type your PIN or Password. After that step your smartphone is successfully encrypted again, enjoy !
Click to expand...
Click to collapse
Hello Gliop022,
Do you know if flashing OxygenOs stock from TWRP 3.1.0 encrypts the phone or do I have to be on stock recovery?
Then once the phone is encrypted, are you able to flash an OOS based ROM (e.g. FreedomOs) and keep the encryption?
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Ran into almost the same thing last night (not using flashfire, but with the factory flash-all.bat). Forgot to clear my theme and got the system UI error with everything borked. Even had the invalid password in twrp.
I hate to say it, but I had to just flash the factory image with a wipe and start everything over. Lost all my pics and music from the few days I had the phone. I have now learned how not to update in the future.
IrocD said:
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first mistake was not disabling my Substratum overlays before doing the above, even though I knew better. So anyway...
I knew something wasn't right the way my device rebooted in the middle of Chainfire doing its thing, and was on the G/progress bar for a long time. I decided to dirty flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread which has ADB commands that supposedly fix this. So I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
Click to expand...
Click to collapse
What a mess hahah! It sounds like your password file got corrupt; doing all that dirty flashing is messy. If I were you I would connect the phone to a computer and get off what data you can (most stuff is cloud now days anyway). And flash a 8.1 stock factory image using fastboot on the bootloader. You can never go wrong with flash a stock factory image. Yes you loose your data, but you get a working phone haha. If your really worried about data see if you can get MTP to work and transfer it off.
Dumbass me
Yep, that was me yesterday. Genius me sideloaded the 8.1 OTA without disabling my Substratum overlays and so I was met with the "System UI Tuner has stopped" message. Then an automatic reboot to the bootloader asking me to either "Try again" or "Factory reset phone". Guess what I had to do to get my phone working again? Had to factory reset that sh*t.
Oh well, at least I made sure to unlock my bootloader this time around before setting up my phone.
But to be fair, would've been f*cked either way even if I had waited for the OTA because it's essentially the same thing as the zip file anyways. Lesson learned: disable Substratum when you update your sh*t.
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Strange. I didn't disable my Themes and I had no issues at all sideloading.
fantasy2c said:
Fastboot boot TWRP beta 2, and go to advanced and sideload the substratum recovery zip and it'll fix it
Click to expand...
Click to collapse
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
I only update once a month when a new patch comes out.
I set my apps to not auto update
After a new patch comes out in the first week of the month I
-disable the overlays and remove them
-update swift black and compile new overlays
-update all my apps
-adb to recovery and flash ota
-apply new overlays
- reboot and good to go
I have done it before to you can just boot TWRP as long as you have that rescues zip on your flash drive you can do it that way too
rajlulla said:
This is exactly what I did. When it asks for your password, click cancel and it'll let you get into twrp. Go to adb sideload and sideload the rescue zip. I've attached it below. When you boot, uninstall the old overlays, then build and enable them.
Click to expand...
Click to collapse
Thought I was screwed, Thank you so much for this post.
Try formatting your internal memory using TWRP. It should be "formatting", no other type of wipe will be sufficient. Then flash your favourite ROM and enjoy!
phone encrypted.
all started one day, i was 0% battery, phone shut down itself, charged, turned on, the first password of encryption is ok, the OS password of the lockscreen GIVES ME ERROR.
i wonder, WHY? i thought i can use the twrp fix to erase the password inside the OS, ok, i try:
1) removed the 5 files with the twrp file manager, rebooted, NOTHING, after the first password accepted the boot logo is FOREVER going.... stuck.
2) tried to dirty flash the same rom i have ( a resurrection remix 5.8.5 by pranay) , nothing, same result
3) tried to format wiping data, cache, dalvik, nothing.
ok so i said myself UPGRATE TO OREO ROM, i boot into twrp ( twrp asks me the password, i enter it.. and WORKS! i don't know why the SAME password no more works into the OS) and with the MTP i transfer all mi video and pictures. ok!
i flashed the NEW twrp 3.2.1 for oreo ( i had 3.1.1.), i download some custom rom oreo, 2 resurrection remix and AEX, i wipe as usual, i install the aex and all works but i do not see the option to add the FINGERPRINT, mmmhhh in the telegram group someone told me that i "need to encrypt" to make the fingerprint option APPEAR into the OS..... ok no problem, i CAN do it! i WANT to do it! i can't live without encryption for privacy reasons. i charge the phone, press on encrypt and it reboots, i see the RR logo, 10 seconds later i am int othe OS. yes... but STILL UNENCRYPTED
i try to change the rom, new formats, new roms, SAME PROBLEM. i discovered that maybe the data partition was ruined, ok i did several "repair", i did several changes to f2fs and return to ext4 .... but sometimes i got some strange errors when trying to change the filesystem TO f2fs.
then i tried to flash the STOCK ROM follwing this guide
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914
i made it all correct, now i am on stock s244 rom, in this rom i can use fingerprint but the encryption password bug is STILL PRESENT, it simply does not encrypt my phone if i press to encrypt! made a lot of tests, repair, change file system of data..... NOTHING HELPED ME. ah yes...... at a precise point into the OS i see that my phone is encrypted. WHAT?
so i boot into twrp and it asks me the password i enter it, but it is WRONG. wrong? NOT POSSIBLE it is the same....the same! i tried a lot of password like password.... default_password, 123456,0000,000000 ........
to recover my twrp i used the command "fastoboot erase userdata", it worked, now i am without a "fake" encryption. i continue to do tests, sometimes my file system showed into the twrp in the wipe menu... is showed as "auto", sometimes as "emmc" ........ MMHHHHH never seen these kind of file systems! so i changed them every time to ext4!
then i tried to flash back my "old" rr rom nougat 5.8.5 , it works, in this rom i see the FINGERPRINT OPTION, but the same bug of impossible encryption at reboot.
- so i think i can try to flash the old twrp 3.1.1 because maybe the latest one is BUGGED! maybe! i flash it....keeping the OREO rom, and still can't encrypt.
- so i try to also flash the 3.1.1 twrp... and another clean instlall of RR nougat, i do all wipes every time, all precise, no dirty flash.... and with rr nougat i CAN use fingerprint but NO encryption.
i wonder ......... i use the SAME twrp image i used for months! same file! my file.
i use the SAME ROM ZIP rr 5.8.5, why in this moment i have a "different" configuration than before? filesystem is the same ext4.... but the phone still does not want to let me encrypt it! and someone must show me the REASON WHY with all oreo roms the user cannot use the fingerprint scanner ( there is no option into the os!) without to use the encryption?
I HAVE ALWAYS USED FINGERPRINT ON OTHER PHONES WITHOUT ENCRYPTION.....
now i have 2 solutions:
1) keep the RR nougat, unencrypted BUT AT LEAST with fingerprint unlock.
2) use the RR ( or any other oreo) rom but unencrypted, and WITHOUT the possibility to unlock with my finger! grrrr!!
please give me your advice, your opinion how is it possible i tested so much different configurations, mxed different twrp, different roms, changed data file system from ext4 to f2fs and the opposite, tried to "repair" file system....... appeared random ENCRYPTED twrp but with an "impossible to know" password.... i also flashed the stock rom with the fastboot command following the guide on xda i posted at the link, i feel really empty and without possibilities to fix this problem.
but as i can remember all started with the phone shut down at 0% battery! from that point my password has never been accepted anymore!!! i was LOCKED OUT from my phone, to be precise not my full phone because the password WORKED to unlock the encryption! ( i recoveredall my files!) but the OS refuses to accept the "same" password i used to unlock the encryption... it is very strange!
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
cd Downloads
Click to expand...
Click to collapse
C:\Downloads\platform-tools
Click to expand...
Click to collapse
Could be somewhat different, depends on where you have your Downloads folder.
adb devices
Click to expand...
Click to collapse
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
adb kill-server
Click to expand...
Click to collapse
adb reboot bootloader
Click to expand...
Click to collapse
Now, use:
fastboot oem unlock
Click to expand...
Click to collapse
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
fastboot flash recovery r.img
Click to expand...
Click to collapse
fastboot boot r.img
Click to expand...
Click to collapse
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
Go into "Reboot" Menu, and chose recovery
Click to expand...
Click to collapse
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Go into "Wipe" ,chose "Factory Reset", then go back and chose "Advanced Wipe", now select the data partition, and chose to change the file system. Chose "f2fs"
Click to expand...
Click to collapse
Now, go back and into the Reboot menu, Chose Recovery again.
Go into "Wipe" again, "Advanced Wipe" -> Select Data Partition only -> Chose Change File System-> Chose ext4-> Go Back into Main menu
Click to expand...
Click to collapse
Chose "Reboot"-> Chose Recovery again.
Click to expand...
Click to collapse
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Go into "Wipe" Menu again -> Chose "Format Data"-> Type yes and accept.
Click to expand...
Click to collapse
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Main Menu>Reboot>Recovery
Click to expand...
Click to collapse
Go back into the Wipe Menu->Advanced Wipe-> Select data Partition-> change file system->Chose ext4
Click to expand...
Click to collapse
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Go to Advanced Wipe->Select System Partition-> wipe it.-> Back to the Main menu
Click to expand...
Click to collapse
Now it's time to flash Stuff!
- Flash your Rom
- Depending on what Android Version you're on, flash your desired Custom Kernel which should be compatible with your Rom.
- Flash Gapps, if desired.
- Flash Magisk or SuperSu for Root, if desired.
- Wipe Dalvik and cache. Now go and reboot
Click to expand...
Click to collapse
thank u, i will test it within a few days!
just a doubt.... when u say to put the recovery image here C:\Downloads\platform-tools
i simply generally put the files i want to flash into the folder called "minimal adb and fastboot" becuase i use that way, is it ok?
and i wonder why to use this command "adb kill-server", i've never used it... and why to priorly use "adb devices" ....jus to see if the phone is read by the pc?
ok.. but i suppose the command "adb reboot bootloader" does not require to kill the adb server.... i've never read to do it.
and last thing.... how do you think that this method would save me? it seems just another option to flash the stock rom.. but i already did it followinf the guide i linked, and i also upgraded at the last OTA within the OS....
sm00th4f3 said:
Now it's time to flash Stuff!
Click to expand...
Click to collapse
thank u bro! u are MY ANGEL now it works!! u solved my problem!
realista87 said:
thank u bro! u are MY ANGEL now it works!! u solved my problem!
Click to expand...
Click to collapse
You're welcome. I had to learn how to solve this the hard way....glad that i could help you!
Rocking RR Nougat+Magma Kernel= Best Combo for now
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
realista87 said:
https://forum.xda-developers.com/lenovo-p2/development/rom-resurrection-remix-v6-0-0-t3792929
why not this OREO rom by PriyeshP? i had nougat rr but battery life was not perfect... i had to mad a lot of tweaks with greenify and bocking some services within the options of the RR just to achieve a good battery life, but not perfect idle battery
Click to expand...
Click to collapse
Some options aren't working and are still present in the rom.
Battery life on Nougat was pretty good for me. 13hours of sot daily under heavy usage.
sm00th4f3 said:
First of all, my deep condolences.
Second, dude, you have done so many wrong turns..but let's get to fixing.
First of all, download this: https://androidfilehost.com/?fid=817550096634780916
It's a one click Firmware Rescue Folder, with our oldest Firmware( 6.0 MM).
This tool can always be used, no matter if you're unlocked or locked. So it's your last key to get on Stock Rom. Even if your phone is stuck at bootloop, etc. .
Turn your phone off and open up "flashall - stock reco.bat".
Let it do it's job and do not under any circumstance remove the cable.
Your phone will reboot on its own after it's done.
Once your phone is started, you can either keep on using Stock and setup as usual , OR you skip Google Login, complete the Setup Wizard. And then login into WIFI manually through Quick Settings.
From there tap on the "System Update is avaibable" Message. And so all of the ota updates. Also while you're waiting for the download to complete, enable Developer Options (Tap 5xTimes on Build Number), then enable USB Debugging.
While it is still downloading on your phone, go ahead and download https://dl.twrp.me/kuntao_row/ to your computer, the latest version.
- - - After all ota Updates are done, you should be on S251, ADB Debugging enabled, Google Account still not setup - - -
Okay, open up CMD from your adb-platform tools folder, if you don't have it, download it from its official source here.
Rename the "twrp-3.2.1-0-kuntao_row.img" to "r.img" and put it into the extracted platform tools folder.
Connect your phone to your pc. Open up cmd and navigate to your platform tools folder.
The Commands for CMD are:
Could be somewhat different, depends on where you have your Downloads folder.
Tick the one tickable option on the new poped up prompt on your phone. Accept it.
Now, use:
Now, use:
after this, either your phone reboots on its own, or it doesn't. If it doesn't, don't worry, it's fine.
Now, use
in TWRP First Time Pop Up Message. Just tick the one small box, and use the slider.
No questions asked, just do it.
Wait for Twrp to boot back into twrp. Once you're back in your menu.
Now, go back and into the Reboot menu, Chose Recovery again.
Wait till it boots to twp again. Tap on the right button on your navigation bar, now the logs will show up. Look for anything red; there shouldn't be any errors now.
Do not reboot under any circumstance.
Now, that this is done, go ahead and reboot back into Recovery.
Go back to Reboot menu and once again chose recovery. Wait for it to boot back into Twrp.
Check for any erros on your log. (right button on your navigation bar. Tap again to go back into the Main menu)
Now it's time to flash Stuff!
Click to expand...
Click to collapse
The file is not available anymore - do you know where I may be able to find it?
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
fingerprint not showing
Lavesh05 said:
my phone shows "encrypted" but there is no "fingerprint" option in security settings. currently on stock s244 deodexed i tried los 15.1 n stock but cant find fingerprint in settings. can u guide me how to get fingerprint option back pleaseee
Click to expand...
Click to collapse
did you find a solution , I'm having the same problem
Same problem for me.... and nothing works.....
The original thread was closed...sorry guys I've been busy. Link to the rom has been updated!!!!
Eureka! After two days of trials, tribulations, and extreme reading, I have been successfully able to create a flashable, working Stock Rom for the MetroPCS XT1765. And yes, I figured out how to get root working on it too (albeit experimental)!!!! This has been something visibly lacking in our E4 community, and since its the phone I have, I felt it was a necessity since once you unlock the bootloader or ever took an update its impossible to get the original .xml back on the phone.
Disclaimers Before You Begin:
This tutorial is for people like me that wanted a flashable stock rom for the Moto E4 XT1765 Metro PCS Qualcomm/Perry Variant running on stock Nougat 7.1.1 Please follow the guide carefully. Cutting corners and skipping steps could have MAJOR CONSEQUENCES.
For everybody with other Perry variants, I don't know if this rom will work or not, so if you're feeling frisky try at your own risk as this has only been tested on the XT1765.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
Introduction
The A8M'S METROPCS XT1765-PERRY STOCKROM PROJECT was created from the Motorola PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml firmware, straight from their official site. This was not made from a backup, but from extracting the firmware files itself, and compiling via Assayyad kitchen. Nothing was removed from the firmware on this build, but you will have to flash Open Gapps and add it during installation, as well as No-Verity. Outside of that, it's a virgin rom slightly removed.
Preparation
1. READ EVERYTHING IN THIS GUIDE BEFORE STARTING! This variant can tear you a new one, so get a handle of what you're working with on this.
2. This is only for people that have bootloader unlocked their phones, and can successfully use TWRP on their device. I highly recommend @squid2's TWRP (which is in my download files list on this guide). I can also only give support for those using his TWRP, as that is the one I used flashing this rom.
3. Backup all your data if you want - the phone has to be wiped clean for this to work right as a dirty flash won't cut the mustard. It's not hard exporting your contact list, or using SMS Backup Restore for your call log and text msgs to your SD card. This helps putting back your phone exactly how you had it before this. Takes a second (but be sure to uninstall SMSBackupRestore when you've successfully restored your stuff unless you like it).
4. Download all the files from the list below,and put all of them but the boot.img on your SD card. That is the Stock Rom, the noverity.zip, the magisk.zip, superuser.zip, rootchecker, and opengapps.zip. Make sure the file sizes are correctly matching and that there are no errors in your transferring.
***NOTES SO YOU DON'T FREAK OUT***
Once you flash the rom its going to take 3-5 minutes to boot the first time. It's normal. If you see the "Hello Moto" constantly repeat, that's a bootloop, and you need to wipe and reflash again (even though this did not happen to me). Also, if you see a Bad Key black screen and it doesn't boot, you've made a mistake by not flashing no-verity after flashing the rom. It isn't a brick, you just need to go to recovery and flash it again.
Files Needed:
Download and add these to your SD card. These are the exact files I used on my phone. ***NOTE*** My file share service says they will delete these June 14th, so if you know of a fast share site that's free and can handle big files, please let me know.
Mod Edit: If / When you update these links, PM @Az Biker to reopen this thread.
1. My Flashable Stock Rom: https://drive.google.com/open?id=1ScvA3zO6qHY4mhMtaM4aDajx9ZH6CpYj
2. OpenGapps Nano: https://drive.google.com/open?id=1x3Uz_sia1N3OYPGrdEwJ7TBeSmyiDlEZ
3. No Verity Opt Encrypt.zip: https://drive.google.com/open?id=1FqcpWgYJ16HYjIzZgIlHEZOlKJPjaorM
4.Superuser-r259.zip: https://drive.google.com/open?id=1iFswMvZ2vycIrQ4tK7nTWZAG7zktrPH2
5. Magisk v14.0.zip: https://drive.google.com/open?id=1wyV5EJe2wtSIadFNZsbJQOfGrsNQzG4p
6. Root Checker (Playstore)
7. Boot.Img file in case you make it to the bonus round: https://www45.zippyshare.com/v/Uhru1YeL/file.html
Additional Software: you may need Minimal ADB and Fastboot in case you don't have TWRP installed already for the rooting part or if you run into problems trying to gain root; you'll have to search XDA for that one .
Part I - Installation:
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. As soon as you flash the stock you'll see the phone trying to push an update, as it auto turns on your data if you choose not to set up wifi (which you shouldn't do just yet).
3. Boot into Recovery TWRP. (If TWRP isn't installed, see 3A and skip this part.) If TWRP is installed you can power the device off and then hold the Volume Down plus the Power key to get into fastboot, and with the volume rocker select recovery and then hit the power button to boot. If you have unlocked the bootloader you will see N/A black screen in this process.
3A. If you do not have TWRP installed, With the phone on, run the command in Minimal ADB and Fastboot "adb devices" without the quotations. You should see your phone ID and device. Next, turn the phone completely OFF. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY). Connect device to PC via USB cable. Then open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your recovery image file is in the Minimal ADB directory or it won't work; the type "fastboot boot thenameofyourrecoveryfile.img". This should boot you to the TWRP.
4. Once booted into TWRP, tap Wipe, then Advanced Wipe; check Dalvik/ART Cache, System, Data, Cache ONLY, then swipe to wipe. Just to be on the paranoid safe side, click back (triangle pointing left) to the main menu, go back to Wipe, Tap Format Data, Type yes and wipe. Click back to main menu after - do NOT reboot.
5. Click Install; install A8M'S-METROPCS-XT1765-PERRY-STOCKROM-PROJECT-04142018.zip. Afterwards, go back to main menu.
6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
7. Click Install; install open_gapps-arm-7.1-nano-20180331.zip. Note: This takes 3-5 minutes. You will see a warning that StockRom Gapps is installed. That's okay - ignore it, its necessary. Click back to main menu after.
8. Click Install; install no-verity-opt-encrypt.zip. Click back to main menu after.
If you don't want root, hit Reboot, then System. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed. Congratulations, welcome to your brand spanky new stock rom flashed phone.
If you do want root don't reboot, keep reading the next section.
Part II - Rooting:
Okay, this section might be challenging, but hopefully this will ease your nerves as you walk through the ever so daunting task of rooting. It has some of the same challenges that rooting the .xml had (refer to my "The Complete Noob Guide to Rooting MetroPCS XT1765 Qualcomm Variant" guide for such challenges). This might feel totally redundant, and to a lesser degree it is, but it will pay off in the end. And remember, if at first you don't succeed, wipe clean and flash again!
9. In TWRP, click Install; install Magisk-v14.0.zip FIRST - very important. Do not install supersuser first. Afterwards, click back to the main menu.
10. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
4. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
5. Disable Updates. This thing will race you to that. On initial launch, you should not have the wifi connected. As soon as you put your Sim card back in, IMMEDIATELY cut off your data until you disable updates.
Bonus Round - In Case Of Error -1 Issues:
Hopefully, the first two parts got you straight, and you're playing on your stock rom now. However, this variant is challenging, and getting root could be a pain in the android ass. If you installed either superuser.zip or magisk.zip and got an Error -1 for either or both, this section is for you.
Unfortunately, the boot.img getting corrupted probably is the main culprit. Don't freak, it was a problem with the original root method on this variant straight out the box. Also, if you have been flashing/re-flashing a lot, sometimes it just makes it funky. But its a fix with a little patience.
1. Turn your phone on, and let it boot.
2. Go into your phone settings, and activate developer options (you know, hitting the build number 7x).
3. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below). Very Important. Also uncheck "Verify Apps Over USB", but only if you having probs with fastboot in ADB. You can recheck it later.
4. Make sure you've enabled Allow installation of apps from Unknown Sources (its in the Security section of Settings).
5. Turn your phone completely off.
6. Plug your phone via USB cable into the computer.
7. Press Volume Down and Power to boot into fastboot mode.
8. Open up Minimal ADB and Fastboot command prompt on the PC (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory (same place you see recovery.img that boots/installs TWRP) or it won't work. Download it from the files list above.
9. In Minimal ADB command prompt type "fastboot erase boot. " It might say permission denied, and that's okay. Keep going.
10. In Minimal ADB command prompt type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And no, you don't have to reflash the stock rom after this either.
11. Reboot into recovery - make sure you select READ ONLY when it launches.
12. 6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
13. Click Install; install Magisk-v14.0.zip FIRST - very important. Afterwards, click back to the main menu. It should be successful.
14. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
15. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
If you're still having problems after flashing the boot.img, start all the way over from the beginning wiping everything clean. That should correct the problem and let you install without trouble or needing to flash the boot.img again.
Bonus Round - In Case Of No Root After Root Issues:
As soon as the little bugger tried to force the update via my data when I stuck my Sim Card in, it messed with my root, even catching and cutting it off as quick as I could and not doing a full update. When I rebooted, I lost root. This has happened off and on every other flash - so your root may stick or it may not. If it doesn't, either you can 1. wait for a better method, 2. reflash, 3. live without it for now. This is still kind of experimental for me, as I had to wipe and reset to get root back. Still trying to figure out a more perm way for this like on the .xml.
Enjoy Everyone - I'm learning, taking it one android day at a time but I'll help when I can. It's an awesome day to be a nerd!
Sincere Thanks:
The devs that created a method of root for various variant E4's that sent me on this journey, I love you guys!
The devs behind Magisk, Superuser, and No-Verity!
@squid2 for the TWRP recovery that helped A BUNCH!
@ASSAYYED for the beautiful kitchen that forced me to keep learning.
@Al936 for the beautiful tutorial that helped me figure out how to extract the files needed in the journey.
@MotoJunkie01 for giving me the inspiration to try it on my own.
@madbat99 for the small, but powerful words of encouragement.
And to the community at large that let me ask questions to the point of getting on their nerves. Thank you!!!
[REPOST][ROM][PERRY][MetroPCS.XT1765][STOCK] A8M'S XT1765 STOCK ROM April 14th, 2018
Reserved.
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
ilanor said:
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
Click to expand...
Click to collapse
Everything is stock. Just as it was on a complete fresh out the box setup. You will find all the metropcs apps there.
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Moto_E4_xt1765_metroPcs said:
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Click to expand...
Click to collapse
you install ADB and fastboot on your computer then open the folder that contains those. Put the boot image in that folder
Pretty sure this guy that is extremely outdated though
this flashed fine and magisk and superuser flashed fine booted actually a little faster than normal. I don ' know how but it say no service though and it throws an error "error occured could not search" or something similar . how can i get my radios back
Had to do a factory reset, and all was good. Using LSposed with Magisk and reinstalled several mondules. Upon reboot, the screen hangs at "Pixel is starting." So I rebooted into safe mode, knowing the Magisk modules would be disabled, but the same thing happens, even in safe mode. Booted again. I can access all my settings, and adb works fine. But I'm clueless as to what I should do, even with adb and settings access.
Will appreciate any help. Everything is backed up, I'm just trying to avoid the nuisance of having to factory reset again and all that entails.
Thanks.
You can try Official Google Android Flash Tool and uncheck the wipe data option (and don't force flash all partitions, either, which will also wipe), and don't forget to uncheck the option to re-lock the bootloader.
That official site has solved many weird issues where even manually flashing the full factory image hasn't solved the problem. Good luck, let us know if that's what you do and how it goes.
my old go-to for boot issues was last_kmsg. I recentlky found abou about boot-chart, which logs what happens during boot, and may log an error for you. You will have to run this in recovery if yopu are in a non-booting state
To enable it:
Code:
mkdir -p /data/bootchart;
touch /data/bootchart/enabled;
try a reboot, which fails. Reboot to recovery and retrieve the logs
init/grab-bootchart.sh - platform/system/core - Git at Google
I havent had to use it "in anger" yet, but it will be my tool of choice.