Related
Hi everyone. Ok so I'm trying to root my HTC Buzz (Wildfire) using unrevoked V3.32, but it keeps saying when the phone rebooted :
Error: failed to get root. Is your firmware too new?
I've done a factory reset on my phone too cause I thought that might help; but it didn't...
I'm running Android version 2.2.1 on my HTC Wildfire.
Can ANYONE PLEASE HELP ME!?!?!
I really need to root my phone.
Also if there is another program that's better to use than unrevoked can you please tell me...
Thanks!
you can only remove security to root it with alpharev x beta
http://forum.xda-developers.com/showthread.php?t=1145035
Remember though, there's no way to revert back yet, so, if you care for your warranty, don't do it, and, there's no other way to root.
Also, this is related to Wildfire Android Development?
@3xeno I don't know if this is really related to Wildfire Android Development; but I just really need some help. Ok I would really like to try it out; but I don't want to lose the phone's warranty...
Are you sure there aren't ANY other ways to root the HTC Wildfire without S-OFF???
I really can't lose the phone's warranty....
Yes I am sure, which is why I forewarned. Else I wouldn't. I would rather not see someone follow a post by me, then come back and ask "I want to revert for warranty... etc etc".
If you need warranty, you will have to wait for AlphaRev X to release the downgrader, which will remove their patched HBoot (bootloader) and restore the stock HTC one. But, there is no release date info on it, so, asking me when it would be released will be pointless, since I have no idea myself.
PS - Development is ONLY for development purposes. There is a dedicated Q and A subsection for these type of posts.
@3xeno Ok since there is no other way; I'm going to downgrade froyo to stock Android 2.1
I found a post explaining how to downgrade my Android. Do you think this will work???
My plan is to downgrade the android OS of my HTC Wildfire, and then root it using unrevoked.
No, it wont work, because its for Desire, and Desire is not equal to Wildfire. There is another thread in the Wildfire Android Development for downgrading 2.2 to 2.1, but its pointless for your purpose because it leaves the bootloader untouched.
As I have specified before, the only way for you is AlphaRev X. Looking at other phones techniques wont help because they are all pretty much unique, unless explicitly specified that it works on other devices.
Thanks for all the help.
Going to use AlphaRev X
I'm Sorry if this has been brought up many times or not, but I got so confused to the point I have to ask you guys on how to do this.
I'm used to play with the Galaxy S2 which I know how to root and all that, so i thought HTC Wildfire S wouldn't be the bigger problem since they both are on Android.. i was mistaken.
Here's my question: How to root my device with stock 2.3.3 firmware, Where is the actual guide which doesn't take me ten other places which confuses me and seems it's not even the correct guides for rooting this device.
Device information:
HTC Wildfire S A510e
Stock Android 2.3.3 European
Sense version: 2.1
Something Called S-on/S-off , could anyone tell me what this mean and how to know wethere im "on" or "off" and how to change this
Any more information i need to give?
I would appreciate it ALOT if some nice guy/gal would show me a tutorial on how to root this device, nothing more, nothing less.
Thanks
To check if your WFS is S-on or S-off you should switch it off and than keep the volume down button pressed whilst you press the power button. The first line of this screen will state if you're S-off or not..
If you're not, there's no other way to get S-off than the xtc-clip.
Unfortunately i'm stuck on S-off and there's no xtc-clip near my location afaik and i don't think buying one for the sake of rooting one device is worth it.
Yeah i got into the Hboot after many tries(guess i did many wrong attemps) and it says it S-On
So basicly I have to buy this "xtc-clip" to ever get my phone rooted, or is there other ways?
For now the xtc-clip is the only way to achieve s-off on the WFS....
I'm still hoping that htc will release the bootloader in due time though
Ahh crap, so it was only about luck wether it's S-off or S-On in the beginning?
That's right, apparently HTC released S-off models of the WFS in the Asian regions... not sure how much is true about that btw
Thanx for that "how to check s-on guide".
Was hoping mine was s-off but its not :-( tough luck
1. How S-ON after XTC-CLIP ? Riff Box help ?
2. How send command [email protected]=7,1 ?
Kamil1987 said:
1. How S-ON after XTC-CLIP ? Riff Box help ?
2. How send command [email protected]=7,1 ?
Click to expand...
Click to collapse
sorry to burst your bubbly man but xtc clip is NOT reversible. end of. it doesn't save any backups of what it changes at all so your stuck like.
no program will give you s-on, or return you to your orginal simlock or cid as xtc clip changes the secure-flag and deletes the rest....
Yesterday i turned on S-ON after XTC-CLIP in HTC Wildfire and HTC Legend, in HTC Desire S still does not work. In the evening I'll check on HTC Wildfire S
Kamil1987 said:
Yesterday i turned on S-ON after XTC-CLIP in HTC Wildfire and HTC Legend, in HTC Desire S still does not work. In the evening I'll check on HTC Wildfire S
Click to expand...
Click to collapse
what? how? just so we are clear you have managed to take a s-offed htc wildfire by xtc clip and make it s-on again?!?!
Secret On HTC Wildfire S also working but HTC Desire S not working.
On HTC Desire Z not working.
Kamil1987 said:
Secret On HTC Wildfire S also working but HTC Desire S not working.
Click to expand...
Click to collapse
What is the point in posting if your not going to share. I have no need for this but it pissed me off when people come on glory and money hunting,cos if you didn't intend making any money from this then you would share.
For me you can just jog on.
UTID
slymobi said:
What is the point in posting if your not going to share. I have no need for this but it pissed me off when people come on glory and money hunting,cos if you didn't intend making any money from this then you would share.
For me you can just jog on.
UTID
Click to expand...
Click to collapse
+1 this is a community based on helping and sharing information and ideas. what is the point of trying to come off with comments like that? are you just trying to get a kick out of it are you generally trying to piss people off?? i bet your just some kid somewhere trying to get jollys from people who took the plunge with the xtc clip as rev. wasnt about.
come back when you ACTUALLY have something of use or you grow up. and i dont expect either soon.
heavy_metal_man said:
+1 this is a community based on helping and sharing information and ideas. what is the point of trying to come off with comments like that? are you just trying to get a kick out of it are you generally trying to piss people off?? i bet your just some kid somewhere trying to get jollys from people who took the plunge with the xtc clip as rev. wasnt about.
come back when you ACTUALLY have something of use or you grow up. and i dont expect either soon.
Click to expand...
Click to collapse
sorry to bump a old thread he lie's it is NOT possible on ANY device. as all data is wiped when secure flag is wiped NO WAY BACK. as you cannot write that deleted data back to the phone. even if you got hold of the needed data you still wouldnt be able to flash it. and did u notice how quick he was between his posts saying desire z works or watever then wildfire s worked its lie's the guys a fool.
I'm also interested in putting back S-ON after having used the XTC clip to make it S-OFF. But what interests me is a general method that would work on any device (compatible with the XTC clip of course).
I think it is possible because I managed to make it work on the Desire Z with the following method:
1) use XTC clip to make the device S-OFF.
2) use gfree to make it back S-ON. (https://github.com/tmzt/g2root-kmod/tree/master/scotty2/gfree)
But the thing is: gfree is using a vulnerability only available on the HTC Desire Z so it does not work on all devices.
Any ideas?
well, once you have s-off you can map the all of the nand via fastboot kernal commands, but like the wildfire s we would need to work out the size of all the partitions and "write in" the information for the radio. if we did that and then xtc clipped a buzz on the revolutionary hboot it may show you where the the s-0n s-0ff "bit" is. then, in theory you could write to the nand and overwrite the bit to change it. in theory this would also work to properly s-0ff the device so all hboots could be flashed. but that would imply that the s-0ff s0n bit is actually in the unmapped partition of the nand. i would like to try this idea just to see how far we could get, as i may be getting another s-on buzz in july but we would have to get the mappings for the mtd partitions. oh, and gfree only works on emcc devices i think, thats why it wont work for us as it is mtd.
gfree only works on devices that use emmc and have this vulnerability, that is to say only the HTC Desire Z...but it does not matter.
Be careful with what is below, it may brick your device so do it at your own risk.
I managed to set the S-ON flag back on the HTC Desire Z with the following command: [email protected]?7,1. This can be sent to the device by first putting the device in HBOOT mode, then issuing "rtask C" and then talking to the radio with AT commands (see http://tjworld.net/wiki/Android/HTC/Vision/RadioAnalysis#TalkingtotheRadio).
But it did not work on a HTC Desire S.
heavy_metal_man said:
well, once you have s-off you can map the all of the nand via fastboot kernal commands, but like the wildfire s we would need to work out the size of all the partitions and "write in" the information for the radio. if we did that and then xtc clipped a buzz on the revolutionary hboot it may show you where the the s-0n s-0ff "bit" is. then, in theory you could write to the nand and overwrite the bit to change it. in theory this would also work to properly s-0ff the device so all hboots could be flashed. but that would imply that the s-0ff s0n bit is actually in the unmapped partition of the nand. i would like to try this idea just to see how far we could get, as i may be getting another s-on buzz in july but we would have to get the mappings for the mtd partitions. oh, and gfree only works on emcc devices i think, thats why it wont work for us as it is mtd.
Click to expand...
Click to collapse
1) Could you develop on your "fastboot kernal" commands ? How do you do what you are talking about ?
2) I know where the security flag is for the HTC Desire Z but not for the Desire S, I would need to backup all the partitions, S-OFF it and then make a diff to identify it.
saidelike said:
gfree only works on devices that use emmc and have this vulnerability, that is to say only the HTC Desire Z...but it does not matter.
Be careful with what is below, it may brick your device so do it at your own risk.
I managed to set the S-ON flag back on the HTC Desire Z with the following command: [email protected]?7,1. This can be sent to the device by first putting the device in HBOOT mode, then issuing "rtask C" and then talking to the radio with AT commands (see http://tjworld.net/wiki/Android/HTC/Vision/RadioAnalysis#TalkingtotheRadio).
But it did not work on a HTC Desire S.
1) Could you develop on your "fastboot kernal" commands ? How do you do what you are talking about ?
2) I know where the security flag is for the HTC Desire Z but not for the Desire S, I would need to backup all the partitions, S-OFF it and then make a diff to identify it.
Click to expand...
Click to collapse
Well, this idea actually belongs to the guys over at the wildfire s s-off campaign( had to be said )
The way it works is that you issue a kernal, or clockworkmod recovery for that matter, with new paramiters for the mtd partitions via fastboot and when that new kernal is loaded the "unmaped areas will then be mapped. Then as you said for point 2 you would dump both before and after the xtc clip and !hopefully! It would show the location of the s-off. The partition information will be device specific, so each device and hboot would need to be accounted for. But, the theory is solid. The only issue the wfs guys are having is trying to write to the nand. But with an s-off device I hope this wouldn't be an issue. If you head over to there s-off campaign you will find out alot more on this idea.
Sent from my HTC Sensation XE with Beats Audio using xda premium
heavy_metal_man said:
Well, this idea actually belongs to the guys over at the wildfire s s-off campaign( had to be said )
The way it works is that you issue a kernal, or clockworkmod recovery for that matter, with new paramiters for the mtd partitions via fastboot and when that new kernal is loaded the "unmaped areas will then be mapped. Then as you said for point 2 you would dump both before and after the xtc clip and !hopefully! It would show the location of the s-off. The partition information will be device specific, so each device and hboot would need to be accounted for. But, the theory is solid. The only issue the wfs guys are having is trying to write to the nand. But with an s-off device I hope this wouldn't be an issue. If you head over to there s-off campaign you will find out alot more on this idea.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Great. Thanks for pointing me to [WFSdev][THE S-OFF CAMPAIGN] Kernal experts needed - exploit is being developed!. Even if they "only" want to get HBOOT S-OFF (different from radio S-OFF that we get with the XTC Clip), the idea behind consisting in using "fastboot boot" to boot a kernel and mapping the usually unallowed partitions differently is an idea that needs to be look at deeply.
The magic is with the following command:
Code:
./fastboot -c "mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata),[email protected](devlog),[email protected](hboot)" boot recovery-clockwork-5.0.2.8-marvel.img
Hello guys i i have htc wildfire a3333 bought from UK and its network locked in.sweden.. I tried to s-off using revolutionary but it gives me error.. Zerg failed something like that.. Then i tried root my phone using all sort of software all of them failed which is kinda weird i even tries to unlock my bootloader using HTCDEV and its failed 「Bootloader err 」 after reading xda topics whole week Revolutionary should able to.unlock my phone since bootloader is 1.01.0001. .. Why cant i at least root my phone? can anyone help me? Pls??
HTC WILDFIRE A3333
FRIMWARE VERSION: 2.1-update1
Baseband version: 13.53.55.24h_3.35.19.25
Kernel: 2.6.29-6fb59e13
Build number 1.37.405.1 CL262524 release keya
Software number: 1.37.405.1
Buzz pvt ship S ON
HBOOT 1.01.0001
MICROP 0622
RADIO 3.35.19.25
P.S i followed exactly every step in guide everytime it stuck in somewhere and givimg me.error such as failed to get shell root..
Sorry if.i posted this wrong.place i made account just to post this.. Pls.help.me
stx3 said:
Hello guys i i have htc wildfire a3333 bought from UK and its network locked in.sweden.. I tried to s-off using revolutionary but it gives me error.. Zerg failed something like that.. Then i tried root my phone using all sort of software all of them failed which is kinda weird i even tries to unlock my bootloader using HTCDEV and its failed 「Bootloader err 」 after reading xda topics whole week Revolutionary should able to.unlock my phone since bootloader is 1.01.0001. .. Why cant i at least root my phone? can anyone help me? Pls??
HTC WILDFIRE A3333
FRIMWARE VERSION: 2.1-update1
Baseband version: 13.53.55.24h_3.35.19.25
Kernel: 2.6.29-6fb59e13
Build number 1.37.405.1 CL262524 release keya
Software number: 1.37.405.1
Buzz pvt ship S ON
HBOOT 1.01.0001
MICROP 0622
RADIO 3.35.19.25
P.S i followed exactly every step in guide everytime it stuck in somewhere and givimg me.error such as failed to get shell root..
Sorry if.i posted this wrong.place i made account just to post this.. Pls.help.me
Click to expand...
Click to collapse
Like you said you should be able to use revolutionary. In this case most likely a solution could only be found if you're more specific what exactly you've done and what responses (confirmations and errors) you got and at which point.
First of all: did you use a guide from this forum? - if yes: which one?
BTW: the place you posted this is absolutely perfect
stx3 said:
Hello guys i i have htc wildfire a3333 bought from UK and its network locked in.sweden.. I tried to s-off using revolutionary but it gives me error.. Zerg failed something like that.. Then i tried root my phone using all sort of software all of them failed which is kinda weird i even tries to unlock my bootloader using HTCDEV and its failed 「Bootloader err 」 after reading xda topics whole week Revolutionary should able to.unlock my phone since bootloader is 1.01.0001. .. Why cant i at least root my phone? can anyone help me? Pls??
Click to expand...
Click to collapse
I would suggest you to try Revolutionary following this guide.
kgs tool can solve zerg root failed error but I am not sure if that also works with Wildfire.
You can confirm that on kgs1992's thread.
Please confirm that before doing anything.
Warning for non HTC Sensation/XE/4G devices:
This tool is not intended for any other phones, although some features may work for other phones as well.
The reason you see batch files & not an executable is because my script is open to all.
View it, use it, change it, do as you wish!
Click to expand...
Click to collapse
optimusodd said:
Please confirm that before doing anything.
Click to expand...
Click to collapse
To be even more specific: you should find out why the suggested method(s) fail before proceeding with other attempts. E.g From what I've heard and seen you should be glad that the htcdev method failed as it doesn't give you s-off which isn't mandatory to root but for flashing a new7different radio, use custom mtd partitions etc.
eventcom said:
From what I've heard and seen you should be glad that the htcdev method failed as it doesn't give you s-off which isn't mandatory to root but for flashing a new7different radio, use custom mtd partitions etc.
Click to expand...
Click to collapse
Doh!It is so sad to see all this happening.It is really a sad scenario to see these buddies going through this.I can feel their pain and frustration.HTCdev sucks!!!
Unlocking via HTCdev is completely Bull****…..Getting ROOT without S-OFF is like listening to porn on the Radiops!
I am so sad for HTC. http://www.eweek.com/c/a/Mobile-and...attle-Looks-to-Windows-Phone-8-Report-441483/
I have been loyal to HTC right from HTC Touch.I adore HTC devices.It is absolutely beyond my comprehension how the company like HTC (the pioneer of smartphones) that produced such outstanding devices would self-destruct like this.They are axing their own feet.
HTC is losing a battle to Samsung coz they have refused to embrace the consumers.Samsung has already released the source codes of their kernels and allows Bootloader unlocking and S-OFF’ing on their devices.Maybe Samsung sucks at coding bootloader protection lol.Whatever!
If HTC don’t assist developers in unlocking bootloaders and S-Off’ing for HTC devices,it will just drive away customers who like to root or tinker with their phones as more and more people want to have complete control over their phone.
May God bless HTCdev!!If they don’t change their policy,I am gonna say adios to HTC and “Hola!Samsung!”
optimusodd said:
Doh!It is so sad to see all this happening.It is really a sad scenario to see these buddies going through this.I can feel their pain and frustration.HTCdev sucks!!!
Unlocking via HTCdev is completely Bull****…..Getting ROOT without S-OFF is like listening to porn on the Radiops!
I am so sad for HTC. http://www.eweek.com/c/a/Mobile-and...attle-Looks-to-Windows-Phone-8-Report-441483/
I have been loyal to HTC right from HTC Touch.I adore HTC devices.It is absolutely beyond my comprehension how the company like HTC (the pioneer of smartphones) that produced such outstanding devices would self-destruct like this.They are axing their own feet.
HTC is losing a battle to Samsung coz they have refused to embrace the consumers.Samsung has already released the source codes of their kernels and allows Bootloader unlocking and S-OFF’ing on their devices.Maybe Samsung sucks at coding bootloader protection lol.Whatever!
If HTC don’t assist developers in unlocking bootloaders and S-Off’ing for HTC devices,it will just drive away customers who like to root or tinker with their phones as more and more people want to have complete control over their phone.
May God bless HTCdev!!If they don’t change their policy,I am gonna say adios to HTC and “Hola!Samsung!”
Click to expand...
Click to collapse
from what I hear and read it's much easier to unlock the current htc devices. The problem is more related to that our buzz is a so called "legacy device" which means: it's not the future and not meant to generate any sales of...
Re. open information to devs: bear in mind that most people don't want to touch their phone any deeper than downloading apps from the app store... XDA is a huge community - but not representative for all the millions of smartphone users worldwide. The problems that HTC is facing are of course the rise of Samsung in the market and a missing response to it. But much worser: Samsung most likely will make a deal with Apple regarding licenses. This probably will leave HTC standing in the rain. Let's see if they will innovate something new. If Apple starts going to sue them, too, it probably will become hard. But who knows - there's also Google... I'm not too sure if they will focus on Samsung for Android hardware as they're already handicapped.
Let's see how it goes...
optimusodd said:
Doh!It is so sad to see all this happening.It is really a sad scenario to see these buddies going through this.I can feel their pain and frustration.HTCdev sucks!!!
Unlocking via HTCdev is completely Bull****…..Getting ROOT without S-OFF is like listening to porn on the Radiops!
I am so sad for HTC. http://www.eweek.com/c/a/Mobile-and...attle-Looks-to-Windows-Phone-8-Report-441483/
I have been loyal to HTC right from HTC Touch.I adore HTC devices.It is absolutely beyond my comprehension how the company like HTC (the pioneer of smartphones) that produced such outstanding devices would self-destruct like this.They are axing their own feet.
HTC is losing a battle to Samsung coz they have refused to embrace the consumers.Samsung has already released the source codes of their kernels and allows Bootloader unlocking and S-OFF’ing on their devices.Maybe Samsung sucks at coding bootloader protection lol.Whatever!
If HTC don’t assist developers in unlocking bootloaders and S-Off’ing for HTC devices,it will just drive away customers who like to root or tinker with their phones as more and more people want to have complete control over their phone.
May God bless HTCdev!!If they don’t change their policy,I am gonna say adios to HTC and “Hola!Samsung!”
Click to expand...
Click to collapse
Indeed, the reason I didn't get another HTC phone is because I don't want jump through hoops in order to unlock, when on my Nexus I can just do "fastboot oem unlock"
Sent from my Galaxy Nexus using xda premium
eventcom said:
Like you said you should be able to use revolutionary. In this case most likely a solution could only be found if you're more specific what exactly you've done and what responses (confirmations and errors) you got and at which point.
First of all: did you use a guide from this forum? - if yes: which one?
BTW: the place you posted this is absolutely perfect
Click to expand...
Click to collapse
optimusodd said:
I would suggest you to try Revolutionary following this guide.
kgs tool can solve zerg root failed error but I am not sure if that also works with Wildfire.
You can confirm that on kgs1992's thread.
Please confirm that before doing anything.
Click to expand...
Click to collapse
firstly thanks for replying so fast.
Revolutionary tool gives me this error.. Zergig root this might takes few minute or so.. Failed to get root
Unlockroot.com gives me error like this- Failed to get shell root..
i used also unrevoked3 almost succeeded actually phone booted but at the end it gave me error.. now its saying Device is not supported since i updated my rom i guess.. so can anyone tell me is there any way root/s-off my phone? im so puzzled right now...
@optimusodd i followed that guide you mentioned exactly every step... i managed to downgrade my HBOOT from 0.2 to 0.1.. but i stuck at Revolutionary part.,, idont think its my computer because i tried on my notebook also..
optimusodd said:
I would suggest you to try Revolutionary following this guide.
kgs tool can solve zerg root failed error but I am not sure if that also works with Wildfire.
You can confirm that on kgs1992's thread.
Please confirm that before doing anything.
Click to expand...
Click to collapse
Holy **** it worked..!! thanks dude.. i want to buy beer for you.. !!! i confirm that KGS tool works on HTC wildfire.. thanks everyone..
stx3 said:
Holy **** it worked..!! thanks dude.. i want to buy beer for you.. !!!i confirm that KGS tool works on HTC wildfire.. thanks everyone..
Click to expand...
Click to collapse
Hahaha,Have you achieved S-OFF ?If yes,I am glad it worked out for you.
Revolutionary tool gives me this error.. Zergig root this might takes few minute or so.. Failed to get root Unlockroot.com gives me error like this- Failed to get shell root..i used also unrevoked3 almost succeeded actually phone booted but at the end it gave me error.. now its saying Device is not supported since i updated my rom i guess.. so can anyone tell me is there any way root/s-off my phone?
Click to expand...
Click to collapse
One thing I didn't get that what made you run Unrevoked when you had got stucked at Revolutionary.
Yes i managed to s-off and rooted my device and installed cyanogen mod.. So happy...
tnx to this forum.. It is so fast and efficent way to.communicate.. :thumbup:
Your advice was gold man..
Sent from my GT-N7000 using xda app-developers app
stx3 said:
Yes i managed to s-off and rooted my device and installed cyanogen mod.. So happy...
tnx to this forum.. It is so fast and efficent way to.communicate.. :thumbup:
Your advice was gold man.. Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
YAMW,Cheers!!!:good:
Hey guys, I recently purchased a HTC One X and have a few questions that I need clarified. I've done my research already but couldn't find much, so I hope it's OK for me to ask it here.
First of all, apparently there's no method to achieve S-OFF and SuperCID on the international HTC One X running Tegra 3, is that correct?
Secondly, some people reported their HTC One X having lags on the home screen, and were able to fix it (I think temporarily) using the "LagFix (fstrim)" tool. My question is, is that a hardware problem in the HTC One X, where I'll eventually have to get it replaced? Because this seemed like the eMMC bug on the Nexus devices, because of a bad chip or something. They eventually had to get it replaced, and the fixes available were only temporarily, they only slowed down the lag deterioration but they didn't fix the problem completely. I'm wondering if this is the same for our HTC One X?
And finally, say if I have an older HBOOT, will it be fine if I simply update to a newer HBOOT? Would I require SuperCID to do that or can I simply update it without any prerequisites?
Thanks.
chaoscreater said:
Hey guys, I recently purchased a HTC One X and have a few questions that I need clarified. I've done my research already but couldn't find much, so I hope it's OK for me to ask it here.
First of all, apparently there's no method to achieve S-OFF and SuperCID on the international HTC One X running Tegra 3, is that correct?
Secondly, some people reported their HTC One X having lags on the home screen, and were able to fix it (I think temporarily) using the "LagFix (fstrim)" tool. My question is, is that a hardware problem in the HTC One X, where I'll eventually have to get it replaced? Because this seemed like the eMMC bug on the Nexus devices, because of a bad chip or something. They eventually had to get it replaced, and the fixes available were only temporarily, they only slowed down the lag deterioration but they didn't fix the problem completely. I'm wondering if this is the same for our HTC One X?
And finally, say if I have an older HBOOT, will it be fine if I simply update to a newer HBOOT? Would I require SuperCID to do that or can I simply update it without any prerequisites?
Thanks.
Click to expand...
Click to collapse
1. No method to achieve S-OFF and SuperCID!
2. No it's not hardware problem on the HOX!
3. No you don't need S-OFF to upgrade your HBOOT!
All this question is answеred in other treads! Use search function
Just to clarify, does that mean I cannot use SuperCID and S-off to change my endeavoru HOX to S-off? If I remember correctly, originally my phone is on S-off. But I flashed a wrong kernel which belong to ICS version and somehow it change itself to S-on.
chaoscreater said:
Hey guys, I recently purchased a HTC One X and have a few questions that I need clarified. I've done my research already but couldn't find much, so I hope it's OK for me to ask it here.
First of all, apparently there's no method to achieve S-OFF and SuperCID on the international HTC One X running Tegra 3, is that correct?
Secondly, some people reported their HTC One X having lags on the home screen, and were able to fix it (I think temporarily) using the "LagFix (fstrim)" tool. My question is, is that a hardware problem in the HTC One X, where I'll eventually have to get it replaced? Because this seemed like the eMMC bug on the Nexus devices, because of a bad chip or something. They eventually had to get it replaced, and the fixes available were only temporarily, they only slowed down the lag deterioration but they didn't fix the problem completely. I'm wondering if this is the same for our HTC One X?
And finally, say if I have an older HBOOT, will it be fine if I simply update to a newer HBOOT? Would I require SuperCID to do that or can I simply update it without any prerequisites?
Thanks.
Click to expand...
Click to collapse
The lagfix is to correct a similar problem to the Nexus where the controller is not TRIM-ing properly (or at all). If you transfer and delete tons of stuff on a regular basis it will drop the performance. It doesn't damage the NAND however. There are more than enough read/write cycles in it's lifetime to lagfix it every now and again and still use it for years. Personally i've never had to use lagfix but I always leave slack space.
As for your hboot...you can upgrade hboot without S-Off no problem PROVIDED there is an hboot compatible with your CID.
ronaldtzh said:
Just to clarify, does that mean I cannot use SuperCID and S-off to change my endeavoru HOX to S-off? If I remember correctly, originally my phone is on S-off. But I flashed a wrong kernel which belong to ICS version and somehow it change itself to S-on.
Click to expand...
Click to collapse
There is NO SupedCID or S-Off method for the HOX. None.
You can buy it that way and that is IT.
I have also NEVER heard of any time an S-Off device has been switched to S-On by flashing a kernel or anything else. It has nothing at all whatsoever to do with kernel or ROM so flashing one would NOT change security.