When I saw that CWM 6 was available for our Flyer, I jumped to install it without waiting to see results of other users (stupid move, I know). Using DoomLord's touch recovery, I installed and rebooted. Seeing as I had nothing new to flash, I didn't boot back into recovery. Today, I decided I wanted to try out IOIDroid's newest work, and rebooted into recovery to prep for install.
CWM 6 was gorgeous! Only one problem: any action taken made all options text disappear! (nothing but the CWM logo would show until the power button was pushed again) I was able to reboot manually, installed ROM Manager, and CWM 5 through ROM Manager. Reboot to recovery, and nothing but a beautiful white screen/HTC logo... Manually rebooted again, and tried to re flash DoomLord's touch recovery through ROM Manager, reboot, same result. Tried using GooIM to flash the same recovery, and nada...
Luckily the ONEXXL still boots, but I'm stuck with no recovery, now... I'm thinking if I uninstall ROM Manager, delete the CWM folder from my SD, reinstall ROM Manager/CWM, that might fix it? I kinda feel like I'll get the same splash screen, though...
Any other ideas? Never completely lost recovery before...
My tab's Flyer than yours (unless this is posted in a Flyer thread... Then it's just as Flyer...)
http://android-gz.com
Use fastboot.
yes fastbot flash the recovery img
fastboot flash recovery "name of file.img"
That's the reply I was dreading... Lol. I've always had problems with fastboot / adb on my laptop... Think it's got something to do with Windows 7. CMD prompt opens and immediately closes when I try to open either... I'll try it again, though...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
mcord11758 said:
are you sellecting the fastboot.exe itself?
you need to open the command prompt on its own and navigate to the directory that holds the commands
Click to expand...
Click to collapse
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
IP IHI II IL said:
Sho 'nuff... I'm a dolt! I haven't tangled with either since my old OG EVO... I soft bricked that, and gave up until I had the time to properly learn, and still haven't gotten the chance to learn. I'll try it the right way now...
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
Click to expand...
Click to collapse
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Woah, dude! You ROCK! With 4 kids, and helping my fiancée with her daycare it's not easy to find the time to tinker, and you just saved my heinie! Thanks a TON!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Here are my failed attempts:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>devices
'devices' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>C:\android\fastboot flash Flyer-HC-CWM5-Recovery-DooMLoRD-v02-T
ouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>c:\android\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>c:\android\fastboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>c:\android\fastboot update update.zip
error: failed to load 'update.zip'
C:\Users\PHILTHY>c:\android\fastboot flashall
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android\fastboot flash c:\android\recovery.zip
unknown partition 'c:\android\recovery.zip'
error: cannot determine image filename for 'c:\android\recovery.zip'
C:\Users\PHILTHY>c:\android\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>c:\android
'c:\android' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PHILTHY>c:\android\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
EDIT: ok, so I re-downloaded/installed the SDK and tools. I put the recovery.img in the folder "C:\android\platform-tools" and ran:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>
WTH am I doing wrong?! I know it's user error...
EDIT 2: MORE failed attempts... starting to get frustrated...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Users\PHILTHY>C:\android\platform-tools\fastboot devices
HT15XJN00873 fastboot
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
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 reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.512s]
finished. total time: 0.514s
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\recovery.img
unknown partition 'C:\android\platform-tools\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\recovery.i
mg'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash Flyer-HC-CWM5-Recovery
-DooMLoRD-v02-TouchEdition.zip
unknown partition 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-TouchEdition.zip'
error: cannot determine image filename for 'Flyer-HC-CWM5-Recovery-DooMLoRD-v02-
TouchEdition.zip'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash C:\android\platform-to
ols\fastboot\recovery.img
unknown partition 'C:\android\platform-tools\fastboot\recovery.img'
error: cannot determine image filename for 'C:\android\platform-tools\fastboot\r
ecovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
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 reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
-n <page size> specify the nand page size. default:
2048
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Users\PHILTHY>C:\android\platform-tools\fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
C:\Users\PHILTHY>
I have the recovery.img in "C:\android\platform-tools". I also created a folder named "fastboot" and put it in there, and tried to run it to no avail...grrrrr
IP IHI II IL said:
Alright, my machine's a dolt now... I try to change the file, and it just renames it start-here.bat.txt... I managed to get into fastboot the right way, finally, and I've tried flashing the recovery to no avail. I've renamed it a few times, but my damn machine just adds the text to the file name instead of changing the file type...
(I just realized I needed to extract the img from the zip, did that and still won't flash...)
I know I must look like an idiot at this point, and sorry if I'm wasting your time with n00bishness, but like I said before, it's been a LONG time since I've been able to practice, so this is basically all new to me...
Sorry guys, and thanks for the help so far!!
Click to expand...
Click to collapse
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
pravus_nephilim said:
Your explorer settings are preventing you from changing the file type. If you are on Windows 7 change it in;
Start > Control Panel > Folder Options > View then uncheck "Hide extensions for known file types"
If you place that start-here.bat in the same folder as your fastboot.exe it will take you to the right directory in the terminal. It was only to try simplify things!
If you have the SDK extracted to the root of your drive and the terminal is saying "C:\Users\PHILTHY>" you're going to have to change directory by typing
Code:
cd C:\android-sdk\platform-tools
Then when you're in the proper folder in the terminal type out the following commands while in fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Extract the recovery.img from the .zip. You don't need to make a folder called fastboot. Just have the recovery.img in the platform-tools folder along with the fastboot.exe.
Click to expand...
Click to collapse
I'll can't believe I forgot to enter the cd command... All that frustration over 2 lil letters... I promise I used to know this stuff well... Guess I've been outta the game for too long... That did it! Thanks for all your help guys, and SUPER thanks to pravus for goin the extra mile to help a dolt!
I chose the red pill... Now I'm in the mAtrix and I know Kung Fu...
http://android-gz.com
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
pravus_nephilim said:
Download the start-here.txt attached to this post and place it in the same directory as your fastboot.exe. Change "start-here.txt" to "start-here.bat" and double click it. Follow the commands in the attached image to flash your recovery.img. Make sure the recovery.img is in the fastboot folder.
If the text options disappear when you're in recovery press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
Click to expand...
Click to collapse
vinteri said:
I had an even worse case on my flyer.
Tried to get the touch recovery, then install a HC based rom. It won't work at all. Everytime I got flash closed on recovery.
Click to expand...
Click to collapse
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
pravus_nephilim said:
Do you have a Gingerbread or Honeycomb hboot and are you HTCDev unlocked or S-OFF?
Click to expand...
Click to collapse
vinteri said:
I have s-off. Before I flashed the touch recovery, I had ICS OneXXl rom installed.
hBoot should be HC.
Click to expand...
Click to collapse
Okay, so you're S-OFF with the Honeycomb hboot and trying to flash another HC ROM in recovery. How did you flash the touch recovery? I don't fully understand what you mean when you said "Everytime I got flash closed on recovery".
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
vinteri said:
Everytime I tried to go to recovery, it showed up for less one second, then turned to black screen. Bad thing is I wiped the previous installed Rom. Without recovery, I can't restore from backup.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Surely you can reboot into the bootloader, go to fastboot and try reflash the a recovery.img? Check the md5 of your downloaded recovery.img in case something is off.
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
Code:
$ adb devices
List of devices attached
NX529J device
$ adb reboot-bootloader
$ fastboot devices
$
I am using Ubuntu 16.04 and installed adb and fastboot with
Code:
sudo apt install android-tools-adb android-tools-fastboot
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
I found a Chinese TWRP on Chinese website (but the download link is now broken)
http://bbs.nubia.cn/forum.php?mod=viewthread&tid=647594&extra=page=1&filter=typeid&typeid=443
http://www.microsofttranslator.com/...tra=page%3D1%26filter%3Dtypeid%26typeid%3D443
However, I found it mirrored on a Polish website
http://telchina.pl/nubia-z11-mini-nx529j-t28452-24.html
which links to https://drive.google.com/file/d/0B0hidJ2sijwIb0ctdk9kaWFGSmc/view
Inside was a bat file that had an extra parameter command
Code:
fastboot -i 0x19d2 boot NX529J_TWRP_3.0.2-0-521.img
According to the fastboot docs you can force fastboot to work with a device even if the vendor ID is unknown by the fastboot binary by using the -i parameter
http://elinux.org/Android_Fastboot#Commands
Code:
-i <vendor id> specify a custom USB vendor id
You can find the vendor ID of devices using lsusb
e.g.
Code:
lsusb |grep ZTE|cut -d: -f2
ID 19d2
That enabled fastboot to work and TWRP started.
It was in Chinese but there is an English button that says Change Language and you can change to English.
He has also packaged SuperSu in the Advanced menu under "Stalence Tools" in order to root your phone.
opticyclic said:
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
Code:
$ adb devices
List of devices attached
NX529J device
$ adb reboot-bootloader
$ fastboot devices
$
I am using Ubuntu 16.04 and installed adb and fastboot with
Code:
sudo apt install android-tools-adb android-tools-fastboot
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
Click to expand...
Click to collapse
type this first fastboot oem unlock-go to unlock bootloader
before that you need to enable oem unlock and usb debugging in options
and I use this twrp
Interestingly I didn't need to unlock the bootloader.
The fastboot oem unlock command didn't work like that though because of my fastboot binary not being aware of the vendor as mentioned in the previous post).
The TWRP you linked to (NX529J-TWRP_3.0.2.3_CUOCO92) is the Italian one.
Is the source available?
Is there an English menu in it?
yes, it is in English but maybe not at first run. to set English follow procedures on pictures
OK.
That is a bit weird though.
Why is an Italian compiling TWRP in Chinese?
The one by Stalance/Silent Star has a button on the first page in English that jumps you to the language section.
I'm trying to compile it myself atm but I don't know how to specify the blobs to extract to create a vendor tree.
The other issue was because I installed adb from the repos.
That was version 1.0.32 but the version at https://developer.android.com/studio/releases/platform-tools.html is 1.0.36.
When I download, unzip and run
Code:
sudo fastboot devices
this time it recognises the device and I don't have to pass the vendor id.
opticyclic said:
I am trying to flash TWRP and although adb seems to work, fastboot doesn't.
I am using Ubuntu 16.04 and installed adb and fastboot with
Does the NX529J support fastboot or did ZTE/nubia disable it somehow?
Click to expand...
Click to collapse
i don't have to unlock, i was already unlocked, should i replace the device
i need qcn NX529J my phone empty imei, but i dont backup
Hi all,
I am trying to unlock bootloader on my Xperia XZ1 compact. Followed all the exact steps on the "sony developer how to unlock bootloader" website and checked out different guides and tutorials. I installed lineage OS on my previous phone (Lenovo P2), so I made it work at least once in the past.
So:
unlock bootloader is allowed on the phone
USB and OEM debugging are turned on
downloaded and installed the latest firmware and USB drivers
download platform tools with ADB and fastboot
I put my phone into fastboot mode (volume up and power button), the blue led is turned on wich supposedly means that it is in fastboot mode
I open up a powershell (run as administrator) etc. and give the 'fastboot devices' command -> which then returns nothing.
Any suggestions? Am i overlooking something?
thanks for your help!
Meat
note: I use ".\fastboot devices" as the actual command, since i get this error if i do not use ".":
fastboot : The term 'fastboot' 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
+ fastboot devices
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command fastboot was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\fastboot".
Hi , if it says fastboot is not recognized means that the path from fastboot terminal is not found .
To fix this you can add path for fastboot or install minimal ADB&Fastboot terminal from here on your PC:
https://androidfilehost.com/?fid=746010030569952951
How to install see here:
https://forum.xda-developers.com/showthread.php?t=2317790
Also instead powershell you can use command prompt .
So Run Command prompt as administrator and directory will be :
C:\Windows\System32 >
change directory to location where you installed ADB &Fastboot terminal for example C:\adb by typing
cd C:\adb
Once you do that your fastboot and adb commands should work fine ...
Good luck
Hi guys, just a disclaimer here but I’m a newb when it comes to flashing ROM’s. I’m trying to flash Calyxos but I’m not having any luck. I get a very quick CMD window (using file flash-all.bat) that appears and then disappears and then… nothing. I’ve tried updating and installing adb drivers, downloading the latest adb fastboot (minimal_adb_fastboot_1.4.3_portable), re-downloading Calyxos (crosshatch-factory-2020.09.22.12) and setting the environment variables to reflect the location of the Caylxos files. I’ve already unlocked the phones bootloader and have USB debugging and OEM unlock enabled. When I run “adb devices” using cmd.exe, it’s able to detect the phone, but this is as far as I can get. If anyone has any advice for me, I’d really appreciated it!
Phone has also been updated to Android 11 and has the latest security patches installed
Anybody?
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Awesome! I'll try it again this evening and report back. Thank you very much for the help
jwoegerbauer said:
@jspicket1111
I guess you have heavily outdated ADB & Fastboot drivers installed. Use this tool to ensure the latest ones are installed.
I also guess the mentioned flash-all.bat is the one that comes with the Calyxos distribution you try to flash. Correct? If so then you can manually input each of the commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot flash bootloader <PATH_TO_BOOTLOADER_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio <PATH_TO_RADIO_IMG_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot erase avb_custom_key
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w --skip-reboot update <PATH_TO_CALYXOS_OS_ZIP_ON_PC_HERE>
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
in a Windows CMD window ( not in a Powershell window ! ) and execute it to see whether an error occurs or not.
Click to expand...
Click to collapse
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools>fastboot flash "C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin"
unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
fastboot: error: cannot determine image filename for 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
I feel like I'm almost there! Not sure if it matters... but the "avb_pkmd.bin" file is only 1 KB in size. Anyhow, I'm not really sure how to fix this error. Would you be willing to help me out again?
jspicket1111 said:
So far I'm making progress. I've got to the part where I'm entering, "fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>" and I'm getting this error in CMD...
...
Unknown partition 'C:\Users\XXX\Desktop\Google_Pixel_Tools_Blueline_Pixel3\platform-tools_r30.0.5-windows(1)\platform-tools\avb_pkmd.bin'
Click to expand...
Click to collapse
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
jwoegerbauer said:
Line
Code:
fastboot flash <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
should read as
Code:
fastboot flash [color=red]avb_custom_key[/color] <PATH_TO_AVB_CUSTOM_KEY_BIN_ON PC_HERE>
Was a copy / paste error. Sorry for this.
Click to expand...
Click to collapse
I finally got it! Thank you very much for the help!