Database Users

[Q] Can't boot. Stuck on Google logo

Hi,
I really need some help on this one. I wiped everything using TWRP recovery in preparation of installing a custom ROM.
I then realised I forgot to transfer the custom rom to my phone! When I went to reboot the system it says "No OS installed! Are you sure you want to reboot?"
No it's stuck on the google logo.
Is there a way to see if any Rom is still installed on on my phone or if it deleted my stock rom also?
I tried to push the rom through adb but it says error read only.
Also USB debugging is not enabled but I can't boot to enable it.
Please help.
Thanks

Go into fastboot and ensure your fastboot devices command shows your s/n. If so then grab the stock image from xda and flash it.
fastboot flash bootloader BOOTLOADERNAME.img
fastboot reboot-bootloader
fastboot flash radio RADIONAME.img
fastboot reboot-bootloader
fastboot -w update IMAGENAME.zip
Alternatively, using ADB.
from command prompt: adb remount
adb push <FILE PATH> /sdcard/0/
Boot into recovery (I use CWM) and then install it.

Thanks for the quick reply.
I managed to solve it by using the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2010312
It's all in fastboot so I had no problems
Problem solved.

[Guide] Most Problems and Info's that you must Know about ADB and Fastboot

Tips & Guides About Moto G 2014 ADB and FastBoot
The most of people have problems with fastboot and ADB. Here will explain some tips and guides.
- Do u know can use ADB in recovery mode?
Yeah if u have bricked your phone or deleted system or can't put the Debug Mode have a alternative. This happens the Device ADB have two modes. The USB mode and Debugging Mode, using two different drivers. When you download Motorola Device Manager he installs the Debugging Drivers. In Motorola is really hard obtain the correct drivers.
- Can I flash zips with fastboot?
Yeah but isn't recommended the people try that:
- fastboot flash zip myzip.zip
This is incorrect he will try to flash a .IMG in a partition called zip.
- fastboot -I flash system myzip.zip
This is incorrect. When you download a ROM backup to flash in Recovery he have some partitions making that will create a partition into a partition. Bricking your device.
The correct way to flash ROM is in recovery.
- I can't transfer file on my device.. Can I flash?
Yes using two methods
- ADB push
You push to your device a .zip with the Rom eg.:
- adb push my file.zip /sdcard or /sdcard1
This will push your file to the device and you can after that flash in recovery.
Is normal after digit the command nothing happens. Differently fastboot the ADB doesn't shows progress of transfer.
- ADB side load
You can flash sideload the zip
Using adb sideload myzip.zip
Must enable sideload mode on your recovery.
- my device doesn't appear on the list.
When you are on boot loader mode the ADB doesn't runs. Only in recovery mode or system mode.
Most times you have incorrect drivers. But if u are on recovery mode try that on cmd:
adb kill-server
adb usb
This will enter the daemon service in USB mode.
- can I reboot my device in recovery? Yes, adb reboot recovery
- can I wipe my firmware with fastboot? Yes, using these cmds.
fastboot erase userdata
fastboot erase cache
- can I get my device info?
Yes with ADB.
adb get-imei
adb get-serialno
adb get-deviceno
If u have more questions write here. I will add on OP.
Downloads:
- Moto G drivers: https://mega.co.nz/#!IY0mUBDL!tukY40l9_GlYpJVuSxahYBXhDjXDBfhG-bfG0oIvEa8
- Minimal (really minimal) ADB & fastboot: https://mega.co.nz/#!NJUVlIwI!uiRi4UAdU-8ZKEeQ1gquGDYbSSG9rWIWeMElUcMD4e0

Impressive, n tnks for sharing
sent From My XT1068{LP} using TapatalK

plez help me
OEM unlock failure! :crying:

adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Dont type UNIQUE_KEY in the command. Its just the syntax.

KrishnaSagar said:
Dont type UNIQUE_KEY in the command. Its just the syntax.
Click to expand...
Click to collapse
I totally did that before lol

adel pro said:
OEM unlock failure! :crying:
Click to expand...
Click to collapse
Hello tipe
fastboot oem unlock TheKey
But u can check if is unlocked in the boot loader is is status code 3
Ah.. If the unlock doesn't work:
fastboot oem get-unlock-data
Pick the code without the word (fastboot)
And put all the code in one line.
THE MOTOROLA PAGE DOESNT VALIDATE YOUR ENTERED CODE ONLY GENERATE A CODE WITH YOUR INPUT.
If u put a wrong code. He will generate a wrong code.
Cheers

No Fastboot Option In Bootloader

I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.

It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.

RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.

RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.

JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?

RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.

teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app

RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.

JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.

RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine

RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices

He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk

Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!

(Solved) Yureka Plus YU5510A - Rooted/TWRP 2.8.7.0

DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done

Flash Latest NON-HLOS.bin before flashing any volte ROM.
Flash through fastboot
File link
https://drive.google.com/file/d/0B8Vodzmhc0GlXzdtOUFjb29EOFU/view
Extract .zip
Copy NON-HLOS.bin in adb folder
Open command prompt here
Connect phone into fastboot mode
Type command
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Wait till process done.
Disconnect phone
Remove battery and insert again
Goto twrp recovery.
Install any volte enabled ROM.
Enjoy.:good:

OEM unlock command not found
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
nischait said:
DWYOR
After a long time of googling I got a solution for yu5510a full access.
You need
Adb + fastboot
Twrp 2.8.7.0 tomato
SuperSU.zip
Coolpad drivers
Cyanogen ROM V1 from firmwarefile.com
Any Custom Rom, I am using aosp extended.
Gapps
Memory card
Install all drivers , adb & fastboot.
First flash Cyanogen ROM using YGDP tool
Use version 3.98 in other versions I got problems.
After ROM installation enable developer option.
Enable android debugging, fast reboot and check update cyanogen recovery
Now connect phone with PC
Goto adb folder
Copy twrp.img in adb folder
Shift + Right click select open command window here
Type adb devices
Device should be shown if not showing try to install adb drivers
Now after that
Type Command adb reboot-bootloader
Device will be rebooted in bootloader
Type command fastboot -i 0x1ebf oem device-info to verify device in fastboot mode and your bootloader is unlocked or not.
If bootloader showing unlocked then follow next process if not then unlock it
Type command fastboot -i 0x1ebf oem unlock
Boot loader unlocked now.
Remove data cable and remove battery from phone for 30 secs and reinsert again.
Press volume + key and hold
Attach phone with PC ( it shows fastboot mode)
After that type command
fastboot -i 0x1ebf flash recovery twrp.img
When done remove data cable & battery
After 30 secs reinsert battery
Press Volume + , Volume - & Power key
When yu logo appears release power key and keep pressing both volume keys
You will be goto twrp
Now wipe everything also format data/don't delete mmc
Restart twrp to recovery
Your internal and external storage are mounted.
Install any custom ROM for yureka/yureka plus
Flash gapps ( not required in miui & quarkos)
Flash SuperSU.zip
Reboot
It takes 10-15 minutes for first boot .
Done
Click to expand...
Click to collapse

nithin1664 said:
hi,
I am trying to root my yu yureka plus( YU5510A white color) running android 5.1.1 , build number is 5.1.111.P0.160314.YU5510A , i am able to connect the phone to my PC running adb,
"adb devices" lists the phone , "adb reboot bootloader" puts the phone in fastboot ( screeen doesnt show fastboot instead it shows do not disconnect usb cable and non secure phone). When i run the command fastboot -i 0x1ebf oem unlock , im getting the error as command not found. same error im getting when i run the command fastboot -i 0x1ebf oem device-info
what could be the reason.
Any help in this regard is appreciated.
Click to expand...
Click to collapse
Try without using 0x1ebf and report.

nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.

Yogesh1969 said:
I tried without -i 0x1ebf also but it does not show in fastboot. With -i 0x1ebf it shows "xyznumbers fastboot" . The problem now is , I flashed through YGDP tool and now it shows aboot failed image, and does not boot at all.
Why doe my phone show non secure phone ?
Please help.
Click to expand...
Click to collapse
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.

nischait said:
Try without using 0x1ebf and report.
Click to expand...
Click to collapse
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.

nischait said:
Download cyanogen ROM and flash it with ygdp
1st ever rom uploaded in AFH.
Your device should be boot up.
Then try with command prompt.
May be new device having different device ID.
Click to expand...
Click to collapse
I couldnt find the ygdp version of Cynogen, any way I found a way from youtube which solved my problems.
Link : https://www.youtube.com/watch?v=2Gpz65r2pNM
---------- Post added at 05:21 PM ---------- Previous post was at 05:18 PM ----------
vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
For drivers problem install pdanet. And you can refer to the youtube video link (above post) if you want for all needs.

vijaykumarbabu079 said:
Hi...
I too face the same problem, I tried fastboot adb and YU yureka drivers reinstalling and connected device to PC it gets charger when connection in on, when connected in fastboot mode on device it shows fastboot but when check in PC for device info, it dosen't show any connected device. I followed many tutorials for this to install TWRP but its impossible to install without establishing a proper connection. I also tried to install TWRP without PC, for this i need to root my device and flash TWRP img, so I started trying root I had used kingroot, kingoroot, towelroot and some more but failed to root, I am still trying to install TWRP can anyone help me in either of the process to install TWRP.
Click to expand...
Click to collapse
Getting your device connected is a very important stage, whether it is system,recovery or fastboot. From what I read , you can connsct through fasatboot, since you flashed cyanogen. Just flash TWRP 3.2.1 or so which is the latest, through fastboot:
fastboot flash recovery twrp.3.2.1 .img ( Remember the spaces, the name twrp.xxx.img should be same as you downloaded. If flash is successful, you can see twrp when you boot to recovery. Then flash supersu file and/or whichever rom you want.

Sorry for late answers.
I was lil busy and sorry for wrong address also.
You could get it from firmwarefile.com
I can't post link here but select yu yureka plus variant and download oldest CBP

Fastboot help

I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....

BlackHawk580 said:
I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....
Click to expand...
Click to collapse
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone

_NikO_ said:
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone
Click to expand...
Click to collapse
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery

BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check

_NikO_ said:
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check
Click to expand...
Click to collapse
Yes, I've done that too, I've tried installing various different drivers as well, it also has Windows 10 as well

BlackHawk580 said:
Yes, I've done that too, I've tried installing various different drivers as well
Click to expand...
Click to collapse
So your phone is showing up in Adb devuces without any yellow warning or anything?

_NikO_ said:
So your phone is showing up in Adb devuces without any yellow warning or anything?
Click to expand...
Click to collapse
It doesn't show up at all on the list, yeah

BlackHawk580 said:
I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all.
Click to expand...
Click to collapse
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?

BlackHawk580 said:
It doesn't show up at all on the list, yeah
Click to expand...
Click to collapse
If there isnt your computer isnt actually seeing it as an adb device

osd_daedalus said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?
Click to expand...
Click to collapse
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume up and power doesn't enter the recovery either.

BlackHawk580 said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume down and power doesn't enter the recovery either.
Click to expand...
Click to collapse
I'm not sure you can reboot to recovery from fastboot.
Some people tell you can launch "fastboot reboot recovery" but it is not a standard command and does not work for me.
In fastboot you can boot the recovery image file with
Code:
fastboot boot recovery.img
Change recovery.img with your recovery file.
Keeping it simply, can you reboot normally and reboot to recovery via adb? With "adb reboot recovery"

Fastboot is the way to flash anything
Your phone don't have to get recognized by adb, it's more for sideload or apk installation. To flash recovery, you need fastboot.
Try fastboot flash recovery recovery.img (recovery.img should be in the same folder as fastboot.exe)

Is there any news? I have a similar problem:
I boot in fastboot mode and I run `fastboot oem device-info` to check status:
Code:
$ fastboot oem device-info [15:20:59]
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
And it seems ok.
Now I try
Code:
$ fastboot flash recovery recovery.img
and it stuck there and it don't do anything.
I tried different PCs and different cables, nothing make it works!
Normally it only lasts some seconds...
What should I try?
Thanks in advance