I need help.
I manage to install TWRP via :
Fastboot flash boot twrp.img
But i can't boot on it don't know why.
I install LineageOS recovery and it boot well !!
Tell me if there a command to flash or type for booting it.
Thanks.
Code:
Fastboot boot "name of your twrp.img"
no quotes
Related
hello i try to flash a rom and i see in some web
that i can to do this with this command :
fastboot flash boot boot.img
but i confused and write
fastboot boot boot.img
now i try to enter to recovery of twrp and i cant it just show me black screen :crying:
someone help me plz.
You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
tamir20121 said:
hello i try to flash a rom and i see in some web
that i can to do this with this command :
fastboot flash boot boot.img
but i confused and write
fastboot boot boot.img
now i try to enter to recovery of twrp and i cant it just show me black screen :crying:
someone help me plz.
Click to expand...
Click to collapse
stathis95194 said:
You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
Click to expand...
Click to collapse
i succed to flash recovery but now all i try to do its write:
E:Unable to mount '/cache'
tamir20121 said:
i succed to flash recovery but now all i try to do its write:
E:Unable to mount '/cache'
Click to expand...
Click to collapse
Try to fastboot erase cache and reboot
stathis95194 said:
You flashed boot.img in the recovery partition.
Download your preferred recovery and flash it with the command:
fastboot flash recovery recovery.img
you will be good to go
Click to expand...
Click to collapse
I didn't see him mention anything about recovery. He booted the boot.img there by he would only "simulate" a boot so to speak, not?
Kinda like:
Building and booting Nexus 5 kernel
Excerpt from posted link:
Code:
$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ adb reboot bootloader
$ sudo fastboot boot boot.img
During this commands your phone will reboot to bootloader mode, next using fastboot command you'll copy the new boot image to RAM of the phone and then boot it. YOUR FLASH IS NOT TOUCHED IT'S 100% SAFE! Now just check in settings, what is version of your kernel. When you've done with hacking, and want to have the original just reboot your phone.
Click to expand...
Click to collapse
He could have just restarted the phone and flashed it properly. Maybe doing that is like booting a "virtual" copy of the Kernel on the device for testing purposes?
Either way though, it's just for the sake of interest/education, if anything else. :good:
thx for the help i succed
Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Try
fastboot flash recovery twrp.img
elwholo said:
Hello whenever i try to use the fastboot boot twrp.img command on adb the img wont load it gets stuck on the fastboot logo.
Click to expand...
Click to collapse
Rename ur boot image file to twrp.img
And then in adb type
1. fastboot devices (see if you are connected or not... If connected type 2nd command)
2. fastboot flash recovery twrp.img
After that by using power up button navigate to RECOVERY MOD and press power key
DONE
U will be running twrp recovery
flash magisk via recovery to maintain root
Enjoy
hello everyone!
I wanted to root my phone but i couldn't manage even if the way should be quiet easy...
-bootloader already unlocked
-debug usb on
downloaded twrp 3.2.3-0 sagit
“fastboot devices”
“fastboot flash recovery recovery.img“
“fastboot reboot”.
i didn't get any errors...
if i try this command: "fastboot boot recovery.img " the phone restart and stay in loop mode...
volume(+) + power keep giving me the stock mi recovery :crying:
MIUI 10
i tried this procedure several times without any result...
Instead of fastboot reboot do fastboot boot recovery name.img and install something
Oreo tastes better with Mi6
worked with twrp 3-2-1-1, but works only if i lunch it via shell
OOS 5.1.4 boots fine, TWRP doesn't ("remote: Failed to load/authenticate boot image")
Hello,
I am trying again from my previous post.
Context: I used TWRP by "fastboot boot twrp.img" without problems for many months. OOS 5.0.4 (Android 8.0). Was rooted using Magisk. Then I updated using OTA to 5.1.4 (Android 8.1) by accident. Had a pattern at the time. OOS 5.1.4 boots fine, I can use the phone. But now "fastboot boot twrp.img" fails.
The phone works fine, but without booting TWRP I can't root (or do any other updates/backups).
Details: I reboot into bootloader (the menu with red/yellow letters on top). I try "fastboot boot twrp.img" and just get stuck for 10s while the warning is on screen that my bootloader is unlocked. Then I drop into a black screen with "1+ fastboot" prompt. If I try "fastboot boot twrp.img" there again, I get error "remote: 'Failed to load/authenticate boot image: 00000050'".
I've tried removing the pattern, and different TWRP images:
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
twrp-3.2.3-0-20181031-codeworkx-dumpling.img
twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img
twrp-3.2.3-1-dumpling.img
twrp-3.2.1-1-dumpling.img
Someone elsewhere suggested to flash TWRP into recovery. But given that I can't even boot TWRP, I am weary of doing this. It seems like a way to just kill the stock recovery.
Please help!!
Use 'fastboot boot filename.img' not flashboot
Bump121 said:
Use 'fastboot boot filename.img' not flashboot
Click to expand...
Click to collapse
Thank you for responding! You are right of course.
That was actually a typo in my post, I meant to write "fastboot boot twrp.img". fastboot is the command I used, flashboot doesn't exist (that I know of). My mind was probably thinking of "fastboot flash", which I am scared to do since I can't even get TWRP to boot. I will edit the post now.
znarg said:
Thank you for responding! You are right of course.
That was actually a typo in my post, I meant to write "fastboot boot twrp.img". fastboot is the command I used, flashboot doesn't exist (that I know of). My mind was probably thinking of "fastboot flash", which I am scared to do since I can't even get TWRP to boot. I will edit the post now.
Click to expand...
Click to collapse
Then Do One Thing (This will wipe all of your data)
go to fastboot and type all these one by one
1. fastboot erase cache
2. fastboot format cache
3. fastboot erase system
4.fastboot format system
5.fastboot erase userdata
6.fastboot format userdata
after running all these commands one by one all you need to do is reboot to fastboot again, then boot the .img file.
This Time I Guess It Will Work.
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)