Database Develop

Better Emergency Recovery [Dual Recovery]

Better Emergency Recovery Project​
This project aims you to get a better "Emergency Recovery" than Huawei's own version since it does really not work as intended for everyone.
I've tested to get "Cyanogen Mod" Recovery to boot and it worked, but since i use M it didn't work quite to well. so i'll give you TWRP 3.0.2.0 version by xepeleato.
Why is this needed?
Well we all know TWRP isn't always doing it's thing when it tries to format the system and then Stock Huawei Emegency Recovery will pop up. With This Package it'll replace the stock recovery2 and give you TWRP instead, so you can easily fix your system to boot up without flashing the need of a pc to regain access to stock recovery(1).
Do notice that it'll take some time for Recovery2 to boot up. (while CM) recovery took faster to boot it won't stop TWRP from working.
It's stable and tested that it works, instead of using fastboot to recoveph your device you can now do it from the phone itself.
Download custom recovery2 http://forum.xda-developers.com/devdb/project/dl/?id=20716
Download NOTE: this is not a full system image. It does not contain ANY files! It is just to restore your system partition. Since it's faster than formating. http://forum.xda-developers.com/devdb/project/dl/?id=20717
Installation instructions:
Download CustomEmergencyRecovery2.zip
If downloading from computer push files to sdcard
Flash the zip.
If you don't belive me. Backup your system. Start formating system when it's formating reboot the device. It'll end up in twrp recovery. It'll take max 1 minute. Enjoy
XDA:DevDB Information
Better Emergency Recovery [Dual Recovery], Tool/Utility for the Huawei P8lite
Credits: @XePeleato for latest TWRP 3.0.2.0 and his continuing contribution for our device.
Credits: Me for playing around with the device
Contributors
LastStandingDroid, Xepeleato
Version Information
Status: Stable
Current Stable Version: 3.0.2.0
Stable Release Date: 2016-10-01
Created 2016-10-01
Last Updated 2016-10-01

Feature plans.
UI overhaul.
Maybe more I don't promise anything. .

Where is the download?

Vinnipinni said:
Where is the download?
Click to expand...
Click to collapse
Look in download section
Updated first post. So tapatalk users can navigate to download section
Sent from my ALE-L21 using Tapatalk

Why would anyone format system just to open emergency recovery 2? There is another way to open it. Boot into bootloader and then press volume up button this will open recovery 2.
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
Suleiman01 said:
Why would anyone format system just to open emergency recovery 2? There is another way to open it. Boot into bootloader and then press volume up button this will open recovery 2.
Click to expand...
Click to collapse
By the way has anyone tried this on Official firmware ?

Suleiman01 said:
Why would anyone format system just to open emergency recovery 2? There is another way to open it. Boot into bootloader and then press volume up button this will open recovery 2.
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
By the way has anyone tried this on Official firmware ?
Click to expand...
Click to collapse
from stock eRecovery you wont be able to recover your system,that why @LastStandingDroid he create this,in some case when you want to flash a custom rom is need to format system

cristi.blidariu said:
from stock eRecovery you wont be able to recover your system,that why @ LastStandingDroid he create this,in some case when you want to flash a custom rom is need to format system
Click to expand...
Click to collapse
Yes I know that but in order to check whether it's working you don't need to format system. Just go to bootloader and then press volume up button. This will open Erecovery (twrp in case you have flashed zip file given in this thread).
---------- Post added at 07:30 PM ---------- Previous post was at 07:22 PM ----------
Working flawlessly on B560. Thanks :good: @LastStandingDroid

Suleiman01 said:
Why would anyone format system just to open emergency recovery 2? There is another way to open it. Boot into bootloader and then press volume up button this will open recovery 2.
---------- Post added at 07:08 PM ---------- Previous post was at 07:04 PM ----------
By the way has anyone tried this on Official firmware ?
Click to expand...
Click to collapse
Man because I'm rather new to Huawei devices. It's my first Huawei device and if Huawei keeps having the same signal strength I have with this phone ill stick with Huawei. I know development is bad for kirinsoc (which usually doesn't bother me at all)since in my case I rather have a stock modified system which I can rely on. (even on my previous snapdragon devices such as G3 and s4) i always used stock firmware even if a stable cm was released. As long as I can root it and back up my system. Get bloat removed I'm most likely happy. But I'll learn about Huawei soon. Also I didn't know you could boot into emergency recovery from bootloader but thanks for telling.
cristi.blidariu said:
from stock eRecovery you wont be able to recover your system,that why @LastStandingDroid he create this,in some case when you want to flash a custom rom is need to format system
Click to expand...
Click to collapse
Well to be honest. You most likely just need to remove all system files. And -rm rf option works well in that case.
Suleiman01 said:
Yes I know that but in order to check whether it's working you don't need to format system. Just go to bootloader and then press volume up button. This will open Erecovery (twrp in case you have flashed zip file given in this thread).
---------- Post added at 07:30 PM ---------- Previous post was at 07:22 PM ----------
Working flawlessly on B560. Thanks :good: @LastStandingDroid
Click to expand...
Click to collapse
Sorry that was the only way I knew [emoji14]
And yes I tested it on "stock" which has my own modification.
Also I created this because if I wouldn't have a pc nearby and i mess up the system. I could easily restore it. Unless I don't have the restore image system file (which is just a empty system.img) which is used to fix the system in case it is being broken. I could release a stock flash able system (which I already have) but I got no plans for it tbh. Could be good though to have.
Sent from my ALE-L21 using Tapatalk

LastStandingDroid said:
Look in download section
Updated first post. So tapatalk users can navigate to download section
Click to expand...
Click to collapse
Thanks.

I'm going to see if we can make it possible to get a similar method (as stock emui recovery) so we can download a system firmware trough wifi it is a long shot. But it's most likely possible (but will take time) and there's actually no progress yet. It's an idea. But we'll hope it could be possible.
Sent from my ALE-L21 using Tapatalk

LastStandingDroid said:
I'm going to see if we can make it possible to get a similar method (as stock emui recovery) so we can download a system firmware trough wifi it is a long shot. But it's most likely possible (but will take time) and there's actually progress yet. It's an idea. But for now it is just an idea.
Sent from my ALE-L21 using Tapatalk
Click to expand...
Click to collapse
That is a good idea [emoji2]
Sent from my ALE-L21 using XDA-Developers mobile app

So I'm going to completely re install my mac.
My windows setup will be removed (thank gosh) it really become a pain since updating from w7.
Also my os x says good bye yay. No more issues while trying to build stuff. Unless I set it up wrong
Sent from my ALE-L21 using Tapatalk

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader

Tutorial(downgrade8.1.0=>7.1.1)use nougat stok/custom-roms on Oreo BC-12 bootloader
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!

reserved

Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
vaserbanix said:
This tutorial is for the users wich are not satisfied by Oreo 8.1.1 rom
Also can be used by users wich changed the touchscreen from some reazons
and on Oreo 8.1.1 this new touchscreen not work​
First got to Settings/System/Developer option and chec OEM-unlockin to be ENABLED!
for flashing twrp-recovery may be need to unlock the bootloader by code but it should work only with OEM-unlocking enabled
Downgrading with FASTBOOT!
1) Charge youre phone to at least 50-70%, better is 100%
2) Download the FILES necessary for downgrading
3) Reboot the phone in bootloader and connect to the pc
4) Opend the terminal and write "fastboot" or "mfastboot" depends by your instaled fastboot
5) Copy/Paste in terminal the lines writed in "fastboot-mfastboot.txt" atached to files
or write them one by one and press ENTER
WAIT 'till it finish
6) In bootloader screen, from buttons vol-up & vol-down navigate and set to "reboot recovery" and press Power
Phone should boot in TWRP-recovery!
Now you have to install a custom-rom or a stok-rom TWRP flashable with Install option
""for this use the instruction to install posted by the developer of each rom""
Also you can RESTORE an older 7.1.1 backup made before update to OREO
Reboot and enjoy by nougat-7.1.1 rom on oreo-8.1.0 bootloader
Downgrading with TWRP
Files to be flashed with TWRP for the users wich have olready the TWRP-recovery instaled!
1) Download the files
2) Copy the zip archive on the sdcard
3) Reboot the phone in TWRP-recovery
4) Search and install the zip
5) Install nougat 7.1.1 rom or restore an older backup made before update to OREO
Enjoy!
Click to expand...
Click to collapse
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?

ShattrdChain said:
Thank You very much
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
Also, can I flash Stock Nougat (using fastboot) after this? And is there any chance of my device being hardbricked?
Click to expand...
Click to collapse
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk

vaserbanix said:
No! you cant flash a full nougat rom with fastboot.
Bootloader cant be downgraded!
for hardbricked phones you have first to boot it using the sdcard img.
then when you get bootloader working without sdcard, can use this tutorial
Sent from my Moto G (5S) using Tapatalk
Click to expand...
Click to collapse
Oh ok. Thank You very much

I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix

What are the problems with 8.1? I'm still on Android 7 (RETEU)

Argon007 said:
What are the problems with 8.1? I'm still on Android 7 (RETEU)
Click to expand...
Click to collapse
1. Oreo Battery drains considerably faster than 7.1. (But charges faster too)
2. Fingerprint unlocks slower than 7.1
3. Lags slightly when doing intensive tasks.

Now we need a maintainer for (a) Nougat rom(s)..

Ænimal said:
Now we need a maintainer for (a) Nougat rom(s)..
Click to expand...
Click to collapse
YES indeed!

Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.

mysticauls said:
Im in 8.1.1 stock rom. Can i install a custom 7.1.2 (ViperOS) with this method? Tks.
Click to expand...
Click to collapse
lineage 14.1 work so it should work ViperOS too!
to be sure ask in ViperOS thread.
Thankyou!

Hello!
Do you lose biometrics by installing twrp?

vaserbanix said:
YES indeed!
Click to expand...
Click to collapse
LOS14.1 has been updated:
NEW BUILD: https://www.androidfilehost.com/?fid...63190603848665
Change log: November 18 Security Update
NOTE: Like so many other users, I too updated my device with OREO and stuck with that. I haven't tried downgrading it because I don't want to end up with a hard-bricked device once again. Point here is the new build is not tested. So please take a TWRP backup before using this build. Don't forget to post me even if works fine.
Thanks,
KS
Click to expand...
Click to collapse
EDIT: When I try to quote properly I get logged out for some reason, so see this thread obviously (and don't forget to thank @kalyansundhar ):
https://forum.xda-developers.com/moto-g5s/development/rom-lineageos-14-1-t3727918

Fantastic tutorial, vaserbanix. Thank you!
Does anybody know where can I get a nougat stock rom TWRP flashable? There is a thread with stock roms but all of them are only flashable via Fastboot...
I would like to get this in particular: [MONTANA_NPP26.102-49-14]
---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------
ShattrdChain said:
I successfully rolled back to 7.1 using this method. No errors or issues. Everything worked flawlessly. A big thank you @vaserbanix
Click to expand...
Click to collapse
Thank you so much for your feedback, ShattrdChain! :good:
May I know what rom did you use for flashing with this method?
And do you know if bootloader needs to be unlocked in order to downgrade with this guide?

TWRP method doesn't work (bootloop), pls fix or delete.

FanderWasTaken said:
TWRP method doesn't work (bootloop), pls fix or delete.
Click to expand...
Click to collapse
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!

vaserbanix said:
i understand it work!
just chek the twrp version!
is posible the twrp to dont read some partitons.
this can make the differences betwen work or not
ask eric rutgers ( @GoldeneyeS2), he instaled sucesful that downgrade.zip
Thankyou!
Click to expand...
Click to collapse
Its works great.
You can also use fastboot to downgrade!

can the downgrade be done without the bootloader unlocked?

the methods don't work for xt1799-2!

FIXED | Failed login to samsung account because device is rooted

can anyone help? when my M20 is not rooted, i can log in to samsung account. but when my M20 is rooted it can't log in. Over and over again.
Is that because M20 is rooted?
In others case, i cant unlocuk lockscreen with pattern when device is rooted.
anyone experienced like that?
Device : Samsung M205GDXU1BSE8
OS : PIE
Its example my case
Fixed
https://forum.xda-developers.com/galaxy-m20/help/guide-how-to-root-m20-t3951938
Fixed
How to (Step by step)
Fixed
https://forum.xda-developers.com/galaxy-m20/help/how-to-fiks-unlock-screen-samsung-m20-t4014419

hi how did you manage to boot into stock rom?
Would you mind giving short guide.

Niraj.njk57 said:
hi how did you manage to boot into stock rom?
Would you mind giving short guide.
Click to expand...
Click to collapse
do you mean how M20 to install android pie?
Sent from my [device_name] using XDA-Developers Legacy app

nodz13 said:
do you mean how M20 to install android pie?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Nah roger that now I too am facing the problem. It just says processing failed. Did you manage to solve it? Magisk Hide didn't help.

How to root m20 pie ???
---------- Post added at 02:34 AM ---------- Previous post was at 02:33 AM ----------
nodz13 said:
can anyone help? when my M20 is not rooted, i can log in to samsung account. but when my M20 is rooted it can't log in. Over and over again.
Is that because M20 is rooted?
In others case, i cant unlocuk lockscreen with pattern when device is rooted.
anyone experienced like that?
Device : Samsung M205GDXU1BSE8
OS : PIE
Its example my case
https://youtu.be/VuQzfj4roYQ
Click to expand...
Click to collapse
How to root m20 pie????

nvthd94 said:
How to root m20 pie ???
---------- Post added at 02:34 AM ---------- Previous post was at 02:33 AM ----------
How to root m20 pie????
Click to expand...
Click to collapse
OEM unlocking-------twrp flashing via Odin------boot into two ----decrypt password appears --- cancel ---- wipe----- format data----- now install the zips RMM, Magisk,noverity--- reboot into recovery--- wipe --- advance wipe --- data--- change or repair file system --- chose FAT ----swipe--- back--- chose the file system that was there before you changed to FAT.

Rooted.android said:
OEM unlocking-------twrp flashing via Odin------boot into two ----decrypt password appears --- cancel ---- wipe----- format data----- now install the zips RMM, Magisk,noverity--- reboot into recovery--- wipe --- advance wipe --- data--- change or repair file system --- chose FAT ----swipe--- back--- chose the file system that was there before you changed to FAT.
Click to expand...
Click to collapse
i follow the instructions here
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
. but when installing twrp by odin i boot into recovery it back to stock recovery without twrp.
---------- Post added at 01:52 AM ---------- Previous post was at 01:41 AM ----------
Rooted.android said:
OEM unlocking-------twrp flashing via Odin------boot into two ----decrypt password appears --- cancel ---- wipe----- format data----- now install the zips RMM, Magisk,noverity--- reboot into recovery--- wipe --- advance wipe --- data--- change or repair file system --- chose FAT ----swipe--- back--- chose the file system that was there before you changed to FAT.
Click to expand...
Click to collapse
8.1 I have unlocked it. update 9.0 with odin I don't know if I have a bootloader locked, I immediately twrp without going into developer settings

nvthd94 said:
i follow the instructions here
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
. but when installing twrp by odin i boot into recovery it back to stock recovery without twrp.
Click to expand...
Click to collapse
Does it say that it was successful?
Try disabling auto reboot in Odin
Odin ----options --- untick--- auto reboot
Flash recovery after green tick is shown on Odin
Volume Down + power and as soon as the display goes black Volume Up + Power. You must be fine
---------- Post added at 03:14 AM ---------- Previous post was at 02:52 AM ----------
nvthd94 said:
i follow the instructions here
https://forum.xda-developers.com/galaxy-m20/development/recovery-twrp-3-2-3-galaxy-m20-t3906705
. but when installing twrp by odin i boot into recovery it back to stock recovery without twrp.
---------- Post added at 01:52 AM ---------- Previous post was at 01:41 AM ----------
8.1 I have unlocked it. update 9.0 with odin I don't know if I have a bootloader locked, I immediately twrp without going into developer settings
Click to expand...
Click to collapse
So I guess you need to first boot into pie and turn on OEM unlocking.
If OEM unlocking isn't present in the developer options then you might wait for 7 days or turn off auto update date and time and change date to next month and then unlock the bootloader.

Rooted.android said:
Does it say that it was successful?
Try disabling auto reboot in Odin
Odin ----options --- untick--- auto reboot
Flash recovery after green tick is shown on Odin
Volume Down + power and as soon as the display goes black Volume Up + Power. You must be fine
---------- Post added at 03:14 AM ---------- Previous post was at 02:52 AM ----------
So I guess you need to first boot into pie and turn on OEM unlocking.
If OEM unlocking isn't present in the developer options then you might wait for 7 days or turn off auto update date and time and change date to next month and then unlock the bootloader.
Click to expand...
Click to collapse
Oke . Thank u

any solution for samsung account error processing failed, on pie with root?

Me too.
Edit:
Hey lad still having the problem?
If so check out my thread I haven't experienced any issues with that method.
https://forum.xda-developers.com/showpost.php?p=79965691&postcount=1

Rooted.ndroid said:
Me too.
Edit:
Hey lad still having the problem?
If so check out my thread I haven't experienced any issues with that method.
https://forum.xda-developers.com/showpost.php?p=79965691&postcount=1
Click to expand...
Click to collapse
This metode for oreo or for pie?
Sent from my [device_name] using XDA-Developers Legacy app

nodz13 said:
This metode for oreo or for pie?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
For Pie

Rooted.ndroid said:
For Pie
Click to expand...
Click to collapse
Is it work ?

nodz13 said:
Is it work ?
Click to expand...
Click to collapse
That's the reason there is a guide.
Works flawlessly,well as the stock does but since you're rooted you are the person in control.

SOLVED: Failed login to samsung account because device is rooted
To get rid of samsung account request when device is rooted, you need to freeze system app "Samsung Experience Service". Useful to set lock screen bypassing samsung login. When finished, unfreeze it to avoid the bootloop at next reboot.

Freeze do you mean force stop ?

ReggaHyko said:
Freeze do you mean force stop ?
Click to expand...
Click to collapse
Not force stop, but disable app. I used Link2SD by Bulent Akpinar

Fixed

after Rooting My Phone Internal Storage decreasing 64 gb to 32 gb .
Any Solution for fixing this problem

October update is out - QP1A.190711.148

October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds

chanh2018 said:
October 2019 Release | Q 10 - Q Release 2 - QP1A.190711.148 | Open Market
https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Won't root for me.

you mean magisk not working with this build?

mcdull said:
you mean magisk not working with this build?
Click to expand...
Click to collapse
No, it's not working for ME.
Sent from my PH-1 using XDA Labs

avd said:
Won't root for me.
Click to expand...
Click to collapse
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.

kt-Froggy said:
Were you able to root the previous 10 build? I have the 148 rooted with Magisk canary, same as the previous two builds (just root, no TWRP). Not sure if it makes a difference, but I don't do OTA updates. I always download and flash the OTA image in adb sideload, then flash the patched boot.img in fastboot.
Click to expand...
Click to collapse
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:

JimmyCash030 said:
oh cool, so flashing boot images work with the latest canary of MM?! will do that then this evening as well :fingers-crossed:
Click to expand...
Click to collapse
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.

kt-Froggy said:
Yes, it does work for me. I've always been doing updates like this, on 9 and 10. Download both OTA and the full image, extract boot.img from the full image, patch it with Magisk, then sideload OTA image in adb, reboot, and finally fastboot flash the patched boot.img. Never had a problem. The only thing is that you have to use Magisk canary build with 10; stable or beta doesn't work.
Click to expand...
Click to collapse
yeah worked for me as well with the latest canary MM !!

Magisk 19.4 works just fine on latest 148 build if need be I can upload magisk rooted boot. Img

https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img

allenjthomsen said:
https://www.androidfilehost.com/?fid=1899786940962605417
MD5:49484e6733bba257051eef831eb25689
This is for QP1A.19711.148
Magisk-Patched-Boot.img
Click to expand...
Click to collapse
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
avd said:
getting back to the topic at hand, i flashed this, then twrp on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now i got to plug this in and swap slots to reinstall twrp.
Is possible that magisk and twrp are back to not playing nice to each other again?
(i'll test this out if i get a chance to swap slots)
Click to expand...
Click to collapse
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.

Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.

allenjthomsen said:
Honestly i couldnt tell you i only rooted havent used twrp much yet because of the lack of android 10 custom roms havent seen a need to use it as of yet.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
And any further information on this would be great.
Click to expand...
Click to collapse
pretty much everything for this phone resides in t.me/ESSENTIALPH1DEV

avd said:
getting back to the topic at hand, I flashed this, then TWRP on top of this.
Booted back into recovery.
Reflashed stock boot image.
Now I got to plug this in and swap slots to reinstall TWRP.
Is possible that magisk and twrp are back to not playing nice to each other again?
(I'll test this out if I get a chance to swap slots)
---------- Post added at 11:11 AM ---------- Previous post was at 10:49 AM ----------
now i'm just sitting here looking at the boot animation. Will let it go a little further to see if it starts.
Click to expand...
Click to collapse
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again

rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
Flashing the patched image provided just sits there looking at the boot animation.
I'll play with it tonight.
It's a Sprint phone. Could that be the issue?
Sent from my PH-1 using XDA Labs

I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?

I'm no expert but did this ans it worked:
1. In TWRP recovery (created nandroid and wiped cache)
2. Flashed full update zip from official download link, then TWRP, then wipe cache
3. Reboot system and let it settle
4. Reboot into TRWP and flashed Canary Channel zip file
5. Wipe cache
6. Reboot system
Hope this helps.

jionny said:
I flashed September build like this no problem however when I try and adb the October build I cannot get into recovery, when trying it just boots back into system however I can get into fastboot, any ideas?
Click to expand...
Click to collapse
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
rignfool said:
Thou shalt always flash thy magisk last...
Even if you already had magisk... Flash it again
Click to expand...
Click to collapse
? I always have trouble remembering, not anymore it seems

gavinfernandes2012 said:
Try using the fastboot image (not the OTA the image one) from the essential site.
Download it, remove the "fastboot or something wipe userdata maybe?" line from the flashall.bat script (or from flashall.sh if you're on Mac/Linux)
Then run the flashall.bat or flashall.sh script (again .bat for Win, .sh for the rest)
Should get you working again, albeit without root & twrp
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
I always have trouble remembering, not anymore it seems
Click to expand...
Click to collapse
Are you able to give more precise instructions on fastboot instructions?

jionny said:
Are you able to give more precise instructions on fastboot instructions?
Click to expand...
Click to collapse
Nevermind, got the instructions from essentials site. flashed via fastboot which erased everything had to do a complete setup again

Need stock firmware

I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?

Morricorne said:
I need stock firmware for my Moto G6 XT1925-5 OPSS27.82-87-6
And compatible working and tested TWRP.
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
---------- Post added at 10:29 PM ---------- Previous post was at 10:22 PM ----------
Morricorne said:
I want to reflash this Phone, and get rid bootloader unlock warning.
Any help with that?
Click to expand...
Click to collapse
Try this tool for Windows
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667/
In case of any problems with the tool I could repack a logo.bin with the images that you prefer.

WoKoschekk said:
This is the signed firmware you are looking for:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Official TWRP is available on https://eu.dl.twrp.me/ali/.
You should start with version 3.2.3-0 for your old Oreo build.
Click to expand...
Click to collapse
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for helpi just wanted only remove this Bootloader warning. Cause im buy this moto with already unlocked Bootloader. I have moto g5 too. With unlocked Bootloader. I replaced this warning with black moto logo. And its work. But i cant do the same thing with moto g6

Morricorne said:
Thanks for answear. I test this fw in next week.
Now im on official newest 9.0 for moto g6.
I find place with stock moto g6 firmware. Tried flash oldest 8.0 rom. But fastboot give me cannot downgrade message. Thats why i decided flash newest avaible fw.
I flashed official TWRP recovery for g6 too.
And try flash zip file. But i cant decrypt storage. And i have error with format data. I Just give up with remove Bootloader warning. And use stock 9.0
I dont have enough data package to download this fw. But i try this fw in future. Thanks for help
Click to expand...
Click to collapse
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.

WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
OK thanks i try this in next week

WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Where i can find this disable forceencrypt zip?

Morricorne said:
Where i can find this disable forceencrypt zip?
Click to expand...
Click to collapse
https://github.com/Zackptg5/Disable...Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip

WoKoschekk said:
Do not downgrade from Pie to Oreo! Once Pie is installed there is no way back to Oreo.
TWRP can't decrypt /data on Moto G6. Start TWRP, don't enter a password and hit cancel. Go to "Wipe > Format Data (do not use 'Advanced'!!) > type 'yes' and swipe to confirm".
Next reboot to recovery twice!
Now /data is unencrypted and you must flash the no-verity/disable_forceencrypt.zip in order to stay unencrypted. A reboot to system without that .zip will encrypt your /data again.
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Flashing newest Magisk v20.4 will cause a bootloop. Use v19.3 instead and update Magisk through Magisk Manager when v19.3 is installed without any issues.
Click to expand...
Click to collapse
Cant format data TWRP 3.3.1-0

Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?

Morricorne said:
Flashed decryption zip, magisk system start.
Can enter TWRP again.
Imei work but no Service.
Wtf?
Click to expand...
Click to collapse
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!

WoKoschekk said:
It's not a decryption.zip, it's a forceencryption-disabler.
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
I guess you don't reboot to system after flashing the stock ROM, do you?
One of the last fastboot commands was "fastboot erase userdata". The missing reboot command is the reason for your problem!
Click to expand...
Click to collapse
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin

Morricorne said:
Nope its a not compatible with android 9 version. I found this on xda
https://forum.xda-developers.com/moto-g6/help/service-root-t4004467
**** that. I reflash everything to Stock cause i dont need magisk and root. I only need get rid Bootloader Unlock warning. What i almost finished. Now i look for modified logo.bin
Click to expand...
Click to collapse
Post a picture and I will convert it for you to a logo.bin

WoKoschekk said:
Post a picture and I will convert it for you to a logo.bin
Click to expand...
Click to collapse
I may send you original logo bin
I have this now

A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Morricorne said:
I may send you original logo bin
I have this now
Click to expand...
Click to collapse
Send it

WoKoschekk said:
A resolution of 1080x2160 would be perfect.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
Send it
Click to expand...
Click to collapse
Finished everything flashed. Bootlogo too. And i get ride unknown password when Phone boot too. I dont use any password. Then i dont know whats wrong. Phone ask me everytime when i reboot my device. Now this is gone. No more modding moto g6. Better is stay on stable working stock. Then cant use phone. Man what a day. Time to relax i almost throw this damn phone on the floor.