How to fix Bootloader? - Hero CDMA Android Development

so after flashing the leaked RUU and then movinf on to other ROMs.. i can not longer flas the leaked RUU or the 1.5 ( factory ) RUU ..tells me Bootloade incorrect...
How do i fix this ?

rgildoss said:
so after flashing the leaked RUU and then movinf on to other ROMs.. i can not longer flas the leaked RUU or the 1.5 ( factory ) RUU ..tells me Bootloade incorrect...
How do i fix this ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=657086
Worked great for me.

danknee said:
http://forum.xda-developers.com/showthread.php?t=657086
Worked great for me.
Click to expand...
Click to collapse
that the correct link bud?
my phone is rooted,, i just cant load the factory ruu anymore ...tells me bootloader is incorrect

the link he sent you effectively does the RUU, without changing the bootloader. there's multiple parts to the phone, the actual ROM, radio, bootloader, recovery image, and other stuff i can't remember on top of my head.
the RUU tries to erase and replace everything, including the bootloader. but bootloaders don't downgrade, so doing the 2.1 RUU will make the bootloader update to that one. youc an't downgrade the bootloader.
but to the best of my knowledge, you can upgrade/downgrade everything else. that's what the link does if you follow the directions, minus the radio(that's up to you)

justinisyoung said:
the link he sent you effectively does the RUU, without changing the bootloader. there's multiple parts to the phone, the actual ROM, radio, bootloader, recovery image, and other stuff i can't remember on top of my head.
the RUU tries to erase and replace everything, including the bootloader. but bootloaders don't downgrade, so doing the 2.1 RUU will make the bootloader update to that one. youc an't downgrade the bootloader.
but to the best of my knowledge, you can upgrade/downgrade everything else. that's what the link does if you follow the directions, minus the radio(that's up to you)
Click to expand...
Click to collapse
hmm thanks for the info ..
so if i read it right the bootloader will stay were it its ? so if i send the phone back will they not know if the bootloader is diffrent then the one that comes with factory RUU?
i think i maybe totaly lost here

rgildoss said:
hmm thanks for the info ..
so if i read it right the bootloader will stay were it its ? so if i send the phone back will they not know if the bootloader is diffrent then the one that comes with factory RUU?
i think i maybe totaly lost here
Click to expand...
Click to collapse
I was in the same boat as you and used the tools in the thread posted above. I was able to restore to the OTA 1.56 build and unroot with no custom recovery. I am fairly positive my bootloader looks the same as it did when I got the phone (white with green text). If this is still the new boot loader they would have to check the version number to know it was different (yeah right).
Otherwise you are going to have to send your phone in with a 2.1 ROM and custom Recovery... Which is definitely noticeable.
*edit* Confirmed that it does NOT restore Hboot. My Hboot is version 1.47.0000, but it is the white with green text (looks identical besides the number). The original Hboot was 1.41.0000. Not sure if there is anyway to get that back...maybe after the official 2.1 ruu comes out?

http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
That is the one I used, I was good to go in about 5 mins!

Roman G said:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
That is the one I used, I was good to go in about 5 mins!
Click to expand...
Click to collapse
i hate to say anything wrong about gbhil, but i'm 99.999999% sure that he used the term 'bootloader' incorrectly, or purposefully in able to make it easier for newcomers to read.
the bootloader that the OP was referring to is the actual BOOTLOADER of the phone, as in turn off your phone, and hold VOLUME DOWN + POWER to get into there. you'll get to a white screen with skating androids on the bottom and some blocky test that says HBOOT ######## and stuffl ike that.
the bootloader that gbhil referenced in his post was the recovery image, which is home+power when the phone is off, or what you use to flash new ROMs, Radios, fixes, etc.
recovery image != bootloader

anyone got a chance to downgrade the bootloader yet?

Related

Anyone notice the MT4GS Bootloader Unlockable?

http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
nice find, it'll make for a nice xmas gift for people with the latest ota
doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
did you have S-ON or S-OFF at the time?
jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
And are you using the latest update or the previous stock ROM?...
beezie916 said:
http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....
Click to expand...
Click to collapse
Yeah I noticed earlier
http://phandroid.com/2011/12/26/htc...-4g-slide-now-officially-unlockable-from-htc/
jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
beezie916 said:
And are you using the latest update or the previous stock ROM?...
Click to expand...
Click to collapse
I was using my 2nd MT4GS which I had done nothing with since I got that one. It is fresh from the box and had the new OTA update on it (I updated it myself like an hour before I tried this). I no better then to use the MT4GS that I currently use as my everyday device which does have S-Off.
And now HTC knows which phones to not honor warranty claims from.
Sent via smoke signal.
doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?
jonnycat26 said:
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?
Click to expand...
Click to collapse
Can you confirm your current bootloader version?
Sent from my NRGZ'D Sensation 4G!
jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
i am getting the same result, the unlock screen does not show up on the phone. i am on the new locked HBOOT, but i have S-OFF from before....
akapaul26 said:
can you confirm your current bootloader version?
Sent from my nrgz'd sensation 4g!
Click to expand...
Click to collapse
hboot 1-45.0013
doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
I am having same results with hboot 1-45.0013 S-on stock. Hopefully revolutionary gets a hold of this soon!
akapaul26 said:
I am having same results with hboot 1-45.0013 S-on stock.
Click to expand...
Click to collapse
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....
jonnycat26 said:
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....
Click to expand...
Click to collapse
I know, but everything works till that point?......
akapaul26 said:
I know, but everything works till that point?......
Click to expand...
Click to collapse
I'm not sure, but I think the tool would work on any HTC phone, but the token would only be accepted if the HBOOT on the phone worked with it.
Just a guess tho...
perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...
yogi2010 said:
perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...
Click to expand...
Click to collapse
I've sent an email to the support link that's listed in the email with the unlock file. Or at least, I think I have, they don't actually confirm that you've sent a message when you hit send.
If I get any response from them, I'll share it here.
My experience with the new OTA
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Jaytex24 said:
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Click to expand...
Click to collapse
If Revolutionary worked the way it was supposed to, it wouldn't be locked.

Red ! when I tried to flash a custom rom, now I am stuck...

So a few days ago I rushed into using htcdev to unlock my bootloader without fully researching. I then tried to flash: aospX 1.0.0-MR1 in haste. I couldn't use cwm or ext4 because it stated the phone was not rooted. I assumed since I unlocked the bootloader using htcdev that I wouldn't need either for some reason. I tried flashing the rom using the directions found in glevitan's newbie guide: http://dl.dropbox.com/u/30674730/ULTIMATE ACE GUIDE V5.pdf. In the directions that were given on step 5 I just booted in hboot instead of cwm or ext4. So basically what I did is go into hboot and fastboot and tried flashing the boot img.
After that it seemed as though it was flashing but then it went to a picture of a phone with a red exclamation point next to it. Now in the past two days I have been researching how the fix my problem from acting hastily without researching first. None of my research or actions thus far have been able to get me past hboot. I have tried the directions in the following thread and have not been able to fix the issue: http://forum.xda-developers.com/showthread.php?t=1396229
When I try to reinstall recovery by the directions given in that thread nothing really happens and it just goes back to hboot. When I try flashing the Inspire 4g stock rom in the thread I get error messages in hboot that say invalid image! and it will flash to the white HTC splash screen for a few seconds and then vibrate and go black then back to htc splash screen for a few seconds then back to the picture of a cell phone with a red exclamation point next to it.
The only semi-success I have it trying to flash a RUU (RUU_Ace_Gingerbread_S_Cingular_US_2.47.502.7_Radio_12.56.60.25_26.10.04.03_M_release_200368_signed.exe)
But when I try to install the RUU it will install for a few minutes but then I get an error message because it is an older version than I have and wont allow me to "downgrade" because I am currently on 3.20
Any help to try to get this phone back up?
Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.
Teichopsia said:
Best guess is (and double check first) relock the bootloader and flash the ruu.
Sent from a dream.
Click to expand...
Click to collapse
First thing, thanks for the response.
It wont let me flash the RUU, I have version 3.20.xxxx and the only ruu I can find is older versions and it wont allow me to flash an older version. The bootloader is already relocked btw.
I'll get back to you. I have to finish doing a few things that will take me a few hours or maybe more, then I'll see what I can find.
Sent from a dream.
You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.
marsdta said:
You have a few options. The exclamation point is because you don't have a custom recovery installed. You have to flash it manually ie fast boot flash recovery recovery.img my guide doesn't cover that as it was written before HTC dev method was available. And those in the inspire land were recommended from flashing the eng hboot.
So anyways. You can flash cwr via fast boot,then attempt to flash aospx. BUT I suggest you actually gain soff.
The 3.20 ruu is available straight from HTC website.
Click to expand...
Click to collapse
Wow can't believe I didn't check there...
Thanks, running the 3.20 ruu at least got me up and running.
Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates
marsdta said:
Now that your up and running and want to root you should read this.
http://forum.xda-developers.com/showthread.php?t=1839855
As the process is a little different now. Should also check out attn1 site for the kit for any updates
Click to expand...
Click to collapse
Thanks that fixed me up. Now rooted and getting ready to flash aospx
EDIT: Got AOSPX running smooth, thanks again!!

[Q] Relock, RUU, Start Over?

Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol

Bell/Virgin HTC Sensation Boot-loop

Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it
Tom-5- said:
Hello, I know this may seem like a redundant post but I cannot for the life of me figure out how to un-brick this phone..
Currently the only menu I can get into is the Hboot menu, where it says
RELOCKED
HBoot-1.27.0000
RADIO-11.24.3504.10_M
eMMc-boot
This phone has never been rooted or modified in anyway and just started this bootloop, where I've tried unlocking the bootloader, flashing different recovery's and many RUU files and nothing has worked..
When trying to enter the recovery menu from the HBoot menu it the phone simply resets itself and back to the dreaded HTC bootloop..
The phone is currently on 3.32.666.13 I believe and there is no RUU that I can use to reflash it because the latest RUU for Bell Sensations is
1.45.666.5 and it errors out saying it's the incorrect version.
I've went through many tutorials and searched through many posts trying to get s-off but there is no method that will work because I cannot get into the recovery or the android os or perform a factory reset even..
If anybody has any ideas or can shine some light onto this problem I'd greatly appreciate it
Click to expand...
Click to collapse
Hi,
To get into stock recovery,hold volume up and down + power button.
malybru said:
Hi,
To get into stock recovery,hold volume up and down + power button.
Click to expand...
Click to collapse
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet
Tom-5- said:
Hi there, thanks for the suggestion but instead of loading the recovery it just boots to the white htc screen, goes black for about second and reboots.. no matter how long or which button combination I use, besides to get into the Hboot Menu, I haven't seen any recovery menu yet
Click to expand...
Click to collapse
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium
ganeshp said:
Can you check the cid?
If it's super CID then change it back to original one and then do a reboot and see
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?
Tom-5- said:
Hello, Unfortunately the CID hasn't been changed, it's currently BM___001
Is there any RUU's available for this model equal to 3.32.666.13 or higher?
Click to expand...
Click to collapse
Hi,
Look HERE or HERE
malybru said:
Hi,
Look HERE or HERE
Click to expand...
Click to collapse
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)
Tom-5- said:
Hello, thanks for the links.
I've tried both the BM RUU's and some of the HTC Europe ones as their firmware versions are higher, but they error out with
<T192024><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
or
<T003702><DEBUG><OUT>FAILED (remote: 41 model id check fail)</OUT>
(From RUU Logs)
it was my understanding I need one with 3.32.666.13 or higher retaining the same '666' region type code and a higher or equal firmware to the one already installed, as far as I'm aware no such RUU exists
I've tried taking the rom from either RUU's and flashing the zip manually with fastboot with either a locked or unlocked bootloader using commands like "fastboot -s SH16LV603891 flash zip C:\rom.zip" and it either says something like "remote:signature fail" or "Remote:not allowed" (with unlocked bootloader)
Click to expand...
Click to collapse
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.
malybru said:
Hi,
Relock the bootloader
Code:
fastboot oem lock
Then,try the RUU again.
Click to expand...
Click to collapse
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands
Tom-5- said:
Unfortunately no matter which RUU I use or whether the bootloader is locked or unlocked it errors out before it can finish
I appreciate the help though
Is is possible to get supercid without booting into the android operating system or recovery menu? so I could at least flash a custom rom or not be limited with my fastboot commands
Click to expand...
Click to collapse
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.
malybru said:
Hi,
I do not think you can supercid with s-on.
But you can try to follow THIS GUIDE to install a custom ROM.
Click to expand...
Click to collapse
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots
Tom-5- said:
I was able to flash the recovery, but when attempting to boot into the recovery it instantly brings up the white HTC logo on the screen, and stays there until the phone eventually reboots
Click to expand...
Click to collapse
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.
malybru said:
Hi,
I am running out of things to suggest.
The best thing would obviously be a RUU to reset everything.
Maybe try to re-install the recovery.
Click to expand...
Click to collapse
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way
Tom-5- said:
It's got me stumped too! I've tried multiple recoveries.. I wonder if it's possible that it could be a hardware-related problem? As I should be able to enter the recovery at this point I think, unless I'm missing something? Would any RUU that is over higher than the current firmware be suitable? for example it currently sits at 3.32.666.13, say I were to use "RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed" The firmware is higher but the region code doesn't match up. If I were to use "RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed" the firmware version is too low, but the region matches up. I figured if I used just an unbranded stock rom.zip based off of 3.32 or 3.33 and flashed it via fastboot with an unlocked/locked bootloader I may have some luck but it was a no-dice situation..
The model of this sensation is a PG58110 with a manufacture date of 2011/06/17
Could these possibly be the wrong RUU's ? I tried ones for the Sensation 4G and regular Sensation
as I wasn't positive which one I have.. No luck either way
Click to expand...
Click to collapse
Hi,
Did you fully read THIS LINK that I gave you?
It shows various alternatives to just running a RUU.
It helps you to determine which of the 3 types of Sensation you have.
Try running all the RUU's that are even reasonably close to your version.
It will only throw up an error if it is no good.
Remember that the phone should be locked or relocked.

[Q] Help with Sense 6.0 Update

Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
Thanks in advance!
P.S. Sorry if I haven't posted any helpful information, I don't know what to post So tell me if you need to know anything, I'll share it right away
Peshyy said:
Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
)
Click to expand...
Click to collapse
just flash stock recovery instead of custom TWRP
iourikil said:
just flash stock recovery instead of custom TWRP
Click to expand...
Click to collapse
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Edit:
I've flashed the 1.31.401.1 and it worked! Currently installing the update ;3
Peshyy said:
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Click to expand...
Click to collapse
use recovery.img from this
firmware m4 OTA 3.10.401.4
https://mega.co.nz/#!eBIRwYIR!vGks0Gloq7VpgAD5POrlbBh1HWPfpRIFAxpMahG7Nk4
iourikil said:
use recovery.img from this
firmware m4 OTA 3.10.401.4
URL HIDDEN
Click to expand...
Click to collapse
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Peshyy said:
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Click to expand...
Click to collapse
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
iourikil said:
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I get the same error... the Phone with a red exclamation mark with a triangle around it.. Is it because I'm rooted. I just searched and it might be it..
Should I follow the guide on theunlockr.com / 2014 / 03 / 18 / unroot-htc-one-mini /
So.. Should I only lock the bootloader or completely unroot it?
I'll try with only locking the bootloader in a sec..
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Peshyy said:
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Click to expand...
Click to collapse
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (hboot 2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
jollywhitefoot said:
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
Click to expand...
Click to collapse
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Peshyy said:
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Click to expand...
Click to collapse
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
jollywhitefoot said:
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
Click to expand...
Click to collapse
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Peshyy said:
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Click to expand...
Click to collapse
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
jollywhitefoot said:
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
Click to expand...
Click to collapse
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Peshyy said:
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Click to expand...
Click to collapse
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
jollywhitefoot said:
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
Click to expand...
Click to collapse
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Peshyy said:
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Click to expand...
Click to collapse
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
jollywhitefoot said:
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
Click to expand...
Click to collapse
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Peshyy said:
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Click to expand...
Click to collapse
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
jollywhitefoot said:
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
Click to expand...
Click to collapse
It's Tampered and Unlocked. I totally formatted everything, put CWM and using stock software.. It's the Sense 5.5 with Android 4.4.2. ClockworkMod Recovery Touch 6.0.3.6

Categories

Resources