Related
Htc raider/vivid rooted ok
1. Unlock bootloader by htcdev
2. Coppy file PH39IMG.zip on root sdcard
http://dl.dbank.com/c0fwbgxr2w
Phone rooted ok.
I'm assuming that's a rooted stock rom that obviously wont unlock the bootloader. but it installs like an official update?
Yeah... What is this?
Sent from my HTC PH39100 using xda premium
Lol k hope it works but unlocked bootloader hmmmm??? Someone should try
Sent from my HTC PH39100 using xda premium
the bootloader on the bell htc raider is unlocked correct?
erik10002 said:
the bootloader on the bell htc raider is unlocked correct?
Click to expand...
Click to collapse
It's unlockable via the htcdev website. Doesn't come unlocked.
rquinn19 said:
It's unlockable via the htcdev website. Doesn't come unlocked.
Click to expand...
Click to collapse
do i use S710d (China Telecom) 3.06.1401.0 or will it automaticly detect my phone and still be able to do the unlock even though my specific phone is not on the green list?
erik10002 said:
do i use S710d (China Telecom) 3.06.1401.0 or will it automaticly detect my phone and still be able to do the unlock even though my specific phone is not on the green list?
Click to expand...
Click to collapse
No need to flash anything, just follow the instructions on the htcdev site.
sent from HTC Raider on Bell LTE
Can anyone test if this runs on a vivid?
Sent from my HTC PH39100 using xda premium
This rom was Reprinted from bbs.xda.cn（china）
gtkansan said:
Can anyone test if this runs on a vivid?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
I attempted this on my vivid. But it failed reading...
Error Code: 170
CID Not Allowed
I will try again tomorrow after my exams
Sent from my HTC PH39100 using XDA App
I meant flashing the file without the unlock
Sent from my HTC PH39100 using xda premium
MODEL ID incorrect
update fail!
that was the error i got, (zip file in root of sd) i have a bell raider and have unlocked the bootloader, i will try a few more things and report back
update: tried extracting the files from the zip and putting them on my sd card and also tried on my internal, just put the zip on my internal as well and still nothing!
Anyone with a vivid attempt to flash this?
edit. Nm
Sent from my HTC PH39100 using xda premium
erik10002 said:
MODEL ID incorrect
update fail!
that was the error i got, (zip file in root of sd) i have a bell raider and have unlocked the bootloader, i will try a few more things and report back
update: tried extracting the files from the zip and putting them on my sd card and also tried on my internal, just put the zip on my internal as well and still nothing!
Click to expand...
Click to collapse
Same thing here.
hmmm...
The zip tried to load twice from hboot.
I tried the recovery option and rec'd the red triangle.
Ended up with correct time on home widget, but 4 hrs ahead in upper right menu.
So I flashed the Cingular ruu and back to normal.
I notice the img file is about 11 MB smaller than the ruu.
I attempted on Tuesday and again today to unlock bootloader, getting the same message as others above.
Here is the whole message you receive.
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: 170.
Error Reason: CID Not Allowed.
Big Dawg 23 said:
I attempted on Tuesday and again today to unlock bootloader, getting the same message as others above.
Here is the whole message you receive.
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: 170.
Error Reason: CID Not Allowed.
Click to expand...
Click to collapse
We have to wait. It took almost a month I think for the Amazed 4G.
Just long enough so that the people who got it on day-one are out of the return/exchange period
---------- Post added at 10:47 AM ---------- Previous post was at 10:44 AM ----------
Still downloading, but does this zip make any changes to the hboot? If so, has someone tried to do the htcdev unlock after running this?
Just wondering out loud, but even if hboot is updated...not sure if that would change the identifier token...
tried flashing through CWM just to see what happens! FAIL
Hi!
i follow the guide to s-off the device in the htc site, driver and all is installed but fastboot stuck on waiting for device... anyone have this problem?
I thought the SXL didnt have S-off yet? possibly you tried S-off for the wrong phone..
no no I checked my version is unlockable! Type the command to extract the codes I still waiting on device ... What can be? 2 days that I feel!
What do you mean that your version is unlockable? I know some SXL phones come shipped with S-off, but when they come locked there is no way to unlock yet..
You sure you dont have the sensation XE?
He probably means his bootloader can be unlocked
redbaronnl said:
What do you mean that your version is unlockable? I know some SXL phones come shipped with S-off, but when they come locked there is no way to unlock yet..
You sure you dont have the sensation XE?
Click to expand...
Click to collapse
Sorry i'm confused whit the root...(version can be rooted) but i think my bootlaoader is unlockable!! the problem is fastboot.exe that don't recognizes the phone!!
all fastboot command don't work (waiting for device error)
Make sure that you are booted into that bootloader thing, to get there: take out battery, restart phone + volume down, then when device is started into the bootloader and connected to USB you should be able to make the blue text go to fastboot with volume up/down. Then try unlocking again, it should work..
ok token extracted but when i press submit after i paste the token, received this error: Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won\'t work.
ok reset the phone and S-OFF!!
this two step are required???
1. You cant just flash a custom rom on this phone, firstly you will need the 'Chinese rom' which is here http://www.filefactory.com/file/c2ec...511_101713.zip and make sure it is on the SDcard part of your phones memory. Make sure it on the root of the SDcard because it will be easier to find later. Then you will need this rom RCMix3d Runny XL rom from here http://dl.dropbox.com/u/56143145/RCM...ny_XL_v1.2.zip (thanks to benjamin.j.goodwin) and make sure that is on the SDcard too with the other rom
2. Then you will need to download this file from here http://forum.xda-developers.com/show...7&postcount=18 it is the 'Chinese boot.img' and will need flashing from fastboot again. So put the phone in fastboot and extract the 'boot.img' from the 'boot.rar' file and put it in the fastboot folder on the PC. Open the command prompt again and type this... fastboot flash boot boot.img ... This should only need doing once if you're coming from a stock rom.
what is it for???
I dont know why, but it has to be done. It only has to be done once, after that you can happily flash whatever you want
---------- Post added at 11:01 PM ---------- Previous post was at 11:00 PM ----------
Godric8 said:
ok token extracted but when i press submit after i paste the token, received this error: Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won\'t work.
Click to expand...
Click to collapse
Be sure to extract only the token itself when its in the window it will look something like this
1 3wt23f26t23fv3
2 352632ev316531
3 53215423626262
Make sure you copy and paste only the fat underscored part, do NOT copy the line numbers you get in front of it
Godric8 said:
ok token extracted but when i press submit after i paste the token, received this error: Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
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: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won\'t work.
Click to expand...
Click to collapse
It appears that you didn't copy the token correctly.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA
Godric8 said:
ok reset the phone and S-OFF!!
Click to expand...
Click to collapse
CAn this be confirmed? I am still pretty sure that we do NOT have S-off yet???
Activate language ?
Hi, i have Sensation XL but no choice in Dutch language?
Can i activate it ?
phone is LOCKED.
HBOOT 1.25.0004 S-on
thanks
Sjakie
So I followed the bootloader unlock directions but at the end when I enter fastboot.exe -i 0x0fce oem unlock 0x(My Key Here) it comes back:
Failed (remote: Command not allowed)
Using the previous "getvar version" line it seems like my phone is connected properly. What can I do to solve this?
Thanks!
First you need to be sure if you can unlock the bootloader or not but checking the service info.
If i remember correctly i think you have to remove one number from your key.
Sent from my C6602 using xda premium
gm007 said:
First you need to be sure if you can unlock the bootloader or not but checking the service info.
If i remember correctly i think you have to remove one number from your key.
Sent from my C6602 using xda premium
Click to expand...
Click to collapse
Yeah, I got the key from unlockbootloader.sonymobile.com. As you said, I had to discard the last digit to make it 14 characters, but the code was sent to me all the same. I'm not sure that's the issue though
hanleyco said:
Yeah, I got the key from unlockbootloader.sonymobile.com. As you said, I had to discard the last digit to make it 14 characters, but the code was sent to me all the same. I'm not sure that's the issue though
Click to expand...
Click to collapse
Do you have bootloader unlock status= yes in service menu?
Maybe you have succeeded the unlock process,try to root it now.
Sent from my C6602 using xda premium
gm007 said:
Do you have bootloader unlock status= yes in service menu?
Maybe you have succeeded the unlock process,try to root it now.
Sent from my C6602 using xda premium
Click to expand...
Click to collapse
Sorry, this was the problem alright. Bootloader unlock status is no. I should have checked, thanks for the help.
hanleyco said:
Sorry, this was the problem alright. Bootloader unlock status is no. I should have checked, thanks for the help.
Click to expand...
Click to collapse
same as my poor docomo version
Hey guys, I am trying to get my bootloader unlocked so I can root my HTC One.
I have installed the Android SDK (when the boxes come up to choose what to install, I leave the default ones checked, and click install. Are there other ones I need to install as well?)
I have also installed HTC Sync Manager, the ADB fastboot files, and java.
I turn off the phone, hold volume down + power to get into the bootloader then go to fastboot.
While in fastboot, I connect the phone to my PC through USB.
I then go to the folder I extracted the Fastboot and ADB tools to, hold shift and right click, then choose Open Command Prompt Here.
I then paste fastboot oem get_identifier_token
and hit enter
Then I copy all of the information
<<<< Identifier Token Start >>>>
61968663D1276A576E5A307335193777
DB2EF827C1E9698DCC86392CE9D76590
2983EB9269241EA4891B1703EA06354B
F3AA81289E585B18863A3C796E301219
F89AFDAFEBC2CC32CAEEC6E58380E9E1
1DB5943E883A02D20C9438BD6E33E6C9
7C54C72FFFB3048827E83FBD8F93CA7B
88B6EE7C24F0AB6DD32408A9F6955E3A
ED98AF7EFDAD4DF731063F2B290BB729
7822B7A669872866AE88A749BACBAD67
F863EFCE5DC83C75D50B77334AD0C629
DE3AF195311E16E019E9260D9881AE5F
60D54B93C2AF18D8485A8EA95E62889F
0CA85388345CC540A7A2973EBB3ADF66
4C07957620120D0FBE40CF636F5A072E
BB533F03D1DF6230110F5EF257CB8089
<<<<< Identifier Token End >>>>>
I paste it into the htcdev.com/bootloader site
and it keeps telling me
Error Code: 160.
Error Reason: MID Not Allowed.
Unlocking Bootloader Failed
What am I doing wrong?
Can anyone help me?
It's the HTC One on Verizon
Thanks guys
Jtmarch86 said:
Hey guys, I am trying to get my bootloader unlocked so I can root my HTC One.
I have installed the Android SDK (when the boxes come up to choose what to install, I leave the default ones checked, and click install. Are there other ones I need to install as well?)
I have also installed HTC Sync Manager, the ADB fastboot files, and java.
I turn off the phone, hold volume down + power to get into the bootloader then go to fastboot.
While in fastboot, I connect the phone to my PC through USB.
I then go to the folder I extracted the Fastboot and ADB tools to, hold shift and right click, then choose Open Command Prompt Here.
I then paste fastboot oem get_identifier_token
and hit enter
Then I copy all of the information
<<<< Identifier Token Start >>>>
61968663D1276A576E5A307335193777
DB2EF827C1E9698DCC86392CE9D76590
2983EB9269241EA4891B1703EA06354B
F3AA81289E585B18863A3C796E301219
F89AFDAFEBC2CC32CAEEC6E58380E9E1
1DB5943E883A02D20C9438BD6E33E6C9
7C54C72FFFB3048827E83FBD8F93CA7B
88B6EE7C24F0AB6DD32408A9F6955E3A
ED98AF7EFDAD4DF731063F2B290BB729
7822B7A669872866AE88A749BACBAD67
F863EFCE5DC83C75D50B77334AD0C629
DE3AF195311E16E019E9260D9881AE5F
60D54B93C2AF18D8485A8EA95E62889F
0CA85388345CC540A7A2973EBB3ADF66
4C07957620120D0FBE40CF636F5A072E
BB533F03D1DF6230110F5EF257CB8089
<<<<< Identifier Token End >>>>>
I paste it into the htcdev.com/bootloader site
and it keeps telling me
Error Code: 160.
Error Reason: MID Not Allowed.
Unlocking Bootloader Failed
What am I doing wrong?
Can anyone help me?
It's the HTC One on Verizon
Thanks guys
Click to expand...
Click to collapse
Maybe your carrier blocked it?
Jtmarch86 said:
Error Code: 160.
Error Reason: MID Not Allowed.
Unlocking Bootloader Failed
What am I doing wrong?
Can anyone help me?
It's the HTC One on Verizon
Thanks guys
Click to expand...
Click to collapse
HTCdev unlock is not allowed by Verizon, head over to http://rumrunner.us/ for the solution
nkk71 said:
HTCdev unlock is not allowed by Verizon, head over to rumrunner for the solution
Click to expand...
Click to collapse
Yea, after doing some more research, it seems Verizon has blocked that method, which really sux. And I don't have one if
those $1100 java cards either.
But I did hear something about that rumrunner, I'll have to give that a try this morning. Thanks =)
Jtmarch86 said:
Yea, after doing some more research, it seems Verizon has blocked that method, which really sux. And I don't have one if
those $1100 java cards either.
But I did hear something about that rumrunner, I'll have to give that a try this morning. Thanks =)
Click to expand...
Click to collapse
http://rumrunner.us/ should do the job, it has specific packages for different ROM versions of Verizon.
nkk71 said:
HTCdev unlock is not allowed by Verizon, head over to rumrunner for the solution
Click to expand...
Click to collapse
nkk71 said:
rumrunner should do the job, it has specific packages for different ROM versions of Verizon.
Click to expand...
Click to collapse
Thanks guys. I've been busy rewiring my pc today (got some really nice individually sleeved cables), so I haven't had a chance to try rumrunner yet, but I'm going to give it a go now. Wish me luck!
I'll post back to let you know how it went
Hey guys. Just did this for my phone on Verizon and a buddies on AT&T, but I'm having issue with a Sprint version.
I retrieve the token code via ADB (and also tried WinDroid's Universal toolkit), but when I submit the token I'm receiving the following error:
"Error Code: 160.
Error Reason: MID Not Allowed."
Everytime I run the command I get a different token, but even after 4 tokens it still produces that error. Any suggestions?
Thanks!
EDIT: DISREGARD. TOTAL USER ERROR.
Jakeobie said:
Hey guys. Just did this for my phone on Verizon and a buddies on AT&T, but I'm having issue with a Sprint version.
I retrieve the token code via ADB (and also tried WinDroid's Universal toolkit), but when I submit the token I'm receiving the following error:
"Error Code: 160.
Error Reason: MID Not Allowed."
Everytime I run the command I get a different token, but even after 4 tokens it still produces that error. Any suggestions?
Thanks!
Click to expand...
Click to collapse
Have you tried doing it manually through Htc Dev?
You shouldn't get 4 different tokens for the same phone...each phone has it's own unique token.
BD619 said:
Have you tried doing it manually through Htc Dev?
You shouldn't get 4 different tokens for the same phone...each phone has it's own unique token.
Click to expand...
Click to collapse
I thought getting multiple different codes was odd too. I had also tried using the fastboot command (fastboot oem get_identifier_token) if thats what you meant. So this definitely isn't something everyone is encountering on this model, right?
Jakeobie said:
I thought getting multiple different codes was odd too. I had also tried using the fastboot command (fastboot oem get_identifier_token) if thats what you meant. So this definitely isn't something everyone is encountering on this model, right?
Click to expand...
Click to collapse
First I've heard of it.
If you want to PM me the token I can give it a shot.
Disregard
Hello.. I have the same problem. Every time I get different token. I'm using Hasoon2000 All-in-one toolkit
I havn't put any of generated token on htcdev because it is a little bit confusing
OK, using also fastboot oem get_identifier_token gives every time different token :/
Globus.gd said:
Hello.. I have the same problem. Every time I get different token. I'm using Hasoon2000 All-in-one toolkit
I havn't put any of generated token on htcdev because it is a little bit confusing
OK, using also fastboot oem get_identifier_token gives every time different token :/
Click to expand...
Click to collapse
Part of your issue may be that worthless tool kit.
I didn't think you were suppose to copy the header and the footer.
Just the characters of code.
mcwups1 said:
I didn't think you were suppose to copy the header and the footer.
Just the characters of code.
Click to expand...
Click to collapse
Lol, was waiting for someone to catch that. Absolutly Correct just the charachters. It actually tells you that and shows an example on the htcdev website
Sent from my 831C using XDA Premium 4 mobile app
I can read with understanding, also pictures on htcdev show what we need to copy
But the problem is different.
Header is not changed, numbers are different every time when you run
fastboot oem get_identifier_token
Click to expand...
Click to collapse