Database Users

moto g4 stuck in fastboot mode (Hard brick)

hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot mode
{
"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"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful

have you found the solution

adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet

System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem

Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?

null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again

Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that

Rom flashing failed . What should I do?

adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?

This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"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"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Phone bricked, need help fast

I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix

DeathBell said:
I wanted to reinstall the stock rom (B360). I booted into TWRP and for some reason I wiped System, Dalvik cache, cache and internal memory (I dont know why I did that). Then I installed the Firmware but it failed probably because my frp was locked and I didnt know about it. Then I rebooted and now I cant boot to the system. When I boot into TWRP it just hangs on the TWRP logo and doesnt go on, eRecovery doesn't work. I can boot into fastboot. Its says that phone is unlocked but frp is locked. I hope that there's a way to unbrick my phone without dc-phoenix
Click to expand...
Click to collapse
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)

Tiagohsoares said:
Install the stock recovery and then stock ROM. (You can install the stock recovery when your phone is in bootloader mode and you install it by the cmd in Windows)
Click to expand...
Click to collapse
Sorry for the late reply. Whenever I try to flash the stock recovery it says FAILED (remote: Command not allowed):crying:. I tried both fastboot flash recovery_ramdisk and fastboot flash recovery, neither of them worked.

After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
{
"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"
}
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.

DeathBell said:
After doing some more research (like 3+ hours) I think that the error can't be easily fixed:crying:. Some solutions that I've found that may work all involve either disabling USB debugging and then rebooting and re-enabling it or somthing like that which I can't do since I can't boot into the system or relocking and then unlocking my bootloader which I also can't do without dc-phoenix since my frp is locked. Also I don't know if the dload method will work as I can't access the sd card when I plug my phone to the PC. It may be possible to push files there using adb but I'm not sure if it will work even when I get the right files to my sd card. So unless you guys don't have a better solution, I'm probably going to buy the HCU + DC-Phoenix 3 day licens for 20€ (still a lot better then changing my motherboard for 100+€). Also here's the adb window with the error.
Edit: I'm not going to buy DC-Phoenix until somebody says that there's no way to fix my device without it. It's so unfortunate that I probably can't fix my phone for free even when things like fastboot, charging and adb are working and bootloader is unlocked.
Click to expand...
Click to collapse
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!

Alexxxx1 said:
It seems that you need just to perform FRP unlock with HCU client.... After that you can flash twrp, etc....
Also you can try method from @vovan1982
"Small manual: removing frp lock.
If you have frp_lock and have not TWRP. Download in FF (FirmwareFinder) third file of firmware (example: update_full_WAS-L21_hw_ru.zip), unpack. Run DCPhoenix small update.app, and when DC Phoenix open back_door, detach usb-cable. On PC run cmd.exe and flash this frp.img"
Good luck!
Click to expand...
Click to collapse
I fixed my phone using the 1th method in dc-phoenix already :laugh:, the HCU frp thing didnt work because my device model wasn't supported. And I didn't know where to flash the frp.img file. But now my device is working great:fingers-crossed:.

if someone read this or newers, watch this video: it works for frp lock

Mi A1 Bootloop after ota update and Locked Bootloader

Hi,
I've installed an ota update and the device didn't boot... it is stuck in a bootloop....
When i try to flash via fastboot, it appears an error saying that the device is locked ant cennot erase...
via fastboot oem unlock i get the error message: Remote: oem unlock is not allowed
via MiUnlocker the unlock gets to de 50% and gives an error and on its logs it says: Remote: oem unlock is not allowed
I tryed to flash TWRP with command fastboot flash recovery but the error is the same: remote: partition flashing is not allowed
Can anyone help me please??
I'm stuck on the bootloop i can't go to setting - developer - allow oem unlock option!!

Have you tried doing a Factory Reset from stock recovery?

This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?

Parnas72 said:
This is a strange behavior, even if an OTA update corrupted the system for some reason, the phone should boot from the original slot.
Have you tried switching slots manually from fastboot ?
Click to expand...
Click to collapse
How can i do that?

Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!

Tepig said:
Have you tried doing a Factory Reset from stock recovery?
Click to expand...
Click to collapse
No recovery.. i get this:
{
"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"
}

Typhus_ said:
Hello!
I've faced the exact same problem yesterday.
You need to force the phone to boot in EDL mode by opening the back cover and short circuit 2 pins as shown in THIS video.
After you have the phone in EDL and being detected by your PC (you need the correct drivers, you may get them on THIS thread by @CosmicDan), you may use MiFlash Tool to flash official PIE Rom, access developer options and enable oem unlock to be able to unlock your phone again.
If you wish to revert to Oreo, please use THIS guide.
Cheers!
Click to expand...
Click to collapse
Obrigado!
I'll try it now!!

xistolas said:
No recovery.. i get this:
Click to expand...
Click to collapse
Actually you have a recovery. You need to long press the power button and, afterwards (not at the same time), press the volume + button. You'll see that all options will appear.

xistolas said:
How can i do that?
Click to expand...
Click to collapse
fastboot getvar current-slot
to show the current slot,
fastboot --set_active=a or fastboot --set_active=b
to change it.

xistolas said:
Obrigado!
I'll try it now!!
Click to expand...
Click to collapse
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
---------- Post added at 09:27 PM ---------- Previous post was at 09:23 PM ----------
akashavel said:
get into fastboot mode
hot boot twrp using fastboot command
copy efs backup to twrp backup folder and restore
then go into bootloader mode
flash the firmware using miflash
Click to expand...
Click to collapse
follow from step 6 to end in below link
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624

Question Help! Stuck in fastboot mode can't do anything

So i try to use the DSU Loader found in Developer Options to flash a GSI, but i forget to unlock the OEM and turn on the usb debug.
After installing a DSU and rebooting, the phone will attempt to boot the GSI but it shows "Your device is corrupt" and will no longer boot.
That said, the phone boot to fastboot mode automatically. But all the options under fastboot is not working, i can't get into the recovery mode and my laptop can't identify my phone when i connect to it.
Is there anyone know how i can fix it?
{
"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"
}

I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/

misecia said:
I had the same problem and flashed the boot.img on it and it was fixed.
If that doesn't work you can follow this guide to restore the system (needs to be in fastbootd mode): https://www.droidwin.com/unbrick-nothing-phone-1-flash-stock-firmware-via-fastboot-commands/
Click to expand...
Click to collapse
Thanks mate
But you can do it even you haven't enable OEM unlock and USB debug before the phone get bricked?

-

i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??

xera3k said:
i have the same problem.. only fastboot commands work, anything i do just reboots the phone back to same menu . cant enter fastbootd. i can flash all partitions apart from product..system and some other. these i get error on. i got the bootloader unlocked but thats about it. i also did DU in dev mode then corrupt device.. anyone got a fix for this??
Click to expand...
Click to collapse
Do you have the latest android platform tools? Try different cables, different ports?

Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/

xera3k said:
Yes this is a problem on the phone. . Vi tried Windows and Linux , i can send commmands but only Flash some partitions and dont have or cant access bootloader or fastbootd.. so im stuck :/
Click to expand...
Click to collapse
Idk if its because of that but you have typo in that command, should be bootloader instead boodloader

What if have you tried to boot into another slot fastboot --active-slot

layz1319 said:
What if have you tried to boot into another slot fastboot --active-slot
Click to expand...
Click to collapse
What command would i use ?

xera3k said:
What command would i use ?
Click to expand...
Click to collapse
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best

layz1319 said:
So you may want to use fastboot getvar current-slot to get what slot you are currently using. Then use fastboot --active-slot=(the opposite slot you are using) eg.fastboot --active-slot=a / fastboot --active-slot=b. Lastly, fastboot reboot
Ps. Sometimes fastboot --active-slot=a/b may not work so you can try with fastboot --active-slot= other to boot into non current slot. Anyway wish you all the best
Click to expand...
Click to collapse
I also am having this issue and tried what you suggested and got this.
Any ideas on how to fix?

Eventually I was able to change the active slot but sadly still looping.

yquitumadbro said:
View attachment 5677361
Eventually I was able to change the active slot but sadly still looping.
Click to expand...
Click to collapse
Try to change it again. I solved with that.

Good evening, I have the same problem after using the DSU Loader, the mobile is stuck like the screenshot in the first post above. I've tried everything but can't unlock anything. Can someone help me ?

If your PC isn't detecting your device while in Fastboot mode, you don't have the correct drivers installed. This may help.
Never try to install non-factory software on a locked bootloader!
Since you didn't enable OEM unlocking, it's unlikely that you'll be able to recover your device. Still, focus on the driver issue for now and we can go from there. Do you have ADB Platform Tools installed?

I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked

Dominicus.1 said:
I installed GSI directly from the smartphone, I don't think I used unofficial software. The pc recognizes the mobile phone in fastboot and I also tried with ADB platform tool, but every time I get the message of device blocked
View attachment 5681643
Click to expand...
Click to collapse
ADB commands do not work in fastboot.
fastboot devices should show the device when connected in fastboot mode.
Try fastboot flashing unlock to unlock the bootloader, which will make recovering your device much easier.

I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works

xera3k said:
I tried everything, Windows never found my device inn fastboot but i plugged om a Linux then voila. Everything works
Click to expand...
Click to collapse
U can't do anything if u r OEM tab is off and you soft bricked and not booting to system.
If unr able to boot in recovery using fastboot menu there do format data it will boot to system