Hi,
Yesterday, my aunt a HTC One S from T-Mobile. Seems to be a very good phone.
I'm not sure if it was me but both my aunt an I find the interface sort of difficult to use. Is it something to do with because this is a branded phone so the bloatware and menus have changed? This is considering I have Galaxy Nexus and it's pretty clean.
That being said, from reading on the forums a bit, it seems like the Europe one is unbranded and maybe the key in solving this + getting rid of the unwanted apps which were were just literally throwing icons off the screen.
My question is, for changing the roms. What is exactly the steps I need to do? When I tried reading the FAQ for here, it seems more difficult than I thought and a bit confused. Since I did flash my own Galaxy Nexus, reading the FAQ over there was more straight forward (ie. dirver, get factory image, unlock boot loader, fastboot flash...).
Your help is appreciated.
i agree with the OP. we have 3 threads in the Development section to perform the root procedure and further manipulations and they all seem to be all over the place. we need one, up to date guide.
Welcome to the forum--
First off you are in wrong section--need to post in Q&A. A mod will probably move it for you
Start by reading FAQ/Rules etc
Hard to find one and only one guide anywhere. Need to read all you can. I have gone thru some threads 3 times to understand it all
I used the Unlock/Root thread and did all manually, and had to ask one or two questions in the noob thread after I got rooted, but all pretty straight forward if you have rooted before
The 1s is a great phone--enjoy
The basics are unlock with htcdev
flash a custom rom, with with stock one as some you have to flash boot.img separately and is more difficult
flash superuser, you can also get SU from market
The unlock/root thread by torxx is fairly easy
You don't need the interim cwr anymore, get regular one from koush 5.8.3.1 I believe
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Or give yourself a week or two with the phone. In the two weeks that I have had my One S, I have disabled apps that I know I will not use, I have personalized it to a point that I find it to be a very productive device.
Of course eventually I will root/unlock, etc. As of now I'm in no hurry.
hTc One S
Related
I use to follow XDA very regularly when I had my HTC Hero a year ago, and then followed another forum (can't remember the name) when I had my Samsung Moment. I remember both of those phones had the ability to use a RUU in case the worse happened. I believe the Samsung didn't use a RUU file, but it was similar in function. Anyhow, I was just wondering since I just got my Samsung Galaxy S 4g and would like to start rooting again, is there a way to revert back to factory in case I decide I no longer want to root or if the worse case scenario happens (boot loop, no boot, ...etc)? Having these factory firmware files made bricking a phone much less likely. Correct me if I am wrong. Thanks in advance!
you posted this in the wrong forum. this goes into the general section.
to answer your question, you can always use odin to restore everything should you soft brick. check out the bible below for should you brick (noobs guide to odin) and for information in general:
http://forum.xda-developers.com/showthread.php?t=1117554
and also user danstheman7's site, as well:
http://cyclopscomputers.com/gs4g
to go back to stock, you can check out krylons stock+root rom. you can unroot using superoneclickroot.
mar122999 said:
I use to follow XDA very regularly when I had my HTC Hero a year ago, and then followed another forum (can't remember the name) when I had my Samsung Moment. I remember both of those phones had the ability to use a RUU in case the worse happened. I believe the Samsung didn't use a RUU file, but it was similar in function. Anyhow, I was just wondering since I just got my Samsung Galaxy S 4g and would like to start rooting again, is there a way to revert back to factory in case I decide I no longer want to root or if the worse case scenario happens (boot loop, no boot, ...etc)? Having these factory firmware files made bricking a phone much less likely. Correct me if I am wrong. Thanks in advance!
Click to expand...
Click to collapse
you used to follow XDA? and yet you post on the wrong forum?? and start reading!!!!! mod please close this thread.. the answers to these question are in the forum. they just need to read more.
Thread closed.
I successfully flashed a custom Froyo ROM on my MyTouch 3g and was quite happy. I did it by following step by step instructions, and while it worked, I didn't understand what I was doing. Now I have a Galaxy S 4g and plan on flashing Gingerbread, but before I do, I would like to understand the process.
I don't want anything specific like instructions on a particular device and ROM, just a general idea of the process, like "Flashing ROMs for Dummies". Then I can come back and re-read some of the threads and know what the posters are talking about.
Question: Where can I find a general tutorial on the process of flashing ROMs to Android devices? I'm an IT consultant so I have a fairly high tolerance for tech-speak. Thanks.
I'll be waiting for the answer to this one too.
It usually works like this:
We root our device to have full access with all priviledges and be allowed to i.e. exchange the kernel.
Now we exchange the kernel against one with an advanced recovery mode (i.e. clockwork mod recovery from cyanogenmod), it allows you to flash unsigned (not official signature) ROM files.
From the new recovery we install a ROM of our choice which can also replace the kernel again.
The recovery mode basicly executes a small script, contained in the ROM file, that copies all the files to the correct location, sets up the partitions and wipes previous data on occasion.
The other possibility would be to use a flash program like odin/heimdall and have your computer setup and write a new firmware onto the device unlike the first method where the device does the setup work.
This is a very broad explanation, i have only flashed an sgs2 and sgs1 so far, so there might be small or huge differences between devices.
Maybe you could ask a more specific question about a particular step if things are not clear.
I'm not 100% sure, if i missunderstood something myself, someone please correct me .
Thanks, Dark3n. That was a very good explanation, in layman's terms, of the process. What I am looking for is one place to learn about what is happening technically; not a developers guide but something sufficient for me to understand.
For example, I've seen threads where someone had a problem with a ROM because they didn't have the right bootloader. What is the significance of bootloaders in changing ROMs? How does the backup/recovery process work? What is the Dalvik cache and why clear it? What is Dalvik?
I found the answer to these questions by Googling them one at a time. I was just wondering if there was one place to go that covers the entire process.
I know that most of the members here are very well informed and get tired of the same questions over and over. If this is the wrong place to ask, let me know and maybe point me in the right direction. Thanks.
lewis750 said:
Thanks, Dark3n. That was a very good explanation, in layman's terms, of the process. What I am looking for is one place to learn about what is happening technically; not a developers guide but something sufficient for me to understand.
For example, I've seen threads where someone had a problem with a ROM because they didn't have the right bootloader. What is the significance of bootloaders in changing ROMs? How does the backup/recovery process work? What is the Dalvik cache and why clear it? What is Dalvik?
I found the answer to these questions by Googling them one at a time. I was just wondering if there was one place to go that covers the entire process.
I know that most of the members here are very well informed and get tired of the same questions over and over. If this is the wrong place to ask, let me know and maybe point me in the right direction. Thanks.
Click to expand...
Click to collapse
I don't think there is such a place. But you could help out others and create a wiki page on the topic.
We have a slightly underused xda wiki
I see a lot of people having problems and lost how to relock bootloader to update via RUU. This is a quick little tutorial. This works with AT&T that I've tested but should work with.others Mods I'm sorry if I'm posting this in the wrong place...but it feels right here.
If you are relocking make sure you have SuperCid.....
Open command where your SDK tools are....quick way is to hold shift and right click and choose open command line here. Make sure debugging is checked on. Plug device in charge mode, and type adb command as followed below.
"fastboot oem lock"
Now you should be relocked on bootloader. While in bootloader run the RUU 1.85 exe file and follow instructions....takes about 15 min or so to complete. Once done the phone will reboot. Enable debugging once again under developer options. Got to the HTC dev page to unlock bootloader....follow instructions to unlock....use option all other supported devices..... obtain token to unlock bootloader...I hear you can use the old token but this is how you obtain new one just incase.
Place the token bin file inside your SDK tools folder....fire up command prompt once again, go reboot into your bootloader on phone, connect phone to pc, and type adb command as followed...
"fastboot oem get_identifier_token"
Then select yes on phone....blah blah...phone will reboot...once rebooted enable debugging again, go to power options and turn off fastboot....then power off phone......go into bootloader by holding volume down and power and make sure bootloader says unlocked...if not run token identifier command again...took me two trys to get it.....I've heard others take more tries.....if it says unlocked....reboot phone....flash cwr...you can use the one click recovery on this forum..... Then reboot into recovery and go happy flashing on your now updated device. I'll update later, I was just typing this up real quick at work. I might make a bat tool to make things easier.
There is already a thread started on this topic in the General section
http://forum.xda-developers.com/showthread.php?t=1675312
This same thing is posted in General I believe by a different user and also in every forum thread I've come across today lol.
Oops sorry didn't know that...I'm sorry...mods you can delete then...sorry guys...didn't mean to step on toes
This is getting redundant
Sent from my HTC One X using Tapatalk 2
mrjaydee82 said:
Oops sorry didn't know that...I'm sorry...mods you can delete then...sorry guys...didn't mean to step on toes
Click to expand...
Click to collapse
No reason to be sorry, you're only trying to help
freshleysnipes said:
No reason to be sorry, you're only trying to help
Click to expand...
Click to collapse
I agree.
Just my 2 cents, I don't regularly comb the General subforum to add important threads to the Index sticky thread. I'd personally rather guides like this be posted in Development. Although I think its inevitable that some useful info is going to end up in General.
plus, i think a .bat tool would be very helpful in this instance. would love if that could be created.
thanks for your work
redpoint73 said:
Just my 2 cents, I don't regularly comb the General subforum to add important threads to the Index sticky thread. I'd personally rather guides like this be posted in Development. Although I think its inevitable that some useful info is going to end up in General.
Click to expand...
Click to collapse
I'm seeing that the One X is a different beast and the users are a bit different too, I bet many won't ever even LOOK in Dev.
This helped me out beyond belief! Even if this was on the forum already, I had not seen it. Thanks for the write up.
This totally belongs in this sub-forum. This is related to modifying boot loaders and working around HTC patching the root exploits in 1.85. This is not "General" material.
As far as it being redundant to what is posted in General, how was one to know? Come one guys.
Also OP, You can use the same token that you initially got when you unlocked on 1.82. You dont need to gen a new one. Just throwing that out there.
I had submitted my reply at the same time as the second poster. It just seems like the same info that a lot of other users have posted else where is all.
Sent from my HTC One X using XDA
Thank you.
I know this has been posted everywhere but the way you worded made it easier.
I finally got it going from another threat but read your take on it and it was easier to follow.
When I get home tonight, gonna write up a .bat tool
scrosler said:
This totally belongs in this sub-forum. This is related to modifying boot loaders and working around HTC patching the root exploits in 1.85. This is not "General" material.
As far as it being redundant to what is posted in General, how was one to know? Come one guys.
Click to expand...
Click to collapse
I posted this guide in GENERAL a few days ago because I felt like there was NOTHING developmental happening here. It is a general how-to on locking and unlocking your bootloader. Nothing new, in a development sense, is happening in this post.
I'm not saying he's wrong, but it's how I felt when I posted this guide in the general section. I suppose it doesn't matter as long as people are finding the help they need.
Moderator needs to move this irrelevant thread.
Sent from my HTC One X using XDA
mrjaydee82 said:
When I get home tonight, gonna write up a .bat tool
Click to expand...
Click to collapse
I actually have the entire process scripted I just didint post it because I dont want to take on that responsibility... I like to focus on ROMS.
If you need help you have my email.
freshleysnipes said:
I posted this guide in GENERAL a few days ago because I felt like there was NOTHING developmental happening here. It is a general how-to on locking and unlocking your bootloader. Nothing new, in a development sense, is happening in this post.
I'm not saying he's wrong, but it's how I felt when I posted this guide in the general section. I suppose it doesn't matter as long as people are finding the help they need.
Click to expand...
Click to collapse
He also delves into custom recovery and that falls under Development. That is not General. With your line of thought the entire "Unlock Bootloader" thread should be in General too because its not technically development?
Sorry not trying to get into a pissing contest I am just trying to show you a alternative point of view.
But we can agree that the that info is useful regarldess of its location...
My thread got hammered with this question when people were updating my ROM. I wish someone made this thread earlier or at least I knew about it. I rarely look at General. Had I seen your thread I could have sent people over there instead of derailing my thread. Oh well. At least I know where to send them now!
And as far as being duplicates, that's a good! Look at any big sub forum and you will see lots of guides on the exact same subject. Each thread explaining it a little different and some threads putting in videos, others with screenshot. There is nothing wrong with too much info. People learn different ways and with different methods / styles of communication.
-Scott
scrosler said:
I actually have the entire process scripted I just didint post it because I dont want to take on that responsibility... I like to focus on ROMS. -Scott
Click to expand...
Click to collapse
Be very nice if you released it.
Pumpiron579 said:
Be very nice if you released it.
Click to expand...
Click to collapse
I sent OP what I have. He can take the scripts over. I like to focus on ROMS. I dont like working with the unlocking aspect.
Hello there, ive been reading for countless times now the forums, guides and all kinds of info in hope of beeing able to restore my HTC One X to its stock tom, but i have failed so far in every attempt, ive changed to cyanogenmod 11 like 2 months ago, but then decided id want the stock rom better, and so far all ive managed is to restore a nandroid backup via clockworkmod but the touchscreen wotn work, so i got completely lost this time,
my CID is 102
and main version is 4.18.401.4
unlocked bootloader etc.
any help? any suggestions? guides? im really desperate now... cant get it to work...
Hi there!
Here's a thread about returning to stock. Of may be a little dated, but you can always ask in the thread if its the latest firmware or not. Read the whole thread to see if any issues you have are mentioned in it.
Post #4 has clear instructions.
http://forum.xda-developers.com/showthread.php?t=1799881
You can ask in that thread for further help I'm sure as well!
Good luck! ?
I've spent a couple days trying to figure out why my install is giving me so much trouble. With less than 10 posts I can't post in the active thread, and the Q&A thread gets no attention. I'm running a stock, previously unmodded (though used) Galaxy S5 G900T T-Mobile version, checking both the internally reported model number as well as the sticker in the battery compartment. It has been functional for over a year but getting slow due to too many apps.
I've reflashed, redownloaded, tried different SD cards, cables, computers, etc. I'm at least on my 20th flash. I've read some people having similar problems, but in the Q&A thread it's just people with no clue talking to each other.
I've even downloaded the same file (pointlessly, with the same hash and all) from multiple mirrors.
The phone hangs on the "starting apps" screen, IF I wipe dalvik and pull battery. Anything else hangs on the "samsung fireworks" boot animation.
CM12 went on just fine, as best I can tell I'm rooted. The other questions in the Q&A thread are, at best, incomprehensible and not providing ANY technical information or even a real question, I can see why they don't get a careful response - but I'm trying to approach this logically and carefully and just plain don't know where to turn. If there were some way I could record some data of use for someone more knowledgeable to look at, I'd be all too happy to do it.
I did just PM Edgar directly, so this may help - but I've got some 16 hours of seat time watching this phone not quite boot up (except on cm12) and I'd really like to flash something beyond the stock ROM. (as a total aside, does anyone know if the latest nightly CM12 build needs the boot animation patch applied or has it been incorporated?)
Thanks!
Hi there,
You already founded the right place for this questions so please wait there an answer.
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Our XDA Assist team will give you links to threads/forums that are relevant to your problem. You may be pointed towards guides and instructions that can be quite complex, so you will still need to read carefully and be cautious before attempting to make software changes to your device. It is essential you are in the correct forum for your device model; what works for one can ruin another.
Click to expand...
Click to collapse
Good luck