Database Develop

[Q] my hero can't boot into recovery .. Can anyone help me

my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help

Place this on the root of your sdcard. Boot into hboot (fastboot) and press the down volume key, that's hboot mode. It'll find the HERCIMG.zip, which is just the RUU and after it flashes you're phone will be back to stock.

DoonRoman said:
my hero cdma can't boot into recovery and can't work only in the normal position after use (fastboot oem boot)
when i power the device and unplug USB cable show me in the screen this lines
Code:
HERO XC SHIP S-OFF
HBOOT-1.47.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-2.41.05.02.99
Mar 1 2010, 16:02:39
RUU
Even when I press volume down + power .. the screen remains black and does not show anything
I tried a lot to work root and flash recovery.img again by (recovery-RA-heroc-v1.6.2.img) .. but every time i enter ((reboot recovery)) does not appear to me anything except previous message ..
my software v2.27.651.5
pardon me because i can't speak english well .. and I ask for your immediate help
Click to expand...
Click to collapse
Im having the same exact error
what i did first is that i accessed the recovery mode without knowing and i did the wipe/factory default settings
it brought me to a black screen with only the top slider while that the recovery mode was working
later i installed the ruu software 2.27.651.6 and downloaded it from htc website , at the end of the installing it showed file error cant open
i thought i was just that software (and i didnt download it right) later i tried installing the 1.27 , 1.56 , 2.27.651.5 and the 2.27.651.6 again and it still gave me the same error
after searching on the net i found the command fastboot oem boot which works only with 2.27.651.5 and the 2.27.651.6 version now i cant open my htc hero sprint without this command ,
is there a way to fix it ? please help

It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...

cytherian said:
It sounds to me like the only way you'll be able to fix your phone is through adb. I'm not sure of the exact steps, but read up on the procedures that have been written up on using adb and you should be able to find what you need. That's all I can think of...
Click to expand...
Click to collapse
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported

mrxuser said:
im already familiar to the adb and fastboot commands , tho i dont know the exact steps to fix my problem , because the other steps i found on the net crashes at a point such as flash_image says it cant find the image , and the fastboot flash update.zip says image is not supported
Click to expand...
Click to collapse
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?

cytherian said:
Bummer... well, sorry I don't know what else to tell you at this point. If you follow the steps for putting your phone completely back to stock and it crashes before it completes, then your phone may have a hardware problem. Did you overclock it at all?
Click to expand...
Click to collapse
what do u mean by overclocking

mrxuser said:
what do u mean by overclocking
Click to expand...
Click to collapse
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?

ElementalBeatz said:
Overclocking makes the phone faster, in simple terms. It's risky. I assume that you didn't?
Click to expand...
Click to collapse
yes never done it before, would the phone be fixed if i did?

No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.

cytherian said:
No, I only brought it up because overclocking can challenge the hardware and if it overheats then you might run into functional issues. If you didn't overclock then this isn't a factor.
I don't have my main computer handy with all of my browser shortcuts (I've got quite a library from researching rooting, modding, etc), but I know for certain that there are at least 3+ ways to load a new recovery program onto your phone, or get back to a stock ROM even if you brick your phone. You'll have to take the time to search the forums for those earlier guides, the ones before programs were developed to make rooting and flashing ROM's easier (not needing to know much about adb). AndroidForums has quite a few good ones. Check out their FAQ for the HTC Hero.
One other thing... I noticed your bootloader is 1.47. I had issues with that bootloader, with trying to set S-OFF. I had to override with 1.46. You might want to try an earlier bootloader.
Click to expand...
Click to collapse
If u dont mind can u show me how to install earilier bootloaders ?

Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki.
Click to expand...
Click to collapse
I already told u that i can use Adb and fastboot , i cant open my phone unless i use this command fastboot oem boot ,

Well good luck with that...

cytherian said:
Since you can't get your phone fully booted, you won't be able to use ADB. But if you can load the bootloader into Fastboot USB, then use "fastboot". Read up on the Fastboot Wiki and Flash Tutorial. The only caveat is that I've seen two variations on flashing the bootloader using fastboot. Whereas the Wiki I linked shows "fastboot flash boot boot.img", I've also seen "fastboot flash hboot.img" (but I think that may be a typo--certainly it'll let you know).
If you have a ZIP file instead of an IMG file, there will be an "hboot.img" within the ZIP file. I think the fastboot is intelligent enough to know that it needs to be applied to the boot partition. So, you can also do this:
* fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
* fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
-- or --
* fastboot flash boot [boot.img]
However, if your current bootloader state is S-ON, you may not be able to execute those commands successfully. I know for myself I had to install ROM Manager to override the hboot 1.47 S-ON that I had installed, which downgraded the hboot. From there I was able to override and flash hboot 1.46 S-OFF.
Click to expand...
Click to collapse
here is the problem while flashing using fastboot
fastboot flash radio radio1.img
sending 'radio' (21376 KB)...
OKAY [ 24.089s]
writing 'radio'...
FAILED (remote: image type not support)
finished. total time: 24.108s
or here when i use flash the zip
fastboot flash zip update.zip
sending 'zip' (118067 KB)...
OKAY [129.171s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 132.015s
why does the (remote: image type not support) or the (remote: 24 parsing android-info fail) appear

Have you tried what I posted yet?

Shelnutt2 said:
Have you tried what I posted yet?
Click to expand...
Click to collapse
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!

mrxuser said:
the problem is that i cant no more enter the hboot menu but i can use the fastboot commands while the Htc silver Logo appears
> fastboot devices
HT9BEHF03035 fastboot
and when i used this command
>fastboot flash zip HERCIMG.zip
sending 'zip' (114210 KB)...
OKAY [129.813s]
writing 'zip'...
its stuck on writing 'zip' and havent done anything for more than 20 min , whats wrong here ??!!
Click to expand...
Click to collapse
so there's nothing to help

Guys , Arent there anything to do to my program ,,, if somebody knows ,,,, please tell me

[Q] My One won't boot up, no OS?

Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.

AllAboutTheCore said:
Hi Guys
I'm in need of urgent help. I rooted my phone and unlocked the bootloader and was going to flash a couple of modded files, one was a more transparent weather widget. Anyways, I somehow ended up with my phone stuck at the "HTC, Quietly Brilliant" screen and it won't boot up. It say's there is no OS installed and I am completely at a loss on what to do because I can't for the life of me understand what RUU I need. I'm in the UK and I bought the phone sim free but none of the resources I've checked seem to be clear. Obviously I am unable to put a ROM on my SDCard as I can't access it so I have no clue how to just get my phone back to stock ... I came from an Xperia Ray where things were so simple. Why isn't there any software from HTC like there is with Sony that lets me reinstallt firmwares? I am at my wits end here with a two day old, £500 phone that I can't even turn on!
PLEASE can someone help me, I know it can be donw but I have no experience with cmd really and there doesn't seem to be any standalone tools to sort it out.
Thanks in advance.
Click to expand...
Click to collapse
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium

redbull123 said:
Can you access the hboot screen on boot up and get into recovery?
If you can, try using the all in one toolkit to sideload a ROM.
http://forum.xda-developers.com/showthread.php?t=2183942
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Cheers for your reply ... Yes I can get into recovery and for further info I follwed a guide on how to install a stock ROM which I downloaded and follwed the re locking of the bootloader which worked but when it comes to installing the firmware.zip file it works but when it gets to the checking bootloader signature part it always fails and says remote 12 signature verify fail, I'm out of my depth here lol This is what I did:
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
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.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.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I followed that but when it gets to step 11 it always comes back with this error message:
sending 'zip' (955862 KB)...
OKAY [ 44.588s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.891s

Decided to take it back to the shop and they just replaced it luckily enough so problem solved ... Thank f**k, I was getting worried and I'd certainly gone past the point of me being able to resolve the issues as even I'd lost track of what I'd done lol .. Cheers to redbull123 for even trying to help

Cannot unlock a relocked bootloader

Got myself in a bit of a mess
Had a S-OFF device with bootloader unlocked (using revone).
Was going to sell on, so put back to S-ON, but this was done before I relocked the bootloader (so bootloader stayed at Unlocked). I've now relocked the bootloader using fastboot oem lock.
However wifi is not working (stuck on turning on), as I appear to have ended up with the wrong kernel.
However, trying to unlock (through htc dev), got by unlock_code.bin, I am running the following command;
fastboot flash unlocktoken Unlock_code.bin
which responds with;
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.142s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.146s
But it is not popping up with anything on the phone, and the bootloader stays at relocked.
Am I stuck, at the bootloader was originally unlocked using revone and now is at status relocked ?
Thanks.

saquib said:
Got myself in a bit of a mess
Had a S-OFF device with bootloader unlocked (using revone).
Was going to sell on, so put back to S-ON, but this was done before I relocked the bootloader (so bootloader stayed at Unlocked). I've now relocked the bootloader using fastboot oem lock.
However wifi is not working (stuck on turning on), as I appear to have ended up with the wrong kernel.
However, trying to unlock (through htc dev), got by unlock_code.bin, I am running the following command;
fastboot flash unlocktoken Unlock_code.bin
which responds with;
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.142s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.146s
But it is not popping up with anything on the phone, and the bootloader stays at relocked
Am I stuck, at the bootloader was originally unlocked using revone and now is at status relocked ?
Thanks.
Click to expand...
Click to collapse
Hi, what boot r u? If you are 1.44 use revone again. The only other thing I can think of is to call fonefunshop to see if they could s-off the device again for you.

I am on HBOOT 1.54 unfortunately.
I don't really want s-off, just the unlocked bootloader.

saquib said:
I am on HBOOT 1.54 unfortunately.
I don't really want s-off, just the unlocked bootloader.
Click to expand...
Click to collapse
Just to cover all bases - after it said complete did you reboot the bootloader using 'fastboot reboot-bootloader'?

I had not, I was expecting the phone screen to display the options to unlock ?
Anyway, I tried that, which gives the following;
fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: loading custom splash failed)
finished. total time: 0.016s

Any ideas? I need to unlock the bootloader as my WiFi is broken. Cannot turn on, I think the reason is that I've ended up with a kernel for a 401.1 Rom but I'm on a 401.8 Rom.

Hi,
if you cid allows try an ruu. If no go then send off to fonefunshop to get s-off. Its got to be worth it to get the phone working again. From personal experience I can say they are fast. Give them a call first to discuss.

It sounds like you possibly went S-on with a custom Hboot. Perhaps the one that removes the red text?
Sent from my One using XDA Premium 4 mobile app

Thanks for the input.
1. I used one of the roms from this thread to return to stock : http://forum.xda-developers.com/showthread.php?t=2471869
2. Comparing the HTC one with the broken wifi to another htc one on 4.2.2, the old difference I can see is in the kernel versions;
- Broken HTC: 3.4.10-g445d072
- Working HTC: 3.4.10-g28df0d6
I don't really want to spend £30 on s-off, if I could unlock the bootloader, I should be able to flash a rom to get wifi working, I think ?
Thanks.

EddyOS said:
Just to cover all bases - after it said complete did you reboot the bootloader using 'fastboot reboot-bootloader'?
Click to expand...
Click to collapse
I had not, I was expecting the phone screen to display the options to unlock ?
Anyway, I tried that, which gives the following;
fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: loading custom splash failed)
finished. total time: 0.016s

Anyone with any ideas ? Is there anything I can do without a RUU and a relocked bootloader to change the kernel to the correct version for the rom ? Thanks!

One thing I've noticed is the the first screen I see when the phone is turned on is a Google logo rather than the HTC logo. Obviously I've got some remnants of a Google Edition Rom left on my phone.
Am I completely lost without s-off ?
Sent from my HTC One using xda app-developers app

Have you fixed this? I have the same problem. Thanks

FIXED!!
I had this exact problem. Android 4.3 is now available via control panel, software updates. I downloaded via mobile data and installed the update and the phone now works fine, including wifi. Hopefully you have a good mobile data plan because the download is >600MB

[Q] Stuck in RElocked bootloader cannot unlock

Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!

FURTHER to the above
jaqzilch said:
...
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,

jaqzilch said:
Hello, I've been raking up the other xda posts all night and can't seem to find the right solution for my situation. Am a total noob so would really appreciate any instructions, whether to solve the problem or to point me to the right post. Quite lost here.
So, I've been trying to return my HTC one to stock (hk version; CID: HTC__622; modelid: PN0714000) and got into trouble. I used to have CM 10.2 with TWRP recovery. So I used TWRP to install what I thought was a stock ROM (not sure if I'm using the terms right) My current situation, in gist:
(1) Can only load into bootloader, if reboot normally then I get htc splash screen then black screen. -->Refuses to boot into the operating system!!!!!! All I get is the htc flash screen then the black screen until eternity (or I force reboot it by holding vol down and power button under strong light-- tip I got from these parts)
(2) Bootloader (top of) reads "tampered" (which I'm least concerned with) and "relocked"
(at one point it said "security warning" as well… but then that disappeared-- see below)
(3) I cannot use adb via either my Mac/ Windows, I have downloaded google SDK and updated HTC drivers on both machines-- adb devices command simply does not register my phone
(4) atm I am only communicating to my phone via fastboot commands… of which I know next to nth except what are commonly found in these forums…
(5) My machine is still S-off. Before my troubles, it was hboot 1.54, after messing around with it, it's now 1.55 if that makes any difference.
I desperate need my phone for the working week…. PLEASE HELP!!!
FYI: I'm on a Mac, but I do have access to a Windows machine running Windows 7
What I have done so far:-
(1) So I was trying to get back to stock, right? First thing I did was used HTC1guru's Guru reset. The ROM I installed was actually for the Asia WWE variant.
Anyway, so I installed it, and it worked, to the extent that I could get OTA notifications and downloaded the update. But HTC could not verify it and did not allow me to install the update. Because I wanted the Kitkat update, I looked up the net to see what could be the problem.
(2) The next mistake I made (probably a mistake) was to think that I had to relock the bootloader. So I did that. Now my Bootloader is relocked and I cannot, for the life of me unlock it again (I've tried going through the HTC dev steps and flashing the new Unlock_code.bin again but I can't unlock it)
At this point, the bootloader also read "security warning" under "relocked"
Subsequent to relocking it, I can't get into my operating system anymore. The only 2 outcomes I get on reboot are (1) HTC splash screen followed by black screen; OR (2) bootloader (if I do power + vol down)
(3) As one 'brilliant' idea followed another 'brilliant' idea, I also did the following list of silly and probably mistaken things our of sheer desperation. Throwing the kitchen sink in really. But none of them really worked because they all say sign not verified or sth to that effect-- I honestly am beginning to forget the order in which things unfolded… but if that's relevant, let me know and I'll try to recall more details.
(a) flash a recovery.img (stock, for both Asia WWE and HK version which I found on the web; and also TWRP)
(b) flash boot.img from Asia WWE
(c )tried rumrunner (can't do because adb won't work)
My latest attempt has been flash oem reboot RUU (then used zip of HK version 1.29.708 Rom zip)
and my phone is now stuck at the grey HTC on black background screen one gets after the first reboot RUU command (terminal has not prompted me to enter a second rebootRUU command yet!)
I don't know what to do. I don't even know if I should unplug the phone and redo the rebootRUU thing…
:crying: PLEASE HELP!!!!
Click to expand...
Click to collapse
Ok...
First flash a recovery(use Case 2):
No Recovery? No Problem​​
Oh sh*t here we can have several kind of problems Still no problem But let's first download the recovery.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
(MD5 hash: 72067AEFB69541D40E8420D7AA46408D)
Case 1 - Normal error with unlocked and s off or s on:
Boot your phone into the fastboot mode
Eat a piece of cheese
Enter this command
Code:
fastboot erase cache
Followed by this command
Code:
fastboot flash recovery "C:\path_to_recovery\recovery_name.img"
And enter the recovery and follow the next piece of guide
Case 2 - For some stupid reason you are s off (that's a MUST) and Relocked:
Sorry, you need this recovery:
https://www.mediafire.com/?ni177radvko5xu7 (If it doesn't work, PM me)
(MD5 hash: F2893CDC17C788B2E49AECEA8C02DCB4)
Boot your awesome HTC One into fastboot
Change CID to superCID using this command (make sure you used 8 times a '1')
Code:
fastboot oem writecid 11111111
Enter this command
Code:
fastboot oem rebootRUU
Wait until your Pc recognized your phone again and enter this command
Code:
fastboot flash zip "C:\path_to_zip\firmware.zip"
(This may delete all your data)
Happy rebooting with this command
Code:
fastboot reboot-bootloader
Enter the recovery and let's unlock the bootloader...
You can unlock your bootloader using these commands(thanks @scotty1223 for your thread!):
[how to] lock/unlock your bootloader without htcdev(s-off required)
If this doesn't work in recovery because you get superSU or permission errors, use this tool here instead:
http://www.htc1guru.com/guides/guru-bootloader-reset/
You can simply push the ZIP file to your HTC One using one of these commands:
Code:
adb push "C:\path_to_zip\zip_name.zip" /sdcard/bootloader_reset.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_zip\zip_name.zip" /storage/emulated/0/bootloader_reset.zip
Code:
adb push "C:\path_to_zip\zip_name.zip" /data/media/0/bootloader_reset.zip
Case 3 - You totally ****ed up your recovery and data partition:
Right now, I am pretty busy and I don't have time to develop this, check this guide there and post your question there, but pls don't spam @mike1986.
How to: fix a corrupted DATA partition on the HTC One
​
now you are unlocked and s off... so what we're gonna do depends on what you want to achieve... I didn't really get what you meant in the first post.. you want to be again 100% stock on a Asian ROM ?
with the unlocked bootloader and s off and the custom recovery you are pretty much able to flash the rom you want to the device... how to do this:
http://forum.xda-developers.com/showthread.php?t=2632736
or:
Bootloop, No OS, Totally f*cked up OS? No Problem​​
THIS WILL DELETA ALL YOUR APPS AND APP DATA BUT NOT SDCARD!​
First of all, make a factory reset in TWRP... then follow the next steps.
Now the key step here copying the rom.zip to your sdcard. You do this this way
Since you are in the recovery you should be able, no.. actually will be able to use adb commands
To copy the rom zip us this command:
Code:
adb push "C:\path_to_rom\rom_name.zip" /sdcard/rom.zip
If this one results in supersu and permission errors, try these paths(Thanks @Sneakyghost for this advice!)
Code:
adb push "C:\path_to_rom\rom_name.zip" /storage/emulated/0/rom.zip
Code:
adb push "C:\path_to_rom\rom_name.zip" /data/media/0/rom.zip
Now, in the recovery, choose install and select the rom you should've just copied and install/flash it.
After that make a factory reset, the standart when chosing wipe in TWRP.
Happy rebooting!
​
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
jaqzilch said:
I've unplugged the phone, rebooted into bootloader, and made a second attempt to rebootRUU with HKvariant 1.29 zip… still gets stuck after 1st rebootRUU command (i.e. black screen with grey HTC logo)
Please do help,
Click to expand...
Click to collapse
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs

LibertyMarine said:
Ok...
First flash a recovery(use Case 2):
...
[/INDENT][/INDENT]
---------- Post added at 11:43 AM ---------- Previous post was at 11:39 AM ----------
ok, ok ok... wait with flashing RUUs... you'll mess up your phone if you continue flashing these RUUs
Click to expand...
Click to collapse
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
and nothing happens on my phone.
Re: Case two-- I'm one of those poor S-on folks so…
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!

jaqzilch said:
Hello, LibertyMarine, thanks for the response!
I've already downloaded TWRP recovery from the TWRP website, is the one you give me different?
Re: Case one-- I've actually tried flashing the TWRP recovery image before, but it doesn't seem to work. Thing is, I've idiotically relocked my HTC one now, so that might be the problem.
This is what I get when I try to flash TWRP recovery:-
fastboot flash recovery TWRPrecovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9948 KB)...
OKAY [ 11.854s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 12.707s
Click to expand...
Click to collapse
yeah.. that's because you are locked ....
jaqzilch said:
as for unlocking my relocked bootloader, I've tried numerous times and I simply cannot get my relocked bootloader to unlock again. Whenever I put in the "fastboot flash unlocktoken Unlock_code.bin" (and yes, I've put the Unlock_code.bin into the same folder as fastboot and adb, the terminal gets stuck at "sending 'unlocktoken' (0 KB)…"
Click to expand...
Click to collapse
hmmm... have you tried redownloading/rerequesting a unlock token ?
try that... try requesting a new one and try flashing this one...
jaqzilch said:
and nothing happens on my phone.
Click to expand...
Click to collapse
haven't had such an issue.. I'll do some research on this topic..
jaqzilch said:
Re: Case two-- I'm one of those poor S-on folks so…
Click to expand...
Click to collapse
I don't know why.. I though you were s off... sorry... I must have commuted you with an other guy
jaqzilch said:
Re: Case 3-- looks like they need custom recovery flashed already… but (see Case one above), I can't seem to flash TWRP on my poor phone … : (
As to the last solution-- totally f-ed up OS etc…. again, I don't have TWRP… nor can I used adb
I'd be ever so grateful if I can just find a way to put twrp on my phone again! o gawd….
THanks again for all suggestions!!
Click to expand...
Click to collapse
Yeah... case 3 needs a custom recovery.. but you won't need that one anyways.. because your data partition seems to be OK

Soft Brick Nexus 6 with No Recovery and Bootloop

Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks

You're screwed.
In situations where there is a locked bootloader and a soft brick like this, sideloading a Google OTA image using the stock recovery would have been able to restore the device to operating condition. Unfortunately you have no recovery, and thus no way to restore this device.

If you are stuck in boot loop and have no recovery, there is a way to fix your problem. If fastboot commands work then download Wugs Nexus Root Toolkit and use that to return to stock. There might be a way to unlock the bootloader first and then go from there. Have you tried to get the bootloader unlocked through fastboot commands then flash TWRP. Dude thinks this through. There is always a way to fix a soft brick. I hard bricked not long ago and was able to fix my device on low level systems code. Just don't give up

Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.

Strephon Alkhalikoi said:
Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.
Click to expand...
Click to collapse
I flashed a faulty bootloader image via fireflash app instantly bricked. I went through low level fastboot recovery options. I fixed my device. This is a mid level soft brick it can be fixed just needs some patience and perseverance. If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible. When I bricked it was a black screen, qhusb Qualcomm level I needed to restore my bootloader, I did it. This guy can fix his situation, I could do it for him if I had the device in hand.

Rondeau79 said:
If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible.
Click to expand...
Click to collapse
Look, we can go back and forth on this until blue in the face. The facts of the matter are as follows.
1. The bootloader is locked.
2. There is no OS in the system partition.
3. There is no stock recovery.
4. An OS in the system partition is required to be able to unlock the bootloader.
5. A stock recovery is required to sideload OTA images.
6. The original post does not mention whether the OP tried unlocking the bootloader.
You mentioned Fastboot. Everything you described in the quoted portion of your post works, but only if the bootloader can be unlocked. I'm assuming however the OP tried that already, failed, and went straight into flashing system images. If he didn't try it, he should, although I believe the attempt will fail.

Any help here. I have the exact same situation. Should I take my phone to Motorola/Google for repair? Anything else i can try?

@sumit.nathany: If you are in the same situation (locked bootloader, no OS, no recovery) you'll need to contact Motorola. But it won't hurt to try unlocking the bootloader before you do.
The only other option requires hardware hacking, and both the tools and methods can't be discussed here (against XDA rules).

Not that I know much about this, but what about the fastboot boot recovery.img command? If used with a Google recovery image, it might get around the bootloader lock?

Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.

Strephon Alkhalikoi said:
Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.
Click to expand...
Click to collapse
Making it work, but only with an original recovery from Google, would not open any opportunities.
BTW, do you, or anyone else have any theories why this happens? Hardware error?

It probably could be made to work, but then you'd run into an issue of people spoofing the stock recovery, which would still open up the whole can of worms. Better to simply block the ability completely unless the bootloader is unlocked.
As to how this happened I will not speculate. Reason being that any speculation would be useless without seeing the devices firsthand and examining them. Not to mention the people that would be throwing hissy fits thinking I accused them of something. All that really matters here is that a device in this state is not something that can be fixed without a trip to the repair center.

fix it
truwrxtacy said:
Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks
Click to expand...
Click to collapse
I found a solution for this problem i know is late in the game but better late than never jijiji

Did you try unlocking the device with?
Code:
fastboot oem unlock

Zombie

Rezz577 said:
fix it
I found a solution for this problem i know is late in the game but better late than never jijiji
Click to expand...
Click to collapse
Hi sir.
Can you tell me the solution, please?
I am in yhe same situation, no recovery and bootloader locked, and bootloop
i wait for your answer