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.....
Related
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?
bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Simone98RC said:
DO NOT encrypt via custom roms: it's cause of troubles and compatibility issues, especially when returning to OxygenOS.
So:
1) Put device in bootloader mode, plug it to computer, type fastboot format userdata via ADB terminal.
2) Go in TWRP and wipe all the partitions (be sure to have /cache formatted in ext4, otherwise change its filesystem):
3) Always from TWRP, flash latest OOS firmware (4.1.6 or OB19);
3) Reboot and configure setup with your PIN required at bootup;
4) After completing wizard, reboot in TWRP;
5) Now you can wipe anything and flash your rom.
Now device should require your PIN even at first boot of DU.
Ps until doing another fastboot format userdata, device will keep encryption.
Click to expand...
Click to collapse
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
nikexv2 said:
Thanks for the answer, do you know why custom rom encryption doesnt work ? I used to to this on my old s5 and it worked perfectly
Click to expand...
Click to collapse
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Xceeder said:
Maybe if you give his post a thumbs up he might continue helping you out , I mean that's the least you could do ......
Click to expand...
Click to collapse
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Come on, do not vent on XDA, do not make useless quarrels ?
@nikexv2 sorry, but technically speaking, I don't know the reason of problematic encryption on custom roms.
Just enable encryption with official firmware and there's no other compatibility issue.
Encryption still remains when you full wipe device via recovery.
Have a good day.
nikexv2 said:
If members had to wait for thumbs up before they answer to someone's post then they wouldn't answer most of them.
What kind of **** philosophy is this, i hope for you that's not your way of thinking everyday.
And even, that's none of your business, maybe i forgot to like his post ?
Click to expand...
Click to collapse
It works like this - you ask for help and if someone gives you good advice or helps you out in any way then a quick thumbs up is appreciated , it's just courtesy but anyway I hope you get your phone sorted out ...
nikexv2 said:
Hello,
Whenever i encrypt my phone on DU, when i set the lock screen Password it asks me if i want the phone to ask it to be able to boot, but then, the phone refuses to boot and says that the Password is wrong.
But when i boot into twrp the Password works and i can decrypt the data partition.
I already had the issue but with the phone accepting the boot pin but twrp not.
This is on a fresh DU install with previously formated data partition.
Click to expand...
Click to collapse
Not sure what's wrong with your set up but I came from OOS OB19 to DU, wiped userdata to switch data to ext4, flashed DU + beans gapps (recommended for DU) then booted up, encrypted my phone via Settings > Security and set ask pin on booting device, same pin has worked on all ROMs, even tried some OOS based ones like Freedom OS CE, now on Omni + open gapps, I'm using blu spark latest recovery.
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
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
-> Boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously, including everything in storage, photos, documents, everything).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push xiaomi.eu_multi_MIMix3_V10.0.12.0.PEECNFH_v10-9.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Note for AMD Ryzen machines: There appears to be a USB2.0 bug associated with Ryzen CPUs which prevent the fastboot flash from working. If the flashing process starts then fails, try a different machine.
ROM File and TWRP not listed
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
Yes they are, you need to look again
Mackay53 said:
Yes they are, you need to look again
Click to expand...
Click to collapse
Thanks, found them.
fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
They're right below the ROM table.
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Lumpka21 said:
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Click to expand...
Click to collapse
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
invisiblewave said:
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
Click to expand...
Click to collapse
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Mackay53 said:
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Click to expand...
Click to collapse
Ok, so once you've flashed TWRP, there are two recoveries on the device and booting into the stock OS changes the bootloader to boot to the MIUI recovery?
Hello, i found this very useful. thank you
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Alexdruso said:
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Click to expand...
Click to collapse
You don't need ADB for flashing twrp so having usb debugging on is irrelevant.
Flash twrp In fastboot and once it's done and without giving any more commands just hold power and volume up. Eventually it will boot into twrp.
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
PWn3R said:
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
Click to expand...
Click to collapse
You never ever need to wipe the System so it won't be that, wipe would be recommended if you can do it
Which version of twrp should I use?
Herrick1209 said:
Which version of twrp should I use?
Click to expand...
Click to collapse
The only one there is for the MM3.
invisiblewave said:
The only one there is for the MM3.
Click to expand...
Click to collapse
I couldn't find it on the twrp website??
Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
You can't find one for the Mix 2s there either.
You can find one for the Mix1 there, but it is non- functional.
. . .
DYODD
Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
That's why I posted the link in the OP.
Thanks, does this apply to the Xiaomi MI Mix 3 Forbidden City Edition?
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .
Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?
I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.