[HTC One S] evoarcher:
Bootloops on 10.2 - Nightlies

Hi Guys,

I hope this helps a little. I have not had this issue with bootloops for a while. Here is what I do when I update my HTC One S (s-on).

I am not an expert, but I think that it is quite strange (unless my phone memory is busted) that I find file systems errors on the p33 partition every time I flash a new version of the nightlies (checking with dmesg | grep mmcb...)

1) Download the zip file and put it in your default folder - then extract from the zip file the boot.img, put it in your default folder.

2) copy the .zip file and the MD5 file in your phone sdcard - I copy/paste the MD5 code from the download site into a text file with notepad and save it with same name as the nighly zip file + .md5. For instance :

adb push cm-10.2-20131110-NIGHTLY-ville.zip /sdcard/CM10-2/

adb push cm-10.2-20131110-NIGHTLY-ville.zip.md5 /sdcard/CM10-2/

3) reboot in bootloader/fastboot with : adb reboot bootloader

4) once the phone is in fastboot-usb : fastboot flash boot boot.img ( you should see a green line raising on the right side of the phone screen while it flashes).

5) using the volume and power keys, reboot into recovery (TWRP) - (press power button while "fastboot usb" is in red (selected) then power down to select the "recovery" option in green.

6) from there wipe the cache, dalvik cache, system -

If you don't have relevant data and don't mind re-entering all the identification data ... accounts etc. and have a good recent backup that you can restore appropriately - you can also wipe the "data" section (I try not to do that because it is a pain to re-enter/re-load everything even if you have a good backup). Yet, if the bootloop persists, I would definitely try to wipe the data in this process for a second attempt. In my experience, you can ruin a good installation by restoring data from TitaniumBackup that is in "red" meaning that it's structure may interfere with the new kernel/software as it is system data).

7) Install the new .zip file, gapps, superuser and superuser update v. 1.43, (for me version 1.65 of SuperSu doesn't seem to work).

cm-10.2-20131110-NIGHTLY-ville.zip

gapps-jb-20130813-signed.zip

SuperSU.zip

UPDATE-SuperSU-v1.43.zip

8) When you are done, wipe dalvik cache and cache.

9) I have noticed that after flashing I get file system errors for blocks 33 and 35, so, before rebooting enter the following commands making sure the partitions are dismounted. (You can dismount the partitions via TWRP going to mount and uncheck all system, cache and data (this will unmount them)

\System is on p33, \cache in p34, and \data is on p35.

while in recovery you should be able to "adb shell" and issue these commands:

C:\Users\cq>adb devices

List of devices attached

HT26XXXXXXX recovery

C:\Users\cq>adb shell

~ # ←[6n

~ # ←[6nmount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

/dev/block/mmcblk0p34 on /cache type ext4 (rw,relatime,data=ordered)

/dev/block/mmcblk0p33 on /system type ext4 (rw,relatime,data=ordered)

/dev/block/mmcblk0p35 on /data type ext4 (rw,relatime,data=ordered)

In this case above the three partitions are mounted so the commands here below will not work until you uncheck the boxes in the TWRP mount function

for syste, cache, data - after unchecking, if you issue the "mount" command again the partitions will not show as mounted.

e2fsck -pvf /dev/block/mmcblk0p33

e2fsck -pvf /dev/block/mmcblk0p34

e2fsck -pvf /dev/block/mmcblk0p35

Leave the partitions unmounted after the checks above and issue a "poweroff" command (better) or reboot.

If you powered-off then hit the power button to start after waiting for 10 seconds.

This "method" doesn't work all the times, but it has allowed me to stay boot-loop free for a while.

Really hope this helps.

CQ