Database Users

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

[Q] Zte custom recovery

I'm following the
hxxp://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
guide to build a recovery.img.
It works fine to edit the ramdisk and rebuild with mkbootfs and mkbootimg. Until I flash it and boot up in recovery it stays on the green android splash and it is not fastboot mode. So I was wondering if there's some more to it. If I need a "--base [address]" or something else.
pls answer

Build Nexus 7 source code.

Hey guys,
I downloaded the JB source and created my own device/myvendor/myproduct folder. I copied the full_grouper.mk file into it and renamed it for full_myproduct.mk.
I basically inherit everything full_grouper.mk does but my own vendor and device. Should I even do that or just edit everything inside device/asus/grouper?
I did the . build/envsetup.sh and lunch and all went fine.
I ran make -j4 and the build was successful. Now how do I flash the system.img into the device? Will it also work ? I havent changed anything in the source I just want to flash my own build and then move on with some changes.
Do I need to have my file as an update.zip? Is update.zip a combination of installing the boot/recovery/system into one file? Is there a quick way to test my image works without flashing it permanently?
Final question: when I build the grouper source etc, does it mean the emulator will work too? It appears it does not.
Sorry for the newbish questions, I've looked around for other topics but I cant find a simple tutorial to just flash my own build. All I want is to flash the source code in which I assume would not have the Google apps and then I'll will take it from there.

You start your device in the boot loader by the button combo, or typing adb reboot-bootloader ( not sure on specifics) then while in boot loader type, fastboot flash system system.IMG . I would advice doing a fast boot --help to avoid bricking by using the wrong commands
Sent from my Nexus 7 using xda app-developers app

Deodexed system 34.0.A.2.292 & 34.0.A.2.301

Hi All,
I've deodexed the systems from 34.0.A.2.292 and 34.0.A.2.301.
How to use:
1. download zip
2. flash with flashfire or custom recovery
3. enjoy
Download links:
F5121_34.0.A.2.292_Deodexed.zip
F5121_34.0.A.2.301_Deodexed.zip

nice work bro

Pandemic said:
nice work bro
Click to expand...
Click to collapse
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.

infected_ said:
we need a kernel with recovery or at least sony init, so we can use recovery on its proper partition..
kick-start development on X/suzu ...
ive compiled a boot img from .292 copyleft sources and added ramdisk/twrp..
https://drive.google.com/open?id=0B2Ayh5ZFCqa8RVI1cHJwYk5BeE0
if someone with a unlocked bootloader could try, it would be great.
Click to expand...
Click to collapse
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.

mstrack said:
i flashed it on my german .292, and its booting.
but im not sure how to enter twrp?
adb reboot recovery results in a 'melting' sony screen and after some second the phone reboots into system.
Click to expand...
Click to collapse
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.

infected_ said:
did you flashed a twrp recovery on the recovery partition?
try this one:
https://drive.google.com/file/d/0B2Ayh5ZFCqa8UkxzYnhIazlZenM/view?usp=sharing
and try enter recovery again with that kernel/boot img above.
Click to expand...
Click to collapse
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...

mstrack said:
so, flashed it, reboot, lands in twrp.
asks for encryption password but doesnt accept my pwd.
edit: doesnt boot into system, only in twrp
edit2: i have to flash the recovery via flashtool -> flash kernel ? or did i something wrong?
hell...i miss my nexus...
Click to expand...
Click to collapse
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?

kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
Click to expand...
Click to collapse
yes, got it, thx.
edit: i used flashtool

kistigun said:
You can press cancel when twrp asks for password. It will bring you to the main menu, but a lot of stuff isnt working yet. Currently there is no working twrp yet for our xperia X, follow this thread for more info: http://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708
edit: did you flash it with flashtool or adb?
Click to expand...
Click to collapse
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.

infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? ok then.
Click to expand...
Click to collapse
Thanks for the tip will try it out tonight and report back!

kistigun said:
Thanks for the tip will try it out tonight and report back!
Click to expand...
Click to collapse
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img

infected_ said:
try ramdisk of the recovery also. extract it and try to add it to your .292 boot.img
Click to expand...
Click to collapse
will do, just wondering: what files/folders of the ramdisk are needed for TWRP? I ask because I use a kernel with allready a modified ramdisk(DM-verity/Sony RIC/DRM-fix/SU?busyBox) so I want to know what files need to be replaced to implements TWRP

infected_ said:
the person who gave me that recovery, ill assure you that is working... it came from one member of omni core dev's, which owns a suzu...
you dont have access to the rest of the twrp options, cause of the encryption.
remember the first time you booted up your X on stock? it asked to encrypt/set a password on the device because if it got stolen or lost, etc...
fastboot erase boot, fastboot erase system && fastboot erase userdata should get rid of the encryption and you can try twrp.
all this is helpless ofc unless we can get a stock boot image working with sony init, so we can enter recovery when flashed on recovery partition.
if you hotboot the twrp it works right? so it is working.
Click to expand...
Click to collapse
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?

kistigun said:
So when i try to hotboot the f5121_recovery.img for the first time it flashes the image, after that it boots but it gets stuck on a black screen. I did a hard reset and flashed the image with adb and tried to reboot to recovery but it just rebooted. After that i tried again to hotboot the recovery image and after this it finally booted into TWRP. indeed it's asking for password
Will i loose my system and userdata when i use fastboot erase boot, fastboot erase system && fastboot erase userdata?
Click to expand...
Click to collapse
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0

infected_ said:
yes, it will all be wiped.
you can also try adding sony init to your ramdisk. you just need to extract it from boot.img, add the sony init files, rename a file and make a symlink, repack again to boot.img
ill provide the files in a minute.
edit:
after extracting contents of ramdisk, rename "init" to "init.real", and place the files on the root of the extracted ramdisk dir.
symlink is already created, pointing at /sbin/init_sony
https://drive.google.com/open?id=0B2Ayh5ZFCqa8N3pIQjZMY0ZzdU0
Click to expand...
Click to collapse
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?

kistigun said:
cant extract the init file, getting an error(cant create a symbolic link: access denied)
Edit: hmm just discovered that the tool i was using for unpaking & repacking boot.img isn't working.... Need to find a new tool first, anyone got a good suggestion?
Click to expand...
Click to collapse
delete the symlink and recreate it:
ln -s /sbin/init_sony init

infected_ said:
delete the symlink and recreate it:
ln -s /sbin/init_sony init
Click to expand...
Click to collapse
Sorry it took me a while, had to set-up a new linux enviorment. Repacked kernel, it boots but sony init still doesnt work

Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"

KOALAaufPILLEN said:
Hy can i install the deodexed System as a regual normal System?
I mean if i break my System does IT work as a normal "Rom"
Click to expand...
Click to collapse
No, it only flashes the deodexed files so it does not contain a ´full rom´

Could you make a full rom ? Cause right now i must use aosp rom but there are some features missing like sony themes and others

Yotaphone 2 soft bricked, step-by-step help

Yotaphone2 from china
YD206-> YD201
android 4.4.3-> Firmware 5.0.0-EU1.187a.zip
Hello, first post!
I bought my first android phone and ofcource tried to upgrade it to Android 5.0 Lollipop using yotaphone flasher program. I ended up to a jammed android logo ->softbricked phone..
The problem was finally solved by using fastboot program. You can find it in yotaphone_flasher folder, which you probably already have if you're in this situation.
So I do not recommend trying to update OS using yotaphone flasher, I would use fastboot, it is easier than you think and above all it seems to be the safest way to update as fas as i know.
If you want to know more about the fastboot: https://forum.xda-developers.com/showthread.php?t=2277112
This is a walkthrough made by androidnoob. Use at your own risk:
Download yotaphone flasher if you don´t allready have it: ftp://fw.ydevices.com/YotaPhone2/YotaPhoneFlasher/
Install yotaphone_flasher.exe and use it to download the firmware.
The default folder is C: Program Files (x86) / yotaphone_flasher, in that folder you will find fastboot.exe and firmware folder.
Copy the following files from the firmware folder to yotaphone_flasher folder (same folder you have fastboot.exe), you will need them later in the updating phase:
userdata.img
system.img
boot.img
Make sure that Yotaphone 2 is in downloading mode:
Simultaneously press the power + vol down until the display reads downloading. It may take more than one reboot so keep pressing until it appears.
Connect your phone to a computer via USB Cable.
Open the fastboot.exe. You can only do it in the command prompt, so press shift + right mouse at yotaphone_flasher folder-> Choose to open a command prompt. (Now you have to press enter after every command line)
In the command prompt, type the following:
fastboot
fastboot devices
If you see your phone's serial number, the connection works.
Start wiping memory, type:
fastboot erase system -w (this will erase everything, including your user data)
fastboot erase boot
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Yotaphone 2 will reboot. Wait 5-30 minutes, and the update is complete! Later my phone automatically updated 5.0.0-EU1.124b, so you can probably download this firmware using yotaphone flasher at the beginning of this process. I haven´t yet installed a sim so no idea if there are more issues.
This walkthrough has been compiled from various sources, so thanks to all for sharing! Hope this helps someone in trouble.

Yes, you can update your phone using manual fastboot commands. For convenience, a 4pda user rewrited YotaFlasher to a more polished version, making it flash system fastboot flash -S 512M system system.img command. I uploaded the new YotaFlasher in this guide.

You saved my day, the other methods did not work, I must add that it must be exclusively with the original cable, the others still with the error of "powered by android"

sotka said:
And it´s time to install the update, type:
fastboot flash userdata userdata.img
fastboot flash -S 512M system system.img (For me installing in parts was a game changer. It´ll take some time so don´t panic)
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Hi, Could you tell me how to install the system.img in parts? I have a 1.4gb system.img file that I am trying to install on a bootlooping Yotaphone 2.
I keep getting a "Invalid sparse file format at header magi" when I do the second step, which I think is linked to the .img being too large. But I have no idea how to make it smaller. Thanks for any help!