Hi guys,
I don't know what piece of info is relevant or not, so I will outline as much as I can.
I was running the latest stable Slimbean with stock kernel, a couple of weeks ago my external sdcard stopped being recognized and would not mount. In Clockworkmod it would show an error mounting what I later learned were 3 different partitions.
Yesterday I installed freegee to try and restore my original partitions, but it would give me an error that my device was not supported. So I uninstalled freegee. The next time I rebooted my phone, it would get stuck on a black screen after the LG logo. I was able to get into recovery and download mode, so I tried the original teenybin with lgpnst and I could not get into recovery, only the LG logo. I then tried the alternate teenybin that boots up with the Google logo and I was able to get into TWRP.
I then sideloaded Houston's aosp KitKat and was able to successfully boot up the phone. I now have no system sounds, no music or media sounds, through the speaker or the headphone jack. Phone audio works through earpiece, speaker and headphones.
Tried wiping and reflashing. I don't know what else to do.
Any ideas would be appreciated.
Thanks.
I also noticed that sensors were not working.
I flashed the W84C27MO84.zip hybrid modem.
This solved the problem with sounds and audio not working and fixed the sensors.
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
XDFernando said:
Post your partition table here!!!
Enter in CWM Recovery, connect your phone to computer, open terminal in administrator mode. open adb shell and run this command.
parted /dev/block/mmcblk0
press P and put your result partition screenshot here.
Click to expand...
Click to collapse
I wasn't able to do it exactly as you described, but I think I got what you asked for. Hope it helps.
Thanks,
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
XDFernando said:
Im so sorry my steps was with Special CWM.
Try this 3 steps on ADB shell.
Code:
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17.bak
mke2fs -T ext4 /dev/block/mmcblk0p17
reboot
good luck!!
Click to expand...
Click to collapse
Thank you for the response.
What exactly will this do?
I ran what you suggested.
I received "Not enough space to build proposed file system while setting up superblock"
How much free space is required? I have almost 2gigs free
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
XDFernando said:
you need to do separate steps. One line is one command. Enter every one line.
And Dont copy paste i see another extra simbols
Click to expand...
Click to collapse
Hello,
Thank you for your responses.
I tried doing it again, one line at a time, but still got the same message after the second line.
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
XDFernando said:
Try add -F to the second line like this:
mke2fs -F -T ext4 /dev/block/mmcblk0p17
Click to expand...
Click to collapse
Hi Fernando,
I tried again with the -F added, but I received the same message about "not enough space..."
Related
I need some help for my gtab to reconise NTFS hard drive. I have latest Clemson kernel and running vegan 5.1. I have found this script.
mount-o umask=000 -t ntfs /dev/block/sda1 /mnt/usbdisk. It does not work. Please help if anyone knows of any solution. I don't have access to PC so can't format to fat32. THANKS!
Unfortunately, that script doesn't work for me as well. Cully's V.1.1 ROM and Clems' ver. 7 Kernel
I've given up trying to get it to recognize NTFS
I was having this same problem, but no one ever really explained what to do in depth. From what you said, it seems you missed on important part of the line, but if you didn't I'm sorry for just saying what you already know.
So what worked for me was first installing was terminal emulator, its a free app from the market. Once on the terminal, you type "su" first and enter. The very first time I did this the superuser permission popped up and I allowed. After this the line should start with a "#" instead of a "$" which should have appeared before typing "su" and that is when you type in the other stuff. So the whole terminal should look like this.
$ export PATH=/data/local/bin:$PATH <<(already there)
$su
#mount -o umask=000 -t ntfs /dev/block/sda1 /mnt/usbdisk
Keep in mind the spaces, there was one after mount, that you didn't have in your post. Also, I don't know of a way to unmount. I've had to turn off my tablet to even get my FAT32 drive to work. But it all works for now.
Hope this helped.
ksVPN
ksVPN said:
I was having this same problem, but no one ever really explained what to do in depth. From what you said, it seems you missed on important part of the line, but if you didn't I'm sorry for just saying what you already know.
So what worked for me was first installing was terminal emulator, its a free app from the market. Once on the terminal, you type "su" first and enter. The very first time I did this the superuser permission popped up and I allowed. After this the line should start with a "#" instead of a "$" which should have appeared before typing "su" and that is when you type in the other stuff. So the whole terminal should look like this.
$ export PATH=/data/local/bin:$PATH <<(already there)
$su
#mount -o umask=000 -t ntfs /dev/block/sda1 /mnt/usbdisk
Keep in mind the spaces, there was one after mount, that you didn't have in your post. Also, I don't know of a way to unmount. I've had to turn off my tablet to even get my FAT32 drive to work. But it all works for now.
Hope this helped.
ksVPN
Click to expand...
Click to collapse
Hi,
Does 'umount' not unmount (in term)?
Jim
Thanks this helped me. My only? Is there anywaynot to have to do this every time u start. The gtab
This was purely experimental for me, but it worked. And now I have my serial number back.
Pre-requisites:
1. You need CWM, running internal, or at least two microSD cards to be running from sd card.
2. Two MicroSD card required.
3. If you're using Windows you need some program that can perform disk dumps. I use Ubuntu... so... I don't know if the commands are similar in windows, sorry.
4. You'll need someone else' serial number. In other words, you'll need someone else' backup of the /rom partition. Check lavero.burgos unbrick topic. I think there is one on there.
This should be at least somewhat risk-free. Since it doesn't actually tinker with settings
Okay, so boot into internal cwm on your Nook. Make sure you have an sdcard in your nook. Then run adb:
Code:
$ adb start-server
$ adb devices
Make sure you see your device and it shows it in recovery mode.
Code:
$ adb shell
~ # mount sdcard
~ # dd if=/dev/block/mmcblk0p5 of=/sdcard/blk/mmcblk0p5.img
~ # exit
$ adb pull /sdcard/blk/mmcblk0p5.img /path/to/file/mmcblk0p5.img
$ adb shell
~ # rm /sdcard/blk/mmcblk0p5.img
~ # exit
At this point you insert your sdcard into your computer. Depending on what adapter you use, we need to make sure that you are going to use the correct device... so...
Code:
$ fdisk -l
Other than your Hard Disk's partitions (usually the first four), you should see a second one, either /dev/mmcblk0 or /dev/sdc depending on the adapter, but make sure it is the same size as your SD card, so you know which one you are going to be using. Once you verify which one is yours go ahead and umount it.
Code:
$ dd if=/path/to/file/mmcblk0p5.img of=/dev/mmcblk0
Wait for it to finish, shouldn't take longer than a half-minute, once it's done, Go ahead and mount it again, you should see the only partition as "rom", and two folders: devconf, and log.
Navigate to devconf, and there's a bunch of other files. Open "DeviceID" in vim or notepad or something. This is your Serial No., or where it should be anyway. On your nook, if you pop open the little MicroSD flap, you will see the device' serial number. Delete whats in that file, and type your Serial No. on there. Close and don't forget to save it. Now open "SerialNumber" and delete what's on there, and key in YOUR serial number. Close and save.
Umount your sdcard again. Delete the original mmcblk0p5 (/path/to/file/mmcblk0p5). Then jump into shell
Code:
$ dd if=/dev/mmcblk0 of=/path/to/file/mmcblk0p5
$ adb push /path/to/file/mmcblk0p5 /sdcard/blk
$ adb shell
# ~ dd if=/sdcard/blk/mmcblk0p5 of=/dev/block/mmcblk0p5
# ~ umount /sdcard
# ~ exit
In cwm go into advanced/reboot recovery. Let it reboot. And then when it's in cwm run "adb devices" and verify your serial number is there.
Thanks to Pete1612 and lavero.burgos ! Hopefully Pete1612 will test out this method too. This should be relatively easy, it's not hard. Just time consuming. -_-
Once again, let me know if I made any mistake
I will as soon as I get the I/O error figured out
Sent from a better galaxy
Pete1612 said:
I will as soon as I get the I/O error figured out
Sent from a better galaxy
Click to expand...
Click to collapse
The I/O error means the partition is damaged, however when unmounted the sdcard and re-inserted it, it seemed to work fine, so I went with it.
I took a different SD card and it worked.
Sent from a better galaxy
Probably keep this but it's u service the as card tab I. the back of the Cover
@ae1990
1. Type reply
2. Verify that what you typed was correct
3. Submit
I think you forgot step 2.
Edit-
That came off ruder than intended, I would actually like to know what you were trying to say.
Sent from my SCH-I500 using Tapatalk 2
I think have a way:
1. Copy mmcblk0p5 from nook tablet fine and push to sdcard
2. Use dd command
dd if=/sdcard/blk/mmcblk0p5 of=/dev/block/mmcblk0p5
3. In Cm7 ( boot sdcard) or stock rom have root, i use root exploer change serial in file devices id, serialnumber in rom/devconf.
I had changed my nook by this way. It success, it pass b&n :0
a much easier method... from any rooted nook with ADBD enabled.
Get either adb shell or a terminal and change to root user by issuing the "su" command.
copypasta this block
Code:
mkdir /data/local/mnt
mount /dev/block/mmcblk0p4 /data/local/mnt
Serial=`cat /data/local/mnt/devconf/SerialNumber`
echo "Your Nook Tablet Serial Number is: $Serial"
You will receive a message that says "Your Nook Tablet Serial Number is: ************"
OP is convoluted.
AdamOutler said:
a much easier method... from any rooted nook with ADBD enabled.
Get either adb shell or a terminal and change to root user by issuing the "su" command.
copypasta this block
Code:
mkdir /data/local/mnt
mount /dev/block/mmcblk0p4 /data/local/mnt
Serial=`cat /data/local/mnt/devconf/SerialNumber`
echo "Your Nook Tablet Serial Number is: $Serial"
You will receive a message that says "Your Nook Tablet Serial Number is: ************"
OP is convoluted.
Click to expand...
Click to collapse
OP has made a guide to restore it.
Yours is a way to print it out *if* its there, anyone can read it under the sd card latch so i dont see your reasoning of this post.
Hello, Can you help a noob with this ? I am at a command prompt. Wrong serial # Recovery
now what exactly ? Thanks
Hey I'm not sure if this is right, but can't you just lift up the tab where the sd card goes? It says SN: followed by a bunch of numbers.
When I needed a new charging cable, they asked for the serial number, and I just read it from there.
Sorry if this isn't what you guys are talking about, just thought I'd post.
ACL3 said:
Hey I'm not sure if this is right, but can't you just lift up the tab where the sd card goes? It says SN: followed by a bunch of numbers.
When I needed a new charging cable, they asked for the serial number, and I just read it from there.
Sorry if this isn't what you guys are talking about, just thought I'd post.
Click to expand...
Click to collapse
Thanks
the thread is to recover a sn that is MIA or incorrect for the nook in use. Some have lost their sn (no longer in nt) or replace an incorrect sn with the correct sn.
What if you can't see your NOOK TABLET?
My problem here is I can't get my computer to see the NT. When I update the drivers, it brings it up as an android phone and under that says "Android Composite ADB Interface". Any help. I think I might have completely screwed this up.
I realize this thread is old but I've been trying to go through the process. My first question is how large does the mmcblk0p5 get when you dd it? I was using a 2gb SD and the file took up 2gb then. My second question is if anyone knows how to complete the final push back to the SD card in the nook. It begins to push but after some time the nook screen flashes and it seems to hang. Thanks in advance.
Just use es explorer with root privileges heh.
So would I just copy the file to the sdcard, then once that's done transfer the card back to the nook, and use the es explorer? I'm not quite sure how to do exactly what you stated.
Boot rom , open es give root rights go to / rom find file edit it onthefly, save reboot done
Demetris said:
Boot rom , open es give root rights go to / rom find file edit it onthefly, save reboot done
Click to expand...
Click to collapse
Really, it's that simple? Wow, and I was working through all this last night!
I was wonder how to add file system check every boot since my data partition often unclean. I had try to add line in init.rc before mount and static e2fsck binary to /sbin.
Like this one: "e2fsck -fy /dev/block/data" but I think it has no effect since my tablet failed to boot. I must go to recovery and do fsck via adb shell. It is annoying. I want to make it automatically. Please help me.
Thank you..
juliantito said:
I was wonder how to add file system check every boot since my data partition often unclean. I had try to add line in init.rc before mount and static e2fsck binary to /sbin.
Like this one: "e2fsck -fy /dev/block/data" but I think it has no effect since my tablet failed to boot. I must go to recovery and do fsck via adb shell. It is annoying. I want to make it automatically..
Click to expand...
Click to collapse
Assuming you know that you need to repack your boot image to change init.rc and you did that, try prefixing your command in init.rc with "exec".
I want to run E2FSCK on every boot and repair the disk if there is some problem on Odroid N2 Android. I have used the tune2fs -c 1 command to check the disks on every boot.I want to confirm whether this command will repair the problem (if detected) as well.
I think that in Android Source code they have made sure that the disk will be checked however, I don't know whether they fix the disk as well. Please confirm this as well.
In Odroid N2 Android image, the directory /etc/default/rcS is missing, so I can't make changes to it. I can't run a script on each boot because the disks are mounted by then and I can't umount them because the disk is being used.
If anyone has some solution, I will really appreciate your help.
Hey guys,
unfortunately i think i bricked my prime
Today i flashed crombi-kk rom which worked flawlessly fine. I came from HairyBean 2.31 so all i did was to up update my TWRP via fastboot and then flash the rom. As said, that worked fine. After my first boot of the rom i thought that i would like to test the "F2FS" option. For this i updated TWRP to v2.8 via the zip-file from this thread: http://forum.xda-developers.com/showthread.php?t=2772093 . This also worked and i've got my TWRP to the new version.
Now i wanted to format the /data partition to F2FS so i went to
Wipe>>Advanced Wipe>>Choose Data>>Repair or Change File System>>Change File System>>F2FS
At this time it told me that it can't UNmount the partition and therefore it couldn't change the file-system.
Dumb as i am i thought: "Okay, then why don't just unmount the partition" so i did this (Mount>>Disabled "Data") an then retried to format the data partition with f2fs. During this process i have to assume that something went wrong? It gave me some error which i fool can't remember.
From this point i couldn't access the /data partition anymore, i can't mount it nor can i boot into Android.
I still have access to TWRP and can get to fastboot access. I have no ADB Access in TWRP - it just can't recognize the prime. In Windows-Hardware Manager it just says: Transformer?! (i have universal naked driver installed)
Forget the last sentence - it seems that my USB-Cable is partly broken. Sometimes it recognizes the prime and sometimes not!
Is it gone forever or is there still hope to recover it?
Hopefully someone can help me, i'm really desperate
P.S.: D didn't want to make things worse, so i stopped messing around with it - would it help to reflash the ne0zone75_tf300t.blob file? Is this even possible if i already updated the TWRP to a newer version?
NiffStipples said:
I still have access to TWRP and can get to fastboot access.
Click to expand...
Click to collapse
As long as this is the fact, we don' t call it 'bricked'.
Try following one after another:
1. TWRP>>Wipe>>Advanced>>[check / data]>>repair file system, flash ROM again.
2. Fastboot:
Code:
fastboot -i 0x0b05 erase userdata
- then flash ROM again.
3. Last ressort: Flash stock ROM and start from scratch.
... hope you've pulled your nvflash files. Good luck!
... you might also want to flash another TWRP, though ne0zone75's normally works well. Try the official 2.8.3.0 (for tf300t because you are on Hairy Bean), works good with my prime.
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones? I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
NiffStipples said:
Thanks a lot for your reply
I've tried the steps you provided:
1) While repairing the data partition it said again that it can't mount the data partition. (Picture of it in the attachment)
2) Reflasing the rom worked okay but as expected it couldn't boot (stuck in bootscreen) - in TWRP the /data partiton was again unmountable
3) erasing the userdata via fastboot gave me the following:
Code:
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
At this time i didn't tried to reflash the rom because i don't think it would change anything?!
Click to expand...
Click to collapse
Sounds as if partition table is faulty.
1. You could try to redo the Hairy Bean procedure.
2. If you feel lucky, then you could try to format partition manually using
Code:
mkfs.ext4 /dev/block/mmcblk0p8
4) i only have the old nvflash files from ages ago when i started flashing with androwook - i fear they are the wrong ones?
Click to expand...
Click to collapse
nvflash files don't grow sour; you could try without changing to wheelie your blob.bin. If it works, you are safe and can continue with the other blobs.
I don't have any clue what to do with these - are there good instructions to get the tab back to it's factory state?
Click to expand...
Click to collapse
Best instruction you find here: http://forum.xda-developers.com/showthread.php?t=1894867
Last but not least - do you have a link for the right TWRP you're talking about. I don't want to gave the wrong one a try
Click to expand...
Click to collapse
I have actually the (official) one from http://www.techerrata.com/browse/twrp2/tf300t
Good Luck!
Okay, now i know why they always say that flashing is nothing for noobs
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
NiffStipples said:
Okay, now i know why they always say that flashing is nothing for noobs
Click to expand...
Click to collapse
Everybody starts as a noob.
I'm a little bit confused - what (in your opinion) is the best shot i should give a try?
Formatting manually (from where? In TWRP or via adb? I'm on Windows)
Click to expand...
Click to collapse
I would first do that manually from TWRP>>Advanced>>Terminal Command>>Select Folder (root)>>type in: mkfs.ext4 /dev/block/mmcblk0p8
Reflash everything with NVFLASH (is that possible without any hassle - the NVFLASH files are from ICS-times and i'm on JB/KK?!)
Click to expand...
Click to collapse
Important is, that blob.bin works with
Code:
wheelie.exe -r --blob blob.bin
After that you should flash 'bricksafeTF201.img' and 'unlock-token-TF201'. Then you can flash any blobs of unblobbed ROMs you can find in the internet or flash stock ROM (JB). Then proceed to fastboot custom recovery and zipflash custom ROM.
I know it's annoying to help someone who doesn't know what he's doing - hope you have time to get me through this flashing nightmare :/
Click to expand...
Click to collapse
I went through any misstep you can think of with the three of 'em: TF201, TF300T, TF700T.
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
NiffStipples said:
Mmmmh, the command
Code:
mkfs.ext4 /dev/block/mmcblk0p8
gives me back:
Code:
mkfs.ext4: not found
Click to expand...
Click to collapse
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
NiffStipples said:
Hooray! :victory: Thanks a lot - everything is back where it belongs
Just for the learning effect - do you have any idea what did go wrong in my case and how would i correctly change the format of the data partition to f2fs? I think i've read a lot of times that this would improve rom speeds a lot?!
Click to expand...
Click to collapse
Congrats!
If you would care to tell what you did last, one could make a guess, what went wrong.
... and yes, changing /data (only!) to f2fs makes a tremendous difference in speed. Normally TWRP complies the job without probs. What TWRP do you have now?
I prefer @ne0zone75's which I linked some posts before. They work on all my tabs.
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
NiffStipples said:
I have installed v2.8.3.0 from the site you gave me above
Mh, as said in the first post i did the following steps to change the format
I tried Wipe>>Advanced Wipe>>Checked "Data">>Repair or Change File System>>Change File System>>Choose F2FS
Then the system gave me an error that it couldn't access the partition because it was mounted or couldn't be unmounted or something like this
So i went back to Mount>>unchecked "Data"
And then again to Advanced Wipe>>...>>Change File System>>F2FS
After that something went wrong because after that step i couldn't mount the data partition anymore?!
Click to expand...
Click to collapse
Yes, but what did you to fix it then?
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
I am still of two minds of f2fs on these tablets.. Just gone back to ext4 to compare... As was getting to sticky on the F2fs with redraws and lag..
Anyway good to hear a successful conclusion on the come back by the OP
NiffStipples said:
Oh sorry, now i get it
I just used your command for repartitioning(?!?): make_ext4fs /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Good! Glad, it helped you. Now you could try the 'mkfs.f2fs' command also.
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
NiffStipples said:
Already tried that - this time it worked without problems :highfive:
Thanks again for the great help!! F2FS brings the prime to a whole new level, now i just have to figure out how to change the dock layout language
Click to expand...
Click to collapse
That should be no problem. If you click in dock, there should be a keyboard icon in notification area, clicking it settings dialog will appear. Additional in settings>>language and input>>physical keyboard you can set keyboard layout of dock.
das chaos said:
Oops! My bad, try
Code:
make_ext4fs /dev/block/mmcblk0p8
.
.... for information's sake type
Code:
fdisk -l /dev/block/mmcblk0p8
You should get
Code:
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Click to expand...
Click to collapse
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
dgcruzing said:
DC,
I wonder if this is why my f2fs where playing up for me?
using your commands I get the following..
Code:
[email protected]:/ $ su
[email protected]:/ # fdisk -l /dev/block/mmcblk0p8
Disk /dev/block/mmcblk0p8: 29.6 GB, 29618601984 bytes
4 heads, 16 sectors/track, 903888 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
[email protected]:/ #
Disk /dev/block/mmcblk0p8 doesn't contain a valid partition table
this is what I am looking at as a problem maybe?
is there a terminal command to see all the partitions and sizes?
I might have to take this thing back to scratch and start again as been flashing left right and center on it of late.
Click to expand...
Click to collapse
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
das chaos said:
No that's normal for f2fs, only fat systems have readable PT. What I was interested was geometry of fs and that is the same as mine. So everything is o.k. You have your tab up and running - that counts.
There is a free app Storage Partitions in the store, which can do no more than show information about partitions. Mainly an exploit of commands
Code:
cat /proc/mounts
and
Code:
cat /proc/partitions
Click to expand...
Click to collapse
Used that one and another to have a look..
This is what I get, just for the hell of it..
As said for me.. F2Fs on this one doesn't play nice and the last few days I am back to Ext4..
Running it in and let it settled, putting it through its paces with plenty of tabs in chrome open and multitasking back and forwards in to Tapatalk and it runs normal with out lag and redraws..
I am using apex as a launcher and under F2Fs with kept in memory set..it was redrawing to the max and timing out from coming out of sleep..
Playing with other tweaks to see if can get it to a sweet spot.
Will let it settle for a few days and play then swop back and see which is better with the tweaks added
Okay so here it goes. I had missing IMEI problem in a custom ROM when not on a samsung base. I had a neatefs (app on android) backup which I tried to restore using HC ktool (Bad idea, I know). It gives me a successfully done message and tells me to reboot. Now my phone is stuck in bootloop no matter what (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
/efs is unmountable for me. I tried various methods mentioned for S3 and Note such as connecting the phone in ADB mode and following the steps but none of that works.
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
AKAndrew41 said:
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
Click to expand...
Click to collapse
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
ruleh said:
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
I've tried all that, none helps. I've even installed a busybox as mentioned somewhere else which said that the syntax mke2fs is not available without a busybox. Nothing worked. Still unable to mount efs afterwards.
pHraiL^ said:
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
Click to expand...
Click to collapse
I'm pretty sure it won't damage anything, or at least to me didn't. Because whenever I want to reinstall a new ROM I always format everything I've mentioned earlier so I don't find it harmful for the device, as long as you don't have data worth backing up.
Also, wipe dalvik.
If you installed busybox, make sure you uninstall the previous version prin pressing uninstall, and them installing 1.23.1 because for me sometimes it says it's intalled, but after reboot I still have the old one.
After you do that, connect phone to PC and try running
adb shell
Once you do that, give a try to the command
umount -f /efs
even if it says it's umounted, then type
mount /dev/block/mmcblk0p3 /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
These two are the commands everyone is talking about the S3 phone having same issue. I tried everything. The first command works and it shows something like:
"The filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override."
For the second line of code when I try, this is what I get:
"It says "mount: can´t find /dev/block/mmcblk0p3 in /etc/fstab"
Now I have also tried adding space and /efs to the second command. It gives me nothing, not even any error. So I presume it works but then when I reboot efs is still messed up. I have no idea what these commands does actually. I think it has something related to re partitioning. Shouldn't the second command line give the same output as the first one? Its been a whole day searching for this thing. I got my phone messed up real bad.
EDIT: One more thing, when I hit the # df command on ADB, it shows 3 drives (/dev, /cache, /emmc) when not in su and 4 when in su (/dev, /cache, /emmc, /system). No where it shows any efs partition. Is there suppose to be any?
EDIT2: After the second line command. Using mount -t following someone's guide I get the efs partition but I think it is way too small. See the attachment. This partition is gone again after reboot.
OH GOD I got it working. After more searching, I found out the the block used for efs storage in S2 is mmcblk0p1 not mmcblk0p3. Phew!
Follow the same commands to make it work. Just rename the block.
Here is a guide which helped me figure out the block: http://www.usoftsmartphone.com/t306464.html
Thanks everyone
im having same trouble now with the S7. the page you share not there anymore. please share me how to figure out the block