I get Error 160 at HTC Dev MID not allowed. The HOX is from AT&T, it's SIM unlocked and it's totally stock (***LOCKED*** and S-ON) phone never modified. Current image version: 1.73.502.1 I tried to install 3.18 RUU but I get error that it's the wrong image file. In few words what I would like to do is to unlock the bootloader. Hope you can help me, thanks!
I also tried to update to 2.20 and I get ERROR 140 BOOTLOADER VERSION ERROR. I'm using AT&T stock RUUs due to my HOX is totally stock.
You can't just unlock at htcdev, you need to get SuperCID first. What are your bootloader details?
Sent from my Evita.
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.16.32.09.01_3
version-cpld: None
version-microp: None
version-main: 3.18.502.6
version-misc: PVT SHIP S-ON
serialno: HT24WW302150
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: CWS__001
battery-status: good
battery-voltage: 3980mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
RUU's didn't work because I already was on 3.18, my bad. But still can't unlock bootloader through HTC dev, I keep getting same error!
I remembered that before unlocking bootloader I had to get cid to 11111111 but just could found 2.20 exploit
I need 3.18 exploit so I can get to SuperCID, do you have a link @timmaaa ?
Click the link in my signature, it's in that thread.
Sent from my Evita.
timmaaa said:
Click the link in my signature, it's in that thread.
Sent from my Evita.
Click to expand...
Click to collapse
I don't know if I am in 1.73.502.1 (as RUU's said) or if I am at 3.18.502.6 (which I find very rare because this device is at 4.0.3)
philohtc said:
I don't know if I am in 1.73.502.1 (as RUU's said) or if I am at 3.18.502.6 (which I find very rare because this device is at 4.0.3)
Click to expand...
Click to collapse
You are most likely already on 3.18, since the hboot for that is 2.14 (as shown in your bootloader details).
What does it say when you go to Settings>About>Software information>Software number?
Can somebody give me a link to SuperCID 3.18 in Windows (not Linux)? I checked but only founded for 2.20 thanks
I told you to click the link in my signature. All of the root exploits can be found within the thread that's in my signature. As redpoint said you need the 3.18 method.
Sent from my Evita.
Software number: 1.73.502.1 710RD
Sent from my HTC One using xda premium
Why are you posting that?
Sent from my Evita.
timmaaa said:
Why are you posting that?
Sent from my Evita.
Click to expand...
Click to collapse
@redpoint73 asked for it
Sent from my HTC One using xda premium
I see. Have you tried the 3.18 root method like we suggested?
Sent from my Evita.
@timmaaa I checked it out but I don´t have Linux, even if I had it, I really can´t get to config properly the sdk, because it doesn´t recognize the adb command eventhough I changed the directory or root from terminal.
You don't need Linux, you extract the attachment and enter the commands manually in a command prompt in Windows. It's the only way you're going to unlock your phone. You don't need the full SDK, only adb/fastboot.
Sent from my Evita.
ok i'll check that
timmaaa said:
You don't need Linux, you extract the attachment and enter the commands manually in a command prompt in Windows. It's the only way you're going to unlock your phone. You don't need the full SDK, only adb/fastboot.
Sent from my Evita.
Click to expand...
Click to collapse
it does not recognize "ln" command
You're typing it incorrectly then.
Sent from my Evita.
Related
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
i have a sensation 4g that I had rooted , super cid, and s-off using revolutionary method ,i'm thinking i have a wrong s-on / soft brick maybe that returned my phone to s- on but still rooted and super cid , I have tried the junopbear s-off method , various ruu , and everything else I could find after doing much research with no luck , in the process i lost super cid and now have T-MOB010 cid with htc unlock and rooted .
the problem I think I have had trying to run a ruu to just put back to stock is that I have hboot 1.29 with version 1.50.531.1 and cid T-MOB010 and cannot find a ruu that will match those or update without an error
version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.531.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any ideas or help on how to either s-off or return to stock and start from scratch would be appreciated
(I have tried kgs , all in one toolkit, control bear windows and linux in a virtual box, various ruu 3.33,1.50,3.32, all error , control bear says cowardly refusing to s off error code B2 B6 41 C9 have flashed stock rooted ics with stock recovery and with 4ext touch with smart flash )
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
rzr86 said:
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
Click to expand...
Click to collapse
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
watters33 said:
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
Click to expand...
Click to collapse
error 155 AFAIK is a connection issue
when you connect the device to pc from bootloader before using the ruu.exe in the hboot screen must say fastboot usb
did you check that?
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
watters33 said:
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
rzr86 said:
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
watters33 said:
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
Click to expand...
Click to collapse
give a try with these drivers
http://forum.xda-developers.com/showthread.php?p=36523572
http://d-h.st/v0p
http://forum.xda-developers.com/showthread.php?t=1668276&highlight=tool (second post->old info(click to show content and you will see somewhere a link for htc drivers)
try each one and see if you have success with ruu installation
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
IIRC the RUU for your device reverts all of that. Not 100% sure about the S-ON though.
I've read somewhere in another guild that it's necessary to first Relock your bootloader (using the oem lock command) and afterwards use the right RUU for your device...
I thought this could be helpful
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader first will cause this to not be the case?
DRUMROT said:
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader it first will cause this to not be the case?
Click to expand...
Click to collapse
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
FantasyGamer said:
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
Click to expand...
Click to collapse
Yeah, I'm assuming I'd have to do some more then just run the RUU.
I'd gladly give it a go but like I posted earlier, I'd like to know if there is a certain order to do this in. If I run the RUU before removing s-off, will that make things easier? Harder? No different?
Anyone?
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
FantasyGamer said:
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
Click to expand...
Click to collapse
Hmmm, all right. I've never used the all-in-one kit but I've noticed it has a "back to s-on" function so I'll give it a try. I'm on Linux so I need to run it in Wine (Windows emulator) so hopefully there's no hiccups.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
1)If you have put on a modified HBoot (such as to remove tampered or red warning) return to stock.
(only added this because if you S-on with modified HBoot it will brick your phone)
2)Run RUU.exe
3)Reset lock status flag
http://forum.xda-developers.com/showthread.php?t=2155955
4)S-ON your phone
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
---------- Post added at 01:15 PM ---------- Previous post was at 01:05 PM ----------
Edited that, If anyone notices a problem please post.
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
FantasyGamer said:
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
Click to expand...
Click to collapse
No, it doesn't need to be locked when S-OFF.
The most important is running the RUU that matches your CID. (since you are s-off it is easy to change the CID to whatever you want, and thus run whatever RUU you want)
i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot
Hi
begining statues of my phone:
my phone is one xl(evita) and relock , s-on then read more!
i did change cid of HTC__J15 to CW___001 and then s-on and relock the bootloader but now i can't unlock retry...!!
the old carrier was GCC but then relock is at&t !
please help me...
tnx
Why did you change it to the at&t CID? The at&t CID is blocked by htcdev. You need to go through the hassle of getting SuperCID so you can unlock your bootloader now. Plus, there's no advantage to having the at&t CID because you can't install any firmware from the standard Evita onto your middle eastern variant. This is a great example of why you shouldn't do anything when you don't know what you're doing. All of the information I've just given you is readily available in our forum hag you done some research. Anyway, what are your bootloader details?
Sent from my Evita
timmaaa said:
Why did you change it to the at&t CID? The at&t CID is blocked by htcdev. You need to go through the hassle of getting SuperCID so you can unlock your bootloader now. Plus, there's no advantage to having the at&t CID because you can't install any firmware from the standard Evita onto your middle eastern variant. This is a great example of why you shouldn't do anything when you don't know what you're doing. All of the information I've just given you is readily available in our forum hag you done some research. Anyway, what are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
(bootloader) version-baseband: 3.12.38.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.01.401.03
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2CTW303033
(bootloader) imei: 35437005019****
(bootloader) product: evita_utl
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8350000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3964mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b27b8968
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
my firmware version is 3.12 and i can't super cid with XPwn xploit and then unlock !!
What can I do to get My phone unlocking?
tnx
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
timmaaa said:
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
Click to expand...
Click to collapse
Would having his device j tagged help him. I think its pretty cheap to get done now , idk about in the middle east tho lol
Senseless Power Unlocked
timmaaa said:
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
Click to expand...
Click to collapse
yes , i know...
if i do super cid with XPwn xploit , My phone is bricked?
DESERT.TECH said:
Would having his device j tagged help him. I think its pretty cheap to get done now , idk about in the middle east tho lol
Senseless Power Unlocked
Click to expand...
Click to collapse
The problem is I doubt they have the correct stuff for the middle eastern variant.
Master King said:
yes , i know...
if i do super cid with XPwn xploit , My phone is bricked?
Click to expand...
Click to collapse
Maybe. But I think it just won't work. You can take the risk and try but if it was me I wouldn't.
Sent from my Evita
timmaaa said:
The problem is I doubt they have the correct stuff for the middle eastern variant.
Maybe. But I think it just won't work. You can take the risk and try but if it was me I wouldn't.
Sent from my Evita
Click to expand...
Click to collapse
ok
now can i install RUU from at&t brand for upgrade frimware & then super cid?
As an example:
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe
I don't know if it's safe. I've seen at least one person brick their phone by installing firmware from the standard Evita onto the middle eastern variant.
Sent from my Evita
What should I do now?
I want to unlock...
please help me
Well first I'd edit out the imei from the post about your bootloader settings..
Like timmaaa said, you're at a point where you have very little options. You could try XPwn or RUU but it's a huge risk. See, this is why you read...so you don't do things like this...
Sent from my One X using Tapatalk
You can't, that's what I've been trying to tell you. The things you've done to your phone have made it impossible.
Sent from my Evita
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S off
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
You don't need root access, because you have s-off. You can simply use fastboot to change the CID to SuperCID.
Code:
fastboot oem writecid 11111111
Next time, do a bit of research before creating a thread. Pretty much every question you could think of asking has been asked, and answered within our forum. Check out all of the links in my signature, almost everything you'll ever need can be found there.
Sent from my Evita
Again Question sir
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?[/QUOTE]
jezi251 said:
I have HTC One X- AT&T(Evita) With S4 processor. In fastboot, First three Lines are:
Tempered
Locked
S ON
I went through complete process, mentioned at HTC devs, but un-successful. the following error occured:
Error 160
MID not allowed
I have to change CID, but for doing this, i must have root access.
Please anybody guide me step by step procedure to root/bootloader unlock?
Click to expand...
Click to collapse
The at&t CID is blocked at htcdev, so you need to get SuperCID in order to unlock your bootloader. Reading the stickied threads (specifically the Evita FAQ thread) in the section you've just posted in world have uncovered this information. You're gonna want to read all of the threads in my signature so you can familiarise yourself with this device, and so you don't ask a question that's already been asked and answered a million times before.
Please post your hboot version, you'll find that in your bootloader screen.
You said earlier that you have s-off, why it s-on now?
Sent from my Evita
Evita pvt ship s-on
HBOOT-2.14.0000
Earlier mistaken s off written
Sent from my HTC One X using Tapatalk
Have you read the threads I mentioned?
Sent from my Evita
First I have to root it for cid change whts the procedure in this situation??
Sent from my HTC One X using Tapatalk
You need to use the 3.18 root method. Full instructions in my How-To Guide For Beginners thread.
Sent from my Evita
recovery
when i follow the procedure of rooting...when it goes to recovery screen (white one) its wait for 5 to 8 seconds and then restart normally..i can't goto recovery ..why??
That doesn't really make sense. The recovery screen isn't white, are you talking about the bootloader? And can you please be more specific about what's happening? I can't help you if you're giving vague two sentence posts like that.
Sent from my Evita
twrp
when i install twrp 2.7..after enter the recovery mode white htc scree appears...when i install twrp 2.2.0..on recovery it opens but touch screen don't works no button works just power button works which locks the twrp...can u send me valid link of twrp 2.7 because at twrp website at 99% downloading stops...
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
details of my evita
timmaaa said:
Why did you flash 2.7 if it didn't download completely? That's a surefire way to brick your phone. The md5 wouldn't have matched either. You'll find downloads here:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
jezi251 said:
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT26GW303783
imei: xxxxxxxxxxxxxxxx
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
battery-status: good
battery-voltage: 4141mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
can i update my jb to 4.3??how?
Click to expand...
Click to collapse
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
rom
timmaaa said:
First thing you need to do is edit your IMEI out of that post, never post your IMEI publicly. It looks like you've successfully gotten s-off now too which is good. What kind of ROM do you want?
Sent from my Evita
Click to expand...
Click to collapse
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
jezi251 said:
i want that rom which works perfectly not issue of baseband,network ...etc...can u suggest me correct rom regarding to my specifications..now i upgraded my hboot to 2.15..
Click to expand...
Click to collapse
I actually meant do you want a Sense ROM or an aosp ROM? Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Our dev sections are as follows:
One XL Android Development (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1541
One XL Original Android Development (aosp ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726
Have a look through the available ROMs and pick one you think will suit you.
Sent from my Evita
evita
thanks buddy
recovery
jezi251 said:
thanks buddy
Click to expand...
Click to collapse
i want to update my recovery from 2.7.0.0 to 2.7.1.0..when i insert fastboot flash recovery openrecovery-twrp-2.7.1.0 in CMD
error:cannot open 'openrecovery-twrp-2.7.1.0'...
because i want to install A.P rom or carbon or candy cat..
justnow i have 4.1.1 stock version,s-off,tempered, hboot 2.15
help me!!
when i try to install any rom by twrp 2.7.0.0 it gives error ..only cm11 snapshot installs but sometimes it hangs ...so i restore to 4.1.1...
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
recovery
timmaaa said:
Is that the exact command you're giving? It looks like you're missing the ".zip" on the end of the filename. For example, if the filename is "openrecovery-twrp-2.7.1.0.zip" then the command should look like this:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0.zip
If you have filename extensions (.exe, .doc, .zip) turned off in Windows, this could be the reason why you're missing the extension from the command.
Sent from my Evita
Click to expand...
Click to collapse
i have also tried with .zip ext but it not works