Okay so my friend asked me to fix a phone that he says one day it got stuck in boot splash screen. He claims he did not try to flash a custom Rom or something but he said he hadn't.here's some of the phones info
HTC one x
***TAMPERED***
***UNLOCKED***
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
Can anyone sheed some light on the subject.
I don't know how to use adb and fastboot
And I have Windows xp and Mac 10.6 and lynx
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Mr Hofs said:
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Click to expand...
Click to collapse
As if by magic, it appears in the One XL forum.
I think your friend is telling fibs, phones don't just magically stop booting for no reason. Please tell him to own up to whatever activities lead to this situation, as embarrassing as it might be, I need to know how this happened in order to help properly.
Now, just to be clear, the phone is actually the HTC One XL, not the HTC One X. They look similar but are actually very different. What recovery is installed on the device?
Another question for you, why isn't your friend posting here and attempting to fix this problem himself? If he can't recover from a simple problem like this (or can't be bothered learning/trying) he honestly has no place having a modified phone. That might sound harsh but it's the truth, this is very basic knowledge, it's flashing 101. Knowing how to recover from something like this is an essential skill for anyone who owns a modified phone. If your friend isn't interested in being honest about what lead to this situation, or interested in learning how to recover from this situation, my only advice is to return to the device to stock and leave it that way. I'd strongly urge him to get on here and post himself, and do some reading to educate himself on the ins and outs of modified devices.
Sent from my Evita
sorry for being so vauge
My friend is a lady friend who had no idea how the phone could have become modified. The phone is a HTC one X and my lady friend said she would love nothing more then to have a stock phone. My friend has no intrest in leaning how the in's and out's of HTC but, I on the other hand would love to learn about HTC and Android. I come from a n Apple community and have a little knowledge but not a lot.
Anything you can tell me would help greatly, and I would be indeed greatful.
Sincerely Nanamkin
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Thank you so much
timmaaa said:
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Click to expand...
Click to collapse
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Nanamkin said:
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Click to expand...
Click to collapse
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Man your GOOD
timmaaa said:
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Click to expand...
Click to collapse
I am sooo sorry. you are absulotly right, and you are good! how did you know that? lol
here is the right info.
TWRP 2.3.1.0
im sorry i cant boot into the phone to check the setting/about phone for a software version. do you know any other way?
and while i was messing around i figured out how to install ADB and FASTBOOT and use it.
I'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the CID for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita
got it
timmaaa said:
i'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the cid for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
sent from my evita
Click to expand...
Click to collapse
cid:11111111
Ok. To get the phone back to stock you Erik need to run an RUU, but in order to do that safely you'll first need to get s-off. To get s-off you're gonna need a booting ROM on the device. Purely for this exercise I think Kickdroid would be your best option, head to our Android Development section and find the Kickdroid thread, download it, and use TWRP recovery to install it. Look in the How-To Guide For Beginners thread in my signature for full instructions on how to flash the ROM. Please note, you'll also need to flash the boot.img from the ROM zip via fastboot after flashing the ROM.
Sent from my Evita
got it
Okay I have the Rom on my phone now what?
Nanamkin said:
Okay I have the Rom on my phone now what?
Click to expand...
Click to collapse
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
your awesome
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
oh yeah i was over there just a little awhile ago. i een your name so i tiend to fallow it but couldnt get the rom. thank you sooo much
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Nanamkin said:
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Click to expand...
Click to collapse
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
I got the rom to work
timmaaa said:
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
Click to expand...
Click to collapse
I got the rom to boot after fallowing your directions(like you said)lol. but when i do steps 7 the 3 codes it says there are no directory. I got the first one to go but the other 2 would not work
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
got the os to boot
timmaaa said:
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
Click to expand...
Click to collapse
okay so i have the rom on the phone (kickdroid) and now i cant run the last 3 codes on step 7. any clue. I have soffbin zip unzipped in the directory but where exactly do i put it? i have it in the same folder as adb and fastboot is that right?
Related
I understand there are other topics on this situation, but I was hoping to get something more specific to my problem, PLEASE, I REALLY NEED HELP!
Details about my phone...
AT&T HTC ONE X
Unlocked - Using SIMPLE MOBILE
When booting into Bootloader:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08.24
When I boot into Recovery:
This build is for development purposes only
Do not distribute outside of HTC without HTC's written premission.
Failure to comply may lead to legal action.
After about 30 seconds the phone reboots.
I received the phone unlocked, but did the rooting myself with help from threads on xda developers. It seems it all went well, when I access RootChecker, it is a success and I have access to Root.
I want to flash custom roms but am not able too!
Please, help me figure out what is wrong with my phone not being able to boot into recovery!
I really, really, need help on this issue!
Did I do something wrong and if so what did I do?! I followed everything about adb and using the cmd on windows. Please help me!
Thank you anyone for any type of information you might be able to give me, I want everyone to know I really appreciate it!
Thank you so much!
mg818 said:
I understand there are other topics on this situation, but I was hoping to get something more specific to my problem, PLEASE, I REALLY NEED HELP!
Details about my phone...
AT&T HTC ONE X
Unlocked - Using SIMPLE MOBILE
When booting into Bootloader:
TAMPERED
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08.24
When I boot into Recovery:
This build is for development purposes only
Do not distribute outside of HTC without HTC's written premission.
Failure to comply may lead to legal action.
After about 30 seconds the phone reboots.
I received the phone unlocked, but did the rooting myself with help from threads on xda developers. It seems it all went well, when I access RootChecker, it is a success and I have access to Root.
I want to flash custom roms but am not able too!
Please, help me figure out what is wrong with my phone not being able to boot into recovery!
I really, really, need help on this issue!
Did I do something wrong and if so what did I do?! I followed everything about adb and using the cmd on windows. Please help me!
Thank you anyone for any type of information you might be able to give me, I want everyone to know I really appreciate it!
Thank you so much!
Click to expand...
Click to collapse
Here you go
http://forum.xda-developers.com/showthread.php?p=30373108
Sent from my One X using Tapatalk 2
you should probably update your recovery http://www.teamw.in/project/twrp2/99
in bootloader run these commands from the pc
fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
then on the phone try to get the phone to go into recovery. older recoveries had a hard time getting into recovery from bootloader.
if that doesn't work boot into your regular rom and run "adb reboot recovery" make sure usb debugging is turned on.
the website says "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!"
I do not have a S-OFF device. Is it impossible to go into recovery? Should I try this method regardless?
mg818 said:
the website says "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!"
I do not have a S-OFF device. Is it impossible to go into recovery? Should I try this method regardless?
Click to expand...
Click to collapse
You need an unlocked boot loader to install recovery.
You can do it with S-off also.
absolutelygrim said:
You need an unlocked boot loader to install recovery.
You can do it with S-off also.
Click to expand...
Click to collapse
still not working, CMD says can not flash. it is getting really annoying actually. i do not know what to do!
i want to flash jelly bean already!
mg818 said:
still not working, CMD says can not flash. it is getting really annoying actually. i do not know what to do!
i want to flash jelly bean already!
Click to expand...
Click to collapse
Ok. PM me your teamviewer.
And don't post a question in the general section next time.
But don't go remake this thread, just wait for it to be moved.
absolutelygrim said:
You need an unlocked boot loader to install recovery.
You can do it with S-off also.
Click to expand...
Click to collapse
now i am using htc one x evita aio kit by hasoon 2000 v1.1 and flashed twrp 2.3.1.0...my phone is rebooting right now....
waiting....
waiting.....
waiting......
waiting.......
now i am rebooting into recovery....
and......
.............
..............
SAME SH$T
wait wait...it went into recovery after it gave me that bs message!
very nice!
highly recommend hasoon!
mg818 said:
now i am using htc one x evita aio kit by hasoon 2000 v1.1 and flashed twrp 2.3.1.0...my phone is rebooting right now....
waiting....
waiting.....
waiting......
waiting.......
now i am rebooting into recovery....
and......
.............
..............
SAME SH$T
wait wait...it went into recovery after it gave me that bs message!
very nice!
highly recommend hasoon!
Click to expand...
Click to collapse
I swear to (insert religious/scientific belief here) you better not flash IceColdJelly or ANY International ROM..
Stay in the AT&T, Rogers HTC One X, Telstra One XL forum
absolutelygrim said:
I swear to (insert religious/scientific belief here) you better not flash IceColdJelly or ANY International ROM..
Stay in the AT&T, Rogers HTC One X, Telstra One XL forum
Click to expand...
Click to collapse
LOL just slam your head in to the wall man its going to be less pain
CheesyNutz said:
LOL just slam your head in to the wall man its going to be less pain
Click to expand...
Click to collapse
:crying: why won't they listen to me? all is lost
Sent from my HTC One XL
Okay so if you are like me and have installed the OTA Update or ran the 3.18 ruu with an S-On Device chances are You are currently hard bricked which in most cases leaves 4 options, Option 1. Try to get a replacement through the carrier or Manufacturer Option 2. Send it off for a repair or Option 3 try and fix it yourself. Option 4 Toss the device and look elsewhere.
I Personally am going with Option 3 and am attempting to figure out a working Unbrick Method that does not require a RIFF box so with that said i will be working in this thread in an effort to get an unbrick project working. Feel free to add your knowledge, input, and advice in the proceeding posts below.
Please Note if you are using Windows 8 you will need to disable driver signature enforcement, while there are many ways to do this by far the easiest way is to open an Elevated Command Prompt and enter
Code:
bcdedit /set {globalsettings} advancedoptions true
when you restart your Computer choose option 7. To Disable Advanced Boot Options Enter
Code:
bcdedit /set {globalsettings} advancedoptions false
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
d3thstalker said:
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
Click to expand...
Click to collapse
no my device is literally hard bricked, no bootloader/hboot no os no recognition on pc other than qhsusb_dload i remember working on the same issue with the htc shooter on sprint so im trying the method we used to recover our device after intentionally bricking it which requires linux but in any case im almost there im currently trying to track down the ENG hboot for the evita atm
FragmentedLogik said:
im currently trying to track down the ENG hboot for the evita atm
Click to expand...
Click to collapse
If you find one, let Leamstears know. He has a thread posted somewhere asking for it.
Also, you might search for unbrick evita in general section. There was a thread started awhile back by my buddy.
Sent from my HTC One X using xda premium
i have you made any progress ??? my htc one s is hard briked too
https://www.dropbox.com/sh/a1n5s4r61wfh7qr/gkgxmKXwka/Evita soff partitions
Maybe this will help.
Sent from my One X using xda premium
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
PUfelix85 said:
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
Click to expand...
Click to collapse
I'm not sure it will really help. The first part is to run brickdetect.sh. That script appears to try to enumerate the partitions. I tried to enumerate my partitions using the manual steps in mirgantrophy's unbrick evita thread to no success before I sent my device off for JTAG. You could always try to run the brickdetect.sh script and see though. It doesn't do anything to your phone. It just searches dmesg (a Linux log) for the partitions being detected when you attach the bricked phone via USB. Don't run the rest of it though. ;-P
I'd like see a method to fix emmc of an htc inspire 4g(htc ace). Can any of our methods be transposed for other htc devices?
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Trozzul said:
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Click to expand...
Click to collapse
I definitely would not try this on any device other than the device it's intended for. Completely different chipsets.
Sent from my Evita
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
gato06 said:
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
Click to expand...
Click to collapse
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
One X at&t
gato06 said:
One X at&t
Click to expand...
Click to collapse
What ROM did you flash?
Sent from my Evita
timmaaa said:
What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
gato06 said:
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
Click to expand...
Click to collapse
Well you've bricked your phone. That ROM is not for our phone.
Sent from my Evita
How unbrick :'( You have idea?
You can either get a jtag repair or send it to HTC to have the motherboard replaced. Jtag is the cheaper option. When you get it back, make sure you stay within our forum and only flash software intended for our device.
Sent from my Evita
ran the 3.18 ruu with an S-On Device
Click to expand...
Click to collapse
i never thought run RUU with s-on device will brick it. Will it be more correct to say "run RUU on device with s-on & supper cid will brick you device"
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
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
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001
Hello everybody! I need help urgent! I have my AT&T HTC One X (XL according to my "Settings" "Model Number" and I need to restore back to stock. I'll list everything that is wrong, I need help with, and more settings on my device. MAINLY, IF ANYBODY CAN AT LEAST HELP ME TO FIND MY CID AS SOON AS POSSIBLE, THAT'S ALL I NEED AS FAR AS I KNOW RIGHT NOW.
My Device Settings:
1. Android Version: 4.1.1
2. I did successfully flash to "MIUI-3.8.9" using "Hasoon2000's HTC One X (Evita) All-In-One Toolkit" for most of this.
3. HBOOT/Bootloader:
*** TAMPERED ***
***RELOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
4. RECOVERY:
ClockworkMod Recovery v6.0.3.1
Notes:
1. I looked at the video on youtube, "TUTORIAL: HTC One X stock ROM update: 4.1.1 to 4.2.2 (via CWM)" using CWM (same version) but kept getting status error 0 no matter whether odexed or deodexed.
2. I tried using fastboot options I saw on other posts on this website to find your stock CID, but it still showed 11111111.
3. I used "Hasoons200's Toolkit" to SuperCID to 11111111.
4. "Xfactor" on the toolkit to exploit the device's CID.
Help With:
1. To at least get/find out a way to find out my TRUE STOCK CID as quick as possible.
2. To find the RUU used for this device.
I truly thank all of you for your help!
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
timmaaa said:
If your phone is an at&t model the original CID is CWS__001. Your CID doesn't actually matter anyway because you're s-off, you can run any Evita RUU without any problems regardless of your CID. The reason fastboot commands were showing your CID as 11111111 is because your CID is 11111111, that's because SuperCID overwrites the original CID.
There's nothing at all "wrong" with your device. I think you're extremely confused. I'm not sure why you've been trying all those toolkits, those give you SuperCID, they don't reverse it. You seem to lack a basic understanding of this device, modifying it, and what you can and can't do with it. Why exactly do you want to return to stock? I can tell you exactly how to do it but I'd like to know why first.
Sent from my Evita
Click to expand...
Click to collapse
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
exad said:
Eh.. You have an evita, not endeavor. If you flash endeavor stuff you will likely brick.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Antm50jr said:
Yeah I do have AT&T. Also, yes, I'm pretty new at rooting and such, but I am still learning
I forgot to add this in the post, will edit it in, that I am using "MIUI" like said, and I decided I wanted to get another rom. I tried to get "Paranoid Android", latest version, boot-loader both unlocked and locked, and TWRP and CWM recovery. It came up with status 0 (having to do with the update-binary) but luckily I made a nandroid backup. The device is still working from the nandroid backup, but I will probably use the CID (CWS__001) to get the stock RUU endeavor, then flash.
Click to expand...
Click to collapse
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
Antm50jr said:
Ok. IS there anyway to know which RUU I would need to get stock without CID? If you need any information to help me with this (such as rom version I'm currently using and such) I'll let you know.
Click to expand...
Click to collapse
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
timmaaa said:
The installer for Paranoid Android probably failed because the ROM wasn't meant for this phone, you got lucky it didn't brick you. You have the Evita, not the Endeavoru, I'm not sure where you're downloading your ROMs from but it's the wrong place. Only ever download ROMs from within this device forum you're posting in now, NEVER anywhere else.
Sent from my Evita
---------- Post added at 04:40 AM ---------- Previous post was at 04:37 AM ----------
You have s-off so you can run any Evita RUU that you want, your CID doesn't matter when you have s-off. Go to androidruu.com and get one from there, just make sure it's from the Evita section. I still have no idea why you want to RUU though, you said you just want to change ROMs, an RUU will return your phone to being completely stock.
Sent from my Evita
Click to expand...
Click to collapse
I can't believe this! It turns out, it's bricked I think! I tried to restore from a nandroid backup I got off the internet, not sure whether it was evita or not, WAS ON THIS WEBSITE (XDA), and not it won't boot. The screen is on, but it shows the white screen HTC logo with red letters under it, and made a low buh-buh sound when in USB. I cant find a way to enter boot-loader or recovery (computer cant detect it) but it does show the solid red light at the top. Please, even if it involves downloading a ton of computer applications, I'm willing to.
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
timmaaa said:
I can believe it. Why the hell did you restore a nandroid if you're not even sure if it was for Evita? Have you not listened to a word we've been saying to you? I'm not sure why I bothered trying to help you if you're ignoring the advice I'm giving. Your phone isn't bricked, if it turns on it isn't bricked. Do some research and figure out how to recover.
Sent from my Evita
Click to expand...
Click to collapse
I just wanted to say that I am sorry, and I did fix the problem. Thank you for your support! You are right: I should have listened and pay more attention. Thank you though! I'll always check to see whether a rom is Evita or Endeavor.
My wife's phone, it's currently running CleanROM JL beta 1, android 4.1. it's been running this for over a year. time to upgrade it. i haven't kept up with development on this phone and now i'm totally lost.
bootloader says:
tampered
unlocked
Evita PVT SHIP S_ON RL
hboot 1.14.0002
radio: 0. 19as. 32.09. 11_2
eMMC-boot
...etc.
recovery is TWRP v2.4.1.0
i have no idea where to go from here. can i just drop a new rom on the sd card and flash it from recovery? don't have any software, adb etc and my only computers are macs. would love some advice or at least get pointed in the right direction. tried searching, but i'm just overwhelmed.
i would love to get as close to vanilla android as possible. thanks in advance for the help!
You can't do anything without first updating your firmware. For that you're gonna need access to a PC with an adb/fastboot environment on it. You need to get s-off, then update your firmware, then flash the latest TWRP recovery, then you will be able to update the ROM.
Sent from my Evita
timmaaa said:
You can't do anything without first updating your firmware. For that you're gonna need access to a PC with an adb/fastboot environment on it. You need to get s-off, then update your firmware, then flash the latest TWRP recovery, then you will be able to update the ROM.
Sent from my Evita
Click to expand...
Click to collapse
crap. ok, thanks for the rundown. now that i know the steps necessary, i'm sure i can work my way through it. i'll get working on this.
cwininger said:
crap. ok, thanks for the rundown. now that i know the steps necessary, i'm sure i can work my way through it. i'll get working on this.
Click to expand...
Click to collapse
were you successful? let us know. [emoji62]
Sent from my Inspire 4G using Tapatalk
marknoll said:
were you successful? let us know. [emoji62]
Sent from my Inspire 4G using Tapatalk
Click to expand...
Click to collapse
well, i appear to be stuck. i'm trying to get s-off with firewater. i've got adb running nicely on my macbook,terminal/shell works etc. but firewater fails every time. i get this message:
The first bottle is open
chugging..........
nasty, need a chaser
nasty, need a chaser
this skunk has some real funk, force (FORCE!!!!) reboot your device and try again!
tried 4 times and got the same result. any ideas? am i missing something?
Forget Firewater, try Rumrunner instead:
Rumrunner S-off
Sent from my Evita
timmaaa said:
Forget Firewater, try Rumrunner instead:
Rumrunner S-off
Sent from my Evita
Click to expand...
Click to collapse
no worky on macbook
Can't you get access to a Windows PC? Pretty much everything you need to do with Android is Windows.
Sent from my Evita
timmaaa said:
Can't you get access to a Windows PC? Pretty much everything you need to do with Android is Windows.
Sent from my Evita
Click to expand...
Click to collapse
yeah i guess. pita though. not sure it's worth it for this aging device. i was hoping to get vanilla 4.4 on it and give it to my father in law, but i don't know how much more i want to jerk with it...
thanks very much for the help, though.
It's not hard do. Tim can help. Just LISTEN to him. He knows his stuff.. This device is his specialty
?
cwininger said:
yeah i guess. pita though. not sure it's worth it for this aging device. i was hoping to get vanilla 4.4 on it and give it to my father in law, but i don't know how much more i want to jerk with it...
thanks very much for the help, though.
Click to expand...
Click to collapse
It's pretty straight forward, just sort out drivers, get s-off, flash firmware, and you're golden.
marknoll said:
It's not hard do. Tim can help. Just LISTEN to him. He knows his stuff.. This device is his specialty
?
Click to expand...
Click to collapse
Not for long. Looks like my emmc is starting to fail in my Evita, luckily I've just bought a OnePlus One, it's gonna take a couple of weeks to arrive though. I'll still support this device though probably.
Sent from my Evita
when you say "flash firmware" is that an ruu? it's been awhile and i'm not sure on the terminology anymore. i've flashed samsungs, htc's motorolas and nexus devices and they all have different approaches. i can't keep them straight
cwininger said:
when you say "flash firmware" is that an ruu? it's been awhile and i'm not sure on the terminology anymore. i've flashed samsungs, htc's motorolas and nexus devices and they all have different approaches. i can't keep them straight
Click to expand...
Click to collapse
No, not an RUU, go to my How-To guide in my signature for details.
Sent from a crappy Samsung because my Evita died
I'll quickly explain the flashing firmware. Firmware is basically the stuff like boot loader and radio. You need the entire firmware package updated.
So to do that, we have to get your phone into that mode that's like when you're taking a RUU. It's the black screen with a green progress bar. From there, we use an unusual command to install the firmware.
Just read the "How to Update Firmware" in my Sig and apply that method to any firmware package, as long as you're s-off and supercid
pandasa123 said:
I'll quickly explain the flashing firmware. Firmware is basically the stuff like boot loader and radio. You need the entire firmware package updated.
So to do that, we have to get your phone into that mode that's like when you're taking a RUU. It's the black screen with a green progress bar. From there, we use an unusual command to install the firmware.
Just read the "How to Update Firmware" in my Sig and apply that method to any firmware package, as long as you're s-off and supercid
Click to expand...
Click to collapse
timmaaa said:
No, not an RUU, go to my How-To guide in my signature for details.
Sent from a crappy Samsung because my Evita died
Click to expand...
Click to collapse
beautiful. Thank you guys very much!