{
"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)
Related
Hi guys, i have a htc on sv. the system not start and enter on recovery
https://www.dropbox.com/s/8xfq4s4rdygh8d9/IMG_20140531_185337.jpg
As you can see i cant remove the S-On (i try htcdev, send me all instruction , i did all fine , but cant select of like the instruction of htcdev)
i try another way for install into microsd or with fastboot the rom
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT312TP02396
(bootloader) imei: **********
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3466mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.080s
Click to expand...
Click to collapse
if i try to go on recovery
SD Checking...
No gift file....
Loading...[PL80DIAG.zip]
No image!
Loading...[PL80DIAG.nbh]
No image or wrong image!
Loading...[PL80IMG.zip]
Loading...[PL80IMG.nbh]
No image or wrong image!)
Click to expand...
Click to collapse
so i found this : RUU_K2_UL_JB_45_S_HTC_Europe_2.14.401.6_R_Radio_1. 15.40a.00.14_2_10.74a.40.23L_release_unsigned.zip
i try to install but give me error , i try to extract rom.zip and renamed to pl80diag.zip, (into microsd) , try the recovery...seems fine but give me error
so i try to :
C:\Android>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(735): error 2
(bootloader) Start Verify: 3
OKAY [ 0.037s]
finished. total time: 0.037s
C:\Android>fastboot flash zip RUU_K2_UL_JB_45_S_HTC_Europe_2.14.401.6_R_Radio_1.
15.40a.00.14_2_10.74a.40.23L_release_unsigned.zip
sending 'zip' (604746 KB)...
OKAY [ 35.290s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 109.491s
Click to expand...
Click to collapse
what can i do? the way is right or i need to do something new?
To go to recovery you can press and hold the power and volume down keys while your device is powered off. Then when your bootloader appears on the screen select the recovery option. Or you can use adb and type then enter:
Code:
adb reboot recovery
What you showed to be your recovery is NOT your recovery. That is your bootloader. They are different.
The only way you will achieve an unlock bootloader for your device will be to use your unlock_code.bin file provided to you through an email by HTC.
You must be in fastboot to proceed using that file.
On your screen it should display in red text, fastboot usb. When you see this on your screen then you may continue forward with unlocking your bootloader using the .bin file and instructions provided to you from HTCDEV.
With this said, you have already opened up a thread over in the Q&A section. This is a forum for Android Development.
Sent from my C525c using Tapatalk
Modding.MyMind said:
To go to recovery you can press and hold the power and volume down keys while your device is powered off. Then when your bootloader appears on the screen select the recovery option. Or you can use adb and type then enter:
Code:
adb reboot recovery
What you showed to be your recovery is NOT your recovery. That is your bootloader. They are different.
The only way you will achieve an unlock bootloader for your device will be to use your unlock_code.bin file provided to you through an email by HTC.
You must be in fastboot to proceed using that file.
On your screen it should display in red text, fastboot usb. When you see this on your screen then you may continue forward with unlocking your bootloader using the .bin file and instructions provided to you from HTCDEV.
With this said, you have already opened up a thread over in the Q&A section. This is a forum for Android Development.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Hello , this is the image not compare when i make the procedure HTCDEV, i think not compare because the operating system not go
https://www.dropbox.com/s/2s8t8dar0uil7yc/2014-06-05 17_11_28-HTCdev - Unlock Bootloader.png
@Benz83
You should have a file called, Unlock_code.bin. Place it in the same directory that currently holds your adb and fastboot files. Open up the command prompt window and change directories to the location where your adb and fastboot files currently are.
Type the following:
Code:
adb reboot bootloader
You should now see on your device screen, fastboot usb.
Go back to your command prompt window....
Type the following:
Code:
fastboot flash unlocktoken Unlock_code.bin
On your device you’ll get a message saying if you want to unlock your bootloader. Use the volume keys to select your choice, and hit the power button to confirm. Once you’re done, your device will restart and you’ll have an unlocked bootloader.
Sent from my C525c using Tapatalk
sincerally the reply on msdos is ok, all done
on the phone i not see nothing and i not see the image i posted, i will try again
Benz83 said:
sincerally the reply on msdos is ok, all done
on the phone i not see nothing and i not see the image i posted, i will try again
Click to expand...
Click to collapse
I edited my last comment. Go back and read it again.
Sent from my C525c using Tapatalk
No choose to select. Only reboot automatically
@Benz83
I want you to tell me where on your computer you currently have your adb, and fastboot files. I also want you to tell me where on your computer you currently have your Unlock_code.bin file.
Type it out as it would be on your computer.
Sent from my C525c using Tapatalk
easy
its all inside the C:\Android
fastboot adb and unlock
so inside the dir C:\android
the phone reboot on fastboot usb i type
fastboot flash unlocktoken Unlock_code.bin
Benz83 said:
easy
its all inside the C:\Android
fastboot adb and unlock
so inside the dir C:\android
the phone reboot on fastboot usb i type
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Good, so you are doing it the right way. Boot your device in to your bootloader using adb.
Code:
adb reboot bootloader
Then on your device select the option, bootloader. At the top of your screen on your device it should say either locked or unlocked. Which one does it show for you?
Sent from my C525c using Tapatalk
Modding.MyMind said:
Good, so you are doing it the right way. Boot your device in to your bootloader using adb.
Code:
adb reboot bootloader
Then on your device select the option, bootloader. At the top of your screen on your device it should say either locked or unlocked. Which one does it show for you?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
locked :crying:
Benz83 said:
locked :crying:
Click to expand...
Click to collapse
Your Unlock_code.bin is corrupted then. Try redownloading it from the attachment in your email. If it still doesn't work then you either left out some needed info when copying and pasting your token or you added more info than what was actually needed while following the steps on the HTCDEV website.
You may need to do that step again and insure you copy EXACTLY what is needed for your Unlock_code.bin file. Then when you receive your new .bin file go ahead and do as you have been doing with trying to unlock your bootloader.
Sent from my C525c using Tapatalk
ok, i will do again, (sincerally i did twice)
Benz83 said:
ok, i will do again, (sincerally i did twice)
Click to expand...
Click to collapse
Make sure you choose "other" when selecting your device.
Sent from my C525c using Tapatalk
yes yes, infact there isnt thad device
Benz83 said:
yes yes, infact there isnt thad device
Click to expand...
Click to collapse
nothing to do, i try again the all procedure but the screen step 10 after command fastboot flash unlocktoken Unlock_code.bin not let me choose nothing
ok, i will do
I also have this problem
hi
i have a HTC one SV and when tern on android not loded and go to bootloader.
i try factory reset but fast reset and come back to bootloader
i try unlock bootloader but after step 10 in htcdev in my phone not show dialog to select YES or NO
in my android folder contain this files:
{
"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"
}
I've searched until I find a solution to my problem but I can not find any solution.
Can you advise me what should I do?
tanks
I don't know, whats wrong with your phone, but why are you doing a "fastboot oem rebootRUU"?
When i can remember correct, this is not needed for unlock, after flashing unlock token.
{
"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
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)
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.