Database Develop

[Q] Downgraded??

I was on Android 5.0 lollipop when something glitched and my phone wouldn't get out of bootloader mode, so i flash stock android. When it then finished and went back to 4.4.4 i tried flashed the factory images again to lock the bootloader, but it wouldn't let me because it kept saying "downgrading" or something along those lines. Now my phones sysetem version is 21.11.17.titan_retuaws.retuaws.en.Us which is the one of 5.0 when im clearly on 4.4.4. I am currently rooted with a custom recovery, any ideas on how i could possibly get back to android L?

ErikG1999 said:
any ideas on how i could possibly get back to android L?
Click to expand...
Click to collapse
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot

doppelhelix said:
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot
Click to expand...
Click to collapse
the A method doesn't work, ive tired it before. It doesn't let me relock the bootloader because it thinks im downgraded the system. I think ill try the B method. In order to instal the custom rom would i have to use a custom recovery? how would i go about doing it (P.S. XT1064 rooted with TWRP)

ErikG1999 said:
the A method doesn't work, ive tired it before. It doesn't let me relock the bootloader because it thinks im downgraded the system. I think ill try the B method. In order to instal the custom rom would i have to use a custom recovery? how would i go about doing it (P.S. XT1064 rooted with TWRP)
Click to expand...
Click to collapse
currently I BELIEVE if you have flashed MOTOBOOT.img (bootloader) from a 5.0 version you can not go back to a 4.4.4 version, but you can still run a 4.4.4 rom on a 5.0 bootloader. a locked / unlocked bootloader should not stop OTA updates. Having the wrong recovery will stop OTA installing. and mismatched bootloader / recoveries MAY cause problems.
to flash titan prime rom use TWRP (make backup 1st) place zipped tp-rom on sdcard and gapps.zip and following instruction in the rom thread
So, A method (blur versions) will always fail if you have TWRP installed, you need stock recovery that matches your rom on phone now , the 1st from moto firmware should work via mfastboot method.

ErikG1999 said:
It doesn't let me relock the bootloader
Click to expand...
Click to collapse
Why would you want to do that? There's absolutely no reason for relock.

help!!!
doppelhelix said:
Two possible ways:
A. the stock method
Download these files:
RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip from motofirmware.com
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0)
Blur_Version.22.21.16.titan_retuaws.retuaws.en.US.zip (Lollipop 5.0.1) (both from this forum)
install the first via fastboot, (ignore errors given by gpt.bin and motoboot.img), reboot
install the second via stock-recovery, reboot
install the third via stock-recovery, reboot
B.
flash The Titan Prime ROM, reboot
Click to expand...
Click to collapse
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!

ErikG1999 said:
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!
Click to expand...
Click to collapse
PM me, if you have some time, so we can go through the whole process step by step without overflooding this thread

ErikG1999 said:
i did what you said and flashed the firmware and know my phone wont boot up. i can access the bootloader and twrp, please help!
Click to expand...
Click to collapse
If you flashed the firmware correctly you should not have twrp.

Android The Greek said:
If you flashed the firmware correctly you should not have twrp.
Click to expand...
Click to collapse
ya i dun goofed, i fixed it now its all good

[LOLLIPOP 5.1][STOCK] Cherry Mobile One H940 Official Links

Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.

do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks

Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.

intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you

Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/

OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.

erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.

intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.

erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.

intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance

Sir
can you capture ota for myphone uno

gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.

still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM

Working internal detect for pc and file ?

marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.

intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM

marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.

success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man

Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!

OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.

[recovery][v500] CWM 6.0.5.1 (Open Bump Edition)

ClockworkMod Recovery (6.0.5.1) Open Bump Edition for LG G Pad 8.3 v500. This custom recovery installation package is for v500 models only. Built from source on 2014-12-13 by Jenkins. This version of CWM 6.0.5.1 has been "bumped" so that loki tool is not required.
Installation: Flash zip file with any custom recovery and reboot into updated CWM recovery.
v500-CWM-6.0.5.1-20141213-recovery-bumped-signed.zip
MD5: 8c8593fc0fb8039949c0f06d48d97e4f
Note: An advantage to using the official CWM recovery with CM 11 is that the CWM recovery can be automatically updated with the CM Update tool, if enabled in the CM 11 developer options.
Manual Installation (first time installing custom recovery):
1) Gain root permission (ie; with Stumproot) and install SuperSU and Busybox.
2) Install Terminal Emulator or use ADB for opening up a shell (this example is using ADB).
Note: If using Terminal Emulator, make sure root access is given via SuperSU.
3) Download CWM installation zip file from the link above and manually extract it.
4) Copy recovery.img (contained in the CWM installation zip file from step #3) to /data/local/tmp on your LG G Pad 8.3 v500 tablet with either ADB or a root explorer application and install with "dd" command.
Code:
adb push recovery.img /data/local/tmp/
adb shell
su
cd /data/local/tmp
ls recovery.img
dd if=recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery

is this the touch version?

This is the latest official swipe version. It's not full touch.

Deltadroid said:
This is the latest official swipe version. It's not full touch.
Click to expand...
Click to collapse
are there any plans to port the touch version to the g pad?

Not at the moment. This recovery was taken from the official nightly builds. I did not personally build it. I have only "bumped" the image and packaged it.

only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?

auleu said:
only bumped roms or kernels works with bumped recoverys? what happens if i flash a normal rom?
Click to expand...
Click to collapse
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).

Deltadroid said:
Any rom or kernel can be installed with a bumped recovery. Although, some ROMs require that your aboot partition is from 4.2.2 so that loki will work so that the kernel can be installed (which has nothing to do with the recovery).
Click to expand...
Click to collapse
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?

Phenom2 said:
Installed this recovery following the instructions :
adb reboot recovery : my tablet didn't reboot to recovery but to system
then I boot into recovery using Titanium Backup (there's an option to boot into recovery in the menu)
I tried to install latest official CM12 nightly : error
tried with latest AOSP 5.1 too, same error
So I tried to toggle Loki in the CWM settings , same results.
Now I can't boot into system nor recovery : "Security Error"
Looks like I'm good to flash once again the stock rom...
Any tips to be able to install CM12 or AOSP 5.1 ?
Click to expand...
Click to collapse
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.

Deltadroid said:
When you typed "adb reboot recovery", make sure you unplug the usb cable or it will not reboot into recovery.. this occurs with all versions of CWM.
When you install a ROM, make sure that your aboot partition is loki exploitable (from 4.2.2) or it will not be able to install the kernel. Most ROMs still use the loki method to install the kernel, which still requires the older aboot.
Click to expand...
Click to collapse
Ok, so I should flash the first stock rom before trying to install a recovery right ?
- Flash 1st stock rom
- Get root (I use towelroot)
- Install recovery with cmd
- Boot recovery and flash rom + gapps
Right ? (edit : OK, I managed to install AOSP 5.1 with theses instructions coming from stock V50010B)
I understood that there's 2 major exploit, loki and bumb.
4.4 = bumb only
4.2.2 = both ?
Isn't your rom (cm12) bumb enabled ? (edit : "Currently, all official CyanogenMod ROMs use loki tool to install the kernel on the LG G Pad 8.3 v500" )

The current official nightly still uses loki so it still requires the 4.2.2 aboot. There is another thread about switching boot loaders which will also downgrade aboot with flashable zip. If the rom you are installing is pre bumped, then an aboot from 4.4.2 will work, but i still recommend downgrading aboot to 4.2.2 version for better compatibility with older roms and official cm.

so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader

auleu said:
so i installed the recovery, after i push the power button in the factory reset menu to load the recovery, the lg logo screen is very dark just like when youre in download mode, is this normal? i'm on kitkat bootloader
Click to expand...
Click to collapse
Yes, that is normal.

Deltadroid said:
Yes, that is normal.
Click to expand...
Click to collapse
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?

auleu said:
and if i install a rom and at the end says something like not loki exploitable does this mean that the rom is not bumped?
Click to expand...
Click to collapse
Yes

Deltadroid said:
Yes
Click to expand...
Click to collapse
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?

auleu said:
if i enable loki support in cwm can i install a non bumped rom ? or what does that setting do?
Click to expand...
Click to collapse
Enabling loki support in cwm is deprecated and wont do anything. The problem is that you need to downgrade your aboot so that the Rom you are installing can execute it's scripts properly. There is a thread here that provides flashable zip files to switch bootloaders. You will want to choose the bootloader package with the downgraded aboot if you want to install older ROMs that have not been updated to use bump yet.
http://forum.xda-developers.com/showthread.php?p=52910560

does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'

auleu said:
does cwm have a rom size limit? im trying to sideload the stock lollipop rom with over 1gb size and gives error. failed to write data 'protocol fault (no status)'
Click to expand...
Click to collapse
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260

Deltadroid said:
This recovery is probably better suited for lollipop
http://forum.xda-developers.com/showthread.php?p=61363260
Click to expand...
Click to collapse
i've installed that one, it worked but didnt tried sideloading it, instead i copied it to sdcard. also its strange that cwm dosent have mount sdcard option

how update from 7.0 to 7.1 march update without losing data ?

hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you

agel1 said:
can somebody tell me how to do it without losing data or root ?
Click to expand...
Click to collapse
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.

NLBeev said:
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
Click to expand...
Click to collapse
sorry dont understand
Im already rooted and with twrp installed

agel1 said:
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
Click to expand...
Click to collapse
Download the factory image of the version you desire to end up on.
Unzip it, then unzip the folder contained in it, then in a terminal/cmd run:
Code:
fastboot flash bootloader bootloader-shamu-*.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-*.img
fastboot reboot-bootloader
cd shamu-*
fastboot flash boot boot.img
fastboot flash system system.img
Now, you said you wanted to retain root too, if that isn't the case, just run:
Code:
fastboot reboot
If you do still want root, download TWRP, cd to the Downloads directory, then either run:
Code:
fastboot boot twrp-3.1.0-0-shamu.img
if you want to keep the stock recovery
OR
Code:
fastboot flash recovery twrp-3.1.0-0-shamu.img
if you want to keep TWRP.
Now that you're on TWRP, just use file explorer to drag and drop the newest SuperSU zip (at the time of writing this, 2.79 is the latest stable, and SR3-2.79 is the latest beta) if you're on Windows or Linux, or use
Code:
adb push [I]nameofsupersu[/I].zip /sdcard/
.
Now reboot.
Have fun! It may take up to 15 minutes to boot (for dex-opting, and encrypting if you were decrypted and decided to re-encrypt), so don't interrupt that first boot process, just let it go. It will also need to "Optimize" all installed apps, so that could take a long while as well.

agel1 said:
sorry dont understand
Im already rooted and with twrp installed
Click to expand...
Click to collapse
Bad reading by me. Sorry.
Nevertheless you can upgrade to 7.1.1 by flashing the lite ROM of Danvdh.
There is a possibility that dirty flashing will cause reboot issue. Backup first and update your bootloader and radio before flashing the ROM.
There's a thread with flashable zips with latest bootloader/radio.
https://forum.xda-developers.com/showthread.php?p=59728002/
Latest TWRP: https://eu.dl.twrp.me/shamu

Why is everyone recommending the difficult ways???
Just download the OTA image from google and sideload it from your PC.
You don't even need TWRP, unloaded bootloader or root access to do it and you won't loose any data or settings.
More info and OTA images at https://developers.google.com/android/ota

[GUIDE] How To Backup Your OWN Firmware on any PRA

This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)

** Note **
just follow the steps and will have a fully backup, I tested 100 times while making roms for this device!
regards

One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..

Dr.TheMaster said:
One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..
Click to expand...
Click to collapse
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.

haky 86 said:
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.
Click to expand...
Click to collapse
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?

Dr.TheMaster said:
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?
Click to expand...
Click to collapse
if you want, you can keep twrp even after rooting.

Hi Haky 86, for my HUAWEI P8 lite 2017, the build number is PRA-LA1C185B167.
I found firmware PRA-LA1C185B176 at below links, do you think they are trustworthy - will they work on my phone ?
forums.easy-firmware.com/showthread.php?182653-PRA-LA1C185B176-zip
easy-firmware.com/home/browse/file-info/id/99327/

haky 86 said:
This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)
Click to expand...
Click to collapse
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?

Hinatasan said:
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?
Click to expand...
Click to collapse
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.

haky 86 said:
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.
Click to expand...
Click to collapse
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468

Hinatasan said:
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468
Click to expand...
Click to collapse
Actually I won't fix nothing, I'm working on emui 8.x source to make newer roms (non treble one)

HELP ME
Good evening need some help to back up the firmware of a Huawei B310s Imei: 869242023527367
serial number: F5S8W17901002756
Thank you