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)
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"
}
Hello guys…I need some help with my htc E8 from sprint
My phone is dead no OS , no recovery and stuck at bootloader screen with s-on and is locked bootloader never I unlocked.
Fastboot oem rebootRUU doesn´t work
Fastboot flash unlocktoken doesn’t work
Fastboot flash zip rom.zip doesn’t work because is locked the bootloader I think
When I try flash from hboot with 0PAJIMG.zip error says: device halted due to the largue image update fail.
And every step that I take never do anything…when I try fastboot oem rebootRUU command says: error the command never completed.
I get the rom.zip from the RUU is normal the file has 1.5gb?
Please help me…thanks.
try to help. give me time. do not upgrade to higher version as it is impossible to downgrade by RUU method. you can simply use ADB commands via USB to unlock bootloader then flash TWRP and use SD card to flash TWRP backup rom. i think this is the easiest method.
Sent from my Nexus 4 using Tapatalk
sallomi said:
try to help. give me time. do not upgrade to higher version as it is impossible to downgrade by RUU method. you can simply use ADB commands via USB to unlock bootloader then flash TWRP and use SD card to flash TWRP backup rom. i think this is the easiest method.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ok...but I cant unlock the bootloader with the fastboot command .tell me what can I do to unlock througt adb, the phone doesnt start.
sawonch said:
ok...but I cant unlock the bootloader with the fastboot command .tell me what can I do to unlock througt adb, the phone doesnt start.
Click to expand...
Click to collapse
Are you opening a cmd prompt from the folder that includes adb/fastboot ? And are you placing the zips inside the same folder
benny3 said:
Are you opening a cmd prompt from the folder that includes adb/fastboot ? And are you placing the zips inside the same folder
Click to expand...
Click to collapse
of course man...but I cant flash zip file because my device bootloader is locked and when I try to unlock it with fastboot command says: the command never completed and another lines with error...
when tipe cmd fastboot oem rebootRUU here is the succes:
C:\Users\Lidia\Desktop\umbricking project>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.285s]
finished. total time: 10.301s
because this error I cant start flashing rom.zip
hardware failure (eMMC problem)
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.
After installing TWRP all I get is a black screen. Any idea why? Here is what I did so far:
Bootloader unlocked:I have unlocked the bootloader as described
Bash:
>fastboot oem unlock 0xXXXXXXXXXXXX
OKAY [123.312s]
Finished. Total time: 123.312s
And the bootloader shows as unlocked in the developer settings:
{
"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"
}
Reboot to Bootloader:I rebooted into the bootloader using adb:
Bash:
>adb devices
List of devices attached
CB512E83J6 device
>adb reboot bootloader
>fastboot devices
CB512E83J6 fastboot
Flash TWRPI tried to flash both TWRP 3.5.2 and TWRP 3.4.0. I also rename the files twrp.img and recovery.img as suggested in some of the instruction. But that didn't make any difference.
Bash:
>fastboot --verbose flash recovery twrp-3.5.2_9-0-maple.img
fastboot: verbose: Do flash recovery twrp-3.5.2_9-0-maple.img
fastboot: verbose: target reported max-download-size of 536870912 bytes
Sending 'recovery' (33596 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.318s]
Finished. Total time: 1.178s
Boot recoveryUsing fastbootFirst I tried to boot the recovery using fastboot but that booted Android instead:
Code:
>fastboot --verbose reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.001s
Using ADBFrom there I tried to adb to boot into recovery. That too booted Android instead:
Code:
>adb reboot recovery
Using Volume down + Power Button
Last I tried the Volume down + Power Button until the first vibration, then releasing the Power Button. That at least resulted in green LED suggesting that the recovery was indeed booted. But the screen is all black and fastboot won't report the device ID.
Bash:
>fastboot --verbose devices -l
???????????? fastboot usb:339869696X
I order to return to Android I have to first boot into the bootloader. If I just reboot the system I will reboot into the revovery again.
Code:
>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001s
Any ideas what else I can try?
Is there an alternative recovery ROM I could try?
All I want is to root the phone and the recovery is only on step into that direction. Which begs the question: Can I root without recovery?
Update:I'm one step further: It's necessary to unplug the USB cable and reboot pressing Volume down + Power Button. That's interesting and I should have tried it earlier.
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?