So, I've been searching, and think I understand what I need to know, but am looking for clarification of which is my best option to get an AT&T HTC One M8 happy under T-Mobile....
I bought a HTC One M8 that is S-Off and has an Unlocked boot loader...
I THINK what I want to do is:
Change my CID to T-Mobile (T-MOB010)
fastboot oem writecid T-MOB010
Click to expand...
Click to collapse
Change my MID to T-Mobile's MID
adb shell
su
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
adb reboot bootloader
Click to expand...
Click to collapse
And then what... Do I need to re-lock the bootloader so I can flash an RUU?
fastboot oem lock
Click to expand...
Click to collapse
(if I lock the bootloader, is unlocking it again as simple as re-requesting an unlock code from HTC?)
And then flash the RUU?
Is there a reasonable way to accomplish this without re-locking the boot loader?
I've used Odin on Samsung devices, and flashtool on Sony Xperia devices... it's been a VERY long time since I had my last HTC device, so my RUU skills are a bit rusty... (I've got a fair amount of experience with CWM and TWRP...)
I'm VERY tempted to simply change the CID and flash the GPE RUU and see how that plays out... I'm just asking before I do something stupid.
scifan said:
So, I've been searching, and think I understand what I need to know, but am looking for clarification of which is my best option to get an AT&T HTC One M8 happy under T-Mobile....
I bought a HTC One M8 that is S-Off and has an Unlocked boot loader...
I THINK what I want to do is:
Change my CID to T-Mobile (T-MOB010)
Change my MID to T-Mobile's MID
And then what... Do I need to re-lock the bootloader so I can flash an RUU?
(if I lock the bootloader, is unlocking it again as simple as re-requesting an unlock code from HTC?)
And then flash the RUU?
Is there a reasonable way to accomplish this without re-locking the boot loader?
I've used Odin on Samsung devices, and flashtool on Sony Xperia devices... it's been a VERY long time since I had my last HTC device, so my RUU skills are a bit rusty... (I've got a fair amount of experience with CWM and TWRP...)
I'm VERY tempted to simply change the CID and flash the GPE RUU and see how that plays out... I'm just asking before I do something stupid.
Click to expand...
Click to collapse
Since you are S-Off, you can simply unlock and relock the bootloader at will. On my M7, I changed the MID through notepad, and overwrote the file, but can be done either way. Once I had the CID and MID correct I ran the RUU and it worked. I even had Wi-Fi calling. I only did it as a test, but everything worked out fine. If anything has changed from the M7 to M8, please chime in so I'm not steering the OP wrong.
scifan said:
Do I need to re-lock the bootloader so I can flash an RUU?
Click to expand...
Click to collapse
With s-off, you can flash RUU with bootloader unlocked.
redpoint73 said:
With s-off, you can flash RUU with bootloader unlocked.
Click to expand...
Click to collapse
Yep, s-off does not require the boot loader to be locked when flashing ruu's.
If you were still s-on then the bootloader would need to be relocked.
redpoint73 said:
With s-off, you can flash RUU with bootloader unlocked.
Click to expand...
Click to collapse
So, change the CID, and run the RUU exe and I'm good to go?
MID must match too, or it will fail.
My phone already had the cid set to supercid... I updated the mid, locked my bootloader, and hit it with T-Mobile's rom, and I seem to be cooking with gas.
Thanks guys!
Sent from my HTC One_M8 using Tapatalk
scifan said:
My phone already had the cid set to supercid... I updated the mid, locked my bootloader, and hit it with T-Mobile's rom, and I seem to be cooking with gas.
Thanks guys!
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Good to hear, good to hear!
Related
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
I'm no dev by any means but why did htc allow you to root the phone and unlock the boot loader and still keep s-on? Doesnt that defeat the purpose? I've been away from htc devices for a while so I'm curious as I'm really close to purchasing this.
HTC is stupid. They don't want kernels/radios to be flashed via recovery. Possibly because of more potential bricks. Hey. At least it's better than nothing.
Its to protect the end users. With an unlocked bootloader, you have all the tools to run custom software, but its near impossible to perm brick the device. But after you remove the nand security, it becomes alot easer to brick a device. Giving people access to the fastboot erase commands and write access to partitions like bootloader.
Sent from my HTC One X+ using Tapatalk 2
So a quick question, say after you root/unlock the device. And you want to return to at&t what needs to be done? Is there an ruu available yet?
Lock the bootloader and flash the RUU. RUU is available.
hasoon2000 said:
Lock the bootloader and flash the RUU. RUU is available.
Click to expand...
Click to collapse
Cool thanks.
SysAdmNj said:
So a quick question, say after you root/unlock the device. And you want to return to at&t what needs to be done? Is there an ruu available yet?
Click to expand...
Click to collapse
I have returned rooted phones to ATT with custom ROM's installed.
They don't care.
joshua43214 said:
I have returned rooted phones to ATT with custom ROM's installed.
They don't care.
Click to expand...
Click to collapse
Been there done that lol.
Can anyone confirm if the HTC Quick Root tool is working for both rooting and fully unrooting?
I need to able to unroot as easily as possible should something happen to my device, since I've only had it for a few days and is still on warranty, which is why I'm avoiding unlocking the bootloader for now.
Attached is the software information screenshot, if necessary.
oddoneout said:
Can anyone confirm if the HTC Quick Root tool is working for both rooting and fully unrooting?
I need to able to unroot as easily as possible should something happen to my device, since I've only had it for a few days and is still on warranty, which is why I'm avoiding unlocking the bootloader for now.
Attached is the software information screenshot, if necessary.
Click to expand...
Click to collapse
As far as I know, any (un)rooting tool will unlock your bootloader to get the job done. Quick Root (along with similar tools, like hasoon2000's "All In One toolkit") will merely automate the process, making it easier. The end result is the same, though: An unlock code will have been requested from HTC, and some fusebits will have been blown. Your warranty may or may not be void.
So essentially, there is no way to root without unlocking the bootloader?
oddoneout said:
So essentially, there is no way to root without unlocking the bootloader?
Click to expand...
Click to collapse
No.
xpirt
Thanks. Guess I will be waiting for S-OFF.
oddoneout said:
Thanks. Guess I will be waiting for S-OFF.
Click to expand...
Click to collapse
It's a long long wait.
Sent from my HTC Desire X using xda app-developers app
I know I'm derailing the thread a bit here, but assuming I do unlock the bootloader and lock it again afterwards for warranty purposes, is there any way to change the RELOCKED warning to LOCKED?
Apparently the following does just that for other HTC devices which have a signed hboot - can anyone confirm?
Code:
fastboot oem writesecureflag 3
oddoneout said:
I know I'm derailing the thread a bit here, but assuming I do unlock the bootloader and lock it again afterwards for warranty purposes, is there any way to change the RELOCKED warning to LOCKED?
Apparently the following does just that for other HTC devices which have a signed hboot - can anyone confirm?
Code:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
You can't change RELOCKED. After first unlock of bootloader you lose warranty for ever.
xpirt
While I understand that the following threads aren't for the Desire X, perhaps you should still have a look at them
http://androidforums.com/rezound-al...-off-guide-info-return-stock.html#post4394129
http://forum.xda-developers.com/showthread.php?t=2034060
oddoneout said:
While I understand that the following threads aren't for the Desire X, perhaps you should still have a look at them
http://androidforums.com/rezound-al...-off-guide-info-return-stock.html#post4394129
http://forum.xda-developers.com/showthread.php?t=2034060
Click to expand...
Click to collapse
Yes with S-OFF you can do all, but for Desire X there is not S-OFF yet.
xpirt
xpirt said:
Yes with S-OFF you can do all, but for Desire X there is not S-OFF yet.
xpirt
Click to expand...
Click to collapse
In the first link, the instructions are to run a RUU (which as far as I understand will set the device to S-ON) and then to run "fastboot oem writesecureflag 3", so I don't quite understand why S-OFF is required.
I recently switched back to stock after converting to Google Edition. Everthing went as planned...flashed Tmo Ruu, Hboot to 1.44, etc. But I noticed after it was all over that my bootloader said LOCKED not RE-LOCKED. Been trying for the last few days to unlock it and no luck. It goes through all the phases when I'm trying to unlock it, it even says that I'm successful in unlocking my bootloader. When the display on my phone displays the screen to unlock the bootloader, I choose yes and my phone reboots as it should. But when I check it, it still says LOCKED. Also I'm S-off and Super Cid. Any help would be very much appreciated. Thanks.
You don't necessarily need to unlock it if your s-off, you can still flash roms and stuff. Just fastboot flash doesn't work. You could do the rebootRUU thing to flash a recovery. Or you could use revone to unlock it. But you're probably on .11 huh?
Sent from my HTC One using Tapatalk
grim489 said:
You don't necessarily need to unlock it if your s-off, you can still flash roms and stuff. Just fastboot flash doesn't work. You could do the rebootRUU thing to flash a recovery. Or you could use revone to unlock it. But you're probably on .11 huh?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
yes, I belive so
if you are s-off, you can use revone to unlock bootloader. ./revone -u
wwjdd44 said:
if you are s-off, you can use revone to unlock bootloader. ./revone -u
Click to expand...
Click to collapse
If you unlock the bootloader using revone, do you still lose the flashlight, Ringtone trimmer..etc that youlose if you use the HTC Dev method. Does it still wipe all personal data such as photos, sms, etc? Thanks!
toaks said:
If you unlock the bootloader using revone, do you still lose the flashlight, Ringtone trimmer..etc that youlose if you use the HTC Dev method. Does it still wipe all personal data such as photos, sms, etc? Thanks!
Click to expand...
Click to collapse
no to all.
wwjdd44 said:
no to all.
Click to expand...
Click to collapse
Awesome. Thanks for the info!
Howdy folks...so my buddy picked up an M8 off of Craigslist that was apparently running some sort of vanilla android. It is unlocked and S off..he attempted to flash a Sense ROM and ended up in a boot loop. He's the kind of guy that shouldn't be doing such things...
This is where I come in to the rescue. After some reading this afternoon, I've come to the conclusion he must have a GPE converted phone. I personally have no experience with this device (G2 Verizon owner) but I'm pretty versed in fast boot and ADB.
The phone is currently in fast boot. This is all it has. If I attempt to boot it into recovery, it loops.
Can anyone help me get this thing running by pointing me in the right direction? Ideally, I'd like to have it fully AT&T stock.
My current plan was to push a recovery via fast boot and flash a GPE ROM off of SD. Will this work?
I just don't want to mess the phone up any further.
m8
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
passion8059 said:
Can you boot phone into bootloader? If so connect phone and type adb oem getvar all.
Should give you details of cid and rom required to get phone working again.
Googling ruu for cid will help so example is m8 ruu htc_001.
Click to expand...
Click to collapse
Yes, bootloader is basically all I have. Thank you for the help!
I won't be able to get to work for a few hours, but I'll update with any progress.
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
m8
mulhiny said:
OK...so turns out the phone indeed was converted to a GPE device, which caused his problem after attempting to flash a Sense ROM...I successfully flashed TWRP via fast boot and installed a GPE rom...now, just need to go about converting it back for him.
Thanks to member Passion for helping me out.
Click to expand...
Click to collapse
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Hope this helps!
passion8059 said:
Change cid to super cid 11111111 (7 ones) by putting phone into fastboot , connect and typing fastboot oem writecid 1111111.
This allows phone to have most stock htc roms to be written to phone.
Find stock rom you require and flash which will revert to stock for you.
Click to expand...
Click to collapse
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
redpoint73 said:
It appears the OP's phone had the full GPE conversion done to it, therefore changing the partitions, and that alone will prevent Sense ROMs for booting. Flashing a ROM in itself will not change the partitions back the Sense partition scheme.
Easiest way to revert is probably RUU. You're right in the OP needs to post getvar all data before all the steps can be laid our correctly. In short, OP needs the proper CID or SuperCID, and relock bootloader (if unlocked) or S-off to run RUU.
Click to expand...
Click to collapse
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
passion8059 said:
Did gpe conversion with my m7 and had to flash with zip file of ruu in order to change.
I have tried looking myself to point him in the right direction for m8 zip's but have not had had any joy?
Click to expand...
Click to collapse
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
redpoint73 said:
Flashing a zip of the RUU isn't necessary. OP can either flash the official exe file: http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Or the bootable RUU here (no PC required): http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Click to expand...
Click to collapse
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
passion8059 said:
But doesn't bootloader need to be changed?
As you said partitions are different and ruu would not like it surely?
Click to expand...
Click to collapse
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
RUU will rewrite all partitions including hboot. I have the advice I did for a reason.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
pclaunch said:
So all I would have to do is run the bootable ruu to bring my gpe converted m8 back to stock sense? Just want to know for future ref
Click to expand...
Click to collapse
Yes.
Keep in mind, if you are s-on, you need to have the proper CID or SuperCID. Plus, you can only run an RUU with equal or greater hboot number than the hboot presently installed on the phone.
S-off should bypass both these issuees (CID and hboot version check).