I have an HTC One m9 that is bricked, but I can unbrick it with fastboot commands to flash the stock rom. I am unable to connect to my device to my laptop with usb for some reason though. When I do "fastboot devices" it shows a list of devices that is empty. when I try to flash anyway, it just says waiting for devices or something like that. Do I need like a special usb driver to connect to my phone via usb? or am I doing something wrong.
Install the HTC USB Driver
HTC One M9 USB Driver for Windows (Official Mobile Driver)
Download the official HTC One M9 USB Driver for your HTC Mobile. We also provide all other HTC Mobile drivers for free.
gsmusbdriver.com
Thank you! Ill post if it worked.
Thank you so much it worked!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
well connecting to the phone worked, flashing failed.
I am getting many errors here is the log
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.063s]
finished. total time: 0.080s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip update.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
OKAY [ 1.033s]
writing 'zip' 1/1...
(bootloader) HOSD CL#894012
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_8
(bootloader) 50laQ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.081s
The ZIP you pass to fastboot is corrupted: at least its Central Directory part - located at ZIP's end - can't be read.
so I need to find a different zip that works then.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped ;( But googled restored contacts, apps & sms
Have a look here for guides: http://forum.xda-developers.com/showthread.php?t=2577043
Help!
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!
SamTenny said:
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!
Click to expand...
Click to collapse
Spam the button their site sucks. Try after a day or two.
If it still doesn't work then this the only solution left.... http://theroot.ninja
SamTenny said:
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!
Click to expand...
Click to collapse
Are you sure you put in the correct value? I thought my xt1032 was not eligible but it was. I typed in the wrong characters.
OK. Thank God
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped ;( But googled restored contacts, apps & sms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any Ideas?
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped :/
SamTenny said:
Any Ideas?
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped :/
Click to expand...
Click to collapse
can you get to fastboot once more and see the top of the screen for device status?
some users reported those error message but their device get unlocked anyway
Yah! Thats what my 2nd threads about! I got a status code 3! Motorola Support even had no clue. They are going to email me this morning. Probably won't help. Their staff recommended here and motorola forums
Remove The Unlocked Bootloader Message
Instruction:
Download the logo.zip
Extract all the files
Reboot to fastboot mode (power + vol down)
Now open cmd and use cd command to go to the directory where you placed the file.
Now Type the command: fastboot flash logo logo.bin
Reboot from the recovery (use vol up to select and vol down to navigate)
Now your bootlogo should be restored back to the normal version
Click to expand...
Click to collapse
screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hit Thanks If It Helped You!!
Reserved!!
works as advertised. thanks
FunkeeC said:
works as advertised. thanks
Click to expand...
Click to collapse
:good:
I'm an idiot, got it working finally. Even when loading from the platform tools folder it failed. Had to move it to root of C:\ and load like this:
C:\windows\system32>fastboot flash logo C:\logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (460 KB)...
OKAY [ 0.019s]
writing 'logo'...
OKAY [ 0.420s]
finished. total time: 0.440s
SurferNerd6987 said:
I'm an idiot, got it working finally. Even when loading from the platform tools folder it failed. Had to move it to root of C:\ and load like this:
C:\windows\system32>fastboot flash logo C:\logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (460 KB)...
OKAY [ 0.019s]
writing 'logo'...
OKAY [ 0.420s]
finished. total time: 0.440s
Click to expand...
Click to collapse
So now what is u r problem??
Don't have one. It worked. Just a bit of different instruction.
It seems this is a copy of http://forum.xda-developers.com/showpost.php?p=52692225&postcount=2
Please do not copy or repost others' work without permission
Thread closed
Hi!
I have this weird situation while trying to update my phone. It's bricked but not hard bricked. Here's the situation.
- I can boot into fastboot and recovery is coming up.
- While clearing data/cache it always throws unable to mount error.
- I can't flash any images using fastboot. It just says that
Code:
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.184s
- Also , when I try erasing, I get this.
Code:
Creating filesystem with parameters:
Size: 1388314624
Block size: 4096
Blocks per group: 32768
Inodes per group: 7712
Inode size: 256
Journal blocks: 5296
Label:
Blocks: 338944
Block groups: 11
Reserved block group size: 87
Created filesystem with 11/84832 inodes and 11157/338944 blocks
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
- I have tried to use the QualComm Tool & the OnePlus Recovery Tool. They detect the phone. QPST detects the phone too but they can't flash anything either.
What can I do? Is the storage corrupted? How can I fix it? Please help!
EDIT :
Here's the output of
Code:
fastboot oem device-info
Code:
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
It says device not unlocked ....try
fastboot oem unlock then try to flash.
bablu048 said:
It says device not unlocked ....try
fastboot oem unlock then try to flash.
Click to expand...
Click to collapse
Tried it. It says OK on command prompt and reboots but when I try doing the same, it says the same error. device not unlocked. Some time earlier i checked that said the tampered bit is set to true.
The weird part is the cyanogen recovery is coming up.
When I try reboot to system, it shows Cyanogen logo and stays there. nothing happens.
I tried adb sideload but it fails saying it cant mount /cache (Invalid Argument). Here's an image for better understanding.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ -0.000s]
finished. total time: -0.000s
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
so ive been at this most of the day, and cant seems to be able to find answers
am trying to flash a Y700 tablet with cr droid, and manged to get nowhere with it for the last 8 hours....
Ive connected the device to windows, loaded platform tools,
adb Devices shows device, then enter command "adb reboot bootloader" device boots into fastboot mode, but then platform tools fails to recognize the device any longer. its show in windows device manger as just andoid with yellow mark. i assumed this was a driver issue, so i have looked for drivers and installed every driver i could find, from sdk tools, adb drivers, lenovo drivers, google adb drivers and prob more to no avail. none of these drivers have worked. The device is still unrecognizable in fastboot or recovery mode by platform tools....what am i missing?
if i connect the device in recovery mode its shows as unauthorised in platform tools.....
any help much appreciated.
Ps this is in this thread as there is no y700 thread yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any help on why its falling to flash?
C:\Users\Admin\Desktop\platform-tools>fastboot flash system C:\Users\Admin\Downloads\crDroid-9.0-arm64_bgN-Unofficial.img
Resizing 'system_a' OKAY [ 0.005s]
error: write_sparse_skip_chunk: don't care size 951510232 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 683078872 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 414647512 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 146216152 is not a multiple of the block size 4096
Sending sparse 'system_a' 1/5 (262140 KB) error: write_sparse_skip_chunk: don't care size 951510232 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 951510232 is not a multiple of the block size 4096
OKAY [ 10.560s]
Writing 'system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
@ STHellRaiser did you manage to resolve your issue?