HELP:
MY bootloader is bad. i want to flash it with usbboot .
but seems something wrong.
[email protected]:~/kf$ sudo ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
< waiting for device >
i don't know what wrong?
pls help me......
USBboot means you need to either change the bootmode to USBboot (4003) or pull the back off and perform the "shorting trick". Your device must be in the USBboot mode for tools like firekit and rekindle to work.
soupmagnet said:
USBboot means you need to either change the bootmode to USBboot (4003) or pull the back off and perform the "shorting trick". Your device must be in the USBboot mode for tools like firekit and rekindle to work.
Click to expand...
Click to collapse
IN fact, I still don't know why this happen:
sending image to target...
< waiting for device >
always waiting.....
bournezhang said:
IN fact, I still don't know why this happen:
sending image to target...
< waiting for device >
always waiting.....
Click to expand...
Click to collapse
That's good. The < waiting for device > means that the usbboot command completed successfully. At that point you should see the screen light up with the FireFireFire triangle.
So what could it be? If FFF isn't starting, you've got real hardware problems. I'd suspect bad RAM, which is pretty much the kiss of death considering that it's soldered on top of the OMAP.
But I doubt that's what's happening here. Looking at you're command line, you're executing two separate commands (the ; operator). Breaking that down to two lines, you get:
$ sudo ./usbboot aboot.bin u-boot.bin
$ ./fastboot boot twrp-blaze-2.0.0RC0.img
Oh noes, you're running as a non-root user in the 2nd command! Unless you've made udev rules, the fastboot command won't have permissions to use the USB interface.
You can fix this by first doing sudo su to become root, putting sudo before the ./fastboot, or grouping them into one command:
sudo bash -c "./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img"
This is why the Firekit docs ask you to become root first.
pokey9000 said:
That's good. The < waiting for device > means that the usbboot command completed successfully. At that point you should see the screen light up with the FireFireFire triangle.
So what could it be? If FFF isn't starting, you've got real hardware problems. I'd suspect bad RAM, which is pretty much the kiss of death considering that it's soldered on top of the OMAP.
But I doubt that's what's happening here. Looking at you're command line, you're executing two separate commands (the ; operator). Breaking that down to two lines, you get:
$ sudo ./usbboot aboot.bin u-boot.bin
$ ./fastboot boot twrp-blaze-2.0.0RC0.img
Oh noes, you're running as a non-root user in the 2nd command! Unless you've made udev rules, the fastboot command won't have permissions to use the USB interface.
You can fix this by first doing sudo su to become root, putting sudo before the ./fastboot, or grouping them into one command:
sudo bash -c "./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img"
This is why the Firekit docs ask you to become root first.
Click to expand...
Click to collapse
thanks a lot. feel very grateful
Breaking that down to two lines-------------still < waiting for device >,with yellow riangle
putting sudo before the ./fastboot------still < waiting for device >,with yellow riangle
fastboot can't work by breaking or with sudo before it
i also fell very strange that when i push the usb into mainboard, with usbboot, the screen lighted with yellow riangle,still< waiting for device >
the fastboot don't work but KF can get into the system --------still< waiting for device >
then i trun off the KF,still can't power on it ,as before .
bournezhang said:
thanks a lot. feel very grateful
Breaking that down to two lines-------------still < waiting for device >,with yellow riangle
putting sudo before the ./fastboot------still < waiting for device >,with yellow riangle
fastboot can't work by breaking or with sudo before it
i also fell very strange that when i push the usb into mainboard, with usbboot, the screen lighted with yellow riangle,still< waiting for device >
the fastboot don't work but KF can get into the system --------still< waiting for device >
then i trun off the KF,still can't power on it ,as before .
Click to expand...
Click to collapse
Welcome back to life, your kindle. That yellow triangle is fastboot. Now you should be able to issue fastboot command.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
same thing happened to me today..i issued commands and it stucked on yellow triangle.and waiting for device..
then i turned off the fire.but now its not powering on..
i think i will have to do it again and when yellow triangle comes up.i have to issue fastboot command.but waiting for device have to resolve first..
linktohack said:
Welcome back to life, your kindle. That yellow triangle is fastboot. Now you should be able to issue fastboot command.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
Click to expand...
Click to collapse
but why i cant use fastboot at the yellow triangle.
i am stucked at waiting for device
i bricked my kindle when i factory resetted with cwm recovery and it stucked at formatting/data
then i powered off the device by pressing down the power button for 20 seconds.then i pressed power button and it did''nt booted up..
now i have installed firekit live usb and issued the command for usb_fix_install_fff_twrp
and plugged the device.
device powered on and in terminal it was showing that
sending 2nd stage to target
waiting for 2nd stage response
sending image
fixing paritiions
and its showing waiting for device
and i stucked there for 30 minutes but nothing happened.then i unplugged the kindle and powered it off
i have issued every command listed on the terminal
one thing is that i have not transferred any fff bootloader,twrp or rom file to root of drive..
should i transfer the files it requires like twrp,fff,or roms
now what should i do for getting my kindle to life
i have tried this for about 4 to 5 times with no success..
have u solved ur problem or not plz reply or i should throw my kindle in trash
shantam said:
have u solved ur problem or not plz reply or i should throw my kindle in trash
Click to expand...
Click to collapse
send to AMAZON ，change a new one.
I have solved, with sudo su before the command .
hope can help you
bournezhang said:
send to AMAZON ，change a new one.
I have solved, with sudo su before the command .
hope can help you
Click to expand...
Click to collapse
my device gets on fix_usb_parts_install_fff_twrp command
but it stucked at waiting for device
so u solved ur problem
what steps u did
should i transfer the twrp image to root of usb drive
and what commands should i type
please reply asap..
shantam said:
my device gets on fix_usb_parts_install_fff_twrp command
but it stucked at waiting for device
so u solved ur problem
what steps u did
should i transfer the twrp image to root of usb drive
and what commands should i type
please reply asap..
Click to expand...
Click to collapse
in linux system，with sudo su before the command：
like this "sudo su ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img"
SO $ sudo ./usbboot aboot.bin u-boot.bin change to # sudo ./usbboot aboot.bin u-boot.bin
$-- # the different
means you should get the su permission
hope help， can't post on time because I FROM CHINA
wont work
i installed ubuntu 13.04 and have the files in the downloads folder i give su permission and sudo ./usbboot aboot.bin u-boot.bin; ./fastboot bootrecovery.img and says it cannot execute usbboot or fastboot and no file or directory found.
please help im trying to install twrp recovery and upgrade the system to a custom rom and i have no factory cable so im trying with the short trick.
thanks
Hey y'all,
I am rooting / rom-ing my third KF.
I could not get TWRP to install so I installed CWM that comes with the KFU
I installed Jandycane and the most current gapps
From then on, the Kindle gets stuck at the boot animation
I have tried other options in KFU, but everything involving fastboot does not work. The kindle shows up as a composite device in the device manager, and is able to be adb-ed into.
In KFU, I see the bootmode being 4000. When I tried the idme command to change it to recovery, it told me that it could not accept the idme command.
I've tried going using the adb shell to push fiels and create directories, but have failed. Su does not work, mkdir does not work, and chmod does not work.
Additionally I have tried the KF Unbrick 1.1 and none of the options seem to do anything.
I am running out of options here. I have tried these procedures on two PCs without avail.
Before I installed the current rom, I have made a backup of the stock rom. Is there any way I could adb into the device and restore it? Would this be a valid way to fix this up?
Can anyone suggest anything else that I have not tried?
Anyone?
When I try to push fbmode from here: http://forum.xda-developers.com/showthread.php?t=1414832
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb push fbmode /data/local/tmp
failed to copy 'fbmode' to '/data/local/tmp': No such file or directory
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
Now lets see if I can escalate my privileges
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ su
su
Segmentation fault
[email protected]:/ #
Now lets see if I can push fbmode regardless
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
/system/bin/sh: cd: /data/local/tmp: No such file or directory
2|[email protected]:/ $ cd /data/local/
cd /data/local/
/system/bin/sh: cd: /data/local: No such file or directory
2|[email protected]:/ $ cd /data/
cd /data/
[email protected]:/data $ ls
ls
opendir failed, Permission denied
255|[email protected]:/data $
So much for adb ... how about that fastboot
Every time I do anything with fastboot it says waiting for device:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot -i 0x1949 flash recovery twrp.img
< waiting for device >
Are there any devices showing?
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot devices
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
fastboot does not see any devices whereas adb does...
I have tried sending the fastboot command while the device is off and then turning it on. The kindle just hangs at the kindle fire screen.
EDIT: I switched computers, and it got back into previous state at being stuck at the animation screen
This is what happens when I try to install TWRP in KFU:
Code:
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No such file or directory
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
kinfauns said:
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
Click to expand...
Click to collapse
That would make sense. I cannot change the bootmode from 4000, so that's why fastboot does not work. I feel dumb for not thinking this through.
It has CWM installed as I could not load TWRP initially due to a poor connection.
This is what I get when I try to change the bootmode:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell su -c 'idme bootmode 4002'
Segmentation fault
<idme> write 4002 to offset 0x1000
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell idme bootmode 4002
<idme> Invalid permission
I cannot get into recovery as I cannot get the tablet to boot into anything but the ROM istelf (or try to, as it never boots into anything but just loops the boot animation)
Tell me about this factory cable. I'm sure I have it somewhere among all of my micro USB cables...
The boot pattern is as follows: kindle fire (white orange/stock) -> jandycane boot animation that runs forever
There is no triangle or any press the power button to boot into recovery.
http://forum.xda-developers.com/showpost.php?p=30376760
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30376760
Click to expand...
Click to collapse
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Yes, if you have a working adb, you can absolutely push those files. The path will be slightly different though. Instead of ~/local/tmp, you will push the files to /data/local/tmp then execute:
Code:
adb shell chmod 755 /data/local/tmp/rcmode
adb shell /data/local/tmp/rcmode
Looking through your other posts I see you are trying to invoke the shell and enter the commands seperately. Try again, but only this time add "adb shell" to the command itself, as above, and see if that makes a difference.
Also, I've seen both /data/local and /data/local/tmp used but I've always used /data/local/tmp
[Edit:] if you still get a "No such file or directory" error, see if you can create it:
Code:
adb shell mkdir /data/local/tmp
Zlatty said:
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Click to expand...
Click to collapse
KFU's included version of CWM recovery does not flash ICS (and very likely JB) ROMS correctly. This is a bug known to corrupt the flash.
It not likely you'll be able to do anything meaningful with the system currently installed on your Kindle Fire. Unfortunately for you, that probably includes using idme or pushing anything that might help you change bootmodes. Of course, I may be wrong and you might find another way out of the mess, but the easiest way for you to fix this is to use a factory cable, put the KF into fastboot mode, flash TWRP, boot into recovery so you can flash a new bootloader and ROM.
factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
beginner's guide...
http://forum.xda-developers.com/showthread.php?t=1552547
supplement for rooting... installing a ROM... etc...
http://forum.xda-developers.com/showthread.php?t=1638452
EDIT: You can try what soupmagnet suggested while I was typing out my post, but you've already shown that you cannot access the /data partition. I think it's going to be something more than simply just an unmounted partition.
I hadn't really thought about mounting the data partition...it's worth a shot either way.
soupmagnet said:
I hadn't really thought about mounting the data partition...it's worth a shot either way.
Click to expand...
Click to collapse
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
Click to expand...
Click to collapse
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Zlatty said:
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Click to expand...
Click to collapse
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Zlatty said:
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Click to expand...
Click to collapse
I could not get twrp to boot into normal. So I used KFU to change to 4000 mode.
Code:
***********************************************
* Activating Normal (4000) *
***********************************************
< waiting for device >
... OKAY [ 0.081s]
finished. total time: 0.082s
rebooting...
finished. total time: 0.001s
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
Everything went better than expected.... w00t!
Money. $$$$$$$$$$$$$$$$$$$$$$
I need HELP in de-soft-bricking my Moto Play G7 and installing the /e/ project (or perhaps other Linux-based build), and I am willing to PAY for tech support to walk me through it (ideally via Skype or Zoom platform). Here are a few more specifics:
I bought a used Moto G7 Play that was updated by a developer from Android 9 to Android 10. I followed tutorials to unlock the phone and install TWRP via ADB but ran into problems, as far as I can tell, due to the Motorola A-B slot issue (it says "No bootable A/B slot, failed to boot Linux, falling back to fastboot" when I try to reboot). I can no longer recover the phone to Android or reset it to "factory" settings via the bare-bones Android and Motorola phone menus, but I remain able to issue commands via ADB / USB and also navigate to the G7's bootloader menus by using the buttons on the side of the phone. As for my PC platforms, I am running Win 10 (with ADB) but I also have Ubuntu running (so I could format SD cards to ext4 if that would help), and I have Android studio installed (not as if I know what to do with it), if that would be of any help. As far as I can tell, ADB and the Motorola USB drivers are working fine, and I USUALLY get positive indication when I type "adb devices", and I can always get the phone to acknowledge that the USB is connected/disconnected.
I don't know if this will help, but as I try to do the ADB sideload for copy-partitions.zip, this is where things don't work, as my Moto G7 play screen says:
Finding update package…
Opening update package…
Verifying update package…
E:footer is wrong
Update package verification too 0.2 s (result 1).
E: Signature verification failed
E: error:21
Installation aborted.
From there, it seems I can't go on to flash the TWRP image. Any ideas how I can work past these problems? Let me know how I can contact you via the forum and we can work $omething out. I'm guessing that this is a fast fix for someone who knows what they are doing. I'm sick of google and don't want to accept defeat! Thanks, -Andrew
Try the motorola rescue assistant
When it not workling download for your device the firmware
Instead of flashing TWRP, have you tried just booting TWRP w/o flashing?
fastboot boot twrp.img
I ran into some problems with my Moto G7 Play; I didn't softbrick it, but several things fought back, so I'll pass along what may get you back on track. First of all, I cannot use Linux to connect via fastboot, so I had to use a Mac, you can use your Windows box. Secondly, TWRP does not officially have a version for the G7 Play. I used an unofficial one from an XDA forum member HERE. It only offers a black screen unless you flash dtmo.img. I didn't want to flash dtmo.img, so I just used the black screen and used adb commands to install Lineage (and /e/) via TWRP command line.
The steps are pulled from another XDA posting showing how to use TWRP command line:
1. Connect the phone in fastboot mode to the PC, run fastboot devices to make sure it is connected.
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache << will not work on Moto G7 Play, but won't hurt anything.
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\lineage-xyz.zip
IF THE TWRP commands do not work and hang saying something about "starting TWRP", I discovered by looking at the log in /tmp that /sdcard is encrypted. You will need to unencrypt /sdcard and I'm not sure how to do that without recovery; I'm sure there is way, though.
If I were you, I would see if you can flash LineageOS (or lineageOS + microG) with this method to get your phone back working, then you can move on to /e/. Note that if this works, you will have a recovery program available (the standard Lineage recovery), which has some basic tools. You CAN ONLY load Lineage-signed roms with this recovery. So if you want to switch from lineage to /e/ or to lineage+microG, you will need to use the twrp method above to switch to the other rom. Then you can use the lineage or /e/ recovery to install lineage or /e/ updates from the same publisher.
Also, if you install stock lineage, don't use a bleeding edge version. Pick one from mid-October so if you decide to switch to /e/ or Lineage+microG you will not be downgrading because they don't make nightly builds. It probably won't hurt since downgrading a week probably has few changes, but just in case.
Hope this helps.
maw1 said:
Try the motorola rescue assistant
When it not workling download for your device the firmware
Click to expand...
Click to collapse
I tried the Motorola Device Manager tool. Not sure if I made a good backup to begin with, and now I try to open the tool it doesn't seem to do anything.
xtermmin said:
Instead of flashing TWRP, have you tried just booting TWRP w/o flashing?
fastboot boot twrp.img
Click to expand...
Click to collapse
Tried that... It says it FAILED.
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.427s]
booting...
FAILED (remote failure)
finished. total time: 1.054s
Exinu said:
I ran into some problems with my Moto G7 Play; I didn't softbrick it, but several things fought back, so I'll pass along what may get you back on track. First of all, I cannot use Linux to connect via fastboot, so I had to use a Mac, you can use your Windows box. Secondly, TWRP does not officially have a version for the G7 Play. I used an unofficial one from an XDA forum member HERE. It only offers a black screen unless you flash dtmo.img. I didn't want to flash dtmo.img, so I just used the black screen and used adb commands to install Lineage (and /e/) via TWRP command line.
The steps are pulled from another XDA posting showing how to use TWRP command line:
1. Connect the phone in fastboot mode to the PC, run fastboot devices to make sure it is connected.
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache << will not work on Moto G7 Play, but won't hurt anything.
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\lineage-xyz.zip
IF THE TWRP commands do not work and hang saying something about "starting TWRP", I discovered by looking at the log in /tmp that /sdcard is encrypted. You will need to unencrypt /sdcard and I'm not sure how to do that without recovery; I'm sure there is way, though.
If I were you, I would see if you can flash LineageOS (or lineageOS + microG) with this method to get your phone back working, then you can move on to /e/. Note that if this works, you will have a recovery program available (the standard Lineage recovery), which has some basic tools. You CAN ONLY load Lineage-signed roms with this recovery. So if you want to switch from lineage to /e/ or to lineage+microG, you will need to use the twrp method above to switch to the other rom. Then you can use the lineage or /e/ recovery to install lineage or /e/ updates from the same publisher.
Also, if you install stock lineage, don't use a bleeding edge version. Pick one from mid-October so if you decide to switch to /e/ or Lineage+microG you will not be downgrading because they don't make nightly builds. It probably won't hurt since downgrading a week probably has few changes, but just in case.
Hope this helps.
Click to expand...
Click to collapse
Thanks for the effort, Exinu, but it seems to not fully recognize the command or is looking for another flag or operand. The "set_active b" command that you proposed just results in making a list like for a "help" or unspecified command. As you can see below, I tried other variations of the command after I tried searching out more details. I also tried "fastboot set_active=b" and it does the same thing with the listing. I'm assuming that it's not accepting this command. I did try the twrp-dirtyport image as well, but as you can see below, that created an error as well:
C:\adb>fastboot --set_active b
fastboot: unknown option -- set_active
C:\adb>fastboot --set-active=b
fastboot: unknown option -- set-active=b
C:\adb>fastboot set_active b
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\adb>
I did try the next step with the dirtyboot but that seem to have failed as well.
C:\adb>fastboot boot twrp-dirtyport-g7play.img
downloading 'boot.img'...
OKAY [ 0.570s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.566s
On my phone on the "Bootloader logs" screen, it said (before I began)
Start Up Failed:Your device didn't stat 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)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB Connected
I then typed fastboot devices from my windows C:\ADB prompt and it showed me it was connected.
After running the stuff mentioned above, it said:
cmd: download:01348000
cmd: boot
Incomplete boot image for booting.
I disconnected and reconnect the USB and then I tried the fastloading of the dirtyport image again. The screen went blank and said the same stuff again with no bootable A/B slot, which leaves me to believe this is where my problem starts.
Any other ideas?
Any ideas
I think you may have several issues that need to be fixed one step at a time. First, I think you have an old fastboot if it doesn't recognize the set_active command. Go to this link: https://developer.android.com/studio/ and scroll down to the section labeled "Command Line tools only" and download the command line tools. Make sure you are in that directory in Windows so you are running the newer version and not the old version installed. If you run "fastboot --help" you should see set_active as an option.
Next, where did you get the TWRP? Go to the link I provided, which has a (black screen) TWRP that I have used and it works. Start from there and see how things proceed.
Exinu said:
I think you may have several issues that need to be fixed one step at a time. First, I think you have an old fastboot if it doesn't recognize the set_active command. Go to this link: https://developer.android.com/studio/ and scroll down to the section labeled "Command Line tools only" and download the command line tools. Make sure you are in that directory in Windows so you are running the newer version and not the old version installed. If you run "fastboot --help" you should see set_active as an option.
Next, where did you get the TWRP? Go to the link I provided, which has a (black screen) TWRP that I have used and it works. Start from there and see how things proceed.
Click to expand...
Click to collapse
I got the TWRP from the link that you provided. As for running "fastboot --help", I did not see the "set_active" flag listed as an option (results pasted below). I also tried to download the command line tools as suggested, but not positive as to which directory they are to reside in, or which of the files I should launch. I unzipped the commandlinetools directory (in my adb directory) and tried running the sdkmanager.bat batch file which was nested in one of the subdirectories (it briefly opened and flashed a window but seemed to do nothing more). Not sure if this matters, but I also have android studio installed, although I am not sure how or where the "set_active" command comes from. I tried downloading windows latest PowerShell, and have also tried CMD as adminstrator. From my searching, I see people using "--set-active" with android commands as well, but I really don't know if this is a MS/DOS based command that is used for controlling drives and partitions on the Windows system, or if it's an adhock SDK - Linux add-on command of sorts. I can't seem to find much info on the command.
This is how it reads:
PS C:\adb> fastboot --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>
PS C:\adb> set_active
set_active : The term 'set_active' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ set_active
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (set_active:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Any other ideas?
The command-line tools download should not require any installation; at least, the Mac version did not. Unzip the file to your desktop. Then open a command prompt which should open in c:\Users\your_user . Enter "cd Desktop" to change to the Desktop folder, then cd <foldername> to change into the folder you unzipped the files into. Windows will sometimes unzip a folder into a second folder, so you may need to cd <foldername> once more. In any case, enter "dir" to make sure you see files like fastboot.exe, adb.exe, etc.
In Windows, when you type a command it will first look to your current directory and run the exe file that exists there, if it exists. If it does not, then it starts looking for the command in your %PATH% environment variable. That's why you need to "cd" to the tools directory: when you run "fastboot", you want it to run fastboot.exe in that directory, and not the old fastboot.exe that is installed somewhere on your system.
It sounds like you haven't worked with the command line much; I suggest you go through some tutorials on basic command line usage for both Windows and Linux; it will make tinkering with computers and phones much easier. And set_active is not a DOS/Windows command, it is parameter you are passing to fastboot.exe to tell it what action you want it to do; it just also calls these actions "commands". So when you typed c:>set_active, you told Windows to find a file called set_active.exe and run it. That file does does not exist, so it did not work.
Quick note: the Unix command line will not run a command from the current directory for multiuser security reasons; you need to specify the current directory (dot) and a slash on the command like this: ./fastboot
This will also work with DOS/Windows, but usually the backslash is used instead of the forward slash, for very old historical reasons.
Exinu said:
The command-line tools download should not require any installation; at least, the Mac version did not. Unzip the file to your desktop. Then open a command prompt which should open in c:\Users\your_user . Enter "cd Desktop" to change to the Desktop folder, then cd <foldername> to change into the folder you unzipped the files into. Windows will sometimes unzip a folder into a second folder, so you may need to cd <foldername> once more. In any case, enter "dir" to make sure you see files like fastboot.exe, adb.exe, etc.
In Windows, when you type a command it will first look to your current directory and run the exe file that exists there, if it exists. If it does not, then it starts looking for the command in your %PATH% environment variable. That's why you need to "cd" to the tools directory: when you run "fastboot", you want it to run fastboot.exe in that directory, and not the old fastboot.exe that is installed somewhere on your system.
It sounds like you haven't worked with the command line much; I suggest you go through some tutorials on basic command line usage for both Windows and Linux; it will make tinkering with computers and phones much easier. And set_active is not a DOS/Windows command, it is parameter you are passing to fastboot.exe to tell it what action you want it to do; it just also calls these actions "commands". So when you typed c:>set_active, you told Windows to find a file called set_active.exe and run it. That file does does not exist, so it did not work.
Quick note: the Unix command line will not run a command from the current directory for multiuser security reasons; you need to specify the current directory (dot) and a slash on the command like this: ./fastboot
This will also work with DOS/Windows, but usually the backslash is used instead of the forward slash, for very old historical reasons.
Click to expand...
Click to collapse
Exinu, thanks for your continued assistance. As it turns out the fastboot/adb version I was using didn't include the "set_active" command (I don't think it was a path problem as I was always typing commands from the in directory where the ADB software was downloaded). As I had tried to follow a number of different tutorials of the course of several weeks, some for the G7 play, and perhaps some for the G7 and others generic, I think the place on the web that I went for the original ADB package (or the ADB version) was the problem. I also found another copy of ADB on my drive (downloaded weeks ago) that was titled "Minimal ADB and Fastboot", and as it turns out, that version DID support the set_active operand (from the fastboot --help command). So, I was able to return to your initial directions to set the active partion to b as initially instructed (see below, but the phone also shows that the set_active:b command seemed to process without error). However, I was not able to do the next step of flashing the TWRP. I tried the TWRP version you suggested and linked to (the dirtyport version) and then also the "channel" version, which I understand to be designed for the G7 play, unlike the "river" version. In either case (dirtyport or channel) I get a new/different "usage: unknown command" error, as seen in text pasted below:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active b
Setting current slot to 'b'...
OKAY [ 0.176s]
finished. total time: 0.178s
C:\Program Files (x86)\Minimal ADB and Fastboot>dir
Volume in drive C has no label.
Volume Serial Number is EC2B-BC54
Directory of C:\Program Files (x86)\Minimal ADB and Fastboot
2020-11-27 01:42 PM <DIR> .
2020-11-27 01:42 PM <DIR> ..
2018-01-11 06:53 PM 1,784,320 adb.exe
2018-01-11 06:53 PM 97,792 AdbWinApi.dll
2018-01-11 06:53 PM 62,976 AdbWinUsbApi.dll
2015-08-09 01:50 PM 29,882 cmd-here.exe
2018-01-11 06:53 PM 853,504 fastboot.exe
2020-08-17 02:31 AM 1,456,678 logo.bin
2020-08-15 11:25 PM 27,848,704 twrp
2020-09-03 02:52 AM 27,133,952 twrp-dirtyport-g7play.img
2020-08-16 01:12 AM 17,307,289 twrp-installer-3.4.0-0-river.zip
2020-11-17 04:21 AM 23,298,048 twrp-moto-g7-play-channel-android-10.img
2020-08-15 11:25 PM 27,848,704 twrp.img
2020-11-27 01:27 PM 5,004 unins000.dat
2020-11-27 01:26 PM 717,985 unins000.exe
13 File(s) 128,444,838 bytes
2 Dir(s) 28,010,246,144 bytes free
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot twrp-dirtyport-g7play.img
fastboot: usage: unknown command twrp-dirtyport-g7play.img
Granted, I'm not a command line expert, but I have been playing with computers since the TRS-80 and the C64 and Apple IIe, and 8086 DOS stuff, and used to do QBasic programming as a kid, so in most cases, I can usually navigate myself through some hairy computer instructions to do whatever I need to do, unless the instructions themselves are hairy. I find that the Android Dev forums are predicated upon some knowledge of those platforms and are a rude awakening for those unfamiliar with the development history and architecture. Obviously, I'm going to extremes to try to de-google an Android phone (frankly I would be happier if there was more stuff on the market that already was preinstalled), as this google censorship and proposed contract tracing stuff is just getting out of hand and going too far... so this is my way of fighting back. I'd rather know nothing about ADB, but here I am.
Is there any chance you know how or why I am getting the "fastboot: usage: unknown command twrp..." error above, or how I can resolve it?
You are getting close. Your fastboot entry is a little off. It should be >fastboot boot <filename.img>. If the twrp img file is not in the current directory, you will need to provide the full path.
Exinu said:
You are getting close. Your fastboot entry is a little off. It should be >fastboot boot <filename.img>. If the twrp img file is not in the current directory, you will need to provide the full path.
Click to expand...
Click to collapse
OK, so that was a head-slapping "duh" moment on my end (using fastboot filename.img instead of fastboot boot filename.img). However, now that I've entered the right command I'm still having problems. As you indicate in your post above, the "fastboot boot" command did initiate the sequence, and the screen did go black, however, one of the screens that it went to only said "bad key" at the upper left hand corner.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-dirtyport-g7play.img
downloading 'boot.img'...
OKAY [ 0.575s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 1.580s
As for my phone screen, it goes black and cycles saying "bad key" a few times, and after a few attempts it reverts to the Bootload logs screen, giving the same message it did that I started with.
Start Up Failed
Your device didn't start up successfully.
Use the Software Repair Assistant on computer
to repair your device.
Connect you device to your computer to get
the Software Repair Assistant. AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB Connected
Exinu said:
You are getting close. Your fastboot entry is a little off. It should be >fastboot boot <filename.img>. If the twrp img file is not in the current directory, you will need to provide the full path.
Click to expand...
Click to collapse
OK, I after the "dirtyport" image didn't work, I went out on a limb and tried to flash a different img file, (first doing the set_active b command), typing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-moto-g7-play-channel-android-10.img
downloading 'boot.img'...
OKAY [ 0.496s]
booting...
OKAY [ 0.178s]
finished. total time: 0.679sIt briefly flashed the Moto screen and then went black. After this, with the black screen, it seemed like it was able to the "adb shell" command, although it seemed to not be able to take the TWRP commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
channel:/ # twrp wipe cache
Unable to find partition for path '/cache'
Done processing script file
channel:/ # twrp wipe dalvik
Failed to mount '/data' (Invalid argument)
Done processing script file
channel:/ # twrp wipe system
E:Error with wipe command value: 'system'
Done processing script file
channel:/ # twrp wipe data
Failed to mount '/data' (Invalid argument)
Done processing script file
channel:/ # twrp sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload lineage-17.1-20201129-nightly-channel-signed.zip
Total xfer: 1.00x
After this point it went back to the "bad key" and return to the Bootloger logs screen.
I'm assuming at this point if there is a failure in the TWRP command sequence (as suggested above) I shouldn't expect the latter commands to work. I also attempted to use the moto g7's built-in recovery menu that is available from pushing and holding the power and upper volume button. When I tried to "apply update from ADB" using the phone to initiate the effort, and then typed, C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload lineage-17.1-20201129-nightly-channel-signed.zip, the phone screen read as follows:
Supported APR: 3
Stopping adbd...
Now send the package you want to apply to the device with the "adb sideload ,filename"...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature Update package verification took 45.2 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted.
Exinu said:
You are getting close. Your fastboot entry is a little off. It should be >fastboot boot <filename.img>. If the twrp img file is not in the current directory, you will need to provide the full path.
Click to expand...
Click to collapse
Even though I was getting errors after the "WIPE" command, it seems like the adb shell is bringing about a linux-esque terminal of the channel image and I can see the files/directories. Using the LS command it seems that the folders you are mentioned are empty, with the exception that there is no "dalvik" directory:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
channel:/ # twrp
TWRP openrecoveryscript command line tool, TWRP version 3.3.1-0
Allows command line usage of TWRP via openrecoveryscript commands.
Some common commands include:
install /path/to/update.zip
backup <SDCRBAEM> [backupname]
restore <SDCRBAEM> [backupname]
wipe <partition name>
sideload
set <variable> [value]
decrypt <password>
remountrw
fixperms
mount <path>
unmount <path>
print <value>
mkdir <directory>
reboot [recovery|poweroff|bootloader|download|edl]
See more documentation at https://twrp.me/faq/openrecoveryscript.html
channel:/ # ls
acct config etc init.rc init.recovery.usb.rc persist plat_service_contexts res sideload tmp vendor_file_contexts vndservice_contexts
bin d external_sd init.recovery.hlthchrg.rc license plat_file_contexts postinstall root storage twres vendor_hwservice_contexts
bugreports data file_contexts.bin init.recovery.mksh.rc mnt plat_hwservice_contexts proc sbin sys ueventd.rc vendor_property_contexts
cache default.prop firmware init.recovery.qcom.rc odm plat_property_contexts product sdcard system usb_otg vendor_seapp_contexts
charger dev init init.recovery.service.rc oem plat_seapp_contexts prop.default sepolicy system_root vendor vendor_service_contexts
Here are the directory contents:
channel:/ # cd data
channel:/data # ls
channel:/data # cd /
channel:/ # cd cache
channel:/cache # ls
channel:/cache # cd /
channel:/ # cd system
channel:/system # ls
channel:/system # cd /
channel:/ # cd dalvik
/sbin/sh: cd: /dalvik: No such file or directory
When you went into recovery mode, was it Motorola's stock recovery or LineageOS's recovery (with the Lineage logo (the three circles))?
In any case, at least you have a working recovery. Error 21 simply means that the signature is on the firmware file is not what it was expecting. If you have a Motorola recovery, then it expects a Motorola-signed firmware. If it is the Lineage recovery, then it will only flash Lineage-signed firmware.
Your TWRP sideload command sure looks like it worked when it loaded the firmware, but if it had worked, you would have LineageOS recovery and it would say current slot: a. I don't remember if the stock Motorola recovery displays the current slot. When you tell fastboot to set_active b, it sets the current slot to b and then when you install the firmware it installs the firmware to slot a.
Exinu said:
When you went into recovery mode, was it Motorola's stock recovery or LineageOS's recovery (with the Lineage logo (the three circles))?
In any case, at least you have a working recovery. Error 21 simply means that the signature is on the firmware file is not what it was expecting. If you have a Motorola recovery, then it expects a Motorola-signed firmware. If it is the Lineage recovery, then it will only flash Lineage-signed firmware.
Your TWRP sideload command sure looks like it worked when it loaded the firmware, but if it had worked, you would have LineageOS recovery and it would say current slot: a. I don't remember if the stock Motorola recovery displays the current slot. When you tell fastboot to set_active b, it sets the current slot to b and then when you install the firmware it installs the firmware to slot a.
Click to expand...
Click to collapse
Exinu,
It looks like the fastboot set_active b command worked, in that my phone acknowledged it did, and the command prompt seemed to indicate the same. As for the phone screen, the Moto splash screen that flashed quickly (probably less than 1 second) did not have any hint of Lineage logo. I tried repeating the process and saw the logo a total of 3x. It was the C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-moto-g7-play-channel-android-10.img command that got me there (the "dirtyport" image you suggested didn't work) and it was before the attempt to flash the lineage image.
However, as for the ADB SHELL commands that you recommended, it didn't seem like they were doing what one might expect. Subsequent to the attempted TWRP commands in the shell, I tried to sideload the lineage system but it would not take, saying "bad key" on the upper LH side of the screen.
Is it possible that prior image flashing attempts have left some incompatible clutter on my phone (perhaps visible by means of exploring other folders or folder names via the ADB SHELL)? I've been working with Raspberry PI's and PC based OMV / Nextcloud servers in recent months and perceive that new installs seem inclined to revert to old files on occasion if not thoroughly formatted.
One thing I forgot to mention: since you are installing Lineage, you can use the Lineage recovery to install it. TWRP is only necessary for /e/ or other roms that do not have their own recovery. Try "fastboot boot" but specify the lineage recovery file.
Also, now that I review things again, I may have used this TWRP instead of the "dirty port" version. I don't know if it will make a difference, but it might be worth a try. Sorry, I guess I have too many irons in the fire right now and got it mixed up. Scroll down to abou t the third or forth comment and there is a google drive link. You just need the recovery.img. Do not flash the dtmo.img, just fastboot/boot the recovery image: https://forum.xda-developers.com/t/...y-custom-recovery-kernel-source-code.3933680/