Related
Hi this might be a noobish question but i cant find the answer anywhare:
so here's the problem i was trying to fix a badly installed rom, so i wiped the phones storage I then tried to kick myself when i realized that i had just deleted my backup and all the data on the phones internal storage, so now i can only get onto fastboot and clockworkmod recovery 5.8.3.1.
So is there a way to flash a rom in fastboot usb, or mount the phones internal storage so i can copy in a rom zip?
I would be grateful for any help
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
malcovitch said:
There is an option in cwm to mount storage you can try that not sure if they work tho.
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
It will not work.
What you can do other than flashing a RUU is:
Boot to fastboot
fastboot boot CWM_recovery_full name.img
Once it boot to recovery
adb shell
adb push rom_name.zip /sdcard
It will take some times to finish as the rom_name.zip is big.
Once complete, you can flash the rom_name.zip as usual
To make it easier, change the rom_name.zip to update.zip, so you can
adb push update.zip /sdcard
Thank you I have done as you said but i must be doing something wrong because i get this error:
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
(The update.zip is Android_Revolution_HD-One_X_5.1.0.zip)
do you think it could be a problem with my adb.exe or something on the phone?
did you do the "fastboot boot CWM_recovery_full name.img"
going to recovery via hboot will not work.
you need to fastboot boot recovery
and it is adb devices , not adb shell... sorry
see this : http://forum.xda-developers.com/showpost.php?p=25774374&postcount=24
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
River825 said:
yes that's how i got to cwm as below
C:\Documents and Settings\me\Desktop\Android>fastboot boot recovery-clockwork
-touch-5.8.3.1-endeavoru.img
downloading 'boot.img'...
OKAY [ 0.771s]
booting...
OKAY [ 0.010s]
finished. total time: 0.781s
C:\Documents and Settings\me\Desktop\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # adb push update.zip /sdcard
adb push update.zip /sdcard
/sbin/sh: adb: not found
~ #
Click to expand...
Click to collapse
my bad
C:\Documents and Settings\me\Desktop\Android>adb shell
change to
C:\Documents and Settings\me\Desktop\Android>adb devices
Then adb push rom.zip /sdcard
ok i think that worked but when trying to find the zip in cwm i just get "no files were found", but in the command prompt it looks like it was copied to the sd card:
C:\Documents and Settings\me\Desktop\Android>adb devices
List of devices attached
HT23WW118450 recovery
C:\Documents and Settings\me\Desktop\Android>adb push update.zip /sdcard
1586 KB/s (577044654 bytes in 355.290s)
That's wierd.
You mean that when you click "choose zip from sdcard" you have nothing in sdcard ?
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
River825 said:
yes clockworkmod says that the sd is empty.
I'm going to try again with a smaller file and maybe try and access the sd with a different recovery
Click to expand...
Click to collapse
No. It won't work as sdcard need to be manually mounted first.... that's why I said something about adb shell earlier.
I'll do the testing now:
my step will be:
fastboot boot xx-recovery.img
adb devices
adb shell
mount sdcard
open another cmd prompt
adb push xxx.zip /sdcard
will let you know in a short while
Just tested: this should be the correct way... I can see my xxx.zip when I choose : choose zip from sdcard
*you need to mount the sdcard first before adb push
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
River825 said:
thank you it worked fine I downloaded the zip to the sd and flashed the rom in cwm, but it didn't work and now i cant boot into recovery it just shows the revery screen for 1/2 a second, and reboots into the bootloader i tried flashing different recovery images but they didn't work.
Is there some way to wipe the phone recovery?
Click to expand...
Click to collapse
Do:
fastboot erase cache
fastboot reboot-bootloader
Then press power once to go to hboot then select recovery. It should work.
Thank you
Thank you so much for all your advice i've just successfully flashed a rom and got my phone working again i was starting to fear for my phone.
Thanks again for all your help
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Sam.Lambert said:
ckpv5, when I try to follow your steps, I get "error: device not found" when doing adb shell in the command prompt? How do I fix that?
(My problem is that I formatted everything like an idiot in my phone and the internal sdcard seems to be unmounted or something like that)
Click to expand...
Click to collapse
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
ckpv5 said:
If you're on stock ROM, you don't have to do all the step, just simply flash RUU.
Click to expand...
Click to collapse
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Sam.Lambert said:
I don't have the executable RUU for the Rogers handset, I only have a zip containing a bunch of img files and the executable RUU for the AT&T version (which didn't work, gave me ERROR [131]: Customer ID error or something like that).
Which the zipped RUU for the Rogers handset, I tried flashing the recovery_signed.img and boot_signed.img, relocking the bootloader and then flashing the system.img file but it would give me an error saying data length too large or something like that.
I really don't know what to do anymore
Click to expand...
Click to collapse
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
ckpv5 said:
Which custom recovery is working for for your set ? Is the one from One X dev section works for you ? If it is not, I'm afraid unable to help you.
Which custom ROM that you use before the brick ?
Click to expand...
Click to collapse
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Sam.Lambert said:
Pretty much the only one available for the Evita One X (this one doesn't work if that's the one you are talking about http://forum.xda-developers.com/showthread.php?t=1594819):
http://www.modaco.com/topic/354009-interim-clockworkmod-recovery-for-the-s4-based-one-x/
Also, I wasn't able to succesfully flash a custom ROM, when I tried to it just kept giving me random status errors in CWM, I'm starting to think the problem is the hardware and not the software since every solution I try is giving me errors related to unable to install/transfer/blahblah
Click to expand...
Click to collapse
So it seems that yours is not on tegra but S4. You need to find a solution for your problem here : http://forum.xda-developers.com/forumdisplay.php?f=1538
I've been searching for a couple of days now - hence this post.
My Desire boots to HTC green on white - nothing more.
I can get to Bootloader / fastboot / recovery, here's some details :
Code:
Revolutionairy
Bravo PVE3 SHIP S-OFF
HBOOT-6.93.1002
MI CROP-051d
TOUCH PANEL-SYNW0101
RADIO-4.05.00.11
Aug 10 2010 12.75.10
Can flash RUU (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704) and it completes with no errors but all I gain (?) is the loss of recovery which I can restore using AndroidFlasher.
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Have done a full wipe and tried a couple of recoveries and am now on recovery-RA-desire-v2.0.1.img. They all give the same errors, ie :
Code:
E: Can't mount /dev/block/mmclk0p1 (or /dev/block/mmclk0) (No such file or directory)
E:Can't mount /sdcard
Searching for these has suggested that it's a USB brick but all fixes include loading something to the sdcard - which I have no access to.
Other things I've tried with no success :
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.096s]
finished. total time: 0.096s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.097s]
finished. total time: 0.097s
Code:
fastboot flash misc mtd0.img
sending 'misc' (640 KB)...
OKAY [ 0.106s]
writing 'misc'...
OKAY [ 0.183s]
finished. total time: 0.289s
Code:
parted /dev/block/mmcblk0
Error: Could not stat device /dev/block/mmcblk0 - No such file or directory.
/dev/block # ls
ls
loop0 loop2 loop4 loop6 mtdblock0 mtdblock2 mtdblock4
loop1 loop3 loop5 loop7 mtdblock1 mtdblock3 mtdblock5
Code:
fastboot getvar cid
cid: HTC__001
finished. total time: -0.000s
Code:
/ # sdparted -es 512M -ss 256M -efs ext4
sdparted -es 512M -ss 256M -efs ext4
checking script requirements...
err: /dev/block/mmcblk0 does not exist!
Code:
/ # /sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/e2fsck: No such file or directory while trying to open /dev/block/mmcblk0p
2
/dev/block/mmcblk0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
It's like it's a "sdcard brick" but I've failed to find anything on that and that still doesn't explain why it doesn't boot. It used to boot with no sdcard.
This is now driving me mad, please can somebody provide some sanity ?
Have looked at bortak's troubleshooting guide? Ul get more info there. Look in Desire Q&A/ Stickies
Sent from my HTC Desire
Yes.
It seems I have two of the problems.
[1]BOOT PROBLEMS
[IF YOU DO NOT HAVE A BACKUP]
[STEP10b]- go back to the main menu, select "install zip from sdcard"
But I don't have a sdcard so ...
[13]RECOVERY CAN'T MOUNT SD-CARD
In fastboot :
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.097s]
finished. total time: 0.097s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.135s]
finished. total time: 0.135s
Which in theory has mounted the sdcard but when I go into recovery for step [1]BOOT PROBLEMS it's no longer mounted.
The commands from [13]RECOVERY CAN'T MOUNT SD-CARD don't work in recovery - I get
Code:
< waiting for device >
Catch 22 and hence my confusion.
How do I mount the sdcard when in recovery - which is what it seems needs doing ?
It cant mount sdcard if u dont have 1. Ul have to buy 1
Sent from my HTC Desire
dik23 said:
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Click to expand...
Click to collapse
..
"But I don't have a sdcard so ..."
......
Sent from my HTC Desire
Ok ?
Lol what??? U don't have a SD card?
Sent from my SAMSUNG-SGH-I717 using xda premium
dik23 said:
I have no access to multiple sdcards (formatted using gparted to fat32) which work in both my Win7 and Linux machines without issue - I don't think the sdcards are at fault.
Click to expand...
Click to collapse
The "no" there is most likely a typo. The guy is saying that he DOES have multiple SD cards which work properly under W7 and Linux but not with the Desire.
dik23 said:
[1]BOOT PROBLEMS
[IF YOU DO NOT HAVE A BACKUP]
[STEP10b]- go back to the main menu, select "install zip from sdcard"
But I don't have a sdcard so ...
Click to expand...
Click to collapse
Again, he's not saying that he does not have an SD card, he's just saying that the procedure described in the guide requires that the phone "sees" the SD card but his phones does not.
Conclusion: he DOES have MULTIPLE WORKING SD cards, but the phone does NOT recognize them.
What the hell is wrong with you guys?
Theres fk all wrong with us. Ok if "no" was a typo then why does he say " but i dont have a sdcard so.." dont take it the wrong but was just a bit confusing. If they dont work, buy a new 1, like i already said because u need a sdcard
Sent from my HTC Desire
...
Again: he's saying that Bortak's guide requires him, at one point, to run a zip from the SD card, BUT HIS PHONE CANNOT MOUNT ANY SD CARD, thus he "does not have an SD card".
TVTV said:
...
Again: he's saying that Bortak's guide requires him, at one point, to run a zip from the SD card, BUT HIS PHONE CANNOT MOUNT ANY SD CARD, thus he "does not have an SD card".
Click to expand...
Click to collapse
Yes, that is exactly my problem. Sorry, I'd not spotted my typo
http://www.google.ie/url?sa=t&sourc...35n2CA&usg=AFQjCNEPzzSqlgqVMhPWLsFoY_dqWn0Xag
Have a read at that, mite help.
Sent from my HTC Desire
jmcclue said:
http://www.google.ie/url?sa=t&sourc...35n2CA&usg=AFQjCNEPzzSqlgqVMhPWLsFoY_dqWn0Xag
Have a read at that, mite help.
Click to expand...
Click to collapse
That thread ends :
the phone is now with the repair guys for next 2 weeks
Click to expand...
Click to collapse
So I flashed RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe and now it works - sort of
It now boots but still has no access to the sdcard.
Menu > Settings > SD & phone storage
shows SD card total/available space as "Unavailable" and the options to mount / format greyed out.
Lol sry, there is a link at the end too, i had a quick read at it and theres something saying about unlocking the sdcard so i thought maybe u have the same problem. Have look again and click the other link at the bottom, it explains more.
Sent from my HTC Desire
jmcclue said:
Lol sry, there is a link at the end too, i had a quick read at it and theres something saying about unlocking the sdcard so i thought maybe u have the same problem. Have look again and click the other link at the bottom, it explains more.
Click to expand...
Click to collapse
Sorry - I fail to find anything new there. All I find is the same instructions
Code:
fastboot oem enableqxdm 0
...
OKAY [ 0.096s]
finished. total time: 0.096s
fastboot oem eraseconfig
...
(bootloader) Erase config: complete
OKAY [ 0.097s]
finished. total time: 0.097s
And then your sdcard will be mounted.
It might be mounted right at that second but when I go into recovery / reboot it defiantly isn't.
Anyone got any ideas ?
Have now made a mtd0.img with this site. I am using RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed so used 2.29.405.5 for the ROM version. Uploaded both it and the file flash_image from this post :
Code:
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod u+x /data/flash_image
/data/flash_image misc /data/mtd0.img
That all went as planned but I am still left without a mountable sd card.
Is my Desire borked ?
dik23 said:
Is my Desire borked ?
Click to expand...
Click to collapse
Ok guys, thanks for all your help but I think I may have just answered my own question.
I've just noticed that it's not just the sd card it won't recognise. It's the SIM card too. This says to me that I've got a hardware rather than software issue here.
Sorry for wasting anyone's time. I need my phone for work calls and have not thought about inserting the SIM into a phone that doesn't work properly.
Again - thanks for your help here. Anyone know how much I can get for a spares / repairs Desire on the open market ?
I have KFHD 8.9 v8.3. I am having problems getting fastboot working. I have read threads that there are specific "fastboot drivers" and then I have seen other threads where fastboot drivers are a part of the Kindle Fire drivers installed by ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe. No matter what I do I am unable to get "fastboot -i 0x1949 getvar product" to work. At one point I had it rooted with validation from suchecker, still couldnt get fastboot to work, but factory restored to 8.3 to validate steps and instructions and it is a nogo at the moment.
Any help would be appreciated.
So, is your device rooted or not? Your post in another forum seems to contradict what you are saying here.
Liek Soupmagnet said are you positive that your device has root access? If so, I would try wipe the drivers and start from scratch.
As far as I know and it worked for me, fastboot drivers are loaded when you install Android SDK on your PC. See picture bellow.
However in case you need the fastboot drivers you can download here: https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit?pli=1 as referenced here: http://forum.xda-developers.com/showpost.php?p=34589184&postcount=6
These ADB drivers worked for me: http://forum.xda-developers.com/showthread.php?t=1890413
For Kindle drivers and Amazon drivers for Windows 8 (if the case),please take a look here: http://forum.xda-developers.com/showthread.php?t=2185402 however I did need not need them.
Is your Kindle showing up when you type the command ADB Devices cmd/terminal window?
I hope it helps.
soupmaget,
I responded to your PM and I said I would try the SoupKit tonight. Calling me out in forums doesn't help you or me and dont know why you keep doing that. I am trying many things but it boils down to the same specific commands. I have even tried the below downloads manually grabbing the commands and typing them in manually.
Last night I refreshed my env following the amazon tutorials step by step. I finally got root by running Root_with_Restore_by_Bin4ry_v25 twice and then Kindle_Fire_Utility_v0.9.6 rooting via recommended option twice. ADB does work, I can "adb reboot", "adb shell" push files, mv files, etc. SUCheck validates I have root.
When I continue to hashchodes TWRP and 2nd bootloader tutorial it states that "you should have working fastboot drivers" which to me means that there is a separate download/driver to install for it to work. I know fastboot.exe is included in the ADK and tried using the other tools for getting fastboot working but its not working.
I do run these with administrative rights....
D:\android\sdk\platform-tools>adb devices
List of devices attached
B0CA060424841KF0 device
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
rwideman said:
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
Click to expand...
Click to collapse
You are blowing my mind right now with your refusal to be helped. Why are you so hell bent on making this difficult for yourself? You have a $300 device that doesn't work and you're being resistant to someone who can most likely help you get it working again. Why? I don't get it...
From what I gather in your various posts, your device is rooted but you cannot access fastboot via the traditional method of entering "fastboot -i 0x1949 getvar product" in the terminal and powering the device up.
Assuming you have a usb/adb/fastboot connection problem with your Mac, you can use SoupKit, but only in certain VMs. But if you have had a previous connection with either fastboot or adb, that probably isn't the case.
Theres a good chance that you can install the Android Terminal Emulator, enter 'su' to gain root privileges and enter "reboot bootloader". That should boot your device into fastboot so you can enter fastboot commands. But, as I told you before, if there is a usb connection problem, and you cannot send fastboot commands to your device, you will be stuck in fastboot. If you have another non-Mac computer available to you, it would be best to boot it into Linux and install soupkit to make sure that doesn't happen. BTW, that is nearly verbatim to what I told you via the first PM.
Are you looking at the timestamps of my postings? Things change over time....
Did you read my PM response? I will try SoupKit tonight, I mentioned this after you told me to try it.
Thank you for your efforts.
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
FYI #3, In the professional world it is better to stick to non-psychologist bashing, what someone is and is not doing/thinking/acting, and sticking to the issue at hand. I have been in the IT world for 15 years and troubleshooting is my day job (windows, vmware, SAP, *nix, .net, java, j2ee, storage, UCS, routers, switches, nexus, cloud automation, orchestration, etc). Professionalism frowns upon psychologist speak.
rwideman said:
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
Click to expand...
Click to collapse
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
I think I have the same problem. twrp installed on my device, but no OS running, and it can't be recognized on my computer, said driver incorrect, tried so many times, but can't get adb and fastboot work without driver supported. Don't know how to do.
soupmagnet said:
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
Click to expand...
Click to collapse
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
rwideman said:
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
Click to expand...
Click to collapse
When it's in fastboot, do you see anything show up in the device manager?
soupmagnet said:
When it's in fastboot, do you see anything show up in the device manager?
Click to expand...
Click to collapse
Unfortunately no. I haven't had time doing linux with soupkit yet.
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
jonahy said:
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
Click to expand...
Click to collapse
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
soupkit Folder Empty out
soupmagnet said:
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
Click to expand...
Click to collapse
Hi Thank you for the direction.
I made a Ubuntu 12.10 usbkey booted
then copied ur soupkit folder on desktop Run install.sh ( have to go into permisions check the allow excute)
Run in terminal then terminal show 2 " closed then all the file in soupkit is gone..ha.
didnt see option 1 and 2.
Then i try in Ubuntu termal do abd and fastboot but same as in window 7 KFHD89 just boot into lock screen.
(adb devices it can see devices though
Setting up android-tools-adb (4.1.1+git20120801-1) ...
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device)
fastboot not
([email protected]:~$ sudo apt-get install android-tools-fastboot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
android-tools-fastboot
0 upgraded, 1 newly installed, 0 to remove and 337 not upgraded.
Need to get 48.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ quantal/universe android-tools-fastboot i386 4.1.1+git20120801-1 [48.6 kB]
Fetched 48.6 kB in 0s (105 kB/s)
Selecting previously unselected package android-tools-fastboot.
(Reading database ... 161214 files and directories currently installed.)
Unpacking android-tools-fastboot (from .../android-tools-fastboot_4.1.1+git20120801-1_i386.deb) ...
Setting up android-tools-fastboot (4.1.1+git20120801-1) ...
[email protected]:~$ fastboot -i 0x1949 getvar product
< waiting for device >
I was thinking maybe its the Root_with_Restore_by_Bin4ry_v26 mess up somthing? I know my KFHD is rooted it by, but if i load any app need root never show the window ask me if i allow this app in superuser massege.
anyway any tips abot that soupkit Folder Empty out issue?
(just got this tablet last friday, good device so far but put a recovery on it seems a bit harder then my other tablets...But hey I guess thats part of fun too right? )
Thank you in advance.
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Installed 2ND-BOOTLOADER
soupmagnet said:
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Click to expand...
Click to collapse
Great! Got Installed the 2nd bootloader and recovery .
adb shell su -c "reboot bootloader" boot device to fastboot mode.
thanks a lot! SoupMagnet.
Share steps:
D:\sdk\sdk\platform-tools>adb devices
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "reboot bootloader"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Jem-PVT-Prod-04
finished. total time: 0.006s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.939 secs (8933554 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.937 secs (8952623 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/system of=/sdcard/stock-system.img"
1814528+0 records in
1814528+0 records out
929038336 bytes transferred in 116.782 secs (7955321 bytes/sec)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-boot.img
2794 KB/s (8388608 bytes in 2.931s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
3008 KB/s (8388608 bytes in 2.723s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-system.img
3004 KB/s (929038336 bytes in 301.978s)
D:\sdk\sdk\platform-tools>adb push stack /data/local/tmp/
571 KB/s (4096 bytes in 0.007s)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/data/local/tmp/stack of=/dev/b
lock/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,rw ext4 /system"
D:\sdk\sdk\platform-tools>adb shell su -c "mv /system/etc/install-recovery.sh /s
ystem/etc/install-recovery.sh.bak"
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,ro ext4 /system"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-
8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.026s]
writing 'bootloader'...
OKAY [ 0.045s]
finished. total time: 0.075s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0
.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.455s]
writing 'boot'...
OKAY [ 0.567s]
finished. total time: 1.030s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-r
ecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.029s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.004s
D:\sdk\sdk\platform-tools>
FIXED
soupmagnet,
Finally had time to install ubuntu 12.10 on my laptop. I used soupkit for KFHD89 and root-plus from the same posting you had. This worked like a charm. rootplus' version of the play store actually worked compared to other versions I had installed, same for youtube and a few other google apps.
I will toy with TWRP tomorrow. Just glad I got normal google apps installed now.
I tried to root my 8.9 kfhd 8.5.1 from a youtube video. I got stuck on the blue kindlefire screen. Through different guides I am able to get to twrp and fastboot. I have not been able to install a rom zip on the device through a cut and paste or a push command. I have left messages in a few threads and got a little response, but nothing that got me fixed. I've working on this for 2 weeks and read dozens of threads and cannot find a solution. I guess I had adb working at one time and had the drivers installed, but I'm not sure if ADB is working and my drivers are gone. I tried this thread "Frequently Asked Questions - 2nd Generation Kindle Fires " which directed me to this thread " [GUIDE] Kindle Fire For Beginners [GUIDE] Kindle Fire For Beginn… Post #2 " where I thought following this "How do I install the ADB drivers?" would be the way to go. So I followed it to here "[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) [First Gen Only] " and it warns me not to use it on my 8.9. So I looked some more and found this "Let's take some of the mystery out of getting ADB working in Windows ". I think I can get through these instructions correctly, but I now not sure if I this is the proper course of action considering I can get to fastboot and twrp. I've looked for a simpler solution to fix this. I even tried the push command to try and get liquid smooth rom and gapps onto the devices sdcard with no luck.
I am a total newbee and most of the lingo goes right over my head. The following is the original log of my first rooting attempt using this guide ......
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Home>cd desktop
C:\Users\Home\Desktop> cd kindlefire/stuff
C:\Users\Home\Desktop\kindlefire\stuff>adb push stack /data/local/tmp/
800 KB/s (4096 bytes in 0.005s)
C:\Users\Home\Desktop\kindlefire\stuff>adb shell
[email protected]:/ # su
su
/system/bin/sh: su: cannot execute - Permission denied
126|[email protected]:/ # dd if=/data/local/tmp/stack of=/dev/block/platform/omap/oma
p_hsmmc.1/by-name/system bs=6519488 seek=1
f=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1 <
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
[email protected]:/ # mount -o remount,rw ext4 /system
mount -o remount,rw ext4 /system
[email protected]:/ # mv /system/etc/install-recovery.sh /system/etc/install-recovery
.sh.bak
.sh /system/etc/install-recovery.sh.bak <
[email protected]:/ # mount -o remount,ro ext4 /system
mount -o remount,ro ext4 /system
[email protected]:/ # reboot bootloader
reboot bootloader
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash bootloader kfhd8
-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.021s]
writing 'bootloader'...
OKAY [ 0.046s]
finished. total time: 0.069s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash boot kfhd8-freed
om-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.773s]
finished. total time: 1.225s
C:\Users\Home\Desktop\kindlefire\stuff>49 flash boot kfhd8-freedom-boot-8.4.3.im
g
'49' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash recovery kfhd8-t
wrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.451s]
writing 'recovery'...
OKAY [ 0.754s]
finished. total time: 1.208s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
Today I tried a factory reset thinking I could push a rom and gapps on the sdcard, but of course that didn't work either.
I don't want to ask people to rehash the same questions over and over but being this far down the road I don't know if I can start the rooting process over or just what. Any help would be appreciated.
Wes
Did you flash the custom rom and gapps to your device?
post the link from which guide you follow the instructions to install a custom rom
This is the video guide I used..
https://www.youtube.com/watch?v=hUW6KARo8Y4
After this I was stuck at the blue kindlefire screen. I found can get to twrp and fastboot mode (twrp by rebooting and holding the up volume and into fastboot by entering "fastboot -i 0x1949 getvar product" in a command prompt). When in twrp my computer (win7) sees the kindle in "devices and printers" and also in device manager but the yellow exclamation mark shows that the drivers are not installed.
I reinstalled my drivers and in device manager I have listed...
"Android ADB Interface" as a sub listing under "android phone" (it doesn't list the kindle any longer)
I ran the RunMe.bat file and got the original root script. I have 5 choices...
1) normal
2) Special (....)
3) New xperia....
G) Goodle glass
x) Unroot
This is all the while I have my device connected to my computer with the usb cable.
My computer sees the device in "devices and printers" and in device manager but does not see it in windows explorer.
Now what?
I took pictures of my screen but I haven't figured out how to add images.
ironrod60 said:
I took pictures of my screen but I haven't figured out how to add images.
Click to expand...
Click to collapse
Help?? Anyone?? Mods?? I've done everything that was laid out in the newbee's section and have found nothing that fits the problem I am having with rooting my device. It said that if I did that people would be more than happy to help. I've been working on it since 14 Jan.
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/