[Q] how to s-off 2.10.124.8 without htcdev - HTC Desire S

This is my first post and a rather simple question. I have been lurking in the forum since i got my last desire. But now I wanna root my htc desire s after I upgraded to sense 3.0 ota.
The question is this: do I have to do anything special before going through the processes? Is it better for me to go with v1 or v2 (meaning the two methods posted here)?
Thank you for answering!

I guess you by now know what adb and fastboot is, so you should now all there's is to know when getting started on rooting your phone. First you need to downgrade you Hboot in order to get the S-OFF, just do a couple of searches on google and they'll pop right up. Once done just use SuperOneClick to root, and you're done, now you can get down to flashing new roms, kernels and so on

Gormsen said:
I guess you by now know what adb and fastboot is, so you should now all there's is to know when getting started on rooting your phone. First you need to downgrade you Hboot in order to get the S-OFF, just do a couple of searches on google and they'll pop right up. Once done just use SuperOneClick to root, and you're done, now you can get down to flashing new roms, kernels and so on
Click to expand...
Click to collapse
Thanks for the reply but you haven't answered my question. First I need to downgrade for sure. But what method should I use between the two posted here in sticky threads? And is it certain that I will be able to downgrade with the ruu for Europe cause this must be for unbranded phones I think. Meaning, must I also create a gold card before hand?
Thanks
edit: Can anyone tell me for sure from the software number I have if I am branded or not? I think it's from vodafone Greece but I am not certain (it was a gift).

Are you referring to the two methods mentioned in this post?
http://forum.xda-developers.com/showthread.php?t=1146601
If so, then go for the method with downgrade and revolutionary S-OFF. I don't quite understand you question?
I never created a gold card, and I'm doing fine without. I don't think you need one unless you use the method with HTC-dev.

Use the newer version from shadi22
Sent from my Desire S using Tapatalk 2 Beta-6

dan-fish said:
Use the newer version from shadi22
Sent from my Desire S using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
How can you be so certain?(not ironic but please explain your reasoning cause I really don't want a bricked phone) Because he says in underlined and bold that :
"This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you."
And I have 2.10.124.8 .

an8rwpofagos said:
How can you be so certain?(not ironic but please explain your reasoning cause I really don't want a bricked phone) Because he says in underlined and bold that :
"This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you."
And I have 2.10.124.8 .
Click to expand...
Click to collapse
Ah my mistake. Then you should use the other one. If done correctly though, neither should brick the phone
Sent from my Desire S

dan-fish said:
Ah my mistake. Then you should use the other one. If done correctly though, neither should brick the phone
Sent from my Desire S
Click to expand...
Click to collapse
Ok then. What about the ruu then? Will i be able to use the one for europe or do I have to create a goldcard ? I have read about it but I am not sure if I am branded or not. If someone can help me I would appreciate it.

You need to use the one specific to your carrier and region. It also has to be one with the older h-boot
Sent from my Desire S

it is recommended that you adjust the following two settings:
Settings->Applications->Development->USB debugging = TICK (Yes)
Settings->Power->Fast boot = UNTICK (No)
Install ADB/FASTBOOT on your PC (by following advice given in this thread http://forum.xda-developers.com/showthread.php?t=1272595 )
You should then be able to determine your base ROM details by using command, and noting all the details in settings...about phone....software ....more
Code:
fastboot getvar cidnum
You'll find the code in the following list
http://forum.xda-developers.com/attachment.php?attachmentid=994630&d=1334067717
Swyped form ym Dersie S unsig XAD Permuim

ben_pyett said:
it is recommended that you adjust the following two settings:
Settings->Applications->Development->USB debugging = TICK (Yes)
Settings->Power->Fast boot = UNTICK (No)
Install ADB/FASTBOOT on your PC (by following advice given in this thread http://forum.xda-developers.com/showthread.php?t=1272595 )
You should then be able to determine your base ROM details by using command, and noting all the details in settings...about phone....software ....more
Code:
fastboot getvar cidnum
You'll find the code in the following list
http://forum.xda-developers.com/attachment.php?attachmentid=994630&d=1334067717
Swyped form ym Dersie S unsig XAD Permuim
Click to expand...
Click to collapse
Thank you! This was a complete answer. I will do it and post here.

Ok so I type the command but nothing is happening... It says that it's waiting for the device and nothing happens. I typed fastboot getvar vodap006.
Any help? Thank you beforehand.

an8rwpofagos said:
Ok so I type the command but nothing is happening... It says that it's waiting for the device and nothing happens. I typed fastboot getvar vodap006.
Any help? Thank you beforehand.
Click to expand...
Click to collapse
You should reboot the phone so that its in BOOTLOADER (fastboot) mode.
plug in USB cable from PC
Alright mis-communication there, you must actually type
Code:
fastboot getvar cidnum
and the purpose of that is you'll get returned the region ie HTC__001
How did you know vodap006? as thats the answer and the purpose of this command
So I suggest reboot phone into bootloader and then you could simply type
Code:
fastboot getvar all
which should return a greater amount of information.

Ok thx for the clarification. I read it at the post you linked and I thought it must have been the one to type. Anyway I will do it right hopefully this time
edit: ok it says I got cidnum T-MOBN14 and I dont know which one is that. I can't find it in your link. Any ideas ?

solved ???? I got same issues
---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------
paul.robo said:
solved ???? I got same issues
Click to expand...
Click to collapse
never mind. sorted it now I typed the same op lol until I went down further lmao

After some searching here on the forum it seems that I must create a goldcard to chance the cidnum to 11111111. Is this correct? Can it be done only with the goldcard or is there any other program needed?
Thank you.

an8rwpofagos said:
After some searching here on the forum it seems that I must create a goldcard to chance the cidnum to 11111111. Is this correct? Can it be done only with the goldcard or is there any other program needed?
Click to expand...
Click to collapse
I believe that the creation of a goldcard will enable you to flash a ROM which is not intended for your region, which is the same as what happens when you have a cidnum of all 1's anyway.
So just create a goldcard and try the RUU with that in place

ben_pyett said:
I believe that the creation of a goldcard will enable you to flash a ROM which is not intended for your region, which is the same as what happens when you have a cidnum of all 1's anyway.
So just create a goldcard and try the RUU with that in place
Click to expand...
Click to collapse
Is there any way I can change the cidnum without a goldcard? I wanna avoid it if possible

an8rwpofagos said:
Is there any way I can change the cidnum without a goldcard? I wanna avoid it if possible
Click to expand...
Click to collapse
Yes, but they're far more complex....ie XTC-Clip
The Gold card is certainly the easier option that you have! just make one! whats the concern, why don't you want to use one? only have one SD card?

ben_pyett said:
Yes, but they're far more complex....ie XTC-Clip
The Gold card is certainly the easier option that you have! just make one! whats the concern, why don't you want to use one? only have one SD card?
Click to expand...
Click to collapse
Well I read the sticky and I would like to use the method with the adb commands but I don't understand how (and if) I must get temproot.

Related

[Q] can someone help me?

i just bought a sensation, and now i'm a previous HD2 owner. so i'm not a noob, i hope.
so...unlocking bootloader and rooting and s-Off...which one to follow? the official on hTCDev website or the revolutionary way?! any difference between those?
please someone clarify some things, as i just became a sensation user, i have no idea about anything of these since HD2 is way different as i noticed and since there are a lot of info on the net, i don't wanna get into things i shouldn't.
i got a second hand sensation but it's still on factory default with android 2.3.4 and sense 3.0
really any help is greatly appreciated
If your HBOOT is supported by Revolutionary ALWAYS use that one...
I dont like HTCdev - It should only be used if your HBOOT is unsupported
Just have a good read through all the noob guides. Be sure of what you're doing before attempting anything...
I cant stress how important it is to follow the guides 100%
azzledazzle said:
If your HBOOT is supported by Revolutionary ALWAYS use that one...
I dont like HTCdev - It should only be used if your HBOOT is unsupported
Just have a good read through all the noob guides. Be sure of what you're doing before attempting anything...
I cant stress how important it is to follow the guides 100%
Click to expand...
Click to collapse
okay great, that was so helpful! you're really a good Q&A contributor, i don't know were i would have learned that anywhere else!
i'm off to check if my Hboot is supported.
thanks button clicked, cheers!
cant help but detect some sarcasm there
azzledazzle said:
cant help but detect some sarcasm there
Click to expand...
Click to collapse
eh? why would you say that?!
Maybe i misinterpreted it !
who knows ?
azzledazzle said:
cant help but detect some sarcasm there
Click to expand...
Click to collapse
no really i searched like two hours and on youtube but i couldn't know what's the difference between the official tool and the one called revolutionary...why you felt sarcasm in my words is beyond me...sorry anyway...
haha maybe its just me..
Anyway, Revolutionary IS THEE best tool for S-OFF... providing your HBOOT is supported of course. Did you check to see if its supported ?
if you got hboot 1.18.0000 please use revolutionary method to unlock your boot loader. If you unlock your bootloader with htcdev method you will unlock somd parts of the hboot. not every thing. then you cant flash a custom kernel because it already locked boot.img and cant write a new file over it. thne you will get wifi,bluetooth problems. so unlock your bootloader with revolutionary.
Sent from my HTC Sensation Z710e using XDA
azzledazzle said:
haha maybe its just me..
Anyway, Revolutionary IS THEE best tool for S-OFF... providing your HBOOT is supported of course. Did you check to see if its supported ?
Click to expand...
Click to collapse
yep, it's supported i will do it tonight before bed and sleep at ease having it unlocked ^.^
namila007 said:
if you got hboot 1.18.0000 please use revolutionary method to unlock your boot loader. If you unlock your bootloader with htcdev method you will unlock somd parts of the hboot. not every thing. then you cant flash a custom kernel because it already locked boot.img and cant write a new file over it. thne you will get wifi,bluetooth problems. so unlock your bootloader with revolutionary.
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
i appreciate your concern i'll certainly use revolutionary.
arabology said:
i appreciate your concern i'll certainly use revolutionary.
Click to expand...
Click to collapse
great
Sent from my HTC Sensation Z710e using XDA
arabology said:
yep, it's supported i will do it tonight before bed and sleep at ease having it unlocked ^.^
Click to expand...
Click to collapse
Happing rooting...
Just curious, how will rooting (& thereby voiding the warranty) bring you some peace... For most people, it would bring anxiety (& bad dreams)...
Wait a minute, you said unlocking, i hope you didn't mean sim-unlock instead of rooting?
Cheers, Jp
japinder said:
Happing rooting...
Just curious, how will rooting (& thereby voiding the warranty) bring you some peace... For most people, it would bring anxiety (& bad dreams)...
Wait a minute, you said unlocking, i hope you didn't mean sim-unlock instead of rooting?
Cheers, Jp
Click to expand...
Click to collapse
hehe yeah. no my phone is not sim locked
it didn't work!!
i tried it and my HBOOT is 1.18.0000 revolutionary supports it! i filled up everything correctly on the site and got a beta key. on revolutionary.exe, it ditects my phone just fine, after that i copy/paste the beta key. it starts but after a minute is gives "failed to get root "
help?
Did you get S-OFF via revolutionary ??
what does your HBOOT say now ??
azzledazzle said:
Did you get S-OFF via revolutionary ??
what does your HBOOT say now ??
Click to expand...
Click to collapse
thanks for your reply. nothing changed in my after i tried revolutionary. HBOOT is still 1.18.0000
and it still says S-ON ??
If so try it again Copy the beta key into notepad and enter it into revolutionary manually.
then tell me what happens, also, link me to the guide you are / was following, and what step you got to before this problem occurred
azzledazzle said:
and it still says S-ON ??
If so try it again Copy the beta key into notepad and enter it into revolutionary manually.
then tell me what happens, also, link me to the guide you are / was following, and what step you got to before this problem occurred
Click to expand...
Click to collapse
yeah it still rights LOCKED up with pinkish red highlight and under it S-ON RL
i already tried like 5-6 times...nothing worked...i installed drivers, unticked fast boot on phone, and ticks usb debugging...
i followed this method: http://forum.xda-developers.com/showthread.php?t=1192300
oh i got the error on step 1 in revolutionary...

How to flash a new radio on S-on HTC-dev unlocked

I think, after much reading in this forum, that the only way to flash a new radio with a dev-unlocked Desire S is the following procedure.
0. BACKUP
1. download official RUU with wanted radio
2. HTC-dev relock device with "Fastboot oem lock"
3. flash RUU package
4. HTC-dev unlock device
5. flash Rom of choice OR do nandroid-restore
6. flash correct boot.img from the Rom used in #5 using "Fastboot flash boot boot.img"
7. restore everything, as the phone is wiped twice during the procedure (unless nandroid restore is used earlier)
As I do not see a RUU with a newer radio than I've got myself (.10.08.04), and I dev-unlocked myself, I cannot try this procedure until the new update is ready.
Please correct or add if you know more....
Jeroen.
You may need to change your main version.
If you have purchased your phone with Sense 3 there might be a chance that it had 2.10.xx.x version before you unlocked it with htcdev.com.
But if you device was with Sense 2 when you got it, then you accept an OTA update and unlocked afterwards then you version will be 12.10.xx.x or 13.10.xx.x and you need to modify the misc partition before running a RUU
have anybody tried it? please answer
+1
glacier1122 said:
have anybody tried it? please answer
Click to expand...
Click to collapse
+1
excuse me, where i can get boot.img..? is it the same with hboot.img..?
and is there anybody try this one?
thanks
padrik said:
excuse me, where i can get boot.img..? is it the same with hboot.img..?
and is there anybody try this one?
thanks
Click to expand...
Click to collapse
@ Padrik ... A polite word. Stop tacking your own problems onto the bottom of somebody else's unless you are 100% sure that you have an identical problem. Stop posting stuff that has nothing to do with the OP. And learn to use the search engine. People are not here to spoon-feed the answers - we had to learn all this and it makes everything better if you learn and understand rather than just accepting what people tell you.
I could have given you the answer far quicker than typing this post, but people need to learn that there are rules on XDA
glacier1122 said:
have anybody tried it? please answer
Click to expand...
Click to collapse
anyone?
Yes, tried it, and....
Working with the latest radio.
Verstuurd van mijn Nexus 7 met Tapatalk
amidabuddha said:
You may need to change your main version.
If you have purchased your phone with Sense 3 there might be a chance that it had 2.10.xx.x version before you unlocked it with htcdev.com.
But if you device was with Sense 2 when you got it, then you accept an OTA update and unlocked afterwards then you version will be 12.10.xx.x or 13.10.xx.x and you need to modify the misc partition before running a RUU
Click to expand...
Click to collapse
Hello. Out of curiousity if I install the new ruu will I get any problem?
I have hboot 2.00.0002
Radio: 3822.10.08.04_m
Currently using fallout 4.4
Sent from my HTC Desire S using xda app-developers app

[Q] It's bricked guys, and this is serious sht

Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?
rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.
all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177

[Q] HTC Sensation totally stock in boot loop

Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.
AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb
rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible
Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++

htc one x no os installed

Okay so my friend asked me to fix a phone that he says one day it got stuck in boot splash screen. He claims he did not try to flash a custom Rom or something but he said he hadn't.here's some of the phones info
HTC one x
***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
Can anyone sheed some light on the subject.
I don't know how to use adb and fastboot
And I have Windows xp and Mac 10.6 and lynx
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Mr Hofs said:
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Click to expand...
Click to collapse
As if by magic, it appears in the One XL forum.
I think your friend is telling fibs, phones don't just magically stop booting for no reason. Please tell him to own up to whatever activities lead to this situation, as embarrassing as it might be, I need to know how this happened in order to help properly.
Now, just to be clear, the phone is actually the HTC One XL, not the HTC One X. They look similar but are actually very different. What recovery is installed on the device?
Another question for you, why isn't your friend posting here and attempting to fix this problem himself? If he can't recover from a simple problem like this (or can't be bothered learning/trying) he honestly has no place having a modified phone. That might sound harsh but it's the truth, this is very basic knowledge, it's flashing 101. Knowing how to recover from something like this is an essential skill for anyone who owns a modified phone. If your friend isn't interested in being honest about what lead to this situation, or interested in learning how to recover from this situation, my only advice is to return to the device to stock and leave it that way. I'd strongly urge him to get on here and post himself, and do some reading to educate himself on the ins and outs of modified devices.
Sent from my Evita
sorry for being so vauge
My friend is a lady friend who had no idea how the phone could have become modified. The phone is a HTC one X and my lady friend said she would love nothing more then to have a stock phone. My friend has no intrest in leaning how the in's and out's of HTC but, I on the other hand would love to learn about HTC and Android. I come from a n Apple community and have a little knowledge but not a lot.
Anything you can tell me would help greatly, and I would be indeed greatful.
Sincerely Nanamkin
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Thank you so much
timmaaa said:
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Click to expand...
Click to collapse
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Nanamkin said:
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Click to expand...
Click to collapse
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Man your GOOD
timmaaa said:
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Click to expand...
Click to collapse
I am sooo sorry. you are absulotly right, and you are good! how did you know that? lol
here is the right info.
TWRP 2.3.1.0
im sorry i cant boot into the phone to check the setting/about phone for a software version. do you know any other way?
and while i was messing around i figured out how to install ADB and FASTBOOT and use it.
I'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the CID for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita
got it
timmaaa said:
i'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the cid for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
sent from my evita
Click to expand...
Click to collapse
cid:11111111
Ok. To get the phone back to stock you Erik need to run an RUU, but in order to do that safely you'll first need to get s-off. To get s-off you're gonna need a booting ROM on the device. Purely for this exercise I think Kickdroid would be your best option, head to our Android Development section and find the Kickdroid thread, download it, and use TWRP recovery to install it. Look in the How-To Guide For Beginners thread in my signature for full instructions on how to flash the ROM. Please note, you'll also need to flash the boot.img from the ROM zip via fastboot after flashing the ROM.
Sent from my Evita
got it
Okay I have the Rom on my phone now what?
Nanamkin said:
Okay I have the Rom on my phone now what?
Click to expand...
Click to collapse
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
your awesome
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
oh yeah i was over there just a little awhile ago. i een your name so i tiend to fallow it but couldnt get the rom. thank you sooo much
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Nanamkin said:
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Click to expand...
Click to collapse
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
I got the rom to work
timmaaa said:
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
Click to expand...
Click to collapse
I got the rom to boot after fallowing your directions(like you said)lol. but when i do steps 7 the 3 codes it says there are no directory. I got the first one to go but the other 2 would not work
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
got the os to boot
timmaaa said:
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
Click to expand...
Click to collapse
okay so i have the rom on the phone (kickdroid) and now i cant run the last 3 codes on step 7. any clue. I have soffbin zip unzipped in the directory but where exactly do i put it? i have it in the same folder as adb and fastboot is that right?

Categories

Resources