Big problem. My Sensation XL run only fastboot. - HTC Sensation XL

I get these phone. But across the entire display advertising, as if it was just a show piece. I need change ROM. I had hboot 1.16. But If i change hboot to 1.28 system freeze on HTC logo on white background. I try instal recovery, but recovery was freezing if i get this phone. Now if I try instal other hboot with use fastboot, program say: SENDING hboot OKEY ..... WRITING hboot FAILED <remote: not allowed>. if i try erase all data using fastboot i get FAILED <remote: not allowed>. I do not know why I'm still writes. Help me please. Thanks
Edit: I love the guy who programmed the RUU ROMs installers. This help me. We can lock or delete this post.

Related

[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

[Q] sos

I have htc one hbott m7 r.4radio 1.54 s-o os 3259.14 2.2247514
I'm desperate to erase everything was black screen with htc letters if I leave here always gets in bootlader give i factory reset no nothing
teneia else to root it before I put it to relocked am trying to install ruu but no way I try install fasboot cmd but nothing much help please thanks

Solution to RUU: Code 152 !!!

Hey everyone,
so i tried to run a RUU for GingerBread on my incredible s and forgot to do "fastboot oem lock"
i ran the ruu and it told me error code 155 and i facepalmed myself -.-
and now i seem to be inable to access recovery NOR bootloader...
i cant even start my Phone up
the only thing it shows is a black screen with hTC on it and in the 4 corners a white triangle with "!" in it...
Can someone help me with reverting back to STOCK GB rom without root etc. s-on etc.
because i want to sell this Phone (no i dont :/) to buy a hTC One X+ and i need the stock stuff for that
NOTE: i *had* BlackRose s-off
Another note: computer recognises my Phone in fastboot mode so i can use fastboot commands but not adb
EDIT: now i get code 152 image update error...
EDIT2: I am able to get into bootloader... only thing it shows is:
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
and some date...
RUU (in orange)
Parsing . . . [downloaded ZIP]
[1] BOOTLOADER -Bypassed
[2] BOOT -OK
[3] RECOVERY -OK
[4] SYSTEM -OK
[5] SPLASH1 -OK
[6] USERDATA -OK
[7] TP -Bypassed
[8] TP -Bypassed
[9] TP -OK
[10] RADIO_V2 -Fail-UZ
[11] RADIO_CUST -OK
Image unzipping fail!
Update fail!
HELP PLEASE
SOLUTION: Delete the RUU, Download it again, and try again, if still nothing, try again, and still nothing, leave a comment!!!
Thanks if i helped u!!!
oziboy said:
Hey everyone,
so i tried to run a RUU for GingerBread on my incredible s and forgot to do "fastboot oem lock"
i ran the ruu and it told me error code 155 and i facepalmed myself -.-
and now i seem to be inable to access recovery NOR bootloader...
i cant even start my Phone up
the only thing it shows is a black screen with hTC on it and in the 4 corners a white triangle with "!" in it...
Can someone help me with reverting back to STOCK GB rom without root etc. s-on etc.
because i want to sell this Phone (no i dont :/) to buy a hTC One X+ and i need the stock stuff for that
NOTE: i *had* BlackRose s-off
Another note: computer recognises my Phone in fastboot mode so i can use fastboot commands but not adb
EDIT: now i get code 152 image update error...
EDIT2: I am able to get into bootloader... only thing it shows is:
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
and some date...
RUU (in orange)
Parsing . . . [downloaded ZIP]
[1] BOOTLOADER -Bypassed
[2] BOOT -OK
[3] RECOVERY -OK
[4] SYSTEM -OK
[5] SPLASH1 -OK
[6] USERDATA -OK
[7] TP -Bypassed
[8] TP -Bypassed
[9] TP -OK
[10] RADIO_V2 -Fail-UZ
[11] RADIO_CUST -OK
Image unzipping fail!
Update fail!
HELP PLEASE
Click to expand...
Click to collapse
Run Blackrose Tool and there is an option for uninstalling Blackrose HBOOT. That will give you Stock HBOOT 1.13.0000 and then run latest RUU.
072665995 said:
Run Blackrose Tool and there is an option for uninstalling Blackrose HBOOT. That will give you Stock HBOOT 1.13.0000 and then run latest RUU.
Click to expand...
Click to collapse
Thanks for yor quick reply, i cant boot into my phoneo enable debugging thus i got no adb
andthe tool is stuck at "waiting for device" :/ it has to be with fastboot :/
oziboy said:
Thanks for yor quick reply, i cant boot into my phoneo enable debugging thus i got no adb
andthe tool is stuck at "waiting for device" :/ it has to be with fastboot :/
Click to expand...
Click to collapse
What does it say when you enter recovery?
072665995 said:
What does it say when you enter recovery?
Click to expand...
Click to collapse
Can't enter bootloader,boot up device and i get a black screen with silver HTC in it with some triangle with ! in it
so cant enter recovery to tell ya ://
I tried some ways to get back to s-on but without success :/
oziboy said:
Can't enter bootloader,boot up device and i get a black screen with silver HTC in it with some triangle with ! in it
so cant enter recovery to tell ya ://
I tried some ways to get back to s-on but without success :/
Click to expand...
Click to collapse
So how do fastboot commands work? You have to be in bootloader to access fastboot....
Are you pressing volume down and power?
072665995 said:
So how do fastboot commands work? You have to be in bootloader to access fastboot....
Are you pressing volume down and power?
Click to expand...
Click to collapse
Yeah i know is kinda weird how i get to fastboot, idk neither
i just press power button and my pc recognises my Phone in fastboot state
and i am able to use *almost* all fastboot commands such as fastboot flash blahblah and fastboot reboot-bootloader and blahblah
if i start up, again, i still get a black screen with silver HTC letters on it
after hitting power button NO SINGLE button is being recognised by the Phone itself
oziboy said:
Yeah i know is kinda weird how i get to fastboot, idk neither
i just press power button and my pc recognises my Phone in fastboot state
and i am able to use *almost* all fastboot commands such as fastboot flash blahblah and fastboot reboot-bootloader and blahblah
if i start up, again, i still get a black screen with silver HTC letters on it
after hitting power button NO SINGLE button is being recognised by the Phone itself
Click to expand...
Click to collapse
when you try fastboot reboot bootloader, that still lands you to nothing?
072665995 said:
when you try fastboot reboot bootloader, that still lands you to nothing?
Click to expand...
Click to collapse
Yes i tried that already
But the worst thing is that i can run the RUU but i keep on getting error 152 system image thingy if thats fixed then i guess this whole thingy here will be installed
only thing i need is to RELOCK my bootloader but i cant use fastboot oem lock, the argument "lock" isnt recognised
Guys please help :crying:
I need to sell this Phone
EDIT: see this
c:\ADB>fastboot oem lock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
and this
c:\ADB>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.686s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.125s]
finished. total time: 0.811s
EDIT2: oh and on my Phone screen when i plug it out it shows on bootloader: "Can not roll back hboot"
I guess my Phone is stuck in RUU mode? (when it was flashing the stuff)
Is it possible that some of the files in my RUU were corrupt?
I downloaded the RUU with some "pauses" and "resumes"
imma redownload the RUU now... hope it works :/
p.s. my hboot id 2.03.blahblah... shouldnt it be 6.blahblah for BlackRose?
so blackrose is uninstalled?!
oziboy said:
Guys please help :crying:
I need to sell this Phone
EDIT: see this
c:\ADB>fastboot oem lock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
and this
c:\ADB>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.686s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.125s]
finished. total time: 0.811s
EDIT2: oh and on my Phone screen when i plug it out it shows on bootloader: "Can not roll back hboot"
I guess my Phone is stuck in RUU mode? (when it was flashing the stuff)
Is it possible that some of the files in my RUU were corrupt?
I downloaded the RUU with some "pauses" and "resumes"
imma redownload the RUU now... hope it works :/
p.s. my hboot id 2.03.blahblah... shouldnt it be 6.blahblah for BlackRose?
so blackrose is uninstalled?!
Click to expand...
Click to collapse
with Blackrose, my bootloader 2.03
DuffyBank said:
with Blackrose, my bootloader 2.03
Click to expand...
Click to collapse
Uhm... how do you mean?
oziboy said:
Uhm... how do you mean?
Click to expand...
Click to collapse
sorry, meant hboot 2.03
Hey i still didn't give up and im still awaiting help meanwhile sitting the whole day on the pc to search for any solutions :/
guys please help me out of this it has been 3 days and im TIRED of it
i have to do it with a nokia now (
Any link to a froyo or ICS RUU is appreciated too :d
oziboy said:
Hey i still didn't give up and im still awaiting help meanwhile sitting the whole day on the pc to search for any solutions :/
guys please help me out of this it has been 3 days and im TIRED of it
i have to do it with a nokia now (
Any link to a froyo or ICS RUU is appreciated too :d
Click to expand...
Click to collapse
Can you please say what it says in your bootloader now?
In all honesty, if you can't access the bootloader, you're pretty much f**ked :/
Your last hope is recovery and trying blackrose tool there
072665995 said:
Can you please say what it says in your bootloader now?
In all honesty, if you can't access the bootloader, you're pretty much f**ked :/
Your last hope is recovery and trying blackrose tool there
Click to expand...
Click to collapse
Well, that was definately a way to put it xD
But yes. If you can't access bootloader, you may have problems.
Sent from my Nexus 5
oh well, F*** then cuz i cant Access bootloader properly to choose recovery from it
i m going to try few more things,
1. do it via sdcard and fllash it
2. remove radio.img from the OTA and flash it since it gives an error
i can Access bootloader but when i do that, my bootloader shows me
***BlackRose***
some information...
and then it shows in orange "RUU"
i cant Access anthing from it and when i plug charger back in it goes into RUU mode
i know what my problem is, but i cant find any solutions, "fastboot oem lock" is an unrecognised command... does it have to do with something about htcdev.com?
OMG TY FOR ALL UR HELP GUYS my phones fixed and is on GB 2.3.3 now ummm
my RUU was just corrupt -_- i ran a new one NOW I HAVE STOCK, ty all so much
THE VIVO IS BACK ALIIIIVE
oziboy said:
OMG TY FOR ALL UR HELP GUYS my phones fixed and is on GB 2.3.3 now ummm
my RUU was just corrupt -_- i ran a new one NOW I HAVE STOCK, ty all so much
THE VIVO IS BACK ALIIIIVE
Click to expand...
Click to collapse
nvm wat we said about u being fked
Sent from my Nexus 5
LamboBull said:
nvm wat we said about u being fked
Sent from my Nexus 5
Click to expand...
Click to collapse
lol xD
To the users keep on having code 152, please delete the RUU and download it again!!!
since thats how i fixed it xD :highfive:

[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

Categories

Resources