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.
Hi guys.
I have been trying to root my HTC One S for hours now without any luck.
I have been using this guide,(http://forum.xda-developers.com/showthread.php?t=1583427) and have managed to get all the way to the last step in the "recovery"-section.
But when I try to flash the recovery, this is what I get:
c:\fastboot>fastboot recovery clockwork-touch.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
How can this be?
Thanks in advance for your help
Type the following command
c:\fastboot>fastboot recovery recovery clockwork-touch.img
Thanks for your reply, frazzeld.
It didn't work. Sorry. Still the same text coming up.
Maybe there is something wrong with have a managed my fastboot-folder.
Because I am a new member I cant post a picture of my folder :/
But it is set up like this:
(folder)add-ons
(Folder)platforms
Folder)tools
adb
adbWinapi.dll
AVD Manager
clockwork-touch.img
fastboot.exe
SDK Manager
SDK Readme
Unlock-code
Never mind.
It worked after all. Don't know what I did wrong the first 50 times.
Thank you
which clockwork are you trying to install?
Edit: I see you've sorted it now
Are you in fastboot mode? Also the recovery image has to be in the same folder as fastboot.exe is.
To point to the correct folder its "cd"
e.g.
cd c:\fastboot
And the correct command is;
fastboot flash recovery name_of_the_recovery.img
Thats all i can see from what you've posted
edit: too slowwww, glad you got it sorted
Big_Den said:
...
fastboot flash recovery name_of_the_recovery.img
...
Click to expand...
Click to collapse
This.
Just in case someone else stumbles across this thread.
Unconn said:
This.
Just in case someone else stumbles across this thread.
Click to expand...
Click to collapse
From the proper directory. It's not C:\ for everyone... Some have their fastboot.exe in C:\Android and some even C:\Android\platform-tools for example.
Point being, make sure u know where your fastboot.exe is located
Sent from my HTC VLE_U using xda premium
Just over half a year ago (January 2012) I have unlocked my sensation with rev. h-boot, installed 4 ext recovery and flashed Android Revolution. I've been using the phone in a number of countries since, with no problems. A couple of days (9/08) back, when I returned to the UK my sensation started behaving as if it had been IMEI blocked, and after fiddling around for a while I discovered that the IMEI android reports is different that the one printed under the battery/on the box. Given it doesn't seem I have any backup (bear in mind it worked like a charm for past half a year) is there any way of repairing that corrupt IMEI? Is it (so naive) stored in more than one place on the phone so I could access the factory IMEI or anything of that sort? I've tried using the fastboot oem writeimei command, as well as the root terminal emulator command that have been posted on these forums a number of times but neither of them worked.
Go to shop where you get it
Sent from my HTC Sensation using xda premium
From the dialler which one does *#06# report ?
Your fastboot might be neutered (can't issue write commands properly) if you upgraded the HBOOT using the universal firmware packages posted in the Dev section, even though it is still s-off.
When you boot into the bootloader, does it say *** LOCKED *** or Revolutionary in the very top left? If it's *** LOCKED ***, you need to reinstall the Revolutionary HBOOT.
If it says Revolutionary, issue the following commands from Windows to fix your IMEI:
Code:
fastboot getvar imei
[shows old imei]
fastboot oem writeimei 123456789012345
fastboot reboot-bootloader
fastboot getvar imei
[shows new imei]
krazykipa said:
Your fastboot might be neutered (can't issue write commands properly) if you upgraded the HBOOT using the universal firmware packages posted in the Dev section, even though it is still s-off.
When you boot into the bootloader, does it say *** LOCKED *** or Revolutionary in the very top left? If it's *** LOCKED ***, you need to reinstall the Revolutionary HBOOT.
If it says Revolutionary, issue the following commands from Windows to fix your IMEI:
Code:
fastboot getvar imei
[shows old imei]
fastboot oem writeimei 123456789012345
fastboot reboot-bootloader
fastboot getvar imei
[shows new imei]
Click to expand...
Click to collapse
Is this not a little illegal ?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
*shrugs* just suggesting a solution, maybe using the phone as he has it right now is illegal... !
This works it is ilegal, kinda.
Sent from my HTC Sensation Z710e using xda premium
not really
I dont believe its illegal if he's repairing/restoring IMEI back to original, if he/she's "changing" a valid IMEI then yes.
My fastboot doesn't give the option of the command ' writeimei' .
Only:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
freelanc45 said:
My fastboot doesn't give the option of the command ' writeimei' .
Only:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Click to expand...
Click to collapse
It needs a custom fastboot binary (Revolutionary) and you are (technically) legally limited to restoring a damaged IMEI on your own consent. As explained, creating a false IMEI is illegal. Just a heads-up.
I'm having some problems here. I tried to get superCID but strangely the CID never changes. Here's the commands. They all looked like they worked but the CID didn't change. (This is after I did the HEX editor and pushed the file back onto the SD card.)
Since that didn't work I tried rumrunners s-off script but that said it couldn't work with my ROM Beanstalk 4.4.2 or kernel.
HTC One S, Rooted, Beanstalk 4.4.2
S4 1.5Ghz Dual Core
HBOOT - 2.15
Kernel 3.4.76-ge75b9c0 phoenixita
Baseband 1.13.50.05........
Code:
C:\fastboot>adb shell
[email protected]:/ # su
su
[email protected]:/ # ls -l /sdcard/mmcblk0p4MOD
ls -l /sdcard/mmcblk0p4MOD
-rwxrwx--- root sdcard_r 1024 2014-02-23 13:32 mmcblk0p4MOD
[email protected]:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.015 secs (68266 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s
Wrong section. Next time Q&A.
Switch for a moment to a sense 2.15 Rom and try facepalm S-off.
fonnae said:
I'm having some problems here. I tried to get superCID but strangely the CID never changes. Here's the commands. They all looked like they worked but the CID didn't change. (This is after I did the HEX editor and pushed the file back onto the SD card.)
Since that didn't work I tried rumrunners s-off script but that said it couldn't work with my ROM Beanstalk 4.4.2 or kernel.
HTC One S, Rooted, Beanstalk 4.4.2
S4 1.5Ghz Dual Core
HBOOT - 2.15
Kernel 3.4.76-ge75b9c0 phoenixita
Baseband 1.13.50.05........
Code:
C:\fastboot>adb shell
[email protected]:/ # su
su
[email protected]:/ # ls -l /sdcard/mmcblk0p4MOD
ls -l /sdcard/mmcblk0p4MOD
-rwxrwx--- root sdcard_r 1024 2014-02-23 13:32 mmcblk0p4MOD
[email protected]:/ # dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes transferred in 0.015 secs (68266 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ # exit
exit
C:\fastboot>adb reboot bootloader
C:\fastboot>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
Try rumrunner s-off and when your finished with that reboot to bootloader then go into fastboot, open up a command window and type "fastboot oem writecid 11111111" (without quotes)
Did you edit that file via hex editor?
EDIT: oh sorry... :cyclops:
dd98 said:
Try rumrunner s-off and when your finished with that reboot to bootloader then go into fastboot, open up a command window and type "fastboot oem writecid 11111111" (without quotes)
Click to expand...
Click to collapse
Unfortunately, I already tried Rumrunner. It didnt' work and mentioned something about the "cap is on too tight" and try a custom kernel or different ROM.
I also tried Firewater and after typing 'Yes' it just exited.
I'm pretty much out of ideas here.
fonnae said:
Unfortunately, I already tried Rumrunner. It didnt' work and mentioned something about the "cap is on too tight" and try a custom kernel or different ROM.
I also tried Firewater and after typing 'Yes' it just exited.
I'm pretty much out of ideas here.
Click to expand...
Click to collapse
Try moonshine
Sent from my SPH-L710 using Nightmare Rom
Thread Moved to Q&A, Help & Troubleshooting
As per the Forum Rules (which you agreed to when you signed up to XDA), development sections are only for development work to be posted, NOT for questions.
Please remember that in future so we don't have a repeat situation.
Regards,
- KidCarter93
Forum Moderator
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