Need to flash boot.img after HTC Dev Unlock - HTC Desire S

Yesterday, I was given a Wildfire S to put on a custom ROM. It was actually my younger sister's and while she was perfectly happy with it performance wise, the internal memory's a joke - some 150 MB!!
So i promptly proceeded to amaze her with the flamboyant show of HTC Dev unlock, followed by rooting and CWM recovery. Then i downloaded a ROM with A2SD built in, placed it on the sd card, partitioned the sd card to support an A2SD partition and a linux swap partition, and flashed the zip after a full wipe. After flashing the new ROM, i was all but ready to flash boot.img from fastboot, i decided to scare her by trying to boot without that and get the phone to hang on the splash screen, then extort a treat from her to get it to boot!!
That's when it hit me in the nuts. It booted! So i attributed it to the ROM being a Sense ROM, able to run on the stock kernel - so i went and checked the phone info - and there it was - a custom kernel!! The same that was included in the ROM zip.
This got me thinking - is it only us that have to flash the boot.img separately? Why can the WFS guys flash custom kernels from recovery itself? I thought the HTC Dev Unlock method prevents you from writing to the boot partition??!!
Maybe Tectas can shed some light on this - I see you're also a WFS guy. Any thoughts on this guys?
EDIT : I'm so sorry this got posted in the Themes and Apps section. Have requested it be moved to the General Section. Goofed up with the tabs on my browser and ended up creating this thread in the wrong section. Sorry guys!!

Was it S-on?
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC

suku_patel_22 said:
Was it S-on?
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
Click to expand...
Click to collapse
Yes - stock S-On to begin with.
And then HTC Dev Unlocked

That's strange then
did you use 4ext?
Edit: saw you already mentioned cwm
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC

suku_patel_22 said:
That's strange then
did you use 4ext?
Edit: saw you already mentioned cwm
Swyped from my Desire S waiting for Kernel 3, WAKE UP HTC
Click to expand...
Click to collapse
I would have used 4EXT in the blink of an eye - problem is, 4EXT doesn't support the Wildfire S currently. The currently supported devices are : HTC Sensation / XE, Incredible S / 2, Desire Z / G2, Desire S, Desire, Desire HD, Inspire 4G, myTouch 4G, Nexus One, Thunderbolt, Evo 3D GSM / CDMA, Amaze
Back to topic : anyone else used any other HTCDev Unlocked device who can flash kernels from recovery?

I'm more or less a wfs guy^^
My gf got one and i take care of their index thread, but i'm pretty less active there since my 2. girly was born.
Also hers is xtc s-offed, because there was no htcdev unlock when she got it and she doesn't let me play that much with it.
I wonder that it was flashed from cwm directly without fastboot, but there are 2 possibilities coming to my mind how this could be possible.
1. Their cwm is an unofficial implementation made by alquez as far as i know, could be that he already made what madmaxx is atm working on.
2. Because the wfs isn't a popular device and they even needed a petition to get at least the htcdev method to unlock their bootloader aside from xtc (for sure only at gsm devices, the wcdma wfs has other possibilies to unlock), htc could have given them a little goody and removed the /boot restriction for recovery.
No matter which case fits, there are many devices needing to flash the boot.img when htcdev was used (i.e. the htc one x also has this restriction at recovery).

Tectas said:
I'm more or less a wfs guy^^
My gf got one and i take care of their index thread, but i'm pretty less active there since my 2. girly was born.
Also hers is xtc s-offed, because there was no htcdev unlock when she got it and she doesn't let me play that much with it.
I wonder that it was flashed from cwm directly without fastboot, but there are 2 possibilities coming to my mind how this could be possible.
1. Their cwm is an unofficial implementation made by alquez as far as i know, could be that he already made what madmaxx is atm working on.
2. Because the wfs isn't a popular device and they even needed a petition to get at least the htcdev method to unlock their bootloader aside from xtc (for sure only at gsm devices, the wcdma wfs has other possibilies to unlock), htc could have given them a little goody and removed the /boot restriction for recovery.
No matter which case fits, there are many devices needing to flash the boot.img when htcdev was used (i.e. the htc one x also has this restriction at recovery).
Click to expand...
Click to collapse
That's the thing... the CWM recovery I used was downloaded and flashed using ROM Manager... so it's the original one by koush. I really don't see why HTC would do something like give the WFS an unlocked boot while deny it on other devices....? There must be something else to it.
The last thing I am willing to believe is that HTC took pity on the WFS owners and did this as a kind gesture. HTC is a corporation - a device manufacturing machine.... and just like any other, it may be good at what it does, but it does not have a heart. None of them does.

enigmaamit said:
That's the thing... the CWM recovery I used was downloaded and flashed using ROM Manager... so it's the original one by koush. I really don't see why HTC would do something like give the WFS an unlocked boot while deny it on other devices....? There must be something else to it.
The last thing I am willing to believe is that HTC took pity on the WFS owners and did this as a kind gesture. HTC is a corporation - a device manufacturing machine.... and just like any other, it may be good at what it does, but it does not have a heart. None of them does.
Click to expand...
Click to collapse
Could for sure be something else behind it.
Never wanted to say they would have done it as a kind gesture (i totaly agree that such a corporation got no heart at all), more to calm them down and keep them up buying htc products, because there where many disappointed wfs users (the petition they made even where featured at the xda portal).
If this is the case why the /boot partition got no write restrictions, i guess it's related to marketing not kindness.

Related

sensation flashing procedures

is someone gonna post a guide to flashing new roms on the sensation , im getting one when they come out and im coming from an HD2,just wondering if the procedures are basically gonna be the same for the sensation as the HD2 as far as hspl 3 etc.....that is once the bootloader problem is woked out,been waiting for this phone for a long time and if it suks i will have no problem going back to my incredible hd2
I expect flashing on the Sensation will be like most other HTC Android devices. Get it permarooted, unlock the bootloader, flash a recovery like CWM, then flash the ROM zip.
tigerz0202 said:
is someone gonna post a guide to flashing new roms on the sensation , im getting one when they come out and im coming from an HD2,just wondering if the procedures are basically gonna be the same for the sensation as the HD2 as far as hspl 3 etc.....that is once the bootloader problem is woked out,been waiting for this phone for a long time and if it suks i will have no problem going back to my incredible hd2
Click to expand...
Click to collapse
Flashing Android devices is nothing like flashing the HD2. I have three HD2's and 2 MT4G and it is night and day difference...except for the Recovery part if you are using MAGLDR for your HD2.
I am looking closely at the Sensation.
Flashing the Sensation will not require anything like HardSPL. Android users do not even know what HardSPL is.
To flash the Sensation we will first have to unlock the bootloader, get some kind of root access(whether that is permanent or not remains to be seen) and finally flash a recovery of some sort from which you can flash a new ROM in the .zip format.
So yeah, nothing like the initial flashing of Android to the HD2.
Thanks for the replies, well I hope the bootloader gets cracked but I just gotta give the sensation a try with the hardware upgrades over the hd2
I have been using HTC Touch Diamond2, I'm gonna get a HTC SEnsation once it comes out. After reading the guides on HTC Desire HD for flashing, I realised it is completely different.
I suggest reading all the guides thoroughly before flashing.
I am also nervous about flashing cause it is my first time flashing an android phone. And Its a new phone, hopefully I dont screw up.
deepakmk said:
I have been using HTC Touch Diamond2, I'm gonna get a HTC SEnsation once it comes out. After reading the guides on HTC Desire HD for flashing, I realised it is completely different.
I suggest reading all the guides thoroughly before flashing.
I am also nervous about flashing cause it is my first time flashing an android phone. And Its a new phone, hopefully I dont screw up.
Click to expand...
Click to collapse
I can't help but think you're jumping the gun. We don't know how locked/unlocked the Sensation will be (once unlocked by HTC, if that happens). If it's made radio S-OFF before shipping or by an official FOTA update or RUU for those already shipped, it will most likely be just a matter of installing ROM Manager from the Market, clicking the 'Install ClockWorkMod Recovery' button, and then using CWM to install any ROM you like from your sdcard. That's a very low risk procedure that's almost impossible to screw up.
We're going to have to wait for the bootloader to be unlocked. We'll probably see a CWM Recovery a little after and a temp root solution for those unfamilliar with fastboot.
Wrong section btw ;p
Sent from my HTC Vision
dazweeja said:
I can't help but think you're jumping the gun. We don't know how locked/unlocked the Sensation will be (once unlocked by HTC, if that happens). If it's made radio S-OFF before shipping or by an official FOTA update or RUU for those already shipped, it will most likely be just a matter of installing ROM Manager from the Market, clicking the 'Install ClockWorkMod Recovery' button, and then using CWM to install any ROM you like from your sdcard. That's a very low risk procedure that's almost impossible to screw up.
Click to expand...
Click to collapse
Over here in singapore, the phone is yet to be released. I heard 18th June for my carrier. I guess it should be S-Off. Or maybe the new batch released. I've never had any experience in flashing a rom on android phones.
I have it now for one week. I have to say sense 3.0 is so nice! For now I miss root only because of titanium backup and deleting vodafone crap... The original rom feels real nice and battery seems ok
Swyped from my HTC Sensation Z710e using XDA App
deepakmk said:
Over here in singapore, the phone is yet to be released. I heard 18th June for my carrier. I guess it should be S-Off. Or maybe the new batch released. I've never had any experience in flashing a rom on android phones.
Click to expand...
Click to collapse
Once it's fully developed someone will post a guide. As long as you read and follow directions exactly... rooting and ROM'ing is easy. 99% of phones that get accidentally bricked are probably because the user didn't read and do everything exactly.
Until that day enjoy Sense 3.0.
I think flashing should be similar to any android device.. copy the rom.zip into sd card and flash via recovery.. before that we need :
1. Rooting of Sensation
2. A compatible recovery
he he
compiling the recovery shouldnt be that hard colockworkmod has a guide i will try to port once we get the sensation running
JonSolo said:
Flashing Android devices is nothing like flashing the HD2. I have three HD2's and 2 MT4G and it is night and day difference...except for the Recovery part if you are using MAGLDR for your HD2.
I am looking closely at the Sensation.
Click to expand...
Click to collapse
This is because hd2 is not a real Android device. Remember when you bought it and there was an OS on it called windows 6.5 all real android devices are similar.
Thank devs for making hd2 run Android. Still considered by me to be the best and most flexible phone out there
nickyg008 said:
Thank devs for making hd2 run Android. Still considered by me to be the best and most flexible phone out there
Click to expand...
Click to collapse
+10
My HD2 will still be up and running something even after I get the Sensation and the Hercules.

[Q] Some more Sensational Questions

My mate just received his Sensation yesterday and is already keen to root/S-Off etc. so I am doing some reseacrh for him. I have the good ol' Desire, which I have done a lot of work with, so pretty familiar with modding that particular phone. The Sensation is entirely new territory for me, however...
I've read and understand the S-Off/CWM/CID thread http://forum.xda-developers.com/showthread.php?t=1192300 , all looks pretty straight forward and simple.
- Since mates phone is already unlocked, is the SuperCID install required to flash custom ROMs?
- Is there a program similar to AndroidFlasher for Desire available for the Sensation? I found this an easy way to update HBoot tables and other things on my Desire. And if not, what is the recommended method to install these?
- For Desire, HBoot.img's can be found at alpharev.com...where do I find CM7/r2 or data++ type tables for Sensation?
- With a Desire that is S-Off, it's highly recommended to update radio's using Android Flasher or fastboot terminal to push the radio.img, since flashing a .zip through cwm can cause bricking. Is this the case with Sensation, or is it OK to just flash the .zip?
...more Q's as I think of them...

Toolkit for the MT4GS. Anyone interested?

So I made a toolkit for 3 HTC phones. You can see them in my signature. Would you guys / girls be interested in using a toolkit for an All-In-One use. If so, please let me know and I can work on it and probably have it up by tonight. Thanks!
hasoon2000 said:
So I made a toolkit for 3 HTC phones. You can see them in my signature. Would you guys / girls be interested in using a toolkit for an All-In-One use. If so, please let me know and I can work on it and probably have it up by tonight. Thanks!
Click to expand...
Click to collapse
I'm not sure what that is, and haven't chased down your links. Be a few hours before I get a chance to scout it out - i'm just skimming general since I just got back to my dev station and am getting my night started.
I'll just go ahead an say yes, and i'd use it for something, and appreciate the development of it.
Anyone who is willing to take the time to develop tools for working with the device should be encouraged to do so - the more resources at our fingertips allows for more productivity.
Also, as developers move on over time and large online file-hosts are no longer safe cloud storage, the more people who write tool packages for the device specifically enables future devs a higher chance of having the tools available over the long haul as people move on to other devices.
So, peg me as one vote for a variety of reasons even beyond the quick justification for your work here.
I welcome your interest in making something for the device and would like to take a minute to thank you for any work you want to do on it - definitely there is interest!
Blue6IX said:
I'm not sure what that is, and haven't chased down your links. Be a few hours before I get a chance to scout it out - i'm just skimming general since I just got back to my dev station and am getting my night started.
I'll just go ahead an say yes, and i'd use it for something, and appreciate the development of it.
Anyone who is willing to take the time to develop tools for working with the device should be encouraged to do so - the more resources at our fingertips allows for more productivity.
Also, as developers move on over time and large online file-hosts are no longer safe cloud storage, the more people who write tool packages for the device specifically enables future devs a higher chance of having the tools available over the long haul as people move on to other devices.
So, peg me as one vote for a variety of reasons even beyond the quick justification for your work here.
I welcome your interest in making something for the device and would like to take a minute to thank you for any work you want to do on it - definitely there is interest!
Click to expand...
Click to collapse
Thank you for your input.
The toolkits I make do the following:
- Install HTC Drivers
- Flash Kernels
- Flash Recoveries
- S-Off via Revolutionary (if available) / Unlock bootloader via HTCDev (if available)
- Boot into recovery/bootloader
- etc.
There are buttons that you press once and it will do what you want.
I can unlock my HTC Amaze bootloader and flash a recovery within 5 mins.
I really appreciate your input. It is very thoughtful and meaningful.
I am looking to spread my toolkit to many HTC devices and possibly other devices as well. I just finished making one for the Rezound since I received a lot of support and feedback.
I hope as well to receive support and would like to feel welcomed to a new area of the forum.
Heck yea I would be interested. I not too savvy on how to root, but.this sounds fool proof if it involves one button. If I
Understand.correctly.
Sent from my myTouch_4G_Slide using XDA App
This should help all the people and existing users. I will try to get it up tonight. Have a lot of homework and some exams this week.
Awesome - We just cracked S-OFF to S-On reversal Here
So that might be something to consider for your tool too.
Don't worry about stretching yourself too thin to get it out the door - take care of the important things first. We all understand that you do this kind of stuff when you can, and when not that's cool.
We're all here in our spare time as we can give it - I look forward to anything you want to put together!
Blue6IX said:
Awesome - We just cracked S-OFF to S-On reversal Here
So that might be something to consider for your tool too.
Don't worry about stretching yourself too thin to get it out the door - take care of the important things first. We all understand that you do this kind of stuff when you can, and when not that's cool.
We're all here in our spare time as we can give it - I look forward to anything you want to put together!
Click to expand...
Click to collapse
I am still trying to understand what the tool does lol. If you are on S-Off (only rare devices have it I believe), then you can go back to S-On and go back to S-Off?
I am aiming to get the toolkit up by Wednesday. First 3 days this week is gonna be long on me
hasoon2000 said:
I am still trying to understand what the tool does lol. If you are on S-Off (only rare devices have it I believe), then you can go back to S-On and go back to S-Off?
I am aiming to get the toolkit up by Wednesday. First 3 days this week is gonna be long on me
Click to expand...
Click to collapse
Its not rare to be s-off.
sent from rubix ics 5.2 mt4gs
leoilios said:
Its not rare to be s-off.
sent from rubix ics 5.2 mt4gs
Click to expand...
Click to collapse
Not all the latest devices have S-Off. For example, the Amaze 4G, the Rezound. That is what I was trying to say.
:thumbup: Ill use it, I use HTC Super Tool! Its amazing. Your tool seems simular
Sent from my HTC myTouch_4G_Slide using Tapatalk
hasoon2000 said:
I am still trying to understand what the tool does lol. If you are on S-Off (only rare devices have it I believe), then you can go back to S-On and go back to S-Off? ...
Click to expand...
Click to collapse
Yes and no -
If on 1.44.0007 hboot version you can S-OFF via the Revolutionary method.
Figured out how to turn that back S-ON again - and afterwards you can S-OFF again using the Rev method. (But only if NOT on hboot 1.45.0013 with S-ON)
You may also run the PG59IMG.zip that restores to factory stock condition whether S-ON or OFF (it's an HTC signed package) and still be either S-ON or OFF depending on what you were when you ran it - your security status is preserved.
When you update to the most recent software version, it will replace your hboot with a 1.45.0013 version...here's the skinny:
If you are S-OFF and upgrade to the most recent OTA then you may freely flash back to the original retail stock condition using the first PG59IMG.zip, or use the new one to flash fresh straight to the most recent software version.
You may also replace your hboot whenever you want.
If, however, you are S-ON and advance to the most recent OTA, that's a one-way trip right now. You will no longer be able to use the Rev method to S-OFF, you will no longer be able to reset before the most recent OTA, and you cannot replace your hboot. You cannot replace your radio.
You also have to flash boot.img seperately from any custom ROM that uses a custom kernel.
So, if S-ON or OFF on versions:
1.28.531.9 (software)
1.28.531.10 (software)
With hboots:
1.44.0006 (factory S-OFF)
1.44.0007 (retail launch)
1.44.1107 (Revolutionary)
... you may do whatever you want.
With S-OFF and:
1.55.531.3 (software)
1.45.0013 (hboot)
...you may still do whatever you want.
With S-ON and:
1.55.531.3 (software)
1.45.0013 (hboot)
...you are stuck where you are, with all the restrictions I mentioned above but we got the HTC Unlock tool working now so it's not hopeless, just crippling.
That's most of it laid out, the rest is kinda common sense but questions always welcome. If "I don't know" wasn't a valid answer no one would ever learn anything.
Edit:
Also, yogi2010 verified earlier that flashing the PG59IMG.zip file (not sure which - probably both though) doesn't wipe out LOCK/UNLOCK status.
It appears that LOCK/UNLOCK and S-ON/OFF are device specific and not so much hboot specific.
When I flash the S-ON copies of hboots people have graciously given me, they read S-OFF on my S-OFFed device. Whether that's a function of what Rev did to it or not is something i'm exploring now.
Hopefully yogi2010 will see this and add what he found about the LOCK/UNLOCk status for flashing the PG59IMG.zip files to clear that up a bit
Alright guys. I feel pretty bad saying that I was gonna update this by yesterday and I couldn't. (No wonder why devs hate making ETAs) A lot came into my life. A lot of school as well as my brother's wife will be giving birth to their first child really soon! Pretty exciting.
For those with requests / updates they want me to add, please PM me the link/info/what device it is for. It will be easier to add in. Thanks!
No worries man, we all have life stuff that pops up. We're in no hurry here.
Sent from my myTouch_4G_Slide using xda premium

[Q] Worst-case scenario regarding S-OFF, root, bootloader

I've searched (both xda and external sites) and I've read through many threads but I still don't have clear answers to these questions so I'd appreciate any help anyone can provide. I'm an Atrix user so I'm assuming a worst-case scenario mindset in order to properly weigh my options before upgrading.
1. What issues would HOX users face if the devs are never able to achieve S-OFF?
I think the normal behavior for S-ON is that you are not able flash kernels or radios. However, the devs have currently figured out a way to flash kernels on the HOX despite the lack of S-OFF. Similarly, there may also be a way to flash radios despite the lack of S-OFF too but this has not yet been achieved. I think S-OFF also lets a user resize partitions but I'm not sure why this would be a huge issue. Is this all more or less correct?
2. 1.85 devices can have their bootloaders unlocked once a new root exploit is found for that firmware, right?
My concern is that I'll get a 1.85 and be permanently stuck with an AT&T/HTC ROM.
This all comes down to the HOX vs. SGS3 for me. I really prefer the HOX but I'm not willing to risk being stuck with the AT&T ROM. Of course, this could be moot because we don't yet know whether or not AT&T will be able to convince Samsung to make an exception to their bootloader policy like they were able to do with HTC.
Thanks again for your help.
I think AT&T phones are being shipped with 1.73 right now which is capable of being rooted. Someone correct me if I'm wrong.
Yes if the htc has 1.73 it can be rooted. Then the cid can be changed to unlock the bootloader through htc dev. After that you lock the bootloader back and upgrade to 1.85. Then you re unlock the bootloader and install cwm and after installing cwm flash SU for root on 1.85. As for Samsung EHH..
1. As far as I know all you've stated is correct, if a dev wants to pop in to correct me by all means you can. There are some kernels that are "flashable" not neccessarily stable though just because of the lack of a source code. And the DCM by viperboy is pretty awesome.
2. Yes they will be able to. Most people are stuck on 1.85 because they were too eager and updated before any development. They're not really all to blame it's just human nature. But as far as I know there is no current development for root because the method from 1.73> to root> to CWM is getting the primary focus. Phones as of right now are being shipped with 1.73 IF you can even get your hands on one. It's hard because of all the customs issues.
Both phones will be excellent and both will get great development. I've just been an HTC guy so I like the HOX. However if you want "right now development" the GS3 might be a better choice in all honesty depending on what AT&T decides on the BL. But HOX development is moving along quite nicely. My phone kicks ass!
Thanks, everyone.
@Shaddy-Z
So in your opinion the lack of progress in obtaining root for 1.85 is mainly due to a smaller current need and not because of some new or challenging hurdle? Would you expect a new method to pop up once a majority of phones begin shipping with 1.85? What would you put the odds at? I know this is not apples to apples but I have residual skepticism carried over from the Atrix bootloader affair. The devs were basically thwarted/defeated and the unlock was only achieved as a result of an anonymous/unsanctioned leak.
Just saw this post: http://forum.xda-developers.com/showthread.php?t=1693624 It appears they are shipping now with 1.85...
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
pside15 said:
You do not need s-off to flash kernels. You can flash them through fastboot just fine, as long as you have an unlocked bootloader. You just can't flash them through recovery until we have s-off. I really don't think s-off is even needed. It would be nice to have but it doesn't stop you from doing anything except flashing radios. I was in the same situation when I was using the Vivid. I didn't even s-off my Vivid when the tool was released because I didn't need it.
Click to expand...
Click to collapse
Actually they have found a way to.flash kernels and radios in recovery.
Sent from my HTC One X using xda premium
In this thread it is mentioned that everything can be flashed though custom recovery now http://forum.xda-developers.com/showthread.php?t=1639972&page=99
so s-off is not limiting us anymore
So... No need for s-off now then? :thumbup:
Sent from my HTC One X using xda premium

[Q] Thing I must know before I purchase a HOX

So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
sunny342 said:
So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
Click to expand...
Click to collapse
First off, when you get it rooted... DONT FLASH ICJ.
Second, when you get it downgrade you hboot via the JET tool or manually through the WIP Unbrick evita thread by Absolutelygrim. Then in the JET tool thread, you'll find a way to RUU down grade. Choose 1.85 Then you won't have to worry about flashing the boot.img in fastboot. All that is, is a way to bypass AT&T's safe gaurd programming. They tried to make it so the boot.img couldn't be formed in recovery. That's only with the 2.20 firmware though.
Third, IDK. I'm still learning why S-OFF is like gold. Someone else might be able to answer that one but, not me.
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
p3terr said:
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
Click to expand...
Click to collapse
Would you be getting the AT&T version, or another variant?
Setting the phone up for flashing ROMs is a bit more complicated than some other manufacturers. But this is just how it is for HTC, they have an increasing degree of security on their phones.
You have to unlock the bootloader, which really isn't all that hard. Then install custom recovery and you can flash ROMs. The AT&T version has the extra steps of temp root, SuperCID before you can unlock the bootloader.
Once the phone is setup, flashing ROMs is just like any other phone. With the exception of having to extract boot.img from the ROM zip and flashing via fastboot. But I believe this only applies to the AT&T version with the 1.14 hboot. Even so, you can downgrade the hboot, so you don't have to do the extra step of manually flashing boot.img.
Bricking the phone while unlocking the bootloader is unlikely. But its always a possibility with any mods. Unlocking the bootloader wipes the phone (not really an issue if you are doing it right away after buying) and you also have to confirm that you understand that unlocking the bootloader may void your warranty. Other than that, there is no real "con" to it.
I just finished unlocking bootloader, rooting, installing venom Rom and putting beastmode custom kernel on my [email protected] hox. It's easy now even with 2.2. Just download the all in one tool kit found in the stickied thread for the hox. Does almost all work for you.
Flashing Rom there after word was very similar to cwm was. Loaded it on my internal storage and flashed via recovery
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Click to expand...
Click to collapse
I am aware of the One X+ but I am on a budget and the slight performance boost to me doesn't justify the price. Radio shack will have the HOX for free on blackfriday. Also thanks for the answers to the questions your comment cleared up alot for me.
ECEXCURSION said:
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Click to expand...
Click to collapse
ARIA FTW lol. I need the upgrade to the HOX. Only 9.9GB sucks pretty bad but I can make it work. If only I too had the money for the one X+
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
If you follow instructions properly and read up on everything necessary, unlocking, rooting, and flashing the HOX is a breeze; 2.20 only introduces one additional, straightforward step.
exygenysys said:
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
Click to expand...
Click to collapse
Im eligible for a qualified upgrade on my family plan so I can't take advantage of the new contract deal.

Categories

Resources