i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
gawgaw said:
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
Click to expand...
Click to collapse
did you try to use unlocked bin code again?if not then do it again
i do it tooo much,and using many tools
now i can think only one thing.flash the specific ruu.exe for your device and start from the beginning
see here
http://forum.xda-developers.com/showthread.php?t=1672425
otherwise if you have patience wait for someone else to provide you a solution
i do all of this and install <RUU FILES>and the problem not fixed ,i copy this information to help you and indicate my problem
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\george>cd C:\Program Files\Android\android\platform-tools
C:\Program Files\Android\android\platform-tools>Unlock_code.bin
C:\Program Files\Android\android\platform-tools>fastboot flash unlocktoken Unloc
k_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.192s
C:\Program Files\Android\android\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 3.243s]
finished. total time: 3.250s
C:\Program Files\Android\android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.190s]
finished. total time: 3.195s
C:\Program Files\Android\android\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (23984 KB)...
OKAY [ 4.164s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.370s
C:\Program Files\Android\android\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.431s]
finished. total time: 0.435s
confirm something
when you use the ruu.exe did you have successful result for flashing it?
yes,the result successful but the problem not fixed ,bootloader relocked
gawgaw said:
yes,the result successful but the problem not fixed ,bootloader relocked
Click to expand...
Click to collapse
ok then
the only thing that i can tell you is to follow the whole process for unlocking the bootloader
start from the beginning.if that don't work too then i am out of ideas
best wishes
if i think something else i will tell you
thank you tooo much ,im sorry to tired you
Can you boot the phone now?
Also did the phone came from a repair with motherboard replaced?
Sent from my HTC Sensation using xda premium
Related
Hi all,
I have a friend's nexus 5, that I try to unbrick. Unfortunally, and after dragging all threads about unlocking via fastboot, I'm still unable to fix his device.
The fact is, I'm able to unlock (fastboot oem unlock) , then when I reboot the bootloader, it's back locked.
I've tried to flash stock bootloader (for both nexus 5 bootloaders (HHZ11k, HHZ10x) but without success
The device is locked on a bootloop Google screen, impossible to access to recovery mode (via fastboot or via vol up + power)
Anybody's got an idea ?
here is a sequence of trying to update bootloader, you can see that I must unlock for allmost each step
Code:
./fastboot oem unlock
...
OKAY [ 2.596s]
finished. total time: 2.596s
./fastboot erase boot
erasing 'boot'...
OKAY [ 0.217s]
finished. total time: 0.217s
./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.215s]
finished. total time: 0.215s
./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.219s
./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.221s]
finished. total time: 0.221s
./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.493s]
finished. total time: 0.493s
./fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 0.404s]
finished. total time: 0.691s
./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
./fastboot oem unlock
...
OKAY [ 2.130s]
finished. total time: 2.130s
./fastboot oem unlock
...
OKAY [ 3.665s]
finished. total time: 3.665s
./fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.514s]
writing 'radio'...
OKAY [ 2.850s]
finished. total time: 4.364s
./fastboot oem unlock
...
OKAY [ 2.999s]
finished. total time: 2.999s
./fastboot -w update image-hammerhead-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ10x
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 02ffc80f08e51d0d
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ10x'.
Update requires 'HHZ11k'.
finished. total time: 0.601s
You need to flash the right bootloader first before the rest can go through
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with fastboot boot recovery.img).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (FAILED (remote: invalid bootloader image))
benoit.bds said:
yep, the fact is I can't find anywhere a bootloader to flash for my version (HHZ10x).
The only files I found are those from Google.
I've tried both for same result.
I've find updates from this thread but I can't boot in recovery mode (from fastboot mode or with
Code:
fastboot boot recovery.img
).
Maybe there is a way to flash those files (from above thread) but I've tried with files (like bootloader.aboot.img, bootloader.imgdata.img, bootloader.rpm.img, etc, ...) without success (
Code:
FAILED (remote: invalid bootloader image)
)
Click to expand...
Click to collapse
Looks like you have corrupted memory and nothing is going to work. Time to rma.
jd1639 said:
Looks like you have corrupted memory and nothing is going to work. Time to rma.
Click to expand...
Click to collapse
i agree.
I don't want to come off as alarmist, but I'm starting to see a worrying trend here. If you look at other threads over the past few days, there have been quite a few people with dying flash chips (myself included). There are a few differences in some of the symptoms, but the most common being that 'fastboot oem unlock / lock' fails to stick. It's like the chip is left in some random state of corruption, and unable to be written to. If I were I betting man, I'd say we can expect to see a flood of these posts in coming days.
I would recommend to anyone with an unlocked bootloader, that you get it locked asap and reset the tamper flag too, just in case this same issue occurs with your phone in future, and you need to RMA it.
To the OP, can you confirm whether the device has been previously unlocked, and whether anything was done to the device leading up to the issue? I'm hoping that if this issue is happening to both locked and unlocked devices that Google / LG will have to take the issue seriously should it become an epidemic.
:crying:
My friend has admitted that his n5 had fallen into water...
He gave it for deoxidation + battery replace, but they didn't manage to boot it more than fastboot mode, so I proposed him to give it a try.
To reply to sir_earl, the device was early bought, stock rom and official OTAs.
Anyway, thank you all for your responses !
Regards
A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.
I did all the set and get my unlock code from HTCdev. Tried all but never UNLOCKED the bootloader !
D:\--- MOBILE\Android\android\platform-tools>fastboot flash unlocktoken Unlock_c
ode.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.152s
Click to expand...
Click to collapse
The phone has a problem it start with Logo HTC then Logo Of operator then it OFF screen.
You still need to run fastboot oem unlock. That just flashes the key.
shinji257 said:
You still need to run fastboot oem unlock. That just flashes the key.
Click to expand...
Click to collapse
I tried but STIll not wotrking
D:\--- MOBILE\Android\android\platform-tools>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.003s]
finished. total time: 0.004s
Click to expand...
Click to collapse
I got home from work plugged my phone in and went to sleep. When I woke up the phone was on the bootloader screen. It wont do anything but switch screens from bootloader to hboot. I have trying installing the stock rom from here http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103 it fails to load from an micro sdcard.
This is a Verizon One M8 phone that has been rooted since release. I have been running Venom http://forum.xda-developers.com/showthread.php?t=2715225 4.3.0 for verizon users.
On the hboot screen it says:
** software statusffical ***
*** Unlocked ***
M8_mlv pvt ship s-offf
cid-vzw__001
hboot-3.19.0.0000
radio-invalid_ver_info
opendsp-invalid_ver_info
os-4.17.605.5
emmc-boot 2048mb
(time and date)
Also when it reboots it shows the android guy in the middle of the screen. It never show the HTC logo.
Try flashing a kernel http://forum.xda-developers.com/showthread.php?t=3152454
Kernels for One M8 AOSP Roms Discussion
Sent from my One using XDA Premium 4 mobile app
How do I flash a kernel? I can only get into fastboot.
I tired this:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Shannon>cd\
C:\>cd Android
C:\Android>cd com
C:\Android\com>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.035s
C:\Android\com>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.075s]
finished. total time: 10.075s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.071s]
finished. total time: 10.071s
C:\Android\com>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: 0
(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.081s]
finished. total time: 10.081s
C:\Android\com>fastboot flash zip rom.zip
target reported max download size of 1826336768 bytes
sending 'zip' (1726320 KB)...
OKAY [ 47.915s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.920s
It does not work
I tried this http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
It never gives me the HTC logo screen.
C:\Android\com>fastboot flash recovery twrp-2.8.6.1-m8.img
target reported max download size of 1826336768 bytes
sending 'recovery' (17006 KB)...
OKAY [ 1.573s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 11.713s
C:\Android\com>fastboot flash boot boot.img
target reported max download size of 1826336768 bytes
sending 'boot' (10066 KB)...
OKAY [ 1.001s]
writing 'boot'...
FAILED (remote: image update error)
Sorry I've been busy all day,but try to reboot your phone
Sent from my One using XDA Premium 4 mobile app
That brings me back to the fastboot screen
tjamscad said:
That brings me back to the fastboot screen
Click to expand...
Click to collapse
Ok try a dirty flash of a different rom
Sent from my One using XDA Premium 4 mobile app
I can't flash anything. Everything fails.
tjamscad said:
I can't flash anything. Everything fails.
Click to expand...
Click to collapse
What ROM did you have installed when this happened?
Sent from my One M8 using XDA Premium 4 mobile app
Venom 4.3 for Verizon
SD card method should work always as long as you are using fat32 and have the file name exact. If it's not working too aren't doing one of the two above correct.
Sent from my HTC6535LVW using Tapatalk
Like this?
tjamscad said:
Like this?
Click to expand...
Click to collapse
Does it do that everytime you flash it? The same exact output?
Sent from my HTC6535LVW using Tapatalk
Yes
I get this when I do factory reset from the hboot screen. I never see the HTC logo like I should.
Like thi
Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
radnam said:
Moto G3 is Bricked,
Device is Locked Status Code:0
XT1550
Tried recovery Mode gives error:
==========
Your Status didn't startup successfully. Use the Software Repair Assistant on Computer to repair your device.
==========
Tried Fastboot it says
C:\Users\admin\Downloads\ADB\ADB and Fastboot>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.048s
Please help.
Click to expand...
Click to collapse
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
adityak1303 said:
Flash stock firmware from here : https://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download links and FAQ are present in that thread.
Click to expand...
Click to collapse
I have tired doing the steps given. However it gives the following error:
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.031s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.459s
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>astboot flash bootloader bootloader.img
'astboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\admin\Downloads\ADB and Fastboot\ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 1.424s
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
acejavelin said:
Just to be sure, you are running this in as an Administrator command window, correct?
It's bricked... Nothing is writing to the internal storage and everything is coming back FAILED. Seen a few of these recently, if it was a different error we might be able to do something but doing 'fastboot oem fb_mode_set' should never give an error.
Click to expand...
Click to collapse
That's what I was wondering. And yes I am running Administrator Command Window.
I am just keeping my fingers crossed that someone can help me resolve the issue.