Database Users

[Q] Flashing non T-Mobile roms on MyTouch 4G

Greetings,
I have purchased a MyTouch 4G from The States that was on T-Mobile and I have intentions on using it here (Canada) with Mobilicity, which is also on HSPA 900/1700/2100. I intend to flash either a stock Panache rom (which is the Canadian version without the T-Mobile stuff), RoyalPanache or I might go with RoyalGinger or something of that nature. I came across this in the Ultimate Rooting Guide:
[...]It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
Click to expand...
Click to collapse
in this Topic
I just wanted to check that I understood correctly. Am I correct in my understanding that I would need to do ultimate root in order to set Super CID so I can flash any of the (non T-mobile) roms I mentioned? Or to put it another way; is the ultimate root my only option? I only ask because I'm quite nervous about rooting and guides such as this seemed to be more friendly...
Thank you!

I am trying to find any information on flashing the Panache Canadian ROM to US HTC Glacier that has no recovery and is not rooted. I can't find an RUU.exe anywhere. I don't understand why nobody has responded to all the Mytouch 4G questions! ALiens abducted them. I've been looking for hours.

You need a goldcard to attempt it, and you can as well just try instead of waiting for answers - in the worst case, it'll fail and won't flash.

RootaToota said:
I am trying to find any information on flashing the Panache Canadian ROM to US HTC Glacier that has no recovery and is not rooted. I can't find an RUU.exe anywhere. I don't understand why nobody has responded to all the Mytouch 4G questions! ALiens abducted them. I've been looking for hours.
Click to expand...
Click to collapse
maybe it's because some of us have busy lives outside of xda

saranhai said:
maybe it's because some of us have busy lives outside of xda
Click to expand...
Click to collapse
Way to speak for thousands of people. And what a nice response as well...douche.

If you already have S-OFF you can flash Panache-based custom ROMs just fine.
If you want to flash the completely stock Panache RUU or PD15IMG.zip, and you have S-OFF, then you may need SuperCID or a gold card.
The RUU files are here:
http://forum.xda-developers.com/showthread.php?t=1216076
If you flash a RUU after rooting by root.sh, you'll revert to S-ON in the bootloader. This is not great with a Gingerbread RUU, because then you will have to go through a more complicated downgrade procedure if you ever want to re-root.
If you use the gfree "ultimate root" S-OFF method, then you will get to keep your S-OFF after flashing any RUU. If you have a ROM without root but you're still S-OFF, then you can use one of the files here to install ClockwordMod recovery and get a simpler route back to root:
http://forum.xda-developers.com/showthread.php?t=1200147

What steps for wifi tether only?

Phone has S-ON and 2.18.001. I just need the wifi tether app, so what exact steps should I take to get me only that app? Thanks.

You need root, please search.
http://forum.xda-developers.com/showthread.php?t=1473373

Thanks. The problem I was having was did I only need S-Off or root or both. Also I didn't know about if I needed the watermark thing. So I needed info to allow me to get that wifi app and not any extra steps. Let me see what I can do.

brentkhack said:
Thanks. The problem I was having was did I only need S-Off or root or both. Also I didn't know about if I needed the watermark thing. So I needed info to allow me to get that wifi app and not any extra steps. Let me see what I can do.
Click to expand...
Click to collapse
The easiest way to get Hotspot working is to actually pay for it . . . that being said:
You just need to unlock the bootloader using the HTCDev.com method, and install a custom recovery. You can then flash superuser, which will provide root access on your current ROM.
With the unlocked bootloader, you don't need to be S-OFF to get root.

Captain_Throwback said:
With the unlocked bootloader, you don't need to be S-OFF to get root.
Click to expand...
Click to collapse
OK captain, I gotta ask. If you unlock bootloader, doesn't that create S-off state? I'm kinda confused by that bit of quote. I know you know more about this than probably anybody, so I'm just curious.
(I haven't messed with any of the new stuff, I still have .76 eng bootloader from 17mo ago, ...I'm only asking out of curiosity and trying to keep up)
Thanks
Sent from my PC36100 using xda premium

After a few hours and help from here it is done. Thank you all.

scottspa74 said:
OK captain, I gotta ask. If you unlock bootloader, doesn't that create S-off state? I'm kinda confused by that bit of quote. I know you know more about this than probably anybody, so I'm just curious.
(I haven't messed with any of the new stuff, I still have .76 eng bootloader from 17mo ago, ...I'm only asking out of curiosity and trying to keep up)
Thanks
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Nope. Not with the HTCDev.com unlocking process. It'll show "UNLOCKED" at the top of HBOOT, but it will also still say "S-ON". And you can still have a custom recovery, and flash ROMs.

root help

my wifes g2 broke so i got a new one, whats the best way to root now? its up to date on updates?

You can use the guide here.

Or if that's too much of a read: http://wiki.cyanogenmod.com/index.php?title=HTC_Vision
(PS: You're most likely going to be using the G2 Gingerbread unlock since I doubt a new one came with Froyo).

Read through that didn't know if there was different way because of the unlocked bootloader from htc

reeshmd23 said:
Read through that didn't know if there was different way because of the unlocked bootloader from htc
Click to expand...
Click to collapse
Htcdev unlock is pretty worthless compared to "ENG S-OFF"
Sent from my T-Mobile G2

kbeezie said:
Htcdev unlock is pretty worthless compared to "ENG S-OFF"
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Thats true and when u use HTC Unlock u lose garanty.

You may simply follow the xda-wiki. I rooted my desire z (2.3.3) this July 12th (though it was bought in April, 2011). I don't think htc is intelligent enough to unlock the bootloader in the first place. They still want people to come and ask them for unlocking and then loose warranty. And the warning they have written on the page, my God!. I almost fainted reading their warning.
I don't know but if the bootloader is unlocked, you should be able to boot a custom rom directly by putting it in your sd card (I'm a NOOB so Devs please confirm this).
I was going o use their method but then I read about its futility and decided to go the hard way:laugh:

if you use the offical htc unlocked bootloader you loose your warranty right then, you have to go through many annoying steps to change roms, and being you don't have true s-off it you will be locked out of loads of other stuff
just root and give yourself an engineering hboot with true soff and you will be much happier, if you have a warranty and something goes wrong you can always go back to stock and send it in without their knowledge of ever being rooted
Sent from my HTC Vision using xda premium

RUU Bootloader update failure

I'm trying to update my ROM before I run the HTC unlocking steps on the bootloader section. For the MyTouch 4G, it says I need to do it and my carrier is listed in the list (DAVE CA). It starts fine and then pops up with error 131 CID Error. The phone is stock and I haven't done anything to it yet.
Current version 2.09.1800.1
To: 2.32.531.1
Anyone know what is causing this CID error and how I can fix it?
Thx.

fruv said:
I'm trying to update my ROM before I run the HTC unlocking steps on the bootloader section. For the MyTouch 4G, it says I need to do it and my carrier is listed in the list (DAVE CA). It starts fine and then pops up with error 131 CID Error. The phone is stock and I haven't done anything to it yet.
Current version 2.09.1800.1
To: 2.32.531.1
Anyone know what is causing this CID error and how I can fix it?
Thx.
Click to expand...
Click to collapse
STOP!
Don't use HTC Dev. Are you on Froyo? If so, go to the development section of this forum and use the gfree thread (ultimate s-off) stickied there.
Everyone who goes through the htc-dev process comes back in here regretting it and goes ahead and roots the XDA way. Save yourself the trouble.

I assume you want to root your phone. Look up the "Mobilicity/Videotron Panache" thread.
If you don't want extra pain - don't use HTCDev unlock.

Jack_R1 said:
I assume you want to root your phone. Look up the "Mobilicity/Videotron Panache" thread.
If you don't want extra pain - don't use HTCDev unlock.
Click to expand...
Click to collapse
I'm still trying to figure out which one he has. He has using an RUU, so I can see now why you said that. Thanks Jack!
OP, clarify whether you have a myTouch 4g or Panache, please.

estallings15 said:
I'm still trying to figure out which one he has. He has using an RUU, so I can see now why you said that. Thanks Jack!
OP, clarify whether you have a myTouch 4g or Panache, please.
Click to expand...
Click to collapse
Panache. DAVE CA/Mobilicity version running stock Gingerbread. Was hoping that I wouldn't have to downgrade OSes but I guess I'll have to do that.
Thanks all.

You can avoid downgrading, but I strongly suggest you go that way instead of HTCDev-unlocking. It'll take very few ROM changes to get really annoyed by flashing boot.img manually.

Got it done following the dev guide.

Do not S-ON your edited HBOOT!

As there are more and more firmware coming, people will be installing them more and more... Same thing about people that wants to go back to stock. This thread could be considered useless and will make people say "yeah man, I knew it I'm not so stupid" that's OK! You're right.
I just wanted to remember that you shouldn't ever ever ever S-ON your HBOOT if it is edited by someone else! This will immediately brick your device, if you want to check do it. You need first to replace your current HBOOT with a stock one and then you'll be good to go.
@Sneakyghost:
* Before resetting Security to ON (S-ON) you MUST flash a stock/unchanged HBOOT! Your device will brick instantly if you set Security ON and reboot on a modified HBOOT!
Click to expand...
Click to collapse

In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk

superchilpil said:
In all the hboot threads it clearly states this
And it's not locking your bootloader that bricks it, it's s-on that does it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I thought it was if you: fastboot oem writesecureflag -3 it will check if it's a modified hboot.
Sent from my HTC One using Tapatalk

I knew That simply locking the hboot would have bricked the device
Sent from my HTC One using XDA Premium 4 mobile app

@superchilpil you were right, I've edited the OP now and it should be ok now... :good:

matt95 said:
@superchilpil you were right, I've edited the OP now and it should be ok now... :good:
Click to expand...
Click to collapse
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!

ieldra said:
Wow, I think I've read about 20 threads so far about this, and this is the first time I've seen this corrected... Lots of threads always mentioned locking the bootloader as the issue if you don't have stock hboot.
I actually had a few questions about this,
1. Does the hboot version have to match that of the firmware ? ( 1.54 for 2.24.x.x for example ?) or does it simply have to be any stock hboot ?
2. Are there any differences between hboot for various carriers ?
3. I've read multiple times that running an RUU will not allow you to downgrade unless you have superCID, I don't understand this. I thought the RUU wouldn't run if the CID didn't match. From what I had understood previous to reading that is simply that an RUU cannot be used to downgrade the firmware or the hboot version, that can only be done manually with S-off
Thank you for your time and for the clarification!
Click to expand...
Click to collapse
1. Matching firmware/hboot is always the best route possible as it can minimize any issues that may arise, so I suggest it.
2.As far as compatibility issues there aren't any, the hardware on all these devices are almost exactly alike so running another hboot is quite possible. Although I suggest keeping to your carriers hboot to minimize issues. Or atleast keep a backup of yours
3.You can downgrade only if you are S-OFF, otherwise you can only upgrade or flash the corresponding firmware you're currently on. SuperCID only allows you to flash RUUs/firmware from other carriers or regions. CID stands for Carrier Identification. So even with supercid you can't downgrade, there are security measures in place to stop you from downgrading you hboot without s-off, it either won't write or you will end up with a brick.
Sent from my HTC One using Tapatalk