Related
I was trying to root my Incredible S and was in the process of installing a new ROM on it and the rom got half way through and gave me an error saying that I couldn't install it on my device. Now I can only access the Fastboot screen and nothing else. (I cannot boot Android).
At the top my phone says:
*****Relocked*****
****Security Warning*****
VIVO PUT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.28_M
eMMC-boot
May 22 2012, 14:22:08
I don't have Clockwork Recovery Installed ( I thought I did but forgot to install it ) and I can't access adb as I can't boot android but I can use fastboot.
I have tried using cmd in windows to rewrite the CID which hasn't worked, none of the ROMs I've found online have worked (same error (Customer Identity) and yeah, I'm pretty stuck here.
If I had a Rom in zip format I could upgrade the OS through fastboot which could solve my problem but I can't find any on the net.
Can anyone help me out here??
LinossierB said:
I was trying to root my Incredible S and was in the process of installing a new ROM on it and the rom got half way through and gave me an error saying that I couldn't install it on my device. Now I can only access the Fastboot screen and nothing else. (I cannot boot Android).
At the top my phone says:
*****Relocked*****
****Security Warning*****
VIVO PUT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.18.00.28_M
eMMC-boot
May 22 2012, 14:22:08
I don't have Clockwork Recovery Installed ( I thought I did but forgot to install it ) and I can't access adb as I can't boot android but I can use fastboot.
I have tried using cmd in windows to rewrite the CID which hasn't worked, none of the ROMs I've found online have worked (same error (Customer Identity) and yeah, I'm pretty stuck here.
If I had a Rom in zip format I could upgrade the OS through fastboot which could solve my problem but I can't find any on the net.
Can anyone help me out here??
Click to expand...
Click to collapse
You have relocked your bootloader for some reason. You can unlock it again in fastboot by reflashing your unlock token that you got from HTC.
Code:
fastboot flash unlocktoken unlock_code.bin
Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't unlock and custom recovery again my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks
Yorgan said:
Hi guys.
Yesterday i decided to s-off via rumrunner.
I was on a GPE ROM (so yes, rooted, twrp recovery and custom rom) so i downloaded and flashed a sense based ROM as suggested, but after repeating 2 times the 8 pouring attempts i was still s-on.
I decided to try another sense base flashing a ruu back to stock to be sure it was compatible, so I relocked the bootloader.
The ruu install went immediately wrong (FAILED signature check verification). The problem now is that when I power it on it immediately goes in fastboot mode (yes fastboot, not bootloader). If I press bootloader and then recovery it goes back to fastboot.
So I tried another thing: unlock again the bootloader to manually flash back a custom recovery to make it work again.
Great idea, so i prepared back the unlocktoken, flash it and BAM: again signature check verification fail.
If I can't relock my only hope I guess its an ruu reset.
Now, I know that I can't revert hboot to an older version, and mine is 1.54.0000 so pretty high, but i tried also a 3.x RUU i found inside the RUU collection thread and got the same error msg.
Also smth must be definitely wrong cause I don't think the Unlocktoken should get that error msg, I never got it!
So to summarize:
- tampered, relocked and s-on 1.54.0000 hboot
- FAILED signature check verification if I try to unlock it via htcdev tocken
- RUU zips get same signature check fail error
- same signature check verification error if I try to manually flash just the boot partition (fastboot flash boot)
Guys I had a Desire, a One XL, a Nexus 4 but I think it's the first time I'm stuck with a completely useless slab and really don't know how to recover it.
Really ANY suggestion to make it boot again would be much appreciated...
Thanks
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
nkk71 said:
can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Sure, here it is:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid:
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 4200mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
gencheckpt: 0
Thanks for the quick answer
Yorgan said:
Sure, here it is:
version-bootloader: 1.54.0000
version-main: 2.24.401.1
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__032
Thanks for the quick answer
Click to expand...
Click to collapse
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did
nkk71 said:
A) Do you still have custom recovery? If yes, can you enter recovery, and on your PC open a shell: "adb shell", does it show $ or #
can you copy/paste the command prompt
B) did you get a new unlocktocken from HTCdev, or are you using your old one?
Hit thanks button if I've helped, though it to soon to tell if I did
Click to expand...
Click to collapse
yup i forgot to press it =)
no custom recovery as i said, it just goes back to fastboot, i wanted to unlock it to flash twrp again but this stupid signature check is preventing me from doing anything!
i somehow think that my rom is still inside, just not booting, that's why i also tried to manually flash just the boot.img.
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think
Yorgan said:
nope, i obtained a new one after the old gave me the error, no luck
really i dont know what to think
Click to expand...
Click to collapse
Okay, this is bad
Yorgan said:
that's why i also tried to manually flash just the boot.img.
Click to expand...
Click to collapse
Won't work with locked/relocked bootloader
Yorgan said:
no custom recovery as i said, it just goes back to fastboot,
Click to expand...
Click to collapse
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?
nkk71 said:
Okay, this is bad
Won't work with locked/relocked bootloader
A) did you at any point flash a stock recovery? (either using a Guru Reset ROM or fastboot flash recovery etc?)
B) have you tried:
fastboot erase cache
fastboot reboot-bootloader
and try to enter RECOVERY (using the volume and power buttons)?
Click to expand...
Click to collapse
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?
Yorgan said:
Nope i never wanted to remove TWRP, but does relocking bootloader not flash back the stock one?
Unluckily it just enters fastboot no matter if i power the phone up with or without volume buttons pressed!
I always thought that "if there's fastboot there's hope", but how to bypass the signature check if i'm s-on?
And why the heck does it fail checking signature of the Unlocktoken?
Click to expand...
Click to collapse
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
It vibrates, White screen with Htc logo, it writes 'entering recovery' for half a second and then back to fastboot
nkk71 said:
you're definitely in a pickle here.
But when in bootloader screen (the screenshot attached), can you select the second line; use VOL DOWN to get to second line, then press POWER to select it, where does it go?
Click to expand...
Click to collapse
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))
Yorgan said:
OMG the UnlockCode worked!
Just to let you know, i changed absolutely nothing: the command i sent was the same as before and so was the token.
I think that maybe one of the many failed RUU attempts just flashed the partition i was missing, not enough to flash rom but enough to check the signature of the token!
Thx a lot dude, you gave me the hope to try to mess around again =)
Happyyy =))
Click to expand...
Click to collapse
:good::good::highfive::highfive::highfive::highfive::highfive::highfive::highfive: (I know that looks funny )
So go get yourself S-Off, and never go back S-On. S-Off is your "get out of jail" card!!!
Do not relock, unless S-Off, there's a thread somewhere around here where plenty of people weren't able to get HTCdev to unlock again!!
Any other help needed, let me know.
Hi guys,
So today I got the 4.4 OTA update on my HTC One M7.
Of course I downloaded it and the phone entered into boot loop - "No command" and "Error".
Via pressing POWER + VOLUME DOWN I entered into the service screen, where I have the following options:
***LOCKER***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
OS-3.07.1700.1
eMMC-boot 2048 MB
Aug 19 2013, 21:01:47.0
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGECRC
SHOW BARCODE
I have tried doing FACTORY reset, but to no luck the phone goes into Erasing mode and then again into the "No command" and "Error" loop.
I don't have the htc one USB drivers currently on my Windows 8.1 laptop.
Could you advice me how to proceed.
Thanks in advance.
I am offering a reward for any help.
You need to fix your driver issue FIRST..
Then unlock bootloader using fastboot oem unlock
As you are S-OFF, you can then run the fastboot flash ruu.zip. Follow the steps from: http://forum.xda-developers.com/showthread.php?t=2358781
Hello, today I've bought a used HTC One. It's soft bricked (I guess), I don't know what was done with it before, but previous owner said it was running official KitKat, I don't know if that's true.
Phone's bootlooping but I can get into bootloader, fastboot. When I try to access recovery it says entering recovery mode... and then reboots. Same happens if I choose Factory reset from bootloader menu.
I can't get this phone working with ADB. I've installed all drivers a few times. When I connect phone to computer I can hear Windows USB input sound and phone says "FASTBOOT USB" but adb is not detecting it. When I type "adb devices" I get no devices. I guess that's because USB debugging is off and I can't enable it since phone is in bootloop.
What I could do with it?
Bootloader information:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMc-boot 2048MB
Oct 17 2013, 23:06:14.0
I would appreciate any help, thank you.
Jst check out for ur mobile's official stock rom & install it
martis347 said:
Hello, today I've bought a used HTC One. It's soft bricked (I guess), I don't know what was done with it before, but previous owner said it was running official KitKat, I don't know if that's true.
Phone's bootlooping but I can get into bootloader, fastboot. When I try to access recovery it says entering recovery mode... and then reboots. Same happens if I choose Factory reset from bootloader menu.
I can't get this phone working with ADB. I've installed all drivers a few times. When I connect phone to computer I can hear Windows USB input sound and phone says "FASTBOOT USB" but adb is not detecting it. When I type "adb devices" I get no devices. I guess that's because USB debugging is off and I can't enable it since phone is in bootloop.
What I could do with it?
Bootloader information:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.401.1
eMMc-boot 2048MB
Oct 17 2013, 23:06:14.0
I would appreciate any help, thank you.
Click to expand...
Click to collapse
When you see fastboot usb in the bootloader, your in Fastboot mode. adb will not work. Type fastboot devices.
Sent from my HTC One using XDA Premium HD app
Can you post an output of fastboot getvar all (remove imei/sn) ?
Now how I flash a new rom with only fastboot?
Maybe I should return to stock?
Edit: Can I flash RUU if I relock bootloader?
From image version: 3.62.401.1
To image version: 1.28.401.7
I've found somewhere, that it's okay to flash with diffrent image version, some guy in a video said, that you must have same image version numbers, so I don't know.
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main:3.62.401.1
version-misc: PVT SHIP S-on
serialno: it's ok
imei: (it's ok, lots of numbers)
meid: 0000000000000000000
product:m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery...
voltage...
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
martis347 said:
Now how I flash a new rom with only fastboot?
Maybe I should return to stock?
Edit: Can I flash RUU if I relock bootloader?
From image version: 3.62.401.1
To image version: 1.28.401.7
I've found somewhere, that it's okay to flash with diffrent image version, some guy in a video said, that you must have same image version numbers, so I don't know.
Click to expand...
Click to collapse
No, you can't as you are S-ON. You can downgrade only if you are S-OFF.
Please try the following, even if you have tried it and paste your command prompt output.
- Connect the phone in fastboot mode.
- Downlaod stock recovery: http://d-h.st/WJ8
fastboot flash recovery stock_3.62.401.1.img
fastboot erase cache
fastboot reboot-bootloader
Try to enter recovery, you should see a triangle with android or a red exclamantion mark. Post back if your device can still NOT enter stock recovery
May have to try flashing couple times
Flashed twice, when I choose recovery in bootloader it only reboots and starts bootlooping.
I've uploaded log picture, it's faster than rewriting.
martis347 said:
Flashed twice, when I choose recovery in bootloader it only reboots and starts bootlooping.
I've uploaded log picture, it's faster than rewriting.
Click to expand...
Click to collapse
Interesting. You are having the same issue as another user right now. Try this please:
Download http://files.trjlive.com/android/htc/one/firmware/firmware_3.62.401.1.zip
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Type: fastboot reboot-bootloader
Type: fastboot erase cache
Please select Bootloader and then select recovery to enter stock recovery. Post back your result.
I should flash, firstly reboot bootloader and then erase cache? Because in previous post order was: flash,erase cache, reboot, as far as I know you have to clear cache and then reboot. Or it doesn't matter?
Please follow as written in my instructions.
I've done everything like you said.
Type: fastboot oem lock (if your device is not relocked yet) (Phone rebooted. Then in bootloader it said relocked)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete I got error both times. While flashing first time I renamed "firmware_3.62.401.1.zip" to "firmware.zip" When flashing second time I renamed it back to "firmware_3.62.401.1.zip"
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware_3.62.401.1.zip and wait for process to complete
Type: fastboot reboot-bootloader
Type: fastboot erase cache
Now phone is same as it was. No recovery, when I'm trying to access it it just reboots and keeps bootlooping.
Sorry looks like the firmware was not signed., yoru fastboot indicates the failure. Please retry with: http://xda7.androidrevolution.nl/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
I checked it is signed.
Now somehow phone does not detect computer when I try plugging in. I mean when I connect it to pc, it's not responding. If i plug it to a wall charger it says Fastboot AC, if i plug it to computer it says only FASTBOOT. Didn't occur before...
Restart computer??
SaHiLzZ said:
Restart computer??
Click to expand...
Click to collapse
I've tried a different computer, restarted mine, nothing changes.
I think phone's charging animation (while off) has changed.
Okay, I got it working.(Haven't tried a port where my mouse is connected)
Flashed firmware like you said, from second try everything went okay.
Tried booting to recovery, still no change. Just bootloops...
damn .. sucks if the official recovery is failing to boot as well. dont have any other suggestions.
SaHiLzZ said:
damn .. sucks if the official recovery is failing to boot as well. dont have any other suggestions.
Click to expand...
Click to collapse
Can't I flash a ROM through FASTBOOT?
Or is there any chance to use RUU?
There is no RUU For 3.62.401.1 or higher. As you are S-ON, you can NOT flash the lower version RUU. You should pray for the day someone releases the RUU for 3.62.401.x or higher!
I am intentionally NOT suggesting you to run the 4.19.401.8 as that will most likely not help and if a month later someone releases the 3.62.401.x RUU, you wont be able to run it. Staying at a lowest possible version will help your odds, however small they are right now.
Please - I Need Urgent Help from anyone who knows...Please , please help.
I got a new HTC M7 and Tried RUU.Exe (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651 .10) update ....
The update was failed with error 152 ....(I have tried it many times but failed again and again)
Now The phone is just displaying 4 triangles at corners with black HTC Logo.
It is showing (when try power + Volume down , for recovery)
***unlocked***
M7-WLS PVT SHIP S-ON RH
Hboot- 1.61.0000
Radio- 1.02.20.0922
Opendsp - v35-120-274-0710
OS - 6.23.651.10
emmc-boot 2048MB
sep 22.2015 time...
RUU..
There is no other option (like fastboot , recovery or any thing below RUU .....
It is not detecting as storage in widnows but shows as My HTC in device manager of PC
I have tried to Flash/Push Firmware through fastboot/adb but it fails...
faheem1982 said:
Please - I Need Urgent Help from anyone who knows...Please , please help.
I got a new HTC M7 and Tried RUU.Exe (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651 .10) update ....
The update was failed with error 152 ....(I have tried it many times but failed again and again)
Now The phone is just displaying 4 triangles at corners with black HTC Logo.
It is showing (when try power + Volume down , for recovery)
***unlocked***
M7-WLS PVT SHIP S-ON RH
Hboot- 1.61.0000
Radio- 1.02.20.0922
Opendsp - v35-120-274-0710
OS - 6.23.651.10
emmc-boot 2048MB
sep 22.2015 time...
RUU..
There is no other option (like fastboot , recovery or any thing below RUU .....
It is not detecting as storage in widnows but shows as My HTC in device manager of PC
I have tried to Flash/Push Firmware through fastboot/adb but it fails...
Click to expand...
Click to collapse
Simple:You must relock the bootloader to flash a RUU on a S-ON phone. Relock it and flash the RUU again.
fastboot oem lock
I have tried this
alray said:
Simple:You must relock the bootloader to flash a RUU on a S-ON phone. Relock it and flash the RUU again.
fastboot oem lock
Click to expand...
Click to collapse
I have tried this also...Relocked ..But update failed again..
***Relocked***
S-ON
Same result
faheem1982 said:
I have tried this also...Relocked ..But update failed again..
***Relocked***
S-ON
Same result
Click to expand...
Click to collapse
Keep it locked, its must be in this state to flash a RUU.
What is the error when trying to flash the ruu exactly? Is it still error 152?
Sometimes same sometimes different
alray said:
Keep it locked, its must be in this state to flash a RUU.
What is the error when trying to flash the ruu exactly? Is it still error 152?
Click to expand...
Click to collapse
After doing that, it is same error once... 152
then when I attempted again in relocked state..It given error 132
Third time it given error number 155...
Mostly it is either 152 or 155 ..When I check Phone screen after getting error
"Partition Update Fail"