FORUMS

Two New Moto X and New Moto G – Specs & Details

Today’s Moto event just ended and now we have a clear look at all of … more

How Strong Is Your Connection? – XDA Xposed Tuesday

Everyone is always talking about their bars. How many bars of WiFi do they … more

OnePlus 2 Announced: Specs, Price and Details

The OnePlus 2 has just had its Virtual Reality Launch event, and at the XDA Office we all … more

A Helpful Guide to Music Streaming Services

With the launch of Apple Music, music streaming services have recently gained a lot of … more

[Q] Internal memory become read-only

37 posts
Thanks Meter: 0
 
By mm_d, Member on 18th April 2012, 05:39 PM
Post Reply Subscribe to Thread Email Thread
21st April 2012, 08:36 AM |#31  
lavero.burgos's Avatar
Senior Member
Flag Guayaquil
Thanks Meter: 1,327
 
Donate to Me
More
Quote:
Originally Posted by mm_d

mount -o remount,rw /
mount -o remount,rw /system

It didn't change anything.

I was explicit:

# mount -o remount,rw /dev/block/mmcblk0p8 /system

try that, for what i're read a reflash should fix it. But i think you already have tried that. We could also try a script under /etc/init.d

~ Veronica
 
 
21st April 2012, 09:01 AM |#32  
OP Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by lavero.burgos

I was explicit:

# mount -o remount,rw /dev/block/mmcblk0p8 /system

try that, for what i're read a reflash should fix it. But i think you already have tried that. We could also try a script under /etc/init.d

~ Veronica

I read your previous post before you edit it.
Anyway, "mount -o remount,rw /dev/block/mmcblk0p8 /system" didn't help.
Last edited by mm_d; 21st April 2012 at 09:03 AM.
21st April 2012, 11:52 AM |#33  
Demetris's Avatar
Recognized Developer
Flag Limassol
Thanks Meter: 7,884
 
Donate to Me
More
ok, let go back in time

Please tel me how you get this gpt partition table

Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 13.6GB 12.0GB fat32 media msftres
11 13.6GB 15.9GB 2315MB ext4 userdata

Especially the /media and /userdata.
What path did you follow?
21st April 2012, 11:57 AM |#34  
OP Member
Thanks Meter: 0
 
More
I repartition internal memory via method by lavero.burgos
21st April 2012, 12:04 PM |#35  
Demetris's Avatar
Recognized Developer
Flag Limassol
Thanks Meter: 7,884
 
Donate to Me
More
And after that repartition the problems start?
Or was ok.
21st April 2012, 12:04 PM |#36  
OP Member
Thanks Meter: 0
 
More
Everything was ok.
21st April 2012, 12:08 PM |#37  
Demetris's Avatar
Recognized Developer
Flag Limassol
Thanks Meter: 7,884
 
Donate to Me
More
adb remount, works?

Remount remounts the /system partition as writable (or readonly if it is already writeable)
Last edited by Demetris; 21st April 2012 at 12:11 PM.
21st April 2012, 01:46 PM |#38  
OP Member
Thanks Meter: 0
 
More
"adb remount" says that "remount succeeded". But actually memory remains read-only: after reboot all changes revert back.
21st April 2012, 11:31 PM |#39  
lavero.burgos's Avatar
Senior Member
Flag Guayaquil
Thanks Meter: 1,327
 
Donate to Me
More
Hi, try this backup NT_MIUI_Tweaks_backup.zip - md5: 3518f9a3289ca6e97b569777873b899b
... it has fixed 2 corrupted Nook Tablets in the past.

~ Veronica
25th April 2012, 07:04 PM |#40  
Junior Member
Thanks Meter: 0
 
More
I have similar problem, i cant fix it to. Try using this:
mount via adb internal partition
11 13.6GB 15.9GB 2315MB ext4 userdata

mkdir mmc0
mount /dev/block/mmcblk0p11 /mmc0

add try to copy file large >1GB(like hd-rip video) -file must be lagre that operating memory(1GB),
adb push <file_>_1GB> /mmc0
wait 3-4 minutes
if you nook restart you will catch memory overflow. I think that this hardware failure...
... but if not, it good news.


try
adb shell
umount /mmc0
reboot

then via adb
mount /dev/block/mmcblk0p11 /mmc0
ls -l /mmc0
if you see your file, MMC memory ok, you can try restore method

(могу попробывать поковырять, без гарантий, от 200 грн, киев)
Last edited by kostic2006; 25th April 2012 at 07:08 PM. Reason: +1
25th April 2012, 07:05 PM |#41  
Demetris's Avatar
Recognized Developer
Flag Limassol
Thanks Meter: 7,884
 
Donate to Me
More
Hi,
Have you manage to solve your problem?

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

Advanced Search
Display Modes