[solved]BRICKed: inside eMMC's dead, with E:Can't open /cache/recovery/log

Search This thread
By:
Advanced…
M

m.s.khan

Member
Jan 11, 2013
7
0
Mumbai
not wipe userdata

Hi, Friends I have a tablet model No sanei N83 delux but it now lock with google username and password I am wiping this by adb or fastboot
when I am connecting with ADB or Fastboot it's connected but when I am wiping then it's show me this massage ''Error opendir' ing /data ' Permission denied'
so any body give me the best solution to solve it
Thanks in advance
 
jugg1es

jugg1es

Senior Member
May 29, 2012
13,282
1,938
m.s.khan said:
Hi, Friends I have a tablet model No sanei N83 delux but it now lock with google username and password I am wiping this by adb or fastboot
when I am connecting with ADB or Fastboot it's connected but when I am wiping then it's show me this massage ''Error opendir' ing /data ' Permission denied'
so any body give me the best solution to solve it
Thanks in advance
Click to expand...
Click to collapse

This is the htc desire s forum, this question would receive a better response if you put it in the general Q&A.

Either write something worth reading or do something worth writing.
Benjamin Franklin
 
P

pychu88

New member
Mar 31, 2013
2
0
I searched a lot and still can't find answer for this

So, my first question is: do you know any other way to restore my phone to S-ON and stock? (besides those I mentioned above) This is to avoid the chance of htc voiding my warranty.
Click to expand...
Click to collapse

I've got htc desire Z and can not find possibility for s-on - matter for warranty :(

when i try to upload img through fastboot or PC10IMG.zip file on SD card there is fail or fail-PU

fortunely i ran the phone with this method
http://xdaforums.com/showthread.php?t=1572924
but it's not the solution..

if there is no chance to make it s-on the phone phone will go in the microwave oven to kill mother board, i tried piezoelectric lighter but mu DZ still alive :p


the question is:
is tehere any way to restore phone to S-ON and stock when the eMMC is fried ?
 
jugg1es

jugg1es

Senior Member
May 29, 2012
13,282
1,938
pychu88 said:
I searched a lot and still can't find answer for this



I've got htc desire Z and can not find possibility for s-on - matter for warranty :(

when i try to upload img through fastboot or PC10IMG.zip file on SD card there is fail or fail-PU

fortunely i ran the phone with this method
http://xdaforums.com/showthread.php?t=1572924
but it's not the solution..

if there is no chance to make it s-on the phone phone will go in the microwave oven to kill mother board, i tried piezoelectric lighter but mu DZ still alive :p


the question is:
is tehere any way to restore phone to S-ON and stock when the eMMC is fried ?
Click to expand...
Click to collapse

If the emmc is fried, does it matter?

"In the end, everything is a gag."
- Charlie Chaplin (1889-1977)
 
P

pychu88

New member
Mar 31, 2013
2
0
Thank you for answer.
Reason for making it S-ON is warranty of corse ;)

when htc service will see the phone is modified, they immediately reject my warranty.

So there are two options:
- S-ON - to avoid warranty rejection
- Damage to the phone to such a state that it was not possible to verify whether it was modified - of course, with no evidence of physical interference ( I use this method with older phones like Nokia ;) )
 
P

paulie-uk

Senior Member
Mar 9, 2013
76
65
London
Snakeforhire said:
Catching the thread incidentally, haven't read all the latest developments, but to answer your question : Most likely. the Desire S and the G2/DesireZ are very similar as far as hardware goes. YMMV but by and large this holds true for .zipfiles that don't need a very low-level hardware access (=most of them, in practice).
Click to expand...
Click to collapse

Does this mean we can flash G2/Z radio/hboot/kernel, use gfree to radio S-OFF, supercid, and then flash back to SAGA radio/hboot/kernel ?
 
P

paulie-uk

Senior Member
Mar 9, 2013
76
65
London
Jack_R1 said:
I tried doing this, the kernel doesn't boot. If one could create working Froyo kernel for DS - then gfree would be a viable option.
Click to expand...
Click to collapse

I know this is a bit of a long shot, but isn't the hardware in the Incredible S (Vivo) really similar to that in the Desire S (Saga), too? That device did ship with Froyo. I can't seem to find references to using gfree to S-OFF, but rather a different tool named incsfree that requires the old radio for that device as well. Depending how our mmcblk0p7 is compared to the other phones I'm not sure which tool we'd need, but if Froyo can run then this route has hope.

You didn't also test putting these onto your Desire S perchance, did you?

It'd be nice to make the move from ENG S-OFF to Radio S-OFF & SuperCID, and have a truly unlocked phone.
 
Last edited:
N

nemesisam

Member
Jun 14, 2012
12
1
Hi people, a question if I may. My adb commands show that:
~ # cat /proc/kmsg | grep mmc0
cat /proc/kmsg | grep mmc0
<3>[ 2.036253] mmc0: No card detect facilities available
<6>[ 2.036619] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18

<6>[ 2.036741] mmc0: Platform slot type: MMC
<6>[ 2.036833] mmc0: 8 bit data mode enabled
<6>[ 2.037016] mmc0: 4 bit data mode disabled
<6>[ 2.037107] mmc0: polling status mode disabled
<6>[ 2.037290] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.037382] mmc0: Slot eject status = 0
<6>[ 2.037504] mmc0: Power save feature enable = 1
<6>[ 2.037687] mmc0: DM non-cached buffer at ff008000, dma_addr 0x57473000
<6>[ 2.037779] mmc0: DM cmd busaddr 0x57473000, cmdptr busaddr 0x57473300
<6>[ 2.171079] mmc0: new high speed MMC card at address 0001
<6>[ 2.171690] mmcblk0: mmc0:0001 MLL00M 2.25 GiB

So I guess my emmc-chip is OK. Why does RUU stucks at 34% if everything is OK??? It has beeb around a month since my recovery (TWRP) corrupted my inernal storage and I managed to make everything mountable. No RUU works though and no custom ROM can be flashed in my phone... Any kind sir to help please?

PM I guess I have searched every thread but I can find no answer other than SD mounted ROM(which is TOO slow) T_T
 
You must log in or register to reply here.

Similar threads

ben_pyett
[INDEX][29 JUN 14] INDEX of ROMS/RECOVERY/ROOT/GUIDES/HBOOT/RADIOS/TWEAKS etc
Replies
251
Views
760K
talayy
talayy
blindndumb
[DISCONTINUED][ROM][19 FEB 13][JB 4.2.2] Android Open Kang Project - R5.0 - SAGA
Replies
2K
Views
482K
niravnn
niravnn
alirez_sos
  • Locked
[ROM][Mar 27] Sabsa Prime v16.0 | 4.0.4 | Full Sense 4.1 | Legendary | Brilliant
Replies
1K
Views
392K
rwilco12
rwilco12
proxuser
[ROM] Saga3D v5.1.0 Desire S official Sense 3.0 - fast, stable, aroma installer
Replies
2K
Views
552K
teadrinker
teadrinker
n0elite
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Replies
596
Views
226K
D
DenisZabar

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    opumps
    opumps
    hi guys, this problem was solved, unexpectedly.



    after read guhl99's post in Thread: PSA: Rooting methods and recently discovered dangersthread,
    i finally confirm that my htc DS was bricked by an accidentally freeze and the immediately battery pulled-out-&-pushed-in unstably.
    the eMMC-chip(marked as SAMSUNG104, KLM4G2DEJE A001, FDAE15PC) was completely dead,
    i made a replacement with a new one(made by Sandisk serial:SEM04G), and then everything goes on good.


    IMAG0003.jpg IMAG0004.jpg



    "Thanks to" the design of the battery compartment door, the battery pullout-pushin becomes running-risks.
    Make sure there's NOT any tiny battery move when you flipping the compartment door from the side.
    Make sure disconnect the battery and DS itself quickly & stably as soon as you could.
    Make sure there's at least 10 seconds between battery pullout and pushin.


    "How can I be sure if it's a hw problem? I mean, it looks like one, but I would like to be sure..."
    please check #27 http://xdaforums.com/showpost.php?p=16135893&postcount=27


    A eMMC design flaw, Confirming info from htc-offical (thanks apairofscissors)
    http://xdaforums.com/showpost.php?p=20163494&postcount=23




    =============Debug Procedure=============
    Here are 3 parts in this post.
    Actually, it's not that long,
    and the most important info is in 8. [ adb shell ]


    ================Background================
    SAGA PVT SHIP S-OFF RL
    HBOOT-0.98.00RADIO-38.03.02.15_M
    eMMC-boot
    Mar 10 2001,14:58:38
    ClockworkMod Recovery 3.2.0.0
    a busybox within

    ================what happend================
    while installing some apps from the market, DS was stuck at a app called "push ups".
    i pulled out battery and reboot, and there came loopboot.
    got in Recovery, it promts
    Code: 
    E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log

    ================things i did================
    1. [ wipe data/factory reset]
    Code: 
    Formating /data...
black splash screen, and then
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
    [ wipe cache ]
    Code: 
    Formating /cache...
Cache wipe complete.
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
    2. [ install zip from sdcard ]
    Code: 
    -Checking Model ID
-success!
 -Model ID - HTC sage
Now flashing
E:Error in /sdcard/*******.zip
(Status 1)
Installation aborted.
    3. [ backup and restore ]
    Code: 
    Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoreing system....
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
    4. [ RUU+Goldencard ]
    Goldencard is good, in FASTBOOT USB mod,
    passed the (version) checking, updating 1.28.401.1 to 1.47.950.3, but stuck at
    Code: 
    rebooting bootloader ......
upgrading ROM image in your Android Phone...
Please do NOT disconnect USB cable nor run any program.
    5. [ ROM.zip->PG88IMG.zip ]
    ROM.zip was picked-up from RUU, renamed to PG88IMG.zip, copied to sdcard,
    reboot to HBOOT, and it unzip the pack normally, then stuck at updating screen, more than 1 hour.
    Code: 
    HBOOT
[INDENT]Parsing...[SD ZIP]
[1] BOOTLOADER                  -updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SLPASH1
[6] USERDATA
[7] TP
[8] DADIO_V2
[9] RADIO_CUST
Do you want to start update?
[/INDENT]


    6. [ PG88IMG.zip for Recovery/Radio ]
    HBOOT asks do you wanna upgrade, click VOL-up, then stuck at updating screen
    Code: 
    HBOOT
[INDENT]Parsing...[SD ZIP]
[1] RECOVERY                  -updating
*********
Updating is in progress...
Do not power off the device!
[/INDENT]


    7. [ fastboot ]
    Code: 
    SH********8 Connected.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
Radio version: 38.03.02.15_m.
SPL/hboot version: 0.98.0000.
product: saga.
mid: pg88*****.
security: off.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
 
[B]fastboot erase cache[/B]
erasing 'cache'...
[COLOR=red]erasing 'cache'... FAILED (command write failed (Unknown error))[/COLOR]

    8. [ adb shell ]

    DS has 2 storages:
    eMMC-chip inside, /system /data /cache are mounted to mmcblk0p25, mmcblk0p26, mmcblk0p27;
    SDCard removable /sdcard is mounted to mmcblk1p1.

    i connect the my phone(DS-brick) through adb-shell, and compared with my friend's (DS-good), here are the prompts:

    DS-good shows
    Code: 
    mount
rootfs on / type rootfs (rw)
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)
/dev/block/[COLOR=blue]mmcblk0p25 on /system type ext3 [/COLOR](rw,relatime,errors=continue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk0p26 on /data type ext3[/COLOR] (rw,relatime,errors=continue,barrier=0,
data=writeback)
/dev/block/[COLOR=blue]mmcblk0p27 on /cache type ext3 [/COLOR](rw,nodev,noatime,nodiratime,errors=co
ntinue,barrier=0,data=writeback)
/dev/block/[COLOR=blue]mmcblk1p1 on /sdcard type vfat[/COLOR] (rw,relatime,fmask=0000,dmask=0000,all
ow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-
ro)
    DS-brick shows
    Code: 
    /dev/block/[COLOR=blue][COLOR=red][B]mmcblk0p27 on /cache type ext4[/B][/COLOR] [/COLOR](ro,nodev,noatime,nodiratime,barrier=1
,data=ordered)
 
~ # mount system
mount: mounting /dev/block/mmcblk0p25 on /system [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
~ # mount data
mount: mounting /dev/block/mmcblk0p26 on /data [COLOR=red][B]failed: Invalid argument[/B][/COLOR]
    it means the filesystem on eMMC was accidentally broke down. so, im trying to restore the filesystem, and get these:

    list the eMMC-chip partition info
    Code: 
    ~ # fdisk -l /dev/block/[B]mmcblk0[/B]
fdisk -l /dev/block/mmcblk0
[B][COLOR=red]fdisk: can't open '/dev/block/mmcblk0': I/O error[/COLOR][/B]

    format /cache with type ext3
    Code: 
    ~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p27[/COLOR]
mke2fs 1.40.8 (13-Mar-2008)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
76912 inodes, 307196 blocks
15359 blocks (5.00%) reserved for the super user
[B]First data block=1[/B]
Maximum filesystem blocks=67633152
38 block groups
8192 blocks per group, 8192 fragments per group
2024 inodes per group
Superblock backups stored on blocks:
        8193, 24577, 40961, 57345, 73729, 204801, 221185
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=red][B]ext2fs_mkdir: Attempt to read block from filesystem [/B][/COLOR]
[COLOR=red][B]resulted in short read while creating root dir[/B][/COLOR]
    format /system with type ext3
    Code: 
    ~ # mke2fs -j /dev/block/[COLOR=blue]mmcblk0p25[/COLOR]
mke2fs -j /dev/block/mmcblk0p25
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
35760 inodes, 142847 blocks
7142 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
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
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue][B]Creating journal (4096 blocks): done[/B][/COLOR]
[COLOR=blue][B]Writing superblocks and filesystem accounting information: done[/B][/COLOR]
[COLOR=blue][B]This filesystem will be automatically checked every 39 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first.  Use tune2fs -c or -i to override.[/B][/COLOR]
    format /data with type ext3
    Code: 
    mke2fs -j /dev/block/mmcblk0p26
mke2fs 1.40.8 (13-Mar-2008)
Warning: 256-byte inodes not usable on older systems
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
75200 inodes, 300799 blocks
15039 blocks (5.00%) reserved for the super user
[B]First data block=0[/B]
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 
[COLOR=blue]Warning: could not read block 0: [/COLOR]
[COLOR=blue]Attempt to read block from filesystem resulted [/COLOR][COLOR=blue]in short read[/COLOR]
[COLOR=blue]Writing inode tables: done[/COLOR]
[COLOR=blue]Creating journal (8192 blocks): done[/COLOR]
[B][COLOR=blue]Writing superblocks and filesystem accounting information: done[/COLOR][/B]
[COLOR=blue][B]This filesystem will be automatically checked every 22 mounts or[/B][/COLOR]
[COLOR=blue][B]180 days, whichever comes first.  Use tune2fs -c or -i to override[/B][/COLOR].
    View
    3
    D
    dave303
    Well... after a long night... I had all of the symptoms described by everyone here, however mine came back from the dead after a stock RUU update from fastboot. I *HOPE* at least a small percentage of people were as lucky as me... details on my blog... which I can't link here as this is my first post..

    search for it if you're interested (dave heavy industries) for the full recount of events, otherwise the nitty gritty is that after following the instructions to work out of your MMC is screwed, I decided to try and get rid of clockworkmod and try my luck at a warranty job. I couldn't get fastboot to flash boot.img or recovery.img so instead I ran the htc telstra RUU while the phone was in fastboot and BLAMMO! success.
    Re-rooted, Re flashed, now 100% up and running... very happy (relieved) camper.
    View
    2
    C
    craigcharlie
    Cliff notes: I think the Hboot “Factory Reset” option cured my problem.

    Details:
    I had lots of “status 1″ errors and phone wouldn’t go past the white HTC logo. I was about to start looking for RUUs when I did this:

    I turned off the phone again (using the trick of volumeup/volumedown/power buttons together) and quickly removed the battery again.

    I rebooted into Hboot (volumedown/power together). From there, just for the heck of it, I selected the “Factory Reset” option. (I’m on the Hboot installed by the Revolutionary tool http://revolutionary.io/, don’t know if ALL Hboots have this option). I didn’t know if this would be different than the recovery tool wipe, but I thought I’d try.

    After I selected this the phone rebooted and went to recovery. When I tried to reinstall the CM 7.1 ROM zip, which failed previously with status 1, it worked.

    Phone seems fine now. Hope this helps someone.
    View
    1
    zorbakun
    zorbakun
    Well, I'm quite sure the DS default partition format is ext4, mine is like wise ext4, you have got nothing to lose there, try to flash that customer recovery and format or convert your phone partitions to ext4, then flash any of the customs roms available around or a RUU if you want.
    View
    1
    InfernalByte
    InfernalByte
    The easiest way to rectify is to RUU and start over. Unless you enjoy the frustration!
    View

New posts