Need the help of the greater minds here at xda on this.
A200 - unlocked bootloader - cwm (various flavors)
If booting CWM via vol-down / power, then everything is usually fine, sometimes I'll get the error described below, but rebooting again will clear it. and as long as this is the only way i boot into CWM, it's fine. dmesg shows a line showing that /cache mounts successfully.
If i do a "reboot recovery" from adb or terminal emulator (or even from Advanced->Reboot Recovery" from within cwm), then I get the /cache errors below. Happens everytime. But I can connect to it via adb while in cwm and do "mount /cache" and it mounts fine. Can't find any reference to cache being mounted in the dmesg log. It like it just not being mounted before recovery tries to access it.
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
The same recovery images works perfect on the A500 with the patched ics bootloader. I've tested with 3 versions of cwm. 1) cwm by hbwelch 2) thor1.7 repacked with the kernel from a200 ics stock recovery 3) modified a200 ics stock recovery with the /sbin/recovery file from thor1.7 image.
Any ideas why /cache doesn't mount when booting recovery w/o using the hardware keys?
Thanks
Figured it out. Recovery was starting before the block devices were created. Added a small delay and its working perfect.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
help
Euclid's Brother said:
Figured it out. Recovery was starting before the block devices were created. Added a small delay and its working perfect.
Sent from my SPH-D710 using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
how to ad a small delay please elebrate the steps.... please
adi_2012 said:
how to ad a small delay please elebrate the steps.... please
Click to expand...
Click to collapse
He added the delay to his program, there's nothing you need to do.
I added the delay in the unit.rc script in the thor 1.7 recovery thread I repacked for the a200. That's the one that is included in my app. if you use that one, you will not get the cache errors.
Sent from my SPH-D710 using Tapatalk 2
Related
Hi everyone! I'm new here, please don't shout at me!
Basically, I've been rooting and installing recoveries images all night. But I've run into a problem. I was going to flash to the Super-Hybrid HD-Desire ROM by MicroMod777 (link to thread: http://forum.xda-developers.com/showthread.php?t=784260) but it won't install, and now won't boot past the Nexus colour logo with the unlock bootloader padlock symbol at the botom. Here is what I did to get to this stage:
Followed these guides: http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
I then downloaded said ROM and put it in my SD card like it said, and booted into ClockWork from ROM Manager. I tried to flash it, but it didn't work, coming up with this error:
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Deleting files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
Copying files...
Copying files...
E:Can't mount/dev/block/mmcblk0p2
(File exists)
E:Can't mount SDEXT:
E:Failure at line 24:
copy_dir PACKAGE:ext SDEXT:
Installation aborted.
I then did a factory wipe, and that didn't work, so I wiped the cache partitions. Nothing worked, always the same error. I also did a restore before I tried to flash for the first time, I've tried to restore that, but it doesn't work either; it also says that it can't mount SD-EXT, but I don't know if this is the error.
I can still get into the bootloader (trackball + power buton) and get to recovery through there, and I saw someone say in a thread here that if you can get into the bootloader it is basically impossible to be bricked. The phone will also not mount when I connect it to the PC, however the PC knows it's there, as I can see the phone, and on fastboot's menu it says 'fastboot usb'.
I hope some of you guys can help me! I really do love my phone, I need it ASAP! Ideally, I'd get onto the ROM I mentioned above, but restoring it to factory settings would also be perfect. Whatever is easier!
Thanks
redbullcat
EDIT: I realised I posted this in the wrong section. It's not in Q/A section, at this link. A mod can delete this topic if needed.
Hi all,
Currently running Rom kitchen 2.2 (JVB based), along with fugumod 3.7 normal kernel, and armani modem.
Recently, every time i boot into recovery i get the following lines:
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
I can use all the functionality of the CWM interface, flashed other roms since etc, and it all works fine. I just get these messages - frustrating.
Im fairly sure they have only been present since flashing to 2.3.3 roms.
Any help as to how i can fix this?
(done a search, can't find anything useful)
Ali
I have the same error as you do. Can't restore any backups via CWM on top of that the USB storage mounting doesnt work properly any more. I can mount but windows just hangs when trying to access the internal or external SD.
Any help would be nice! Running Gingerbread too.
Same error here. running Juwes 4.3.1 with fugumod 3.8
I am not 100% sure... but it may be a kernel mismatch with the ROM you are using? Try changing to the Rom suggested Kernel and see if it fixes the issue...
Sounds like what happen to me last week.
check out my thread, hope it helps !
http://forum.xda-developers.com/showthread.php?t=1076055
Thanks guys.
Fixed mine by flashing 2.2.1 Rom using PIT file and re-partition via Odin.
hey @all,
I not allowed to write in the Development section. My post goes to "Lenovo Thinkpad CWR Port"
My System
18382DG
ThinkPadTablet_A310_02_0037_0076_WE
with 64 GB
I'm using http://everyrandom.com/files/download.php?file=538ventana64_recovery.img
in CWM-based Recovery v5.5.0.4
install zip from sdcard -> chosse zip from sdcard
"E:Can't mount /sdcard/
But when i connect over adb:
"# mount /sdcard"
this command works
advanced -> Show log
"failed to open /sys/class/android_usb/android0/state: No such file or directory"
this messages i got 12 times
http://everyrandom.com/files/downloa...4_recovery.img
I changed somthing in the OTA2 in ThinkPadTablet_A310_02_0039_0086_WE.zip
But the installation aborted. I added some print in update-script but didn't see that prints ?
Thanks.
Okay i solved Thema scard problem. The size of sdcard is the size of the extern sdcard. But i can't install any update.zip that i want. Is there any way to get some information why the installation stops ?
Sent from my ThinkPad Tablet using xda premium
MacGyver_Wildfire said:
Okay i solved Thema scard problem. The size of sdcard is the size of the extern sdcard. But i can't install any update.zip that i want. Is there any way to get some information why the installation stops ?
Sent from my ThinkPad Tablet using xda premium
Click to expand...
Click to collapse
Choose toggle signature verification then let us know.
Sent from my K1 using XDA
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
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
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
**UPDATE** 06/18/2012
by following this ( http://forum.xda-developers.com/showthread.php?t=919353 ) guide, i am able to get some result with sudo:
Code:
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
0000000000000000 recovery
Then I try entering the quoted commands and even attempt to edit them, but the result sucks:
Code:
[email protected]:~$ dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: opening `/sdcard/boot.img': No such file or directory
[email protected]:~$ sudo android-sdk-linux/platform-tools/adb shell
~ # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/sdcard/boot.img': No such file or directory
~ # dd if=/boot.img of=/dev/block/mmcblk0p1
dd: can't open '/boot.img': No such file or directory
~ # dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd: can't open '/sdcard/system.img': No such file or directory
the reason for this is that I can't mount the sdcard. if i could mount the sdcard, then this would be an easy fix and i never would have posted in the first place. using CWM 3.2.0.1 in place of nookie froyo since EVERY link for nookie froyo i have found has been a dead link or the instructions require mounting the sdcard which is the problem i am having. Also, CWM 3.2.0.1 and TWRP 3.2.0.1 or older are the ONLY things that actually allows the NC to turn on.
XSmoky said:
I have tried searching forums here and google and am just running in circles with same solutions to every problem except mine, the few times I HAVE seen a problem similar to mine, it has been added to an existing fix and no answer posted.
I have an old NC (stock 1.0.1) and quite a while ago i put a new honeycomb rom on it that worked great for a few days, then black screen. following various guides here I have seen the "need to update CWM" and all the like, but here is what I have and the problem:
I have CWM 3.2.0.1, I have tried a variety of restore to stock and custom roms, but it doesn't seem to matter what i add to the sdcard after writing the CWM image because no matter what I do (tried TWRP and got same results) I always get the following errors:
Turn on while plugged in with sdcard in --
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
When I try to follow directions found in one thread to format data and system --
Formatting /data...
Error formatting /data!
Formatting /system...
Error formatting /system!
When I try to mount sdcard --
Error mounting /sdcard!
When I try to mount USB --
E:Unable to write to ums lunfile (No such file or directory)
I am able to see the device with cmd adb devices...it gives me a bunch of 0's instead of the actual s/n and says "recovery" at the end of that line.
Have i managed to completely brick a NC or is there a way to fix this? I have learned quite a bit since I decided to try and fix the black screen, but nothing I have found has given me a solution to this.
I appreciate you guys being here and thanks in advance for any help you may have!
Click to expand...
Click to collapse
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
leapinlar said:
Look in my tips thread linked in my signature. There is an updated CWM SD listed there. Try using that. Read items A8 and A10.
Edit: I suspect your internal partitions are somehow corrupted. Search the threads for references to restoring stock partitions.
Click to expand...
Click to collapse
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
XSmoky said:
Ok, first of all, thanks for the fast reply. Second, with CWM 3.2.0.1, I can see the CWM menus and navigate them, however, with the 5.5.0.4 I am left with the black screen. I have so far attempted including restore zips and nothing but the 5.5.0.4 with no success.
I believe that somehow, with all my attempts to fix, the internal may be completely wiped, but I still find it strange that from a NC I can only use the 3.2.0.1 or older CWM or TWRP to get anything besides a black screen.
Click to expand...
Click to collapse
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
leapinlar said:
I suspect the 5.5.0.4 did not get burned properly and it is not trying to boot from it. It just is still trying to boot emmc which is corrupt. But I'm not sure that it would have done you any good anyway. Like I said in my edit above, I think you need to somehow rebuild your partitions. And that means more than just trying to flash a stock ROM. You have to find a thread that tells you how to use adb to rebuild the partitions.
Click to expand...
Click to collapse
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
XSmoky said:
I used win32diskimager and received no error messages, so i guess it was the long shot.
I have been digging through all kinds of recover partitions threads but have thus far been plagued by dead links. My searches for adb partitioning keeps showing me recovery zips that I have already tried multiple times. Atm I am working on IOMonster's method, but have my doubts.
I will post results and if I manage to find an ADB guide, I will link it or repost it with citations and keywords to make it easier to find
Click to expand...
Click to collapse
No error messages and being able to read in your PC does not necessarily mean it will boot from it.
But like I said, I'm not sure it would have helped you anyway. Did you look at this thread?
http://forum.xda-developers.com/showthread.php?p=25433167
Your problem is that your partitions have gotten corrupted.... you will need to dd some img's back to the nook... I have all of them available... but for /dev/block/mmcblk0p2 and 0p3 you will need to do some editing... since they are device specific.
If you're lucky... /dev/block/mmcblk0p3 is still "normal" and the device can recover 0p2 from the rombackup.zip on there... if not... editing is in your future.
Anyway... if you need the img files... I can make them available... have helped a few out with this problem.
Thanks guys, I'm gonna dual boot linux and get to work on the harder to do things now, but with my kids running around it'll take me some time to do.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
lufc said:
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Click to expand...
Click to collapse
Thought i was in the right place given other similar issues posted in same area, thanks for putting me in the right place.
****Moderator please delete this extra post****
Ive unlocked it and followed the proper steps to root it but when im in Clockworks mod or TWRP, I get the same "cannot mount" errors like unable to mount /data etc etc.
Thinking i did something wrong, i looked for an alternative and found wugs Nexus Root Toolkit 2.0.5
Everything runs smoothly, even did a successful factory flash to 5.1.1 and retried rooting.
Same errors, unable to mount. Im not sure whats causing these errors but would it have something to do with "secure boot enabled" ?
Ive been googling this since yesterday and I cant find a concrete answer as too why TWRP cannot mount or find anything.
Nexus 7 2013 LMY47V
Some errors:
E: Unable to find partition size for '/boot' and '/recovery' and '/misc'
E: Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '.data' is not present!
E: unable to recreate /data/media folder.
E: unable to find partition size for '/sbl1/
E: unable to mount '/system' and '/data' and '/cache'
Nothing? Am I missing something completely obvious? Sorry if I am, ive only ever rooted a kindle fire hd once a few years ago.
I guess ill be using no root firewall then? Funny thing I always though the adblock app needed root to work but its working without it.
Shame I cant remove hardware programs like "google +"
cerbyd said:
Ive unlocked it and followed the proper steps to root it but when im in Clockworks mod or TWRP, I get the same "cannot mount" errors like unable to mount /data etc etc.
Thinking i did something wrong, i looked for an alternative and found wugs Nexus Root Toolkit 2.0.5
Everything runs smoothly, even did a successful factory flash to 5.1.1 and retried rooting.
Same errors, unable to mount. Im not sure whats causing these errors but would it have something to do with "secure boot enabled" ?
Ive been googling this since yesterday and I cant find a concrete answer as too why TWRP cannot mount or find anything.
Nexus 7 2013 LMY47V
Some errors:
E: Unable to find partition size for '/boot' and '/recovery' and '/misc'
E: Primary block device '/dev/block/platform/msm_sdcc.1/by-name/userdata' for mount point '.data' is not present!
E: unable to recreate /data/media folder.
E: unable to find partition size for '/sbl1/
E: unable to mount '/system' and '/data' and '/cache'
Click to expand...
Click to collapse
Wow i have the same **** with mine same version and same device... you find a solution
I was having the same issue and after a few hours of searching, I found this post: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
It seems like there's a new version out that doesn't work quite as easily as just flashing the latest TWRP version.