Document the Story of Your Social Life with 8tory

The different forms of social media are growing every day. It’s hard to imagine a day … more

Make Calling Your Loved Ones Easier and Cheaper this Diwali

Diwali, or Deepawali as some Indians call it, is the pride and joy of Indian … more

Big Android BBQ 5.0 Recap – XDA TV

This fifth annual Big Android BBQ has come and gone. The speakers have spoke, the sponsors have … more

Microsoft to Counter “OK Google” with Bing Torque

When Microsoft is making apps for Android, users should be aware that something … more
Post Reply

[Q] Stuck in Bootloader (cache does not mount)

OP Jini.Dough

17th May 2014, 02:54 PM   |  #1  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: May 2014
I tried to install cyanogenmod (cm-11-20140504-SNAPSHOT-M6-m4.zip) and in the process I probably did something wrong

Any help is highly appreciated.

The header in the unlocked bootloader is:

Code:
*** TAMPERED ***
*** UNLOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000 
RADIO-1.24.40e.00.26
Recovery can be easily flashed via

Code:
sudo fastboot flash recovery recovery-clockwork-touch-6.0.4.8-m4.img
After selecting "BOOTLOADER" > "RECOVERY", I get the error messages

Code:
ClockworkMod Recovery v6.0.4.8
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
After sideloading "adb sideload cm-11-20140504-SNAPSHOT-M6-m4.zip", I receive the following error messages

Code:
Restarting adbd...
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: File exists
Finding update package...
Opening update package...
Installing update...
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
If anybody can help me, that would be great. (Flashin the Nexus4 was so much more fun )
17th May 2014, 03:24 PM   |  #2  
AnGrY sCoTsMaN's Avatar
Senior Member
Flag Scotland
Thanks Meter: 116
 
264 posts
Join Date:Joined: Nov 2011
More
Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6 from here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m4
or twrp 2.7.0.8 from here http://mdmower.cmphys.com/twrp-m4/
these two support the new partition layout.
Last edited by AnGrY sCoTsMaN; 17th May 2014 at 03:26 PM.
17th May 2014, 03:55 PM   |  #3  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by Braddison

Ive not seen a cwm v6.0.4.8 for the Htc Mini (m4) i could be wrong?
either try flashing philz latest touch recovery v6.41.6
or twrp 2.7.0.8
these two support the new partition layout.

With philz and twrp I get the same behaviour (warnings and errors).
17th May 2014, 04:20 PM   |  #4  
AnGrY sCoTsMaN's Avatar
Senior Member
Flag Scotland
Thanks Meter: 116
 
264 posts
Join Date:Joined: Nov 2011
More
Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers
17th May 2014, 05:56 PM   |  #5  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by Braddison

Try changing the name of your recovery "recovery-clockwork-touch-6.0.4.8-m4.img" to just "recovery.img" (its easier and less chance of a typo)
then try this sudo fastboot flash recovery /path/to/recovery.img
hopefully that will give you a working recovery,if that fails do the same with a different recovery
hope that helps,cheers

I am not sure why renaming the file would help, but I did anyway.
Still, I get the same errors.
17th May 2014, 06:27 PM   |  #6  
AnGrY sCoTsMaN's Avatar
Senior Member
Flag Scotland
Thanks Meter: 116
 
264 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by Jini.Dough

I am not sure why renaming the file would help, but I did anyway.

as stated in previous post, it's for ease of use and less likely to make a spelling mistake causing things to go t*ts up


am thinking your partitions are messed up,
Last edited by AnGrY sCoTsMaN; 17th May 2014 at 08:25 PM.
17th May 2014, 08:42 PM   |  #7  
410eaL's Avatar
Member
Thanks Meter: 7
 
63 posts
Join Date:Joined: Mar 2012
try used twrp1 2.7.0.8 recovery

Sent from my HTC One mini
17th May 2014, 09:39 PM   |  #8  
mypat's Avatar
Senior Member
Flag iSTaNBuL
Thanks Meter: 444
 
424 posts
Join Date:Joined: Aug 2012
Donate to Me
More
did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?
18th May 2014, 02:05 PM   |  #9  
OP Junior Member
Thanks Meter: 0
 
4 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by 410eaL

try used twrp1 2.7.0.8 recovery

I am not sure if I do understand what you mean by twrp1. Do you have a link.

Quote:
Originally Posted by mypat

did you tried OTG option inside of the twrp via OTG cable and usb flashdisc?

No, I did not try this. I am not sure if I have an OTG cable.

Since mounting of cache seems the main problem, I tried to get some information about the partitions. Does anybody recognize if these partitions are OK or if I do have to apply some change here:

Code:
adb shell
~ # cat /proc/partitions
major minor  #blocks  name

 179        0   15392768 mmcblk0
 179        1        128 mmcblk0p1
 179        2        256 mmcblk0p2
 179        3     130671 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5         16 mmcblk0p5
 179        6        256 mmcblk0p6
 179        7      15577 mmcblk0p7
 179        8        256 mmcblk0p8
 179        9       1024 mmcblk0p9
 179       10        256 mmcblk0p10
 179       11       2048 mmcblk0p11
 179       12       2080 mmcblk0p12
 179       13       5120 mmcblk0p13
 179       14       1024 mmcblk0p14
 179       15       1024 mmcblk0p15
 179       16      46080 mmcblk0p16
 179       17      10240 mmcblk0p17
 179       18       5120 mmcblk0p18
 179       19       8190 mmcblk0p19
 179       20       4096 mmcblk0p20
 179       21      28671 mmcblk0p21
 179       22       1022 mmcblk0p22
 179       23       4096 mmcblk0p23
 179       24       4096 mmcblk0p24
 179       25      20480 mmcblk0p25
 179       26          4 mmcblk0p26
 179       27        256 mmcblk0p27
 179       28         16 mmcblk0p28
 179       29       1280 mmcblk0p29
 179       30         64 mmcblk0p30
 179       31       1448 mmcblk0p31
 179       32      32767 mmcblk0p32
 179       33      16384 mmcblk0p33
 179       34      16383 mmcblk0p34
 179       35    2195455 mmcblk0p35
 179       36     688127 mmcblk0p36
 179       37   11927552 mmcblk0p37

~ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   399632       128    399504   0% /dev
tmpfs                   399632         8    399624   0% /tmp
tmpfs                   399632         0    399632   0% /storage
tmpfs                   399632         0    399632   0% /mnt/secure
tmpfs                   399632         0    399632   0% /mnt/fuse

~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
To me it appears as if /cache does not even exist anymore. The recovery seems to be OK, since the selinuxfs is used for a sys-partition.

Braddison, do you know how to fix the partition?
Last edited by Jini.Dough; 18th May 2014 at 02:56 PM. Reason: Typo
18th May 2014, 05:01 PM   |  #10  
AnGrY sCoTsMaN's Avatar
Senior Member
Flag Scotland
Thanks Meter: 116
 
264 posts
Join Date:Joined: Nov 2011
More
Quote:
Originally Posted by Jini.Dough


Braddison, do you know how to fix the partition?

Iím afraid I donít.

I would try the above recoveries ensuring that they are copied in your fastboot folder , and spelled exactly the same when flashing.
Then try a different rom other than CM , just to see if you can boot . can always flash cm at a later date from recovery.
Hopefully someone on here will come to the rescue.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes