So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
Hey guys, I somehow managed to soft brick my verizon GS3 this afternoon. I just need a little help in getting the thing back up and running and possibly an explanation on were I went wrong. I thought I had unlocked the bootloader and then rooted the phone. I managed to install TWRP 2.5.0.0 and do a backup. Then I installed a custom ROM and got the infamous "Software not authorized" message with the yellow triangle.
1st, is it possible to get this far with the bootloader still being locked??
2nd, If I understand correctly, I need to use ODIN to go back to stock and start over. Correct? Or is there another way to salvage this situation. If I have to go back to stock, can someone point me to the latest files? I've found links to a lot of different ones and I don't want to make a bad situation worse. BTW, I can't get into recovery but I can get into ODIN mode.
Any help is greatly appreciated!!
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
scheirere said:
Ok, using ODIN, I was able to get a stock ROM onto the phone and get the thing booted. So essentially I'm back to square 1 and I still didn't figure out what I did wrong the first time around. Bummer Eh?
Click to expand...
Click to collapse
Yea, I soft bricked once and was able to boot into recovery by holding volume up, power, and home at the same time while the phone was off. I thanked my lucky stars I had a nandroid backup. I would make sure you unlocked the boot loader properly. When I first started rooting YouTube was great for instructions. I would post a link to a YouTube video but it won't allow me until I have ten posts, I swear some of these rules are retarded. Anyway search in YouTube having visual and audio guide helps a lot. good luck!
Ok so I am unsure if someone is filtering out OLD topics but i keep coming across FORUM posts from people and it seems like they are getting no help or being referred to NON existent topics.
I just recently bought a HTC ONE M8 H/K from sprint. I have had android for a decade and am seriously tired of the ROOT it people. so I figured why not no down falls and everyone says it is easy. Well I am Murphy last name law and you people have not seen or know the things I am about to post
I recently spent over 32 hours watching video and preparing for ROOTING. I unlocked phone got Pilz touch recovery and everything worked fine. I even got CWM and SUPERSU and Busy box. all of which needed OTHER files to work properly. Again a few forced quits everything was fine.
I wanted to Switch to TWRP and the install didnt go through. however now I have BOOTloop. trust me this is the tip of the berg at this point.
Just short of finding NO help after another 24hrs binge session on the CPU and just shy of RUNNING MY PHONE OVER WITH A DAMN CAR>
I get oh so simple easy fix and the only posts I see are FIXED IT!!! so that helps me approximately as much as my phone helps me make phone calls currently.
After the boot loop SEVERAL friends versed in this so called ROOTING (which I still find to be a hoax and not actually possible by any means at this point and time.) and no one has any clue. Tried flashing ROMS RUU's everything comes back to NO will not work.
Then it brings me to the STOCK RUU config for the HK M8 which seemed like it was going to work through ADB flash but guess what. 2 hrs idle NOTHING. after that The recovery program dropped out and boot loader only stated RUU in the menu. (something never before logged in a forum or post as I can tell) after many attempts to do GOD KNOWS WHAT WITHOUT ANSWERS as i was about to smash my beautiful gold phone into a dozen tiny peices and claim accident the Recovery came back to...... You guessed it NOTHING. All directories are UNMOUNTED and cannot be mounted.
I am stuck. Seriously you all fix my phone or help i am willing to send gifts because I am out 700$ now on this nice paperweight but everything and everyone tells me. OH SO SIMPLE you have recovery it aint no thang.
Well guess what it is and I am tired of being so PISSED OFF for something that was so automated.
Again I am Murphy and what you attempt to get me to follow will come up with some REALLY weird repercussions I will post back.
Please oh mighty gods of ruining my life. Spare me this one thing I will never ask for another again.
How do I get my phone to just WORK, Simple. Right?
Hi there! I think I found a thread that can get you back on track. Please read every word carefully and follow every step. If you have further trouble or want to clarify anything, please ask in the thread. They know the device best and can help you I'm sure.
http://forum.xda-developers.com/showthread.php?t=2503646
I'm afraid that is the extent of what we do in the XDA Assist Section. We are guides...pointing people in the right direction when they can't find what they are looking for. Unfortunately we don't do hands on support in this section, so as I said....if you need a further hand, I am sure someone in the thread I linked can help.
And make sure anything you download and flash is for your model. And as always, do a Nandroid backup in recovery... before flashing anything new....it can be a lifesaver to help restore you when you hit trouble.
Good luck!
Details
Let me re iterate.
All guides are demanding S-Off (cannot as I cannot acess phone apps to do so)
All guides need HOME access for apps to modify certain things
I cannot:
Push packet through adb as they are unreadable
Get past boot screen
Recovery is only 40% operational with visibilty of phone only working sometime.
Cannot flash
Cannot push
Cannot fastboot
Cannot see device on CPU as it is stuck in recovery
ALL DIRECTORIES in /SDCARD have been removed
No Firmware
No RUU
No img
As far as I can tell.....Phone is empty and cannot be populated with anythin. I did manage to get SuperSu pushed through and installed. But how do I open it?
No ROOT access as well in the recovery.
I followed ALL STEPS of EASY guides even downloaded one button app that runs it all for me. Can't talk to phone does not see it in ADB.
The other guide I went to was helpful but I have already attempted all of those things.
With an empty phone NO DATA and no ability to get ADB to even run data over cable I am baffled.
I did exactly like the 500 guides i read said.
1) bootlock unlock
2)instal recovery (Philzmod)
3) get CWM (retrieved from playstore) Need a .zip to run in ADB
Phone worked fine until I changed from Philz mod to TWRP which never took place. Philz mod still runs but TWRP said it installed.
Now I have a completely worthless empty phone and I have cried about a tub worth of tears over the 700 i will be dropping over the next year for a piece of metal.
Oh and 99.9% of time if ADB DOES do something either no directory once pushed, cannot read or cannot FIND/Open directory stating BAD installation aborted I NEED a better recovery
I understand your frustration. Not a fun situation at all.
As I said, XDA Assist is here to help navigate the website. Not to troubleshoot I'm afraid.
The purpose of XDA Assist... http://forum.xda-developers.com/showthread.php?t=2764768
The very best place to ask for help in your situation is right here, in the Q&A section for your device... http://forum.xda-developers.com/showthread.php?t=2764768
The people there know your device best. Start a thread that's to the point, polite and accurate....what is exactly wrong, and the exact steps you took to get there. And hopefully help will follow.
Hope it can be solved for you!
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
Hello!
I've posted a similar thread on a different page a couple months back, never finished through with it, and now I'm back looking to finish rooting this SM-G935V once and for all. That's all I want to do with it. I've become somewhat familiar with the lingo used for rooting. All I want to do is root it so I can download apps that require rooted phones. No custom ROM's or anything else, just a simple root.
I think it's tough for me to find valid information on this particular phone because it's already 3 years old and people have moved on, leaving older guides outdated and no longer valid (Atleast I believe it leaves them invalid).
Anyway here's what I got so far.
From what I understand, the only way to root this phone is to unlock the bootloader. I was researching and figured I had to download ADB, so I did, and I got it working. Using the command prompt on Windows, ADB communicated with the phone successfully. But, before I could continue messing with it further, I tested to see if the Fastboot was working aswell (apparently I'm supposed to have both ADB and Fastboot working). I tried using the Fastboot command to test it. What happened was that it sent my phone into a different screen, but the screen was not the typical bootloader screen that I've been seeing other people get. It was a fairly blank screen with nothing but an android logo with the word "Downloading" in the middle. Typing the "fastboot -devices" command returned no devices. After waiting 5 minutes the screen stayed the same and I just gave up on that part, deciding I should consult the experts here.
Any help will be greatly appreciated. Starting to think I'm better off just buying a new device that's easier to root.
WorstedSet said:
Hello!
I've posted a similar thread on a different page a couple months back, never finished through with it, and now I'm back looking to finish rooting this SM-G935V once and for all. That's all I want to do with it. I've become somewhat familiar with the lingo used for rooting. All I want to do is root it so I can download apps that require rooted phones. No custom ROM's or anything else, just a simple root.
I think it's tough for me to find valid information on this particular phone because it's already 3 years old and people have moved on, leaving older guides outdated and no longer valid (Atleast I believe it leaves them invalid).
Anyway here's what I got so far.
From what I understand, the only way to root this phone is to unlock the bootloader. I was researching and figured I had to download ADB, so I did, and I got it working. Using the command prompt on Windows, ADB communicated with the phone successfully. But, before I could continue messing with it further, I tested to see if the Fastboot was working aswell (apparently I'm supposed to have both ADB and Fastboot working). I tried using the Fastboot command to test it. What happened was that it sent my phone into a different screen, but the screen was not the typical bootloader screen that I've been seeing other people get. It was a fairly blank screen with nothing but an android logo with the word "Downloading" in the middle. Typing the "fastboot -devices" command returned no devices. After waiting 5 minutes the screen stayed the same and I just gave up on that part, deciding I should consult the experts here.
Any help will be greatly appreciated. Starting to think I'm better off just buying a new device that's easier to root.
Click to expand...
Click to collapse
You can root by following this thread. If your phone is current on its updates, near the end of the thread I believe there is the attached eng.boot.tar that you'll need to flash in the AP slot in Odin 3.13. Everything you need should be in this thread: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616