Hello, I've been having this problem for about 2 days, well I'll summarize what happened to save mine and your time.
One day I was working with my g5s plus normally (using pixel experience 9.0), the other day I blocked the phone screen normally, but after that it turned off by itself and it is no longer booting the system...
interestingly it normally goes into bootloader and recovery mode, but whenever I try to install a rom, either custom or stock, it always has the same behavior, I install the rom and start the system, it loads up to the motorola logo and it turns off, it's not like a bootloop, it just loads up to the motorola logo and simply turns off.
I've tried many ways to recover, nothing worked, I tried to pass the rom through rsd lite, through motorola manager and of course through adb, I even tried to install a custom rom through twrp, but that always happens.
recently I was passing his latest rom through fastboot adb, when I noticed that during the process two errors appeared in the terminal, does anyone have any idea what it could be? I will leave the images linked here.
1. at the beginning of the rom installation it displays this highlighted 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"
}
2. almost at the end of the installation it displays this same message...
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
lynxrz said:
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
Click to expand...
Click to collapse
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
ocod said:
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
Click to expand...
Click to collapse
First step:
Try to find gpt compatible firmware and flash it with fastboot.
Not Adb, not Rsdlite, not lenovo rescue asistant only with fastboot!
You will not get 'permission denied' error while flashing correct gpt partition table. If you find this firmware keep it, it could be correct firmware to go next step.
Examine my flash.bat file and don't flash all of them just these
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
I found it my compatible gpt firmware with downloading 30 GB+ stock firmware files then tried to flash every one of them in fastboot mode. Don't give up. I found the solution about a week. I'll check this post daily and try to help you step by step.
Related
Hi friends,
i have a mate s L09 and i had 5.1.1 Lollipop on it CRR-L09C432B161 or something like that.i think it was a rom for Turkey.
i wanted to root it and installed carrera 2.8 twrp with fastboot mode but nothing changed.i could not get twrp.so i could not install supersu and i wanted to install CRR-L09C432B145 rom and my device get bootloop.
So i tried to install other roms via fastboot but nothing changed.
Then i gooogled all the net and did everything but i could't get device back.
i wanted to install twrp rtecovery but i think there is a problem and no rom or recovery got installed.
Now:
1-i don't know which rom was installed on it.CRR-L09C432B161 or something else.
2-i can not install any rom or recovery.(i did many times to extract with Huawei extract tool cust,boot,recovery,system and installed with fastboot but nothing)
3-My device's bootloader is unlocked but i don't know FRP is locked or unlocked(the pic is under)
4-Maybe FRP is locked and i can not install anything becouse of it,i do not know
5-My compuer can't load the device,all the adb drivers installed,no problem.i changed cable and sd card but same problem.
Please help me.i can not use my device.
The pics:
{
"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"
}
]
The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.
Tuerkay said:
The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.
Click to expand...
Click to collapse
Hi,thanks for your reply,
i tried many times that solution.when i do volume+/ and power device get Huawei's erocovery and i press the "update with internet" it says "no wireless found".the other alternatives are "power off" and "reset".
PS:Yes,you're right in the second image,it says:
PHONE Unlocked
FRP Unlock
with red color.
If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.
Tuerkay said:
If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.
Click to expand...
Click to collapse
ADB drivers all installed.Phone unlocked but it says "FRP Unlock".Not FRP unlocked.i flashed many times new system. Extracted System.img Recovery.img boot.img and cust.img from an Update bu nothing changed.i think they can not installed.
i tried many different roms..B145,B321,B114.And i tried to install twrp recovery but nothing changed again.
i tried all adb command to erase local stroge but isays the command are false.
and i forget to say:my computer can not see the device.it says "device not found".i uninstall the adb drivers and install again the last driver but nothing changed.
Any other way to install rom?
Or if i have to unlock FRP can i install rom?i don't know muck more about the Huawei system.
i upload images again.
You have to use fastboot commands in fastboot Mode. ADB commands wont work. Plug in your Phone. Open device Manager on your pc. Look for "android device". Remove Driver. Unplug Phone. Install "minimal adb and fastboot". Reboot pc. Plug j. Phone. Pc should find Phone now.
Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.
altanis said:
Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.
Click to expand...
Click to collapse
contact me, i can solve your problem
mutahharbashir said:
contact me, i can solve your problem
Click to expand...
Click to collapse
Thank you for your reply @mutahharbashir,
but i did not solve the problem and sold my phone.
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screen
{
"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 can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Catnip202X said:
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screenView attachment 5281583
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Click to expand...
Click to collapse
TWRP must be flashed with the command:
fastboot flash recovery_ramdisk ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
zgfg said:
TWRP must be flashed with the command:
fastboot flash recovery ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
Click to expand...
Click to collapse
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Catnip202X said:
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Click to expand...
Click to collapse
Yes, sorry, you are right, typo.
But I wanted to point that you must use fastboot flash command (not FLASHBOOT or whatever you used in your post #1)
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
But also READ the P9 LOS thread - it clearly describes that LOS must bi flashed from fastboot, not from TWRP and it actually asks users not to use TWRP
See here and better ask there to get the answers directly from developer:
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9
This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches. It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera...
forum.xda-developers.com
zgfg said:
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
Click to expand...
Click to collapse
I have indeed tried this route, but as I have stated before, trying to boot into recovery mode right after flashing TWRP and pressing key combo still boots me into the error screen where it says that I need to update something. On the bottom of the screen will also show errors such as Function11 not found and error 2 no image etc. I’ll try to replicate it and send you a picture of the error screen when I get home from work tonight.
Hello there
I think i did somethinh wrong while trying to install twrp. Now when it boots it stays stuck on twrp screen, i cant switch it off. If i try, it will boot again on twrp screen. But i can boot it on fastboot mode.
I tryed with adb commnds to reinstall twrp but it does not recocnize dhe device when the phone is in fastboot mode.
If i boot the phone on the stuck twrp screen it is recognized by adb but it does not executes any command.
Eventually i thought trying to clean flash the stock rom will fix everything and i can try again with a fresh start. But the mi flash gives error,; flashing is not allowed for critical partitions.
The bootloader is unlocked.
Your browser is not able to display this video.
Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.
Andrologic said:
Try flashing your original boot.img (that worked with your current ROM version) back to the device from Fastboot.
Click to expand...
Click to collapse
Thnx for the suggestion. But as i said the phone does not respont to adb commands.
biqe said:
Thnx for the suggestion. But as i said the phone does not respont to adb commands.
Click to expand...
Click to collapse
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...
Andrologic said:
Not adb. You need to be in bootloader mode with Fastboot access to be able to flash boot back. Power up the device in bootloader mode with the vol+power buttons and confirm that your device has Fastboot access (e.g 'fastboot devices' returns your device id). Flash your boot from there. If Fastboot access is impossible, it's a bigger issue but try that first...
Click to expand...
Click to collapse
When i try vol+power it boots on twrp and stays like that
{
"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"
}
Update. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.
biqe said:
Update. It loks like using adb was the problem. But using the platform tools i could execute comands and i fixed the issue. The phone is clean and i could flash the stock rom with mi flash.
Click to expand...
Click to collapse
Hello, i have the same problem. Did you use only mi flash to resolve the issue?
Mi A2 does not have /recovery partition, a recovery is a part of the /boot image, and thus TWRP is not to be "flashed" into /boot (or absent /recovery), but can be "patched" into /boot installing appropriate .ZIP file in a temporarily booted TWRP (tip: search Guides).
This "revelation" could be found in many threads / guides in this forum - search could help you.
As well as "revelations" answering your question:
AndroidOne devices do not need any MiFlash (except for testpoint unbricking, tip: search Guides), if bootloader and critical partitions are unlocked, just normal fastboot.exe from latest Android platform-tools (tip: search in Guides).
hello,xiaomi redmi note 9 of my friend,he just know where is on/off button and graphics icons.
he give me the phone in bootloop whit Redmi on screen.
hard reset no help,flash firmware or update error or end at 4.99%.
recovery look's ok,i can select reboot to system/wipe data/my assistant but no help.
Fastboot mode available but bootloader locked,if i try to unlock bootloader whit official app after some check's the web app suggest me to add mi account on the phone menu' but impossibile bcz phone not start
so i try to flash whit some tools...no succes,only flash by XiaomiADB whit phone in "MI assistant mode" try to flash but almost always error server or "custom flash not allowed" or similar.
i don't know what firmware have,
only info by screen of Xiaomi Mi Pc Suite i see "Version V12.0.3.0.QJOEUXM" and update available to "V12.0.10.0QJOEUXM" but if try upgrade still freeze at 0,00% or 4.99%.
Flash whit XiaomiADB give me error descripted as before maybe pics help me to more clear explain,i see on phone screen incremental upgrade bar but stop at 4,99%.
XiaomiADB format data success but not help to boot.
Opened phone and no hard damage or water inside,disconnect battery not help.
thanks for help me
SPFlashTool fear to lose NV data...maybe last chance but i need exact instructions for flash.
{
"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"
}
You can flash safely using spflashtool.
Just avoid to flash using FORMAT ALL mode, it will clear NV too.
If you flash using FIRMWARE UPGRADE mode, it will clear userdata only and relock bootloader.
thank's
what kind of firmware need? (fastboot? update? recovery?) and what version suggest?
i try to flash fastboot rom official,gave an flashtool error BROM etc so i switch to Firmware upgrade,flash start but end as can see at 23%.
now phone start whit redmi logo then show fastboot bunny...
what i can do now?
updated news...
i try whit vol+ press,battery connected,download green key then connect usb cable.
flash done,look's all ok but...no imei 1 and imei 2
absolutely never used Format!!!
stakkio said:
updated news...
i try whit vol+ press,battery connected,download green key then connect usb cable.
flash done,look's all ok but...no imei 1 and imei 2
absolutely never used Format!!!
Click to expand...
Click to collapse
Certainly, the old user, lost it before you get the device.
sorry for annoyng messages,
after 1st settings of the phone and ime check i try reboot,
phone starts but still freeze on MIUI logo,
recovery menu' available,fastboot available,bootloader still locked.
actual version flashed is v12.0.3.0qjoeuxm
how i can contact you via telegram? maybe some direction for solve
hello
some days after...finally end of the sad story
just for info,maybe help someone.
flash the engineering rom,write original imei sim 2 whit maui meta (imei on the original label package),
imei operation can do whit some methods,pytoon/libusb or mct mtk tools but maybe not need bcz the Engineer ROM look's open at mods,
switch on the phone and see very simple android system,*#06# imei appear on SIM 2,look at phone info and show imei correct but single sim,not big problem,look's all done,put sim card in and try to call,is all ok,still engineer ROM,
so i want restore the MIUI,i try the same as before crash,the V12.0.3.0.QJOEUXM,
always error in spflashtool,sometimes writing "cust. image",sometimes during "super",
whit auth file and whitout,same scatter of ROM or another for same version,always error during flash
i try to wipe data from recovery menu' (available)....result...lost imei again
so,tired,i repeat all,Eng ROM,maui meta imei,and new version (fastbootfile) V12.0.4.0QJOEUXM whitout AUTH file in FIRMWARE UPGRADE,flash done,
TADA...after MIUI boot correctly i check imei and,surprise,i have all 2 available and all 2 IMEI exact
Phone alive,SIM 1 and 2 working
i stop OTA auto update from MIUI option because i dont know what can happen if phone upgrade MIUI,notice me info about thanks.
You can upgrade your device safely.
It can't cause any damage to your device.
Hello. I have unlocked my bootloader last night and flashed my redmi note 10 pro max through fastboot mode today. After flashing xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13 rom, my phone started rebooting, MIUI 14 logo appears but suddenly it went into recovery mode directly within 04-05 seconds. Now if I reboot the phone, it opens but after 04-05 seconds it again went into recovery mode. I tried wipe out and safe mode option too. The scenario is the same for both cases. Asking for your help regarding this
Rabbi_RN10promax said:
Hello. I have unlocked my bootloader last night and flashed my redmi note 10 pro max through fastboot mode today. After flashing xiaomi.eu_multi_HMNote10Pro_V14.0.2.0.TKFMIXM_v14-13 rom, my phone started rebooting, MIUI 14 logo appears but suddenly it went into recovery mode directly within 04-05 seconds. Now if I reboot the phone, it opens but after 04-05 seconds it again went into recovery mode. I tried wipe out and safe mode option too. The scenario is the same for both cases. Asking for your help regarding this
Click to expand...
Click to collapse
I think you dl'd the global stable, not EEA for EU. You want the 14.0.3.0 for EU.
Sheist! said:
I think you dl'd the global stable, not EEA for EU.
Click to expand...
Click to collapse
yes may be. what to do now? how can i flash any other rom?
Put on your phone and try the Apply Update from your recovery. I believe it looks in the downloaded_rom folder in Downloads on internal SD.
There is no such things like apply update in the recovery mode.
how can i flash custom recovery without turning on USB Debugging? as I can't open my mobile right now I ain't able to turn on the usb debugging. please suggest
{
"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"
}
Correction. The downloaded_rom folder is not in Downloads, but beside it in the root of internal C. Try creating that folder in Windows with the phone connected and put the file in there then reboot and see if it installs automatically. If not or you do not see the phone in Windows, then you can flash the version of TWRP for your phone using the official TWRP source location and install from it. You stated it is unlocked already, and USB Debugging may not be a problem since this is a stock MIUI ROM. Use the 3.7.x from twrp.me.
Can you still get fastboot? If that case, I'd revert to stock with MiFlash and start again...
pnin said:
Can you still get fastboot? If that case, I'd revert to stock with MiFlash and start again...
Click to expand...
Click to collapse
I can get to fastboot mode. but as my usb debugging is off, my pc doesn’t recognize my device.what to do then?
Don't quote me on this, but I think MiFlash doesn't need USB debug, only the right drivers.
pnin said:
Don't quote me on this, but I think MiFlash doesn't need USB debug, only the right drivers.
Click to expand...
Click to collapse
will try then. thanks!
Try flashing TWRP without USB Debugging from fastboot. It might work. Then you can flash your install file inside it, which being MIUI, it should not require USB Debugging either.
hello, to use fastboot you don't need usb debugging, usb debugging works with user confirmation only with the system started, instead, in custom recovery it works automatically, if you want to restore your smartphone, you can do it by downloading the latest miui fastboot for your device from here: https://xiaomifirmwareupdater.com/
once you download the right package (be careful what you download!), you will have to flash the rom via fastboot, you can use mi flash if you are comfortable with it, be careful with the options below, if you leave "flash and lock" it will flash, but it will lock the bootloader, if you don't want to lock it, select "clean all". good luck