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!
Related
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Same Thing
Hi mjamsek,
I have exactly the same experience as you. I cannot enter the fastboot mode since unlocking/rooting my tf201. Did you solve the problem. ANY help is greatly appreciated!
mjamsek said:
Problem
I cannot flash either Recovery Clockwork (version 5.8.3.4 standard or touch) or TWRP (version 2.6)
I have tried flashing both Recovery Clockwork and TWRP manually through Windows cmd prompt and with ROM Manager Pro
Specs
Asus TF201
Android 4.1.1
Rooted (w/ motochopper)
Unlocked (w/ Asus unlock device v6)
======================================================================================
When booting into fastboot I am presented with four (4) icons on the TF201 screen:
Code:
[B]RCK | android | USB | Wipe Data[/B]
-I select the USB icon for fastboot
TF201 displays (in the top left corner. But the screen remains otherwise unchanged, with the four (4) icons still displayed in the center of the screen. Is this usual?:
Code:
[I]Starting Fastboot USB download protocol[/I]
Cmd prompt input:
Code:
fastboot devices
Cmd prompt display returns:
Code:
[I]015d07879b082207 fastboot[/I]
Cmd prompt input:
Code:
fastboot -i 0x0b05
Cmd prompt return:
Code:
[I]fastboot [ <option> ] <command>[/I]
then displays the available commands and options, i.e. it doesn't tell fastboot which USB device to communicate with. I assume it's not necessary?
Cmd prompt input:
Code:
fastboot -i 0x0b05 flash recovery clockwork_touch.img
Cmd prompt return:
Code:
[I]sending 'recovery'
writing 'recovery'
finished[/I]
TF201 screen: a 'progress bar' appears beneath the four (4) icons in the center of the screen. The bar completes, but remains on the screen. Nothing else happens. Is this usual?
Cmd prompt input:
Code:
adb reboot bootloader
Cmd prompt return:
Code:
[I]adb server is out of date. killing...
*daemon started successfully*
error: device not found[/I]
So I reboot into bootloader manually (volume down and power buttons)
I select the 'RCK' icon to boot into recovery
In the top left corner of the TF201 screen:
Code:
[I]'Booting recovery kernel image'[/I]
But it just hangs on this screen forever
======================================================================================
I've tried this with both clockwork standard and touch, and with TWRP. I've tried it without the -i command. I've tried installing it through ROM Manager Pro. All no bueno.
Any suggestions? I'd appreciate some help. Thanks.
Click to expand...
Click to collapse
I'm having this exact issue except I used Kingo to root instead of Motochopper. I also tried all of the above to fix it, nothing yet.
@mjamsek
Hey it is not going to fix your issue but, you cant run adb commands in fastboot....
So it should look more like this.....
Code:
fastboot reboot-bootloader
What is your bootloader version ?
Maybe try this as long as you are on a bootloader that ends in 2.17 or 2.18
type this
Code:
fastboot erase recovery
then reboot bootloader
then flash a CWM recovery
then reboot-bootloader
then flash TWRP....
Try that and tell me where it gets you...
Thx Josh
I have a similar issue, I will try your cmd lj50036
Exactly the same issue there...
Device rooted and unlocked. Recovery flashed ( CMW), but unable to entered on....
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 I am having a problem trying to flash my g610f/DD phone. I tried removing the FRP lock with FRP Hijacker by Hagard and it totally messed up the phone where its boot looping. I've read and tried almost all the solutions on this website for that model phone. When I flashed the stock rom it is saying Re-Partition Failed in odin. Also on the phone it says in red "secure check fail". The current binary displays as Custom and the FRP lock is on.
I need some help since I tried a lot of solutions and none of them work.
Thanks,
A phone's NAND flash ( storage memory ) is divided into partitions, each of them is of fixed size. When you try to flash a ROM what contains partitions that exceed the size of already existing partitions then you will run in such a trouble. To get rid off of this you would have to completely clean / format the existing partitions ( except the EFS partition !!! ) before re-flashing a ROM. This can be achieved with ADB / Fastboot commands.
Generic Batch-file Example ( untested ! ) :
Code:
@echo off & setlocal
set "ROM=C:\stockrom.zip"
if NOT exist "%ROM%" ( goto :end )
set "PIT=%TEMP%\pit.txt"
adb devices
adb shell "cd /"
adb shell "ls -d" > %PIT%
if NOT exist "%PIT%" ( goto :end )
adb reboot bootloader
fastboot devices
for /f "tokens=9 delims= " %%a in ( "%PIT%" ) do (
if NOT [%%a]==[] (
echo %%a | findstr /I /C:"/EFS" > nul
if %ERRORLEVEL% NEQ 0 (
set "pn=%%a"
set "pn=%pn:~1,0%"
fastboot format %pn%
)
)
)
del /F /Q "%PIT%"
fastboot flashall %ROM%
fastboot reboot
:end
endlocal & @echo on & exit
Read also here: https://technastic.com/odin-nand-erase-samsung/
Hi Thanks for your reply. I can boot into the recovery mode now but when I tried to run the adb commands it gives me an error closed. Also try to install a stock rom it says custom rom block FRP lock.
itwayne said:
Hi Thanks for your reply. I can boot into the recovery mode now but when I tried to run the adb commands it gives me an error closed. Also try to install a stock rom it says custom rom block FRP lock.
Click to expand...
Click to collapse
In Recovery Mode you can't run most of ADB subcommands as for example "adb shell", this because Android OS isn't running.
jwoegerbauer said:
In Recovery Mode you can't run most of ADB subcommands as for example "adb shell", this because Android OS isn't running.
Click to expand...
Click to collapse
How can I format the partitions to get a stock rom on then if adb cant do it.
Thanks,
Hi Guys.
I am new to Forum.
I wanted to root my Samsung A505F/DS but when I try to do flash download mode and using ODIN try to install TWRP but it say "Custom Binary (VBMETA) blocked by OEM. I tried to turn on/off OEM unlocking in developer options but all in vain. Kindly help me out in this regard as i want to root the phone and flash TWRP with custom rom.
You have to disable AVB
Example code ( OF COURSE NOT TESTED ! )
Code:
adb devices
adb pull /vbmeta.img %TEMP%\VBMETA.IMG
adb root
adb shell "setenforce 0"
adb disable-verity
adb reboot fastboot
fastboot --disable-verification flash vbmeta %TEMP%\VBMETA.IMG
fastboot reboot
jwoegerbauer said:
You have to disable AVB
Example code ( OF COURSE NOT TESTED ! )
Code:
adb devices
adb pull /vbmeta.img %TEMP%\VBMETA.IMG
adb root
adb shell "setenforce 0"
adb disable-verity
adb reboot fastboot
fastboot --disable-verification flash vbmeta %TEMP%\VBMETA.IMG
fastboot reboot
Click to expand...
Click to collapse
I tried to code above to disable but it shows " adb: error: failed to start remote object '\vbmeta .img ' : No such file or directory"
okjadoon said:
I tried to code above to disable but it shows " adb: error: failed to start remote object '\vbmeta .img ' : No such file or directory"
Click to expand...
Click to collapse
It's on you to find the correct path to vbmeta.img
Code:
adb devices
adb shell "mkdir -p /data/local/tmp"
adb shell "ls -R / > /data/local/tmp/Android-Tree.txt"
adb pull /data/local/tmp/Android-Tree.txt %TEMP%\Android-Tree.txt
type "%TEMP%\Android-Tree.txt" | more
and input the path found instead of /vbmeta.img
Did u succeed?
jwoegerbauer said:
You have to disable AVB
Example code ( OF COURSE NOT TESTED ! )
Code:
adb devices
adb pull /vbmeta.img %TEMP%\VBMETA.IMG
adb root
adb shell "setenforce 0"
adb disable-verity
adb reboot fastboot
fastboot --disable-verification flash vbmeta %TEMP%\VBMETA.IMG
fastboot reboot
Click to expand...
Click to collapse
Not working on samsungs
So the device is a motorola one hyper , bootloader is unlocked . TWRP is on micro sd , internal at root dir and adb folder .
I rebooted to bootloader . tried to flash and boot to renamed twrp.img im getting a access denied from SU in ubuntu terminal
adb reboot bootloader works . adb devices lists and sees my device .
Fastboot boot twrp.img or fastboot flash recovery twrp.img comes back with a permission denied error. Again Im sudo su to get root permissions when I run the commands.
I just want root access .
Any ideas ?
Also current slot set to B on device. Maybe this is why I cant boot TWRP ???
Set slot to a as it was set active to slot b same permission denied.
On the active slot ( A ) disable SELinux, dm-verity and/or AVB ( read: Android Verified Boot ) if not done yet. FYI: Slot B is used by OTAs.
Synthax:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a <vbmeta.img>
jwoegerbauer said:
On the active slot ( A ) disable SELinux, dm-verity and/or AVB ( read: Android Verified Boot ) if not done yet. FYI: Slot B is used by OTAs.
Synthax:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a <vbmeta.img>
Click to expand...
Click to collapse
The active slot by default was b I switched it to a
jwoegerbauer said:
On the active slot ( A ) disable SELinux, dm-verity and/or AVB ( read: Android Verified Boot ) if not done yet. FYI: Slot B is used by OTAs.
Synthax:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a <vbmeta.img>
Click to expand...
Click to collapse
whats vbmeta.img ? Is that just a standin for my twrp.img name or ?
vbmeta.img actually contains the hashes/keys for the boot, system, and vendor partitions.
More info here:
https://android.googlesource.com/platform/external/avb/+/master/READstructME.md#The-VBMeta-
In your case you have to pull out the existing vbmeta.img, and then pass this copy to fastboot as already shown above.
Example:
Code:
adb devices
adb shell "mkdir -p -m0664 /data/local/tmp/vbmeta"
adb shell "dd if=<DEVICE_NAME_OF_VBMETA.IMG> of=/data/local/tmp/vbmeta/vbmeta.img bs=4096"
adb pull /data/local/tmp/vbmeta/vbmeta.img %TEMP%\vbmeta.img
adb shell "rm -rF /data/local/tmp/vbmeta/*"