Help, I can't sideolad Havoc Os on pitch black rp, It always shows: Total xfer: 0.00 in cmd, and the recovery shows: failed adb.
Fixed, found a newer twrp.
Related
This morning I woke up to discover that my phone will not boot. It just sits on the HTC splash screen until I hold the power button down and turn it off. I can get the phone into bootloader, but when I try to boot into recovery the phone just freezes. I can enter Fastboot mode, and it shows "fastboot USB" when connected to a computer, but any command I try to run via ADB fails. For example, when trying to erase cache it goes like this:
Code:
fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.369s
I've also tried running some commands using Hasoon2000's All-in-one toolkit, but it always returns a "error: device not found" message on the first popup, and then fails to complete the task. For example, attempting to flash a new recovery goes like this:
Code:
sending 'recovery' (7420 KB)...
OKAY [ 1.142s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.322s
The phone does show up as "My HTC" under the "Android USB Devices" heading in my PC's device manager, and the drivers appear to be up to date.
I was running Pac-man ROM nightly from Sept. 19, and I had no issues with it for over a week. Hboot version is 1.44.0000. I haven't flashed a custom kernel or radio at all.
Any thoughts on what could be wrong, and how I might go about fixing it?
I would also accept any tips on getting rid of the "this build is for development purposes only" screen so I can at least return the phone under warranty.
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
It would seem that for me Flashing the TWRP Recovery (or any other, tried Orangefox too) doesn't work. I would really appreciate some input on this.
Here's some info:
- Redmi 4
- MIUI 10.2 | Stable // 10.2.2.0(MBECNXM)
- Android version 6.0.1
- Android Security Patch level 2018-04-01
- Unlocked the Phone (Successfully)
- Booted into fastboot
- used "fastboot flash recovery <filename>.img" to flash the twrp image (also tried older versions of the twrp image; also tried the orange fox recovery image)
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot flash recovery twrp.img
Sending 'recovery' (36040 KB) OKAY [ 1.002s]
Writing 'recovery' OKAY [ 0.977s]
Finished. Total time: 2.046s
- I proceed to use "fastboot boot twrp.img"
It gives me the following output:
Code:
C:\Minimal ADB and Fastboot> fastboot boot twrp.img
Sending 'boot.img' (36040 KB) OKAY [ 1.001s]
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
Now unto the errors / things I've tried:
- If I try to just use "fastboot reboot" -> it proceeds to eternally get stuck on the "mi.com" loading screen
- If I try to use the "standard" power off > Power + Vol Up -> The phone boots into the Chinese interface which is not TWRP (yellow big buttons, bottom button is blue) -> I change the language to english, hit "Recovery" and it yet again either stays stuck or boots into Mi 3.0 Recovery
I have tried all TWRP Santoni versions currently officially available on the official TWRP site.
All give me the same error if I try to boot the recovery direclty through fastboot as seen above: "(remote: dtb not found)"
can anyone please help me with this?
Flash latest stock ROM with fastboot first without re locking bootloader, boot into it, and then flash twrp 3.2.3-1 official from fastboot again, and then disconnect the phone and reboot into recovery with vol up + down + power button and ensure that you have downloaded lazyflasher into your phone storage, and after booting twrp, flash lazyflasher, clear cache and reboot system. Done!
Hey guys
I really urgently need to set up my P20 Pro since my daily driver just broke, but I cant make it work somehow.
Its running stock android 9 at the moment (i tried to downgrade it to 8.1 a while back to properly use xposed but that didnt seem to work either), the bootloader is unlocked and i just installed a bunch of drivers.
But wenn i go into sdk platform tools and my phone is in fastboot mode, i cant install a recovery via adb/fastboot. the device is just not there. in the fastboot mode on the phone screen it says phone unlocked in red and frp lock in green. is that right?
when i regularly boot it and connect it to my pc and open adb it and type adb devices it shows up, but when i do the same in fastboot mode it doesnt:
C:\Users\DK_FineArt\Desktop\Neuer Ordner (2)\platform-tools_r29.0.5-windows\plat
form-tools>adb devices
adb server version (39) doesn't match this client (41); killing...
* daemon started successfully
List of devices attached
and when i just try to install twrp via fastbood following error appears:
C:\Users\DK_FineArt\Desktop\Neuer Ordner (2)\platform-tools_r29.0.5-windows\platform-tools>fastboot flash recovery_ramdisk twrp.img
Sending 'recovery_ramdisk' (10642 KB) OKAY [ 0.234s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not
allowed')
fastboot: error: Command failed
C:\Users\DK_FineArt\Desktop\Neuer Ordner (2)\platform-tools_r29.0.5-windows\plat
form-tools>
I havent modded a phone in a long time but thats the right order right? first unlook bootloader, then install recovery via adb, then flash rom, then root?
but im stuck with the first step. please help!
thank you!
Please?
I tried to root my mi a2, but the android had some bugs so I tried to do a "reset factory". Now everytime i try to use MiFlash to install a new image, the fastboot logo disappears and show a message "press any key to shutdown". Besides that, I can't use TWRP, because th mi a2 just show the logo "team win".
Anyone can help me?
Video showing my problem:
streamable.com/6xppe
Fastboot flashing unlock_critical
...
FAILED (command write failed (Too many links))
finished. total time: 0.004s
As always with these issues:
Do you use the latest fastboot and adb version from sdk or some others like "minimal"?
Make sure you got the sdk version and execute all commands as root (linux) or admin (windows).