yashsingh1/xdaforums huggingface dataset:
[HTC One S] nashwing:
No luck with 1.84 ruu. Trying the EU JB 45 RUU now..

unlocked bootloader

S-OFF

only doing fastboot then RUU, nothing else

will report back, thanks!
[HTC One S] nashwing:
No luck with the EU JB 45 RUU - getting image error 158
[HTC One S] real187:
Image error? Have you tried another sourse file?

Correct cid?

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] nashwing:
I noticed something strange when I got back to my office this morning.

It appears that I used the PJ4010000 zip for the S-OFF on my PJ4011000 model

Strangely it S-Off'd, or appears to be according to the bootloader.

BUT, I don't know if it really is, because I can't do a 'fastboot flash radio radio.img' - it says remote not allowed (as if it was S-ON)

Would flashing the wrong zip orginally may have messed something up so that it won't boot fully now on after the RUU?

(I had no problem when I S-OFF'd and continuing to use the ROM I had installed...)

Oh, and do I need to set the CID for the EU JB RUU? (It's currently SCID [11111111])
[HTC One S] nashwing:
Adding to the list:

I did manage to flash the EU JB RUU with no problems, however, same results on boot - goes to lock screen, unlock and says "preparing phone storage.." with the white HTC background, then bootloops

I went in to the stock recovery for giggles, and noticed it is saying "can't mount sdcard" about 5 times...

So, I did the clear storage and factory reset in the bootloader, still no luck...
[HTC One S] joemanbui:
Can anyone help here too? I am having the exact same problem. I successfully flashed the tmous ics RUU and was able to unlock bootloader again. But this same message shows up with every rom that I try. Just says preparing phone storage and stays on the white htc screen.
[HTC One S] nashwing:
Exact same problem... I can't figure it out. I'm piecing pieces of the rom back in to see if it helps, but something is awry.

Are you S-OFF'd?
[HTC One S] real187:
You still cant fastboot the radio like on older devices because of the hboot. Need a eng hboot. Use the tempradio installer in dev section.

Change to a HTC cid. Like HTC__001 (always 8 digits) however supercid also works. But don't do ota on that cid!!!

But is your mid stil original?

Check in fastboot. Fastboot getvar all

Does a custom Rom work without the problems?

Try ruu after ful formatting/cleaning of all mounts device with custom recovery.

How about the image error?

You readed this tread http://xdaforums.com/showthread.php?t=1630459

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] joemanbui:
yeah. I'm S-off. Keep this updated if you find a fix please! Btw, how did you get the JB RUU to work? I'm also getting error 158.
[HTC One S] AKToronto:
Heres my thread on SD Card issues. Its a bit more comprehensive http://xdaforums.com/showthread.php?t=2086156&highlight=sd%A0card
[HTC One S] joemanbui:
Hey thanks for the response. I think the issue is the sd card. However, everytime i try to clear storage or factory reset, it does not detect the sd card and nothingg appears to happen. Custom Roms still boot up after selecting those options. Upon trying to use the adb method, my computer does not detect anything when I am in twrp. Is it supposed to show up?

EDIT: okay i was able to get into adb. but i keep getting the message /data/local/tmp/busybox: not found. I pushed the busybox file to that directory.
[HTC One S] nashwing:
I've done this, flashing a new radio from recovery doesn't seem to have any affect. Still stuck after swiping the unlock ring on saying "Preparing Phone Storage" on a white HTC background.

I think you meant imei?, yes, it's good

Nope, all ROMs I've tried (At least 3 ICS and 3 JB) still result in same as above...

image error gone after setting SCID - after RUU, same results as above

Have read and followed, flashed stock recover, clear storage, factory reset, flashed twrp, sdcard is fine. (only after RUU does it 'disappear') your method makes it visible and formatable again, and I can flash a custom rom off it (once copied over from windows on mount from twrp) and when the booting fails, and I go back in to recovery, it's there, and all the data (like .android.sec and TWRP, and the ROM zip) are all there...

Thanks!
[HTC One S] nashwing:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.09.0000

(bootloader) version-baseband: 0.16.31501S.16_2

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.84.531.2

(bootloader) serialno: HT24XW4[XXXXXX]

(bootloader) imei: [XXXXXXXX] (correct)

(bootloader) product: vle

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ4011000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 4125mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: e964c535

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[HTC One S] joemanbui:
I seriously have all the same problems as you. the sdcard works fine until booting the actual rom, then it becomes corrupted or something.
[HTC One S] nashwing:
So, booting the rom (after fixing sdcard) results in same problem

Rebooting back to recovery shows the sdcard is good

Mounting it from recovery shows:

.android_secure (empty)

LOST.DIR (empty)

TRRP (containing .twrps and .version)

SO the sdcard is there. it appears that if you let the ROM bootloop, then the card becomes corrupt.

Sometimes when booting, I'll see the 'process system' not responding error wait or ok to close...

Sometimes when booting, I'll see just a black screen with the notification bar showing battery and signal (not swipable)

Sometimes when booting, it will just bootloop

In all instances, it will eventually reboot itself (IE, it will not stay running)

(Just trying to provide as much info as possible)
[HTC One S] nashwing:
Out of curriousity, when you S-OFF'd, do you know if you used the correct boot image? (PJ04011000)

I know I didn't, but even still, it -was- running fine after I did S-OFF.
[HTC One S] nashwing:
More Info:

I don't see any drives showing up in bootloader or fastboot

In recovery, I see both drives show up, but it's "Windows can't access it' or insert disc

I can mount /sdcard and it shows up with the contents...

I can flash rom's fine off the sdcard, but still no go on boot...

nothing in the recovery.log indicating any errors

When booted, I see both drives show up in Windows, but both are inaccessible

I also see the usb connection icon show up on the notification bar
[HTC One S] joemanbui:
same here. does not show up in fastboot but mounting in recovery works just fine. i've been reading around and it's gotta be something about the partitions? or i might be totally off.

CWM recovery shows the following

I: checking for extendedcommand...

I: skipping check for extendedcommand... file not found

I: Can't format unknown volume : /external_sd

I: Can't format unknown volume : /emmc

Partitioning SD Card... please wait... fail1

checking script requirements...

err: you are not using parted v1.8.8.1.179-aef3!

Done!

fixing permissions...

sh: fix_permissions: not found

Done!
[HTC One S] joemanbui:
I used PJ4010000 zip. I guess I'm in the same boat as you. That was the file listed under the S-off instructions. I assumed it to be correct.

a user here had the same problem and flashing RUU worked apparently.

http://xdaforums.com/showthread.php?t=1710781

is it possible to return to S-ON, stock recovery, lock bootloader then flash RUU? i'm afraid that if it doesnt work then we cant go back to s-off right?
[HTC One S] nashwing:
Okay, I've kinda confirmed that something is happening to the sdcard on boot after a while... stock recovery will not see it after a boot, but twrp will for some reason

So, we either have a recovery problem, a fastboot problem, or some partition problem.

I know we can go S-ON easily enough, but I'm afraid to do so at the moment, because this is what is allowing easy cid changes, and ruu loads, etc. - but I'm not so sure that it's required

As far as going back to S-OFF, I don't see why we couldn't once this issue is resolved (IF it's resolved)

I did manage to get ADB to see my device during one boot session, and unfortunately, couldn't see anything as it was scrolling through wifi networks over and over... I haven't been able to replicate whatever I did to get ADB to see it again...

I also noticed that I have no adb access in fastboot or bootloader (not sure if I should) - and no adb access in stock recovery (not sure if I should)

And, of course, no drives showing up in windows in fastboot/bootloader/recovery
[HTC One S] nashwing:
@ joemanbui - by any chance does your windows username have a space in it?
[HTC One S] real187:
I think partition/hardware problem.

You can restore, but when used or corrupts.

Did you try format Sd partition on custom recovery before flash/use

Verstuurd van mijn HTC One S met Tapatalk
[HTC One S] nashwing:
Yes, sdcard is fine in custom recovery (twrp and cwmr) even after booting... (mounts fine and content is there)

If stock recovery is loaded, it appears not to be fine.
[HTC One S] joemanbui:
There is no space in my windows username. Also the only way I was able to get access through adb was in cwm recovery. I was able to partition the sd card using the busybox method posted earlier but I keep getting an error in the log. I'm pretty sure something is wrong with the sd card. Does anything happen when you flash stock recovery and select "clear storage" from the bootloader? Whenever I do it, it's as if nothing happens and just boots to the original Rom or RUU that I flashed prior to it.

---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------

Yup tried that with cwm recovery, twrp, philz touch, even gparted and nothing seems to work.
[HTC One S] nashwing:
okay, to flash the EU JB RUU you have to be on an hboot of 2.0.9 or higher as the rom.zip is encrypted (I flashed the firmware.zip from the tmob jb ota) then did the eu jb ruu with no prob)

once I get that RUU done, I can then format the sdcard in twrp by 'usb mount' in the mount menu and I can format it via windows

then I can reboot into ROM and same problem, however, I can go back to TWRP and still see the sdcard along with all the contents of what appears to be a correctly booted rom... IE: the sdcard contains all the directories the ROM creates, like android, dcim, ringtones, etc...

however, still no go on boot... same problem.
[HTC One S] joemanbui:
ahhh someone help us! haha. Yeah I also flashed the eu jb ruu earlier today using the hapoon's decrypted rom.zip but no go either. What other options do we have at this point?
[HTC One S] nashwing:
sit back and cry I suppose...

Hopefully someone will come along

Oh, do you have a link for a fastboot flashable cwm recovery? Mine is at work, and I can't find one for some reason, probably too tired since I've been trying to fix this for two days straight
[HTC One S] joemanbui:
No problem. I've also spent way too much time trying to fix this. This should be the direct link to the cwm touch recovery.

http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-ville.img

And the cwm recovery non touch just in case.

http://www.clockworkmod.com/rommanager

This is my phone info if it helps.

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.14.0004

(bootloader) version-baseband: 1.15.50.05.29

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: xxxxxxxxxx

(bootloader) imei: xxxxxxxxxxxxx

(bootloader) product: vle

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ4011000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4174mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 8b9e2080

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.065s
[HTC One S] joemanbui:
Also by any chance, were you running a custom kernel before all this happened?
[HTC One S] nashwing:
No, all stock kernels on this one. (I believe) The last rom I was running prior to the 'crash' was the new T-Mob JB stock.
[HTC One S] nashwing:
I wonder if we could get some images of each of the pertinent partitions from a working HOS and dd them over to our partitions.

I think we have some sort of partition corruption (content, not layout)
[HTC One S] nashwing:
- Deleted -
[HTC One S] nashwing:
Noticed when manually flashing the RUU rom.zip that the following had signature verify failures

sbl1-1 OK

sbl1-2 FAILED

sbl1-3 FAILED

Not sure if this means anything, but according to the flash, these are the only things 'FAILED'
[HTC One S] joemanbui:
Yea I was able to partition it this way only once. Now it gives me an error message whenever I try. Says the directory does not exist. And I'm not really sure what your second post about flashing the ruu rom zip means. Seems like your onto something though. I've been asking around everywhere on the forums and most people are saying we bricked from s-off. I don't believe it though. It's gotta be something with these partitions.
[HTC One S] nashwing:
I think we'll see more bricks as folks flash that firmware.zip for the t-mobile JB rom

I think it's a combination of early S-OFF folks using the wrong model zip (as you stated, that was the only one there originally) and something in the the new firmware caused an issue.

Regardless of what TWRP and CWMR state, the stock recovery is unable to mount the sdcard after you boot... so something is corrupting the sdcard on boot. -OR- the firmware/rom/stock recovery is seeing the sdcard somewhere else than where TWRP and CWMR are seeing it. IE: /dev/block/mmcblk0p36 when in TWRP or CWMR - don't know in stock recovery, cause we can't ADB in to see... :confused: :crying:
[HTC One S] joemanbui:
Ah... So do you think its official? Our phones are bricked? What can you do with a bricked phone? Sell it?
[HTC One S] nashwing:
It's official that the sdcard is the issue - even clearing storage and factory reset (which has worked for others on 'unable to mound sdcard') doesn't really 'fix' it for us.

Here is the scenario for my 'official' response:

1) Flash RUU (both EU JB and TMOB US ICS (many versions))

* on other trials

- 1) Tried to manually flash firmware.zip compiled from other RUU's as well

2) Boot in to (stock) recovery - errors out on E:failed to mount /sdcard (No such file or directory)

3) Boot in to bootloader - clear storage and factory reset

* also done on another trial

- 3a) boot in to stock recovery - still errors out on E:failed to mount /sdcard (No such file or directory)

- 3b) boot back to bootloader

4) Flash custom recovery

5) Boot to custom recovery, mount sdcard for usb storage - windows will prompt to format it

6) Custom recovery 'sees' the sdcard find after this - and you can copy things to it fine

* also done on another trial

- 6a) boot back to bootloader

- 6b) flash stock recovery

- 6c) boot in to stock recovery - still errors out on E:failed to mount /sdcard (No such file or directory)

- 6d) boot back to bootloader

7) Boot to ROM - fails to finish boot with error "Preparing phone storage..."

8) Boot back to custom recovery - sdcard is fine, and files are still there no problem

9) Boot to bootloader

10) Flash stock recovery

11) Boot to stock recovery - errors out on E:failed to mount /sdcard (No such file or directory)

12) Boot to bootloader

13) Flash custom recovery

14) Boot to custom recovery - sdcard is fine and files you put previously are still there...

15) Boot to ROM - fails to finish boot with error "Preparing phone storage..."

So, to answer the question, yes we are 'bricked' - can it be fixed? I don't know:

* perhaps with a new TMOB JB RUU?

* perhaps by copying over 'good' partitions to our 'bad' partitions?

* perhaps someone smarter than me knows?

* perhaps removing s-off will help? I don't know as I don't see how this could have 'bricked' us

* ...

* profit?

:crying:
[HTC One S] joemanbui:
someone needs to respond to this! you pretty much summed up our thread so it should be easier to diagnose the problem. I've been trying to contact a lot of people about this. I'll definitely refer them to your post.
[HTC One S] nashwing:
Did notice something I didn't catch before.

While in stock recovery, if I select update from internal_sdcard I see the contents of what twrp and cwmr show for /sdcard (all the files I placed on the 'sdcard' within those recoveries...)

It appears as if /dev/block/mmcblk0p36 is being mounted on /internal_sdcard in the stock recovery - perhaps this is correct??? I think it may be... but then where is 'sdcard' and why can't it mount?

I sure hope someone chimes in here who is smarter than I am...

(PS: I also was able to apply the update.zip I put there as well from stock recovery, it installed no probs, but same boot issue)
[HTC One S] nashwing:
I did manage to pull a logcat while booting last night, I'll be studying it today to see if I can see anything out of the ordinary. (This was after RUU'ing the EU JB RUU again.)
[HTC One S] joemanbui:
Sounds good. If anything, I could send my phone in for the jtag repair and see if that works.
[HTC One S] nashwing:
So many errors in the logcat, but nothing at all that I can see that would be specific to a problem with the device. The errors are mostly permission type errors

mostly like these

W/PackageManager( 557): Unknown permission com.htc.permission.SOCIAL_NETWORK in package com.android.phone

W/PackageManager( 557): Unknown permission com.htc.socialnetwork.permission.useprovider in package com.android.phone

W/PackageManager( 557): Unknown permission com.kddi.android.iida.iidahome.permission.BUBBLE_NOTIFICATION in package com.android.phone

W/PackageManager( 557): Unknown permission com.htc.fmservice.permission.FMRadioService in package com.htc.fm

W/PackageManager( 557): Unknown permission com.htc.widget.people.permission.SETTINGS in package com.htc.idlescreen.people

W/PackageManager( 557): Not granting permission android.permission.DEVICE_POWER to package com.htc.syncagent (protectionLevel=2 flags=0x83e45)

This is the vold mount of sdcard

I/Vold ( 241): Vold 2.1 (the revenge) firing up

I/Vold ( 241): Set handling read only 0

I/Vold ( 241): Vold : mount mmcblk0p36,and the partition number is 36

D/Vold ( 241): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)

D/Vold ( 241): Volume usb state changing -1 (Initializing) -> 0 (No-Media)

And a bunch of these at the beginning

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_NAME' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_STATE' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_NAME' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_STATE' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_NAME' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_STATE' not found

E/NetlinkEvent( 241): NetlinkEvent::FindParam(): Parameter 'SWITCH_NAME' not found

this too?

W/WindowManager( 557): ***** BOOT TIMEOUT: forcing display enabled

Nothing else really at all
[HTC One S] nashwing:
found these in another logcat from another RUU:

I/Vold ( 183): Vold 2.1 (the revenge) firing up
I/Vold ( 183): Set handling read only 0
I/Vold ( 183): Vold : mount mmcblk0p36,and the partition number is 36
D/Vold ( 183): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
W/VoldDirectVolume( 183): device name = mmcblk0
D/Vold ( 183): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 183): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)
W/Vold ( 183): Duplicate state (1)

W/EntropyService( 392): unable to load initial entropy (first boot?)
W/EntropyService( 392): java.io.FileNotFoundException: /data/system/entropy.dat: open failed: ENOENT (No such file or directory)

This looks suspicious

I/MountService( 392): doMountVolume: Mouting /mnt/sdcard
D/VoldCmdListener( 183): volume mount_encrypted /mnt/sdcard {} off
I/Vold ( 183): /dev/block/vold/179:36 being considered for volume sdcard
D/Vold ( 183): Volume sdcard state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/MountService( 392): onEvent:: raw= 605 Volume sdcard /mnt/sdcard state changed from 1 (Idle-Unmounted) to 3 (Checking) cooked = 605 Volume sdcard /mnt/sdcard state changed from 1 (Idle-Unmounted) to 3 (Checking)
I/MountService( 392): notifyVolumeStateChanged::unmounted
I/MountService( 392): updating volume state checking
D/MountService( 392): volume state changed for /mnt/sdcard (unmounted -> checking)
D/Vold ( 183): Bad container magic number (619058eb), expected c0defeed
[HTC One S] nashwing:
Well, nothing in the logcat is pointing to an issue, and nothing I can find to figure out more details.

I'm calling it, time of death: 15:54.
[HTC One S] joemanbui:
haha good work though. hopefully a jtag repair can revive our phones.
[HTC One S] nashwing:
I hope so.

You know, this is the FIRST time, (in 7 years,) that I've ever bricked a phone. The sad part is, I don't even know why or what bricked it!

It was either, the S-OFF or the TMOB US JB update (or some combination thereof) - as I didn't have any problems after the S-OFF with old ROM(s) prior to flashing the JB rom/firmware. And, I haven't heard of any bricks from the TMO JB ROM.

It wasn't until I flashed the firmware.zip that I think it went bonkers on me.
[HTC One S] nashwing:
Well, got the official RUU off htc for the Tmob JB. https://support.htc.com/en-us/080-HTC_One_S_T-Mobile/Software_Updates/HTC_One_S%E2%84%A2_for_T-MOBILE_ROM_Update_%7C_4.19.2013

Still no go! Same results (across the board) same symptoms, same thing, brick!

So, I'm guessing the partition tables, or a partition is fubar'd.

JTAG or bust! :mad:
[HTC One S] joemanbui:
hey could you link me to the tmobile ota? I need the firmware.zip
[HTC One S] nashwing:
Don't have a link handy with me (on travel at the moment) but rom1.zip is the firmware, and rom2.zip is the rom itself within the RUU I posted last night.

Edit: found it:

http://fotadl.htc.com/OTA_Ville_U_J....30.50.08L_release_3095152gf3d5egc1kw6ovn.zip
[HTC One S] joemanbui:
hey i found something new. if you flash the ruu here http://xdaforums.com/showthread.php?t=2279588

then use clear storage, factory reset in bootloader

flash cwm recovery

and flash any non sense rom afterwards, it will boot up into the phone for a good 2-3 minutes, then restarts on its own.

---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------

sense roms still get stuck on the preparing phone storage message though
[HTC One S] nashwing:
Pushing back a good mmcblk0p23 and mmcblk0p4 didn't fix it.
[HTC One S] nashwing:
Ran a logcat on your above scenario from boot-to-reboot.

Only thing I can ascertain is a ton of QMI_FW and QMI_RIL and QC-NETMGR errors - tons of them.

Samples:

D/QMI_FW ( 121): QCSI: Received REMOVE_CLIENT cmd for 00000000:00000007

D/QC-NETMGR( 131): netmgr_kif_ifioctl_open_port() failed for rmnet0
D/QC-NETMGR( 131): ifioctl: open port failed: (19)No such device

I/QMI-RIL ( 124): [main] qcril_qmi_init_core_client_handles: Trying qmi_client_init() for (0-referenced) try # 3 port[rmnet0]

I/QMI-RIL ( 124): [main] qcril_qmi_client_init: function entry
I/QMI-RIL ( 124): [main] qcril_qmi_client_init: Trying qmi_init() for (0-referenced) try # 0

D/QMI_FW ( 543): QCCI: Received NEW_SERVER cmd for 00000013:00000101
D/QMI_FW ( 141): QCCI: Received NEW_SERVER cmd for 00000013:00000101
[HTC One S] bombina:
I pretty much have the same error as you. The problem seems to have occurred after flashing the firmware for the TMOUS OTA. You pretty much described exactly my issues. Have you made any groundway on fixing this issue?