Related
I'm not sure how to get back to stock as I purchased my phone off craigslist and it has CM10 on it with a custom recovery (TWRP or something I believe). I would like to get back to completely stock as if I purchased the phone brand new from AT&T. I searched through the forums and found stock RUU's but I'm not sure which one to use or how to flash it.
I would appreciate any help at all. Thank you.
Give it time and your question will be answer in here
Sent from my HTC One X using xda premium
---------- Post added at 07:46 PM ---------- Previous post was at 07:41 PM ----------
Also this need to be posted in the question section to be answer.
Sent from my HTC One X using xda premium
Check your hboot version ...if 1.14 relock bootloader then run the 2.20 ruu...if your on 1.09 or 1.11 I guess if you wanna go back to stock and have no desire of rooting then just relock and run the 2.20 ruu
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Mrkrackie said:
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Click to expand...
Click to collapse
Selling it, buying nexus 4
brian85 said:
Selling it, buying nexus 4
Click to expand...
Click to collapse
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Mrkrackie said:
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
i wouldnt change cid back. id just ruu then give the guy your selling it to the unlock token incase the buyer wants to mod it. save the person some time. if you want to just run the 1.85 ruu you can still get it from htc http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe
absolutelygrim said:
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Which is still not true stock. You cannot get the boot loader back to factory locked. The warranty is gone and cannot be recovered so these steps that are being taken are useless and make extra hurdles for the buyer if they plan to root. I'd recommend just selling it with a stock ROM on it with the boot loader left unlocked.
Sent from my HTC One XL using xda app-developers app
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Nice Grammar, wrong section all together.
http://forum.xda-developers.com/forumdisplay.php?f=1013
Is stock recovery required before flashing a RUU?
no, all you need to do is get into bootloader and "fastboot oem lock" then flash ruu.
mbh87 said:
Is stock recovery required before flashing a RUU?
Click to expand...
Click to collapse
i suppose you have twrp recovery right?
if you have, then just flash device with cleanrom. or stock.
i personally prefer cleanrom, cause its deoxed.
cleanrom is odexed
Cant get to regular OS. Screen says tampered on hboot. On twrp I installed a zip but still cant run an OS. I'm lost can't figure this thing out. i'm a first timer
If you have hboot 1.14 you need to manually flash boot.img in fastboot using "fastboot flash boot boot.img"
http://forum.xda-developers.com/showthread.php?t=2136172
How to fix and for future fixes
jvele16 said:
Cant get to regular OS. Screen says tampered on hboot. On twrp I installed a zip but still cant run an OS. I'm lost can't figure this thing out. i'm a first timer
Click to expand...
Click to collapse
Ok dude here's what you are going to do.
1. go into the bootloader.
2. read the hboot number if it is 1.14 or higher then get cleanrom 5.1 from scottsroms.com make sure u get the one for the htc one x and it is in archived builds GET 5.1 only 5.1 otherwise still for any other number follow the link, this is just to help you in future installations.
3. download cleanrom 5.1
4. get into twrp while in fastboot/bootloader by hitting bootloader with power key and volume down to recovery which you will click with the power button.
5. plug phone into computer and tap the big 5 sided rectangle like shape that says mount and in there hit mount usb storage or something like that.
6. drag cleanrom 5.1 to the downloads folder or where ever you keep your roms.
7. x out of the file explorer than hit unmount in the phone. Unplug the phone.
8. hit the back arrow in TWRP and go to the wipe menu. Hit factory reset, wipe cache and dalvik cache. If you want to be safe wipe system.(do this for all future rom installations.)
9. go to the install after getting out of the wipe menu.
10. tap clean rom and install the settings you want (make sure you hit the i never took the 2.20 firmware update/unsure option).
11. reboot system
12. wait up to 10 minutes if it doesn't work ruu use instructions on onexroot.com under unroot and then go to unbrick at&t one x
13. for future rom installations if you have hboot 1.14 or higher extract the boot.img and either booting in the bootloader and going to the fastboot menu and putting in the command fastboot flash boot boot.img or as do what i do which is to use the TN win installer to flash them for me in the bootloader.
IF YOU RUUED THEN YOU WILL NEED TO DO STEP 13 To INSTALL CUSTOM ROMS
Say something if this fails or you don't understand.
sorry there's no links xda doesn't let me post links.
boss1019 said:
Ok dude here's what you are going to do.
1. go into the bootloader.
2. read the hboot number if it is 1.14 or higher then get cleanrom 5.1 from scottsroms.com make sure u get the one for the htc one x and it is in archived builds GET 5.1 only 5.1 otherwise still for any other number follow the link, this is just to help you in future installations.
Click to expand...
Click to collapse
This is the HTC ONE XL EVITA. You're gonna brick someone with instructions like this. If this guy who clearly has no idea what he's doing flashes an htc one x rom, he's got an irrecoverable brick.
Since you are a first timer, the best way for these guys to help you is to give them as much information as you can. Don't go flashing anything until you and they understand what it is going on.
Sent from my One X using xda premium
boss1019 said:
Ok dude here's what you are going to do... blah blah blah
Click to expand...
Click to collapse
Boss you need to leave the "advice/instruction giving" to people who actually know what they're talking about man.
Sent from my One XL using XDA Premium
cleanrom 5.1 is for at&t one x /one xl
exad said:
This is the HTC ONE XL EVITA. You're gonna brick someone with instructions like this. If this guy who clearly has no idea what he's doing flashes an htc one x rom, he's got an irrecoverable brick.
Click to expand...
Click to collapse
dude i have a one xl i flash one xl kernels, roms etc. i just gave instructions on how i get out of of the same situation.
---------- Post added at 01:01 AM ---------- Previous post was at 12:56 AM ----------
exad said:
This is the HTC ONE XL EVITA. You're gonna brick someone with instructions like this. If this guy who clearly has no idea what he's doing flashes an htc one x rom, he's got an irrecoverable brick.
Click to expand...
Click to collapse
dude i have a one xl i flash one xl kernels, roms etc. i just gave instructions on how i get out of of the same situation. I would not be dumb enough to flash a international one x rom on an xl. The only reason I don't give links is because xda doesn't let me. Cleanrom 5.1 has feature for those who bricked and had to ruu or took the ota to 2.20 with hboot 1.14 where you don't have to write the boot.img first.
boss1019 said:
dude i have a one xl i flash one xl kernels, roms etc. i just gave instructions on how i get out of of the same situation.
Click to expand...
Click to collapse
Good then since you're so capable, you know that when it comes to the one xl and stituations like this, it's best to get all the details hboot, SiperCID, S-ON or S-OFF and what the person did when the brick occured. To just go off spouting unspecific, unteaching instructions like that you're causing more bad than good. Thank you though.
Can I get an AMEN!
Sent from my One X using xda premium
exad said:
Good then since you're so capable, you know that when it comes to the one xl and stituations like this, it's best to get all the details hboot, SiperCID, S-ON or S-OFF and what the person did when the brick occured. To just go off spouting unspecific, unteaching instructions like that you're causing more bad than good. Thank you though.
Click to expand...
Click to collapse
I completely agree which is why i gave instructions geared towards someone like this guy who won't give us any thing. The instructions are designed for any hboot and SuperCID. Which btw this guy seriously needs to give us more info.
Venomtester said:
Can I get an AMEN!
Sent from my One X using xda premium
Click to expand...
Click to collapse
AMEN!!
Sent from my One XL using XDA Premium
really
timmaaa said:
Boss you need to leave the "advice/instruction giving" to people who actually know what they're talking about man.
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
no offense the best advice giving i've seen so far is dude you need to do fastboot flash boot boot.img to a guy who probably doesn't as far as I can tell is very new to this kind of thing (roms, kernels, s-off etc. )
---------- Post added at 01:29 AM ---------- Previous post was at 01:23 AM ----------
jvele16 said:
Cant get to regular OS. Screen says tampered on hboot. On twrp I installed a zip but still cant run an OS. I'm lost can't figure this thing out. i'm a first timer
Click to expand...
Click to collapse
dude back and forths aside, you're going to need to give as much info. What hboot are you on. what twrp do you have. what did you try to install. what rom are you on. what did you do to install zip (what did you wipe). finally are you s-off (if you don't know what it is you're probably s-on)
---------- Post added at 01:50 AM ---------- Previous post was at 01:29 AM ----------
jvele16 said:
Cant get to regular OS. Screen says tampered on hboot. On twrp I installed a zip but still cant run an OS. I'm lost can't figure this thing out. i'm a first timer
Click to expand...
Click to collapse
give us a blow by blow what happens when you boot. Example: Phone vibrates and goes to white htc screen with read text, then goes to the boot animation for cyanogenmod and doesn't stop the animation unless it is forcebly shut down
Venomtester said:
Can I get an AMEN!
Sent from my One X using xda premium
Click to expand...
Click to collapse
Amen +2
Sent from my HTC One XL using xda app-developers app
exad said:
This is the HTC ONE XL EVITA. You're gonna brick someone with instructions like this. If this guy who clearly has no idea what he's doing flashes an htc one x rom, he's got an irrecoverable brick.
Click to expand...
Click to collapse
I just like to add, before I knew the difference between Evita and endeavor, I flashed cm 10 with the endeavor, and had no problems booting. But then I got decided to switch, and actually found out what the code names represent.
Sent from my Carbon-ize Evita using xda-developers app
Venomtester said:
Can I get an AMEN!
Sent from my One X using xda premium
Click to expand...
Click to collapse
AMEN!!!
Help
Bootloader says **tampered** and **unlocked**, and I have hboot version 1.14.002. Flashed TWRP. Wiped, so now I don't have my stock OS anymore. Tried to flash Cleanrom 6.5 and selected options, but the install always ends in a second and fails. The reboot screen warns me that I don't have an OS installed and when I do, it tells me that it's a developer build/etc. Help, it's my first time doing this.
Edit: Never mind, used an older version of TWRP, worked.
I have a black HTC screen with a ! triangle in each corner. Tried to ruu and it failed and I have no clue what to do now. I've never seen this before so I'm lost. . .
I was running carbon rom and was having some bad random reboot problems. I wiped and tried to flash venom and it kept rebooting. So I locked it and tried to ruu, and it failed horribly.
I should also add that I am soff.
Have you tried to get back into boot loader manually? Press and hold volume down and power at the same time. When lights stop flashing, release power while continuing to hold volume down until you enter boot loader.
You can try http://forum.xda-developers.com/showthread.php?t=1982442
Sent from my One X using xda premium
---------- Post added at 05:10 AM ---------- Previous post was at 05:03 AM ----------
You have what is called a radio brick. I don't know of any method to fix it unless you can get another ruu to flash or search around for a method to repair it.
Sent from my One X using xda premium
fadetoblack2104 said:
I have a black HTC screen with a ! triangle in each corner. Tried to ruu and it failed and I have no clue what to do now. I've never seen this before so I'm lost. . .
I was running carbon rom and was having some bad random reboot problems. I wiped and tried to flash venom and it kept rebooting. So I locked it and tried to ruu, and it failed horribly.
I should also add that I am soff.
Click to expand...
Click to collapse
First off, you are not bricked in any sense of the word. On this device, if the screen comes on at all, you are not bricked, and you can recover from it. It just takes the proper steps.
RUU should have given an error code (like "ERROR 170"). Telling what code comes up might help.
You might just try to download the RUU again.
Or you can try to re-unlock the bootloader and flash custom recovery via adb. If that works, just load a custom ROM zip (by way of mount USB in recovery) and flash it.
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
Venomtester said:
You have what is called a radio brick.
Click to expand...
Click to collapse
Is that what the HTC screen with the red triangle with exclamation mark in each corner symbolizes? This screen is new to me.
I'm only familiar with the screen that had the big red triangle and exclamation in the middle of the screen, which is stock recovery.
I wish someone would put that you don't need to relock bootloader to RUU if you are S-OFF in the stickies somewhere.
Unfortunately, yes. The triangles in each corner with exclamation points are for radio brick. He damaged the partition in some way. Like you said, he may be able to flash over it but depends on the damage. If not it will be jewel or JTAG time.
Sent from my One X using xda premium
Venomtester said:
Unfortunately, yes. The triangles in each corner with exclamation points are for radio brick. He damaged the partition in some way. Like you said, he may be able to flash over it but depends on the damage. If not it will be jewel or JTAG time.
Click to expand...
Click to collapse
Maybe something went awry while the RUU was trying to write to the radio partition?
He should be able to just reflash a new radio.
I suspect the initial problem was trying to run a Sense rom (Venom) on top of the AOSP kernel from Carbon.
Very possible. Bad ruu or didn't flash properly. Maybe op can let us know how reflashing turns out or if the jewel kit works. And like stated above, sense and aosp radio partitions are different. Being hung up on an asop ROM while flashing a sense ruu can not be good.
Sent from my One X using xda premium
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
I believe so. But if he still has asop boot image it will have to be asop radio. This might help http://forum.xda-developers.com/showthread.php?p=27022095
Sent from my One X using xda premium
Venomtester said:
Very possible. Bad ruu or didn't flash properly. Maybe op can let us know how reflashing turns out or if the jewel kit works. And like stated above, sense and aosp radio partitions are different. Being hung up on an asop ROM while flashing a sense ruu can not be good.
Sent from my One X using xda premium
---------- Post added at 02:02 PM ---------- Previous post was at 01:40 PM ----------
I believe so. But if he still has asop boot image it will have to be asop radio. This might help http://forum.xda-developers.com/showthread.php?p=27022095
Sent from my One X using xda premium
Click to expand...
Click to collapse
AOSP radio is part of the Rom. Sense radio partitions are not even touched by an aosp Rom. You can flash a sense radio while on aosp and have no effect. I don't know if hboot has issues with a borked radio partition though.
I don't know about that. I have never flashed a ruu not compatible with the rom I am using. Hopefully reflashing the radio will fix op's problem.
Sent from my One X using xda premium
That screen from what I can tell is what you get from a bad ruu flash. You need to flash an ruu to completion to fix it.
I left the phone overnight and I guess the battery died. Wont charge when I plug it in. Computer doesn't recognize it either.
What happened was my stupid cat knocked my phone off the computer desk when I was running the ruu and the cable came out. I tried to re run the ruu, but it wouldn't run. Adb commands also did nothing.
Since the phone wont charge and appears to be dead, I ended up using my phone insurance. . . should have a replacement in a few days.
fadetoblack2104 said:
I left the phone overnight and I guess the battery died. Wont charge when I plug it in. Computer doesn't recognize it either.
What happened was my stupid cat knocked my phone off the computer desk when I was running the ruu and the cable came out. I tried to re run the ruu, but it wouldn't run. Adb commands also did nothing.
Since the phone wont charge and appears to be dead, I ended up using my phone insurance. . . should have a replacement in a few days.
Click to expand...
Click to collapse
He was jealous because you spend too much time playing with your phone. I would keep a close eye on that cat for a few days.
S-Off Evita Chameleon OS
Yeah unplugging during ruu is a perfect way to brick. I usually keep my cats out of the room while running an ruu and I ruu often lol. I don't trust twrp.
Sent from my One X using xda app-developers app
exad said:
Yeah unplugging during ruu is a perfect way to brick. I usually keep my cats out of the room while running an ruu and I ruu often lol. I don't trust twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Exad, you named your cat twrp?
S-Off Evita Chameleon OS
Venomtester said:
Exad, you named your cat twrp?
S-Off Evita Chameleon OS
Click to expand...
Click to collapse
lol no, my cats names are Kal-El and Lex lol
twrp is the recovery which I don't trust lol
I think twrp would be a cool name for a cat lol.
Sent from my One X using xda premium
Hello, I recently received an AT&T One X and the very first thing I did with it was try to root it and all that fun stuff. After a long adventure I couldn't get the HBOOT to upgrade so I had changed the CID to HTC__001 from cws_001 (I couldn't find this CID anywhere, but I swear that's what it said) and then the bootloader was re-locked. There is no OS, there is no recovery, I've tried 10 RUU's from Asia WWE to the UK RUU's and than all the AT&T ones I can find.
Most fastboot commands come back with a "Too many Links" error which I assume is from the bootloader being locked, and I cant change the bootloader's status because the bin file I got is for the supercid.
Please help me, I am usually quite proficient with this type of stuff but I really buried myself in a hole.
Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app
exad said:
Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Isn't that cid for the international version?
Sent from my HTC One X using xda app-developers app
Re
My HBOOT is 1.14.0002. I tried to upgrade it for all the newer roms and such but thats when I managed to screw everything up. Yes, it is still HTC__001 and that is the international. I've tried several WWE RUU's and all refuse to work giving me various errors..
Yeah no ruu will work because you have an international cid with an at&t phone.
You'll need to htcdev over again and pray it works.
Sent from my HTC One X using xda app-developers app
I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..
koolgshizman said:
I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..
Click to expand...
Click to collapse
You can only change the cid once with fastboot oem writecid unless you are s-off
As for fastboot not working. Are you able to flash recovery?
Sent from my HTC One X using xda app-developers app
I managed to put on twrp but I didn't make a nandroids
koolgshizman said:
I managed to put on twrp but I didn't make a nandroids
Click to expand...
Click to collapse
Flash a stock-based ICS rom and then S-OFF, then you can change your cid, or whattever you need to do
Doesn't necessarily need to be ics but yeah you get the idea. After s-off then you can ruu to update your hboot and anything else that gets updates. Bear in mind that on aosp ROMs the touchscreen won't work after you upgrade until you downgrade the touchscreen firmware.
Sent from my HTC One X using xda app-developers app
Don't you still need supercid to s-off? Or is that no longer a requirement?
Never tried with am international or cid from another carrier.. Maybe it'll work? If not he can always hex edit his cid.
Sent from my HTC One X using xda app-developers app
Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try
koolgshizman said:
Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try
Click to expand...
Click to collapse
You should be able to flash any rom so long as you fastboot flash the boot.img ics or jb.
A million thanks, well, I thanked you once, that should suffice. I'm almost set now, for a second I thought the phone would be a goner.
If you can get to bootloader your phone can be saved. Good luck, have fun.
Sent from my HTC One X using xda app-developers app
Yes, CM10.1 is now running, I'm just waiting for my gapps.. thanks again
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
bikeracer4487 said:
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
Click to expand...
Click to collapse
You can only S-OFF with super CID 11111111
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so. You can do whatever you like regardless of what your CID is after S-OFF. I set mine to R00T_001 after for example. (must be 8 characters)
Just noticed your other thread and see why you want the default CID. If you're selling it, make sure your cid is currently 11111111 then S-OFF then you can use that command to change the cid to default. If you're going to sell it, after S-OFF, I'd just format the SD card and run the 3.18 RUU and then power it off after so the person you sell it to will have a fresh start.
exad said:
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so.
Click to expand...
Click to collapse
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
redpoint73 said:
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
Click to expand...
Click to collapse
Sorry, the other thread was started because I couldn't turn my phone on, and was becoming unrelated to original post, thought it would be prudent to create a new thread. Really appreciate your help though.
Just a heads up, I bricked my first TELUS HOXL eventhough I had changed my CID back to the default prior to RUUing. May have been a fluke but yeah do with this info what you will.
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
bikeracer4487 said:
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
Click to expand...
Click to collapse
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
exad said:
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
Click to expand...
Click to collapse
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
bikeracer4487 said:
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
Click to expand...
Click to collapse
Yeah that bid brick I believe. Get live USB stick running Linux. All you need is small USB stick like 2 or 4 GB. Then download pen drive USB image creator. And run Linux from that. Then exad mentioned a thread to look into. I recommend an Ubuntu based distro. I use Linux mint
Sent from my Carbon-ize Evita using xda-developers app
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
exad said:
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
bikeracer4487 said:
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
Click to expand...
Click to collapse
Great!! But is it on the new unrootable software?
ImagioX1 said:
Great!! But is it on the new unrootable software?
Click to expand...
Click to collapse
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
bikeracer4487 said:
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
Click to expand...
Click to collapse
LoL!!
Sent from Xparent Red using my Venomized Evita
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
exad said:
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
area51avenger said:
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
Herc08 said:
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
exad said:
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wow. Didn't know that
Sent from my Carbon-ize Evita using xda-developers app
exad said:
They don't warrant lost phones here.
Click to expand...
Click to collapse
They don't cover lost phones on warranty anywhere. He was talking about insurance, not a warranty.