So I rooted my ATT One X and recently used the tool to get the token and unlock it via HTC. I've tried to install CWM via ROM manager and it says it is installed but if I try and boot to recovery it hangs at a screen with an HTC Logo saying that "this build is for development purposes only, etc..."
If I power down and reboot with the vol down held I get the menu and it says tampered, unlocked, S-On. Trying to boot into recovery from this menu produces the same result.
I'm sure I'm missing something here since I'm a bit of a noob with this but can anyone give me a suggestion?
Thanks in advance!
Ok, looks like I managed to get it down through ADB commands. It's times like this when us noobs actually learn a little bit about our phone
As you've discovered, I don't think that ROM Manager properly installs CWM on our phone. The best way is the one-click install in the Development forum.
Related
Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
SOLUTION: Ok this is what I did to get it working again. My phone is on Rogers so I had to download this RUU and then follow these steps to flash the RUU onto the phone. Pretty simple actually.
Well, I can tell you that the ROM you were trying to flash was not for the S4 variant of the HTC One X, the ROM you saw was for the international Tegra 3 chip which is VERY different. I would attempt to flash an RUU from the At&T HOX thread if that is possible. Sorry if I can't be of any more help, that's all I've got.
I just had this exact same problem on mine. Well I didn't try to install a full rom, but accidently tried to apply the mod where you remove the menu bar and remap the keys that was for the HTC One X (Internation/Tegra3) to my HTC One X (AT&T) and what happened was it would freeze at the HTC One Beats Audio screen and not do anything. Tried going to Recovery as well and nothing. So I thought. What I had to do was unplug my phone from USB, hold down power for about 7 seconds until screen goes black, immediately after screen goes black, release power button and start to hold down volume down button, this should get you to the Recovery menu. From here what you will need to do is go into FlashBoot, and then from ur PC (or mac... hopefully PC though) you need to relock your BootLoader, and get stock recovery (if you changed it). After this reboot and then go back into Recovery, FastBoot, and connect to PC. Now download the AT&T RUU (i used the newest, 1.85) and run through those steps. After this is finished phone should boot fine and your expensive device is saved.
Oh by the way, I'm an evolving Noob. Just started to do anything ...interesting... with my phone today, crap went down, and using these steps I was able to fix it, so if I am off on some of my steps or unclear, just comment please and I'll try and correct myself or giver farther details on what I did.
-Good Luck
Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?
achoj said:
Thanks for the replies but I think my situation is further complicated by the fact that my phone is a Rogers phone. I know the RUU is 1.73.631.1 but I don't know if a stock recovery is available for Rogers yet. It sounds like all I have to do is find the correct RUU and flash it to the phone.
TrueLandon, you said after you held the power button down for 7 seconds you could put the phone into recovery mode. Would that be the same thing as the bootloader menu (where you can select fastboot, factory reset etc)?
Click to expand...
Click to collapse
Yes, sorry if I were unclear, still trying to learn the lingo and technical terms , and yea, that's what you would need then is the RUU for Rogers, but I think the other steps should work for you.
I'll PM you a link to 1.73 RUU for Rogers
achoj said:
Hi. This is the first time I've tried to install custom rom's on my phone so bear with me. I followed a post (since I can't post links yet just google: CyanogenMod 9 (CM9) for HTC One X is Here. It's the first link) detailing how to install CM9 on the OneX. Everything worked up until step 16 where you have to boot into recovery mode. When I select recovery mode from the bootloader, the phone just tries to restart and gets stuck at the HTC loading screen with a message underneath saying that this ROM is not official etc.
Is there an easy way to try and fix this and make it work properly? I've tried erasing the fastboot cache and that didn't make a difference. At this point I don't really care if I have to erase everything and just go back to what I had before. The phone doesn't show up as a drive on the PC when I plug it in.
Any help would be great!
EDIT: Is it even possible to do a factory reset at this point?
Click to expand...
Click to collapse
The facepalm is significant and this makes me wish HTC forced carriers to label the S4 One X as the One XL.
If your bootloader was unlocked, lock the bootloader and run the RUU from fastboot.
Thanks for the replies guys. Truelandon sent me the RUU that I need for my phone but there's no .exe file in it. I was just wondering if I can somehow use these files and flash my phone with this RUU. Most of the files that I ended up downloading are disk image files.
Addition to the issue
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.
manmeets said:
I flashed a cm9 rom on my hox (international version). Its working fine but the only issue is that i want to install black and cyan theme to it and when i try to flash it and the moment i hit recovery in boot loader my phone restarts and comes back normal.so i can't enter cwm to flash the theme.
Click to expand...
Click to collapse
Wrong forum you have the international one x the is the one xl forum so we can't really help your phone has completely different partitions.
The only thing I would suggest is to reflash your cwm and see if it helps.
Sent from my HTC One XL using Forum Runner
This is my first Android and I've been reading a lot and following some guides to eventually get to my goal of having cleanrom installed.
So far I've rooted, unlocked the bootloader, and attempted to install clockwork recovery mod...I think.
Everything went fine until the clockwork business. I followed this guide(XDA wont let me post the URL... google "clockwork on htc one x" and it's the first link), and everything worked until the last step. Which is booting into clockwork recovery.
When I go into my bootloader and highlight recovery and press power the phone turns off, the comes up with the HTC screen. Then it goes black and comes up with another HTC screen with red lettering at the bottom that says something like "this is a non-public htc build that isn't safe blabla..." then it turns off. If I try to reboot the phone stays in this loop.
To get out of it I have to go into my boot loader and boot normally to the phones OS.
From where I am now, what is my next step to get to my goal of cleanrom?
Sounds like you installed clockwork for the international one x. Look for either twrp or cwm in our development section. Either one works and will solve the problem.
Someone needs to change the guide or add a sticky...
DL Goo Manager from the Play Store...hit the settings button and install recovery from there. You'll have the newest TWRP
Thank you so much gunny and rquinn. I'm trying the goo manager right now. I appreciate your assistance.
I seriously want to go to att corporate hq and beat someone's head in for not calling this phone the one xl. Causes lots of problems.
I've just gone through all the steps to unlock my bootloader, gone through all the HTCDEV bit with no issues, the bootloader is now unlocked. I've also managed to flash my ROM with the CWM Recovery image and as far as I know that was successfull too, i've now come to booting into recovery and the phone hangs on the HTC splash screen and doesn't appear to want to go any further. I've tried to access recovery both by doing it manually (Pull the battery, restart holding vol down etc etc), and also via the One X All-In-One Kit with the same results. Any idea chaps....
Andy
bettsaj said:
I've just gone through all the steps to unlock my bootloader, gone through all the HTCDEV bit with no issues, the bootloader is now unlocked. I've also managed to flash my ROM with the CWM Recovery image and as far as I know that was successfull too, i've now come to booting into recovery and the phone hangs on the HTC splash screen and doesn't appear to want to go any further. I've tried to access recovery both by doing it manually (Pull the battery, restart holding vol down etc etc), and also via the One X All-In-One Kit with the same results. Any idea chaps....
Andy
Click to expand...
Click to collapse
try using adb
from pc
adb reboot bootloader
Expert Help*****HTC Sensation XL Brick/Bootup issue PLS HELP
bettsaj said:
I've just gone through all the steps to unlock my bootloader, gone through all the HTCDEV bit with no issues, the bootloader is now unlocked. I've also managed to flash my ROM with the CWM Recovery image and as far as I know that was successfull too, i've now come to booting into recovery and the phone hangs on the HTC splash screen and doesn't appear to want to go any further. I've tried to access recovery both by doing it manually (Pull the battery, restart holding vol down etc etc), and also via the One X All-In-One Kit with the same results. Any idea chaps....
Andy
Click to expand...
Click to collapse
Bro, i am experiencing the same ordeal and i did what you did aswell.
I am using the Australian Vodafone region of the HTC Sensation XL with Android 4.0.3
HBoot is 1.28
Phone has been Unlocked and I have successfully rooted my device.
I'm stuck on HTC screen when i flash or recovery using USB.
If i soft reset and reboot, the phone will shutdown after HTC screen.
I can' even see my beloved Vodafone logo :crying:
My delimna first started when downloaded JRUMMY app called OVERCLOCK or something. I slightly adjusted the LCD density and frequency and then i used the inbuilt reboot option. From memory it was HBoot reboot or something similar.
Ever Since i couldn't boot up my phone and it was stucked at the Vodafone Logo.
I then used HTC one X all in one toolkit and the N66 super utility to tried boot the phone.
I tried flashing the recoveries within the tools but it won't work.
Now, those tools don't even recognise my Device when i tried to connect.
Calling all experts to assist in this matter. Thanks
1HTC1 said:
Bro, i am experiencing the same ordeal and i did what you did aswell.
I am using the Australian Vodafone region of the HTC Sensation XL with Android 4.0.3
HBoot is 1.28
Phone has been Unlocked and I have successfully rooted my device.
I'm stuck on HTC screen when i flash or recovery using USB.
If i soft reset and reboot, the phone will shutdown after HTC screen.
I can' even see my beloved Vodafone logo :crying:
My delimna first started when downloaded JRUMMY app called OVERCLOCK or something. I slightly adjusted the LCD density and frequency and then i used the inbuilt reboot option. From memory it was HBoot reboot or something similar.
Ever Since i couldn't boot up my phone and it was stucked at the Vodafone Logo.
I then used HTC one X all in one toolkit and the N66 super utility to tried boot the phone.
I tried flashing the recoveries within the tools but it won't work.
Now, those tools don't even recognise my Device when i tried to connect.
Calling all experts to assist in this matter. Thanks
Click to expand...
Click to collapse
Hi,
There is a Sensation XL forum, you should try posting this in that one
Jonny said:
Hi,
There is a Sensation XL forum, you should try posting this in that one
Click to expand...
Click to collapse
thanks will do. Can you please answer me then ?
ganeshp said:
try using adb
from pc
adb reboot bootloader
Click to expand...
Click to collapse
I'll try that.... I should have said that my phone is not rooted, and the only way I can get the phone to start is by popping the battery. Once it restarts everything is fine, I'm trying to root my phone as i have a couple of apps that require root acces, otherwise i wouldn't be too fussed about all this, but now i'm best part of the way there I want to see it through.
Andy
SORTED!
I re-flashed the rom with the CWM Recovery and blow me, it worked. Booted into recovery no problem. The first time I did it it must have not flashed properly. I've now since flashed my phone with SuperSU and now have root access.. Alls fine and dandy, and I have also installed Cerberus in the root which is why I wanted root access in the first place.
Thanks for all your help with this,
Cheers
Andy
Hello xda-forum/developers.
I'm new to this, so pardon me for asking a question that has been asked a million and one times before.
Just recently my older brother gave me an HTC One S (T-Mobile) he told me the only plot twist was that it wouldn't go past the "HTC quietly brilliant" screen and so, my question here is... is this fixable? I am able to get it to the Boot-up menu and everything.. only other problem is that my computer won't read it unless I go into "Mount and Storage" -> "Mount USB Storage" but even then it shows up as "Removable Disk (E" , but other than that, there's nothing more that I am able to do.
Sorry if I'm leaving anything out, I'm new to this so I don't have much knowledge of what to do. I've watched tutorials of other "HTC One" but non were "HTC One S". If you guys need any further information, just ask, please.
[By the way, the phone says "Tampered" "Unlocked" and the current Rom/Mod or whatever you guys call it CWM Recovery v6.0.2.9]
possible fix
First it needs to be S-OFF.
If it is I would update the recovery with a new TeamWin recovery you can download it Here.
just because that is the most up to date recovery for the device.
if you don't have them you will also need the ADB for windows. this is a great tool for installing it Here.
with the adb installed you can flash the new recovery to the phone. (instructions on TeamWin site)
Once the recovery is loaded, you can boot into recovery
first by holding the VOL down button and press and release the power button while keeping the VOL down button held to bring up the bootloader,
second press VOL down to select Recovery.
once the Recovery loads, select the advanced settings and select ADB sideload.
This allows you to load a new ROM which will allow the phone to boot.
ADB sideload instructions Here.
The ROM that you chose is very dependent on what Hboot version you are running. other than that it is up to you.
I had this problem when I first started to mess with my One S.
i also softbricked my device but so far my only problem is that i cant find a ROM wich runs with hboot 2.13 !?
and im new in the HTC ONE S area so i dont know the ROMs well so i would be very happy if u could help me to find a ROM wich i can run !
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.