Moto Z2 Force: Can´t boot into TWRP from fastboot mode - Moto Z2 Force Questions & Answers

Hey, I wanted to install TWRP recovery on my Moto Z2 Force. I wanted to boot into twrp.img which I have in the Minimal ADB & Fastboot. But always if I run the "fastboot boot twrp.img" it fails and I don´t know why. On my friends PC it always works (when I installed Custom ROMS or rooted my phone and stuff like this) but on mine it doesn´t. Can someone tell me, why I can´t use fastboot commands with my cmputer? I´ve reinstalled all the USB drivers, the Minimal ADB & Fastboot app or whatever it´s called.
Btw, this is, how my CMD looks like after I´ve put in the command:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY224ZCKZN fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
FAILED (remote: unknown command)
finished. total time: 0.003s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I´ve spent hours to find out what the problem is but I just cant figure it out. Does anyone have some ideas, what I should do?
Aaron

Off the top I'd say that unless you've renamed your twrp.img to "twrp.img" and it resides in your Minimal ADB folder then it just doesn't have the correct path or filename.
Try
PHP:
fastboot boot 'Drag n Drop twrp.img here'

Related

Bricked Kindle, bought factory cable, got to stay in fastboot, then bricked it again

I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"
Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Hmmm did you try the kfu or the kindle fire unbrick utility?
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s
When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.

help me to flash twrp

this is happening i did all step by steps but whole day i tried many drivers and ways to make it flash but nothing.Please help
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (22) doesn't match this client (35); killing...
* daemon started successfully *
LGH815ba365ed2 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
< waiting for any device >
iko84 said:
this is happening i did all step by steps but whole day i tried many drivers and ways to make it flash but nothing.Please help
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (22) doesn't match this client (35); killing...
* daemon started successfully *
LGH815ba365ed2 device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
< waiting for any device >
Click to expand...
Click to collapse
Again a windows driver problem? You should better switch to Linux.
For the moment:
Download Ubuntu install it on a stick and boot it.
Install adb tools and fastboot there and no driver issues anymore!
There are many guides how to make that. Search by google to find them.
And you said you read everything: but you missed the official guide. Read the installation steps from the official twrp thread (see my sig) --> fastboot flash will not work!
.

[ask]devices not show in fostboot mode

nignt,
usb debugging ON.
in normal mode in command prompt if " adb devices" device show :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
635a7750 device
but if in fastboot mode :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
device not show...
what wrong ??
sorry my english
update
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
635a7750 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
635a7750 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull /sdcard/TWRP TWRP
adb: error: connect failed: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
why even adb pull, device not found ?
device in fastboot mode
ajegile said:
update
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
635a7750 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
635a7750 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>adb pull /sdcard/TWRP TWRP
adb: error: connect failed: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>
why even adb pull, device not found ?
device in fastboot mode
Click to expand...
Click to collapse
Try to change the USB port of your computer...
bayad said:
Try to change the USB port of your computer...
Click to expand...
Click to collapse
change port same problem...
Have you try reinstalling android driver on your computer?
Sent from my LEX727 using Tapatalk
phidung3721 said:
Have you try reinstalling android driver on your computer?
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
working ...thx

Install TWRP and then to root.

Hello please can anyone advise me and forgive any wrong terms..
I am trying to push twrp to my lg g4 H815 20g using adb and fastboot but everytime it comes back with
error: cannot load 'twrp.img': No such file or directory
PS C:\Users\Anthony\Desktop\ADB>
i have tried renaming twrp file to various things and changing the command fastboot flash twrp.img or fastboot flash recovery.img
but i keep getting errors of one discription or the other..
I have followed guild after guild but still not made the magic happen..
Bootloader is officially unlocked via LG and twrp for lg g4 downloaded from twrp site.
Been trying for two days to install a recovery so i can also root but having no luck.
please any help or advise would be appreciated..
you must put the "twrp.img" into to your "ADB" folder and then exec this:
Code:
fastboot flash recovery twrp.img
Hi thanks for your help
yes I have the img file in adb/fastboot folder and been doing this and still comes back in cmd as no such file etc..
Tried renaming twrp img file and changing fastboot flash line to match but still no joy..
Tried earlier g4 twrps same outcome it’s as if downloaded recovery’s are corrupt or something as they don’t appear to be being seen..
What is best name for the twrp image or do you leave it as it came downloaded and run the
fastboot flash recovery twrp.img Regardless of what twrp called when downloaded..
Thanks
Have you changed directory to the sdk folder? Or shift + right clicked in folder "open cmd here"?
The command is "fastboot flash *whatever recovery is called in adb folder*"
I ended up changing the name to "twrp3.1.1" or whatever cause it had a hell of a name when downloaded. Just name whatever you want as long as you call it same thing when flashing.
Make sure you also have a copy of it on your SD too because it wont stick and when you reboot to the recovery you then need to reflash the image from in there.
Hi I think it was successful i changed name of twrp on second attempt and it seemed to work..
only problem was when i tried to manually boot into recovery via volume down and power i did something wrong and accidentally reset the dam thing instead of booting into twrp......will have to do it all over again but hopefully i have it sorted..
PS C:\ADB> adb reboot-bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
PS C:\ADB> fastboot flash recovery twrp.img
error: cannot load 'twrp.img': No such file or directory
PS C:\ADB> fastboot flash recovery twrp-3.1.1-1-g4.img
target reported max download size of 536870912 bytes
sending 'recovery' (33952 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.219s
PS C:\ADB> fastboot reboot
rebooting...
finished. total time: 0.031s
PS C:\ADB>
Hello! I reopen this tread.. I have an issue with flashing twrp, via adb I start into bootloader, but when i put the command to flash it.. <waiting for device>. Why?

Nokia 3.2 Europe version stuck in bootloader

Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
Thanks
same bro idk how to fix it could someon please help?
try the next command
fastboot getvar current-slot
Click to expand...
Click to collapse
if it says _a or _b then its good and you should be able to flash images if it says unknown you should try the command
fastboot set_active=a
Click to expand...
Click to collapse
edit: second command was wrong should now work.
thegamingcat13 said:
try the next command
if it says _a or _b then its good and you should be able to flash images if it says unknown you should try the command
edit: second command was wrong should now work.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot: b
finished. total time: -0.000s
second command not working
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active=a
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Phone stuck in fastboot
does anyone have recovery files for nokia 3.2 or stock image
my nokia 3.2 bootloader version is blank. how can i recover from this. i am stuck
Anyone has got a solution for this?
just flash it via fastboot and all will be well. just use fastboot flash boot boot.img, fastboot flash system system.img. with this format you'll be able to boot your phone again.
I have the same problem.I was in twrp and i tapped on recovery and now every time i want to exit to my system,i go back to the bootloader and for about 2 hours i was trying to fix this and now i did the fastboot oem lock and im on the screen where i need to lock my bootloader and i tried to go up or down but the buttons dont work,anybody got an acutal solution for this?
smure said:
just flash it via fastboot and all will be well. just use fastboot flash boot boot.img, fastboot flash system system.img. with this format you'll be able to boot your phone again.
Click to expand...
Click to collapse
how do you do that?
smure said:
does anyone have recovery files for nokia 3.2 or stock image
Click to expand...
Click to collapse
here you go https://gsmusbdriver.com/nokia-3-2
hi, I have here a Nokia 3.2 stuck in bootllop,
I tried to wipe/factory reset from recovery menu, but I still get a bootloop?
I have not even enabled developer settings from it.

Categories

Resources