Database Users

[Q] Help Please? Old NC being a pain

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****

[Q&A] [MOD][TWRP][RECOVERY] Reclaim the whole free space of your system partition

Q&A for [MOD][TWRP][RECOVERY] Reclaim the whole free space of your system partition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][TWRP][RECOVERY] Reclaim the whole free space of your system partition. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Khaon said:
Hello,
many users complain that since lollipop their system partition size doesn't reflect the actual system of the block device. Therefore, they can not install some extra in this partition( busybox, big gapps packages,etc.).
This is due to the system image size specified when building the rom:
One of the parameter of your system partition(which has been hardcoded in some config file, I.e. BoardConfig) is its size, but if the block device(i.e. the part of your internal storage that will be mounted for the system partition)'s size that is mounted is larger than the system partition's size than you will loose some space.
Fortunately resize2fs executable allows to modify an ext2,ext3,ext4 partition size:
This package simply resizes your system size to match the size of your block device size.
It does not alter your partitions table just reclaim the unmounted space.
Instructions:
Boot on a twrp 2.8.x.y TWRP recovery
flash the package
Download :
https://drive.google.com/file/d/0B9kxrJw-dzUmNG12QkdaU3R4Ujg/view
Credits :
@m11kkaa from whom I took the idea
Click to expand...
Click to collapse
Hello,
It doesn't work on my fresh install of 5.1 (stock and on nexus 7 2012 wifi). TWRP says :
Code:
Error executing updater binary in zip '/sdcard/resize_manta.zip'
Error flashing zip '/sdcard/resize_manta.zip'
I've tried both with TWRP and with nexus root toolkit. I've redownload the zip. Still the same.
Any idea ?

carrion crow said:
Hello,
It doesn't work on my fresh install of 5.1 (stock and on nexus 7 2012 wifi). TWRP says :
Code:
Error executing updater binary in zip '/sdcard/resize_manta.zip'
Error flashing zip '/sdcard/resize_manta.zip'
I've tried both with TWRP and with nexus root toolkit. I've redownload the zip. Still the same.
Any idea ?
Click to expand...
Click to collapse
The binary is not static and it was built for nexus 10.

OK, thank you. I will search for another solutions.

Khaon said:
Can you confirm this is the path of your system partition's block device?
Code:
dev/block/platform/sdhci-tegra.3/by-name/APP
Click to expand...
Click to collapse
I have a Nexus 7 (2012) and can confirm that this is the path of the device:
Code:
[email protected]:/ # cat /proc/mounts
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,seclabel,relatime,user_xattr,acl,barrier=1 0 0

OK I won't be able to edit now but if you open the .sh fi!e you will be able to hardcode this path instead of the one I put!

0.0mb system on Nexus 7
So I found this post which have the solution to this problem here;
http://forum.xda-developers.com/nexus-10/development/mod-reclaim-free-space-partition-t3029605
This does not currently work for the Nexus 7. Since I'm a new member here I cannot answer the OP personally, but if he sees this or anyone care to relay the information;
I can confirm that this is the correct path
Code:
dev/block/platform/sdhci-tegra.3/by-name/APP
//MarK

Khaon said:
OK I won't be able to edit now but if you open the .sh fi!e you will be able to hardcode this path instead of the one I put!
Click to expand...
Click to collapse
Okay so I tried to hardcode this path. Maybe I'm just extremely stupid, but I couldn't get it to work.
Still get the Error executing updater binary. I'm on TWRP 2.8.7.0.

MarkPersson said:
Okay so I tried to hardcode this path. Maybe I'm just extremely stupid, but I couldn't get it to work.
Still get the Error executing updater binary. I'm on TWRP 2.8.7.0.
Click to expand...
Click to collapse
If you are on twrp 2.8.7.0 you dont need this anymore , yu can from the wipe screen resize a system partition

Khaon said:
If you are on twrp 2.8.7.0 you dont need this anymore , yu can from the wipe screen resize a system partition
Click to expand...
Click to collapse
Oh. I had no idea.
I don't know if the N7 has too low memory, but this didn't help at all unfortunately.
I get the following info:
Present: Yes
Size: 639MB
Free: 0MB
Used: 639MB
Backup Size: 639MB
Tried both to Resize and Repair but to no avail. :crying:

MarkPersson said:
Oh. I had no idea.
I don't know if the N7 has too low memory, but this didn't help at all unfortunately.
I get the following info:
Present: Yes
Size: 639MB
Free: 0MB
Used: 639MB
Backup Size: 639MB
Tried both to Resize and Repair but to no avail. :crying:
Click to expand...
Click to collapse
I'm probably, no ... surely ... completely out of my depth, but is there any chance this was done intentionally to keep Bad Things(tm) from being put onto the system partition? It seems like a horrible oversight so I'm wondering if it was intentional. Of course if a hack was in a position to write the the system partition, then it is just as likely in a position to delete something to make room, but that might then be noticed.
Just something that popped into my head after all day cooking for the in-laws and now trying to decompress with some Nexus hacking

Both the script and the TWRP functionality worked fine on my N10. But it still doesn't leave much space on /system when running a Marshmallow-based ROM. Meanwhile, I have 22GB free on my internal user storage (emulated SD card).
I'm curious if it would be possible to shrink that user partition size some and add that space to /system using this script or TWRP? Running fdisk -l /dev/block/mmcblk0 in adb shell shows only one partition, so I'm not totally sure how things are being sectioned off internally.

I used this for the main reason to fix the issue of insufficient space in system partition that wasn't letting me install gapps, I don't know why but after I did the mod, and flashed aicp is showing 700mb total on system partition in tibu, I thought it's supposed to be 800mb on it, no biggie since I fixed my main issue but I only have 13mb left in system.
Sent from my Nexus 10 using Tapatalk

PIT files
My nexus 10 has the boot loop problem and I think I have been left with the only option of Re-Partition but I need the PIT file. Can anybody help or provide this file?
I have tried everything else (fastboot, adb, temporary custom recoveries, Nexus Root Toolkit) with no success.

Cant mount errors when in TWRP recovery. Nexus 7 2013

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.

Please Help How fix Unable to mount internal storage

Hello everyone,
Please Help me to fix this issue
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
I have twrp v2.5
Actually, I am trying many solutions but nothing change

Hi, pal. I have the exactly same problem these days. On my opinion, when you have made wipe and wipe dalvik cache, you just deleted the system folder and data. I did same thing, now I'm stuck! :Д When you are trying to change the firmware, is the logo pictures changing for you every time you flash any other .zip file? We' are now complete lost man. Is your USB working like mine where PCs not detecting it? I think they've launched this kind of firmware only to destroy our device, so we can buy a new one. That's the idea. Go to the service and repair center of Lenovo and ask them for help! I wrote them down before a while, now I'm waiting for the response. We have left only two or three possibilities to flash the Rom with the Terminal in the Recovery. But if your PC recognizing the drivers, you will manage to flash the Stock 4.2.2 Rom with Flash tool , otherwise you are stuck too! I have no idea how to flash it. I can give you the terminal commands for you, which are hard to find, but you and me, we need the proper .img files for the flashing procedure. Go to the 4pda forum and ask for help, if you find any solution, come back here telling it and for me. There's a possibility, but it is difficult to create a proper .zip archive, because I only know that we need those folders and files: meta folder- updater-script, logo. bin, lk.bin, boot.img and system.img.
But when I insert the commands there, I don't know how the whole process must be working, something is happening there. The problem is that one of those lines did not work for me. Those are the commands for flashing any Rom with the terminal in the recovery. But first you must see if the PC is installing your drivers properly, open device manager and look for the drivers on the internet and try to install them. May be you have a working USB port, so there's no problem, just flash the stock rom with the Flash tool. But if it is not working as it is here, no other possibilities left, my boy! The only one left or two of them : Flashing the device either through fast boot mode or adb sideload, but you must install those drivers so PC can find the device. Well, you can always do this at your own risk from the terminal.
Oh, I forgot, those problem came when we deleted fstab file for our device.

Flashing firmware through the TWRP terminal commands:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6 (for the memory ROW+ ) or
dd if=/external_sd/system.img of=/dev/block/mmcblk0p5 (for CN+ memory)
dd if=/external_sd/boot.img of=/dev/bootimg
dd if=/external_sd/lk.bin of=/dev/uboot
dd if=/external_sd/logo.bin of=/dev/logo
First, system.img must be converted to systemEXT4.img, then flashing it and you need to have a systemEXT4 in the .zip archive. But I think my system folder is deleted. :Д
simg2img /external_sd/system.img /external_sd/systemEXT4.img
Good luck to you! According to me there is a space after the dot and it must be like this: system. img, boot. img. But not sure!

Hi again. Tooday It occurred to me where our problem may be came with the tablets. When we flashed a custom Rom, we put it for the wrong MTK processor. Ours is MT8389, not 6589. The stock roms are too for the MT8389 according to me. We flashed a wrong Rom. Now the tab must be formatted somehow either through some commands from the terminal, or USB port and path to the USB must be repaired. Then, flashing with the Flash tools is our only option left! Sorry! );
They killed our device on purpose with the Custom rom. Do not flash them any more with such Roms.

"Failed to mount '/system' (invalid argument)", Help translating tech talk

To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/

strapdad said:
To be quick, I have a very specific error in all TWRP versions on LS997 that won't let the system stay mounted while flashing roms, "Failed to mount '/system' (invalid argument)".
I believe I found a fix for it in a dead reddit thread, but I can't understand how to do it on an LG v20.
Help is much appreciated.
It reads
"for anybody that stumbles upon this thread: I got it working by using a parted binary and mkfs.ext4 binary.
I removed the partition and added it again with parted, don't forget to name it correctly. And then I reformatted with mkfs.ext4. Those three links might help:
https://en.miui.com/thread-340966-1-1.html
https://android.stackexchange.com/q...in-terminal-emulator-on-my-android-smartphone
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171"
The thread.
https://www.reddit.com/r/LineageOS/comments/aozjvf/twrp_can_not_mount_system_with_invalid_argument/
Click to expand...
Click to collapse
I’m also looking at the thread, and the miui link is stale because miui cleaned their forum.
I tried erase data (entire partition). I tried wiping system data cache, no matter what I did it was error 7 or unable to mount system.
I’m suspecting it might be which kdz I used for the downgrade but honestly it can’t be the case because I did this before 2 months ago and it was ok, now I can’t do anything.