e.g which partition is the dalvik cache? mmcblk0p*?
i know mmcblk0p18 is emmc, and mmcblk0p12 is system or cache i think. I ask this because a while ago, a battery outage during a flash has corrupted a few partitions such that when i do a certain amount of activity on the phone, it locks up, all apps FC and no amount of reboots fix it. I removed and formatted partitions in the above locations and now i can freely restore my backups (they used to fail on flashing system probably due to corrupted partition there). I still get FC here and there, only when i haven't used the phone in a while (enters deep sleep) and whatsapp/messaging also FC so it's a serious problem which affects my daily life.
The only important place i haven't removed and wiped is the dalvik cache, so i specifically need the location to that.
Thanks!
I'm pretty sure Ive read that the Dalvik cache is part of the normal cache partition.
dblades said:
I'm pretty sure Ive read that the Dalvik cache is part of the normal cache partition.
Click to expand...
Click to collapse
I don't think so. I think it's in the /userdata/ partition. Anyways, i found a comprehensive list here: http://pastebin.com/hxugnyQC
There is no partition specifically designated for dalvik cache. Depending on your ROM/setup, dalvik cache can be in many places. Typically system apps (those in /system/app) have their dalvik cached at /cache/dalvik-cache, and user apps (those in /data/app and /data/app-private) have it in /data/dalvik-cache. If you have apps2sd, there could be another one at /sd-ext/dalvik-cache. There could be even more, depending on your ROM/setup.
I have the complete Atrix partition map saved on my computer but have no access to it right now since I'm on my phone.
EDIT: Here you go. Based on http://forum.xda-developers.com/showthread.php?p=12687720 and my own research.
Code:
mmcblk0p1 ? 3.5 MB
mmcblk0p2 ? 512 kB
mmcblk0p3 /pds 2 MB
mmcblk0p4 <extended> -
mmcblk0p5 /signature 1 MB
mmcblk0p6 ? 512 kB
mmcblk0p7 /misc 512 kB
mmcblk0p8 /logo 1 MB
mmcblk0p9 /kernelpanic 2 MB
mmcblk0p10 /recovery 8 MB
mmcblk0p11 /boot 8 MB
mmcblk0p12 /system 320 MB
mmcblk0p13 /osh 768 MB
mmcblk0p14 /cdrom 20 MB
mmcblk0p15 /cache 640 MB
mmcblk0p16 /data 2 GB
mmcblk0p17 /preinstall 345 MB
mmcblk0p18 /emmc ~11 GB
Related
I've searched through the all the XS forums and Backup & Restore within CWM Recovery seems to work for everyone, on all the different ICS Based Kernels with Recovery except for me.
I get the error below whenever I try to format my /system partition through recovery; as the Restore tries to format the partition before restoring to it by restores always fail and I'm left with a /system partition that I can't mount. Only through restoring through Flashtool can I get the phone to boot again. Has anyone seen this before or have any idea what the problem is? Someone having a similar issue on the Samsung Galaxy Player had a similar issue and it was down to a corrupt partition table Galaxy Player Problem
Error From Recovery
Code:
Formatting /system...
E: format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /system!
Error mounting /system!
My Partition Table (if it's any use)
Code:
Disk /dev/block/mmcblk0: 31.9 GB, 31910264832 bytes
4 heads, 16 sectors/track, 973824 cylinders, total 62324736 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 4096 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 4097 5120 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 8192 49151 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 49152 61071359 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 50176 51199 512 46 Unknown
/dev/block/mmcblk0p6 53248 59391 3072 4a Unknown
/dev/block/mmcblk0p7 61440 67583 3072 4b Unknown
/dev/block/mmcblk0p8 69632 75775 3072 58 Unknown
/dev/block/mmcblk0p9 77824 88063 5120 70 Unknown
/dev/block/mmcblk0p10 90112 106495 8192 83 Linux
/dev/block/mmcblk0p11 106496 139263 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 139264 2236415 1048576 83 Linux
/dev/block/mmcblk0p13 2236416 2748415 256000 83 Linux
/dev/block/mmcblk0p14 2748416 6942719 2097152 83 Linux
/dev/block/mmcblk0p15 6942720 61071359 27064320 c Win95 FAT32 (LBA)
I was sondering if anyone had any suggestions, or could at least post their Partition Table to see if I need to sort mine out
(From ADB:
fdisk /dev/block/mmcblk0
U,
P
Then paste it here)
Cheers,
Andy
hello Andy..
mine partition table is just the same with you. but i can restore my backup (which include /system backup) just fine.whick kernel are you on?
It happened to me once. I formated data partition and it worked, don't know why
I've had the same problems with the FXP kernels ( both CM9 & CM10) ,Advanced Stock and SSpeed. I'm starting to wonder if the memory is actually damaged.
It's hit and miss as to which partitions it'll let me format, system and cache almost always fail, data sometimes works,but then frequently won't mount afterwards.
Sent from my LT26i using xda premium
Hi!
I've the same problems.
My phone has a srange behavior... Often can't ormat partitions, can't mount them, but after few retries i can manage it. And it's totally random..
You think is a software memory or a damaged memory ?
I never can't restore a nandroid backup because it give me an error restoring system partition.
Any ideas ?
mrscope said:
Hi!
I've the same problems.
My phone has a srange behavior... Often can't ormat partitions, can't mount them, but after few retries i can manage it. And it's totally random..
You think is a software memory or a damaged memory ?
I never can't restore a nandroid backup because it give me an error restoring system partition.
Any ideas ?
Click to expand...
Click to collapse
I've found a sort of work around. It appears to only be recoveries that use an ICS kernel that give me issues, so I loaded Doom's Advance Stock GB Kernel onto the phone and the recovery on that works flawlessly everytime. (it also has better features than regular CWM Recovery)
All the ICS kernel's that I tried will always successfully back up and restore the boot partition, so I use them to do that. Then restore DoomKernel (advanced restore, restore boot) then do all my backups, restores, and flashing with DooMRecovery. Then you can tidy everything up by moving the ICS Kernel BootPartion image into the DooMRecovery system/data backup folder, then insert the boot.img line from the checksum MD5 file at the start of the ICS MD5 file into the DooMRec MD5 file. (so you have all the correct files in the same folder, with the correct MD5 sum for each of the images in the folder). Then you can do a restore via DoomRecovery if you ever need to.
I grant you it's a bit messy and if the timestamps don't work properly a little confusing, but it does do the job, and it means you can easily swap between ROM's on the go.
sixdaysandy said:
I've found a sort of work around. It appears to only be recoveries that use an ICS kernel that give me issues, so I loaded Doom's Advance Stock GB Kernel onto the phone and the recovery on that works flawlessly everytime. (it also has better features than regular CWM Recovery)
All the ICS kernel's that I tried will always successfully back up and restore the boot partition, so I use them to do that. Then restore DoomKernel (advanced restore, restore boot) then do all my backups, restores, and flashing with DooMRecovery. Then you can tidy everything up by moving the ICS Kernel BootPartion image into the DooMRecovery system/data backup folder, then insert the boot.img line from the checksum MD5 file at the start of the ICS MD5 file into the DooMRec MD5 file. (so you have all the correct files in the same folder, with the correct MD5 sum for each of the images in the folder). Then you can do a restore via DoomRecovery if you ever need to.
I grant you it's a bit messy and if the timestamps don't work properly a little confusing, but it does do the job, and it means you can easily swap between ROM's on the go.
Click to expand...
Click to collapse
I had the same thing last week, couldn't restore a backup form CWM (on Xperia S/FXP CM10 207). Formatting cache and system 'manually' in CWM also failed. /data was OK.
I ended up formatting from adb (mkfs.ext2 -T ext4 /dev.... ) and mounting the partitions through CWM. Then I untarred the different partitions of my CWM-backup and everything was fine.
Is this a problem of CWM or my phone, or ...?
Thanks
Frank
I am having the exact same issue. I cannot -ever- format the cache . So every restore attempt ends in error.
I have rooted stock .55 , with locked bootloader.
Did anybody ever found a fix for this.
I have read the other recovery option but it requires kernel changing and possibly unlocked bootloader.
I created a thread with my issues, here
http://forum.xda-developers.com/showthread.php?t=2163141
**SOLVED**
I got a little restless waiting for a response, so I just went ahead and re-flashed the latest RUU. It worked. My internal sd card is fine and fully functional now.
(I'm leaving the original question below in case this helps someone else in a similar situation)
--------------------------------------------------------------------------------------------------------------------------------------
Hi. I tried to partition my internal sdcard and did something wrong. Now it won't mount.
About my phone:
-------------------------------------------------------------
Info at the top of my bootloader screen:
Code:
**vinylfreak89**
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
Radio-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
Currently running ra recovery v3.15
Currently on Neo's AOSP RAGERom 1.9.1
-------------------------------------------------------------
How I broke it:
I tried to partition my sdcard and use the s2e app to move my apps to the sd partition. In order to do this, I removed my external sd card, booted into recovery, and selected partition sdcard, then partitioned an ext2 section of about 1GB. I reinserted my external sdcard, rebooted and tried to use the app. I made some selections in the app, rebooted phone, and tried moving my apps to sd, but it still didn't work. Then I did some more stuff, accidentally wiped my external sd card, (i'm a little fuzzy on exactly the remaining details, but I don't think anything else beyond this point is pertinent... suffice it to say my internal sd is not working, but I fixed everything else).
Current symptoms:
Everything on my phone works fine, except that the internal sdcard doesn't mount. While running my phone normally, if I try to mount usb mass storage, It mounts my external sd, but not the internal sd.
From recovery, if I try to wipe my Internal SD, i get the following error:
Code:
Formatting INTERNALSD
E:Can't mount /dev/block/mmcblk0p37 (or /dev/block/mmcblk0p38)
(Invalid argument)
Error mounting /internal_sdcard/!
Skipping format...
I get the same error when trying to mount Internal SD.
I tried other recoveries ( TWRP_v2.3.2.1, CWM_Touch_5.8.1.5v1.1, CWM_Touch_6.0.1.0v1 ) and get the same errors.
I know enough about linux to break my stuff on my own (or to follow directions if I have them). This being said, I know that that app s2e installed a script on my phone (not sure where). I Imagine that script changed the mount points for internal sd and sd-ext (that is the point, after all). I also imagine that this is my current problem (I could be completely wrong, of course).
So I imagine that one possibility for fixing this would be to remount and reformat the sdcard from within adb shell. I imagine this might involve the fdisk tool (which I don't have much experience with) and perhaps even the /etc/fstab file.
here's the output from
Code:
/dev/block # ls
Code:
loop0 mmcblk0 mmcblk0p16 mmcblk0p23 mmcblk0p30 mmcblk0p38 mmcblk1p1
loop1 mmcblk0p1 mmcblk0p17 mmcblk0p24 mmcblk0p31 mmcblk0p4 platform
loop2 mmcblk0p10 mmcblk0p18 mmcblk0p25 mmcblk0p32 mmcblk0p5
loop3 mmcblk0p11 mmcblk0p19 mmcblk0p26 mmcblk0p33 mmcblk0p6
loop4 mmcblk0p12 mmcblk0p2 mmcblk0p27 mmcblk0p34 mmcblk0p7
loop5 mmcblk0p13 mmcblk0p20 mmcblk0p28 mmcblk0p35 mmcblk0p8
loop6 mmcblk0p14 mmcblk0p21 mmcblk0p29 mmcblk0p36 mmcblk0p9
loop7 mmcblk0p15 mmcblk0p22 mmcblk0p3 mmcblk0p37 mmcblk1
Remember, the error I get says it can't mount mmcblk0p37 (which is present on this list) or mmcblk038 (which is not present - maybe it was the sd-ext partition that is no longer there?)
If I hadn't just spent the past two days breaking my phone, I'd probably tinker around with fdisk, mount, etc myself, but I figured it'd be better to ask at this point instead of likely causing some catastrophic damage.
I did try factory reset, wiping /data, /system, /boot, etc... and reflashing the rom from scratch. Still no go. As I mentioned above, I also tried several different recoveries to try to wipe the internal sdcard. Something else I haven't tried yet is to reflash the RUU. I don't know if that would fix this problem, but if there's a chance that it will, I'll try it. (maybe someone can point me to the correct RUU to flash if this is necessary?)
Anyway. That's my problem. I hope someone can help point me in the right direction, because while 32GB in my external sd is plenty of room, that 16GB internal memory card would be nice... and I just don't like having broken stuff!
Thanks!
I want to downgrade my rom-based google maps (v. 7.x) to 6.14.4. I have downloaded the apk file for 6.14.4 and I can install it without trouble. But when I reboot the phone, the rom-based google maps is the only one present. Currently, I install 6.14.4 after each reboot, but that seems silly. It is not autoupdating from Google Play because Google Play offers an updated v7.x (and autoupdate is turned off).
I am thinking the I have to erase google maps som /system (being root) and then install a the old google maps (and possibly move it to /system). Is that the only way?
galmok said:
I want to downgrade my rom-based google maps (v. 7.x) to 6.14.4. I have downloaded the apk file for 6.14.4 and I can install it without trouble. But when I reboot the phone, the rom-based google maps is the only one present. Currently, I install 6.14.4 after each reboot, but that seems silly. It is not autoupdating from Google Play because Google Play offers an updated v7.x (and autoupdate is turned off).
I am thinking the I have to erase google maps som /system (being root) and then install a the old google maps (and possibly move it to /system). Is that the only way?
Click to expand...
Click to collapse
yep that is your best choice coz each time you reboot the system app is shown.
Use titanium backup to backup the app incase something happens and uninstall it and move your desired version to system app folder and check permissions
machokingjim said:
yep that is your best choice coz each time you reboot the system app is shown.
Use titanium backup to backup the app incase something happens and uninstall it and move your desired version to system app folder and check permissions
Click to expand...
Click to collapse
Thanks. I'll do that.
But when I checked /system/app, I saw many (not all) files that were linked to /preload like this:
ls -l /system/app/YouTube.apk
lrw-r--r-- root root 2013-09-25 11:29 YouTube.apk -> /preload/symlink/system/app/YouTube.apk
Checking /preload I see this:
mount | grep preload
/dev/block/mmcblk0p12 /preload ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/preload is another partition on the internal memory.
[email protected]:/system/app # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 30777344 sectors, 29.3M
Logical sector size: 512
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30775262
Number Start (sector) End (sector) Size Code Name
1 8192 49151 40960 0700 EFS
2 49152 51711 2560 0700 SBL1
3 53248 55807 2560 0700 SBL2
4 57344 73727 16384 0700 PARAM
5 73728 90111 16384 0700 KERNEL
6 90112 106495 16384 0700 RECOVERY
7 106496 311295 200K 0700 CACHE
8 311296 344063 32768 0700 MODEM
9 344064 1392639 1024K 0700 FACTORYFS
10 1392640 5586943 4096K 0700 DATAFS
11 5586944 29720575 23.0M 0700 UMS
12 29720576 30769151 1024K 0700 HIDDEN
p12 is 0.5GB, just like /system (that is p9).
Does anyone know if it is safe to modify /preload (p12)? It has more free space than /system:
df /system /preload
Filesystem Size Used Free Blksize
/system 503M 474M 29.0M 4096
/preload 503M 403M 100M 4096
It is confusing why Samsung has decided to split the files over so many partitions. It really limits the usability of the phone.
This version of SafeStrap is based on SafeStrap 3.75 but has a lot of differences with it:
- there is not more the splashscreen during the boot, to enter in Safestrap you have to select BP Tools in the Boot Mode Selection Menu(VolUp&&VolDown+PowerOn)
- has been added a Safe Rom slot that uses the unused partitions:
/preinstall (~ 600mb) for /system
/webtop (~ 1,4gb) for /data
/cache is shared with the Stock Rom slot
- in this version you have 6 slots: the Stock Rom slot, the Safe Rom slot and the four virtual slots
- the Safe Rom slot is faster than any virtual slot and safer than the Stock Rom slot
If you are using the original Safestrap you can simply install this new version over it and you will still have your roms in the virtual slots.
This version of Safestrap works like any other version of Safestrap and you can use the Stock Rom slot and the four virtual slots as you are usually do, the only thing that is a bit complicated is to install an aosp rom in the new Safe Rom slot that i provided in it.
DOWNLOAD AND GUIDE TO USE THE SAFE ROM SLOT
HOW TO POST REQUEST FOR HELP:
You have to entirely read this thread, I do NOT answer redundant question.
I do not answer to requests for help in private, I have neither the time nor the interest in doing so.
Any doubts, questions or requests must be posted in this thread in order to answer a single time and help everyone.
XDA:DevDB Information
Safestrap 3.75 for unused partitions (/preinstall & /webtop), Tool/Utility for the Motorola Droid RAZR
Contributors
Mentor.37
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2016-01-05
This thread is not about the ramdisks so do not ask about them.
In case of problems you can build the ramdisk as i explained in the main thread.
Waiting to xt910 support... Does this version support lollipop ROMs?
Yes it supports lollipop roms.
As i told in the previous post i need to know the size of the partitions /preinstall and /webtop of the xt910, if they are big enough i will surely build a version for it.
How can I help you with it.. I have the xt910 but I don't know how to get my partitions' sizes
major minor #blocks name alias
7 0 30292 loop0
7 7 4096 loop7
179 0 15564800 mmcblk1
179 1 128 mmcblk1p1
179 2 512 mmcblk1p2
179 3 512 mmcblk1p3
179 4 1 mmcblk1p4
179 5 512 mmcblk1p5
179 6 512 mmcblk1p6
179 7 4096 mmcblk1p7 pds
179 8 512 mmcblk1p8 utags
179 9 1024 mmcblk1p9
179 10 2048 mmcblk1p10
179 11 512 mmcblk1p11
179 12 512 mmcblk1p12
179 13 4096 mmcblk1p13
179 14 8192 mmcblk1p14 boot
179 15 9216 mmcblk1p15 recovery
179 16 217088 mmcblk1p16 cdrom
179 17 512 mmcblk1p17 misc
179 18 512 mmcblk1p18 cid
179 19 4096 mmcblk1p19 kpanic
179 20 793600 mmcblk1p20 system
179 21 737280 mmcblk1p21 cache
179 22 9216 mmcblk1p22 preinstall
179 23 1364992 mmcblk1p23 webtop
179 24 3989504 mmcblk1p24 userdata
179 25 8401792 mmcblk1p25 emstorage
179 26 128 mmcblk1p26
179 32 15630336 mmcblk0
179 33 15626240 mmcblk0p1
254 0 30292 dm-0
There it goes
Based on what you said and what I can see, our preinstall is very much smaller than yours... If understood it right we (XT910 users) have only 9 MB on preinstall partition... :/
You can check their size with:
fdisk -l /dev/block/preinstall
fdisk -l /dev/block/webtop
As I presumed, we have only 9 mb on preinstall partition
Mentor.37 said:
You can check their size with:
fdisk -l /dev/block/preinstall
fdisk -l /dev/block/webtop
Click to expand...
Click to collapse
for xt910 could you still use Web top for data, with system on SD card?
Sent from my XT907 using Tapatalk
I just uploaded a little update that fixes a problem in the layout of the new safe slot menu.
I also saw that this recovery has been downloaded a lot of times in few hours and i'd like to know if everything is ok, in this way i can remove the warning from the second post.
icarome said:
As I presumed, we have only 9 mb on preinstall partition
Click to expand...
Click to collapse
Well, as i suspected, then i can't build a similar version for it, i'm sorry.
Anyway i can tell you that some days ago i built a versione without the splashscreen at boot time for several devices, xt910 included, if interested you can find it here.
sd_shadow said:
for xt910 could you still use Web top for data, with system on SD card?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Yes i could but as i explained in the op the new safe slot in this version should be supported by the roms' mantainers with the editing of the fixboot.sh and for this i would avoid to create a lot of different versions to leave it the more "standard" possible. I'm afraid.
I used BMM over 2 years and I always tested roms on webtop partition which had 1.2 GB available for apps.I switched to SS just to be able to flash Lollipop.I miss BMM and I say that is still better than SS despite the fact that there is no longer support for it.
Is it possible to make SS like that? How come that XT 912 has bigger partition than XT 910? I thought they are the same phones except the radio...
Yes, me to i used bmm for more than an year on my xt894 and i loved it, for its second system it used this partitions layout:
- a virtual slot in /data/media/virtual/system_1/cache.img for /cache
- /cache for /system_2
- /webtop for /data_2
- /cdrom for /cache_2
and as you can see it did not use the /preinstall partition, at this point i think because on the xt910 /preinstall is very small.
Considering that on the xt894 we had /preinstall ~ 600mb and /webtop ~ 1,4gb i made a patch to change the layout for the second system in this way:
- /preinstall for /system_2
- /webtop for /data_2
- sharing the /cache partition between /system_1 and /system_2
but now bmm is an abandoned project that does not support the metadata and the SeLinux for the lp roms and for this i built this my personal version for the xt894 that installs a second rom in the unused partitions as i did with bmm with my patch and given that the xt912 has the same partitions with the same sizes i built a version also for it.
The xt910 and the xt912 are very similar but not identical, the xt912 is more similar at xt894 than at the xt910.
As i told in some post before you can verify what i'm telling simply checking the size of your partitions with these commands:
fdisk -l /dev/block/preinstall
fdisk -l /dev/block/webtop
I'm sorry.
Mentor.37 said:
Yes, me to i used bmm for more than an year on my xt894 and i loved it, for its second system it used this partitions layout:
- a virtual slot in /data/media/virtual/system_1/cache.img for /cache
- /cache for /system_2
- /webtop for /data_2
- /cdrom for /cache_2
and as you can see it did not use the /preinstall partition, at this point i think because on the xt910 /preinstall is very small.
Considering that on the xt894 we had /preinstall ~ 600mb and /webtop ~ 1,4gb i made a patch to change the layout for the second system in this way:
- /preinstall for /system_2
- /webtop for /data_2
- sharing the /cache partition between /system_1 and /system_2
but now bmm is an abandoned project that does not support the metadata and the SeLinux for the lp roms and for this i built this my personal version for the xt894 that installs a second rom in the unused partitions as i did with bmm with my patch and given that the xt912 has the same partitions with the same sizes i built a version also for it.
The xt910 and the xt912 are very similar but not identical, the xt912 is more similar at xt894 than at the xt910.
As i told in some post before you can verify what i'm telling simply checking the size of your partitions with these commands:
fdisk -l /dev/block/preinstall
fdisk -l /dev/block/webtop
I'm sorry.
Click to expand...
Click to collapse
Ok,here is what I got:
Disk /dev/block/preinstall: 9 MB, 9437184 bytes
4 heads,16 sectors/track,288 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/webtop: 1397 MB
4 heads,16 sectors/track,42656 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Update
Now we have an only Q&A thread shared between the xt894 and the xt912, in this way for me is easier follow the project.
I just uploaded in the download section the new version in which i cleaned the code and i also solved an error in it, now we should have a faster boot. I also updated the main thread with some useful info.
After what you've done I've noticed that I have at least 1,3 GB of useless space on webtop partition, so I decided to know more about this stuff and noticed that I can manually mount this partition and use this unused space. Now I just wish to know how can I automatically do it at every boot... I've created a mountpoint (a empty folder) on internal storage and mount webtop on it with this comand: mount -t vfat /dev/block/webtop /sdcard/extra it works like charm, but I didn't manage to do automatically, can you help me? Or anyone else?
You can put in /system/etc/init.d a script with permission 755 like this:
Code:
#!/system/bin/sh
mount -o rw,remount /
mkdir /storage/extra
mount -o ro,remount /
mount -t ext4 /dev/block/webtop /storage/extra
chmod 777 /storage/extra
Mentor.37 said:
You can put in /system/etc/init.d a script with permission 755 like this:
Code:
#!/system/bin/sh
mount -o rw,remount /
mkdir /storage/extra
mount -o ro,remount /
mount -t ext4 /dev/block/webtop /storage/extra
chmod 777 /storage/extra
Click to expand...
Click to collapse
Man thnx 4 this one! Now I can get rid off ScriptManager =)
by the way blkid shows that webtop's fs is ext3:
# blkid /dev/block/webtop
/dev/block/webtop: UUID="b564fc60-1780-4452-bbbf-5784b5833de9" TYPE="ext3"
Click to expand...
Click to collapse
I have cid deleted and im currently using bmm. And dats cos while i was using safestrap tho it can bypass cid bt my problem was dat my fone dosent charge while its off unlike bmm. Any fix for dis
Murphyung said:
I have cid deleted and im currently using bmm. And dats cos while i was using safestrap tho it can bypass cid bt my problem was dat my fone dosent charge while its off unlike bmm. Any fix for dis
Click to expand...
Click to collapse
Charging when off, that was the reason why I've switched to BMM from older version of SafeStrap. Which means it's impossible to calibrate battery. And that's what I was affraid when decide to take a try on early builds of CM12. So I've switched to not this but original SafeStrap 3.75.
Well in that version my phone does charge when off.
Eta for xt910 support?
[Troubleshoot] Android Phone in Read Only mode - "Internal SD" is unmounted/damaged
Android model: VKWorld VK700 old version, 1GB RAM/8GB ROM, MTK6582, running Android 4.4.2 (Kernel Version 3.4.67 [email protected]#1), rooted.
Problem: Phone works albeit very unstable. Looks to be locked in read-only mode. The internal storage was 1GB for apps, rest for the other various stuff including user data. Now phone sees only that 1GB, claims that "SD Card is damaged". ES Explorer claims "SD Card is unmounted". Can't mount it of course. I've put an external SD and that appears also to be Read only, but not sure about that (file explorers simply say copy failed).
Cause: Used an app (HKPHONEROMEDITTOR2014) that increases the partition size for the apps. Unfortunately it was set up for 4GB phones so it probably messed up my partitions/mount points, ebr's or something.
Tried:
Hardware reset/recovery does nothing, it says deleting stuff for 2-3secs, reboots, nothing changes. Uninstalling apps, making whatever changes and rebooting, phone again has all the same apps, needs the same updates etc. Copying files via ADB to say /sbin is successful. Reboot and the files are gone. Of course the same goes for apps. Install app, app works, reboot phone, app is gone.
Tried flashing the phone with various ROMS, from stock to custom, with various recovery images. Used two methods:
1) Via SPMultiPortFlash and .bin images, flashing fails at the end producing a CHKSUM(EBR1) ERROR.
2) Via SP_Flashtool and .txt scatter. Flashing is reported success. The progress is correct, everything should be ok. However boot into the phone, nothing changes. Selected Firmware upgrade, Format and download and download only, doesn't make a difference. Selected format flash, reported success. Again, nothing changes.
Installed busybox, checked parted and fdisk. Parted doesn't work (can't have partition outside the disk error). Checked fdisk, internal flash size is reported correct, two blocks start before they end
Code:
/dev/block/mmcblk0p1 Start 65: End 64
/dev/block/mmcblk0p6 Start 260033: End 64
however the exact scheme is followed by a stock VK700pro (same processor / ROM size) so I don't think that's the problem.
Included below are whatever I could think that might be of other help to troubleshoot.
Can anybody give me a hand? I am way beyond my waters here, I had zero knowledge about flashing / linux / rooting etc up until yesterday and my mind is all mush right now from all the reading...
vold.fstab
Code:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
dev_mount usbotg /mnt/usbotg auto /devices/platform/mt_usb
vold contents:
Code:
brw------- root root 179,0
brw------- root root 179,1
brw------- root root 179,2
brw------- root root 179,3
brw------- root root 179,4
brw------- root root 179,5
brw------- root root 179,6
brw------- root root 179,7
brw------- root root 179,8
brw------- root root 179,96
brw------- root root 179,97
/proc/partitions
Code:
7 0 1254 loop0
253 0 524288 zram0
179 0 7605248 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 921600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 2097152 mmcblk0p7
179 8 4374016 mmcblk0p8
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 3858432 mmcblk1
179 97 3857408 mmcblk1p1
So to recap:
Mount points are messed up. Partitioning is messed up. EMMc is on read only because of that, so can't flash a new ROM or recovery. Current recovery does nothing but erase for 1-2 secs something (which is not the /data partition) and reboot the phone. There's no option to delete caches, delvik etc. Fastboot erase takes hours and does nothing. It produced a "too many links" but I think that's because the phone eventually died of because of the battery (I'm retrying with full charge and new usb port). Bootloader is locked on the device so can't use fastboot to try to flash the device that way.
Is there any way to ef2chk the /dev/block/mmcblk0 from edb shell? I can't since it's being used by the system, maybe unmount it or something?