Hello fellow One-X'ers, I am coming from a long line of Samsung devices and have only had one HTC phone in the past, (HD2).
I cant for life of me figure out how to root this phone, I have tried the conventional method, alternate root method, im getting nothing... Bootloader will not unlock through htcdev (which it says to do in half of the root how-tos), i always see error 160 invalid MID...
I have installed and updated the following:
-Java
-HTC Mobile drivers as well as sync
-SDK
-Fastboot
wtf am I missing here? I just want to get a new rom as this sense stuff absolutely sucks. Yes I have searched, yes I have read...
What phone have you got? If I remember correctly the "Error 160" / "invalid MID" responses are returned when you try and use HTCDev to unlock the AT&T One X (actually the One XL) which doesn't support unlocking the bootloader in that way.
Boot into the bootloader and check the model name displayed at the top of the screen: if it says "evita" then that's your problem, and you'll need to head over to the forums for your particular device to get some help because none of the stuff in this section will work - http://forum.xda-developers.com/forumdisplay.php?f=1538
If the bootloader shows "endeavoru" then you are in the right place, but in that case I don't know what the problem is.
Uninstall HTC sync, keep the USB drivers mind.
Sent from my HTC One X using Tapatalk 2
Related
hi ive been having some problems trying to root my htc one x phone on telus (in canada). unlocking the bootloader worked but when i tryed to do fastboot flash recovery in command prompt it would say error. ive tried other methods to get the recovery to work and to get superSU on my phone so that i have the root but none seem to work. can anyone help me find out what im doing wrong and how to fix it? also when i tried to do the recovery the first time it sent me to a black screen with a green loading wheel over a phone not moving, then a few seconds later it send me to another black screen with a phone and a red caution sign, i dont know what this means but i knows its not helping. any progress will do thanks
Umm isn't the Telus the dual-core version? This is the forum for the International One X. Despite your device being known as the One X, it's the One XL here.
You can find a guide for your phone here:
http://forum.xda-developers.com/showthread.php?t=1814914
PS. do not install any ROMs from this section, you will brick or even possibly hard brick your phone.
Seriously, I'm so pissed off with HTC right now that I just wanna throw this piece of crap into the wall. This is the last time I'm buying a HTC phone unless they unlock bootloaders from the start.
So I relocked my phone few days ago because I wanted to install JellyBean, but it turned out that EVERY damned mobile operator except mine have released JellyBean. So now I wanted to unlock it, downloaded the tools (http://forum.xda-developers.com/showthread.php?t=1604439). Got my Token ID, downloaded the unlock file, but when I try to unlock it I get some weird error (sending "unlocktoken" <0 KB>... FAILED <unknown status code>)
And that's where I'm stuck.
So I thought I need to download and install OpenSense SDK. Downloaded it, but of course, when I start it nothing happens, it just closes itself.
And then there are a bunch of idiotic errors on HTC website like "You have exceeded the allowed page load frequency." when I try to scroll from one page to another. My god.
The token id that you are sending to the device
Seems to be corrupt. It can not be of 0kb size. Try tree downloading it.
Sent from my unlocked HTC One X using XDA premium.
:angel: patience man. are you the one who unlock your phone before? if yes. you can use the unlock code.bin you used when you first unlocked your phone.
Does samsung unlock their bootloaders from the start?
No one unlocks their bootloaders from the start, not even Nexus devices, but they have very easy bootloader unlock methods. HTC gave a half-assed, convoluted method and Motorola is even worse than HTC. The bootloader unlock process of HTC is fine, nobody expects them to ship phones with unlocked bootloaders, but the unlock should result in S-OFF. There's no reason it should remain S-ON.
Sent from my Desire HD using xda premium
Yes, I was the one who unlocked the phone from the start. I never had any issues, it's just after I relocked it that it suddenly is refusing to unlock again.
The unlock code is actually 1kb, not 0. Dunno why it says 0 in the error.
Just make sure you run the unlock command in fastboot mode not hboot mode.
I was in fastboot usb mode when I tried to do everything.
Alright, now that I cooled down. I'm gonna see what I can do again.
I got it working, managed to unlock the exact same way I tried before, with the exact same file, just with the updated tools that were released yesterday.
Sometimes fastboot can be a pain in the A$$.
Might have been the same problem you faced
If i enter an incorrect command in fastboot (i.e. I spelt something wrong) it will not accept any more commands for the rest of that session until i reboot.
When flashing the unlock token mine also gives me an error but it still works
If I try an invalid fastboot command then try to flash the token. I get the same error but it doesn't work.
Figure that
Personally i think its just poor software on the one X, i point the finger at the device because i had no such problems with these types of commands on the Nexus 7 & Nexus One
there are commands that when tried will actually crash the phone rather than giving an error, such as fastboot oem writesecureflag 0 (code for turning S-OFF)
you would expect an error saying not allowed or something but instead the phone just locks up forcing you to hard reboot
Sent from my HTC One X using xda app-developers app
Hi Folks
Just Got my One X today from Virgin Mobile and I want to install Open EU 3,14 JB on it. Now according to Virgin they say they use Non-Branded software on the One X, but it still has the Virgin Mobile symbol on Boot up.
So I downloaded the RUU charged my device, Installed the HTC USB Drivers, put the One X into "USB Debugging" On, It got half way through the flash itself, then said "Incorrect Device Signature".
Any advice how I can install JB.
Thanks
Ok, Ive read around the forums and it seems I need to S-OFF my ONE X, but after looking at the thread.. it appears that I either have to pay for the tool or its not possible yet.. but is there something i can do to Temporarily do so i can install 3.14 JB.
Cheers
Hello,
I tried to help out a friend with rooting a Desire Z. He used the guide on http://forum.xda-developers.com/showthread.php?t=1178912. He was still on stock and everything and the guide pointed to that to do first.
According to him everything went fine untill he got at point "I - 4a) Manual Downgrade". After reviewing the files he had used it seemed to me that he had used the G2 version of PC10IMG.zip instead of the Desire Z version (could see it when inspecting how large the file was)
He told me that all other steps before (the temp rooting etc etc) was no problem. And after he rebooted his phone the install of PC10IMG started. After the first reboot however the phone stuck.
The situation now is a follows:
* phone does not boot. It gets stuck at the white screen with green HTC letters/logo and then does nothing
- S-ON
- Phone does boot into Hboot (version HBOOT-0.82.0000)
- RADIO-26.02.01.15_m2
- eMMC-boot
I can get into Fastboot and can send commands thru adb to the phone. However commands that try to flash result in a FAILED blabla signature. Probably since its S-ON status
SDcard is recognized (finally) and I managed to make it accept a stock rom. Many other .zips fail. System says no image or wrong image when searching for them.
I suspect the phone has a wrong bootloader (?) and will only accept G2 roms (wich would not be right since its a Desire Z (?)).
Things I tried so far:
* flash a stockrom: It did do something (saw the blue "loading" bar in the bootloader). After it's done it verifies and returns to the bootloader. The I reboot but it still hangs at white screen with green letters HTC/logo
* tried to flash other roms by putting then on the SD. Gives message no image or wrong image
* tried with adb with fastboot. Nothing is accepted.
Is this phone beyond DIY repairs? Advice or tips would be greatly appreciated (since this crap costed me already a full saturday and sunday)
Many thanks in advance!
(PS: I should have the basic knowledge about rooting, adb and such. Also I rooted my own desire Z succesfully already)
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
demkantor said:
use THIS RUU directions will be there
now DOWNGRADE AGAIN which you already know
then follow either THE XDA WIKI or THE CYANOGEN WIKI or STRAWMETALS PDF GUIDE
Click to expand...
Click to collapse
Thanks a lot for your reply!
I tried what you suggested 3 times and this is the outcome:
The program starts up fine. Checks the phone with no errors. After a few install screens the phone reboots into a black screen with silver letters HTC (same as seen with adb/fastboot I think?). It starts wiping userdata. Then it says "busy sending"; goes all fine.
The it gets to the point sending "signature" (not sure if I translate correct. I have a dutch version or at least the install was in dutch).
And after a while I get:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
during install it said I had image version 1.00.000.0 and asked if want to update to 2.16.531.6
Anymore advice or sugestions I could try?
Thanks in advance for your answer!
[EDIT]
Seems I can go into some kind of recovery mode (choosing recovery from menu >> gives black screen with greenish icon >> gives red triangle
at that screen I do volume + and power and it gives me a menu in wich I can choose update from SD. Not sure if that can help me in any way? Maybe there is some .zip I can install and reset everything back to factory or something?
Tried already to select something there but gives an error:
(in yellow line) E: Can't mount /cache/recovery/command
Sounds serious tome
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
demkantor said:
Then you'll need the ruu for your model phone, got to HTC.com, find support, look for desire z, then find downloads, follow same steps as before
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Tried quite a lot of RUU versions but everytime the same damn message:
ERRORCODE: 130 (model-ID error)
Get right updateapplication and retry
Tried to get unlocked bootloader with the tool from HTCdev but that gave me a message ERROR[191]: ROM not supported
Anything else I can try out? (going to try and see if I can get something of a rom thru a goldcard but my hopes dwindle by the minute
Thanks in advance for any help/advice
[EDIT]
After hours and hours of reading I can only think of 2 things myself:
1. somehow the emmc is defunct (broken or totally messed up beyond flashable)
2. it has a wrong radio version (= bricked beyond DIY repairs as far as I could read)
Therefor I descided to contact a company that can JTAG the phone and restore it to its glory. What is a reasonable price for such?
If anyone else has still some tips I'll keep watch of this thread
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
demkantor said:
You can't use an older version of the software/firmware so you would need the latest from HTC, if the phone already has the latest installed then you would need a gold card to change the cid. Problem is, as far as I know, you need to at least a functioning adb access to make a gold card.
Being its hard to the version that you were running the state your phone is in, my guess you are at the latest ota, so if there was a ruu that came out for it that wasn't an ota then that will probably be the only one that works. Its a long shot, but you could call HTC (don't mention rooting just say you picked up the phone at it was like this) and ask for a link to the latest ruu so you can try and fix it, even if you're past warranty they should point you in the right direction
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks a lot for your advice Demkantor
According to my friend he checked for OTA updates a few days ago (was his motivation in the first place to unroot and flash a custom since he was pissed that his great device didnt get much love anymore from updates and after seeing my Desire working on a custom hehe)
I checked out the RUU versions and also read that they kinda only work if it essentially updates the device (checked the site http://shipped-roms.com/index.php?category=android&model=Vision.
Tried a lot from there but only the WWE versions (CID of gsm was one of those numbers that indicated the gsm is unbranded)
For the sake of it I did make a goldcard and tried to use the extracted rom from an RUU. No luck. It sees it, sends it but fails at checking after that and returns to Hboot. Had a hope that the downgrade (step before perm root) was kinda succesful...
Gonna give it one last try with one of the none WWE versions with the lastest version number to see what it does.
I'll keep you posted!
PS: Damn I wished Gigabyte would make phones! I bet they'd put in some kind of recover rom in case the **** hits the fan hehe
I followed some instructions I read up and found online. I couldn't get the clockwork mod to work, every time I go into recover it get the "This build is for development purposes only..." Red text and in the bootloader at the top top it says ***tampered*** and ***unlocked***.
I ran the fastboot oem lock, and now it says ***tampered*** and ***relocked***.
Is there any way to restore it back? I cant update my Android OS because it gets stuck at that red text error.
The phone is originally locked with Telus(Canada) but I used a sim unlock to move it to my carrier Fido(Canada)
Just as a side note, I can still use my phone properly its just that bootloader stuff isnt working
I think you need to run ruu for the bootloader to work properly again.
Although you need fastboot to get the right ruu..(version number) so I'm not sure how I can be of help
Sent from my HTC One X using xda app-developers app
If anyone can point me to the correct files or a tutorial on this RUU that would be greatly appreciated
Please close this