Related
Anyone tried this yet? I know the boot loader is locked. But since rogers from is official as well. That should work right? Any one has directions on how to do it?
Just run the exe? Any Mac versions?
Please don't post in the development section with this kind of stuff. Thread moved.
In answer to your question, no it won't work. Model numbers between at&t and rogers differ slightly and the ruu looks for model id to verify that it is right to flash. This is by design and is good so that some moron can't flash a vivid RUU on a HOX or flash int'l ruu on an at&t
Sent from my HTC One X using Tapatalk 2
Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?
hexproject said:
Thanks. I am a noob when it comes to htc. For xperia s. We can load other similar roms with no root or bootloadet unlock. So the only way to load rogers onto att is to wait for bootloader unlock then? Can anyone verify this?
Click to expand...
Click to collapse
Nothing to verify. This has been HTC's model for quite some time.
Sent from my HTC One X using Tapatalk 2
So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.
hexproject said:
So only way is bootloader unlocked and then flash with official rogers rom if you are on att? So thats why everyone is all pissed about att version not having bootloader unlocked. Thanks for your info.
Click to expand...
Click to collapse
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2
Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?
mikelebz said:
Are the bootloaders between Rogers and AT&T different? I know that when you try to unlock the bootloader, it gives you a string of numbers that you enter prior to unlocking the bootloader. If the bootloaders are the same, then theoretically us AT&T users ought to be able to use a string of numbers from a Rogers phone just to make the tool happy. Right?
Click to expand...
Click to collapse
Nope. Its a hash of some sort. Its different everytime you run the command.
Sent from my HTC One X using Tapatalk 2
Pirateghost said:
Unlock bootloader
Flash cwm recovery (don't have one yet)
Flash rom
Profit
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...
hexproject said:
I dont want custon rom just yet, Just rogers official rom to work on att . Do i still need cwm? No one has tried putting the rogers zip file in the root and update that way?.. You can download all the official rom from the development section. Iatt is in exe and rogers is in zip file...
Click to expand...
Click to collapse
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....
Pirateghost said:
you're spinnin your wheels here mate.
i KNOW how it works with RUUs and the zip files they produce....i have been around for at least a few months with a few HTC devices.....
JUST having root DOES NOT mean that you can miraculously flash any file you want
unlocking the bootloader would allow you to modify the rom zip that is produced by the RUU and fastboot flash it, but you will not be able to flash the radio that comes with it, essentially all you could flash is /system and /boot
you dont think that every possibility was attempted while working on the Vivid? this aint my first rodeo.....
Click to expand...
Click to collapse
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........
beaups said:
These RUU files are funny. Way back in WM days, with the HP 6315 (htc built) I was the guy that hex edited the RUU executable to bypass the model check. I had/have VERY little programming experience but it only took me a few hours to figure it out. I wonder if this method is still feasible..........
Click to expand...
Click to collapse
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip
That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.
hexproject said:
That would be cool. I came from sony and samsung and this is my first time with HTC. So thanks for all these info. A great help with people who just want to use stock roms from other carrier.
Click to expand...
Click to collapse
after unlocking bootloader, and getting a recovery installed, you can run stock rom from any other carrier, just from a CWM version
I like having several stock rooted roms in CWM format, so I tend to knock em out as soon as I can....and get them into your hands
Pirateghost said:
have a crack at it, but the zip file actually contains the signature and the model check, not the exe.
if you can modify the zip file without changing the signature, then by all means, please do....
or someone could just unlock the bootloader and it wouldnt matter if the zip is signed or not, just need to edit the checks and remove the hboot, recovery, radio, adsp, etc from the zip
Click to expand...
Click to collapse
My skills are rusty. But back when I was dealing with the WM RUU I bypassed both the model check and also the CRC check right in the executable. Granted these security measures have come a LONG way since then, but sometimes people overlook the obvious, you know?
If the phone gets S-OFF you can set SuperCID and flash away.
Ok so I have a One X with AT&T and I am just asking for some clarifications.
1.) I am on software version 1.73, which is from what I understand to be root-able, but software version 1.85 isn't root-able?
2.) After reading around on here people keep referring to them re-locking their boot-loaders after they unlock them through htc-dev, so my question is do you need to re-lock it afterwards? Also, what is the reason why?
Any answers are appreciated, please inform me if I have blatantly missed something obvious or if i'm in the wrong place.
Can I ask Red or one of the other mods to please move this to Q&A, it seems I neglected this
And Red are you really 15?
1.85 has not yet been rooted. Correct. After gaining root, super cid and unlocking bootloader you only need to relock it when needing to use a ruu, say to upgrade to 1.88 or if you just want or need to go back to stock. After ruu you can go back and re unlock it since ruu won't affect super Cid. Hope this helps
Sent from my HTC One X using xda premium
Thanks for the answer.
One more thing, are you able to flash CWM and roms after unlocking the bootloader the first time? Or do you have to run the RUU to be able to?
Once bootloader is unlocked you can flash your recovery. The latest twrp recovery is choice since it the only one with functioning USB at the moment. If you decide to relock and run a ruu remember to unlock and reflash your recovery of choice too. The only time u need to ruu (typically) is to upgrade or downgrade firmware or fix a soft brick so you don't NEED to ruu at all but it's a good idea to upgrade for the bug fixes from 1.73.
Sent from my HTC One X using xda premium
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk
You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.
To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk
Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk
redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita
timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only
What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita
lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root
Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita
timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.
Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app
hi guys,
i've a htc m8 verizon branded and I'm asking if i can rename the model ID to use with stock rom such as european rom. is it possible?
thanks
Peuf said:
hi guys,
i've a htc m8 verizon branded and I'm asking if i can rename the model ID to use with stock rom such as european rom. is it possible?
thanks
Click to expand...
Click to collapse
If s-off you can. But not sure that's necessary as once s-off you could flash the intl firmware and then a custom intl (stock rom). If you attempt to fully convert by changing mid and cid and then ruu you likely won't succeed. There's more to it than that.
Sent from my XT1575 using Tapatalk
dottat said:
If s-off you can. But not sure that's necessary as once s-off you could flash the intl firmware and then a custom intl (stock rom). If you attempt to fully convert by changing mid and cid and then ruu you likely won't succeed. There's more to it than that.
Click to expand...
Click to collapse
ok, thanks for your help. Yes i'm s-off and I've changed teh mid to 0P6B100 and cid to supercid but you're right, i get error everytime i try to flash ruu.
and on top of that, i cannot revert back to verizon mid with the mid changer thing. now i'm stuck with a no rom m8 'coz none of all i've tried did work, neither zip flashable ruu nor the exe one
a little help please
Peuf said:
ok, thanks for your help. Yes i'm s-off and I've changed teh mid to 0P6B100 and cid to supercid but you're right, i get error everytime i try to flash ruu.
and on top of that, i cannot revert back to verizon mid with the mid changer thing. now i'm stuck with a no rom m8 'coz none of all i've tried did work, neither zip flashable ruu nor the exe one
a little help please
Click to expand...
Click to collapse
So this is usually what happens. I can help you back out of it if you want using teamviewer if you are game. The partitions from a Verizon to a sprint to an intl m8 aren't the same. That's the problem.
Sent from my XT1575 using Tapatalk
dottat said:
I can help you back out of it if you want using teamviewer if you are game.
Click to expand...
Click to collapse
yes I am, the thing is, i'm on mac os x. adb and fastboot cmd are working great but if you plan to use shell cmd I'm not sure it will work though
I think The same happened to me
I'm bringing this over from the HTC One help thread as instructed
I'm on Metropcs and wanted an HTC One GPE
Bought an unlocked verizon HTC One M8
Rooted it with kingroot, then unlocked the bootloader and s-off with sunshine.
Was in the process of changing the model id by flashing it with Golv's MID changer when the usb cord was pulled from the computer (I'll take that to the appropriate thread for THAT discussion)
Now the phone only comes up in bootloader mode, but I have no options (reset, reboot etc) it only says RUU where my options were.
ADB won't detect the phone however fastboot will and when I do fastboot getvar all I seem to have all the original stuff. (Except the CID has been changed to GOOGL001)
I can fastboot reboot-bootloader but the screen comes up as if I did fastboot oem rebootRUU except that there is a triangle in each corner of the screen with an exclamation mark in them.
Yes this is my first time trying anything like this.
Any ideas would be appreciated.
heinzdb said:
I'm bringing this over from the HTC One help thread as instructed
I'm on Metropcs and wanted an HTC One GPE
Bought an unlocked verizon HTC One M8
Rooted it with kingroot, then unlocked the bootloader and s-off with sunshine.
Was in the process of changing the model id by flashing it with Golv's MID changer when the usb cord was pulled from the computer (I'll take that to the appropriate thread for THAT discussion)
Now the phone only comes up in bootloader mode, but I have no options (reset, reboot etc) it only says RUU where my options were.
ADB won't detect the phone however fastboot will and when I do fastboot getvar all I seem to have all the original stuff. (Except the CID has been changed to GOOGL001)
I can fastboot reboot-bootloader but the screen comes up as if I did fastboot oem rebootRUU except that there is a triangle in each corner of the screen with an exclamation mark in them.
Yes this is my first time trying anything like this.
Any ideas would be appreciated.
Click to expand...
Click to collapse
Same thing I offered the guy abovw
Sent from my XT1575 using Tapatalk
ok, so let's do it then
seems like finally I figure out how to fix it. I was able to bring back the verizon's MID by using the shell command and then flash a verizon's rom and firmware without any issues
Fixed it!
dottat said:
Same thing I offered the guy abovw
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Thanks so much for your offer, but someone told me about another post of yours using ruuM8_TWRP_2_7.zip and that solved it! So either way you're a great help!
Now is there a way I can get this phone's hotspot to work on the Metropcs plan? (That's what started this debacle)