Related
Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
Click to expand...
Click to collapse
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_178580_signed.exe
Click to expand...
Click to collapse
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much
Samwan said:
Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much
Click to expand...
Click to collapse
Hi there,
You need to flash the RUU that is supported by your phone's version.
Turn the phone into fastboot mode (voldown + power), click fastboot, wait till it shows fastboot usb.
Open console in PC and find the android tools, type:
<androidtool dir>\ fastboot getvar all
It should come up as: INFOversion etc.
What you need to look for is INFOversion-main and INFOcidnum
Go to http://forum.xda-developers.com/showthread.php?t=1002506
and download the RUU that matches!
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231
anchemis said:
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231
Click to expand...
Click to collapse
Very helpful reply buddy.
But i don't think the last line applies to him. He said he just got the phone, and it had the v2.xxx hboot to begin with, so he went looking to downgrade. If he had acheived S-off, he wouldn't be asking how to S-off in the first place.
@OP : You should try using a Goldcard when faced with a difficult choice of Region-specific RUUs. Try making one (Use Search function) and then re-running the European RUU. (You may also have to check your Misc_version to ensure compatibility, or you may hit a roadblock again.
Hi,
I just wanted to confirm for further searches / use that what has been stated inside the first answer is fully working.
I got my Desire S downgraded, S-OFFed and was able to flash MIUI, so it's finding it's way to my girlfriend as birthday present soon thank you for helping.
I can't even re-unlock the bootloader for some reason either.
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I mistakenly used the JBFW tool on my AT&T branded phone (CID: CWS__001) to change the CID to HTC__001, not realizing that my phone was still S-ON and the CID changing option was apparently for S-OFF only. I had root, I had the bootloader unlocked. Now I can't even get into recovery, and I think since my CID is apparently stuck as HTC__001, that the RUU for my phone's actual CID won't work. I should note that before I relocked the bootloader, I tried to change my CID back to the SuperCID but it would just freeze the phone. That's why I tried to relock it, hoping it would help. I thought I could just unlock it again, but it won't work. I can't flash anything via ADB, it all fails. This is the RUU I was trying to use:
RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed.exe
and I got a Wrong Customer ID error.
Is there anything I can do to remedy this situation or am I at the warranty center's mercy? Thank you in advance for any help.
im in the same boat, hopefully we get some help here soon, ive got another phone on the way from the warranty center but they want the one i have now and if they see its been tampered there gonna send me a bill for the full price of the phone. wish i could help.
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Myrder said:
We have the exact same phone. I have a dif RUU though. Mine says AT&T. I'll find the link to dl that RUU in a sec. Currently away from the pc where I have that page bookmarked
EDIT: I do believe that all the Cingular RUUs don't work anymore, their currently out of business thanks to our carrier AT&T... Don't know why you would try and use a Cingular RUU...
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Cingular is att.
If you see a ruu that says.Cingular,it will work
Sent from my HTC One XL using xda app-developers app
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
Myrder said:
Now, this is the correct RUU http://www.4shared.com/file/35bbU4_Y/htc_one_x_RUU_2205027_att_us_0.html. It's going to take anywhere from 10-25min to complete.
After you complete the RUU, go to this thread http://forum.xda-developers.com/showthread.php?t=1952426
Download and follow each step. You will then be rooted, correctly.
---------- Post added at 03:18 PM ---------- Previous post was at 03:16 PM ----------
Cingular doesn't have an RUU for the people that have 2.20, I've looked.
Click to expand...
Click to collapse
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I stand corrected.
Myrder said:
I stand corrected.
Click to expand...
Click to collapse
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
absolutelygrim said:
It's all good bro! You're trying to help,.that's all that matters. I've been trying to take a break from the Q&A and work on the unbricking. But something attracts me here :crying:
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have a nag for wanting to help people and it seems you do too. Lol.
Speaking of, I've been trying to keep up with that thread you have. How's that coming?
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Lmao, now that is a hard pickle to get yourself into!!!
If cid was changed to HTC_001 properly, go snag a new token off htcdev website........I'm not going to explain the rest
Sent from my HTC One XL using Tapatalk 2
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Just to let you know our (The HTC One XL). Super Cid is 1111111 (I'm pretty sure it's seven 1's?). In any case you should not be looking at the One X (Tegra) forums and much rather look at the One XL/ATT One X forums unless you enjoy staring at a $600 paperweight.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
8, I believe
First rfatmen
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
knyghtmayre said:
I wasn't able to change my CID back to the SuperCID via any method I could find. And I don't think the CID was "properly" changed/spoofed to HTC__001, but I definitely could still get verified tokens from HTCDev. The problem was that I couldn't re-unlock it by pushing the .bin via ADB because it just failed. Since I'd upgraded less than a week ago, I was able to convince the semi-clueless guy at AT&T to exchange my One X.
Click to expand...
Click to collapse
That's the spirit.
absolutelygrim said:
The 1.85 ruu says Cingular in the file name. Cingular may not have an ruu for 2.20 because it was released as "att" ota.
If you look at 1.85 it says AT&T Cingular
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Crappyvate said:
link to 2.20 ruu http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Click to expand...
Click to collapse
well I know there is an RUU for it silly, I meant the naming convention isn't the same as previous RUU's
DvineLord said:
he wont be able to flash the ruu because he changed his cid to the international one x to try to flash the international jb rom which would of bricked his phone if it worked. running "OUR" supercid might get it set to supercid and let you reflash ruu.
Click to expand...
Click to collapse
I accidentally flashed recovery to boot portion. ie
HTML:
fastboot flash boot twrp.img
instead of
HTML:
fastboot flash recovery twrp.img
.
Then I also flashed recovery to recovery portion thinking that I can boot into recovery.
But now my phone boots and stays at twrp logo.
Even when I try to boot into recovery the same twrp logo nothing happens.
Is there any way to unlock bootloader on at&t evita one x that has had the ota JB update?
Unfortunately, I did not root this phone prior to applying the update.
Any help/answers are obviously welcome.
I have tried going through the htcdev.com hack, but get the following error after entering my token id: Error Code: 160.Error Reason: MID Not Allowed.
tamanedalabe said:
Is there any way to unlock bootloader on at&t evita one x that has had the ota JB update?
Unfortunately, I did not root this phone prior to applying the update.
Any help/answers are obviously welcome.
I have tried going through the htcdev.com hack, but get the following error after entering my token id: Error Code: 160.Error Reason: MID Not Allowed.
Click to expand...
Click to collapse
At the moment there is not.
At the very least you need to be able to gain temp root access in order to change the CID to allow you unlock it through htcdev.
The error you get is because AT&T don't allow bootloader unlock through htcdev.
thejosh86 said:
At the moment there is not.
At the very least you need to be able to gain temp root access in order to change the CID to allow you unlock it through htcdev.
The error you get is because AT&T don't allow bootloader unlock through htcdev.
Click to expand...
Click to collapse
Is that something new that came with the ota update? I only ask because prior at&t evita one x's (2.20.502.7 ruu) had no issues with the htcdev unlock process
No it's been that way since the beginning.
With the 2.20 RUU there was an exploit so you could change your cid to another carrier or supercid which allowed you to unlock it through htcdev.
You still couldn't unlock it if it still had AT&T's cid on the device.
Sent from my HTC One X using xda premium
Has this been resolved? I'm following Hasoon 2000's guide to unlocking the bootloader on my htc one x (ATT) and there are many people who have had success and are posting on Hasoon's thread as recently as a few hours ago, so I'm assuming it is allowed now, but I'm still getting the error 160 code. I'd like to post directly on that thread but I'm a noob and don't have the minimum number of posts...
Any help appreciated
Bump
If you have the latest ota update, you will be unable to gain temp root. You have to change your CID to be able to unlock bootloader with HTC dev. Unless you were s-off, there is no way at this time to accomplish this.
Sent from my HTC One X using xda premium
the 3.18 update introduced system write protection so even with root, one cannot alter the CID unless one is S-OFF.
exad said:
the 3.18 update introduced system write protection so even with root, one cannot alter the CID unless one is S-OFF.
Click to expand...
Click to collapse
Any updates on this? Is there a way to change the CID on stock 3.18 update now?
averylowiq said:
Any updates on this? Is there a way to change the CID on stock 3.18 update now?
Click to expand...
Click to collapse
One word:
Search.
Sent from my Evita
timmaaa said:
One word:
Search.
Sent from my Evita
Click to expand...
Click to collapse
I tried but couldn't find anything useful.
averylowiq said:
I tried but couldn't find anything useful.
Click to expand...
Click to collapse
What exactly do you want to do?
Sent from my Evita
timmaaa said:
What exactly do you want to do?
Sent from my Evita
Click to expand...
Click to collapse
I want to be able to install nightly CM10.1 on an AT&T HTC One X. I just received this phone as a warranty replacement from AT&T and all my attempts to root this phone have been futile.
Which root method have you tried?
Sent from my Evita
sim unlock only , One x Att , Hboot 1.14
Is there a method to unlock just sim so i can use one x with different carrier ...please help
bratuha said:
Is there a method to unlock just sim so i can use one x with different carrier ...please help
Click to expand...
Click to collapse
There is no method to unlock the sim right now regardless of root, s-on, s-off, whatever. No one's cared to look for one. I would but I don't have another carrier sim to test with.
sim unlock only , One x Att , Hboot 1.14
exad said:
There is no method to unlock the sim right now regardless of root, s-on, s-off, whatever. No one's cared to look for one. I would but I don't have another carrier sim to test with.
Click to expand...
Click to collapse
So basicly one x can be used one on ATT network , iam i right ? and no way to use it on any other one ?
bratuha said:
So basicly one x can be used one on ATT network , iam i right ? and no way to use it on any other one ?
Click to expand...
Click to collapse
as of the moment, that's correct.
It can be used on whatever network it came from. Other carriers sell the evita too. You can always try contacting the Carrier and requesting the unlock code or buying an unlock code from an unlock service.
Sent from my One X using xda app-developers app
Unlock windows version HTC 3.18 ATT
timmaaa said:
What exactly do you want to do?
Sent from my Evita
Click to expand...
Click to collapse
I want to root my HTC One X on AT&T, with 3.18. I have also searched, and come up with nothing. So the "one word - search" is not helpful, why even post that? I can see it being helpful if you posted your search results on how to do it, but you didn't.
Thanks
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk
You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.
To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk
Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk
redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita
timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only
What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita
lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root
Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita
timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.
Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app
I've tried to unlock the bootloader for my HTC One X multiple times but every time it's failed, I keep getting the same error on HTC Dev
"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."
Any Help?
You have to have superCID first.
Use this: http://forum.xda-developers.com/showthread.php?t=2283760
Sent from my One Xl using xda premium
magnetboard said:
You have to have superCID first.
Use this: http://forum.xda-developers.com/showthread.php?t=2283760
Sent from my One Xl using xda premium
Click to expand...
Click to collapse
I tried this method and double-clicked the "Only One X" file and it failed to put my CID at 11111111 it stayed at CWS__001
Try doing the steps by yourself. Usually doing it that way will work better
Sent from my One Xl using xda premium
magnetboard said:
Try doing the steps by yourself. Usually doing it that way will work better
Sent from my One Xl using xda premium
Click to expand...
Click to collapse
How would I go about this?
Look at the first post of that page. It has all of the commands.
Sent from my One Xl using xda premium
Hang on, that might not even be the right method depending on his current firmware.
@frozen23
I need to see your bootloader details please, then I can direct you to the right method.
Sent from my Evita
See the FAQ thread sticky at the top of this section, and look at Question 5. Find the correct root/bootloader unlock method for your current firmware.
They call them "frequently asked questions" for a reason".
I assume you mean the lines of text at the top of the bootloader screen, so here
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.18.0000
RADIO -1.35A.32.45.27
OpenDSP-c33.1.0.45.1128
eMMC-boot
Dec 3 2013, 17:10:01:-1
HBOOT
There's no method for your specific firmware, the last known method might work though. Here it is:
http://forum.xda-developers.com/showthread.php?t=2285086
Give that a try. If it doesn't work it means they've plugged the "hole" so to speak, and you'll have to wait for a new exploit to be found.
Sent from my Evita
If this method dosen't work is there a way to perhaps downgrade to a firmware where I can root it?
No there isn't, otherwise everyone that came before you world have done that. If it doesn't work there's nothing you can do except wait for a senior dev to find a crack.
Sent from my Evita
Ok Thanks for all of the help I'll try out this method
Btw is there a windows version of this root method?
It is Windows compatible. Check out my q&a thread (link in my signature), I wrote a quick guide of that method for someone in the last few pages.
Sent from my Evita
I tried using your guide and when I executed one of the adb shell commands I got this error
"adb shell ln -s /data/local/tmp/busybox /data/local/tmp/sed link failed File exists"
Can you please check your CID?
Code:
fastboot oem readcid
Sent from my Evita
Yea sure it's CWS__001 isn't it suppose to be "11111111"?
Did you use the fastboot command to get your CID?
Sent from my Evita
Yes I did
"C:\sdk>fastboot oem readcid
...
(bootloader) cid: CWS__001
OKAY [ 0.010s]
finished. total time: 0.010s"