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****
Hello,
I tried to move from one rom to another, but it seemed that the device got bricked.
Currently, it has Skrilax_CZ's bootloader v8 and TWRP recovery 2.6.3, which is working.
The problem is, that the file system got messed up, i think. When i start the recovery i see the following in the console:
Code:
Unable to mount '/data'
Unable to recreate /data/media folder.
Unable to find partition size for '/misc'
Unable to find partition size for '/boot'
Unable to find partition size for '/recovery'
Unable to find partition size for '/system'
Unable to find partition size for '/data'
Unable to find partition size for '/cache'
Unable to find partition size for '/flexrom'
Unable to find partition size for internal storage
Unable to set emmc bootloader message.
I see most of the folders in the file explorer in the recovery but they are all empty.
I tried wiping everything but still got errors. When i try to install any ROM, i get the same errors.
EDIT:
I installed older version of TWRP - v.2.4.4. There seems to be less errors with it. When i try to restore from a backup now i get: "Restoring data..." and the message ERROR after that. Interestingly, the CPUID now is all zeroes (000....) instead of the original one, which i have written down.
I think that some system directories are missing, but i may well be mistaken. Is there a way to recreate them?
Any suggestions?
EDIT #2:
I solved it! After a lot wondering i came upon this thread: http://forum.xda-developers.com/showthread.php?t=1516012
It helped me to get the tablet working with the stock rom, in case anybody else gets stuck like me. That is why it is very important to write down the CPUID!
Well thats a new one...I'd say yr memory chip is hosed. To have yr cpuid reported like that doesn't sound good. Try runnng babsector.rar to reset partitions...see post 2 in my root guide in my sig
Sent from my GT-I9300 using Tapatalk 4
---------- Post added at 06:37 AM ---------- Previous post was at 06:33 AM ----------
Wow awesome, yep that euu can also reset partitions. As u say, keeping yr cpuid safe is THE most important things you can do...well done!
Sent from my GT-I9300 using Tapatalk 4
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.
Hi,
i'm pretty new to this and i have kinda big problem. I had MIUI 7 rom installed on my S4 I9505, but yesterday after the update phone wont boot. I downloaded new .zip file, put it on SD card, boot into recovery, wipe everything and tried to install new rom. With no succes. I tried 3 differrent roms, i even tried with diffirent recovery, still nothing.
This is what it says:
Installing: /storage/sdcar1/cm-12.1-20151106-NIGHTLY-jfltexx.zip
Finding update package
Opening update package
Installing update
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by_name/userdata
Patching system image unconditionally...
And that's it. Previosly i was getting errors, status 0 and status 7 if i remmember correctly, but now not even that
Now what to do? Please be noob friendly At this point i don't even care any more what rom to install, stock or custom, but i think i would prefer stock.
Thanks for your help!
Edit: I found this guide, will it do it? forums.androidcentral.com/ambassador-guides-tips-how-s/499009-guide-samsung-how-flash-stock-rom-via-odin-new-interface.html
It worked. Admin, you can close/delete this thread.
What is the vendor section that appears when you want to do an advanced wipe? And why does it come out on some mobiles and not on others?
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
NOTE: I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources like this and many others. This information is according to best of...
forum.xda-developers.com
So if in twrp it says that it is impossible to mount vendor (invalid argument) is it something bad or does it not matter?
The_severo said:
So if in twrp it says that it is impossible to mount vendor (invalid argument) is it something bad or does it not matter?
Click to expand...
Click to collapse
it doesn't matter