Hello, everyone,
Yesterday while browsing, my phone freezed. After restart, it went to bootloop.
I was using CWM+ Maclaw's CM11 (not the latest).
I reflashed my rom, but Gapps kept FC.
I reflashed Gapps (2 different builds)- same FC's.
At some point I managed to boot OK without Gapps.
I tried formatting data/dalvik- no change.
After some more digging- I messed up ( formatted system, modemfs,cache,data...)..
Now I can only boot into CWM and into Recovery.
When in Recovery, the following message appears:
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
E: Can't mount /cache/recovery/last_install
E: Can't open/cache/recovery/last_install
I tried to flash stock rom using Odin (with/without PIT); other CWM, TWRP with no luck. No matter if it's the green PASS, or blue RESET at the end .
I have ADB, I've used it in the past...
I think I've checked my emmc with adb- here's the code (I don't know what/where to look at?)
dmesg | grep mmc0
<6>[ 1.252746] mmci-pl18x sdi2: mmc0: PL180 manf 80 rev4 a
,-1 (pio)
<3>[ 1.288299] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.288726] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 52
<3>[ 1.311920] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 8
<3>[ 1.312316] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.312713] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313110] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313476] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 5
<3>[ 1.313873] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.314270] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.314666] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<3>[ 1.315063] mmc0: [MMC] CMD TIMEOUT STATUS: 4, CMD: 55
<6>[ 1.471466] mmc0: new high speed DDR MMC card at addres
<6>[ 1.472473] mmcblk0: mmc0:0001 SEM04G 3.68 GiB
<6>[ 1.472778] mmcblk0boot0: mmc0:0001 SEM04G partition 1
<6>[ 1.473022] mmcblk0boot1: mmc0:0001 SEM04G partition 2
<3>[ 2.545837] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 2.647064] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.748718] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.850280] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 2.951568] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.052856] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.154174] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.255462] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.356811] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.501464] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 3.602722] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.703857] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 3.921295] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 4.022216] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 4.123413] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 5.686920] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 5.788208] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 5.889678] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.116516] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 6.217834] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.319305] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.593414] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 6.694732] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 6.796325] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.063079] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 7.164337] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.266326] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.591979] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 7.693298] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 7.795074] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 8.061920] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 18
<3>[ 8.163146] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
<3>[ 8.265136] mmc0: [MMC] DATA TIMEOUT STATUS: 8, CMD: 17
I used this link, and I'm not quite sure I did it right...
Any suggestions ? Is it hardware or there is still hope? The fact that I can access Recovery and DL mode plus ADB still sees my phone is encouraging, right?
Did you try to flash russian "repair rom" with odin? It makes repart in semi-hopeless situations..it differs from newer odin roms, that is.
Thank you for your reply.
Never heard of it. I'll give it a try after work.
As far as I can understand, my partition is messed up, my emmc seems to be OK, but I can't flash any rom ( custom or original ), or any recovery...
p.s. Which one is the "russian rom" ? Is it stock SER rom, or some kind of MODDED Rom?
Is it MG2 ?
I tried MB4 - Passed in Odin, but without any change. Still on bootloop, still with CWM recovery.
Next is MG2... Same.
I'll try to downgrade to GB, it's the last thing I can think of.
Any help is much appreciated.
p.p.s TWRP instal with ODIN- no change, still on CW
Sir, here's the thing(i hope, that link's providing proper rom I am talking about..):
http://d-h.st/AZN
(resumable source)
If this will not work, i'd be worried.
You need to carefully add EVERYTHING to odin.
If it works, you need to - flash any jb you want, then update.zip(temp cwm) and do what you want, you are saved.
I did many stupid things with my machine, and this rom was always an lantern in the dark.
Thing is, that "russian rom" has unique set of files, that seem to heal any ace2 issues after problematic flashes.
Imho, every ace2 user should keep this rom on HDD(day, when it's gone is closer, and closer...keep it on your laptops/desktops, guys).
Downloading... I tried couple of LK6's (one with 1 file, and one with the CODE, PIT and CSC files).
Odin 1.85 states "pass" , while 3.09 stays on RESET!.
It's like the phone rejects anything I'm trying to flash.
I'm going to try with ODIN 1.85;1.86 and 3.09.
Edit: Still on bootloop. .
Any other ideas, guys ?
In desperate move, I can try to change the size of the partitions with adb...
p.s. I have trouble finding stock recovery.img to push with adb... Can anyone help ?
grundio said:
Downloading... I tried couple of LK6's (one with 1 file, and one with the CODE, PIT and CSC files).
Odin 1.85 states "pass" , while 3.09 stays on RESET!.
It's like the phone rejects anything I'm trying to flash.
I'm going to try with ODIN 1.85;1.86 and 3.09.
Edit: Still on bootloop. .
Any other ideas, guys ?
In desperate move, I can try to change the size of the partitions with adb...
p.s. I have trouble finding stock recovery.img to push with adb... Can anyone help ?
Click to expand...
Click to collapse
So, you did not use my advice? Ok, have a luck.
xo.en said:
So, you did not use my advice? Ok, have a luck.
Click to expand...
Click to collapse
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
grundio said:
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
Click to expand...
Click to collapse
Wipe data in recovery..
E: oh i didn't see 3 part. But still try :/
I can wipe only /boot in recovery. Wipe data;cache;system;partition commands results in error or just with "Formatting.." and blank progress bar.
I am searching recovery.img to flash with adb. If i try to flash recovery in CWM, the screen blinks couple of times and nothing happens.
grundio said:
No, I think I did exactly as you told me.
I downloaded the LK6 ROM from the link you gave (3 file rom- pit, csc and code).
I selected them in corresponding way in ODIN, and flashed. IT PASSED.
When the phone restarts, it's still on samsung logo ( left it for about half an hour, just to be sure).
I tried the same procedure with my other Odin versions too... Still on bootloop.
Click to expand...
Click to collapse
Now, this is weird...you may try to manually mess with partitions
http://forum.xda-developers.com/showthread.php?t=2596521
then flash sth with odin(it will repart machine again, so it may fix your problem then).
Btw, it does not matter, if russian rom is not starting, flash newer one after flashing russian.
Thanks for your reply. I've looked at the same thread in your link and I'll try it.
I'll try with flashing newer rom after the LK6 too. It's that corrupted CWM recovery that's stuck in the memory that grinds my gears.
I'm still trying to figure out why this happened... I'll post results in couple of days.
Ok, I'm currently trying to repartition the Ace 2...
In the process I get the following error:
print
Error: /dev/block/mmcblk0: unrecognised disk label
The same error with "rm" command...
I think I'm starting to give up on my Ace 2... Everything I tried is a deadend.
Hm-m.. That's strange...
I can install Temp CWM 6.0.2.8 (the screen blinks couple of times and it loads). The problem is I still can't mount anything. But it's working smoother than 6.0.4.8 (which I want to get rid of).
Now, I'm searching for .zip TWRP recovery (or even stock recovery .zip) to flash. I tried several types of kernels, but with no luck (the screen freezes/is loading on "Installing zip..." and nothing happens), it still can't mount/format anything in the menu.
Any thoughts ?
Dead...
Well, my Ace 2 is completely dead now (no signs of life at all) - no dw/recovery mode, the battery is not charging.
I feel bad for the phone, I really liked it.
Thank's for the help, guys. I appreciate it :good:
Related
My inc2 is always at the htc face, i have tried the RUU, with the USB, and also tried the rom.zip to TF card,with the PG32IMG.zip.
but they did not work.
I can go into the hboot and recovery.
it is s-off.
and now what else can I do.
thanks!!!!!!!!!
[update] i just found that i can only use the cm9 rom.
http://forum.xda-developers.com/showthread.php?t=1561816
so, what the difference of CM9 and others?
Go into recovery.. wipe all data and then flash a rom...
Sent from my Incredible 2 using Tapatalk 2
THE PG32IMG has to be installed from the bootloader. make sure it doesn.t have two zips on it : power down phone hold power button and volume down at same time to get bootloader and if the zip on ROOT of sd card is ok it will pick it up and install it.
what rom are you running now
i have tried a few roms, and today i use the PG32IMG.zip from the forum
this link. http://forum.xda-developers.com/showthread.php?t=1599767
it still does not work.
i am very very puzzle...
i have tried "dmesg | grep mmc0" on adb shell
will u tell me sth from the following information?
<3>[ 10.749847] mmc0: No card detect facilities available
<6>[ 10.750488] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 10.750640] mmc0: Platform slot type: MMC
<6>[ 10.750762] mmc0: 4 bit data mode disabled
<6>[ 10.751007] mmc0: 8 bit data mode enabled
<6>[ 10.751159] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 10.751403] mmc0: Slot eject status = 0
<6>[ 10.751525] mmc0: Power save feature enable = 1
<6>[ 10.751647] mmc0: DM non-cached buffer at ffa0d000, dma_addr 0x2a4b0000
<6>[ 10.751953] mmc0: DM cmd busaddr 0x2a4b0000, cmdptr busaddr 0x2a4b0300
<4>[ 10.864257] mmc0: high speed mode max_dtr = 50000000
<4>[ 10.864593] mmc0: host does not support reading read-only switch. assuming
write-enable.
<6>[ 10.864807] mmc0: new high speed SDHC card at address aaaa
<6>[ 10.865875] mmcblk0: mmc0:aaaa SE04G 3.69 GiB
Does recovery say anything when you try to install roms?
Sent from here
i can flash all the roms of IC2.
and i also can change different kinds of recoveries.
the rec works well.
anyone can help me ?
i have no idea for a few days already.
thanks .
Maybe your partitions are ext4? Try converting back to ext3
Sent from my Xoom using XDA Premium HD app
Use 4ext recovery man... it auto converts it
Sent from my Incredible 2 using Tapatalk 2
it should not be the matter of filesystem.
i have changed Ext3 and ext4 for a try , it didn't work.
Hey everyone, today I started having some really horrible problems with my G2. It started when I woke up and noticed that the phone was powered OFF, which was not normal. Pressing the power button was unable to turn it on, but pulling the battery worked fine.
Everything was normal for a couple hours, but then I began getting random freezes. At least they seemed random, but I was able to reproduce it fairly consistently by turning the screen off and then on a few moments later.
Ok I thought, haven't wiped in a while (Currently on Mimicry 1.4 using 4EXT recovery), so in I went to the Superwipe. Flashing the Superwipe failed. This is the error I see (and have NEVER seen before)
E:Error in /sdcard/SuperWipeG2+ext4.zip
(Status 1)
Installation aborted
So I just went in and did a basic wipe everything and reinstall the ROM, unfortunately this leads to just a white HTC screen.
Flash a Nandroid? Nope, below is the error I see
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error while formatting /system!
I feel like somehow my file system got corrupted, but unlike using Odin with the Vibrant I'm unsure how to fix this on the Vision. Anybody?
If you're in recovery, hook the phone up to your computer and run these two commands:
adb shell
dmesg | grep mmc0
if you see something like:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Then it means your internal memory (emmc) is fried/dead.
You can do the following two commands:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
To see if you have the 'good batch' SEM04G chip, or if you were yet another victim of the faulty 'bad batch' of M4G2DE chips
kbeezie said:
If you're in recovery, hook the phone up to your computer and run these two commands:
adb shell
dmesg | grep mmc0
if you see something like:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Then it means your internal memory (emmc) is fried/dead.
You can do the following two commands:
adb shell
cat /proc/kmsg | grep 'mmc0:0001'
To see if you have the 'good batch' SEM04G chip, or if you were yet another victim of the faulty 'bad batch' of M4G2DE chips
Click to expand...
Click to collapse
Thanks for helping out. This is what I get with your first command.
<3>[ 7.968688] mmc0: No card detect facilities available
<6>[ 7.969268] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.969512] mmc0: Platform slot type: MMC
<6>[ 7.969665] mmc0: 4 bit data mode disabled
<6>[ 7.969909] mmc0: 8 bit data mode enabled
<6>[ 7.970031] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.970275] mmc0: Slot eject status = 0
<6>[ 7.970428] mmc0: Power save feature enable = 1
<6>[ 7.970550] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0fffb000
<6>[ 7.970825] mmc0: DM cmd busaddr 0x0fffb000, cmdptr busaddr 0x0fffb300
<6>[ 8.136444] mmc0: new high speed MMC card at address 0001
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
And with your second
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
Looking good I think?
Nospin said:
Thanks for helping out. This is what I get with your first command.
<3>[ 7.968688] mmc0: No card detect facilities available
<6>[ 7.969268] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.969512] mmc0: Platform slot type: MMC
<6>[ 7.969665] mmc0: 4 bit data mode disabled
<6>[ 7.969909] mmc0: 8 bit data mode enabled
<6>[ 7.970031] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.970275] mmc0: Slot eject status = 0
<6>[ 7.970428] mmc0: Power save feature enable = 1
<6>[ 7.970550] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0fffb000
<6>[ 7.970825] mmc0: DM cmd busaddr 0x0fffb000, cmdptr busaddr 0x0fffb300
<6>[ 8.136444] mmc0: new high speed MMC card at address 0001
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
And with your second
~ # cat /proc/kmsg | grep 'mmc0:0001'
cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 8.137908] mmcblk0: mmc0:0001 SEM04G 2.10 GiB
Looking good I think?
Click to expand...
Click to collapse
So looks like the internal memory isn't fried.
Which recovery are you using? clockworkmod or 4EXT Touch Recovery (I much prefer the latter, but you're probably using CWM if you have to use that superwipe zip).
4EXT Touch, I just use the superwipe zip out of habit.
What would you suggest I do to wipe the slate clean? It certainly seems like something is corrupted. When trying a Wipe Data/Factory Reset in 4EXT I get this.
Formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formatting /cache
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
So it seems mmcblk0p25 through 27 are all failing out.
Since you're using 4EXT, I recommend repartitioning your phone to see if that fixes it. If not, then hopefully you just have a bad download and redownloading the ROM can fix it.
Sent from Spaceball One.
Nada.
After full wipes of everything (including the SD card) I did manage to get rid of the mmcblk errors for a time (they came back, usually after a reboot or too many actions in recovery). After flashing Mimicry I do manage to get past the HTC screen, but I get an endless boot animation. Pulling the battery during an endless animation prompts a normal startup (including the "Android is Upgrading" dialog), but it begins the endless boot animation again after completion.
Ughhhhh. I feel like my salvation is in adb, but i'm just not very familiar with the commands that might solve this....
Edit- whoa whoa whoa, we may have something here. Give me a few.
Edit- I managed to achieve the "Welcome" screen of Mimicry. But I got a barrage of process.acore/Calender/Contacts/Googleeverything force closes.Then it froze.
Edit- And I may have full boot. Going to let it sit for 10 minutes before I attempt anything. What scares me is I never determined the cause of this.....
if your still having problems and the above didn't fix anything do the following.
boot to recovery and reformat everything to ext4 (execpt the fat32 partition of sd card)
try flashing a stable rom again
if problem still persists then I suggest booting into fastboot and flash your spl again (assuming you have eng s-off)
fastboot devices
(if you see yours continue)
fastboot -w
fastboot flash bootloader XXX.img
fastboot reboot bootloader
(of course rename the XXX to whatever you have image named, have it in the same folder as fastboot.exe)
now boot to recovery, you may need to reformat recovery, go for it, now flash rom of choice
hope your phone is working without all this but if not the above should do the trick
Sent from my HTC Vision using xda premium
Nospin said:
Hey everyone, today I started having some really horrible problems with my G2. It started when I woke up and noticed that the phone was powered OFF, which was not normal. Pressing the power button was unable to turn it on, but pulling the battery worked fine.
Everything was normal for a couple hours, but then I began getting random freezes. At least they seemed random, but I was able to reproduce it fairly consistently by turning the screen off and then on a few moments later.
Ok I thought, haven't wiped in a while (Currently on Mimicry 1.4 using 4EXT recovery), so in I went to the Superwipe. Flashing the Superwipe failed. This is the error I see (and have NEVER seen before)
E:Error in /sdcard/SuperWipeG2+ext4.zip
(Status 1)
Installation aborted
So I just went in and did a basic wipe everything and reinstall the ROM, unfortunately this leads to just a white HTC screen.
Flash a Nandroid? Nope, below is the error I see
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Error while formatting /system!
I feel like somehow my file system got corrupted, but unlike using Odin with the Vibrant I'm unsure how to fix this on the Vision. Anybody?
Click to expand...
Click to collapse
Try flashing a ROM that formats your partitions for you try ICS "Blackout" it makes it easier
hey ! i have the exact same problem! did u manage to fix ur phone ? how?
*fingers crossed*
I'm having the same problem. Whenever I try to reboot phone it goes to htc, reboots and goes to htc, then boots into recovery. Can't get past it.
I've tried connecting the phone via usb but it won't show up under adb devices.
I've wiped the phone and re-partitioned sd card.
Will be trying a different rom and seeing if that helps.
Any help other than that?
Edit: Flashed MIUI v4_2_8_10__VISION_CLEAN and phone booted fine. Must've been the TrickDroid rom I was trying to flash.
did any one tried this? any progress?
error in /sdcard/superwipeg2+ext4.zip (status 1)
For this error in ClockWork Recovery I did this:
CHANGE OPTION: "toggle script asserts" then the wipe script on my T-Mobile HTC Vision G2 acting correctly like it should and rebooted correctly instead of throwing the error above.
Hope this helps!
phone started rebooting then stuck.
Desire Z is stuck at HTC logo when power on
stuck at factory reset from hboot
stuck at wipe data/factory reset from cwm
error when opening cwm cant open /cache/recovery/log
error when install zip from sdcard
stuck at wipe data command from adb
stuck at fastbooting cwm.img
HBOOT menu
***UNLOCKED***
VISION PVT SHIP S-OFF
HBOOT-0.85.0015
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
Dec 20 2011, 16:21:13
Recovery: clockworkMod Recovery v5.8.1.0
ran this command and getting the results cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
so emmc chip is ok
any more ideas, or am i missing something??
Regards
zabroadcast said:
phone started rebooting then stuck.
Desire Z is stuck at HTC logo when power on
stuck at factory reset from hboot
stuck at wipe data/factory reset from cwm
error when opening cwm cant open /cache/recovery/log
error when install zip from sdcard
stuck at wipe data command from adb
stuck at fastbooting cwm.img
HBOOT menu
***UNLOCKED***
VISION PVT SHIP S-OFF
HBOOT-0.85.0015
MICROP-0425
RADIO-26.08.04.30_M3
eMMC-boot
Dec 20 2011, 16:21:13
Recovery: clockworkMod Recovery v5.8.1.0
ran this command and getting the results cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
so emmc chip is ok
any more ideas, or am i missing something??
Regards
Click to expand...
Click to collapse
no one's having any idea???
When this situation happens either you have some corrupt partitions or your emmc is fried, if its just a corrupt partition you can try an reformat to fix, nothing can be done if the chip is bad
You'll find more info in the second post here
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
When this situation happens either you have some corrupt partitions or your emmc is fried, if its just a corrupt partition you can try an reformat to fix, nothing can be done if the chip is bad
You'll find more info in the second post here
http://forum.xda-developers.com/showthread.php?t=2348266
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for replying
tried fastboot erase system -w but permission error
tried ALL IN ONE Wipe Tool , its formatting from format but nullifying tool is not working,
Supe Handy SuperWipe Tool installs but nothing happens after that.
Is there a way to know that emmc is fried or not?
Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
great, i will look into PC10IMG.zip
what i did for now is according to
http://forum.xda-developers.com/showthread.php?t=1572924
under
Testing for a fried ROM:
i ran
Code:
adb shell
dmesg | grep mmc0
and i am getting
~ # dmesg | grep mmc0
<3>[ 4.305236] mmc0: No card detect facilities available
<6>[ 4.305847] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 4.305999] mmc0: Platform slot type: MMC
<6>[ 4.306121] mmc0: 4 bit data mode disabled
<6>[ 4.306365] mmc0: 8 bit data mode enabled
<6>[ 4.306518] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 4.306762] mmc0: Slot eject status = 0
<6>[ 4.306915] mmc0: Power save feature enable = 1
<6>[ 4.307037] mmc0: DM non-cached buffer at ff817000, dma_addr 0x2ae32000
<6>[ 4.307281] mmc0: DM cmd busaddr 0x2ae32000, cmdptr busaddr 0x2ae32300
<6>[ 4.463348] mmc0: new high speed MMC card at address 0001
<6>[ 4.464660] mmcblk0: mmc0:0001 M4G2DE 2.04 GiB
<3>[ 5.832824] mmc0: Failed to get card ready i = 122095
<6>[ 5.833068] mmc0: reinit card
<4>[ 5.833190] mmc0: Starting deferred resume
<6>[ 7.873016] mmc0: Deferred resume failed
<3>[ 8.078094] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.079254] mmc0: Controller has been reset
<6>[ 8.080017] mmc0: Worked around bug 1535304
<3>[ 8.082550] mmc0: DMA channel flushed (0x80000004)
<6>[ 8.083679] mmc0: Controller has been reset
<6>[ 8.084442] mmc0: Worked around bug 1535304
<6>[ 8.093109] mmc0: reinit card
<4>[ 8.093475] mmc0: Starting deferred resume
<6>[ 10.132995] mmc0: Deferred resume failed
<3>[ 10.245178] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.245971] mmc0: Controller has been reset
<6>[ 10.246520] mmc0: Worked around bug 1535304
<3>[ 10.248535] mmc0: DMA channel flushed (0x80000004)
<6>[ 10.249359] mmc0: Controller has been reset
<6>[ 10.249664] mmc0: Worked around bug 1535304
<6>[ 10.257629] mmc0: reinit card
<4>[ 10.257873] mmc0: Starting deferred resume
<6>[ 12.292999] mmc0: Deferred resume failed
<3>[ 12.526947] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.527374] mmc0: Controller has been reset
<6>[ 12.527587] mmc0: Worked around bug 1535304
<3>[ 12.529083] mmc0: DMA channel flushed (0x80000004)
<6>[ 12.529510] mmc0: Controller has been reset
<6>[ 12.529815] mmc0: Worked around bug 1535304
<6>[ 12.537475] mmc0: reinit card
<4>[ 12.537719] mmc0: Starting deferred resume
<6>[ 14.572998] mmc0: Deferred resume failed
Click to expand...
Click to collapse
so mmc is not fried...... i will check this samsung one and let you know.
Regards
demkantor said:
Not great ways, you can check what chip you have (Samsung being the one likely to fail) if you get an engineering bootloader, the act of flashing the new bootloader, if successful, will wipe partitions as well but then you will be allowed fastboot commands to format.
Look in that thread again for a PC10IMG.zip I made for this purpose, it will flash a new radio, bootloader and recovery (but no os) so you can have the engineering bootloader.
There is also instruction to check if you have rooted via the gfree method ( flashing this may not be safe otherwise but many have done so and says it works fine still)
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I got an android running up form [GUIDE] Booting an Android System when only Recovery is at your disposal but this is not the solution, so can i do anything while i am at it. If emmc is not fried then why cant i reformat it and skip the bad partation.
STATUS
the PC10IMG.zip was stuck at updating.....
downloading another rom from sd
[GUIDE][KANG] Android Boot-From-SD w/ GAPPs and Play Store
Click to expand...
Click to collapse
but the download link was broken, found another link from google at
HTML:
http://inclu.net:82/HTC/DesireZ/
wifi does not work when boot form recovery, but amazingly
HTML:
[CODE]fastboot boot boot.img[/CODE]
is working and wifi was working....
but other commands are not working ......
you are limited to the fastboot commands available being you have a shipped bootloader,
you can try to get into an adb shell and run
mke2fs /dev/block/mmcblk0p25
mke2fs /dev/block/mmcblk0p26
mke2fs /dev/block/mmcblk0p27
to see if this will reformat for you
also
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
will tell you what chip you have, SEM04G being the 'bad' one
Results of the commands are pasted
mke2fs /dev/block/mmcblk0p25
Click to expand...
Click to collapse
Code:
~# mke2fs /dev/block/mmcblk0p25
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
35760 inodes, 142847 blocks
7142 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=146800640
5 block groups
32768 blocks per group, 32768 fragments per group
7152 inodes per group
Superblock backups stored on blocks:
32768, 98304
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs /dev/block/mmcblk0p26
Click to expand...
Click to collapse
Code:
~ # mke2fs /dev/block/mmcblk0p26
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
75200 inodes, 300799 blocks
15039 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=310378496
10 block groups
32768 blocks per group, 32768 fragments per group
7520 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Writing inode tables: done
Writing superblocks and filesystem accounting information:
done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
mke2fs /dev/block/mmcblk0p27
Click to expand...
Click to collapse
Code:
~ # mke2fs /dev/block/mmcblk0p27
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p27 is apparently in use by the system; will not make a filesystem here!
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
Click to expand...
Click to collapse
Code:
~ # cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
M4G2DE
Hi,
I think I have the SDS bug on my N7100. My phone crashed during a morning wake-up alarm and it won't boot again. I want to sent it for repair because it's under warranty only I can't flash my recovery to stock (or don't know how to do it) i'm currently using Philz Recovery.
Does anyone now how I can flash stock recovery or even if it's possible.
What i tried to fix my problem:
1. Tried to flash the original stock rom from sammobile using odin, it says it's passed and flashed system/cache/boot/recovery images. But then when I reboot it's still stuck at Samsung Bootloader logo. when i enter recovery it's still Philz Recovery.
2. Tried to flash recovery while using fastboot, but it won't recognize the device in download mode or recovery mode.
3. When i boot into recovery none of the partitions get mounted. I get the following error using: adb shell "dmesg | grep mmc0"
Code:
<3>[ 2.124315] c3 mmc0: Version ID 0x5342240a.
<6>[ 2.124568] c3 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.125100] c3 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.155873] c0 mmc0: cmd 52 response timeout error
<3>[ 2.156724] c0 mmc0: cmd 52 response timeout error
<3>[ 2.160779] c0 mmc0: cmd 8 response timeout error
<3>[ 2.161629] c0 mmc0: cmd 5 response timeout error
<3>[ 2.162465] c0 mmc0: cmd 5 response timeout error
<3>[ 2.163300] c0 mmc0: cmd 5 response timeout error
<3>[ 2.164130] c0 mmc0: cmd 5 response timeout error
<3>[ 2.164987] c0 mmc0: cmd 55 response timeout error
<3>[ 2.165859] c0 mmc0: cmd 55 response timeout error
<3>[ 2.166706] c0 mmc0: cmd 55 response timeout error
<3>[ 2.167553] c0 mmc0: cmd 55 response timeout error
<3>[ 2.186791] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.186822] c0 mmc0: VTU00M: 15010056545530304df1d72b21e9af87
<3>[ 2.291768] c0 mmc0: cmd 13 response timeout error
<6>[ 2.291871] c0 mmc0 : disable PON feature : ffffff92 : 00(0c) : 00000000
<3>[ 2.292721] c0 mmc0: cmd 6 response timeout error
<3>[ 2.293551] c0 mmc0: cmd 6 response timeout error
<3>[ 2.294380] c0 mmc0: cmd 6 response timeout error
<3>[ 2.295210] c0 mmc0: cmd 6 response timeout error
<3>[ 2.295265] c0 mmc0: error -110 whilst initialising MMC card
And when I run adb shell "ls /dev/block" i don't see any reference to the internal storage MMC card:
Code:
adb shell "ls /dev/block"
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
Also when booting it points out that it can't mount any of the partitions.
Thanks in advance,
Jesse
If you can get the Samsung boot screen it is not sds. Sds the phone will not turn on. I would try the recovery firmware from skipsoft.net. There is a thread on here for mskips toolkit, but that is the website for it
Sent from my GT-N7105 using Tapatalk
Thanks tried it with mskips toolkit but it couldn't get futher then 'waiting for ADB mode'. When i run "adb devices" my device popups although in recovery mode or sideload mode. I cannot mount any device that should be available on internal storage. Also flashing the device using a zip file that's pushed to external storage (like twrp or cwm) in Philz Recovery won't stick . Also tried to repartition using a PIT file but no afail... (although it says it passed).
Seems like i'm screwed ...
Hi I'm having exactly the same problem with my Galaxy S3 GT-i9300. I get exactly the same logs from ADB, and get a write fail from Odin when I try to write a new PIT file.
Did you have any success resolving your problem? I'm starting to think I might need to replace the eMMC.
Thanks!!
Gibbitup said:
Hi I'm having exactly the same problem with my Galaxy S3 GT-i9300. I get exactly the same logs from ADB, and get a write fail from Odin when I try to write a new PIT file.
Did you have any success resolving your problem? I'm starting to think I might need to replace the eMMC.
Thanks!!
Click to expand...
Click to collapse
No sorry man mine is still gathering dust. Sent it in for repair wouldn't repair it because it is rooted .
Hi,
recently my Note 2 just died spontaneously. It was running as normal, suddenly it was off and instead of booting, it just hangs infinitely at the "Galaxy Note 2"-bootlogo.
I can still boot to recovery and download mode.
adb analysis shows this:
Code:
~ # dmesg | grep mmc0
<3>[ 2.034803] c2 mmc0: Version ID 0x5342240a.
<6>[ 2.035079] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.036574] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.065840] c0 mmc0: cmd 52 response timeout error
<3>[ 2.066686] c0 mmc0: cmd 52 response timeout error
<3>[ 2.070765] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071614] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072445] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073280] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074116] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074978] c0 mmc0: cmd 55 response timeout error
<3>[ 2.075840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.076699] c0 mmc0: cmd 55 response timeout error
<3>[ 2.077558] c0 mmc0: cmd 55 response timeout error
<3>[ 2.096727] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.096757] c0 mmc0: VTU00M: 15010056545530304df1e7ae5fd88fbf
<3>[ 2.179611] c0 mmc0: cmd 13 response timeout error
<6>[ 2.179697] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 2.180533] c0 mmc0: cmd 6 response timeout error
<3>[ 2.181359] c0 mmc0: cmd 6 response timeout error
<3>[ 2.182182] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183006] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183052] c0 mmc0: error -110 whilst initialising MMC card
Code:
~ # cat /proc/partitions
major minor #blocks name
Code:
~ # ls /dev/block
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
I was running CWM recovery and resurrection remix 5.6.9 (marshmallow). The flash of this ROM was maybe a week ago.
Recovery log is attached
Code:
mount: mounting /dev/block/mmcblk0p12 on /cache failed: no such file or directory
Does this mean that my eMMC is dead? Sudden death syndrome? Download mode still shows the device name. I'm wondering why I can still boot to recovery.
xkawer said:
Hi,
recently my Note 2 just died spontaneously. It was running as normal, suddenly it was off and instead of booting, it just hangs infinitely at the "Galaxy Note 2"-bootlogo.
I can still boot to recovery and download mode.
adb analysis shows this:
Code:
~ # dmesg | grep mmc0
<3>[ 2.034803] c2 mmc0: Version ID 0x5342240a.
<6>[ 2.035079] c2 mmc0: FIFO WMARK FOR RX 0x80 WX 0x40. ###########
<6>[ 2.036574] c2 mmc0: MSHCI controller on samsung-mshci [dw_mmc] using IDMA
<3>[ 2.065840] c0 mmc0: cmd 52 response timeout error
<3>[ 2.066686] c0 mmc0: cmd 52 response timeout error
<3>[ 2.070765] c0 mmc0: cmd 8 response timeout error
<3>[ 2.071614] c0 mmc0: cmd 5 response timeout error
<3>[ 2.072445] c0 mmc0: cmd 5 response timeout error
<3>[ 2.073280] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074116] c0 mmc0: cmd 5 response timeout error
<3>[ 2.074978] c0 mmc0: cmd 55 response timeout error
<3>[ 2.075840] c0 mmc0: cmd 55 response timeout error
<3>[ 2.076699] c0 mmc0: cmd 55 response timeout error
<3>[ 2.077558] c0 mmc0: cmd 55 response timeout error
<3>[ 2.096727] c0 mmc0: PERM_WRITE_PROTECT was set.
<6>[ 2.096757] c0 mmc0: VTU00M: 15010056545530304df1e7ae5fd88fbf
<3>[ 2.179611] c0 mmc0: cmd 13 response timeout error
<6>[ 2.179697] c0 mmc0 : disable PON feature : ffffff92 : 00(0e) : 00000000
<3>[ 2.180533] c0 mmc0: cmd 6 response timeout error
<3>[ 2.181359] c0 mmc0: cmd 6 response timeout error
<3>[ 2.182182] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183006] c0 mmc0: cmd 6 response timeout error
<3>[ 2.183052] c0 mmc0: error -110 whilst initialising MMC card
Code:
~ # cat /proc/partitions
major minor #blocks name
Code:
~ # ls /dev/block
loop0 loop2 loop4 loop6 ram0 ram10 ram12 ram14 ram2 ram4 ram6 ram8 vold
loop1 loop3 loop5 loop7 ram1 ram11 ram13 ram15 ram3 ram5 ram7 ram9
I was running CWM recovery and resurrection remix 5.6.9 (marshmallow). The flash of this ROM was maybe a week ago.
Recovery log is attached
Code:
mount: mounting /dev/block/mmcblk0p12 on /cache failed: no such file or directory
Does this mean that my eMMC is dead? Sudden death syndrome? Download mode still shows the device name. I'm wondering why I can still boot to recovery.
Click to expand...
Click to collapse
Have a look to this thread
http://forum.xda-developers.com/showthread.php?t=2501951
dr.harsh said:
Have a look to this thread
http://forum.xda-developers.com/showthread.php?t=2501951
Click to expand...
Click to collapse
Unfortunately, I can't access the drive on my PC. When I click on "mount system/cache/data/..." I just get "Error mounting /system/...". When I click "mount USB storage", nothing happens. The phone gets listed as "Universal Serial Bus devices/GT-N7100" in Device Manager, but explorer doesn't show it as a drive. The Samsung USB driver is installed, odin also detects it in download mode.
I'll try if I can flash stock with odin, should I try repartition with pit?
Flashing stock without repartition fails:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNE1_N7100DBTFNE1_N7100XXUFND3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)