Develop Bugs

Htc m9 corruted bootloader blue screen,Please HELP

When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?

are you soff?

blue screen error
plz some one help..
htc m9 asia tw
s-on
firmware update to 5.1 sudden mobile reset and now when it on after gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error plz someone help. what to do.

You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.

philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This screen comes every time and reset htc logo and then same blue screen

Maybe try fastboot boot recovery.img and see if that works??

philicibine said:
Maybe try fastboot boot recovery.img and see if that works??
Click to expand...
Click to collapse
FAILED (remote: Not allow when s-on)

mnhs1010 said:
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
Click to expand...
Click to collapse
Is your error solved or are you still stuck with the blue screen as I am also the effected

LineArc said:
Is your error solved or are you still stuck with the blue screen as I am also the effected
Click to expand...
Click to collapse
Still same problem dear blue screen...

mnhs1010 said:
Still same problem dear blue screen...
Click to expand...
Click to collapse
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money

sa3d12 said:
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
Click to expand...
Click to collapse
did your problem solved >>>>>

mnhs1010 said:
did your problem solved >>>>>
Click to expand...
Click to collapse
U mean you solved your problem or you are asking me? ..
Anyway i dont have problems with my device

hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
Click to expand...
Click to collapse
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again

I think you only need to flash the hosd

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
Thanks a lot! You have been avoided a heart attack hehe!

You my friend are a star... I thought my HTC M9 was a brick for sure.
Just to add people, remember do not try and copy through ADB installer (As I did to begin with)... It will not detect your phone... Use the Fastboot application within CMD.
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
does anyone have for m9 verizon ?

@VashSV, I already pressed thanks button but want to write and say thanks to you. You save my phone. Happy new year 2017

Many many many thanks to you!!! I what in this blue screen loop, thanks to your commande list I managed to write .img by .img, you are the boss.

Exact same problem
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
Hello, a bit late but I have the exact same problem with my HTC one M9, can you please help me? I am s-off, unlocked and my phone is T-MOB010 with N7 corrupted firmware :/ pleaseeee

jUST BOOTLOADER SCREEN JUST

NO RECOVERY JUST BLUE SCREEN NO DOWNLOAD MODE JUST BLUE SCREEN
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?

iElvis said:
What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?
Click to expand...
Click to collapse
htc m9 asia tw
s-on
firmware update to 5.1 (2.10.709.1) through RUU mode sudden mobile reset and now when it on after that gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error.
plz someone help. what to do.

We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?

iElvis said:
We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?
Click to expand...
Click to collapse
HTC m9 asia tw it was with firmware 1.40.709.8 then i unlocked bootloader from htcdev.com and used venom rom...
after that i started to update to 5.1 i used following commands,
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
fastboot oem rebootRUU
fastboot flash zip firmware-2.10.709.1.zip
fastboot reboot-bootloader
firmware updated successfully but it stuck at htc logo.
then i flash again firmware.zip sudden mobile reset and this blue screen appears. now when going to RUU, download, recovery mode this blue screen appears.
bootloader screen come while pressing vol + and vol - and power button but can't flash anything. while using command on bootloader screen fastboot gives error FAILED (remote: cannot flash this partition in s-on state)
FAILED (remote: Not allow when s-on)

solve this problem
please reply

how can you solve the problem ???

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
not solved yet....

mnhs1010 said:
not solved yet....
Click to expand...
Click to collapse
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least

clsA said:
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least
Click to expand...
Click to collapse
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...

mnhs1010 said:
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...
Click to expand...
Click to collapse
any solution please tell

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
please u have any solution please tell me.

https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
inset Firmware Packs
"WARNING: HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Because of that it's not recommended (especially to S-ON Users) to relock the Bootloader and flash these files if you want to update to Firmware 2.XX.XXX.X or newer. You better use a RUU and the Update Function in "Settings>About" for that purpose."
Flash stock rom, RUU.exe

finally replacement of mainboard

Possible Solution!
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work

I Did say S-OFF only but thanks for your input - I know a few people who were stuck with S-OFF too.
Arthas92 said:
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work
Click to expand...
Click to collapse

I'm stuck at same problem. Does anyone can help?
Is XTC an option?

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
Hi. I have the same problem which is blue screen on download mode. I tried this method but nothing happen. My HTC is verizon version. I tried to flash all the img from 3.37.605.7 firmware but still the same.

How to re-lock Bootloader of all Potter version

Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader.
DISCLAIMER:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
and I am also not responsible for anything happens as a result of flashing these files
What you need :
1- Motorola drivers :
64-bit
32-bit
2- Minimal ADB and Fastboot:
Minimal ADB and Fastboot
3- Stock Fastboot flashable official firmware.
Here is the donwload of NPNS25.133-37-11 it should be perfect for lock BL for all RETEU users:
Mirror 1 (MEGA)
Mirror 2 (GoogleDrive)
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
Now let's start with the guide.
1- Install Minimal ADB and Fastboot.
2- Extract stock firmware to any folder.
3- Now copy all the stuff that is in Minimal ADB and Fastboot folder in the folder where you extract the firmware.
4- Connect your device in fastboot mode (power off the device and while you press VOL down button insert the USB cable).
5- Open ADB and Fastboot terminal (press SHIFT+right click on the folder where you extract the firmware and select "open command window here").
6- Now type in Fastboot terminal "fastboot devices" (without commas) to be sure that your device is recognized.
7- Type these command one by one on terminal
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
Now your device will restart and your BL will be locked.
Now for be sure reflash all the complete firmware repeat the point from 5 to 7 but insert this code now
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now you will be able to receive the OTA update with your locked BL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @Nirbhay2

aSaro12 said:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Click to expand...
Click to collapse
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:

manos78 said:
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
Click to expand...
Click to collapse
Yes, this is a little but important thing. :good::good:

Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

siddhesh9146 said:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
That thread is specific for Indian Variant.
And if you read carrefully I've mentioned the writer of the thread that you've posted.

Thank you!!
That worked perfectly on XT1685. Much appreciated.

Thanks
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?

SeRi0uS007 said:
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
Click to expand...
Click to collapse
My Software status is also Modified and I never got ota's I always had to manually clean flash stock images. If someone found a way I would love to know how to get ota's on stock rom.

Thank you. my phone can get OTG now.

I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !

pfufux said:
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
Click to expand...
Click to collapse
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?

tufoz said:
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
Click to expand...
Click to collapse
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.

pfufux said:
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
Click to expand...
Click to collapse
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93

pfufux said:
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
Click to expand...
Click to collapse
Everyone else is getting the 137-92 update, why does yours say 137-93?

I don't know but the update came from OTA.

pfufux said:
I don't know but the update came from OTA.
Click to expand...
Click to collapse
you confirm me that amazon replaced your phone? i think i will do the same thing

Ok .. i tried the procedure again.. I used 137.33.11 cid 50 NPNS but i got this error messages..
when flashing system: invalid signed image
when flashing bootloader "security downgrade version"...
any hint?

tufoz said:
you confirm me that amazon replaced your phone? i think i will do the same thing
Click to expand...
Click to collapse
I confirm Amazon changed the motherboard of my phone. I have a new IMEI number.

I can't re lock bootloader
Hi, i am trying to install stock rom and relock bootloader because after installing custom rom, i am not getting network in my device. but now after installing stock rom(see below image for version), i cant relock my bootloader. it gives me error like security downgrade issue.

Thanks a lot
:good::good::good::good:
the indian variant relock is not correctly explained
You Have Explained It
Listen all
You will need the firmware which you were using before unlocking your bootloader then only you can relock it again
Now i can give it for warranty Thanks a Lot

Help Z2 PLAY XT1710-11 + Testing

Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions​
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends

I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .

Trying to install latest TWRP on Moto G5 gives error (bootloader) Image size exeeded partition limits

Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?

trickyDicky314 said:
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
Click to expand...
Click to collapse
Note later 64bit twrp version for some reason exceed partition size. If you require a permanently installed TWRP use an old version.
To use the later versions of TWRP you need to boot to TWRP instead each time you want to use it.
Click to expand...
Click to collapse
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com

As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.

sd_shadow said:
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for fast reply! I will try just booting new version and installing. I didn't realize that would work, I thought u needed TWRP permanently installed for it to work, (am not experienced with this stuff).
Thanks again!

TheFixItMan said:
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
Click to expand...
Click to collapse
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.

trickyDicky314 said:
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
Click to expand...
Click to collapse
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.

sd_shadow said:
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
Click to expand...
Click to collapse
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to

sd_shadow said:
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again

TheFixItMan said:
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
Click to expand...
Click to collapse
Thanks so much! This worked, I am now in Lineage OS! Thanks for taking the time to help out a newb like me by writing out every step

trickyDicky314 said:
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
Click to expand...
Click to collapse
Yeah, just skip that, and go straight to the rescue option