[Q] HTCDev with AT&T One X - AT&T, Rogers HTC One X, Telstra One XL

I have had my HTC One X for AT&T for a week now. I noticed that paulobrien has found a way to root the One X. Unfortunately when I go to htcdev.com I get this message while trying to unlock my bootloader.
"We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed."
I remember getting this message with the HTC Vivid.

DasTestament said:
I have had my HTC One X for AT&T for a week now. I noticed that paulobrien has found a way to root the One X. Unfortunately when I go to htcdev.com I get this message while trying to unlock my bootloader.
"We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 160.
Error Reason: MID Not Allowed."
I remember getting this message with the HTC Vivid.
Click to expand...
Click to collapse
In due time
Sent from my HTC One X using Tapatalk 2

I also get this error when attempting to unlock the bootloader. Any ideas?

you cannot unlock bootloader yet for AT&T, it's known fact right now. root is independent of the bootloader too, so just cuz we have root doesn't automatically let you unlock bootloader. just give it some time, maybe in a month or so.

I thought it wasn't possible to unlock if you was on ATT
Sent from my HTC One X using xda premium

it's not possible. all we have at the moment is root, we'll have a bootloader unlock in some time i'm sure, either sanctioned or unsanctioned.

http://htcpedia.com/news/No-Unlock-...Users-Begin-The-Attack.html?l_page=1&p_page=1

niceppl said:
http://htcpedia.com/news/No-Unlock-...Users-Begin-The-Attack.html?l_page=1&p_page=1
Click to expand...
Click to collapse
I signed it!

any news?

-=knop=- said:
any news?
Click to expand...
Click to collapse
Sorry but... you're kidding, right? Check the dev section, we've been able to unlock now for weeks.
Sent from my HTC One X using xda premium

It is possible to unlock the One X's BL:
http://forum.xda-developers.com/showthread.php?t=1671396

_MetalHead_ said:
Sorry but... you're kidding, right? Check the dev section, we've been able to unlock now for weeks.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I still get this message when I try to get it from HTCDEV
Error Code: 160.
Error Reason: MID Not Allowed.
Where else can I get it from?

Jesus...
There's a tutorial in the dev section. This thread gave me cancer.
Sent from my HTC One X using xda app-developers app

Here
http://forum.xda-developers.com/showthread.php?t=1672284
Sent from my Nocturnalized Beast

Give a man a fish vs teach a man to fish.

Sorry about your cancer. You might want to get that looked at..
But, it turns out that it wasn't working because of my OTA update to 2.2.. So even the tutorials in the development section won't work until someone figures how to get behind the new update.
Just thought everyone should know!
Also, I know how to search, I just wanted one of you guys to do it for me. Thanks!
Sent from my HTC Sensation using xda app-developers app

deleted....

GotSoul said:
Sorry about your cancer. You might want to get that looked at..
But, it turns out that it wasn't working because of my OTA update to 2.2.. So even the tutorials in the development section won't work until someone figures how to get behind the new update.
Just thought everyone should know!
Also, I know how to search, I just wanted one of you guys to do it for me. Thanks!
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Proudly proclaiming your ignorance will not get you much help here.
Sent from my Inspire 4G using Tapatalk 2

I received the same exact error. So if it are allowed to unlock it, what would be my problem?
Error Code: 160.
Error Reason: MID Not Allowed.

SedaG said:
I received the same exact error. So if it are allowed to unlock it, what would be my problem?
Error Code: 160.
Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
Are you serious? You bumped a 3 month old thread which is only somewhat relevant to your situation AND made your own post?
Did you even read how to unlock a 2.20 htc one x?
Did you read the 3000 threads here on how to do it?

Related

Id Simeone working on a way to unlock the one S without htcdev?

Hi there!
I really would like to unlock my one S but I don't want to loose the warranty, I have seen this thread regarding the work that is under development for the one X http://forum.xda-developers.com/showthread.php?t=1604300 and I was wondering if something like this exist here too
Sent from my HTC One S using xda app-developers app
light_n_roses said:
Hi there!
O really would like to unlock my one S but I don't want to loose the warranty, I have seen this thread regarding the work that is under development for the one X http://forum.xda-developers.com/showthread.php?t=1604300 and I was wondering if something like this exist here too
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
There isn't really any active work toward s-off for the One S. I think the hope is that anything the Att One-X guys come up with will work on or phone also. So there is still hope.
Also, you can unlock your phone without going through HTCdev. Therefore not losing your warrenty but you would need files from someones phone who is unlocked. The link below explains it but DO NOT try it with the files in the link as it won't work. You need the files from a One S.
http://forum.xda-developers.com/showthread.php?t=1732980
Well, I think that an exploit for the one X cannot be used for the one S because of different chip used on the devices... We have a Qualcomm one while the one X has tegra. I would check the link that you have pass me but I think that it will be hard to find someone who would pass me the right files...
Sent from my HTC One S using xda app-developers app
light_n_roses said:
Well, I think that an exploit for the one X cannot be used for the one S because of different chip used on the devices... We have a Qualcomm one while the one X has tegra. I would check the link that you have pass me but I think that it will be hard to find someone who would pass me the right files...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
The AT&T (and some other NA carriers) One X (AKA One XL) has the MSM8960 which is also a S4 Krait+Adreno 225 combo, just with an LTE modem.
light_n_roses said:
Well, I think that an exploit for the one X cannot be used for the one S because of different chip used on the devices... We have a Qualcomm one while the one X has tegra. I would check the link that you have pass me but I think that it will be hard to find someone who would pass me the right files...
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It would work for sure. If someone has a device going back to t-mobile or HTC for replacement we could use their partitions.
dc211 said:
It would work for sure. If someone has a device going back to t-mobile or HTC for replacement we could use their partitions.
Click to expand...
Click to collapse
Then the bootloader woukd NOT show the message tampered right??
Sent from my HTC One S using xda app-developers app
light_n_roses said:
Then the bootloader woukd NOT show the message tampered right??
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
TAMPERED isn't such a great issue. It goes away by just flashing a RUU.
The real issue is the RELOCKED message you get when relocking the bootloader. To prevent this RELOCKED message, and to have it displaying LOCKED isntead (this way the bootloader won't appear to have been ever unlocked), you have to achieve S-OFF. That's what they're working on, if I'm not mistaken.
light_n_roses said:
Then the bootloader would NOT show the message tampered right??
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It would still show tampered. The only reason you would want to do it this way is so your phone wouldn't show up in HTC's database of phones they unlocked. When you unlock through HTC Dev you agree that unlock the phone may void parts of your warranty.
And as the other poster above stated even if you locked the boot-loader again it would say Relocked instead of Locked. So there isn't really much a reason to do it this way.
Well I hope that a way to unlock the phone without leaving traces will eventually cames out. I do not want to use htcdev because I have to keep this phone for 30 months as I have taken it with an operator contract, so if something happen and I have unlocked it then I would have no warranty.
Sent from my HTC One S using xda app-developers app

[Q] Why would my one s be s-off, with a red htc disclaimer :S

Hi, as my nexus s has recently been lost i decided its time to put a custom rom on my one s, i was about to unlock the bl on it and noticed the tamper banner on the bl screen, its also s-off with a cid of 11111111, i have attatched a pic of the bl screen for reference, As far as i know the one series cant as of yet cannot be s-off'ed like the older htc devices, how would this be possible on my device? It was bought from brand new quite a while ago and until now has always run the the stock rom with no root etcetc.. The only thing i can think of is i had it unlocked not long after purchasing it but not sure what method the shop used. When i access the bootloader on my one s i can choose what to do fastboot or recovery etc etc but on this one s i get the red htc disclaimer like pictured below when i select recovery, i have the latest cwm touch flashed but cannot get into it.. So how can i access recovery?? any help would be appreciated
Sorry about image quality its taken on an old webcam
Your bootloader is still locked, that would be my guess. That's why the pink banner at the top says "locked". Unlock that and you should have access to recovery.
Sent from my H1S using XDA Premium.
I have since unlocked the bootloader, and still getting the same problem, recovery just won't load, as with old HTC devices such as sensation, desire s, DHD bootloader unlock was not relevant if you had s-off not sure about the one series, my main question is how it's become s-off in the first place
Sent from my HTC One S using xda premium
Keep the bootloader locked, don't use the HTCDev method to unlock it. You're extremely lucky to have S-OFF, this means that you can easily get your warranty back running an RUU, changing CID and fastboot oem writesecureflag 3. This will make it S-ON again, and no trace of it being S-OFF will be there.
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
S-OFF is better than HTCDev for flashing ROMs, as it means you don't have to flash the boot.img seperately.
usaff22 said:
Keep the bootloader locked, don't use the HTCDev method to unlock it. You're extremely lucky to have S-OFF, this means that you can easily get your warranty back running an RUU, changing CID and fastboot oem writesecureflag 3. This will make it S-ON again, and no trace of it being S-OFF will be there.
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
S-OFF is better than HTCDev for flashing ROMs, as it means you don't have to flash the boot.img seperately.
Click to expand...
Click to collapse
Hi thanks for your responce. Since I took those pics the bl has been unlocked, warranty I'm not too fussed about, the main issue I have is how its become s-off in the first place, and when I try to boot cwm I get the red message pictured in my first post, I've tried to flash a recovery via fastboot and.Rom manager and no luck what so ever, I've tried com touch and cwm standard aswell as twrp I have the s4 device and Im stuck lol. Jeez I miss my nexus already
Sent from my HTC One S using xda premium
PEP-C is a friend of mine, I've just purchased the above mentioned one s for £150 but that's irrelevant, I have owned HTC devices before but never have I seen that red message pictured in the first post, it appears every time the phone boots up, any suggestions? My mate said he's had it from new but I'm not so sure.
Sent from my HTC One S using xda premium
furrabbit.nh said:
PEP-C is a friend of mine, I've just purchased the above mentioned one s for £150 but that's irrelevant, I have owned HTC devices before but never have I seen that red message pictured in the first post, it appears every time the phone boots up, any suggestions? My mate said he's had it from new but I'm not so sure.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Its a new thing HTC is doing. Normally pops up when you have a modified kernel/recovery.
Sent from my HTC One S using xda premium
Posted in error
Sent from my HTC One S using xda premium
usaff22 said:
The current method is HTCDev, which submits a Unique Device Identifier so they can decline your warranty due to an unlocked bootloader.
Click to expand...
Click to collapse
Man... I hate HTC sometimes haha
Sent from my SGH-T999 using xda premium
Sgt-Hartley said:
Ahh thanks for clearing that up, I did wonder, all though it does show up even on a fully stock system, no root, stock recovery, as you can see from the pics in first post the BL was still locked when those snaps were taken, even though its s-off it would not let me flash a recovery for him without unlocking the BL after I typed the fastboot command it said not allowed or something similar.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I have no idea how its like that, but that's normally why it shows up.
Maybe it has to do with it being S-off?
I do know however, that with S-off you can remove the red text. I'm sure someone here would know what to do.
Sent from my HTC One S using xda premium
xxquicksh0txx said:
I have no idea how its like that, but that's normally why it shows up.
Maybe it has to do with it being S-off?
I do know however, that with S-off you can remove the red text. I'm sure someone here would know what to do.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
You can remove it, but messing around with it could brick your phone. I wouldn't even think about it.
Sent from my HTC One S using Tapatalk 2
---------- Post added at 08:23 AM ---------- Previous post was at 08:21 AM ----------
PEP-C said:
Hi thanks for your responce. Since I took those pics the bl has been unlocked, warranty I'm not too fussed about, the main issue I have is how its become s-off in the first place, and when I try to boot cwm I get the red message pictured in my first post, I've tried to flash a recovery via fastboot and.Rom manager and no luck what so ever, I've tried com touch and cwm standard aswell as twrp I have the s4 device and Im stuck lol. Jeez I miss my nexus already
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Try flashing a stock recovery, then flash the one from modaco. Apparently that one works best
Sent from my HTC One S using Tapatalk 2
It is a s4 device right ? According to the hboot its a s4
Sent from my HTC VLE_U using xda app-developers app
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
gock said:
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Consider yourself extremely lucky too, I'd die to have S-OFF
Sent from my HTC One S using Tapatalk 2
Sure does seem to be a rash of s-off devices popping up lately. Maybe we'll get lucky and somebody will wander over to the forums and help us with the method(s).
diabolusmiles said:
Sure does seem to be a rash of s-off devices popping up lately. Maybe we'll get lucky and somebody will wander over to the forums and help us with the method(s).
Click to expand...
Click to collapse
Why cant a dev ever get lucky lol.
Darknites said:
Why cant a dev ever get lucky lol.
Click to expand...
Click to collapse
Even if a Dev gets lucky, there's nothing no one can do about it. It's how it got there that's important, not whether you have it or not.
Sent from my HTC One S using Tapatalk 2
gock said:
Mine is s off too and also with the red text when booting
Click to expand...
Click to collapse
You get the red text if your boot image is not signed by HTC. Regardless of s-on/off.
And afaik, you get **TAMPERED** if your recovery image is not HTC signed.
touch of jobo said:
You get the red text if your boot image is not signed by HTC. Regardless of s-on/off.
And afaik, you get **TAMPERED** if your recovery image is not HTC signed.
Click to expand...
Click to collapse
I have ***TAMPERED *** and I have the stock recovery and a locked bootloader. The only thing I have is su.bin and superuser.apk
Sent from my HTC One S using Tapatalk 2
usaff22 said:
I have ***TAMPERED *** and I have the stock recovery and a locked bootloader. The only thing I have is su.bin and superuser.apk
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The s-off device of mine had tampered before I even unlocked the bootloader or even flashed custom recovery, I only bought it to sell but no I'm unsure, the one s and one x both seem to be.doing well even without s-off. As for the red message it only appears with custom Rom on my device, if on stock its not there.
Edit: Just to clear things up I now own the device mentioned in the first post
Edit 2: does anyone know if xtc clip can s-off the one series? Can't find any updated info
Sent from my HTC One S using xda premium
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
gock said:
Mine is s off too and also with the red text when booting
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Did you ever get your phone sim unlocked via a third party company, if so what method did they use?
Sent From My HTC One S-Off
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
aditya. said:
It is a s4 device right ? According to the hboot its a s4
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Yes it's s4
Sent From My HTC One S-Off

Network Unlocking problem

I bought a Sensation of a forums site and the guy gave me the unlock code to unlock it but when I add it, it says code successful but the phone doesn't unlock I then tried the unlock methods on this website and it still won't work. Whenever the box appears to put in the code I can put in any random numbers and it will still say unlock code was successful. The rom is cynagogen mod 10 jb 4.1.2 but not sure if this can cause any problem?
aty27 said:
I bought a Sensation of a forums site and the guy gave me the unlock code to unlock it but when I add it, it says code successful but the phone doesn't unlock I then tried the unlock methods on this website and it still won't work. Whenever the box appears to put in the code I can put in any random numbers and it will still say unlock code was successful. The rom is cynagogen mod 10 jb 4.1.2 but not sure if this can cause any problem?
Click to expand...
Click to collapse
If you did the method on here you shouldn't have to enter an unlock code. Make sure you did the method right. I've done the method on here to 2 sensations and it worked perfectly
Sent from my HTC Sensation using xda app-developers app
urmothersluvr said:
If you did the method on here you shouldn't have to enter an unlock code. Make sure you did the method right. I've done the method on here to 2 sensations and it worked perfectly
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Hi mate could you give me the link for the one you've done?
aty27 said:
Hi mate could you give me the link for the one you've done?
Click to expand...
Click to collapse
this is the guide
http://forum.xda-developers.com/showthread.php?t=1232107
but you have to be S-OFF
rzr86 said:
this is the guide
http://forum.xda-developers.com/showthread.php?t=1232107
but you have to be S-OFF
Click to expand...
Click to collapse
Thanks sadly didnt work as it says update fail security fail.
Thought i was good at this rooting lark but Htc phones are much more complex.
my phone is S-OFF btw mate.
Starting to think h-boot 127.0.0 is the reason why i'm having a problem if this is the case i'll have to return the phone and make sure i stay well away from HTC.
aty27 said:
Starting to think h-boot 127.0.0 is the reason why i'm having a problem if this is the case i'll have to return the phone and make sure i stay well away from HTC.
Click to expand...
Click to collapse
Hi,
If you are hboot 1.27, you need to look HERE

[S-off] Firewater s-off for HTC One XL

Firewater S-off for HTC One XL!
Firstly let me say that this isn't my own work, all credit goes to @beaups and @Fuses for bringing this to our device.
Firewater is a new method for achieving s-off on HTC devices.
For everyone that has taken the 5.18 at&t update before unlocking you should be able to use Firewater. It has a temp root feature which will enable you to get s-off on your device, once you have s-off you can get SuperCID via a simple fastboot command (fastboot oem writecid 11111111), then you can unlock your bootloader at htcdev. I'd really appreciate any feedback on whether this works for you.
This is just a simple thread to get this method some exposure for users with our device. As per the licensing section on the site and beaup's wishes I cannot include the download or instructions in this thread. However, we can have this thread serve as a troubleshooting/help location for the One XL. Alternatively, support for rumrunner s-off is available at #rumrunners on the freenode and andirc networks. Please make sure you meet all of the requirements before contacting support.
Firewater S-off.
Please go give beaups and Fuses a bunch of thanks for their work!
Sent from my Evita
Sent from my Evita
I'll try this in a little bit. I'll post back and see of it works.
Sent from my HTC One X using xda premium
Hey
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
Has anyone tested this? I will try here in about 30 mins
Sent from my SM-N9005 using XDA Premium 4 mobile app
I have an unlocked bootloader and supercid. Folowwed directions and it didn't work. Just quit after chugging the first bottle. Now I'm kinda stuck with s-on until I flash cm tonight.
Sent from my HTC One X using xda premium
Hmmmmm..... well I'm total stock with the new update and sense 5. I'm gonna give it a shot.
Sent from my SM-N9005 using XDA Premium 4 mobile app
zounduser said:
Hmmmmm..... well I'm total stock with the new update and sense 5. I'm gonna give it a shot.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your situation is the situation I'm really interested in, we really need to find out whether it's possible to unlock the bootloader after taking the 5.18 update. Let me know how you go.
Sent from my Evita
timmaaa said:
Your situation is the situation I'm really interested in, we really need to find out whether it's possible to unlock the bootloader after taking the 5.18 update. Let me know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Unfortunately I won't know until tomorrow when I can get to a laptop. I was gonna do it today, but couldn't. I'll let u know tomorrow after work unless someone else beats me to it.
Sent from my beastmode of a phone, THE Galaxy Note 3
Doesn't work for me.
Stock at&t 4.2.2 (firmware 5.18), bootloader locked, s-on. Output on temproot:
[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
Well that's a shame, thanks for the feedback though. If anybody else can please attempt this also that'd be great.
Sent from my Evita
timmaaa said:
Well that's a shame, thanks for the feedback though. If anybody else can please attempt this also that'd be great.
Sent from my Evita
Click to expand...
Click to collapse
I agree we need a few more people to test, as new as the guy that did test is. it could be a simple mistake as having anti virus on the computer, etc.
rpomponio said:
I agree we need a few more people to test, as new as the guy that did test is. it could be a simple mistake as having anti virus on the computer, etc.
Click to expand...
Click to collapse
I tried it under linux with no antivirus, in windows (7) -- antivirus off. Everything done according to "Instructions (temp-root method)". What other mistakes could be?
ttol3g said:
I tried it under linux with no antivirus, in windows (7) -- antivirus off. Everything done according to "Instructions (temp-root method)". What other mistakes could be?
Click to expand...
Click to collapse
I can't think of any. You might try entering a root shell after running the temp root, just to verify that is what is failing
Sent from my HTC6435LVW using Tapatalk
timmaaa said:
Well that's a shame, thanks for the feedback though. If anybody else can please attempt this also that'd be great.
Sent from my Evita
Click to expand...
Click to collapse
I'll give it a go. I'll tell you all if it works out. (AT&T One X)
*UPDATE* I had no luck. same error as the last guy
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
I'm going to be receiving another HTC One X soon. I can only assume that it will be on the 5.18 firmware so I will try this method. If not... off to Mobiletechvideos for S-Off.
I got the sane errors
Sent from my HTC One X using Tapatalk
Confirm NOT working on 5.18 firmware
Since I like to run the updated AT&T ruu whenever they come out WeakSauce-1.0.1.apk worked great for temp root and to get everything going again without needing pc after initial ruu. I was wanting to test stock for abit then was on the road and wanted to go custom and weaksauce worked perfect.
I am on 5.18. temproot gives the same errors others have posted. Weaksauce enables a successful su but firewater fails, not always with the same messages. I would love for this to work, but it looks like I'm just going to get any M8 anyway and make sure I s-off while the exploits still work on it.
Just did s-off on mine tonight and then super-cid. Mine also hung up at chugging. Exited the program and ran it again successfully. I am overjoyed now. Many thanks to the devs.
Sent from my One X using XDA Free mobile app
quicksilver53 said:
Just did s-off on mine tonight and then super-cid. Mine also hung up at chugging. Exited the program and ran it again successfully. I am overjoyed now. Many thanks to the devs.
Sent from my One X using XDA Free mobile app
Click to expand...
Click to collapse
So, you successfully obtained root and S-Off on a stock One X on the newest OTA (4.2.2)?

M8 Verizon not able to be unlocked through HTC Dev

Looks like you can't unlock the bootloader through HTC Dev on the VZW M8 Just got mine and tried and get the dreaded Error 160 MID Not Allowed.
Ohhhhh, that is garbage
Sent from my VS980 4G using XDA Premium 4 mobile app
Good ol Verizon locking their phones down again
Sent from my HTC One using Tapatalk
bloodiedwraith said:
Looks like you can't unlock the bootloader through HTC Dev on the VZW M8 Just got mine and tried and get the dreaded Error 160 MID Not Allowed.
Click to expand...
Click to collapse
IM sure someone will find way!
Why don't you try firewater s-off to see if the exploit still works? Please report back with your findings.
eidt: devs have said it could brick device, would not recommend doing it.
Thread Moved over to the Verizon M8 forum as it makes more sense to be here than the International forum
Regards,
- KidCarter93
Forum Moderator
bloodiedwraith said:
Looks like you can't unlock the bootloader through HTC Dev on the VZW M8 Just got mine and tried and get the dreaded Error 160 MID Not Allowed.
Click to expand...
Click to collapse
Just Tried. Can't Believe big red would do this to us. Time to dig out that ice cream and just wait till either community cracks it or htc actually lets us through.
FadedLite said:
Can't Believe big red would do this to us.
Click to expand...
Click to collapse
REALLY? This was the most predictable thing that Verizon could of done. Besides scribbling on the home power button and etching on the back,
"Dear consumers, we don't care..."
--------------------------
Verizon Rage.... |
--------------------------
Not sure why anyone is suprised. Those of us with the M7 knew this month's ago. For the first day after the M7 was released you could use HTC DEV unlock then VZ made HTC lock that down for the M7.
I too hoped maybe VZ had not gotten to HTC yet for the M8 so I tried but no luck. Will need to wait for rumrunner or firewater to be updated to support the M8. It may take a while....
Mike02z said:
Not sure why anyone is suprised. Those of us with the M7 knew this month's ago. For the first day after the M7 was released you could use HTC DEV unlock then VZ made HTC lock that down for the M7.
I too hoped maybe VZ had not gotten to HTC yet for the M8 so I tried but no luck. Will need to wait for rumrunner or firewater to be updated to support the M8. It may take a while....
Click to expand...
Click to collapse
I'm coming from a Note 3 so I'm not familiar with the M7, did rumrunner or Firewater allow for running custom asop roms?
Sent from my HTC6525LVW using xda app-developers app
PhilPan said:
I'm coming from a Note 3 so I'm not familiar with the M7, did rumrunner or Firewater allow for running custom asop roms?
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
Yes sir. Rumrunner gave you S-Off which is "Signature Off". Once that is set, you can flash custom recoveries and then custom rom's. It took months for the team to get this working and I know it did not work on 4.4.2. I think we are in for a long wait. If you bought this hoping you could get custom rom's you might want to reconsdier. If you like the phone and can live with it stock for a few months, it's a great device.
The M7 was the best phone I ever had and I swap phones a lot.
FadedLite said:
Just Tried. Can't Believe big red would do this to us.
Click to expand...
Click to collapse
That's sarcasm, right?
it will get unlocked. name another htc phone that hasn't?
oneandroidnut said:
it will get unlocked. name another htc phone that hasn't?
Click to expand...
Click to collapse
The stock One with 4.4.2 has not been able to achieve S-Off without a Java card. At lest not last time I looked.
Mike02z said:
The stock One with 4.4.2 has not been able to achieve S-Off without a Java card. At lest not last time I looked.
Click to expand...
Click to collapse
oh boy not good LOL
This phone has an sd slot. The earlier one didn't. Easier to hack from what I remember
Well what about root? With xposed, root alone can provide a lot of nice added functionality before the bootloader is figured out
Just picked up the M8. Tried HTC Dev and failed
ocman40 said:
This phone has an sd slot. The earlier one didn't. Easier to hack from what I remember
Click to expand...
Click to collapse
Couldn't agree more. I'm fine if we get custom recovery at some point but I'd really love to get titanium on and remove some of this Verizon crap... I mean stuff....
Sent from my Nexus 7 using xda app-developers app
myron317 said:
Couldn't agree more. I'm fine if we get custom recovery at some point but I'd really love to get titanium on and remove some of this Verizon crap... I mean stuff....
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I disabled it all until then.

Categories

Resources