Database Info

Phone Kinda Bricked

I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0

Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.

chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.

saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices

Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command

ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.

He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.

Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...

chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all

When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".

I do not see # sign when i type adb shell..
Means I have to root again ?

What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.

this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S

Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.

Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.

Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?

It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?

Possible Brick

Hey all,
So tonight I attempted to install the Unofficial AOKP Jelly Bean posted here: http://forum.xda-developers.com/showthread.php?t=1862156
Before doing that, I followed the instructions to Unlock, Recovery, and Root my One S here: http://forum.xda-developers.com/showthread.php?t=1583427
After following those instructions, I then followed the instructions for AOKP Jelly Bean however my sdcard couldn't be mounted and the phone was in a boot loop if I didn't boot into fastboot by holding down the volume - and power buttons.
I attempted these instructions below however I couldn't get a stock recovery flashed.
1) Use the All-in-One-Kit and flash your recovery back to stock
2) Boot into the bootloader and choose to "clear storage" and afterwards to reset to factory defaults.
3) Go back to the all-in-one-kit and flash a CWM recovery version again.
4) Reboot into recovery (CWM). Your /sdcard should now be mounted and visible.
5) Now, try the UTB rom (it worked for me), rename the zip file to something short (i.e. utb.zip), and push it to the sdcard using adb as follows:
Click to expand...
Click to collapse
Still caught in the reboot loop, I relocked and tried to run an RUU file found here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
I was able to successfully re-lock the phone however every time I try to run the RUU file it comes back with an error about 3-5 minutes into the process.
At this point, my phone boots into fastboot. At the top I have "Tampered, Relocked, Security Warning." My HBOOT is 1.14.0004 and my Radios is 1.08ts.50.02.16
I would appreciate any help if there is a solution. Thank you for your time!
Update: Not sure if this is helpful or not, but whenever I try to do something with The All in one toolkit the cmd window says device not found. Also, when I try to boot into recovery from fastboot, I get a green downward and circular arrows before getting the red triangle and exclamation point.
Update: Running the RUU mentioned above fails at the Signature stage and the cmd prompt when trying to write recovery returns "signature verify fail"

Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app

whozilla said:
Are you s4 or s3? what kind of computer you got? The drivers need to be installed. then read up how to use android SDK. Then retry to flash the stock recovery using the same steps in your quote.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I am pretty sure I am S4 (tmobile USA). I am on a windows 7 home build, and the drivers should be installed (at least, I could use HTC sync before all of this). I'll definitely try again tonight. If anyone has any other suggestions they would be much appreciated!

Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app

whozilla said:
Make sure HTC sync is NOT active on your pc. Try searching for the original version of one s all in one toolkit. It has the stock recovery. I'm pretty sure this unbrick method works for all hboot versions but don't take my word for it. Focus on your goal. Get stock recovery flashed. You can also try unlocking your boot loader again and using the all in one to reflash cwm. In some cases like mine. The unofficial cwm touch is the only successful flash I got. Ps. Try having your phone in fastboot. Plug in USB and see if it says "fastboot USB" then type your android SDK directory for your fastboot folder. For example open cmd
cd\
cd androidsdk\tools
androidsdk\tools fastboot devices.
Fastboot devices command will tell you if your drivers are working.
You can also type in adb devices instead of fastboot devices.
Hope this helps. But you probably already know this
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help!
Here are my results:
HTC Sync is not running. Fastboot devices returns a device ID so that seems good. When trying to flash a stock recovery (that I got on this forum somewhere, but can't remember where) it sends it ok but I still get "remote: signature verify fail"
I unlocked the device and flashed TWRP 2.2.2.0 with the all in one tool kit. This put me back into the boot loop mentioned above. Once I manually got back into the bootloader and selected recovery, I was able to get into the TWRP recovery. At this point, I am kind of worried about doing anything. I would like to be able to push AOKP Unofficial JB if at all possible. Any further guidance would be appreciated!

Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville

usaff22 said:
Please, please don't use the toolkit. It makes people find problems later on and not know a thing about what to do.
Sent from my locked, tampered ville
---------- Post added at 08:24 AM ---------- Previous post was at 08:23 AM ----------
Oh well, flash AOKP through TWRP and then reboot into bootloader and flash the boot.IMG.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
It is clear to me that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!

You have to fastboot push the AOKP zip through the bootloader I think.
Sent from my locked, tampered ville

Veritas327 said:
It is clear to fme that I didn't do enough research before getting into this. I thought my experience with putting custom roms on my galaxy S (a phone I really disliked) would give me the appropriate background. Clearly I was wrong! I'm a little unsure how to flash AOKP through TWRP when AOKP is not on my SD card. In fact, when I look at the SD card in TWRP, the only file on it is "TWRP."
I think I need to flash TWRP 2.3.0 (rather than the 2.2.2.0 I have), because it supports ADB Sideload (talked about here on their site which I can't yet link to). Can I do that through the Android SDK like I have been doing? I don't need to do anything to the TWRP 2.2.2.0 before trying to flash 2.3.0 do I? It seems if I do that, I could send AOKP to my phone through adb when it is in recovery.
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Thanks again!
Click to expand...
Click to collapse
Just like the post above mine says, you have to adb push the file onto the sd card. I'm not to familiar with TWRP (using it actually got me into a bit of a dilemma) so I only know the process for CWM. If TWRP is anything like CWM then you have to be in recovery to adb push and have sdcard and system set to "unmont". It's pretty easy and there's a couple threads explaining how to do it. The command basically is :: adb push romname.zip /sdcard/romname.zip:: Note the space before "/sdcard" I'dpn't know if this ill help you or if you've solved your problem already but this is just my 2 cents, good luck!

Sorry for my late reply; I was rushed to the ER last night in excruciating pain. Looks like I'll be dealing with a kidney stone over the next few days.
So far, I have tried to push AOKP through fastboot. ADB says "no devices found" and when I type adb devices, I get "List of devices attached" and nothing under it. However, when I type fastboot devices, I do get a device ID. As of now, I am downloading the TWRP 2.3 recovery and will try to sideload with adb with that.

Update:
I was able to successfully install TWRP 2.3 and adb sideload the AOKP zip file. The phone then went back into a reboot loop, and I was able to get into recovery to install the .zip. The phone then rebooted, showed the HTC with red text screen very briefly, went to black, showed the HTC with red text screen again, went black, and now the aokp boot animation is repeating over and over. It has been doing so for about 5-7 minutes. I haven't yet installed gapps as mentioned in the AOKP post (I'm honestly not even sure what that is). Where should I go from here?
As a side note, the phone is plugged into power though the LED is not lighting up. It was at 98% when I flashed the .zip, but I obviously don't want it to die on me. Should I turn the phone off or is it still charging?

Veritas327 said:
And just for my better understanding, what is different about flashing it in TWRP and then flashing the boot.img in fastboot?
Click to expand...
Click to collapse
The newer hboot versions (1.13 and up) don't let you flash boot images in recovery, even if it reports success.
So there is technically no difference, except fastboot always works and recovery depends on hboot version.
Did you fastboot flash the boot image that comes with your rom?
-Jobo
Edit to add: So it seems that following the recipe in your post #1 did in fact make your sdcard mountable again, or did you do something else as well for that?

Fixed!
I ended up flashing the boot.img with fastboot and then going into recovery, factory resetting and then re-installing the rom (and gapps which I now know stands for google apps). I'll be playing around with the ROM but at least I have a working phone again!
I think, in the end, it came down to my sd card not being mounted and my lack of knowledge about how to fix it.

adb not recognizing my bootlooping One xl

Rogers HTC one xl
2.14 s-on, bootloader unlocked at htcdev, running the new Cleanrom (sense 5), everything was fine.
Now in a bootloop as a result of running the Beastmode 3.5 installer
Can't get into fastboot with "power + volume down, wait for flashing leds to stop, screen to go black, then let go of power and continue to hold volume"
not sure why. I've been in fastboot many times and know the procedure.
Obviously next step would be to adb reboot bootloader, go into recovery and flash my backup....
But... list of devices attached: zilch.
Any idea?

dkom1 said:
Rogers HTC one xl
2.14 s-on, bootloader unlocked at htcdev, running the new Cleanrom (sense 5), everything was fine.
Now in a bootloop as a result of running the Beastmode 3.5 installer
Can't get into fastboot with "power + volume down, wait for flashing leds to stop, screen to go black, then let go of power and continue to hold volume"
not sure why. I've been in fastboot many times and know the procedure.
Obviously next step would be to adb reboot bootloader, go into recovery and flash my backup....
But... list of devices attached: zilch.
Any idea?
Click to expand...
Click to collapse
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.

Just hold volume down, the next time it starts the boot loop you should get into bootloader.
Sent from my Evita

Uh oh - tried the above with no luck. Just flashed Viper XL 4.2 in TWRP - but now it's just in a loop between the htc dev warning screen, the htc one screen, then off.
Volume down doesn't work. ADB doesn't see it (just installed the new one).
Help please.

Myrder said:
With the new 4.2.2 Android version ADB has a security feature that has to be authenticated on the users screen before the phone can be accessed.
You also need to check your ADB version: 1.0.29 or 1.0.31?
1.0.29 - Will not see your device/gives a "device offline" output.
1.0.31 - Will give a prompt on your device asking for authentication. This is the one you want.
To check your ADB version, nav to your ADB folder in cmd prompt and type "adb version" no quotes.
If it gives you 1.0.29, you need to update using your SDK manager.
To do this you need to nav to your /tools folder in your SDK folder. Here you will type "android" no quotes. Then follow the upgrade process.
Click to expand...
Click to collapse
Do you have link for this adb 1.0.31 version? I got same error device not found when using Android 4.0.3 sense 4 ROM?
Swyped From BlueICESense_JBE

For you, that doesn't matter. Which OS are you on?
Windows, make sure you have the proper drivers and the SDK tools are properly installed. If you ha e them installed, navigate to your /sdk-tools/tools folder in a cmd prompt and type android. That will five you the SDK update manager.
Ubuntu/Linux, make sure your udev rules are set up correctly.
Sent from my Alienized Evita using XDA Premium IV

Myrder said:
For you, that doesn't matter. Which OS are you on?
Windows, make sure you have the proper drivers and the SDK tools are properly installed. If you ha e them installed, navigate to your /sdk-tools/tools folder in a cmd prompt and type android. That will five you the SDK update manager.
Ubuntu/Linux, make sure your udev rules are set up correctly.
Sent from my Alienized Evita using XDA Premium IV
Click to expand...
Click to collapse
I'm on Windows 7 and I tried both Android 4.2.2 and Android 4.0.3 same result......I might think HTC driver not installed properly as well ......check my other thread S-OFF_Htc One XL driver I don't want clutter with this on his thread.......
Swyped From BlueICESense_JBE

dayz3r0 said:
Uh oh - tried the above with no luck. Just flashed Viper XL 4.2 in TWRP - but now it's just in a loop between the htc dev warning screen, the htc one screen, then off.
Volume down doesn't work. ADB doesn't see it (just installed the new one).
Help please.
Click to expand...
Click to collapse
Is the volume down button broken? Usually if it doesn't work it's a timing error.
Sent from my Evita

timmaaa said:
Is the volume down button broken? Usually if it doesn't work it's a timing error.
Sent from my Evita
Click to expand...
Click to collapse
Volume down got it into bootloader - seems like it was a timing issue. Had tried a bunch, so kind of surprising. Going to flash back to the old ROM and do s-off and a bunch of other upgrades then try again. Thanks for your help.

No problems.
PS. If someone helps you on XDA, press the thanks button.
Sent from my Evita

Help me

I am new to htc
i am flashing a custom rom for first time on htc
what do i have to know?
and what is needed?
and i am stuck on soft brick and cant mount internal storage
i am using
hboot 2.15
it shows tampered
and twrp 2.8

Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...

Rapier said:
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Click to expand...
Click to collapse
Do i need to s off
and ive noticed that even after flashing rom system folder is empty except for bin and by the way my device is t mobile

S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...

Rapier said:
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Click to expand...
Click to collapse
unlocked yes i did it but i cant flash the rom it wont be pushed into system at all
please my mind is not clear can you give me a link for kernal pleaseee

Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...

Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
ive restored from ruu

Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
Why my device wont s-off its always telling me to f***off

eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
What RUU Worked?

eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
În order to properly s-off, you might need a certain ROM to be installed. Have you tried to get s-off having that stock ROM you got after RUU?
Sent from nowhere over the air...

Can s-off be achieved without an installed ROM?

bobby2x420 said:
Can s-off be achieved without an installed ROM?
Click to expand...
Click to collapse
Only by a j-tag device but I don't know how that works. The software methods presented here needs a ROM as far as I know
Sent from nowhere over the air...

bobby2x420 said:
What RUU Worked?
Click to expand...
Click to collapse
Ya it worked (not androidruu though) i had to search a lot i got tired of it

[Q] HTC One X (ATT) No OS

Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?

kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon

timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.

kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?

timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.

kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.

timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.

kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.

timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.