Related
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...
I have an HTC One X with 3.18 firmware that is rooted, SuperCID, S-OFF and unlocked. I want to return it to stock, unroot and re-lock - basically I want to get it as close to stock as possible.
I made a backup of the stock ROM prior to flashing a custom ROM onto it, so I was able to restore that.
So here is how I assume I need to go about this:
unroot - not sure how to do this, I can't RUU 3.18 can I? I'm downloading the stock OTA right now just in case.
set the bootloader back to "locked" using this: http://forum.xda-developers.com/showthread.php?t=2168578
Is this correct? Do I need to undo the SuperCID? Is it possible to undo the S-OFF?
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
exad said:
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's a work phone. My bosses didn't care about me rooting it, but I will need to return it eventually to exchange it for another phone and it needs to be stock in case another employee gets it.
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
exad said:
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
Click to expand...
Click to collapse
Ah, gotcha. I didn't know that would happen when I unlocked and rooted - thought I had read everything I needed to about it prior to rooting, but I guess I missed that.
I guess I could just RUU, change the CID back, but leave it as S-OFF. That would keep it from getting bricked, right? The chances of it being an issue would be pretty slim I imagine.
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
So there's really no way to return it back to stock? That's kind of a bummer...
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
kimboinatl said:
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
Click to expand...
Click to collapse
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
RollTribe said:
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
Click to expand...
Click to collapse
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
EDIT: Crap, just realized my tampered flag is still on. The RUU doesn't fix this, right? Guess I need to remove this first.
kimboinatl said:
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
Click to expand...
Click to collapse
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
RollTribe said:
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
Click to expand...
Click to collapse
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
kimboinatl said:
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
Click to expand...
Click to collapse
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
31ken31 said:
When I ruu'd it set it back to locked
Click to expand...
Click to collapse
Really? RUU shouldn't have an effect on the LOCKED flag.
31ken31 said:
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Are you sure? If so, did you happen to have s-off when you did this?
Yes and supercid
Sent from my HTC One XL using xda premium
kimboinatl said:
Are you sure? If so, did you happen to have s-off when you did this?
Click to expand...
Click to collapse
If he didn't (have s-off) he would have bricked.
I am also curious about this. If the combo of S-off and RELOCKED and RUU results in LOCKED, than its the first I've heard of it.
Running the RUU and UNLOCKED, I can say first hand, the result is that it still says UNLOCKED.
I went ahead and used the method here to set it back to LOCKED:
http://forum.xda-developers.com/showthread.php?t=2168578&page=3
I set the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
31ken31, I probably would have just tried what you did if this wasn't a work phone, I just didn't want to risk it.
Thanks to everyone for the help!
kimboinatl said:
the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
Click to expand...
Click to collapse
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
redpoint73 said:
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
Click to expand...
Click to collapse
Yes on both counts
I could have also claimed that I got one with super CID, I think I've read that it happens sometimes, but it was easy enough to change back so hey, why not.
I'll really miss having root though. It makes things so much better.
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
Sorry for the repeating post, I know there are many threads out there regarding this problem but I had problems after following those.
I used TWRP and installed "cos-0.7-20130427-NIGHTLY-evita", bootloader is unlocked (via HTCDev) and rooted. But my phone is still returning "ROGER001" when I search for supercid and s-on, hboot 2.14.
I followed this post (to turn s-off) "http://forum.xda-developers.com/showthread.php?t=2155071", but after step 5, I got FAILED (remote: 99 unknown fail) and for the touchscreen firmware (downgrade), I need s-off.
Can anyone help step by step or should I revert back to stock ROM? If I have no other option but reverting back, is there any thread I can follow?
Thanks in advance!
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Wubbz said:
You need to downgrade your touchscreen firmware to get the 4.2.2 since your on hboot 2.14. There's a sticky at the top of the original android thread. as for getting s-off it may take a couple times, I had to changes roms from cm to viper to get mine s-off(ed)
Click to expand...
Click to collapse
I saw that post to downgrade the touchscreen firmware, but pre-req for that is to turn s-off, can you please guide me how you did the s-off.
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Wubbz said:
All I can recommend is switching to a Sense based rom if your on an AOSP based one. I was on cm10 or 10.1 when I first tried it, I got the same error 99 or 96 not sure. I tried it about 5 times on cm before switching to Viper 3.2.5 and it worked first try. other than that and fallowing the directions perfectly that's all i got. If you have any other problems I'd try the thread for s-off
Click to expand...
Click to collapse
Any thread with all the steps?
right here
Wubbz said:
right here
Click to expand...
Click to collapse
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
jashang87 said:
lol, that's the thread i mentioned in my first post, I am stuck at step no 5, where I get that 99 error
Click to expand...
Click to collapse
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
exad said:
Press and hold power until the phone shuts off. this will simulate a battery pull. Reboot the PC and then try again. Repeat that until you get error 92. I don't want to say it's normal that you're getting error 99 but it certainly is extremely common. It's not that you're doing anything wrong, it's just the way the exploit works.
Click to expand...
Click to collapse
tried that 5-6 times, still no luck. Is it windows 8 that is causing the problem or how do I check if my phone has SuperCID or not? (it returns "ROGER001" in supercid)
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
exad said:
Then it doesn't have supercid. It needs to be 11111111.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
jashang87 said:
Any help how can I do SuperCID at this moment. I have OS but no touchscreen, all that available is fastboot and recovery
My phone is unlocked, I followed the instructions on HTCDev.com and it shows unlocked at bootloader screen, but still it is returning "ROGER001"
Click to expand...
Click to collapse
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
jashang87 said:
From where, I can get RUU for rogers htc one x (hboot-2.14) ?
Click to expand...
Click to collapse
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
exad said:
you need to edit your cid in mmcblck0p4. look into hex edit mmcblck0p4. There's a couple guides floating around in Q&A and General section. I am not sure if you will be able to push the file back since 2.14 introduced write protection of system files.. There was a thread where beaups helped someone to do it in Q&A but I'm at work and can't find it for you right now. If I manage to find out before you I will post it here.
Click to expand...
Click to collapse
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
jashang87 said:
Thanks for your help, I tried that already but didn't work. I flashed my phone with ViperXL rom (with Sense) and its working fine now. I will untill the release of 4.2.2 rom which will have the firmware for touchscreen.
Click to expand...
Click to collapse
All you need to do is change your cid in fastboot
Sent from my HTC One X using Xparent Green Tapatalk 2
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
exad said:
False. That only works with s-off or if you already have supercid you can change it once without s-off
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Well I tried everything, supercid in fastboot, changing cid manually, tried htc one x all-in-one toolkit. But nothing worked for me, still if there is something else I can try, I will try that.
Downgrade your hboot with jet tool then hex edit your cid.
Sent from my One X using xda app-developers app
Hi guys,
I have an HTC Explorer and I unlocked and rooted it few days back, later I got a strange problem that everytime I receive or make an outgoing call, my phone goes on loudspeaker automatically and anything I do, I can't make it stop. I factory reset it several times, reflashed stock ROM but nothing. Finally I decided to take it back to service center but since it's rooted, I tried to unroot it first and then relock the bootloader. I flashed back the stock recovery and then locked the bootloader but got some warnings while locking it.
Now it shows bootloader relocked but with some warnings in red color. I can't start my phone now as it goes in bootloader mode always, unlocking it again makes it work again so I am sure I am not doing something right.
Can you suggest me what I should do to make it lock properly and also if some suggestions related to loudspeaker problem, I will be really thankful.
Thanks.
nicesoni_ash said:
Now it shows bootloader relocked but with some warnings in red color. I can't start my phone now as it goes in bootloader mode always, unlocking it again makes it work again so I am sure I am not doing something right.
Click to expand...
Click to collapse
Flashing an RUU is the only definitive way of *relocking* your device. And, as of why it shows *relocked* and not *locked*, I quote Rohan Pruthi (dunno if he's on XDA).
Because, its a virgin no more! no matter how much you try to show otherwise...
Click to expand...
Click to collapse
vineethraj49 said:
Flashing an RUU is the only definitive way of *relocking* your device. And, as of why it shows *relocked* and not *locked*, I quote Rohan Pruthi (dunno if he's on XDA).
Click to expand...
Click to collapse
Thanks for your reply. I read this on so many places to flash RUU to solve this problem, unfortunately I am only have enough knowledge in Samsung area since I have S3 and never had to deal with HTC, so can you explain a bit more what's this RUU all about and where can I get it to flash on my friend's HTC?
If there are any links or something, that would be great. Thanks.
nicesoni_ash said:
Thanks for your reply. I read this on so many places to flash RUU to solve this problem, unfortunately I am only have enough knowledge in Samsung area since I have S3 and never had to deal with HTC, so can you explain a bit more what's this RUU all about and where can I get it to flash on my friend's HTC?
If there are any links or something, that would be great. Thanks.
Click to expand...
Click to collapse
Reboot to bootloader and connect your phone to PC, and type
Code:
fastboot getvar all
and paste the output here... It will be easier for me to tell which RUU you'd need then...
Else, you can search for one yourself... Only thing that the Radio version and hboot should match...
http://www.androidruu.com/?developer=Pico
I am not with that device now but thanks for the command, I will do that later. Hopefully I will be able to find one for my device, since it's exe file, I just need to run that once I get it downloaded?
nicesoni_ash said:
I am not with that device now but thanks for the command, I will do that later. Hopefully I will be able to find one for my device, since it's exe file, I just need to run that once I get it downloaded?
Click to expand...
Click to collapse
you should have htc sync/drivers installed.
just reboot to fastboot, connect the device, and run the exe
Can you suggest me RUU for this model as shown in attached screenshot since this version doesn't seem to be exist on your suggested link?
Thanks.
Hey bro call through loudspeaker is ur problen ri8 try flashing some latest 4.3 custom rom , it will solve ur problem
nicesoni_ash said:
Hi guys,
I have an HTC Explorer and I unlocked and rooted it few days back, later I got a strange problem that everytime I receive or make an outgoing call, my phone goes on loudspeaker automatically and anything I do, I can't make it stop. I factory reset it several times, reflashed stock ROM but nothing. Finally I decided to take it back to service center but since it's rooted, I tried to unroot it first and then relock the bootloader. I flashed back the stock recovery and then locked the bootloader but got some warnings while locking it.
Now it shows bootloader relocked but with some warnings in red color. I can't start my phone now as it goes in bootloader mode always, unlocking it again makes it work again so I am sure I am not doing something right.
Can you suggest me what I should do to make it lock properly and also if some suggestions related to loudspeaker problem, I will be really thankful.
Thanks.
Click to expand...
Click to collapse
use all in one toolkit for pico...that will be bit easier for u...:angel:
vijnathin said:
Hey bro call through loudspeaker is ur problen ri8 try flashing some latest 4.3 custom rom , it will solve ur problem
Click to expand...
Click to collapse
Can you provide me some links for those custom roms as few I saw have problems as not working camera etc.
piraterex said:
use all in one toolkit for pico...that will be bit easier for u...:angel:
Click to expand...
Click to collapse
For relocking the bootloader or flashing RUU, coz RUU flashing option is not there?
nicesoni_ash said:
Can you provide me some links for those custom roms as few I saw have problems as not working camera etc.
For relocking the bootloader or flashing RUU, coz RUU flashing option is not there?
Click to expand...
Click to collapse
checkout this..this will work for u...
http://forum.xda-developers.com/showthread.php?t=2093137
piraterex said:
checkout this..this will work for u...
http://forum.xda-developers.com/showthread.php?t=2093137
Click to expand...
Click to collapse
Download link removed from there by a mod. I already got that from somewhere else a while back and that's why my earlier question, should I use it for RUU purpose since there is nothing about RUU in that toolkit or simply to relock my bootloader?
nicesoni_ash said:
Can you provide me some links for those custom roms as few I saw have problems as not working camera etc.
For relocking the bootloader or flashing RUU, coz RUU flashing option is not there?
Click to expand...
Click to collapse
almost all 4.3.1 rom's are bug less u can find those in pico development section select as per ur wish , if u need some thing like stock rom u can use nexgen 1.6 or jaggy rom
http://forum.xda-developers.com/forumdisplay.php?f=2185
nicesoni_ash said:
Download link removed from there by a mod. I already got that from somewhere else a while back and that's why my earlier question, should I use it for RUU purpose since there is nothing about RUU in that toolkit or simply to relock my bootloader?
Click to expand...
Click to collapse
for relocking your bootlocker..
how to unlock the relocked bootloader
i m using htc explorer as per the instruction i unlocked the bootloader by using htc bootloader unlock 0.2.0.1819 after that i flashed the custom rom in htc,even though i icreased the internal memory also by using mini tool partition wizard as by ur following youtube video but respond in too slow manner i reset the factory settings after i worked normally.................now what i did means using htc bootloader unlock 0.2.0.1819 software i locked the bootloader now the phone always start in cwr mode it doesn't start in normal mode........please help me i just want ur kind response..............