Help Soft Bricked!

[ootnaboot]

Hey Everyone!

I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.

So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..

I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?

I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone

Thanks in advance.

 

[Brian706]

Not sure exactly what went wrong. Seemed everything was going fine and simple as it should be

Here is a link to what I believe is the correct ruu for your phone: http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html

Please make sure that's the one you want since I'm not 100% positive but it seems to be correct.

If the ruu gets you up and running i would try one more time. Maybe re download the files in case something got corrupted and try again. You can use the unlock token you already have though.

 

[scotty85]

some info about your phone may help us,as im not 100% sure if you have one x or one xl...
if you can put the phone into fastboot,and enter:

fastboot getvar all

in a cmd window,then paste the output here,that will tell us alot about your phone,and what ruu you may need.

 

[Brian706]

some info about your phone may help us,as im not 100% sure if you have one x or one xl...

This part confused me... Even our forum section is called one x/xl. Searching around online a little made it sound like both were code named evita. I was thinking possibly they use the same ruu? Not sure if that's possible though. What exactly is the difference between the x and xl? Just specs?

 

[scotty85]

This part confused me... Even our forum section is called one x/xl. Searching around online a little made it sound like both were code named evita. I was thinking possibly they use the same ruu? Not sure if that's possible though. What exactly is the difference between the x and xl? Just specs?

one X is endeavor_u,and is the tegra 3 processor version.

one XL is evita,and is the dual core s4 version.

endeavor_u is used internationally. evita is used internationally to a lesser extent,most common carrier here in the forums is the ATT version.

all evita roms/ruus are compatible,much like all gsm evo 3d roms/ruus.(ie. you can flash any carrier ruu or rom on any other evita)

evita and endeavor_u are definately NOT compatible! an s on and carrier or htc branded device wont let you flash the wrong RUU,but an s-off super CID device will,leaving you with a nice hard brick

even worse with s on devices,custom roms that arent doing any sort of model check will flash on either phone,and one x roms will brick a one xl,due to a completely different partition lay out(one x rom flashes the boot image to a non-write protected critical partition-exactly wich one,i cant remember at the moment)

all this is the reason we have tegra 3 and s4 specific ATR subforums

edit: it bugged me i couldnt remember what the simple flash of an endeavor_u rom on an evita handset would trash,so i dug it up

the endeavor_u rom flash basically overwrites evita mmcblk0p4, mmcblk0p5*, mmcblk0p6*, mccblk0p7* and then attempts to write mmcblk0p12. p12 is hboot on evita,and thus write protected.

on evita,boot needs to go to mmcblk0p22,and system to p29