Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

HTC One X need help to flash stock ROM... x-post from XDA

  • 15-04-2014 1:07pm
    #1
    coillcam
    Registered Users, Registered Users 2 Posts: 1,835 ✭✭✭


    I recently purchased a One X from ebay in the UK, On receiving it I realised that it has a custom nexus styled jellybean ROM and won't pick up a signal with any sim card I use. Unfortunately returning the phone isn't an option. I don't know if it had an EU rom or network branded one previously. I had a situation once like this in the past where I just ran the stock RUU on my old HTC sensation and it worked like a charm. Just not sure how to approach this one.

    EDIT: The seller just mailed me to say that its originally T-Mobile network.

    Here's all the info I know of that may be helpful.

    Its obviously rooted

    From the bootloader:

    Unlocked
    endeavoru pvt ship s-on rl
    hboot-1.39.0000
    microp-none
    radio-5.1204.163r.30
    eMMC-bootmode: disabled
    CPU-bootmode: disabled
    HW Secure boot: enabled
    Modem path: off

    Also it has Custom recovery - CMW based v6.0.2.7

    Android Version 4.2.2
    Baseband Version 5.1204.155.29
    Kernal Version 3.1.10-g3d29e5d adrian@fuzzy #2013082515 Sun Aug 25 14:13:56 CEST 2013
    Build no: tg_endeavoru-userdebug 4.2.2 JDQ39 eng.adrian.20130825.141556 test keys

    Any help would be greatly appreciated.


Comments

  • #2
    Julius Seizure
    Closed Accounts Posts: 459 ✭✭Julius Seizure


    Could be network locked, could be just a bad ROM although that's less likely. Do you get a popup telling you to insert network unlock code? I'd try and download another ROM, install it and then try again. I used to have a HOX so I'm glad to help, it's an odd phone for installing ROMs (you have to extract the boot.IMG and flash in fastboot)


  • #3
    Ballyv24
    Registered Users, Registered Users 2 Posts: 1,144 ✭✭✭Ballyv24


    coillcam wrote: »
    I recently purchased a One X from ebay in the UK, On receiving it I realised that it has a custom nexus styled jellybean ROM and won't pick up a signal with any sim card I use. Unfortunately returning the phone isn't an option. I don't know if it had an EU rom or network branded one previously. I had a situation once like this in the past where I just ran the stock RUU on my old HTC sensation and it worked like a charm. Just not sure how to approach this one.

    EDIT: The seller just mailed me to say that its originally T-Mobile network.

    Here's all the info I know of that may be helpful.

    Its obviously rooted

    From the bootloader:

    Unlocked
    endeavoru pvt ship s-on rl
    hboot-1.39.0000
    microp-none
    radio-5.1204.163r.30
    eMMC-bootmode: disabled
    CPU-bootmode: disabled
    HW Secure boot: enabled
    Modem path: off

    Also it has Custom recovery - CMW based v6.0.2.7

    Android Version 4.2.2
    Baseband Version 5.1204.155.29
    Kernal Version 3.1.10-g3d29e5d adrian@fuzzy #2013082515 Sun Aug 25 14:13:56 CEST 2013
    Build no: tg_endeavoru-userdebug 4.2.2 JDQ39 eng.adrian.20130825.141556 test keys

    Any help would be greatly appreciated.

    Did you have any luck unlocking this phone?


  • #4
    coillcam
    Registered Users, Registered Users 2 Posts: 1,835 ✭✭✭coillcam


    Ballyv24 wrote: »
    Did you have any luck unlocking this phone?

    Unfortunately not, stuck on the custom rom. Won't take the 2 T-Mobile ROMs that match that model.


  • #5
    Riesen_Meal
    Registered Users, Registered Users 2 Posts: 10,580 ✭✭✭✭Riesen_Meal


    coillcam wrote: »
    Unfortunately not, stuck on the custom rom. Won't take the 2 T-Mobile ROMs that match that model.

    What happens if you try to run the stock RUU file?

    Have you tried any other custom ROMs on it?


  • #6
    coillcam
    Registered Users, Registered Users 2 Posts: 1,835 ✭✭✭coillcam


    Fieldog wrote: »
    What happens if you try to run the stock RUU file?

    Have you tried any other custom ROMs on it?

    I can't remember the specific error code from the time but I think the RUU gave this error code after the file was pushed to the device: FAILED (remote: 12 signature verify fail)

    I remember googling it and the responses were try it again, try another RUU as it didn't seem to match or re-download. None of which work. I don't have the phone anymore to try but I never bothered with any other custom roms at the time. Wasn't picking up a network but would detect the sim so I gave up.


  • Advertisement
  • #7
    Julius Seizure
    Closed Accounts Posts: 459 ✭✭Julius Seizure


    coillcam wrote: »
    I can't remember the specific error code from the time but I think the RUU gave this error code after the file was pushed to the device: FAILED (remote: 12 signature verify fail)

    I remember googling it and the responses were try it again, try another RUU as it didn't seem to match or re-download. None of which work. I don't have the phone anymore to try but I never bothered with any other custom roms at the time. Wasn't picking up a network but would detect the sim so I gave up.

    If you still have it or will have it again you could do 
    Fastboot getvar cid

    The CID on the RUU has to .watch for it to take


  • #8
    coillcam
    Registered Users, Registered Users 2 Posts: 1,835 ✭✭✭coillcam


    Julius Seizure wrote: »
    If you still have it or will have it again you could do 
    Fastboot getvar cid

    The CID on the RUU has to .watch for it to take

    Yeah I know, I matched the CID to the correct RUU (T-MOB005). When I got the phone initially I didn't know what the OEM config was. The CID matched T-Mobile UK and the seller told me it was T-Mobile too.

    Actually thinking of it now I don't remember trying to write a different CID(or superCID) and push a different RUU. Should have at least tried this.


  • #9
    Julius Seizure
    Closed Accounts Posts: 459 ✭✭Julius Seizure


    Wouldn't have worked, there's no S-OFF for the one X like there was for the sensation because it had a tegra chip instead of a Qualcomm, it's still one of HTC's most locked down phones. So no SuperCID, no carrier unlocking without a code, no flashing radios, you always had to flash the boot.IMG in fastboot as recovery wouldn't flash it so you needed a computer to update a ROM.

    So glad I got a nexus 4 after it!


  • #10
    coillcam
    Registered Users, Registered Users 2 Posts: 1,835 ✭✭✭coillcam


    Julius Seizure wrote: »
    Wouldn't have worked, there's no S-OFF for the one X like there was for the sensation because it had a tegra chip instead of a Qualcomm, it's still one of HTC's most locked down phones. So no SuperCID, no carrier unlocking without a code, no flashing radios, you always had to flash the boot.IMG in fastboot as recovery wouldn't flash it so you needed a computer to update a ROM.

    So glad I got a nexus 4 after it!

    Such a pain in the hole. Actually I had a sensation in the past and loved it. Great phone at the time and very straight forward to tinker with.

    Currently have a Moto G and its an amazing piece of kit for the money. Thinking of a OnepluOne when manufacturing catches up with demand and it has a couple of months in consumer hands. Otherwise I'll probably wait until later in the year to see what flagship phones are available. Not in a rush to upgrade as 4G coverage is poor in Westmeath.


Advertisement