Related
I flashed a RUU and it worked, i then wrote s-on via adb and it now only boots into hboot, says-s-on but i cant do any functions,, at the top it says locked and security warning. I tried running the RUU file again but it just didnt work, says it cant upgrade the adndroid version. Please help, im desperate. On the RUU, it says ERROR 132. It stops after the updating signature procedure.
sensation lover said:
I flashed a RUU and it worked, i then wrote s-on via adb and it now only boots into hboot, says-s-on but i cant do any functions,, at the top it says locked and security warning. I tried running the RUU file again but it just didnt work, says it cant upgrade the adndroid version. Please help, im desperate.
Click to expand...
Click to collapse
By RUU I presume you mean you went back to stock? Did you boot and test this before going S-ON?
Yes it was fully working but then i wrote the s-on and my RUU file doesnt work anymore
sensation lover said:
Yes it was fully working but then i wrote the s-on and my RUU file doesnt work anymore
Click to expand...
Click to collapse
Please confirm when you say RUU, this is an executable file from the manufacturer or your carrier? This should work when you are S-ON but if you are trying to flash a custom ROM from recovery, then this definitely won't work.
Its an exe RUU for HTC Europe, sensation ics stock. It worked perfectly fine but then i put s-on....and presto. I got it from the thread on xda, quite a large and famous one.
Did you want to be S-ON for a reason? The only thing I can really suggest is to go S-OFF and start again.
How can i get to s-off if the phone wont fully connect to the coimputer because it's stuck at hboot? The s-off revolutionary toll just cant pick it up. I can get it in adb so to speak, i went of the image calculoate option at hboot and then adb picks it up if i do fastboot devices but then no other command works.
sensation lover said:
How can i get to s-off if the phone wont fully connect to the coimputer because it's stuck at hboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192300
Can you get into recovery? A trick I found can work is to open up a command prompt on the PC, type 'adb reboot recovery'. If you get "error: no device found", then hit the up arrow and enter to run the command again. At some point the command will work and you get no response instead of the error, then it should boot into recovery.
Read the follwoing two threads . They may help you.
http://forum.xda-developers.com/showthread.php?t=1469296
http://forum.xda-developers.com/showthread.php?t=1478828
nope, i think that because its locked it wont connect, i tried that code like 100 times.
it says i need the htc dev to unlock it but i cant find it on that thread, can sum1 please get me a link? (from tehe top link of the guy who posted two links)
sensation lover said:
it says i need the htc dev to unlock it but i cant find it on that thread, can sum1 please get me a link? (from tehe top link of the guy who posted two links)
Click to expand...
Click to collapse
This?
sensation lover said:
it says i need the htc dev to unlock it but i cant find it on that thread, can sum1 please get me a link? (from tehe top link of the guy who posted two links)
Click to expand...
Click to collapse
Here it is ...
wmoore said:
This?
Click to expand...
Click to collapse
Be aware that this can void your warranty.
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
you are lucky to have white screen
You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium
xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.
vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...
xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.
can anyone please help
Where can I get stock recovery, stock boot for the phone?
First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^
thanks for the reply, however ur link is broken.
And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??
Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though
xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up
I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app
Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.
hi all,
i HAD a sensation running Android Revolution HD 6.8.0. and without checking properly, i installed AOKP-42-20130118.zip and gapps-jb-20121212-signed.zip. the phone won't boot or charge. i then realised this is not a sensation rom, it's a HTC ONE rom, i think!! . i've followed the HTC Unbricking Project and get "device not found...check connections" in ubuntu. phone shows up on windows as other device labeled QHSUSB_DLOAD. is my phone toast? sorry if all this sounds amateurish as im completely new to all this. thanks all.
thats some dangerous thing happened there ..if HTC UNBRICKING not doing any help ..then service center only
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Alsager said:
Try flashing the official RUU suitable to your device. It may recover your device
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
cant seem to connect to device to flash anything. not looking good. any ideas?
Only service center :/
miticogirl said:
Only service center :/
Click to expand...
Click to collapse
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
bensod said:
thanks all for your help. it seems i live in a country where nobody can fix my phone. i've called nearly every service center in New Zealand. it may be my only option to send this phone to my brother in the USA and get it fixed there. can anyone recommend a repair center anywhere that can fix this? Thanks again.
Click to expand...
Click to collapse
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Alsager said:
have you:
1. installed the HTC drivers
2. put the device in "bootloader mode" when trying to flash the RUU,
3.uninstalled the HTC sync program,
4. used the original USB cable
sorry for very late response.
Click to expand...
Click to collapse
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
bensod said:
no worries, thanks for answering.
yes tried all of the above, several times. tried newest drivers, and 3.0.0.007, messed around with several usb cables, changed computers. device not found error every time. i think the phone is stuffed. will send it to mobiletechvideos in Texas. it's a 50 dollar repair. will be a bit more careful next time.
Click to expand...
Click to collapse
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
no, can not boot phone. phone is dead boot bricked.
found a place to fix it but it's not cheap. thanks all for your help.
ganeshp said:
What?
You can boot the phone up to boot loader?
Then did you try flashing a ruu?
Can you post the boot loader details?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
bensod said:
hi, my phone has been recovered and back working. service centre returned the phone with locked bootloader, s-off and hboot 1.29.
i'd like to get back to Android Revolution HD 6.8.0, can i just root and flash a recovery, or have i to unlock the bootloader again on htv dev? can i use the backups i made earlier on hboot 1.27?
thanks again.
Click to expand...
Click to collapse
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
ganeshp said:
you received the phone with LOCKED bootloader and SOFF ?
then before doing anything ..i would suggest you to ..check whether the phone is soff or not (I've seen 3 cases at-least where the phone showed soff (after the phone got back from service center) but its not actually soff and people bricked their phone again trying to flash stuff) ... to check soff status go to my soff guide (link in my signature)..try the controlbear soff NO HTC_DEV unlock one ..if the phone is properly soff then the controlbear says soff and exits ..otherwise your phone is not soff ..
also you cant do HTC-DEV unlock (motherboard got replaced so IMEI changed) as IMEI changed and the unlock procedure fails ..the only way is JB SOFF
Click to expand...
Click to collapse
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
bensod said:
hi again, thanks for the heads up. i've run controlbear and confirmed the phone is s-off. during the process it asked to install modified juopunutbear hboot, which i said no. should i have? also phone imei is same as before (no motherboard replacement) so whats my next move, i'm a little cautious as I've bricked phone already once!! thanks ganeshp.
Click to expand...
Click to collapse
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
ganeshp said:
yes install juopunutbear hboot via controlbear and if that didnt went successfully ..install patched revoultionary hboot (at the end of first post i think) from kohr-ah firmware thread present in sensation development section.
then you cna continue with custom recovery flashing and then custom rom (if you want you can backup your current stock rom too from the custom recovery before trying the new rom )
Click to expand...
Click to collapse
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
bensod said:
hey thanks for all your help. i'm back to where i was before all the drama. one last thing, is there a rom out there that's pure android? no sense? one you would recommend? thanks again for your help.
Click to expand...
Click to collapse
cm 10.1 of albioman ?
the latest one is pretty stable
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1..0.45.0622
emmc-boot
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001
I've got HBOOT 1.27.0000 so I had no choice but to use the ControlBear method.
The virtual Machine doesn't work on my computer, so I was forced to search for the windows files.
I couldn't find any for the HTC Sensation, but I found one for the Evo 3d.(I have less than 10 posts, so I can't give you guys the link.)
So you can guess what I did. I downloaded the linux files for my HTC Sensation from unlimited.IO site.
And I also downloaded the files for the Evo3D.
Then I extracted both of them.
I replaced the jb_boot.img file and ControlBear.exe. (Not jb_boot.zip) Without the jb_boot.img ControlBear gives an error.
After that I conected my phone, ran ControlBear.exe.
It found my device and did its job(not really), and my phone had to restart. But it keeps on restarting.
All what ControlBear says is trying to reconnect to my phone.
I didn't come to the point where I have to do the "Wire-Trick". The ControlBear logo didn't even show up on my HTC.
I still can launch the menu when I hold the Volume Down+ Power button.
It's not S-Off though, but that was to be expected.
Additional Information:
My HTC Sensation is S-On.
Usb Debugging settings is enabled.
I used the temp-root.batch (it worked)
I did the bootloader thing.
I already turned once my HTC Sensation S-Off, but then with the revolutionary tool.
I had to turn S-On because of the warranty (that also worked).
Sorry for this mistake guys, I know it's stupid.
I'd greatly appreciate it if you help me.
Thank you for your time.
EDIT:
I've fixed it now!
I want to thank you all for your help and contribution, each one of you!
After 4 days i can fineally enjoy my HTC Sensation.
you need to ruu your phone
paxtoncamaro91 said:
you need to ruu your phone
Click to expand...
Click to collapse
Yes I guess RUU needs to be done
Wich RUU would you suggest?
The stock one?
I think I already have the stock RUU.
My CID is VODAPE17, and my MID is PG5813000.
version-main: 3.32.162.52
find the 3.32.162.52 RUU and flash it. Then attempt again using the linux version from the official site. The windows version was taken down for a reason
A little off topic; but why was the windows one taken down?
Worked perfectly for me. :/
Btw I do have windows one (Beta 0.6) for Sensation if OP still needs it.. I can PM..
dexter93 said:
find the 3.32.162.52 RUU and flash it. Then attempt again using the linux version from the official site. The windows version was taken down for a reason
Click to expand...
Click to collapse
I can't find that one.
Is this one fine too? RUU Pyramid Vodafone DE 1.27.162.1.zip
I have to download it from Rapidshare, and it takes... 1 day...
or this one: RUU_PYRAMID_ICS_Vodafone_DE_3.32.162.11_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251539_signed.exe
Or this one:
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
Though my HTC isn't Pyramid ISC?
EDIT:
When I try to install the RUU_PYRAMID_ICS_Vodafone_DE_3.32.162.11_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251539_signed.
it says that the utility can't update the android phone. Get the right RUU and try again?
RUU_Pyramid_Vodafone_FR_1.27.163.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_191976_signed and RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed don't work either...
Why is HTC doing this...
It still isn't working...
Ouch, i just used the KGS utility tool to do this on hboot 1.29, worked on first try...
pyramid==htc sensation, ICS==ice cream sandwich (android 4.xx) which by your firmware, you're probably on
stillsober said:
Ouch, i just used the KGS utility tool to do this on hboot 1.29, worked on first try...
pyramid==htc sensation, ICS==ice cream sandwich (android 4.xx) which by your firmware, you're probably on
Click to expand...
Click to collapse
ah okey, thanks for the information.
I have hboot 1.27 though.
And it still isn't working...
Pm me for controlbear
I have the correct control bear for the sensation for windows, pm me and i will send the file to you.
Well I've fixed the RUU problem, by relocking my HTC again.
I had to type fastboot oem lock.
So i've installed this RUU:
RUU_PYRAMID_ICS_Vodafone_DE_3.32.162.11_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_251539_signed
Click to expand...
Click to collapse
My HTC booted nice and worked again.
I've UNLOCKED my HTC with the Unlock_Code.bin from HTCdev(my own code)>
I've used temp-root, and ran ControlBear.exe ( THIS time I got the right one, from a known contributor on this forum)
It made a back-up etc.
But here's the problem again..
After it found his fourth bear my HTC restarted.
After that, it is stuck in a boot loop again...
I've unplugged my phone and plugged back it, but it's still in a boot loop.
I've relocked my HTC, and I'm installing the RUU again..
Any help guys?
I'm kinda getting desperate...
Arslan17 said:
Well I've fixed the RUU problem, by relocking my HTC again.
I had to type fastboot oem lock.
So i've installed this RUU:
My HTC booted nice and worked again.
I've UNLOCKED my HTC with the Unlock_Code.bin from HTCdev(my own code)>
I've used temp-root, and ran ControlBear.exe ( THIS time I got the right one, from a known contributor on this forum)
It made a back-up etc.
But here's the problem again..
After it found his fourth bear my HTC restarted.
After that, it is stuck in a boot loop again...
I've unplugged my phone and plugged back it, but it's still in a boot loop.
I've relocked my HTC, and I'm installing the RUU again..
Any help guys?
I'm kinda getting desperate...
Click to expand...
Click to collapse
what version of controlbear do you have?
the that requires htcdev unlock or the nohtcdev one?
Google kgs utility sensation, you still need the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip zip unless you plan to go HTC dev route but there's both option in the utility(u choose) phone will reboot many times during this, just let it, it's not a 2 minute process, more like 15 or 20minutes
rzr86 said:
what version of controlbear do you have?
the that requires htcdev unlock or the nohtcdev one?
Click to expand...
Click to collapse
I'm using: ControlBearRelease_pyramid_ICS_WIN
stillsober said:
Google kgs utility sensation, you still need the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip zip unless you plan to go HTC dev route but there's both option in the utility(u choose) phone will reboot many times during this, just let it, it's not a 2 minute process, more like 15 or 20minutes
Click to expand...
Click to collapse
So you're saying that I should unlock my HTC but not with the HTC DEV thing?
Or is my phone not requiered to be UNLOCKED for ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip
Or do I just have to let my phone reboot for 10-15 minutes, with USB plugged on?
Arslan17 said:
I'm using: ControlBearRelease_pyramid_ICS_WIN
So you're saying that I should unlock my HTC but not with the HTC DEV thing?
Or is my phone not requiered to be UNLOCKED for ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip
Or do I just have to let my phone reboot for 10-15 minutes, with USB plugged on?
Click to expand...
Click to collapse
if your bootloader is unlocked then use the ControlBearRelease_pyramid_ICS_WIN
if your bootloader is locked then use the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip
rzr86 said:
if your bootloader is unlocked then use the ControlBearRelease_pyramid_ICS_WIN
if your bootloader is locked then use the ControlBearRelease_pyramid_ICS_WIN_NOHTCDEV.zip
Click to expand...
Click to collapse
I've unlocked my bootloade already with the Unlock_Code.bin from htc.
I've used ControlBearRelease_pyramid_ICS_WIN.
Like I said, my HTC gets stuck in a boot loop
Arslan17 said:
I've unlocked my bootloade already with the Unlock_Code.bin from htc.
I've used ControlBearRelease_pyramid_ICS_WIN.
Like I said, my HTC gets stuck in a boot loop
Click to expand...
Click to collapse
i really don't know mate
but you can still flash custom roms if you want even on S-ON:good:
rzr86 said:
i really don't know mate
but you can still flash custom roms if you want even on S-ON:good:
Click to expand...
Click to collapse
The nohtcdev one is working.
Now the wire trick...
EDIT: Aaaah, fineally I've fixed it.
I want to thank you guys for your help and contribution!