Related
I don't really know too much about root, but I'm wondering how things will work when root is widespread. Will we always have to rely on devs for every future android upgrade or something?
do some research!
rocketpaul said:
do some research!
Click to expand...
Click to collapse
I'd assume no, except for perhaps the first one, but I haven't seen it explicitly stated anywhere.
The short version is that there's userland root access. That pretty much means that the what's on the device can be modified, like apps removed etc but afaik there's no bootloader access yet which would be necessary for flashing custom images.
Root will make cracking the bootloader easier though so it's a major step on the way.
Octanum said:
I don't really know too much about root, but I'm wondering how things will work when root is widespread. Will we always have to rely on devs for every future android upgrade or something?
Click to expand...
Click to collapse
If its anything like the HTC Dream I had before my Sony X10, the root is a process that keeps your phone rooted. Unless you revert back to the original software, you should never lose it. As for the OS, there usually will be people developing custom ROM's for quite a while on this phone but essentially on that part, yes it does depend on the devs.
Hi i have a uk x10i thinking of rooting it
q1. will rooting enable me to install any android fw
q2. are there any custom x10i fw out yet
q3. what about andorid 2.2 on the x10i
thanks
raysmobile said:
Hi i have a uk x10i thinking of rooting it
q1. will rooting enable me to install any android fw
q2. are there any custom x10i fw out yet
q3. what about andorid 2.2 on the x10i
thanks
Click to expand...
Click to collapse
q1. No, it allows you to run certain apps but not to flash custom ROMs.
q2. No
q3. After 2.1, that's all we know currently.
That being said, there's lots of work being put into cracking the bootloader. With any luck we'll have that done in a few months, perhaps even less. It's not entirely unreasonable to hope for and even expect custom ROMs before the end of the year considering how skilled and hard-working the guys cracking it are.
ddewbofh said:
q1. No, it allows you to run certain apps but not to flash custom ROMs.
q2. No
q3. After 2.1, that's all we know currently.
That being said, there's lots of work being put into cracking the bootloader. With any luck we'll have that done in a few months, perhaps even less. It's not entirely unreasonable to hope for and even expect custom ROMs before the end of the year considering how skilled and hard-working the guys cracking it are.
Click to expand...
Click to collapse
I want to know more about Q2. Like can I run Flash and Apps which support 2.0+ ?
Anandc said:
I want to know more about Q2. Like can I run Flash and Apps which support 2.0+ ?
Click to expand...
Click to collapse
With root? No. You still need a 2.0+ firmware to do that, that's why everyone's so anxious over the update to 2.1 coming in Q3.
i've still not used the OTA froyo on my X. It doesn't appear there are any drawbacks since most developers have abandoned the X. Are there any drawbacks to using froyo OTA?
You will loose root
twon23 said:
You will loose root
Click to expand...
Click to collapse
Yes, you will lose it.. but you can reroot no problem. There is no reason not to update to the latest OTA
There doesn't seem to be any reason to stay on the 2.2 leak because no developers are working on cracking the bootloader or making roms from the 2.1/2.2-leak days. Everyone is working against the 2.2 OTA/SBF.
I have been wondering the same thing. Until now, there has been no reason to do the OTA.
This is in no way a flame on Team Black Hat, but I was concerned that in the last 2.2.1 release, TBH decided to include the bootloader 10.04. (I am guessing they did it for a good reason). Then they built a Tranq. ROM specificly for that release. No 10.04 bootloader, no ROM.
I am still having a hard time voluntarily giving up the 10.01 bootloader which does not need the signature keys. But I guess there is no longer much choice.
i wanted to understand (and let everyone understand) the froyo wildfire bootloader and its other security details, so that someone will root the wildfire finally. Everything needs to be done by sharing the security loop holes of wildfire.
its not an easy task. but i dont really wanted to wait further for rooting.
any suggestions, comments and complements are widely accepted.
everyone who wants to root wildfire share ur information here.
whatever the information u know, post it here
lets get it done.
No offense, but, this is such a pointless thread. Why don't you start by telling us what all you know about the new Bootloader? (Technicalities). If it were so easy, I am sure someone would have done it already.
I'm a newbie and will learn to do that. I posted this thread to share information of wildfire bootloader. If everyone shares whatever he knows, then I'm sure that finally someone roots it. That's the beauty of sharing and unrevealing things. I believe the persons who root and develop apps are also once new bies. So I would like people to support this thread. There s nothing that can be undone. Only its a matter of time. So try to share.
Sent from my HTC Wildfire using XDA App
Moved to general.
I agree that sharing information is vital to accomplishing mutual goals but asking people for general info about the bootloader or general advice about the root process is not development...hence I moved the topic to general.
Good luck and I hope you are able to learn enough to achieve your goal...that's what XDA is all about.
krook6023 (mod team)
a little bit of help maybe
there are two things that we can aim to achieve root on our widlfires . .
1. downgrade the Hboot to rootable versions (1.01 to 0.80 for eg) reported successful in another htc device in which i don't remember what it was
2. try to achieve root with the 1.01 Hboot instead (which seems to be harder )
do not ask me about the technicalities of this options as i am no developer like i said, just trying to help
yes downgrading wildfire HBOOT 1.01 to 0.80 will make rooting easier, but there is a more chance of bricking.
i remember the other phone which downgraded HBOOT was desire z. watch out this link,
http://forum.xda-developers.com/showthread.php?t=905261
in that process, observe the path
/data/local/tmp/misc_version -s 1.33.405.5
someone said this on xda,
I own a HTC Desire Z, and I have downgraded my software including Hboot using this method .
I have tried the same thing on my girlfriend wildfire and I managed to obtain temporary root, but when I tried to change "misc_version" to 1.24.405.1 I got this error:
Code:
# /data/local/tmp/misc_version -s 1.24.405.1
--set_version set. VERSION will be changed to: 1.24.405.1
Patching and backing up partition 17...
Error opening input file.
I know that this files are specific for Desire Z, psneuter worked only after I have downloaded from somewhere else (I don't remember where), but maybe someone will manage to edit "misc_version" and make it work on wildfire, then it will be possible to downgrade everything including H-boot.
so if we r working on downgrading the HBOOT, then our target will be to change the version of the "misc_version" to 1.24.405.1
i would prefer to work on downgrading the HBOOT rather than rooting the newer HBOOT. because, if once we have successfully downgraded the HBOOT, we can root, then unroot, then re-root anytime without any limitations.
Lol, its not a problem of patching the HBOOT. The problem is, overwriting the current HBOOT with a patched one. That requires a vulnerability/exploit, which are generally hard to find.
edit: posted this without fully reading the thread, i see you're looking at downgrading as well. what i said is still valid though.
tell me about exploit / vulnerability
hey are u sure it is not an issue of patching HBOOT. is it only the issue with overwriting the original HBOOT with a patched one. pls reply
and what is meant by vulnerability or exploit in this process. pls describe it.
on march 18th 2011, unrevoked released source for an exploit (zysploit exploit) in 2.2 using github. im giving u the link of it here.
https://github.com/unrevoked/zysploit
the download link of zysploit here:
https://github.com/unrevoked/zysploit/archives/master
im also trying to attach the files. and tell me if that zysploit helps us anyway.
hoping to hear.
bharatgaddameedi said:
hey are u sure it is not an issue of patching HBOOT. is it only the issue with overwriting the original HBOOT with a patched one. pls reply
and what is meant by vulnerability or exploit in this process. pls describe it.
on march 18th 2011, unrevoked released source for an exploit (zysploit exploit) in 2.2 using github. im giving u the link of it here.
https://github.com/unrevoked/zysploit
the download link of zysploit here:
https://github.com/unrevoked/zysploit/archives/master
im also trying to attach the files. and tell me if that zysploit helps us anyway.
hoping to hear.
Click to expand...
Click to collapse
Yes I'm sure about patching HBOOT. I'm currently using a patched 1.01.1000 HBOOT S-OFF. You should really know what a vulnerability/exploit is before getting into this stuff. Google is your friend. You can't go from total noob to HBOOT exploiter directly.
AFAIK zysploit does not help if your bootloader is completely locked down.
edit: oh and i didnt mean that you ARE a total noob, i said that because you were saying everyone was a noob at some point (which is true, but there IS a learning curve)
im sorry for going into the details of u. but pls let me know this.
i have seen ur phone details on this thread like below.
Phone: HTC Wildfire
HBOOT - AlphaRev 1.01.1000 S-OFF
Recovery - Clockworkmod 3.0.2.4
Radio: 13.55.55.24H_3.35.20.10
ROM: [2.3.3] Locally built CyanogenMod 7 with Darktremor Apps2SD
SDCard: SanDisk 4GB Class 4 (512MB EXT).
urs HBOOT is 1.01 and is S-OFF. and then there is alpharev, which works with rooted phones.
i dont understand really, how a HBOOT 1.01 with S-OFF is rooted and then alpharev is made used. i have seen some others peoples phone details to be exactly like this.
have u used xtc clip to make S-OFF. if it is so, then i heard that u must downgrade to the HBOOT 0.80 to make the phone rooted. also heard that alpha rev is not yet compatible with wildfire. let me know something if u r willing to share.
and google search for exploit gives irrelated data. do u know any specific link to learn about exploits.
bharatgaddameedi said:
im sorry for going into the details of u. but pls let me know this.
i have seen ur phone details on this thread like below.
Phone: HTC Wildfire
HBOOT - AlphaRev 1.01.1000 S-OFF
Recovery - Clockworkmod 3.0.2.4
Radio: 13.55.55.24H_3.35.20.10
ROM: [2.3.3] Locally built CyanogenMod 7 with Darktremor Apps2SD
SDCard: SanDisk 4GB Class 4 (512MB EXT).
urs HBOOT is 1.01 and is S-OFF. and then there is alpharev, which works with rooted phones.
i dont understand really, how a HBOOT 1.01 with S-OFF is rooted and then alpharev is made used. i have seen some others peoples phone details to be exactly like this.
have u used xtc clip to make S-OFF. if it is so, then i heard that u must downgrade to the HBOOT 0.80 to make the phone rooted. also heard that alpha rev is not yet compatible with wildfire. let me know something if u r willing to share.
and google search for exploit gives irrelated data. do u know any specific link to learn about exploits.
Click to expand...
Click to collapse
The patched HBOOT by AlphaRev is v1.01.1000. However, stock 1.01.1000 CANNOT be replaced by any known methods. AlphaRev replaced my stock 0.80.0002 with their 1.01.1000 PATCHED HBOOT. No, I have NOT used an XTC Clip. And no, only people who have no clue what s-off is would downgrade to 0.80.x to root after s-off. When you're s-off, fastboot lets you flash a custom recovery, which lets you flash a rooted ROM. Done.
A test version of AlphaRev has existed for ages for Wildfire. Just not released, though it should be released soon.
About exploits: http://tinyurl.com/bwqgkp
See the first link.
hboot versions
As far as now we have 3 versions of hboot. Making a note of them below along with the associated radio (in official roms)
1st version: hboot 0.80.0002 and Radio_13.45.55.24H_3.35.15.31 (at the time of phone manufacture)
2nd version: hboot 0.80.0007 and Radio_13.53.55.24H_3.35.19.25 (in august or later)
3rd version: hboot 1.01.0002 and Radio_13.55.55.24H_3.35.20.10 (came with froyo update in december 2010 or later)
Based on different regions, the hboot may slightly vary in the last number like 0.80.0002 and 0.80.0003
So, remember that. And the above versions are for ASIA---INDIA.
here it says that wildfire has temp root - http://unrevoked.com/rootwiki/doku.php/public/root_friendly - does anyone now how to temp root and is it then possible to install custom roms via rom manager? Thanks.
Aca902 said:
here it says that wildfire has temp root - http://unrevoked.com/rootwiki/doku.php/public/root_friendly - does anyone now how to temp root and is it then possible to install custom roms via rom manager? Thanks.
Click to expand...
Click to collapse
that link doesnt mean that wildfire now has temporary root.
that link means that wildfire with 2.1 can be rooted whereas wildfire with 2.2 is in a temporary unrootable stage, which will be rooted in future. same applies to htc aria. watch out there is "temporary" even to aria also.
htc aria got updated to official froyo in feb 2011, and like wildfire, aria is also yet to be rooted.
so presently wildfire and aria are the phones eagerly waiting to get rooted.
and i wanted to mention something about htc legend.
this htc legend (unlike wildfire and aria), got rooted in a very short time.
htc legend and htc wildfire both got updated to official froyo almost at the same time. but in the 1st week of jan 2011, legend got root access. legend devs managed to downgrade from official froyo to rooted hboot 1.01 eclair. its there in the legend forums. maybe it can help someone to understand wildfire rooting. link: http://forum.xda-developers.com/showthread.php?t=894465
wildfire with 2.1 (older hboot) is rooted by some processes like unrevoked, paulO'Brien process, and etc.
now can we expect those teams to release the source code of those processes.
once if it is done, i think rooting will be made opensource just like android operating system. almost every android phone will be rooted and great android development follows. what do u say
bharatgaddameedi said:
joined xda in nov 2010. dont even know how to create a thread. remained passive.
created my first thread on 10th april 2011. now exploring xda. would like to simply say that xda is an ocean with immense of knowledge. suggesting everyone to explore.
irrelative matter, sorry for that.
now coming to the point of rooting wildfire.
wildfire with 2.1 is rooted by some processes like unrevoked, paulO'Brien process, and etc.
now can we expect those teams to release the source code of those processes.
once if it is done, i think rooting will be made opensource just like android operating system. almost every android phone will be rooted and great android development follows. what do u say
Click to expand...
Click to collapse
here's what i think: you should read. all of your questions are answered somewhere or the other already. source code of NAND exploits WILL NOT be released, because that would enable HTC to patch the vulnerability, which they have already done anyway. and, these exploits only apply to HTC bootloaders, not all android phones. meh. each manufacturer -if they choose to do so- locks their bootloader IN THEIR OWN way.
bharatgaddameedi said:
now coming to the point of rooting wildfire.
wildfire with 2.1 is rooted by some processes like unrevoked, paulO'Brien process, and etc.
now can we expect those teams to release the source code of those processes.
once if it is done, i think rooting will be made opensource just like android operating system. almost every android phone will be rooted and great android development follows. what do u say
Click to expand...
Click to collapse
If the source code of those exploits are released, HTC will patch it up with an updated bootloader, like they did with the HBOOT that came with OTA Froyo update. Plus, every manufacturer have different bootloaders on their phones. For example, exploits that work on HTC's bootloaders don't work on others. Same goes for rooting, different phones require different method of doing it.
The reason why it's almost impossible to root is that the manufacturer, in this case, HTC, decided to lock the bootloader. That's what I say.
TL;DU The exploit used to root that worked with Eclair (HBOOT 0.8) doesn't work with Froyo (HBOOT 1.01) anymore because HTC patched it.
doomed151 said:
If the source code of those exploits are released, HTC will patch it up with an updated bootloader, like they did with the HBOOT that came with OTA Froyo update. Plus, every manufacturer have different bootloaders on their phones. For example, exploits that work on HTC's bootloaders don't work on others. Same goes for rooting, different phones require different method of doing it.
The reason why it's almost impossible to root is that the manufacturer, in this case, HTC, decided to lock the bootloader. That's what I say.
TL;DU The exploit used to root that worked with Eclair (HBOOT 0.8) doesn't work with Froyo (HBOOT 1.01) anymore because HTC patched it.
Click to expand...
Click to collapse
Right. Im aware that if source code of a rooting process is revealed, HTC will patch it and make it won't work.
im aware just changing a version of bootloader by htc will not make any rooting process stop work, unless they have patched the previous exploits.
but my way of thinking here is completely different.
Let them further patch their bootloaders. But, tell me who is going to make a second official update. I, personally won't make any other official update. and at this point of time, i dont think any wildfire user, who is eagerly waiting to get the phone rooted, will make a 2nd official update. even after waiting for 4months just to get rooted, if a wildfire user makes a 2nd official update, then i dont know what to call him/her.
its pretty clear that wildfire users willing to get rooted will not make any other official updates. and those who are not willing to get rooted (at this point of time) will continue to make updates, and get their bootloader locked up, of which i expect no one bothers.
but i wanted to know if it is the same exploit that roots different htc phone models.
if the same exploit is rooting different htc phones, then my arguement to reveal the source code makes no sense. i agree and i give up.
but the exploits for rooting different htc devices are different, then my arguement to reveal the source code makes some sense.
i think htc HBOOT also has source code. what if some unloyal member of htc reveals the source code, so that it becomes easy to root.
bharatgaddameedi said:
Right. I knew that if source code of a rooting process is revealed, HTC will patch it and make it won't work.
i knew just changing a version of bootloader by htc will not make any rooting process stop work, unless they have patched the previous exploits.
but my way of thinking here is completely different.
Let them further patch their bootloaders. But, tell me who is going to make a second official update. I, personally won't make any other official update. and at this point of time, i dont think any wildfire user, who is eagerly waiting to get the phone rooted, will make a 2nd official update. even after waiting for 4months just to get rooted, if a wildfire user makes a 2nd official update, then i dont know what to call him/her.
its pretty clear that wildfire users willing to get rooted will not make any other official updates. and those who are not willing to get rooted (at this point of time) will continue to make updates, and get their bootloader locked up, of which i expect no one bothers.
but i wanted to know if it is the same exploit that roots different htc phone models.
if the same exploit is rooting different htc phones, then my arguement to reveal the source code makes no sense. i agree and i give up.
but the exploits for rooting different htc devices are different, then my arguement to reveal the source code makes some sense.
i think htc HBOOT also has source code. what if some unloyal member of htc reveals the source code, so that it becomes easy to root.
Click to expand...
Click to collapse
wow you really have no clue do you? the HBOOT can be easily disassembled using any disassembler. people have gone through it and found that the old hole/weakness is NO LONGER THERE. If there's no weak point, what will they attack? even with the source code they can't do anything.
nhnt11 said:
wow you really have no clue do you? the HBOOT can be easily disassembled using any disassembler. people have gone through it and found that the old hole/weakness is NO LONGER THERE. If there's no weak point, what will they attack? even with the source code they can't do anything.
Click to expand...
Click to collapse
Yes u r right about me. I thought that the source code will atleast tell us the way of approach of the process. So here u tell me that the way of approaches to root via 2 different exploits is completely different. So everytime the HBOOT gets patched, then we should seek a complete different way to exploit it. Am I correct.
Hi,
Just wanted to see how much interest is there in getting S-OFF for our HTC One phones. I personally could use this for testing Tmobile radios on the HTC Dev Edition phones. What are some of your interest and thoughts about S-Off. Most importantly, why is it important to you?
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
ArmedandDangerous said:
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
Click to expand...
Click to collapse
Could you please educate me more about the HoX? Thanks
Becool0130 said:
Could you please educate me more about the HoX? Thanks
Click to expand...
Click to collapse
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Not sure about the Tegra3 version of the HOX, but the S3 version of the HOX has achieved S-OFF for awhile now. There is definitely interest in ALL HTC devices to achieve S-OFF. Just a matter of time before devs crack the code.
getting the Tmobile AWS radio to work on the dev version would be my top interest
illestfob said:
getting the Tmobile AWS radio to work on the dev version would be my top interest
Click to expand...
Click to collapse
Don't hold your breath, I doubt this will work.
BenPope said:
Don't hold your breath, I doubt this will work.
Click to expand...
Click to collapse
its a slight crap shoot, but i live in a refarmed area so it should be liveable until LTE gets turned on.
I usually restrict my current phone (G2) to only edge anyway to conserve battery life
I think the problem with the HTC One X was the fact that it was Tegra and not Qualcomm - most of the major players in s-off work with Qualcomm chips. I remember when I had the One X about a year ago - rumour had it that the likes of revolutionary didn't want to work with Tegra hardware.
Things might be better for the One.
Out of interest did the One S get s-off?
Well with big devs getting it like Steve Kondik (CM) Koushik Dutta (CWM) etc I think the dev support will be strong on this one
ArmedandDangerous said:
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Click to expand...
Click to collapse
Thanks for the education man! I really think we can get this one done though because it's from Qualcomm as opposed to Tegra right?
Anyways, s-off is extremely important for warranty purposes I see Guess I should return my developer edition back right?
BenPope said:
Don't hold your breath, I doubt this will work.
Click to expand...
Click to collapse
Why is this? I actually bought the developer phone for the sole purpose of this working on TMobile network 1700 3G. I'm not refarmed to 1900 yet which means Edge speeds -_-. Gotta give us some hope! Lol
huwwatkins said:
I think the problem with the HTC One X was the fact that it was Tegra and not Qualcomm - most of the major players in s-off work with Qualcomm chips. I remember when I had the One X about a year ago - rumour had it that the likes of revolutionary didn't want to work with Tegra hardware.
Things might be better for the One.
Out of interest did the One S get s-off?
Click to expand...
Click to collapse
Good point! Qualcomm does seem fairly easy to hack with all the s3 and soon s4 out.
Sent from my SGH-T959 using xda app-developers app
ArmedandDangerous said:
Most HTC devices now are S-On (at least the recently released ones from 2011-2013). What they do have though is an unlocked bootloader. That means you can install a custom recovery like CWRM or TWRP, and you can flash kernels through Fastboot. S-Off gives the ability to flash kernels from within the recovery (Fastboot requires a USB cable and a computer) and also the ability to flash radios.
With the HoX (HTC One X, and all phones unlocked through HTCDEV), when you unlock your bootloader it will say UNLOCKED (as opposed to Locked when stock). Relocking the bootloader will say RE-LOCKED, but not LOCKED. This means HTC can see that you have unlocked the bootloader and they can, and depending on luck, wil reject your warranty claim.
With S-Off we can overwrite the HBOOT and downgrade to an older version where it still says LOCKED, send that back for warranty and all will be well
Click to expand...
Click to collapse
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
nugzo said:
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
Click to expand...
Click to collapse
I was mostly referring to the HoX, as mine is the Tegra one, and there is no workaround to flashing kernels or radios without ADB But yes I did read that on the One, it can be done through recovery although S-On. Would still love S-Off though for HBOOT downgrading
ArmedandDangerous said:
I was mostly referring to the HoX, as mine is the Tegra one, and there is no workaround to flashing kernels or radios without ADB But yes I did read that on the One, it can be done through recovery although S-On. Would still love S-Off though for HBOOT downgrading
Click to expand...
Click to collapse
Yes i totally agree. S-off is what we all want. Just not as important as it once was.. :fingers-crossed: we'll get it. I'd even make a bet that we have it in less than 60 days from now I did see somewhere that there is a suprcid method being worked on also.. That would be great as well :good:
nugzo said:
Yes i totally agree. S-off is what we all want. Just not as important as it once was.. :fingers-crossed: we'll get it. I'd even make a bet that we have it in less than 60 days from now I did see somewhere that there is a suprcid method being worked on also.. That would be great as well :good:
Click to expand...
Click to collapse
Just in time for me to wait out supply and batch issues from my telco, should start being available in early to mid May
First Android device I haven't rooted due to the Warranty issues with HTC ( How they are a right pain somtimes! ). Once S-OFF becomes available I will happily go ahead and unlock my boot loader etc. For now everything is fine without root
also would like super cid or S-off even better. to flash other region roms. INT RUUs etc . and we all know how ATT likes to software update HBOOT versions and no way to downgrade without S-OFF
nugzo said:
Dont need s-off for Radios or flashing kernels through recovery. There is a work around for all of that. We can change radios and flash kernels through recovery on this HTC One. The Renovate rom says the kernel is flashed with the rom install. You can install radios by installing radio to different partition then symlink to the new radio. Turge will be posting more about it soon. For now here is the thread where i tested this for him. http://forum.xda-developers.com/showthread.php?t=2243159 So we should be able to test the tmobile radio soon enough.
And yeah it's the tegra devices that are having the hardest time with s-off. The ATT One X (qualcom) THe DNA are both s-off. Since this is also qualcom, i have high hopes for s-off soon. Although it is not as important as it once was.
Click to expand...
Click to collapse
Ha! There is hope to flashing radios without S-OFF. I wonder if we can get a developer to try to get T-Mobile radios and flash them over to our Developer Edition phones. Meh, essentially they are ATT Htc Ones without restrictions
daddioj said:
also would like super cid or S-off even better. to flash other region roms. INT RUUs etc . and we all know how ATT likes to software update HBOOT versions and no way to downgrade without S-OFF
Click to expand...
Click to collapse
+1
BTW, I'm very curious what the cid is for the dev model.
Sent from my HTC One X+ using xda app-developers app
ArmedandDangerous said:
Interest? Sure. Able to do it? No idea. The HoX is still locked up tight. And for most people, S-Off would just mean easier to flash kernels, ability to flash radios and downgrade HBOOT so that it says LOCKED instead of RELOCKED for warranty purposes.
Click to expand...
Click to collapse
That's not exactly true. Downgrading hboot will still be relocked. There is a "lock status flag" that must be reset in order to become locked again.
S off does remove write protection on mmcblk0p3 where the lock flag lives,allowing the user to reset it and become locked again. User S_trace initially figured out what was going on and posted a flashable zip file. We have modded the zip(removed the device check) and i have threads in several forums,titled [how to]reset your lock status flag if you'd like a little more info/detail. The flag thus far has been the same in all s3 and all dual/quad core s4 devices.
The fact that the radio partition is currently writeable from recovery,is likely a fluke that will be "fixed" with newer hboots,so I'd advise those of you that like this feature to not update
Even tho the radio itself can be chanaged,other firmware cannot. Thus the newer radios may not be optimized with the older firmware remaining on the phone.(read: the new radios may not be working as good as you think they are)
My personal interest in s off is to change cid,and eliminate the security checks that prevent other carrier/regional ruus from flashing,and from going backwards in firmware. I also like to change the splash image
I cannot truly enjoy an s on device,and won't get one unless some means of s off becomes available.
Sent from my HTC PG09410 using xda app-developers app