Develop Bugs

How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)

How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?

First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?

After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.

kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.

Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
echo off
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
fastboot flash fsg fsg.mbn
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 system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.

Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?

Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.

kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time

Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk

akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk

Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?

This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!

I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$

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

[ROM] [10] OmniRom for OnePlus7T Pro [EXPERT]

CLOSED PER OP REQUEST
{
"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"
}
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2020-01-08

first

Wahoo. Thanks for this.

Oooo nice ?

new build is up
fingerprint should be fine now
10.0x whatever is the latest release blobs.
other little stuff
and whats below:

darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-19
Click to expand...
Click to collapse
download error!

Thx. How to root??

Just_Pisces said:
Thx. How to root??
Click to expand...
Click to collapse
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.

p70shooter said:
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
Click to expand...
Click to collapse
Thx. Just forgot to check“Preserve AVB 2.0/dm-verity”. Now Successfully

Hello to all ..... Unfortunately, the download link is not up to date or the destination host is not available ... could someone please upload the ZIP or create a new link to download? many thanks

its back online

darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-22
Click to expand...
Click to collapse
Hi for some reason it didn't work for me
Wipe successful could not partition
Error message Failed remote not discoverable when flashing images.
I'm paraphrasing I accidentally closed the command prompt after rebooting.

It clearly says its only for people that can read and follow instructions.

Hm, I can't write system neither to 'a' or 'b' slot ... boot image is looking ok.
What I am doing wrong?
I am on latest 10.0.4.
Code:
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.309s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.651s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.412s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.047s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.317s]
Writing 'boot_b' OKAY [ 0.410s]
Finished. Total time: 2.753s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.450s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
EDIT:
Not sure if it helps but this is what I get from "fastboot getvar all"
Code:
(bootloader) has-slot:system:no
Also tried it from 10.0.3 base to check if it's bootloader issue with no change.
EDIT2:
Oh well, I am an idiot who can't read instructions properly and didn't realize there are two fastboots
You need to reboot to fastbootd from fastboot !!
I will leave this here for people like me.

@darkobas thanks for the amazing rom!!! it works flawlesly

guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks

darkoj2007 said:
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
Click to expand...
Click to collapse
Find the kernel patch then we can continue to talk

maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
Can we talk about Wireguard?

maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?

houmles said:
Can we talk about Wireguard?
Click to expand...
Click to collapse
No - somr things never change
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
darkoj2007 said:
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
Click to expand...
Click to collapse
BORING!!!

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

Development [ROM][11.0][OFFICIAL][ALIOTH/ALIOTHIN] EOL - crDroid v7.22 [12.09.2022]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features: https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Sources:
ROM:https://github.com/crdroidandroid
Kernel: kernel Optimus Drunk
Github: raystef66
LATEST crDroid Build
Flashing Instructions: FOLLOW NEW GUIDE
POCO F3 TELEGRAM GROUP
What's working / what's not:
* most of it is working :
ril
audio
wifi
BT
camera
NFC
FP
Faceunlock
GPS
AOD (tile)
hotspot
DT2W (on doze)
DT2S
ambient features
ok google
...
* bugs : DO SEND LOGS WHEN REPORTING BUGS
. . .
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
If you like my work, consider a donation! MY PAYPAL
Contributors
@raystef66
@jomadeto
Source Code: https://github.com/crdroidandroid/android/tree/11.0
ROM OS Version: 11.0
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, miu v12.0.x or 12.5.x
Status: stable
Sec. Patches : 2022.09.05
Created : 2021.05.07
Last Updated : 2022.09.12

CHANGELOG
Highlights & Device Specific Changes:
Build type: Monthly
Device: POCO F3 (alioth)
Device maintainer: raystef66

raystef66 said:
CHANGELOG
Click to expand...
Click to collapse
Congrats boss for being Official

raystef66 said:
GAPPS INCLUDED for now
Click to expand...
Click to collapse
"for now" gives me hope that it won't be there at some point. Yes?
BTW: Thank you very much for developing/porting this ROM

Fahmid Islam Soumya said:
Congrats boss for being Official
Click to expand...
Click to collapse
Thnx bro

Awesome work

Robert314 said:
Awesome work
Click to expand...
Click to collapse
Waiting for yours

can I flash this from xiaomi*eu latest stable rom, sir?

My poco f3 should be delivered in days, I'm so happy seeing development advancing so fast. Thank you!

Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed

Does it have OTA?

Can i flash it over base miui 12.6?

So only SSOS has a fully working D2tw right?
so far so good. love crdroid! thanks matey! <3

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...have no problems with xiaomi.eu though

navey said:
Having the exact same issue with this ROM and Pixel Experience.... coming from a newly flashed 12.0.2 global fastboot and freshly unlocked bootloader...
Click to expand...
Click to collapse
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot

Abaddon said:
replug or use a different cable.
use a different platform tools (adb and fastboot exe) I prefer the one's from google but not the latest fastboot as it borks flashing stock roms via fastboot
Click to expand...
Click to collapse
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research

navey said:
tried several cables and like i said I don't have any issues with xiaomi.eu at all. I see my device just fine in adb and fastboot as well.. will do more research
Click to expand...
Click to collapse
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap

hkfriends said:
Installation is not working on stock (unlocked) alioth_global_images_V12.0.3.0.RKHMIXM rom
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it will boot to a special FASTBOOTD menu and it is stuck with < waiting for any device >
... so i have to select fastboot again..... then it reboot to MI fastboot menu it stuck the same, so i have unplug the usb cable to continue and work..
but in the MI fastboot mode, it cannot flash system.img
H:\crDroidAndroid-11.0-20210507-alioth-v7.5>.\platform-tools-windows\fastboot flash system_a Images/system.img
Sending sparse 'system_a' 1/2 (774900 KB) OKAY [ 17.824s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Click to expand...
Click to collapse
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com

Abaddon said:
I said those because I had a similar scenario. xiaomi eu fastboot flashes fine but other fastboot roms wont flash properly. its either my port (had to replug), usb drivers and the fastboot exe itself. I fixed it by changing the fastboot.exe to an older one. goodluck with yours hope u get it fixed asap
Click to expand...
Click to collapse
Thanks man i actually got it fixed by installing system wide adb but it was your thoughts that lead me there. THANK YOU!!

navey said:
Fixed this! Enabled system wide ADB on my machine and now its working smoothly so far with no errors whatsoever. Follow this link
Set up System-wide ADB and Fastboot on Windows 10/11
Here's how to set up system-wide ADB and Fastboot on Windows 10 and 11. Download SDK platform tools and enjoy universal ADB and Fastboot.
technastic.com
Click to expand...
Click to collapse
will try this out tonight... strangely it is due to missing system path to execute fastboot?