34 replies to this topic

[gavinlew]

dj_destruction, on 18 April 2012 - 01:08 PM, said:

Thanks gavinlew :-) downloaded in ten minutes excellent.

No problem - Happy to Help

[dj_destruction]

im still running the stock branded t-mobile rom and my hboot is still locked but my cid is "none" ??? any one else got this? run cmd "fastboot getvar cid" to get ur cid. My mid is showing as PJ4610000 you can check in cmd with "fastboot getvar mid" . If any one on a locked branded one x can check theirs and post would be great.

thanks.

Edited by dj_destruction, 18 April 2012 - 06:57 PM.

[Kiwizz]

I've rooted but mine also shows "none" and my MID is the same: PJ4610000
I'm on Optus in Australia.

dj_destruction, on 18 April 2012 - 06:22 PM, said:

im still running the stock branded t-mobile rom and my hboot is still locked but my cid is "none" ??? any one else got this? run cmd "fastboot getvar cid" to get ur cid. My mid is showing as PJ4610000 you can check in cmd with "fastboot getvar mid" . If any one on a locked branded one x can check theirs and post would be great.

thanks.

[dmlewis]

Gavin

Thank you doing this. I have been reluctant to try custom ROM until had a stock ROM to return to if I make a boo-boo.

Downloaded in less than 10 minutes.Will archive on my Box.com storage

[GuyAdams]

PaulOBrien, on 10 April 2012 - 01:40 PM, said:

Which version are you running?

P

I started on 1.26.401.5 but have since flashed a custom ROM based on the latest 1.29 OTA. There is however still an issue of firmware not being updated by the custom ROMs, like HBOOT etc due to S-ON.

gavinlew, on 17 April 2012 - 08:17 AM, said:

...Not tested or verified but TMobile UK RUU here ; http://kuai.xunlei.com/d/XQAAQPWZSHVF

Hope this helps.

Cheers

Gavin

gavinlew, on 18 April 2012 - 08:52 AM, said:

Here we go ; http://db.tt/RolbW6sN

Cheers

Those RUU's are for versiom 1.26.401.2 which is the T-Mobile RUU that doesnt OTA update. The version that came on the handset originally is 1.26.401.5 which will automatically update OTA (including your firmware, etc)

P.S. Apologies for the delay in response, for some reason I haven't received any notifications for the thread.

Thanks

Guy

Edited by GuyAdams, 14 May 2012 - 11:21 AM.

[EddyOS]

Flash the 1.29 RUU (to get the latest FW) then flash your ROM back on

[GuyAdams]

EddyOS, on 14 May 2012 - 06:45 PM, said:

Flash the 1.29 RUU (to get the latest FW) then flash your ROM back on

The WWE and Euro RUU's won't flash on a carrier branded device due to the different CID and there is no 1.29 RUU for T-Mobile, infact there is not 1.28 RUU either, as it was an OTA.

[EddyOS]

I know that, you were asking how to flash the new firmware as you were on 1.26.401.2 originally. If you flash the 1.29.401.7 RUU you'll get the bits you can't flash manually and then can use a new ROM to it's full potential

[GuyAdams]

EddyOS, on 15 May 2012 - 08:00 AM, said:

I know that, you were asking how to flash the new firmware as you were on 1.26.401.2 originally. If you flash the 1.29.401.7 RUU you'll get the bits you can't flash manually and then can use a new ROM to it's full potential

I wish it were that easy, unfortunately there is no T-Mobile UK 1.28 RUU at the moment, let alone a 1.29!

But still doesn't help with the original debrand question (change CID). It look like we are going to have to wait for S-OFF to do it.

[EddyOS]

So you're didn't get your handset originally on 1.26.401.2 as you answer Paul on the previous page?

GuyAdams, on 14 May 2012 - 11:21 AM, said:

I started on 1.26.401.5 but have since flashed a custom ROM based on the latest 1.29 OTA. There is however still an issue of firmware not being updated by the custom ROMs, like HBOOT etc due to S-ON.

But this says you were on 1.26.401.2 (which is unbranded) so you can just flash the 1.29.401.7 RUU

[GuyAdams]

EddyOS, on 15 May 2012 - 03:42 PM, said:

So you're didn't get your handset originally on 1.26.401.2 as you answer Paul on the previous page?


But this says you were on 1.26.401.2 (which is unbranded) so you can just flash the 1.29.401.7 RUU

My device came with 1.26.401.5 but I flashed a custom ROM pretty much straight away thinking there would be a T-MO RUU available but the only one I can find is 1.26.401.2 which will work with my T-MO One X but doesn't OTA update, so I can't get the 1.28 OTA.

[EddyOS]

Right, so you have an unbranded handset. If it was a T-Mobile branded one you would've been on x.xx.110.x out the box

So you can flash the 1.29.401.7 RUU without issues

[GuyAdams]

EddyOS, on 15 May 2012 - 07:21 PM, said:

Right, so you have an unbranded handset. If it was a T-Mobile branded one you would've been on x.xx.110.x out the box

So you can flash the 1.29.401.7 RUU without issues

Apologies, I have got the numbers missed up, what I meant was 1.26.110.2.

What I need is either 1.26.110.5 or 1.28.110.9 or 1.29.110.7, although I think the later is dreaming a little

Sorry again for the mix up.

[psthomas]

Hi Gavin, I'm trying to do exactly the same with my Voda One X, can you give me a step by step as to what you did as I am fairly new as this?

[rickywyatt]

could any one using this rom upload the build.prop found in system
thanks