Database Info

[Q]stuck in bootloader,no recovery

Hi to everybody,my friend has a problem with his desire S.
his phone is turned off itself vibrating.now he can boot only in bootloader mode,and the recovery is gone.
here some spec.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
( bootloader ) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) [email protected] baseband : 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
He also tried to flash the eng hboot to run a RUU,but seems he can't flash the hboot (hangs on "writing hboot").
thanks for any help.

Did your friend happen to pull his battery anytime before all this started?
Recovery doesn't just "disappear" - he must have done something prior to that...
Anyway, the first thing is to rule out (or in) a fried eMMC
So do this:
Set up adb/fastboot and connect your phone (link in my sig)
Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
For further details, consult this excellent guide by amidabuddha:
http://forum.xda-developers.com/showthread.php?t=1284196

thanks for the quick reply.when I have the output of the dmesg | grep mmc0 ,I'll post here.I haven't the phone with me,so I have to wait for my friend.

the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?

NeTvAmPiRe70 said:
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
Click to expand...
Click to collapse
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery

enigmaamit said:
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
Click to expand...
Click to collapse
...no luck hangs on "writing recovery".

NeTvAmPiRe70 said:
...no luck hangs on "writing recovery".
Click to expand...
Click to collapse
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
Click to expand...
Click to collapse
this is not the same thing but with a different recovery?
however,I'll give it a try.
NeTvAmPiRe70 said:
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
Click to expand...
Click to collapse

NeTvAmPiRe70 said:
this is not the same thing but with a different recovery?
however,I'll give it a try.
Click to expand...
Click to collapse
I don't know what was there in that file... so i sent you mine.
But if fastboot wasn't working, the possibility of an eMMC brick is looming larger...
Just try the commands i asked you to type in my first post... I mean boot into bootloader, then see if these commands cough up a report... if it doesn't work, boot into fastboot and try again. You must have some kind of recovery man...
Also, you didn't say what happens when you select Recovery option from the bootloader... what happens?

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
Click to expand...
Click to collapse
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.

NeTvAmPiRe70 said:
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
Click to expand...
Click to collapse
Then i think your friend might have fried his eMMC.
Last resort is to call in the expert : Send a PM to amidabuddha, the guy whose guide i linked in my first post. I haven't found anyone more knowledgeable in these matters. If anyone can help you, its him.
I hope you can salvage the device...but its not looking very good....

thanks for your help,I'lll contact the expert

...and the expert has decreed:fried eMMC

NeTvAmPiRe70 said:
...and the expert has decreed:fried eMMC
Click to expand...
Click to collapse
That's what i thought too... just didn't want to mouth off such a grave judgement without being doubly sure.
Very sorry - unable to help any further. Hope your friend takes the news well, and wish him/her better luck for the next device!

[Q] Cache partition problem, HELP!

Hi,
I am trying to change my rom using CWM. I made my phone S-off. Than installed CWM. While trying to wipe all user data before rom install, it stuck. So I took the battery off. Now it gives error in CWM screen:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
So I read a bit and tried to format the cache partition from mounts and storage section. It gives
Error formatting /cache!
message.
I can go into fastboot, CWM and hboot.
I can install rom zip from sdcard.
I have a backup created with CWM.
I can't boot into Android, I can't restore my backup.
I tried to push recovery again using fastboot but it freezes there too.
I used recovery-clockwork-5.0.2.0-saga.img file while installing CWM on the first place. Now it is the installed one.
I have SDK and tools like adb and fastboot.
Please help!

1. Download Android Flasher to your PC
2. Download 4EXT Recovery image
3. Reboot the phone to bootloader (there should be FASBOOT USB written somewhere on the screen)
4. Flash the image with the Android flasher (check the "already in fastboot" box)
5. Wipe all partitions and try to install a custom ROM
If not working see the "before eMMC replacement" guide in my signature

Thank you very much for your detailed and quick response. I really appreciate it
I did what you told but, android flasher froze so I shut it down. After that I went to the topic on your signature and checked if the emmc is fried but it is not and responding well. Then I went to the post that is about the partition size. I ran
cat /proc/mtd
command in adb shell and got no partitions listed at all.
Now what should I do?
Again I can not install the recovery you mentioned. Is there anything that I can do with CWM which is already installed and working?
Also as far as I read from other topics, some are mentioning about putting the PG88DIAG.zip file which hboot is searching for in the bootloader startup to the phone and making it un rooted and re root it afterwards. But I could not find the zip file named PG88DIAG.zip so I could not try that. Is there anything you can say about it?
Regards;
y.

ysayita said:
Thank you very much for your detailed and quick response. I really appreciate it
I did what you told but, android flasher froze so I shut it down. After that I went to the topic on your signature and checked if the emmc is fried but it is not and responding well. Then I went to the post that is about the partition size. I ran
cat /proc/mtd
command in adb shell and got no partitions listed at all.
Now what should I do?
Again I can not install the recovery you mentioned. Is there anything that I can do with CWM which is already installed and working?
Also as far as I read from other topics, some are mentioning about putting the PG88DIAG.zip file which hboot is searching for in the bootloader startup to the phone and making it un rooted and re root it afterwards. But I could not find the zip file named PG88DIAG.zip so I could not try that. Is there anything you can say about it?
Regards;
y.
Click to expand...
Click to collapse
Freezing during fastboot command execution is not a good sign at all. Nevertheless if the eMMC check is stating that your card is initializing properly then you should be able to restore your phone.
Desire S in not mounting in /mnt so you cannot see partitions there
Rename the image from my previous post to recovery.img and try to flash it with fastboot (be sure that you have your serial as output of the "fastboot devices" command): fastboot flash recovery recovery.img
If not working go through the eMMC guide again - especially point 4. Note your hboot version - if it is the Revolutionary one you have to change it

amidabuddha said:
Freezing during fastboot command execution is not a good sign at all. Nevertheless if the eMMC check is stating that your card is initializing properly then you should be able to restore your phone.
Desire S in not mounting in /mnt so you cannot see partitions there
Rename the image from my previous post to recovery.img and try to flash it with fastboot (be sure that you have your serial as output of the "fastboot devices" command): fastboot flash recovery recovery.img
If not working go through the eMMC guide again - especially point 4. Note your hboot version - if it is the Revolutionary one you have to change it
Click to expand...
Click to collapse
Again thank you.
I did the procedure from the fastboot directly as you told but when it sends the file and begins the write procedure, it freezes. So I went to the eMMC topic again to step 4 and tried to change the hboot version to 0.98.2000 from current 6.98.1002 which is revolutionary by the way. But in android flasher I have this log output
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.196s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.225s
also in the screen I see
Code:
Can not roll back hboot version
message at the bottom in red.
So I tried to do it again with fastboot and in command prompt I wrote
Code:
fastboot flash bootloader <img file>
but this time I got this output
Code:
fastboot flash bootloader ..\hboot_0.98.000
0_361a7ba6_0310.img
sending 'bootloader' (1024 KB)... OKAY [ 0.197s]
writing 'bootloader'... FAILED (remote: partition does not exist!)
finished. total time: 0.222s
Then I renamed the zip file to PG88DIAG.zip and pushed it to /sdcard/ using adb. After rebooting hboot, it asked if I wanted to start the update and I chose yes. But again at the end it gave the same message with the android flash:
Code:
Can not roll back hboot version
at the bottom in red.
I can not change hboot version to the required 0.98.2000 version with the methods mentioned.
Is there anything else I can do?

The proper command is
Code:
fastboot flash hboot hboot.img
but this is what the Andorid FLasher did
try the following: boot to Recovery, connect to PC, copy the hboot.img file to your SDcard, open command prompt and type:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
if not working try to unmount/mount the SDcard:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
umount /sdcard [I](not a typo the command is umount, not u[B]N[/B]mount)[/I]
mount /sdcard
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]

I copied the file to the SDCard. Then in adb shell
Code:
~ # ls /sdcard/
ls /sdcard/
~ # umount /sdcard
umount /sdcard
umount: can't umount /sdcard: Invalid argument
~ # exit
exit
adb push ..\hboot.img /sdcard/
1627 KB/s (1048576 bytes in 0.629s)
adb shell
~ # ls sdcard
ls sdcard
hboot.img
~ # dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 11.191921 seconds, 91.5KB/s
~ # reboot bootloader
reboot bootloader
It still has the same hboot.
After that;
Code:
fastboot flash hboot ..\hboot.img
sending 'hboot' (1024 KB)... OKAY [ 0.201s]
writing 'hboot'... INFOimage update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.231s
Again result is same with AndroidFlasher or installing with zip file from hboot.
Code:
Can not roll back hboot version.
Is there a some kind of write protection? Is there a possibility of mmcblk0p18 not being the right partition section?
Again, thanks a lot!

Yes there is a write protection and this is the reason why I always recommend to change it right after the S-OFF procedure.
Anyway search in the forum for hboot over alpharevx or 2.00.2002 and try them with dd. This is you only way to restore with RUU. But for me this is an indication of bad eMMC and I am surprised that you have positive output of the dmesg command. Also you can push the hboot.img to /data/temp and dd from there
Sent from my Desire S using Tapatalk

How about RUU-ing your way back to stock, re-rooting it, and restoring your backup? Assuming there is later RUU.exe with higher HBOOT version, compatible with your CID.
And when I say RUU-ing, I mean stock HTC RUU.exe, not Android Flasher.
And if RUU fails, you can be sure it's your eMMC...

amidabuddha said:
Yes there is a write protection and this is the reason why I always recommend to change it right after the S-OFF procedure.
Anyway search in the forum for hboot over alpharevx or 2.00.2002 and try them with dd. This is you only way to restore with RUU. But for me this is an indication of bad eMMC and I am surprised that you have positive output of the dmesg command. Also you can push the hboot.img to /data/temp and dd from there
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
I found something that may be relevant. The problem is that, before dd'ing I need to get su rights so every guide I read requires to enter the su command and acquire those rights on before the dd command. But the problem is that, when I enter the adb shell, it seems that I already have the su rights (I have the # mark on the command line) and if I enter su again, it says it is not recognized. So could this be the reason why the partition seems to be overwritten and it is not, me not having su rights while dd'ing? If that's the case, how could make the su command work?
Thanks a lot.
Regards;
y.

Jack_R1 said:
How about RUU-ing your way back to stock, re-rooting it, and restoring your backup? Assuming there is later RUU.exe with higher HBOOT version, compatible with your CID.
And when I say RUU-ing, I mean stock HTC RUU.exe, not Android Flasher.
And if RUU fails, you can be sure it's your eMMC...
Click to expand...
Click to collapse
As far as I learned today, because that my bootloader is s-off'ed by revolutionary, the bootloader contained in RUU cannot overwrite it. So installing RUU without getting the stock bootloader with hboot 0.98 is not an option. But thanks anyway, any tiny bit of help is really precious.
Regards,
y.

ysayita said:
I found something that may be relevant. The problem is that, before dd'ing I need to get su rights so every guide I read requires to enter the su command and acquire those rights on before the dd command. But the problem is that, when I enter the adb shell, it seems that I already have the su rights (I have the # mark on the command line) and if I enter su again, it says it is not recognized. So could this be the reason why the partition seems to be overwritten and it is not, me not having su rights while dd'ing? If that's the case, how could make the su command work?
Thanks a lot.
Regards;
y.
Click to expand...
Click to collapse
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)

amidabuddha said:
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.468.2
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 4198mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.025s
First guide seems to be pulled off. First, trying the other one.
Thanks.
y.

amidabuddha said:
# prompt means root privileges, so this should not be the case. The strange is that you do not have any I/O errors.
Try this and this
also post here the output of
Code:
fastboot getvar all
(hide your IMEI)
Click to expand...
Click to collapse
Now, I read from somewhere that /system should be mounted before dd'ing so I mounted it from recovery's mounts and storage menu. Than I tried to dd again and I got this output:
Code:
~ # dd if=/data/tmp/hboot.img of=/dev/block/mmcblk0p18
dd if=/data/tmp/hboot.img of=/dev/block/mmcblk0p18
dd: writing '/dev/block/mmcblk0p18': I/O error
1+0 records in
0+0 records out
0 bytes (0B) copied, 5.013903 seconds, 0B/s
So what can be the problem? Is it mean that chip is fried?
Edit:
I got dmesg output again and it seems responding well:
Code:
dmesg | grep mmc0
<3>[ 6.956176] mmc0: No card detect facilities available
<6>[ 6.956817] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 6.956939] mmc0: Platform slot type: MMC
<6>[ 6.957183] mmc0: 4 bit data mode disabled
<6>[ 6.957305] mmc0: 8 bit data mode enabled
<6>[ 6.957427] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 6.957672] mmc0: Slot eject status = 0
<6>[ 6.957794] mmc0: Power save feature enable = 1
<6>[ 6.958038] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0ba0d000
<6>[ 6.958160] mmc0: DM cmd busaddr 0x0ba0d000, cmdptr busaddr 0x0ba0d300
<6>[ 7.111846] mmc0: new high speed MMC card at address 0001
<6>[ 7.113494] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
y.

Your eMMC is fine according to this command but it may be failed by another reason...
The first guide is pulled off but there is an attachment at the first post..try it as well as 2.00.2002
Mount data before "dd", not system, or mount them all. Try all possible combinations, because in general you should change the hboot first. You cannot proceed otherwise. Then take a look here, because you will not be able to find a RUU for your version.
You can try falshing hboot with a Goldcard as well

amidabuddha said:
Your eMMC is fine according to this command but it may be failed by another reason...
The first guide is pulled off but there is an attachment at the first post..try it as well as 2.00.2002
Mount data before "dd", not system, or mount them all. Try all possible combinations, because in general you should change the hboot first. You cannot proceed otherwise. Then take a look here, because you will not be able to find a RUU for your version.
You can try falshing hboot with a Goldcard as well
Click to expand...
Click to collapse
I tried both and result is the same.
Also I mounted data and tried. Again same error with I/O.
When I try to mount /system first and then /data, I got error mounting /data. And when /data first and then /system, I got error mounting /system. So I could not try with both of them mounted.
I read about creating Goldcard but I can not get the CID with this code
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
So I can not move further in gold card creation.

Goldcard without device
Also wipe all and try a custom rom again

amidabuddha said:
Goldcard without device
Also wipe all and try a custom rom again
Click to expand...
Click to collapse
I had a goldcard at last. Then I tried to install the RUU with goldcard in device. But it keeps freezing at rebooting bootloader phase.
So I tried to flash with fastboot again but result is as below:
Code:
sending 'hboot' (1024 KB)...
OKAY [ 0.185s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.214s
And I get
Code:
Can not roll back hboot version
message again.
Then I tried putting P88IMG.zip to goldcard and tried to flash from there in hboot but again the same cannot rollback message appeared and froze.
So I went back to adb shell and tried dd'ing from /sdcard/hboot.img but I/O error persists.
So I am aware that I am running out of choices but, please keep suggesting.
Thanks,
y.

This was mentioned at the first hboot link that I gave you. There is a problem sometimes with region specific or branded devices.
But honestly I have no idea why you cannot replace it via dd. Sorry, but out of suggestions
Maybe you should try at the Revolutionary freenode IRC channel - they are the experts in this field after all....

amidabuddha said:
This was mentioned at the first hboot link that I gave you. There is a problem sometimes with region specific or branded devices.
But honestly I have no idea why you cannot replace it via dd. Sorry, but out of suggestions
Maybe you should try at the Revolutionary freenode IRC channel - they are the experts in this field after all....
Click to expand...
Click to collapse
Thank you for your deep interest and kind efforts, I really appreciate it. As you suggested, I contacted with the guys in Revolutionary freenode IRC channel and they helped me. But there were no solution for it right now. I am going to try my chance with HTC Service. Hope they can do something about it.
Regards;
y.

[Q] Help!!!

Hi, tried to install a new rom on my HTC One X ATT without success..
Specs : HTC ONE X Evita PVT Ship S-On RL
Hboot- 1.140002
Current status : ******TAMPERED******
******UNLOCKED******
I currently have TWRP 2.2.0 but I am unable to install any rom, also I have by mistake formatted my drive so my phone doesn't have any operating system atm. I changed the SCid to 1111111 but can't get from S-On to S-Off. I tried using a method on this forum and I keep getting
C:\.................>adb push soffbin3 /data/local/tmp/
error: device not found
Same for the next 3 lines, I am guessing maybe because those folders don't exist anymore on my drive....
Would really appreciate any help on what step to take next to have it back n working... The latest of Pac Man Rom was what I tried to install....
Sam

You couldn't install any aosp ROMs because you don't have the correct firmware, you would need to upgrade via the 3.18 RUU to update your phone to the 2.14 firmware. First thing you need to do is use the mount menu in TWRP and copy a Sense 4+ Android 4.1 ROM to the phone from your PC. Once you've installed a Sense 4+ ROM just use the Rumrunner method to get s-off, you'll find it here. Once you have s-off you can run the 3.18 RUU, then you can flash TWRP again, then you can install current aosp ROMs.
Sent from my Evita

Thanks
Thanks will do right away but got 1 more question, sorry I am new at this, but you said "Sense 4+ Android 4.1 ROM to the phone from your PC"
Is there a specific version I should install or could you give me a name of one I could look up to download and install ? I just read that some I can't install because my Hboot is only 1.14.... Is there a website I can go to download a sense 4+ rom ?

You don't ever need to go anywhere except XDA for information and software for your phone. Specifically you need to stay within this forum you're posting in now. Here's the main page for our device:
http://forum.xda-developers.com/one-x-att
And here's our two development sections:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
You'll find what you need there, any Sense 4 ROM will be fine.
Sent from my Evita

S-Off
So I installed Rage XL Evita V2.1 rom and it works... Next I tried to use the Rumrunner method to S-off but here's what I get...
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (9/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (9/120)
FATAL: Download updated package at rumrunner.us
Press ENTER to exit
Any idea on the problem ? I did follow instructions and use the Universal HTC Download 0.5.0....

It might be an incompatibility issue with the Rage XL ROM, you could try the Facepalm s-off method instead. You'll find it here.
Sent from my Evita

NVM
Sorry please ignore previous post, finally got it to work. Hboot 1.14, S-Off and RageXL Evita V 2.1 atm, I am currently downloading the 3.18 RUU.. Thanks a lot for the help will let you know if I have any more questions....

Cool, glad it worked. Yell out if you have any further issues.
Sent from my Evita

error Device Not found
Thanks, current status is
*****UNLOCKED******
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT- 2.14.0000
Radio- 0.24p.32.09.06
So I ran and updated the RUU, unfortunately after it did it somehow deleted my twrp I had installed so i cant mount and flash/ install other roms, I tried to re flash TWRP 2.6 for evita but it keeps telling me thers an error and device not found.. So I reinstalled the drivers, and when I check in my device manager I can see my HTC with it's driver installed, I even get a sign at the right bottom of my screen telling me the device is ready to be used but when I run fastboot flash openrecovery....., once again device not found... Any suggestions on what to do next ?

Can't Root
I tried rooting like I did before but couldn't, heres what I get..
Rooting...
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: can't create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
1102 KB/s (1075144 bytes in 0.952s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chown /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
I am guessing this is why I can't flash twrp, tried also to flash through android ( Recovery Tools ) I get that my phone isn't rooted...

Another fail
I tried another method still not rooted....
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb devices
List of devices attached
HT24YW310539 device
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push oneXchopper /data/local/
tmp/xpwn
2329 KB/s (1283460 bytes in 0.538s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push busybox /data/local/tmp/
busybox
2445 KB/s (811432 bytes in 0.324s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push ownage /data/local/tmp/p
hase1.sh
57 KB/s (296 bytes in 0.005s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell chmod 755 /data/local/t
mp/xpwn /data/local/tmp/busybox
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell ln -s /data/local/tmp/b
usybox /data/local/tmp/sed
link failed File exists
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell "/data/local/tmp/xpwn"
[+] This may take a few minutes.
[-] Failure.

ysfsam said:
Thanks, current status is
*****UNLOCKED******
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT- 2.14.0000
Radio- 0.24p.32.09.06
So I ran and updated the RUU, unfortunately after it did it somehow deleted my twrp I had installed so i cant mount and flash/ install other roms, I tried to re flash TWRP 2.6 for evita but it keeps telling me thers an error and device not found.. So I reinstalled the drivers, and when I check in my device manager I can see my HTC with it's driver installed, I even get a sign at the right bottom of my screen telling me the device is ready to be used but when I run fastboot flash openrecovery....., once again device not found... Any suggestions on what to do next ?
Click to expand...
Click to collapse
Of course it deleted TWRP, it returns your phone to a stock state. I did mention you'd have to flash TWRP again after the RUU.
Sent from my Evita
---------- Post added at 05:26 AM ---------- Previous post was at 05:23 AM ----------
ysfsam said:
I tried rooting like I did before but couldn't, heres what I get..
Rooting...
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: can't create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
1102 KB/s (1075144 bytes in 0.952s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chown /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
I am guessing this is why I can't flash twrp, tried also to flash through android ( Recovery Tools ) I get that my phone isn't rooted...
Click to expand...
Click to collapse
I'm not sure why you're doing that again, that process doesn't root your phone, it gives you SuperCID which you already have. There's no point in trying that again. No your phone isn't rooted, in order for it to be rooted you need TWRP installed first so you can install root or a rooted ROM. You just need to work out why fastboot isn't working and you'll be good to go.
This may seem like a stupid question but I have to ask it, is the phone in fastboot mode when you're trying the fastboot commands? If it is and you're still having problems, try uninstalling your drivers, then download HTC Sync Manager from HTC.com, once that's installed connect your phone while booted into Android and it'll make sure the right drivers are installed.
Sent from my Evita

[Q] s-off

For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
HTC One XL: http://forum.xda-developers.com/show....php?t=1952038 (2.2)
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
1.) Download patcher and unzip it in your working directory:
soffbin3.zip soffbin3.zip Mirror
2.) Download the zip below
OneX.zip = MD5: 99a8eced1010543e12cbd4e4e8f9638f, Mirror
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip PJ8312000-OneX.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
At step 7...command adb shell su -c "/data/local/tmp/soffbin3"
not found ...
Tempered
Unlocked
Evita pvt ship s-on
HBOOT-2.14.0000
Wht should i do now?

Did you extract the file into your fastboot folder after downloading it as per the instructions?
Sent from my Evita

timmaaa said:
Did you extract the file into your fastboot folder after downloading it as per the instructions?
Sent from my Evita
Click to expand...
Click to collapse
yes i have extracted the files but option 7 part 3 not works

The "not found" message suggests that you haven't extracted/unzipped the soffbin archive to your fastboot folder.
Sent from my Evita

One Mini s-ON, trying to get s-OFF

Hey guys, I have a problem with this phone HTC one mini, in fact I'm trying to unlock it with Sieempi method, but for this I need the device to be s-off. I unlocked the bootloader, the device be rooted, and when I try to use Rumrunner i got this error message.
Code:
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (19/120)
Waiting
Test 2: Booting device
Waiting for ADB (55/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (55/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Then i find this theard
http://forum.xda-developers.com/showthread.php?t=2573479
And download this two files, but then I stuck.
I'm not sure how to do the rest, but I tried it this way and I have failed.
I unpacked JmzM4_Kernel-09-4-13.zip file, and copied the boot.img file in the SDK folder from where I started CMD. In the CMD I typed "fastboot flash boot boot.img" and I got the message OK.
Then I went into recovery and found JmzM4_Kernel-09-4-13.zip file on the internal memory of a cell phone and I tried to install it (so I read) a zip file, and then I got the error MD5 file check, something like that.
I then reboot to recovery again and tried to install "JmzM4StockRootedOdex-WWE 1.22.401.1" also a zip file, and again the same error MD5 file check.
Then the phone in fastboot mode remained and could not boot the system. So I had to do a restore of backup I in which they made before I got into flash kernel, and roma.
Here is also my fastboot getvar all the info.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.22.0000
INFOversion-baseband: 1.28.40e.00.24
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.14.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid:
INFOproduct: m4_ul
INFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4316mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.124s
C:\ADB>
Can someone tell me what is the solution for my problem, I just want my device S-off to try Sieempi method of unlocking, to see if it works. Thx!

Nothing? I try a couple thing more. I think its problem in the file I downloaded, and download a MD5 checker, and says thats ok. Then I save a md5 file from Md5 checker @ the same folder like zip file, and run again from recovery, and now got another error, you can see image.
IMG]http://tapatalk.imageshack.com/v2/14/10/08/624d91145625043f190be1d67997e6a2.jpg[/IMG]
Revone method doesnt work i got error -2. And boot intro the bootloader and stil s-on.

Please lock theard, phone was smashed. I lost nerves!

Hi Errornt
pardon if i only post today!
had your same situation and now i've solved! the solution? just flash a new kernel! i've used xXminiWHOOPERxX Kernel and now.... i'm s-off
so, unlock bootloader, install custom recovery and root, flash an insecure kernel with fastboot method and run rumrunner
that's all
i'm sorry for your smashed phone
br
ss