Related
Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.
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!
Hello
I've just recently got a HTC Desire HD. I've rooted it with the help of aahk-11092012.
I've installed CM 7 first and it all worked fine.
A bit later I installed JellyTime ( http://forum.xda-developers.com/showthread.php?t=1778202 ).
This worked fine for about 2 days. Than, suddenly, the phone crashed. The screen went black and I the phone would not accept any key presses anymore. So I removed the battery and started the phone again. It hung on the htc-logo.
I was still able to get into recovery but it complained that it could not access the cache partition.
Upon further investigation i found out, that the partition table of the internal memory is broken. I could not mount or format any of the partitions. Factory reset just complained about that it could not access the partitions.
So i switched off the phone and started adb.
dmesg shows this
Code:
<6>[ 7.630279] rs30000048:00040000 rs30000048:00040000: setting system clock to 2012-11-23 20:51:58 UTC (1353703918)
<4>[ 7.630645] Warning: unable to open an initial console.
<6>[ 7.630828] Freeing init memory: 156K
<6>[ 7.739837] mmc0: new high speed MMC card at address 0001
<6>[ 7.740966] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<6>[ 7.741851] mmcblk0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 >
<4>[ 7.767913] mmcblk0: partition table partially beyond EOD, truncated
<4>[ 7.769744] mmcblk0: p28 size 42495 extends beyond EOD, truncated
<3>[ 7.816436] init: Unable to open persistent property directory /data/property errno: 2
And if I try to use parted I only get errors:
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print list
print list
Error: Can't have a partition outside the disk!
(parted)
The same error is show if I try to remove partitions.
When I try to write a new disklabel it just hangs there forever. No error message (also not in dmesg) or anything like this.
How can I fix the partition table of the internal memory and what do I have to do to get it to work again?
I guess that I will have to create a new partition table (and most probably destroy all the data on the internal memory in the process).
What will I have to reinstall in what order afterwards?
hboot?
cwm?
and how do I have to do this from the adb? Or is there a possibility do do this out of recovery?
I've tried several things in the meantime.
Ind the longer I try, the more I think that I have a bricked phone now since I seem to be unable to write anything to the emmc
I've tried to get back to the original firmware. So I copied the File PD98IMG.zip the the sd card, got into hboot and started the installation in hboot.
I could start it and it told me "Updating in progress, do not power off"
But there was no progress bar and after 10 minutes I pulled the battery. The phone is still in the same state as before so I think it did not write anything to the internal memory.
With fastboot, it seems to be the same. I can start fastboot on the phone aqnd it changes to "fastboot usb" when i plug the phone in. But every attempt to flash something to the phone just let's fastboot on the computer stop and hang (no message is shown, it's just sitting there and apparently doing nothing).
My computer system is debian linux btw.
I'm running out of ideas... please help... and it it's just the confirmation, that I have a bricked phone (that is long out of the warranty period anyway)
try with fastboot erase command. do google it a bit before you try
You have a full brick mate the EMMC is fried not amount of commands will fix it.
If you try fastboot getvar all then the try fastboot oem rebootRUU and the phone locks up its a new EMMC chip and jtag session to get it back online.
Google helps sometimes, you can also wipe out sectors on the emmc, because the partition table is corrupt.
http://archive09.linux.com/forums/topic/4033
Sent from my HTC Desire HD using Tapatalk 2
I have tried if he has the Dodgy EMMC doesn't matter what you try its fried and will not work. I have tried everything myself on a Bricked DHD with the Dodgy EMMC chip.
Hello, guys!
This morning I found my phone with black screen and not responding to power button. I pulled the battery out and tried to boot. The phone only showed the "Google" text on the black screen for several minutes (five, may be ten minutes) and did not respond to any buttons. At this point I pulled the battery for the second time and tried the recovery mode. The stock recovery booted after about a minute of "Google" screen. In stock recovery the only option I tried first time was "Wipe cache". It showed a static image of "work-in-progress" with static progress bar for several seconds and then returned to main recovery screen. I tried the "reboot" and received the black screen with no buttons working.
Pulled the battery and tried normal boot, which stuck on black "Google" stage.
Ok, I connected the phone to my laptop, and booted TWRP via fastboot, it took a little longer to boot, but at least I managed to "adb-shell" it and grab dmesg output. This is the relevant part (containing "mmc" word):
Code:
<6>[ 2.828399] mmc0: new high speed MMC card at address 0001
...
<6>[ 2.829101] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.829345] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 2.829681] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 2.835021] Reprogramming LPDDR2 timings to 400000000 Hz
<3>[ 2.836090] Power Management for TI OMAP4.
<6>[ 2.836334] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
<6>[ 2.836517] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
<4>[ 2.837432] sr_init: No PMIC hook to init smartreflex
<6>[ 2.837799] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838073] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838317] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838592] sr_class1p5_driver_init: OMAP4460: add 10mV margin for class 1.5
<6>[ 2.838928] SmartReflex class 1.5 driver: initialized (86400000ms)
<6>[ 2.839569] mmcblk0boot1: unknown partition table
<6>[ 2.840728] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 2.840972] mmcblk0boot0: unknown partition table
...
<4>[ 3.851135] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3.899353] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3.915679] mmc1: new high speed SDIO card at address 0001
<4>[ 3.917633] F1 signature read @0x18000000=0x16844330
<4>[ 3.927154] DHD: dongle ram size is set to 294912(orig 294912)
...
<3>[ 7.677093] mmcblk0: timed out sending r/w cmd command, card status 0xe00
<3>[ 7.677276] mmcblk0: not retrying timeout
<3>[ 7.677581] end_request: I/O error, dev mmcblk0, sector 1495040
<3>[ 7.677764] Buffer I/O error on device mmcblk0p11, logical block 0
<4>[ 7.678100] lost page write due to I/O error on mmcblk0p11
<6>[ 7.678802] EXT4-fs (mmcblk0p11): recovery complete
<6>[ 7.679138] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 8.737213] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737304] mmcblk0: command error, retrying timeout
<3>[ 8.737426] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737548] mmcblk0: command error, retrying timeout
<3>[ 8.737701] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737762] mmcblk0: command error, retrying timeout
<3>[ 8.737915] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
...
and a lot of I/O errors with mmcblk0 block device
Reading from /dev/block/mmcblk0 constantly fails, even the first sectors (dd if=/dev/block/mmcblk0 of=/dev/null).
I pulled the battery out, left the phone and rushed to the work.
With my little knowledge it looks like broken sdcard itself or sdcard controller. Does it make any sense? Is it possible to repair it easily? I realize I cannot simply replace sdcard, as it most likely soldered in the board, but how hard is it to replace if I have the equipment and spare parts?
Another question: as I can boot TWRP recovery via fastboot, is it theoretically possible to find and boot a custom kernel, which does not require internal storage at all, like some stripped kernel which works only in RAM, but still provides the basic functions like phone calling, wifi browsing and something like this?
Any help would be greatly appreciated!
Try restoring your phone to stock using ODIN
http://forum.xda-developers.com/showthread.php?t=1827685
I think the PIT file should repair your partition table if it's just a software problem
Thanks for the tip. I guess I will try odin methods only as as a last resort since it may void my warranty. I am still positive about sending my unit to the service center in January.
At the moment fastboot methods do not work if they try to actually write something. fastboot boot works pretty good.
Looks like a bad partition, ODIN back to factory wont void your warranty. All it does is reset your phone to the stock image, that's probably what they'll do when you send it in for warranty repair. Save yourself the time and trouble.
Bad blocks is something software won't fix. This is a hardware problem with the flash memory and it needs replaced.
I had something like this happen when I was formatting my /data partition in TWRP. I did a factory reset and it was like "wiping /data without wiping /data/media" and just to be on the safe side I wiped /data and it froze and when I got control back it said that it couldn't format it or anything so I ended up restoring the factory image and that fixed everything.
varet tviengt
Once again, just to be on the safe side, I will not try ODIN factory reset just yet. As it may be the hardware problem and I may end up with phone-triangle-computer state, in which case my warranty might be rejected like I messed something up myself blah-blah-blah.
The problem with the warranty is that I should go to my home, and I am now several thousands kilometers away from it on a vacation. So I will just wait for it.
I'm having the exact same problems for the last few weeks. Did you fix it? If so, how?
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have a GNexus 4.2.2 stock and I have reboot problem from the last week.
in the last_kmsg(attached) I read many references to mmc problems, for example
Code:
[ 5213.429595] mmcblk0: timed out sending r/w cmd command, card status 0x900
[ 5213.429779] mmcblk0: not retrying timeout
[ 5213.429901] end_request: I/O error, dev mmcblk0, sector 2450976
[ 5213.430084] end_request: I/O error, dev mmcblk0, sector 2450984
[ 5213.430175] end_request: I/O error, dev mmcblk0, sector 2450992
[ 5213.430328] end_request: I/O error, dev mmcblk0, sector 2451000
[ 5213.430450] end_request: I/O error, dev mmcblk0, sector 2451008
[ 5213.430603] end_request: I/O error, dev mmcblk0, sector 2451016
[ 5213.430694] end_request: I/O error, dev mmcblk0, sector 2451024
[ 5213.430847] end_request: I/O error, dev mmcblk0, sector 2451032
[ 5213.431091] Aborting journal on device mmcblk0p12-8.
I have already restore the Factory Images from Google developer, but I don't solve.
Is damage the memory or is a software problem?
up
Any news here? Since a few days I'm experiencing the same problem .
I have sane issue ! Any info for us ?
Inviato dal mio Galaxy Nexus usando Tapatalk 4
I am experiencing this problem too. Often apps crash when SQLite tries to write something to disk: Disk I/O error (code 1034).
I'm also getting random reboots and corrupted files.
This happens both with CM11-M2 and stock 4.3 ROM, so I don't think it's a software problem.
Do you think the internal storage is dying? Is there something I can do? Thanks!
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