Develop Bugs

Droid Inc Possibly Bricked

Ok i rooted using unrevoked method and it came with the 2.15 radio update.. i attempted to unroot using this guide http://androidcommunity.com/forums/f75/unroot-your-incredible-36262/
and now my phone has a blank screen however when i press power it vibrates and the led is on when charging and when i hold down the trackball and power my computer picks it up as android 1.0... tried a battery pull
is this fixable?
Thanks!
timinator94

timinator94 said:
Ok i rooted using unrevoked method and it came with the 2.15 radio update.. i attempted to unroot using this guide http://androidcommunity.com/forums/f75/unroot-your-incredible-36262/
and now my phone has a blank screen however when i press power it vibrates and the led is on when charging and when i hold down the trackball and power my computer picks it up as android 1.0... tried a battery pull
is this fixable?
Thanks!
timinator94
Click to expand...
Click to collapse
Tried vol down and power? Will boot into bootloader.

Your phone isn't bricked. Its in debug mode. Pull battery and do volume down + power to see if you can get into the bootloader, if you can you aren't bricked, load up an RUU and you should be good.
Sent from God, who uses OMGB-5.

Not sure as i cant see the screen... I press it and it vibrates... did some more digging and found this-http://forum.xda-developers.com/showthread.php?p=8960978&posted=1#post8960978
would this fix it? would it hurt to try?

Did you try a battery pull? Try that and then volume down and power.

timinator94 said:
Not sure as i cant see the screen... I press it and it vibrates... did some more digging and found this-http://forum.xda-developers.com/showthread.php?p=8960978&posted=1#post8960978
would this fix it? would it hurt to try?
Click to expand...
Click to collapse
Yes if you have an SLCD this is your problem. When you downgrade to 2.1 you have no drivers for your screen. Pull the battery, hold down and then hit power. Set your phone down for 10 minutes or until hboot loads. Make sure that you have this PB31IMG.zip in the root of your sd and then upgrade it. It took a while for my hboot to load. So give it some time. If that doesn't work try booting with trackball and power.

How do I know what kind of screen I have?

and where do i get an ruu?

Good luck with this one guys... lol. I commend you!
Sent from my ADR6300 using XDA App

lol sorry im really new to this

timinator94 said:
and where do i get an ruu?
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showthread.php?t=829783
This is the ruu EXE. I dont know quite whether it works for SLCD, but its a resource.

If you recover by loading the PB31IMG in hboot, you'll need to also format your SD card to FAT32 if it isn't already. Might be a slight point of contention if you don't have a USB card reader or another device which can interface the card with a PC.
Might be easiest to run the RUU on a Windows computer. Link above looks perfect, it's the latest.
Download to PC, hook up phone via USB cable and lanuch the RUU program then follow instructs. I despise HTC Sync but in this case, might be easiest to go ahead and load it to your PC before you run the RUU. It'll allow the RUU to function properly (all this all assumes Windows). I'd delete HTC Sync when done if it were me. It can be problematic in other regards.

I am 99% sure that the phone dosent boot past hboot... so the above method wont work correct?

The 2 ways to do it are:
1.) go into hboot and have the PB31IMG already on your SD card. Once in hboot, it should recognize the PB31IMG and you press volume up to load. However, as mentioned it'll likely fail if you have not formatted your card to FAT32 at some point.
2.) Forget about hboot. Pull your batt, replace it and start the phone even though you can't see what's up. You should feel it vibe and in reality it's working, you just can't see anything on the screen due to the lack of drivers as previously mentioned. So hook up phone to USB port on PC and with HTC Sync installed, launch the RUU you downloaded from 3 posts up. It runs on Windows and loads the software to the phone via the USB charging cable.

I have grown tired of these downgrade posts on multiple forums. Instead of writing a "how to" in 50 posts I have made one
You downgraded, welcome to the land of suck.
And OP you phone does boot and works quite well minus the screen. To prove the point boot it up and call it.

OP,
Go with Doug's link. Great description and is using the same files already posted here. Just much better instructs to follow.

Alright thanks trying that now

timinator94 said:
I am 99% sure that the phone dosent boot past hboot... so the above method wont work correct?
Click to expand...
Click to collapse
Follow my earlier post. I posted a link to the zip you need. If you need more help e-mail me at [email protected].

the ruu didnt work error 117... would it help if i uses xp?

Do you have SLCD or Amoled screen? Also, if you used 3.22 you might have to get your own recovery. Download ROM manager from the market and install Clockwork Mod.

I cant believe it!!!

Ok! So i was running fresh 3.5 on my evo 4g and everything was running great. I decided that I wanted to add a battery percent on the battery indicator. I download a zip file that would allow me to do that...I put it on the root of my sd. I tried flashing it with clockwork mod 3.0 but it didnt let me cuz it came up with an error saying to update my binary and script. So i googled on how to bypass that error and it said to use the ra recovery(the other recovery program,i think thats what its called ) so i flashed ra with rom manager. I rebooted my evo and went into recovery and flashed the zip file then a couple of minutes later it said it was complete(no errors came up during the flashing process). I rebooted my evo after the flashing was done. This is where it starts getting weird! I turned my phone back on and after the white screen a black screen came up and didnt go away. After about a minute the phone vibrated about 4 times and the indicator light started flashing green. I couldnt power down so I had to take out the battery. I turned it back on and it booted up to the fresh boot logo. It tried to reboot itself about 3 times and without success the black screen came up and vibrated with flashing green light. Took the battery out for an hour then I booted it to the boot menu, went into recovery to try to delete the zip file and all it did was give me the black screen, vibrated and flashing green lights. I checked to see if s-off was still engaged and it wasnt. S-on was showing. I think some how that zip file made that happen. I have a nandroid backup. I dont have recovery and s-on is engaged. What should I do? This is the file that I flashed( smooth-sense_evo1.0.2_batteryonly ) Sorry if Iam posting this in the wrong section. Any help would be appreciated. Thanks

Holy Wall-O-Text Batman!
But getting to your issue:
You enabled security again. Flash the stock RUU found in the most up-to-date unrooting guides and go back to stock. Re-root again using Unrevoked and then flash again. Mind you, you will be starting over more or less.
The reason why I'm telling you to unroot and then root again is that you want to get rid of that funky flash. Its the safest way possible.

So I need to unroot first (even though it says s-on)
Then root again with unrevoked
Then flash stock ruu

Flashing the RUU should unroot for you. It will undo any mods except for s-off from unrevoked.

Still no luck.
This is what i have done.
Ive tried rooting again using unrevoked 3 but it doesnt pick up my evo when i plug in my phone. It does come up in my device manager but its not assigned a drive letter. Yes i did enable hboot usb. Yes my drivers are installed right.
Ive tried different ruu's but they wont detect my evo. Ive tried different stock PC36IMG's and they will update with no errors but when it reboots into the the screen with green arrows and a phone it vibrates 4 times then turn off.
Can you guys be more specific on the steps that in need to do. Thanks once again.
Info:
HBoot 2.10
Radio 2.15

I feel your pain, same thing happened to me after months of successful evo hackery. Was very difficult to convey to people the extent of random roadblocks preventing all the supposed fixes. I followed every suggestion, maybe 200 separate tries at a workaround, but in the end I had to trade it in for a refurb.

To flying low,
I still have faith especially with everybody helping me out. I know theres a workaround cuz i still have hboot up and running even tho i lost recovery and rom.

Can i use unrevoked when iam in hboot? Cuz thats the only option i have.(i think)

calishooter said:
To flying low,
I still have faith especially with everybody helping me out. I know theres a workaround cuz i still have hboot up and running even tho i lost recovery and rom.
Click to expand...
Click to collapse
you need to flash the RUU in hboot or run the RUU in Windows...it doesnt matter whether it says s-on or not all it will do is restore the phone back to its shipped factory settings and unroot you

What you do:
Find and download the latest RUU. I Think this is it: http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe (download should start automatically)
name it PC36IMG.zip
Place it on the root of your sd card (root of sd card = no in any folders, just put it on there).
Boot into bootloader (power off, hold volume down and turn power on to get there)
it'll ask if you wanna parse update, hit volume up for yes.
basically, this will flash the stock rom back onto your phone. Since you're s-on already, this will complete a full unroot. Then simply re-root your phone like you did the first time and you're back in the game

Ok i will try flashing the ruu from the link that you gave me.
Thanx. Will report back soon.

I tried the link but its a .exe file not a zip. So I converted it to a zip file using winrar. I renamed it PC36IMG and put it on the root of my sd. Ran it and it just got to the checking part and it stoped checking. I did it 2 times with same result.I also formated my sd card to fat32.

calishooter said:
I tried the link but its a .exe file not a zip. So I converted it to a zip file using winrar. I renamed it PC36IMG and put it on the root of my sd. Ran it and it just got to the checking part and it stoped checking. I did it 2 times with same result.I also formated my sd card to fat32.
Click to expand...
Click to collapse
If you want to run the ruu in PC36IMG form, you need the right file.
http://dl.dropbox.com/u/19699565/3.70 RUU Zip.zip < Rename to PC36IMG, then flash in the bootloader.
The ruu.exe is meant to be run from a computer, with the phone booted into the bootloader, and mounted to the pc in fastboot.

Yes i agree tech roxxorz. I was just doing what he told me. Ive tried RUU.exe before but it wont recognize my evo niether does my computer and iam in hboot usb mode. I will try your link and repot back.

calishooter said:
Yes i agree tech roxxorz. I was just doing what he told me. Ive tried RUU.exe before but it wont recognize my evo niether does my computer and iam in hboot usb mode. I will try your link and repot back.
Click to expand...
Click to collapse
Well you can't do it in hboot usb. You have to select fastboot, connect to the pc, and when it shows up as fastboot usb in blue on the phone, then you run the ruu.exe.
Though either method will work.

So when I click on fastboot on my evo, what do i click on next to run RUU.exe cuz I only have reboot or power down options.

calishooter said:
So when I click on fastboot on my evo, what do i click on next to run RUU.exe cuz I only have reboot or power down options.
Click to expand...
Click to collapse
Turn the phone off. While turning the phone off, hold vol+down till you see a white screen with androids skateboarding [bootloader] From there, after it scan, navigate to fastboot with the volume keys, press the power button to select, then connect to the PC via usb cable. When it says 'fastboot usb' in blue, run the ruu exe on the pc.

OK got it. Will report back soon.

Aye aye cappy.

I did what you wrote. The ruu.exe gave me an error 170-usb connection error. I booted into the bootloader by holding down the power button and volume down why the evo is turned off. It scaned the sd card, I selected fastboot and plugged in my usb cable. It said fastboot usb highlighted in red.

EVO 4G stuck at htc 4g splash screen - I searched for 2 days!!!

Hey guy's, well first off I just want to say I'm a big fan of android and especially xda-developers and all the helpful people on this site. I'm having a pretty big issue, one that I searched for a solution for 2 days now using the search function on here as well as google and many others available and I'm in a corner. I have an EVO 4G I bought from someone off craigslist and everything was fine for 3 weeks then 3 days ago the phone died and i plugged it in with no led light showing the charging status. I thought perhaps it was a bad battery so I bought another battery and with the little life the new battery has it turned on and got stuck on the HTC EVO 4G splash screen.
So I pulled the battery out and re-installed and booted into the bootloader menu only to find out more bad news. When I try to boot into recovery from the bootloader menu it goes to the HTC EVO 4G splash screen and stays there forever. I have tried to clear storage, in which it clears and says everything is ok reboots into the HTC EVO 4G splash screen and gets stuck again, So I'm really concerned now and I cant find a solution anywhere I've tried several different methods to flash amon RA recovery, I downloaded the zip file and changed the name accordingly so the bootloader menu would automatically recognize it and it said installed successfully but still to no avail, and I do not believe I am able to manually flash another recovery method because I cannot get into usb debuggine mode from the phone so I'm not sure how adb would even begin to recognise the phone.......... someone for love of all things fancy please help me!!!! I'm struggling!!! lol

Also this is what appears on my bootloader menu:
supersonic EVT2-3 SHIP S-OFF
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01

If u can boot into recovery u can mount SD card to put a new rom on it. Wipe everything except ur SD card n flash new rom
Sentt from mmy pockett

{ParanoiA} said:
If u can boot into recovery u can mount SD card to put a new rom on it. Wipe everything except ur SD card n flash new rom
Sentt from mmy pockett
Click to expand...
Click to collapse
I cannot boot into recovery

If you have a card reader,you should be able to download a Rom,put it in the root of your sd card,rename it pc36img.zip,put it back in your phone and flash it through the bootloader.
Sent from my PC36100 using XDA App

BrianBusby2038 said:
If you have a card reader,you should be able to download a Rom,put it in the root of your sd card,rename it pc36img.zip,put it back in your phone and flash it through the bootloader.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have already attempted this method twice but I'll give it another shot

Try running RUU update. Download here:
OTA 3.70
http://www.megaupload.com/?d=86NCAM22
Link grabbed from PPCGEEKS user KarlE
this will revert you back to android 2.2, but this should fix your problem.

munesh23 said:
Try running RUU update. Download here:
OTA 3.70
Link grabbed from PPCGEEKS user KarlE
this will revert you back to android 2.2, but this should fix your problem.
Click to expand...
Click to collapse
Ok thanks I'll give it a shot any chance you could tell me the best way to apply the RUU update? name change to PC23IMG??

STRteg said:
Ok thanks I'll give it a shot any chance you could tell me the best way to apply the RUU update? name change to PC23IMG??
Click to expand...
Click to collapse
all you have to do is download that file and execute it in windows then just follow the instructions.

munesh23 said:
all you have to do is download that file and execute it in windows then just follow the instructions.
Click to expand...
Click to collapse
downloaded the file and executed it in windows and it reboots the phone from bootloader to bootloader again but phone never comes back on...

Do this, in this order...
Charge battery to full (since there's no way for you to tell how much charge there is you might as well be sure it's full...)
Boot to Bootloader
Select FASTBOOT with volume up/down
Press Power button to go into FASTBOOT
Plug phone in to PC
Run RUU.

Unknownforce said:
Do this, in this order...
Charge battery to full (since there's no way for you to tell how much charge there is you might as well be sure it's full...)
Boot to Bootloader
Select FASTBOOT with volume up/down
Press Power button to go into FASTBOOT
Plug phone in to PC
Run RUU.
Click to expand...
Click to collapse
Hey I tried this method and all was well for the most part and then the executable ruu said that it could not continue because my battery was less than 30% and my phone won't charge for some strange...

STRteg said:
Hey I tried this method and all was well for the most part and then the executable ruu said that it could not continue because my battery was less than 30% and my phone won't charge for some strange...
Click to expand...
Click to collapse
The phone doesn't charge in bootloader, turn the phone off and leave it on the charger when it's OFF until the light goes green, then start over.

Unknownforce said:
The phone doesn't charge in bootloader, turn the phone off and leave it on the charger when it's OFF until the light goes green, then start over.
Click to expand...
Click to collapse
Phone is not charging when it's off or at least there is no led lit up or anything

STRteg said:
Phone is not charging when it's off or at least there is no led lit up or anything
Click to expand...
Click to collapse
Then it's possibly a bad battery or simply a brick now, because if you can't charge it normally, doing anything to get it working again is futile... If you have another battery try that, or if you can take it to a shop and try one of their batteries in it... That's all I can think of doing...

Unknownforce said:
Then it's possibly a bad battery or simply a brick now, because if you can't charge it normally, doing anything to get it working again is futile... If you have another battery try that, or if you can take it to a shop and try one of their batteries in it... That's all I can think of doing...
Click to expand...
Click to collapse
Well I don't think its a complete brick just yet the usb port can't be bad if fastboot reads the pc when connected and vice versa, however I went to frys and bought a universal battery charger and am charging the battery to full right now. I'll let you know something soon thanks for all your help so far.

Ok so I let the battery charge, re-installed and ran the RUU executable file it flashed and installed successfully but is at the same place still gets stuck on htc evo 4g screen

What Rom and kernel were you on when you discovered it at white screen.
Also, did you just find it at the splash screen? or did it random reboot or just not boot?

Zac95 said:
What Rom and kernel were you on when you discovered it at white screen.
Also, did you just find it at the splash screen? or did it random reboot or just not boot?
Click to expand...
Click to collapse
Stock as far as I know and the phone died and when i went to recharge it and discovered the white splash screen

Ok I'm really stuck nothing is working for me the RUU ran and flashed properly just to get back stuck at the htc evo 4g screen again I was reading somewhere else that it needs to read S-ON on bootloader to flash the OTA RUU is this correct? and if so how can I change it with unrevoked if I cant get adb to recognize the device?

Totally bricked?

Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!

jaavaa said:
Okay, I tought i just could RUU my phone using RUU file. So I downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe and booted to fastbood mode -> connected USB -> ran RUU. Anyways, all wen fine and the gray HTC logo appeared on my screen but after few seconds the RUU gave me "Bootloader version error [140]". After that my phone is just dead. It wont turn on or anything, I cant get ADB to my phone. Screen is totally black. The phone just randomly vibrates when i plug it in the charger or press the power button after taking the battery out. But its just random. The charging led indicator wont even turn on.
I Had few weeks old XJ's MIUI installed, CWM 4.X.X.X and hboot 6.93.9999 (if i remember right, 6.93.XXXX it was anyways). After failing the RUU, I googled and found out that i shuold have downgraded hboot first? I recently bought a new phone so actually just didnt give s*** Im having proximity sensor problem in my old Desire, so I would like to return it to the shop after flashing the default rom.
So folks, how do I proceed? Totally bricked?
Thanks!
Click to expand...
Click to collapse
sounds like wrong RUU file meant for SLCD/Amoled.
try the first post in Q&A which should deal with this...it's a sticky for a reason

It looks like slcd brick look for droidzone slcd brick guide
Sent from my HTC Desire using XDA Premium App

Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.

jaavaa said:
Thanks, but as I already said, the phone cant be detected by PC. The phone wont even turn on. I tried again starting the phone to fastboot mode, but the phone wont even vibrate or show any signs of life. The only thing is that when i randomly plug the phone to the charger, it might vibrate and start warming up.
And yes, I've tried charging the phone over night assuming the battery would be empty.
Click to expand...
Click to collapse
so holding down back and power to get straight to fastboot doesn't work at all? i'm only referencing the troubleshooting guide
droidzone's slcd brick guide is more comprehensive, if that doesn't work then i dunno unfortunately...

Whoa, got some life to my phone! Started it somehow with usb plugged and vol down and i got it to recoverymode! ADB Devices gives me following:
List of devices attached
HT07XPL06736 recovery
Dont want to boot the phone again, what do i do now? tried running a RUU for SLCD spotted in the sticky thread here, but it gives me 170 USB error.
EDIT:
So I'm in this situation now? (taken from droidzone's guide)
"IF YOU SOFT BRICKED AN SLCD BRANDED DESIRE WHICH HAD AN UPDATED VERSION OF HBOOT BY FLASHING AN INCOMPATIBLE RUU, AND IF THE DISPLAY WONT TURN ON NOW, YOU CANNOT RESTORE THE PHONE TO WORKING CONDITION UNLESS YOU HAVE A CORRECT RUU FOR THE UPDATED HBOOT, OR A GOLDCARD. "
Click to expand...
Click to collapse
Well, is there a correct RUU for me?

as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there

kotag82 said:
as you are in recovery fastboot commands will not work try adb ones:
adb reboot bootloader
download fastboot commander you can find info there
Click to expand...
Click to collapse
Okay entered the command and now the phone cant be recognized in any ways again. Tried running RUU right after boot but still error 170. Cant get the phone visible to ADB again..

do you have goldcard? download WWE RUU 2.29 and try do it blind google some videos as pb99200 method is shown, how to use pb99200 method see bortak guide from stickies... im off now till wednesday

HOX bricked help to flash (no ROM in sd card)

ok i got my phone bricked since i change some fonts ¬¬ yeah its stupid but its done, my htc stays in HTC ONE X splash screen
1.- i already did wipe cache & dalvik (i dont want to try full restore yet)
2.- i cant access to the SD card to put the ROM.zip into it
any idea on how to bring it to life again?? (without losing data)

ok i did a full reset and now its showing only ANDROID label (splash screen) and thats all u.u still bricked, any idea????
is there any way to flash from PC i mean having ROM on PC i dont have it on my HTC

flash lastest clockworkmod and you can mount USB from recovery, copy rom and install as normal.
Sent from my Transformer TF101
@vorticalbox tweet me

what the latest version i got 5.8.4.0 i think this is the latest but i dont know hot to mount USB :/

Yep that's the latest version. Flash it via fastboot:
Put the recovery.img in your fastboot folder and rename it to "recovery.img", then open a command prompt and:
cd..
cd..
cd fastboot
fastboot flash recovery recovery.img
Now extract the boot.img from the ROM you want to flash on your PC, and copy it to your fastboot folder and:
fastboot flash boot boot.img
Then boot into recovery and:
Go to mounts and storage
Choose Mount USB Storage
Copy ROM to your phone
Factory reset
Wipe Dalvik cache
Choose Zip from SD Card
Flash Rom
Reboot and enjoy
If this doesn't work, you'll have to boot into flastboot mode and run the RUU for your phone.
Either way, it's not 'BRICKED'.
Just make sure your battery doesn't go below 30% before you fix it or it will be much more difficult to recover (but not impossible).
It's impossible to totally brick an S-ON One X as whatever happens, you can always get into fastboot mode.

Guys i have problem too. I flashed boot.img with kernel http://forum.xda-developers.com/showthread.php?t=1967897 via this tool http://forum.xda-developers.com/showthread.php?t=1962428
Now phone is bricked. It's only showin "htc quietly brilliant"" logo and i can't do anything. Won't go into fastboot, won't reset at all . Only logo..
Please help me. My hands are shaking.... :|||
EDIT
ok luckily i can restart it, but only restart. I can't turn it off by holding power button.
EDIT 2
Ok i managed to turn bootloader on. There is some hope!!

Einstein001 said:
Guys i have problem too. I flashed boot.img with kernel http://forum.xda-developers.com/showthread.php?t=1967897 via this tool http://forum.xda-developers.com/showthread.php?t=1962428
Now phone is bricked. It's only showin "htc quietly brilliant"" logo and i can't do anything. Won't go into fastboot, won't reset at all . Only logo..
Please help me. My hands are shaking.... :|||
EDIT
ok luckily i can restart it, but only restart. I can't turn it off by holding power button.
EDIT 2
Ok i managed to turn bootloader on. There is some hope!![/QUOTE
try this. http://forum.xda-developers.com/showthread.php?t=1734365
Click to expand...
Click to collapse

Ok guys. I almost had heartattack. By holding vol down buttont and power it went into Bootloader mode. I was able to get into recovery and then used venom flasher to change back to stock kernel. Oh god... Thank you guys trying to help me

Dudes, when its stuck in start up logo doesn't mean its bricked. It's bricked when you can't turn it on or go into bootloader. Please don't use "bricked" to describe every problem you encounter please.
Sent from my HTC One X using xda app-developers app

That is true. What's more I was stupid enough to flash kernel to totally different phone (One XL). Luckily my stupidity was spared this time.
I hope OP will repair his phone too.

Like I said, it's pretty much impossible to 'BRICK' an S-ON device.

What about If you flash a Ron intended for a different phone, doesn't this change the layout of system positions? Or I'm just being stupid and you need s-off to mess things up like that?
Sent from my HTC One X using xda premium

Einstein001 said:
That is true. What's more I was stupid enough to flash kernel to totally different phone (One XL). Luckily my stupidity was spared this time.
I hope OP will repair his phone too.
Click to expand...
Click to collapse
thanks i know how to mount UB from now when this happens my htc is alife again and sorry for the title

Sentinel196 said:
Like I said, it's pretty much impossible to 'BRICK' an S-ON device.
Click to expand...
Click to collapse
and than everybody cry, cause they have no s-off...Guys, You better say thanks for this one, you don`t know how many devices with s-off was bricked for real...

It still cant overwrite the bootloader, firnd you can always repartition by running the RUU
Sent from my HTC One X using xda premium

eltoffer said:
ok i got my phone bricked since i change some fonts ¬¬ yeah its stupid but its done, my htc stays in HTC ONE X splash screen
1.- i already did wipe cache & dalvik (i dont want to try full restore yet)
2.- i cant access to the SD card to put the ROM.zip into it
any idea on how to bring it to life again?? (without losing data)
Click to expand...
Click to collapse
Flash the newest CWM Recovery. Or any recovery with that you can use the option "advanced restore". Now Backup your Rom> wipe everything> restore>advanced restore>restore data only
Here you go
Sry, can one the mods delete this post? My browser is f****** up and didn't show me there are already answers...

I think this qualifies as "bricked"
OK, I am trying to help my sister with her HTC 1X. It will not turn on whatsoever. I hold down the power button, nothing. I hold down the power and one of the volume buttons (up or down), nothing. I hold down the power button and both of the volume buttons, nothing.
I have hooked it up to my laptop because I was able to find some drivers for the device and some files that will allow me to root it, should I be able to get the phone to do anything. Anyway, the only thing I get is a message from Windows saying that the device has malfunctioned and that I should disconnect it and reconnect it or replace the device.
I've scanned through several of the threads but cannot seem to find anyone with as legitimately bricked a 1x as my sister has. I am used to rooting and ROMing Samsung devices and thought I would lend a hand by trying to help out with this HTC device but I cannot get it to even show up in MY Computer.
Any help would be greatly appreciated.

D5S said:
OK, I am trying to help my sister with her HTC 1X. It will not turn on whatsoever. I hold down the power button, nothing. I hold down the power and one of the volume buttons (up or down), nothing. I hold down the power button and both of the volume buttons, nothing.
I have hooked it up to my laptop because I was able to find some drivers for the device and some files that will allow me to root it, should I be able to get the phone to do anything. Anyway, the only thing I get is a message from Windows saying that the device has malfunctioned and that I should disconnect it and reconnect it or replace the device.
I've scanned through several of the threads but cannot seem to find anyone with as legitimately bricked a 1x as my sister has. I am used to rooting and ROMing Samsung devices and thought I would lend a hand by trying to help out with this HTC device but I cannot get it to even show up in MY Computer.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
sounds like you need to activate the warranty

zuadao said:
sounds like you need to activate the warranty
Click to expand...
Click to collapse
Yeah, I was afraid she was going to have to send it back to HTC. What really stinks is that she's only had the phone for 35 days at this point. Started having problems a couple of days ago and ATT doesn't seem to want to do diddly.
Anyway, thanks for the response!

No worries. Pls let us know the outcome. Good luck.
Sent from my HTC One X