Database Info

NeedHelp:screwed up my g1,cant finished boot

It just loop on the green sparkling robot.
What I did is just modifying TC5-RC8 update.zip with test key, and do the update as normal.
I've been using RC8 for couple days since it's been released and no problem.
After this problem occurd, I've tried to re-flash it to the origianl TC5-RC8 update.zip which released by JesusFreke. BUT the problem still.
My guess is flash recovery.img when booting due to some hardware issues.
Need Your Help.

I finally do a update to and old version of my modified TC5-RC8, the phone booted.
The bad news is I do recovered it to factory mode, so I need to login to Google account again.
Unfortunately, when I finished the Login, and ready to press "Finish setup" and move(dont know how to express in English that movement, the screen is open, what I do is close it so it covers the keyboard) the the screen, and exception occured: "com.google.process.gapps has stopped..."
Don't know whether google will check its own sign or not, im using the test key.
And, I can do adb shell, this is the ps:
# ps
ps
USER PID PPID VSIZE RSS WCHAN PC NAME
root 1 0 264 176 c00a5cd0 0000c36c S /init
root 2 0 0 0 c005bd28 00000000 S kthreadd
root 3 2 0 0 c004c12c 00000000 S ksoftirqd/0
root 4 2 0 0 c006e978 00000000 S watchdog/0
root 5 2 0 0 c0058b40 00000000 S events/0
root 6 2 0 0 c0058b40 00000000 S khelper
root 7 2 0 0 c0182558 00000000 S suspend/0
root 8 2 0 0 c0058b40 00000000 S kblockd/0
root 9 2 0 0 c0058b40 00000000 S kmmcd
root 10 2 0 0 c0058b40 00000000 S btaddconn
root 11 2 0 0 c0058b40 00000000 S btdelconn
root 12 2 0 0 c0058b40 00000000 S qmi
root 13 2 0 0 c003263c 00000000 D rpcrouter
root 14 2 0 0 c0058b40 00000000 S detection/0
root 15 2 0 0 c0032fb4 00000000 S krpcserversd
root 16 2 0 0 c007a964 00000000 S pdflush
root 17 2 0 0 c007a964 00000000 S pdflush
root 18 2 0 0 c007e8b4 00000000 S kswapd0
root 19 2 0 0 c0058b40 00000000 S aio/0
root 20 2 0 0 c0032fb4 00000000 S kadspd
root 21 2 0 0 c0058b40 00000000 S panel_on/0
root 22 2 0 0 c0151ff8 00000000 S mtdblockd
root 23 2 0 0 c0157d84 00000000 S USB mass_storag
root 24 2 0 0 c0058b40 00000000 S synaptics_wq
root 25 2 0 0 c020dfc0 00000000 S krfcommd
system 26 1 796 276 c0189f10 afe0b74c S /system/bin/servicemanager
root 27 1 1828 336 ffffffff afe0b50c S /system/bin/mountd
root 28 1 652 252 c0196e68 afe0c0bc S /system/bin/debuggerd
radio 29 1 7720 936 ffffffff afe0bdbc S /system/bin/rild
media 31 1 17304 3420 ffffffff afe0b74c S /system/bin/mediaserver
bluetooth 33 1 1164 716 c00a5cd0 afe0c69c S /system/bin/dbus-daemon
root 34 1 788 292 c01fb090 afe0b50c S /system/bin/installd
compass 36 1 1304 572 c0169014 afe0b74c S /system/bin/akmd
root 37 1 3324 148 ffffffff 0000e664 S /sbin/adbd
root 43 2 0 0 c01751d0 00000000 S mmcqd
root 359 1 66044 19428 c00a62ec afe0b874 S zygote
system 360 359 183032 25080 ffffffff afe0b74c S system_server
radio 392 359 106732 18708 ffffffff afe0c824 S com.android.phone
app_11 409 359 88092 12244 ffffffff afe0c824 S com.android.mms
app_4 430 359 87436 10576 ffffffff afe0c824 S com.google.android.talk
app_12 441 359 87988 11940 ffffffff afe0c824 S android.process.media
app_14 444 359 90068 11992 ffffffff afe0c824 S android.process.acore
app_18 463 359 93428 14788 ffffffff afe0c824 S com.android.calendar
app_22 475 359 87120 11456 ffffffff afe0c824 S com.android.alarmclock
app_16 487 359 87472 11300 ffffffff afe0c824 S com.google.android.gm
app_8 582 359 106360 15604 ffffffff afe0c824 S com.android.setupwizard
app_0 608 359 94940 15916 ffffffff afe0c824 S com.google.process.gapps
root 645 2 0 0 c0032dc8 00000000 D audmgr_rpc
root 687 37 724 320 c0049a2c afe0c4cc S /system/bin/sh
root 689 687 868 328 00000000 afe0b50c R ps
#
Click to expand...
Click to collapse

I do it again, said "The setup wizzard stopped unexpectly"

[Q] Android 4.0.4 and high cpu usage of system_server with autorotate on

Hi,
i have nexus S with IMM76D_deodexed. I had preciously 4.0.3, then 4.0.4 - IMM26. Now IMM76D, CWM.
With IMM76D I hoped all will be solved, but not.
before updating to IMM76D I did:
back to factory reset
format SD card
clean Dalvik
clean /system except /boot
Now i think, I'm only one, who has infamous autotate high cpu usage bug
- without autorotate (cpu usage is normal):
Code:
top -m 100 -d 1 -n 1 | head -20
User 0%, System 3%, IOW 0%, IRQ 0%
User 0 + Nice 0 + Sys 4 + Idle 99 + IOW 0 + IRQ 0 + SIRQ 0 = 103
PID PR CPU% S #THR VSS RSS PCY UID Name
11891 0 7% R 1 1000K 396K bg root top
11867 0 0% S 1 0K 0K fg root kworker/0:0
11814 0 0% S 11 273628K 23708K bg app_70 com.google.android.maps.mytracks
132 0 0% S 81 369556K 45464K fg system system_server
330 0 0% S 25 294536K 29760K fg radio com.android.phone
8 0 0% S 1 0K 0K fg root sync_supers
9 0 0% S 1 0K 0K fg root bdi-default
10 0 0% S 1 0K 0K fg root kblockd
11 0 0% S 1 0K 0K fg root khubd
12 0 0% S 1 0K 0K fg root kinteractiveup
14 0 0% S 1 0K 0K fg root kswapd0
15 0 0% S 1 0K 0K fg root fsnotify_mark
16 0 0% S 1 0K 0K fg root crypto
with autorotate - system_server
Code:
top -m 100 -d 1 -n 1 | head -20
User 7%, System 12%, IOW 0%, IRQ 0%
User 6 + Nice 2 + Sys 13 + Idle 85 + IOW 0 + IRQ 0 + SIRQ 0 = 106
PID PR CPU% S #THR VSS RSS PCY UID Name
132 0 14% S 81 369572K 45768K fg system system_server
12030 0 5% R 1 1004K 400K bg root top
200 0 3% S 17 285416K 33964K fg system com.android.systemui
78 0 2% S 8 42944K 16884K fg system /system/bin/surfaceflinger
290 0 0% S 1 2464K 636K fg wifi /system/bin/wpa_supplicant
223 0 0% S 1 0K 0K fg root dhd_dpc
11939 0 0% S 1 0K 0K fg root kworker/0:1
10 0 0% S 1 0K 0K fg root kblockd
11 0 0% S 1 0K 0K fg root khubd
12 0 0% S 1 0K 0K fg root kinteractiveup
14 0 0% S 1 0K 0K fg root kswapd0
15 0 0% S 1 0K 0K fg root fsnoti
again top with Threads
Code:
User 5%, System 12%, IOW 0%, IRQ 0%
User 15 + Nice 3 + Sys 39 + Idle 254 + IOW 0 + IRQ 0 + SIRQ 0 = 311
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
132 146 0 7% D 369572K 45768K fg system system_server system_server
12028 12028 0 4% R 1192K 588K bg root top top
132 166 0 2% S 369572K 45768K fg system er$SensorThread system_server
132 148 0 2% S 369572K 45768K fg system er.ServerThread system_server
132 147 0 1% S 369572K 45768K fg system SensorService system_server
200 200 0 0% S 285416K 33964K fg system ndroid.systemui com.android.systemui
11864 11864 0 0% S 0K 0K fg root kworker/u:2
11939 11939 0 0% S 0K 0K fg root kworker/0:1
78 111 0 0% S 42944K 16884K fg system SurfaceFlinger /system/bin/surfaceflinger
132 187 0 0% S 369572K 45768K fg system WifiService system_server
What should i do?
edit:
strace is writing following block repeatedly like crazy
strace -f -T -v -p 132
Code:
(Timeout) <0.000037>
[pid 147] write(103, "h\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0pe\34d\2340\0\0\354\337\267?>\205\[email protected]\275"..., 104 <unfinished ...>
[pid 166] <... epoll_wait resumed> ) = 1 <0.031740>
[pid 166] read(102, "h\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0pe\34d\2340\0\0\354\337\267?>\205\[email protected]\275"..., 104) = 104 <0.000034>
[pid 166] clock_gettime(CLOCK_MONOTONIC, {53448, 257720074}) = 0 <0.000030>
[pid 166] write(46, "W"..., 1) = 1 <0.000278>
[pid 166] read(102, 0x519ebb80, 104) = -1 EAGAIN (Resource temporarily unavailable) <0.000032>
[pid 166] epoll_wait(0x6a, 0x519eb9f0, 0x10, 0xffffffff <unfinished ...>
[pid 148] <... epoll_wait resumed> ) = 1 <0.029798>
[pid 148] read(45, "W"..., 16) = 1 <0.000038>
[pid 148] clock_gettime(CLOCK_MONOTONIC, {53448, 261245950}) = 0 <0.000035>
[pid 148] getpid() = 132 <0.000090>
[pid 148] getuid32() = 1000 <0.000029>
[pid 148] epoll_wait(0x2f, 0x50787a90, 0x10, 0) = 0 <0.000032>
[pid 148] clock_gettime(CLOCK_MONOTONIC, {53448, 263335575}) = 0 <0.000276>
[pid 148] epoll_wait(0x2f, 0x50787a90, 0x10, 0xa6d7 <unfinished ...>
[pid 147] <... write resumed> ) = 104 <0.008302>
[pid 147] poll([{fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}, {fd=41, events=POLLIN}], 5, -1 <unfinished ...>
[pid 146] <... write resumed> ) = 16 <0.012667>
[pid 146] ioctl(39, 0x80066108, 0x50587ec0) = 0 <0.016268>
[pid 146] write(36, "\0\0\0\0\0\0\0\0\2\0\0\0]\1\0\0"..., 16) = 16 <0.000044>
[pid 146] write(36, "\0\0\0\0\0\0\0\0\2\0\1\0J\0\0\0"..., 16) = 16 <0.000300>
[pid 146] write(36, "\0\0\0\0\0\0\0\0\2\0\2\0G\1\0\0"..., 16) = 16 <0.000039>
[pid 146] write(36, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 16 <unfinished ...>
[pid 147] <... poll resumed> ) = 1 ([{fd=42, revents=POLLIN}]) <0.021342>
[pid 147] read(42, "\310\320\0\0\352P\4\0\2\0\0\0]\1\0\0\310\320\0\0\333T\4\0\2\0\1\0J\0\0\0\310"..., 512) = 64 <0.000039>
[pid 147] poll([{fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}, {fd=41, events=POLLIN}], 5, 0) = 0

Hey dude,
No, you are not the only one with the auto-rotate bug. I have it too, but im on stock, non rooted ICS 4.0.4 for the Nexus S. But I can't help you either
Just wanted you to know that you are not alone.

what are the symptoms of this bug? every since i loaded 4.0.4, my phone seems to be eating up battery like crazy, also freezing up and shutting off randomly. sounds like it could be my problem.
should i just disable the auto-rotate setting for now?

00Hensley said:
what are the symptoms of this bug? every since i loaded 4.0.4, my phone seems to be eating up battery like crazy, also freezing up and shutting off randomly. sounds like it could be my problem.
should i just disable the auto-rotate setting for now?
Click to expand...
Click to collapse
It's worth a try, you can't damage anything if you do

I've been using the attached patch (against the stock ICS 3.0 kernel source, but should apply to any Nexus S 2.6.35 ICS or 3.0 kernel), which throttles the orientation sensor device and reduces system_server CPU usage to a more reasonable 2-3% (similar to Gingerbread).

Thanks for confirmation.
based on the confirmation there is new bug from me:
xxxttp://code.google.com/p/android/issues/detail?id=29965
For quick autorotate on and off i'm using quick app:
xxxttps://play.google.com/store/apps/details?id=com.friedflow.autorotate&feature=order_history
Thanks for the kernel patch... but i think, i will not building kernel...
i don't understand, why these bugs are not fixed yet... Like USB slow file transfer...

steven676 said:
I've been using the attached patch (against the stock ICS 3.0 kernel source, but should apply to any Nexus S 2.6.35 ICS or 3.0 kernel), which throttles the orientation sensor device and reduces system_server CPU usage to a more reasonable 2-3% (similar to Gingerbread).
Click to expand...
Click to collapse
How's this patching working out for you? Any side effects to watch out for? Also, did you find anything more refined along the way?
Thanks!

InstigatorX said:
How's this patching working out for you? Any side effects to watch out for? Also, did you find anything more refined along the way?
Click to expand...
Click to collapse
I've been carrying this patch since December with absolutely no ill effects, and given that it works, I haven't bothered to look for better solutions ...

steven676 said:
I've been carrying this patch since December with absolutely no ill effects, and given that it works, I haven't bothered to look for better solutions ...
Click to expand...
Click to collapse
Any hints how to apply this patch?

How configure the phone to use the internal memory on bricked DesireS?

I have bricked EMMC chip on my HTC Desire S, but bootloader and recovery working in readonly mode. I created the partition table on the external memory card (Micro SD), similar to the structure of internal memory in the extended partition. I modified the init.saga.rc in boot.img for using new partitions on sdcard. After booting over fastboot, I got a working phone
But i need help to configure the phone to use the internal memory, 1st partition on sdcard mmcblk1p1(vold/179:65 - fat32) or /data partition for DCIM, Music and etc.
I see several solutions, but do not know how to do:
1. "/data" partition, like /data/Documents...
2. Automounting through DirectVolume manager 1st partion on sd
3. Mount through init.rc, but system cant find STORAGE
4. Make 2nd storage like PHONE_STORAGE/INTERNAL_STORAGE
5. ?????
Code:
# logcat | grep Vold
logcat | grep Vold
I/Vold ( 1217): Vold 2.1 (the revenge) firing up
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1217): USB connected
D/Vold ( 1217): Share method ums now available
D/Vold ( 1217): USB connected
D/VoldCmdListener( 1217): volume list
D/VoldCmdListener( 1217): share status ums
Code:
# logcat | grep Volume
logcat | grep Volume
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
Code:
# logcat | grep Mount
I/SystemServer( 1332): Mount Service
D/MountService( 1332): got storage path: /mnt/sdcard description: USB storage pr
imary: true removable: true emulated: false mtpReserve: 0 allowMassStorage: true
maxFileSize: 4294967296
E/MountService( 1332): Error processing initial volume state
E/MountService( 1332): java.lang.Exception: Unexpected state 2
E/MountService( 1332): at com.android.server.MountService$2.run(MountService.ja
va:656)
D/MountService( 1332): volume state changed for /mnt/sdcard (null -> removed)
Code:
# mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p8 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk1p9 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=
ordered,noauto_da_alloc)
/dev/block/mmcblk1p10 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk1p11 on /devlog type ext2 (rw,nosuid,nodev,noatime,barrier=1,da
ta=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Code:
# ls -l dev/block/vold
brw-rw---- 1 root root 179, 64 Jul 3 11:09 179:64
brw-rw---- 1 root root 179, 65 Jul 3 11:09 179:65
brw-rw---- 1 root root 179, 66 Jul 3 11:09 179:66
brw-rw---- 1 root root 179, 69 Jul 3 11:09 179:69
brw-rw---- 1 root root 179, 70 Jul 3 11:09 179:70
brw-rw---- 1 root root 179, 71 Jul 3 11:09 179:71
brw-rw---- 1 root root 179, 72 Jul 3 11:09 179:72
brw-rw---- 1 root root 179, 73 Jul 3 11:09 179:73
brw-rw---- 1 root root 179, 74 Jul 3 11:09 179:74
brw-rw---- 1 root root 179, 75 Jul 3 11:09 179:75
brw-rw---- 1 root root 179, 76 Jul 3 11:09 179:76
Code:
# cat /etc/vold.fstab
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
PS: Manual mount
Code:
mount /dev/block/mmcblk1p1 /mnt/sdcard
working, but system applications still want to EXTERNAL_STORAGE.

kibril said:
I have bricked EMMC chip on my HTC Desire S, but bootloader and recovery working in readonly mode. I created the partition table on the external memory card (Micro SD), similar to the structure of internal memory in the extended partition. I modified the init.saga.rc in boot.img for using new partitions on sdcard. After booting over fastboot, I got a working phone
But i need help to configure the phone to use the internal memory, 1st partition on sdcard mmcblk1p1(vold/179:65 - fat32) or /data partition for DCIM, Music and etc.
I see several solutions, but do not know how to do:
1. "/data" partition, like /data/Documents...
2. Automounting through DirectVolume manager 1st partion on sd
3. Mount through init.rc, but system cant find STORAGE
4. Make 2nd storage like PHONE_STORAGE/INTERNAL_STORAGE
5. ?????
Code:
# logcat | grep Vold
logcat | grep Vold
I/Vold ( 1217): Vold 2.1 (the revenge) firing up
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 1217): USB connected
D/Vold ( 1217): Share method ums now available
D/Vold ( 1217): USB connected
D/VoldCmdListener( 1217): volume list
D/VoldCmdListener( 1217): share status ums
Code:
# logcat | grep Volume
logcat | grep Volume
D/Vold ( 1217): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
D/Vold ( 1217): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
W/DirectVolume( 1217): Invalid 'PARTN' value
Code:
# logcat | grep Mount
I/SystemServer( 1332): Mount Service
D/MountService( 1332): got storage path: /mnt/sdcard description: USB storage pr
imary: true removable: true emulated: false mtpReserve: 0 allowMassStorage: true
maxFileSize: 4294967296
E/MountService( 1332): Error processing initial volume state
E/MountService( 1332): java.lang.Exception: Unexpected state 2
E/MountService( 1332): at com.android.server.MountService$2.run(MountService.ja
va:656)
D/MountService( 1332): volume state changed for /mnt/sdcard (null -> removed)
Code:
# mount
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk1p8 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
/dev/block/mmcblk1p9 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=
ordered,noauto_da_alloc)
/dev/block/mmcblk1p10 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,dat
a=ordered)
/dev/block/mmcblk1p11 on /devlog type ext2 (rw,nosuid,nodev,noatime,barrier=1,da
ta=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
Code:
# ls -l dev/block/vold
brw-rw---- 1 root root 179, 64 Jul 3 11:09 179:64
brw-rw---- 1 root root 179, 65 Jul 3 11:09 179:65
brw-rw---- 1 root root 179, 66 Jul 3 11:09 179:66
brw-rw---- 1 root root 179, 69 Jul 3 11:09 179:69
brw-rw---- 1 root root 179, 70 Jul 3 11:09 179:70
brw-rw---- 1 root root 179, 71 Jul 3 11:09 179:71
brw-rw---- 1 root root 179, 72 Jul 3 11:09 179:72
brw-rw---- 1 root root 179, 73 Jul 3 11:09 179:73
brw-rw---- 1 root root 179, 74 Jul 3 11:09 179:74
brw-rw---- 1 root root 179, 75 Jul 3 11:09 179:75
brw-rw---- 1 root root 179, 76 Jul 3 11:09 179:76
Code:
# cat /etc/vold.fstab
# Mounts the first usable partition of the specified device
dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host/mmc2
PS: Manual mount
Code:
mount /dev/block/mmcblk1p1 /mnt/sdcard
working, but system applications still want to EXTERNAL_STORAGE.
Click to expand...
Click to collapse
hey, hey,,,, can u pls describe the following:
"I created
the partition table on the external
memory card (Micro SD), similar to
the structure of internal memory in
the extended partition. "
u r my new hope. I really need this. pls pls...can u put some attachments to help me??

All done, thanks for replays!
I'll build images ROM(CM7) on the weekend.

I'm very interested on this, same situation here, fried emmc chip but recovery and boot still workin on ro mode. I've been trying with fastboot for a while but all I can do is boot with a different recovery image.
Keep on this and please share all you can

Usb mass storage
Now from unresolved problems remained automounting via usb fat32 partition, ill try fix this.
PS: Somebody can up my rating for developer part of forum?!))

You need another 4 posts to be able to post there.

[GUIDE] How to run SD version of CM7.1 on HTC Desire S (fried emmc chips too).
I published a complete guide in "Desire S General":
http://forum.xda-developers.com/showthread.php?t=1756287

Bootloop & Dalvik Cache Wipe failed

Hello friends,
I'm stumped. Don't know what to do anymore.
Im am not new to rooting/modding but I am at a point now where I can't help myself.
I had CM10 running on my HOS and wanted to go back to Stock. So I relocked the Bootloader and started flashing my device. Unfortunately it didn't work and ended with the Errorcode 155 (as far as i can remember).
From there on nothing worked anymore. I think i got the HTC logo and then a black screen.
So i unlocked the Bootloader again and put CWR on it. I wanted to put CM ROM on it via adb put but didn't work. "Device not found".
So, after that i flashed TWRP and mounted my external storage so i could put the ROM on it. But didn't work. Windows said I had to format it. So i formatted it with FAT32. After that i was able to put ROM and gapps on it. Finally I was able to flash the ROM and gapps. That did work. I wanted to wipe Dalvik Cache but it said "Failed". Rebooted into Fastboot and did fastboot flash boot boot.img
I took boot.img out of the CM-Zip File.
Wiping external storage also failed.
Does anyone have a clue what is going on? How can i fix it?
I got a log from clockwork. Hope anyone can do something with it.
Code:
Starting recovery on Tue Feb 19 09:05:09 2013
framebuffer: fd 4 (540 x 960)
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/mmcblk0p22 (null) 0
2 /boot emmc /dev/block/mmcblk0p21 (null) 0
3 /cache ext4 /dev/block/mmcblk0p34 (null) 0
4 /data ext4 /dev/block/mmcblk0p35 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p36 (null) 0
6 /system ext4 /dev/block/mmcblk0p33 (null) 0
7 /misc emmc /dev/block/mmcblk0p23 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.koush.20120429.134456
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sun Apr 29 13:45:32 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=ville
ro.product.brand=htc
ro.product.name=cm_ville
ro.product.device=ville
ro.product.board=ville
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=ville
ro.build.description=cm_ville-userdebug 4.0.4 IMM76D eng.koush.20120429.134456 test-keys
ro.build.fingerprint=htc/cm_ville/ville:4.0.4/IMM76D/eng.koush.20120429.134456:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=ville
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-ville-UNOFFICIAL
ro.modversion=9.0.0-RC0-ville-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=SH24KW405401
ro.bootmode=recovery
ro.baseband=1.11.50.05.28
ro.carrier=HTC-GER
ro.bootloader=2.15.0000
ro.hardware=ville
ro.revision=128
ro.emmc=1
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
-- Wiping cache...
Formatting /cache...
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
Creating filesystem with parameters:
Size: 268431360
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65535
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65535 blocks
warning: wipe_block_device: Discard failed
Cache wipe complete.
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
Couldn't open directory.
No files found.
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
W:failed to mount /dev/block/mmcblk0p35 (Invalid argument)
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
-- Wiping cache...
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
Formatting /cache...
Creating filesystem with parameters:
Size: 268431360
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65535
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65535 blocks
warning: wipe_block_device: Discard failed
Cache wipe complete.
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 115 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 1
fd: 12
ev: 0 0 0
fd: 12
ev: 1 114 0
fd: 12
ev: 0 0 0
fd: 12
ev: 1 116 1
fd: 12
ev: 0 0 0

looks like it's not mounting mmpcblk0p35 which is /data. I'm curious about the line '/datadata'..
You can cause some pain with TWRP and wiping, you can wipe a mount point. Maybe a contributing factor to a failed install? I would boot to TWRP and install the ROM again and then reboot.

I tried several times installing the ROM from scratch via both CWM and TWRP. Didn't work. Still stuck on CM animation.

So I finally got my phone running again. However no stock rom, "just" CM10.1.
I did a factory reset with TWRP to do a formatting of the partitions. After that I flashed CM10.1-Nightly and the corresponding boot.img
...I tried again to install the stock RUU (with relocked bootloader) but still getting Error-155.
So i'm on CM10.1. Not too bad

tonestar81 said:
So I finally got my phone running again. However no stock rom, "just" CM10.1.
I did a factory reset with TWRP to do a formatting of the partitions. After that I flashed CM10.1-Nightly and the corresponding boot.img
...I tried again to install the stock RUU (with relocked bootloader) but still getting Error-155.
So i'm on CM10.1. Not too bad
Click to expand...
Click to collapse
great job. as you get more devious in breaking your phone, you get better at fixing it CM10.1 rocks, everything is working for me on it.
Unless your planing on selling the phone, I'm not sure why you'd want to use any RUU's (or any OTA/Vendor stuff). Your now managing the software on your phone not the telco/HTC. For sure you do a better job!

Got Stuck into BOOTLOOP
I am running Noir A2 Lite, with Spreadtrum chip SP8810. I am stucked into Bootloop, and I am fully sure it is due to not clearing Dalvik-cache.
I was setting up the low internal memory issue with ext3 partition of Sdcard method using Pimk Rom, BusyBox etc. Everything was fine and in the end I got the internal memory increased but the phone was working slow so I thought to get back to the previous state where my genuine internal phone memory was existing. So I just done the RESET FACTORY from Settings of phone. After that it rebooted and still keeps rebooting again and again. I searched on the causes of BOOTLOOP and came to know it might happen due to not clearing DELVIK-CACHE.
Phone is rooted D Of course), and I can't boot into Recovery Mode, I don't know why because since I rooted I wasn't able to get into recovery mode by pressing any key combinations. But I can go into fastboot by pressing VOL+ and POWER button together.
Can you suggest me any way to resolve this problem?
Regards!!

MTK 6592 Touch Screen Bricked ?

hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?

dhis is my test
Code:
============ Memory Detection Report ===========
Internal RAM:
Size = 0x00020000 (128KB)
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000200000(2MB)
EMMC_PART_BOOT2 Size = 0x0000000000200000(2MB)
EMMC_PART_RPMB Size = 0x0000000000020000(0MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000003a3e00000(14910MB)
============ RAM Test ============
Data Bus Test:
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
Address Bus Test:
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
RAM Pattern Test :
Writing ...
OK!!
Increment/Decrement Test:
Writing...
OK!!
============ NAND Test ============
SKIP! NAND Flash was not detected!
============ EMMC Test ============
OK!!

Code:
?????????adb?fastboot?????,??:
??adb??:adb devices
??shell:adb shell
??????:adb logcat
???????SD?:adb push D:\myfile.pdf /sdcard/
???SD?????:adb pull /sdcard/myfile.pdf D:\
??fastboot??:fastboot devices
??adb????:adb help
??fastboot????:fastboot help
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/devices
cat /proc/devices
Character devices:
1 mem
2 pty
3 ttyp
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
13 input
14 sound
29 fb
90 mtd
108 ppp
116 alsa
128 ptm
136 pts
141 mtk_stp_usktrk
153 mtk_wmt_WIFI_chrdev
160 Vcodec
166 ttyACM
168 MJC
180 usb
182 sec
184 ccci0
184 CCCI_IPC_DEV0
184 ccci1_fs
184 vir_chr0
184 ccci_tty_drv0
188 M4U_device
189 usb_device
190 mtk_stp_wmt
191 mtk_stp_GPS_chrdev
192 mtk_stp_BT_chrdev
193 fm
196 devmap
204 ttyMT
226 ttyGS
227 camera-pipemgr
228 mt3326-gps
229 camera-sysram
230 camera-isp
231 FM50AF
232 kd_camera_hw
233 DumChar
234 accdet
235 mtk-adc-cali
236 mtk_disp
237 MTK_SMI
238 dummy_eeprom
239 dummy_cam_cal
240 hall_dev
241 AGOLD_DRIVER
242 mtk_jpeg
243 pmt
244 kd_camera_flashlight
245 flash_info
246 btn
247 mtk_almk
248 btif
249 MT_pmic_adc_cali
250 mtkfb_vsync
251 mmp
252 sched
253 BOOT
254 rtc
Block devices:
259 blkext
7 loop
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 zram
254 device-mapper
[email protected]_v92_zlh_hd:/ $
C:\Program Files (x86)\Shuame>adb shell
[email protected]_v92_zlh_hd:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
253 0 1048576 zram0
179 0 15246336 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 819200 mmcblk0p5
179 6 131072 mmcblk0p6
179 7 1212416 mmcblk0p7
179 8 13001728 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 7764992 mmcblk1
179 97 7760896 mmcblk1p1
[email protected]_v92_zlh_hd:/ $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ord
ered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]_v92_zlh_hd:/ $

BliNeR-KeY said:
hello i flash my drivice mtk6592 ( star n3+ ocracore ) with a same rom.
is not first time to i flash rom, but dhis new phone worked just a 30 min
after flash my touch screen dont work . and imei ( imei fix ok)
i try so send a lots rom , rom accept never found error . same my touch screen dont work.
and factory rom no success.
maybe i need to edit scatter file?
maybe my touch screen is bricked?
maybe my touch screen have hardware problem?
Click to expand...
Click to collapse
Same happened to me. Have you managed to fix this issue?

anyone found solution?

same happened to me too. i've tried removing the digitizer, but i don't think the problem is in digitizer. when it's connected i can see touchscreen: ili2113a in factory mode. when i disconnect the digitizer, i can see touchscreen: (null)
so digitizer should be working. i've tried flashing like 15 roms, but didn't manage to fix the problem.
anyone found a solution?

hello
you solved?
---------- Post added at 11:45 AM ---------- Previous post was at 11:34 AM ----------

maybe not yet solved

İ have same as your problem. My device is General Mobile etab5. Calibration failed it says invalid value: 165