[Q] Is my HOX fully bricked? - AT&T, Rogers HTC One X, Telstra One XL

Hello. I'm a new user to these forums and right now desperate for some help.
So I rooted my HOX a couple of hours ago. I installed TWRP 2.2.2.0 recovery and then flashed the [RD-MIUI Jelly Bean] 2.9.28 ROM. It didn't quite meet my expectations so I tried to flash another ROM. Before flashing the second ROM I went into TWRP Recovery and did a backup. After wiping cache/dalvik cache I flashed the second ROM (Viper 2.6.0). This time the phone got stuck on the HTC logo. I went back into recovery and restored from the backup. However, now the phone gets past the HTC logo then... blackness. The phone is completely black. The LED for charging still comes up. The worst part is, I can't get into bootloader. Holding down the volume and power method doesn't get me back into the bootloader.
Is my HOX really bricked? If so, how do I fix it? Do I need to get it replaced or repaired?

Viper is on 1.2.4. I think you flashed a ROM for the international (Tegra3) version, and it might have overwrote recovery (the partitioning is different between the phones).
Try to re-install TWRP over adb. Or relock the bootloader and run the RUU.
If you are still getting the HTC logo boot screen, and have a charging light, I think you can recover.

redpoint73 said:
I think you flashed a ROM for the international (Tegra3) version
Click to expand...
Click to collapse
Oh man, I hope your device is recoverable! If you're able to reinstall TWRP and bring your device back to life, make sure to stick in the "AT&T, Rogers HTC One X, Telstra One XL" forums when you're looking for ROMs. The "other" HTC One X forum is for the international One X, which is completely incompatible with ours.
Actually, you should figure out which device you have first If you can get into the bootloader, look on the screen for the term "evita" or "endeavoru"... if you see "evita" then you have the North American One X, and you want to be in this forum; however, if you see "endeavoru" then you have the International One X, and want to be in the "other" One X forum.

Related

[Q] Thing I must know before I purchase a HOX

So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
sunny342 said:
So Guys black friday is around the corner and I plan to upgrade from my dated HTC Aria. I'm obviously looking at the HOX and the S3 and just by personal preference am leaning towards the HOX (ATT version). However what is really worrying me is that the HOX seems to be locked down quite a bit. I'm not a dev or anything I just want to be able to flash custom rom and experience senseless android in jellybean. So I have some questions...
1) If I buy a HOX with the 2.02 version what are my options rooting wise or am I just screwed?
2) I'm coming from a rooted Aria where rom flashing was easy with clockworkmod recovery. I been lurking this forum and it seems like a painful process now and what is this boot.img thing.
3) Also if anyone isn't to annoyed by my lack of knowledge could you explain what the "S-ON/S-OFF" is as well as the limitation with the fact that HTC locked the boot loader?
I like the HOX but am getting scared away by the fact that this phone is so locked up.
Click to expand...
Click to collapse
First off, when you get it rooted... DONT FLASH ICJ.
Second, when you get it downgrade you hboot via the JET tool or manually through the WIP Unbrick evita thread by Absolutelygrim. Then in the JET tool thread, you'll find a way to RUU down grade. Choose 1.85 Then you won't have to worry about flashing the boot.img in fastboot. All that is, is a way to bypass AT&T's safe gaurd programming. They tried to make it so the boot.img couldn't be formed in recovery. That's only with the 2.20 firmware though.
Third, IDK. I'm still learning why S-OFF is like gold. Someone else might be able to answer that one but, not me.
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
p3terr said:
Hello guys, i am also thinking about getting this phone, but i've been searching this forum and it seems that flashing ROMs is a bit complicated, and i'm not sure..
What are the pros and cons of unlocking the bootloader? could i brick the phone by doing that?
Is there a guide for noobies like me, a tutorial or something? sorry.. i'm new to this.. :fingers-crossed:
Click to expand...
Click to collapse
Would you be getting the AT&T version, or another variant?
Setting the phone up for flashing ROMs is a bit more complicated than some other manufacturers. But this is just how it is for HTC, they have an increasing degree of security on their phones.
You have to unlock the bootloader, which really isn't all that hard. Then install custom recovery and you can flash ROMs. The AT&T version has the extra steps of temp root, SuperCID before you can unlock the bootloader.
Once the phone is setup, flashing ROMs is just like any other phone. With the exception of having to extract boot.img from the ROM zip and flashing via fastboot. But I believe this only applies to the AT&T version with the 1.14 hboot. Even so, you can downgrade the hboot, so you don't have to do the extra step of manually flashing boot.img.
Bricking the phone while unlocking the bootloader is unlikely. But its always a possibility with any mods. Unlocking the bootloader wipes the phone (not really an issue if you are doing it right away after buying) and you also have to confirm that you understand that unlocking the bootloader may void your warranty. Other than that, there is no real "con" to it.
I just finished unlocking bootloader, rooting, installing venom Rom and putting beastmode custom kernel on my [email protected] hox. It's easy now even with 2.2. Just download the all in one tool kit found in the stickied thread for the hox. Does almost all work for you.
Flashing Rom there after word was very similar to cwm was. Loaded it on my internal storage and flashed via recovery
Sent from my HTC One XL using xda app-developers app
redpoint73 said:
1) 2.20 firmware is fully rootable, and has been for a few weeks now. Worries about there not being a root method for 2.20 are outdated, and no longer apply.
2) First off, CWM is not recommended for this device. It never officially supported the Snapdragon S4 variant, and was just a port, with serious known issues. A different custom recovery, TWRP is recommended, and works great.
With the 1.14 hboot that comes with the 2.20 firmware, the hole by which boot.img was flashed via recovery was plugged. So whenever you flash a new ROM, you need to extract boot.img from the ROM zip, and flash it separately via fastboot (phone connected to your PC). Or as previously mentioned, you can downgrade the hboot to eliminate this step.
Aside from that, flashing ROMs on TWRP is just as easy as CWM on your Aria (once you have bootloader unlocked and TWRP installed).
3) S-Off means all security off. It hasn't yet been achieved yet on this device. But with an unlocked bootloader, you can flash ROMs and other mods. With a downgraded hboot, you can flash radios. So there isn't much that S-Off would give you, that isn't already possible. Being able to get SIM unlock for free might be possible with S-Off, as well as turning off the warning flag that the bootloader was unlocked. But for the most part, that is really it. For most uses, S-Off simply is not needed. S-On and bootloader unlock fulfills most needs.
All that said, are you aware the One X+ is being released by AT&T tomorrow? It features a slightly faster CPU/GPU and much more internal storage. Unless you are on a budget, that is probably the phone I would go for at this point. But I think it also remains to be seen about root and bootloader unlock for the One X+.
Click to expand...
Click to collapse
I am aware of the One X+ but I am on a budget and the slight performance boost to me doesn't justify the price. Radio shack will have the HOX for free on blackfriday. Also thanks for the answers to the questions your comment cleared up alot for me.
ECEXCURSION said:
Another aria convert, yay. As stated above, you shouldn't have any concerns about this device. TWRP is actually much easier to use than CWM. The flashing boot.IMG separately is something you won't need to do once you downgrade the firmware.
And as said above, I'd just get a one x+ if I had the money. We only get 9.93GB of SD storage space on this phone.
Sent from my HTC One XL
Click to expand...
Click to collapse
ARIA FTW lol. I need the upgrade to the HOX. Only 9.9GB sucks pretty bad but I can make it work. If only I too had the money for the one X+
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
If you follow instructions properly and read up on everything necessary, unlocking, rooting, and flashing the HOX is a breeze; 2.20 only introduces one additional, straightforward step.
exygenysys said:
You don't need to wait for black friday to get the HOX for free. It's currently free on ATT on Amazon Wireless, and has been for a couple weeks.
Click to expand...
Click to collapse
Im eligible for a qualified upgrade on my family plan so I can't take advantage of the new contract deal.

[Q] HTC One SV boot.img

Hello All
So thinking I was being smart I decided to try and install cyanogenmod on my what I then thought was a HTC One S (I had my One X replaced via insurance and they told me I was getting a One S) After much hassle and HTCDev Unlocking the phone, flashing the recovery and the boot.img I find that it wont boot and is stuck in a bootloop. After reading the fine print under the battery I find that I instead got a One SV which is I'm assuming why its not working.
Also in my smartness I didnt take backups of anything.
So does anyone have or is able to get a HTC One SV recovery or boot.img so that I can use my phone again? You will get all the karma points in the world if you can help me out!
wierdthing said:
Hello All
So thinking I was being smart I decided to try and install cyanogenmod on my what I then thought was a HTC One S (I had my One X replaced via insurance and they told me I was getting a One S) After much hassle and HTCDev Unlocking the phone, flashing the recovery and the boot.img I find that it wont boot and is stuck in a bootloop. After reading the fine print under the battery I find that I instead got a One SV which is I'm assuming why its not working.
Also in my smartness I didnt take backups of anything.
So does anyone have or is able to get a HTC One SV recovery or boot.img so that I can use my phone again? You will get all the karma points in the world if you can help me out!
Click to expand...
Click to collapse
Got exactly the same problem, hope someone can help us !
Hi.
You'll find what you need here.
Helpt i nedd boot
HTC One SV recovery and boot.img please help i need:good:
Hi.
You'll find the JB ones in the OTA.zip linked in this post.

[Q] Why is my HTC One x (PROTOTYPE) stuck on ICS?

Why is my HTC One x (PROTOTYPE) stuck on ICS?
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Rad io_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radi o_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just check the attachments. It has all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and Thank you for it, I hope you can help me!
Sorry to say it after you've written such a lengthy post, but you're in the wrong forum. This is the HTC One XL (at&t One x) forum, they're completely different phones. You'll need to ask in the HTC One X forum, we don't know enough about your phone here, sorry.
Sent from my Evita
Oh sorry about that :/
timmaaa said:
Sorry to say it after you've written such a lengthy post, but you're in the wrong forum. This is the HTC One XL (at&t One x) forum, they're completely different phones. You'll need to ask in the HTC One X forum, we don't know enough about your phone here, sorry.
Sent from my Evita
Click to expand...
Click to collapse
Sorry about that I didn't notice that I posted in the wrong forum. Thank you for letting me know, I will repost this in the correct forum
No worries.
Sent from my Evita

Custom ROMs Boot to White Screen With HTC Logo

Hello all! This is my first post on XDA, so hopefully I don't screw anything up
Anywho, I have a rooted Verizon HTC One (M8) that I was running CyanogenMod on up until recently when I wanted to switch back to a ROM based on HTC Sense. I ended up finding the Android Revolution HD mod for the M8 and decided to give it a try. I flashed my firmware to 3.28.401.7 as that was the one listed on the post, and installed it using TWRP. The device booted, I left it alone, but for some reason it would show a lock screen (that would only let me swipe up) and after I would unlock it all that would be shown was the HTC logo over a white background, with the home and back buttons lit up. Thinking that maybe I goofed, I kept trying again. Eventually I gave up on Android Revolution and decided to try the ViperOne mod, and it ended up doing the same exact thing. Does anyone have any ideas? Thanks for your time, and any help is greatly appreciated!
Regards,
Nate
NathanialTheGreat said:
Hello all! This is my first post on XDA, so hopefully I don't screw anything up
Anywho, I have a rooted Verizon HTC One (M8) that I was running CyanogenMod on up until recently when I wanted to switch back to a ROM based on HTC Sense. I ended up finding the Android Revolution HD mod for the M8 and decided to give it a try. I flashed my firmware to 3.28.401.7 as that was the one listed on the post, and installed it using TWRP. The device booted, I left it alone, but for some reason it would show a lock screen (that would only let me swipe up) and after I would unlock it all that would be shown was the HTC logo over a white background, with the home and back buttons lit up. Thinking that maybe I goofed, I kept trying again. Eventually I gave up on Android Revolution and decided to try the ViperOne mod, and it ended up doing the same exact thing. Does anyone have any ideas? Thanks for your time, and any help is greatly appreciated!
Regards,
Nate
Click to expand...
Click to collapse
X.X.401.X firmware is for Europe. UK variants. You should not be flashing firmware to your vzw one like that. Flash back to stock vzw firmware.
dottat said:
X.X.401.X firmware is for Europe. UK variants. You should not be flashing firmware to your vzw one like that. Flash back to stock vzw firmware.
Click to expand...
Click to collapse
Ahhh okay, thanks! So, how limited do the options for flashing ROMs become for the One? Also, once I revert back to stock firmware, will I be able to retry one of the ROMs that I tried previously, or will the stock vzw firmware not be compliant? I apologize for any super nooby questions, this is my first system dealing with root stuff (as I had an iPhone previously so I used jailbreak items)
NathanialTheGreat said:
Ahhh okay, thanks! So, how limited do the options for flashing ROMs become for the One? Also, once I revert back to stock firmware, will I be able to retry one of the ROMs that I tried previously, or will the stock vzw firmware not be compliant? I apologize for any super nooby questions, this is my first system dealing with root stuff (as I had an iPhone previously so I used jailbreak items)
Click to expand...
Click to collapse
Just stick to the roms from the M8 VZW Development forum and you'll be fine. Viper is there, NuSense, CleanROM and many more...

[Q] How to get back my Htc one S after soft-brick JB-4.1

Hello my phone is htc one s3
Unlocked
villec2 s-on
hboot 3.00.000
radio 16.15.20.24_m
Hello everyone again, i'm new in this world but there's ma problem. I'm 19y Angolan dude, i bought a htc with vodafone carrier, at 8th November i decide to root my htc one S after unlock boot (with all sucess) then i tried to install cm11 4.4.4 kitkat, i wipe all thing but comes error so i had deleted os of my fone, and i didin't made a nandroid backup, now i stuck in HTC logo with the red advise and i just can go to recovery twrp 2.2.1 and now my battery died when i'm trying to charge up only comes black screen, I get some look insisted he power up but for a short time, i don't know what to do, i have read a lot of guides but I'm insure because i can't find a nandroid and a stock Rom for my htc, please can somebody here help me?
You have to install a new recovery from fastboot

Categories

Resources