[SOLVEDL]Y not booting with kuro kernel - Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl

Heyyyy buddies
I was using ussrv5+kuro kernel 1+ akurodata2sd
Today I thought of uninstalling games and apps cause of 12th board, cet, aieee...
After uninstalling 32 apps...
I open cf3d and uninstalled it my phone rebooted with lots of force closes then it stuck on splash screen
I restored my latest backup
Same fate
Went to internet cafe downloaded DDLF2 odin pack (thanks to sir docky73)
Flashed it and phone booted..
After that restored my backup and wow it booted...
Bt kernel was stock one
My all apps were gone...
So I flashed kuro kernel and again it stucked at splash screen
So I flashed stock kernel
Now all my apps are gone..
They were in 2nd partition
So which kernel should I flash????
And worst thing
I heard a conversation in my cell
Stock Kernel to battery: Babes I am gonna eat you
Battery:noooooooo!!!!! Somebody plzzz save me
Sent from my GT-S5360 using xda premium

Use savies rev 73, the easiest to install and user-friendly kernel yet with very good performance imo..I had problems booting with kuro kernel for some ROMs (having custom kernels), but with savies kernel never had a problem
Merruk Dev 7 would be the best performing kernel out there, but a bit tricky to get it installed..

thats's akuro failure. the phone didn't boot because the data inside ext partition is different with the one used by system. you must delete /data folder inside your sdcard partition to boot up. after that you can copy /data/data into /system/sd/data as usual. if you don't know how to delete /data folder inside your sdcard, the easiest way is reformat your partition.

kurotsugi said:
thats's akuro failure. the phone didn't boot because the data inside ext partition is different with the one used by system. you must delete /data folder inside your sdcard partition to boot up. after that you can copy /data/data into /system/sd/data as usual. if you don't know how to delete /data folder inside your sdcard, the easiest way is reformat your partition.
Click to expand...
Click to collapse
What if I delete akuro script from init.d and make a complete wipe of 2nd partition...
Or
Which partition I should delete???
/sdcard/data or /data/data
P.s. I never moved my /data/data to /system/sd/data
Sent from my GT-S5360 using xda premium

for safety reason you can delete (or copy into somwhere else) all files in your init.d folder and wipe 2nd partition. after that you can move your tweaks into init.d again. this step might a lil bit inconvenient but in this way we could boot up the system succesfully and easily diagnose the problem source.

kurotsugi said:
for safety reason you can delete (or copy into somwhere else) all files in your init.d folder and wipe 2nd partition. after that you can move your tweaks into init.d again. this step might a lil bit inconvenient but in this way we could boot up the system succesfully and easily diagnose the problem source.
Click to expand...
Click to collapse
Going to try it
Edit: it booted yeppie yesss..
Two things sir kuro
1 thanx a lot
2 plzzz give me your brain
Sent from my GT-S5360 using xda premium

Problem2: how to get apps back
Erasing /data/data will work
Sent from my GT-S5360 using xda premium

if you have TBU you can use it to recover your backuped apps

I want to use my second partition so I think I shuld delete useless data in /data/data/
Sent from my GT-S5360 using xda premium

umm...you better don't touch any of them. you can copy /data/data to /system/sd/ to activate dt2sd function and prevent system to write your original /data partition but you'd better don't delete/modify them

kurotsugi said:
umm...you better don't touch any of them. you can copy /data/data to /system/sd/ to activate dt2sd function and prevent system to write your original /data partition but you'd better don't delete/modify them
Click to expand...
Click to collapse
I will try titanium backup to recover apps....
Thanks
Sent from my GT-S5360 using xda premium

Terminal command to wipe 2nd partition plzzz
Sent from my GT-S5360 using xda premium

Code:
su
mount -t extX -o nosuid,nodev /dev/block/mmcblk0p2 /system/sd
note:
1. extX - replace X with your type partition
2. its mmcblk[zero]p[two]
after executing these command you can go to /system/sd then delete all files there. if you don't have any app backup you can move the /app content to your sdcard. in this way you can reinstall all your app later.

Related

switching to cm7#199.( ended up in cm7#203)

dudes i am planning to switch to #199 cm7.
the plans are...
1) fresh flash #199 with 2.6.32 buzz kernal.
2) dta2sd beta 3,jewz ram script, sd speed increase script(4068) .
3) custom mtd partition with 170mb system and 30 mb cache.
4) data and app to sd ext4.
5) 8gb class 4 sd partitioned to 1gb ext4, 32mb swap, rest with fat32 with a large allocation value.
6) lot of paid app of course.
i need your suggestions ....
thanks in advance.
Sent from my HTC Wildfire using XDA App
Do the mtd partition as you install 199, I got problems when a2sd was already installed, my mtd settings are 140 10, 10mb works fine for cache just make sure you have 06mountdl in your init.d folder otherwise you wont be able to download anything from the market above 10mb in size, if it isn't in the init.d folder you should find it in the cm zip.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Do the mtd partition as you install 199, I got problems when a2sd was already installed, my mtd settings are 140 10, 10mb works fine for cache just make sure you have 06mountdl in your init.d folder otherwise you wont be able to download anything from the market above 10mb in size, if it isn't in the init.d folder you should find it in the cm zip.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
dude i haven't heared of init.d folder. pls explain. well i surely plan to give 25 mb cache. if so do i need to care about init.d folder?
" just make sure you have 06mountdl in your init.d folder" dude i realy dont understand this.
" if it isn't in the init.d folder you should find it in the cm zip." and this too i dnt understand.
so i am a newbee to custom mtd partition. hence i need help about this. how should i need to use the script? i plan to flash it soon after i reboot to #199. only after that i will install my apps.and also gapps. so do i need to take nandroid backup? as i have backups of my app using titanium backup. so i will install every thing later.
Sent from my HTC Wildfire using XDA App
Put the files needed on your sd card and write your settings in the txt file.
Run the first part of the mtd partition (wipe system/data/cache and install the first zip, bravo recovery or something like that, reboot your recovery from the advanced setting.
After doing the first step install your fresh copy of cm7 (instead of the nandroid backup) without wiping anything, then run the bravo boot zip and let it boot before installing anything else.
Files from the market, when first downloaded go to your /cache folder which if set to only 10mb would mean you can only download files below 10mb in size, the 06mountdl script deals with this by diverting the downloads elsewhere /data partition I think (not sure), the scripts are found in /system/etc/init.d after installing cyanogen if your cache size is small just check that folder (with root explorer) as a few times I have had to extract 06mountdl from the cm7 zip because it hasn't installed.
All that happens if 06mountdl isn't there is, when you go to the market you'll get an annoying message saying you don't have space left if the filesize of the app is larger than your cache.
Hope that made sense its 7am here.
Sent from my HTC Wildfire using xda premium
thanks for your help dude. i will check it out. also do i need to flash dta2sd b4 or after i install apps. i had done it b4 i install apps in my current rom#177. do you have any suggestions?
Sent from my HTC Wildfire using XDA App
Not entirely sure, I know some people say before but its never harmed me doing it after, you may aswell just run it straightaway though after your first reboot. Just in case.
I only use beta 3 as I had problems with beta 4, I don't think there's any noticeable changes between them tbh.
Sent from my HTC Wildfire using xda premium
k. i will check it. and will post my experience. thank you dude. see you soon.
Sent from my HTC Wildfire using XDA App
So i ended up in cm7#203. Stable. Fast, like it a lot.
The sad thing is i can't make custom mtd. Every time i ended in a non booting cm7 boot screen. Actually i had to flash froyo 2.2.1 ruu 2 times. Rooted, installed cwm. 2 times. Coz i had done like u said. Flashed custom mtd recovery with mtdpartmap.txt file containing 160 25. Then installed new rom with a reboot of recovery only.also flashed bravo boot. All as you said. Stuck in splash screen. So again tried to flash new rom and kernel from recovery. Still the same after flashing. So again ruu flash. Install custom cwm v5.xxx.partitioned SD. This time the SD got corrupted. So removed custom cwm and put original cwm using fastboot flash. Then partitioned with out errors. And installed cm7#203 from cwm, SD speed increase script,Jews ram script,2.6.35 kernal, latest radio, mediaprofile patch, gapps for 2.3.5 Andy. Rebooted after dalvic wipe. Itz running perfect. Installed s2e app . Moved app,private app, data, to ext.
I think that s2e is more efficient than dta2sd. It is faster, move almost every thing to ext. And internal memory consumption is quite low after app installations(when compared to dta2sd). Also booting and shut down are faster.
I will be watching for future errors. Thank you.
Sent from my HTC Wildfire using XDA App

[Help] Flashing zip files off sdcard

EDIT: Ok, I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Hi there,
A few weeks back I flashed Paranoid Android onto my phone (latest release), however now I have discovered that in recovery mode, my phone can't read or mount the sdcard, i.e. I can't apply updates.
Code:
If I select 'Install zip from sdcard > Choose zip from sdcard' I get:
E:Can't mount /sdcard/
And if I try 'Mounts and storage > mount /sdcard' I get:
Error mounting /sdcard!
I would really appreciate any help on this issue.
Note it was working previously (which is how I installed the ParanoidAndroid ROM) but now my phone can't read the sdcard in recovery. IT CAN READ IT ONCE THE PHONE HAS BOOTED UP.
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
thekguy said:
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do and will post the results, but before I do, would that show anything because the sdcard works fine once the phone has booted up?
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
thekguy said:
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
But I can't flash using recovery, so how would I test Quarx's build? Haven't had time to boot up my windows partition, but I will eventually.
EDIT: Ran fsck on fedora partition (forgot about the command). It came up with this
Code:
fsck from util-linux 2.21.2
e2fsck 1.42.3 (14-May-2012)
fsck.ext2: Is a directory while trying to open /media/CDF2-6BE2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I've backed up my SDCard and am going to run e2fsck command (will post results) otherwise I'm going to have to reformat it
EDIT 2: Came up with same error. Should I reformat it? As ext3/ext4? What should I do?
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
thekguy said:
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Code:
/dev/sdb vfat 7856128 1361952 6494176 18% /media/CDF2-6BE2
Now I've checked fsck again
Code:
fsck.vfat /media/CDF2-6BE2/
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Read 512 bytes at 0:Is a directory
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
thekguy said:
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do
EDIT:
Code:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.
OK, Am backing up now. Will reformat as fat32
Ok... So now I've formatted as fat32, tried again, flashed full sbf, re-rooted phone, installed 2nd-init, flashed Quarx's latest build (before wi-fi experimentation builds) and still I have the problem
Sorry for the triple post
I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Any suggestions on how I might be able to fix this?
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
thekguy said:
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you could show me how to do that, I would so extremely grateful
Aparently there was a similar problem with the Defy running the 'official' CM and the wiki documented a fix here: http://oldwiki.cyanogenmod.org/wiki/Motorola_Defy:_FAQ#SD_Card
Do you think that could possibly work for the Defy+?
EDIT: However if I make a .zip file, would that put my phone in bootloop though? Because whenever I reinstall 2ndInit (v2.3) and it 'downgrades' my CWM/Bootmenu it causes a bootloop where I have to reflash everything. If I make a .zip that I flash after each install would it cause the same problem because it's 'downgrading' from the Bootmenu/CWM of the JB CM10 ROM.
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
thekguy said:
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I really appreciate your help! I guess you could perhaps guide me in doing it, or I could wait till you've got a wroking computer.
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
thekguy said:
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
Click to expand...
Click to collapse
Thank you very much, I'll definitely try this out!
EDIT1: First attempt, didn't work
Trying something again...
EDIT2: Second attempt.... Put phone into bootloop :\
EDIT3: Third attempt... Seems like a bootloop again
So basically it changes the Recovery version (not the bootmenu) and puts it into bootloop :\ however I can flash via recovery.
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
thekguy said:
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yeah I can enter bootmenu during bootloop before it starts. I'll retry with the recovery folder only.
EDIT: Wow it worked! Thank you so much I hope you don't mind too much, but if you can modify the recovery slightly that it'd help out a lot and make everything perfect. But I can't thank you enough
I'll upload my working Patch.zip:
If you can do these, that would be amazing: (this is from the working CWM)
1) When I select 'Wipe data/factory reset' it says 'Formatting /data...' and then immediately says 'Formatting /cache...' and when the phone boots up, all my data is there. Now that isn't a problem as such but if I needed to do a clean install that may cause some issues.
2) This isn't a problem, but I was wondering if you could add a printed line whenever I execute the 'Wipe dalvik cache' because it wipes it very fast, but doesn't say anything in the console so I'm not sure if I clicked it or not. Nevertheless when I boot my phone up it says optimising apps which means that it worked.
But yeah only minor things.
Thank you so much
1)I can't modify the recovery, since I'm not really a dev but I can try to make you another zip to wipe data separately
2)Again, that is something coded in the recovery, which I don't know how to alter. Plus, my computer isn't working again(bad ram :banghead: ) so I'm limited to the phone
But are you able at all to wipe data from the custom recovery? Bootmenu? Are both not working?
Sent from my MB526 using xda premium

[Q] Mount partition without init.d?

Ok guys, this is my first post since i've joined this forum for a long time.
I've a question, how does Link2SD work on stock ROM without init.d support?
I mean the mount script. How does it work?
For example:
I've mounted my 2nd partition to /data/myext via terminal emulator. everytime i am restarting my phone the partition just lost (unmounted) so i've to mount it again via terminal emulator manually.
Are there any way to mount my partition automatically every boot?
Sorry for my bad english
It's the work of a custom kernel sir. Not bad for a first post, you created a topic in a wrong section. This should be in Q&A.
Sent from my GT-S5360 using xda premium
CrazeXDA said:
It's the work of a custom kernel sir. Not bad for a first post, you created a topic in a wrong section. This should be in Q&A.
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
I'm sorry if i wrong posted here.
But, link2sd doesn't need a custom kernel to run sir. Link2sd can run in stock rom + stock kernel and without init.d support.
crash.override said:
I'm sorry if i wrong posted here.
But, link2sd doesn't need a custom kernel to run sir. Link2sd can run in stock rom + stock kernel and without init.d support.
Click to expand...
Click to collapse
As far as I know, Link2SD uses a init.d script to mount the partition of the sdcard at boot, so a kernel with init.d support is required for the auto-mounting at boot.
I heard about an app wich enables init.d support on stock kernel, but i dont remember the Name nor if it was here in SGY section or in Android apps and games section.
Also I think, Tasker can mount the partition at boot, if you make the boot condition as trigger for a shell script, wich mounts the partition, but I dont know, if ist working this way.
adi2500 said:
As far as I know, Link2SD uses a init.d script to mount the partition of the sdcard at boot, so a kernel with init.d support is required for the auto-mounting at boot.
I heard about an app wich enables init.d support on stock kernel, but i dont remember the Name nor if it was here in SGY section or in Android apps and games section.
Also I think, Tasker can mount the partition at boot, if you make the boot condition as trigger for a shell script, wich mounts the partition, but I dont know, if ist working this way.
Click to expand...
Click to collapse
I think Link2SD doesn't use init.d, because i'm using a STOCK ROM and STOCK Kernel without init.d support and link2d is still working. I've also checked my /system/etc folder, and there is no init.d folder. So LINK2SD doesn't use init.d i guess
Btw, what is that tasker? Can you explain me? I'm new to linux & android.
crash.override said:
I think Link2SD doesn't use init.d, because i'm using a STOCK ROM and STOCK Kernel without init.d support and link2d is still working. I've also checked my /system/etc folder, and there is no init.d folder. So LINK2SD doesn't use init.d i guess
Btw, what is that tasker? Can you explain me? I'm new to linux & android.
Click to expand...
Click to collapse
Link2sd only uses the init.d folder if you partitioned your sd card.
Sent from my GT-S5360 using xda premium
CrazeXDA said:
Link2sd only uses the init.d folder if you partitioned your sd card.
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Sent from my GT-S6102 using Tapatalk 2
I've partitioned my sdcard. I've created mount script to mount my 2nd partition. I've seen /data/data folder, it's a 2nd sdcard partition, right? So the 2nd partition has mounted.
But you said that link2sd used init.d, but i'm using a stock rom without init.d support, i checked my /system/etc and there is no init.d folder, so my rom doesnt support init.d.
So i think Link2sd doesnt use init.d script to mount 2nd partition every boot
So, how do i mount my 2nd partition without Link2sd and without init.d support. Because link2d has done it.
crash.override said:
Sent from my GT-S6102 using Tapatalk 2
I've partitioned my sdcard. I've created mount script to mount my 2nd partition. I've seen /data/data folder, it's a 2nd sdcard partition, right? So the 2nd partition has mounted.
But you said that link2sd used init.d, but i'm using a stock rom without init.d support, i checked my /system/etc and there is no init.d folder, so my rom doesnt support init.d.
So i think Link2sd doesnt use init.d script to mount 2nd partition every boot
So, how do i mount my 2nd partition without Link2sd and without init.d support. Because link2d has did it.
Click to expand...
Click to collapse
No, you're wrong sir. Link2sd only ENABLED your 2nd partition! Without init.d support, your 2nd partition can't be mounted every boot. That's the purpose of the script, to mound the sdext2 every boot.
Btw, i think what you're asking is impossible. Sorry 'bout that.
Sent from my GT-S5360 using xda premium
CrazeXDA said:
No, you're wrong sir. Link2sd only ENABLED your 2nd partition! Without init.d support, your 2nd partition can't be mounted every boot. That's the purpose of the script, to mound the sdext2 every boot.
Btw, i think what you're asking is impossible. Sorry 'bout that.
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
How about install-recovery.sh in /system partition
When I opened it with root explorer there is a command to mount 2nd partition
Code:
mount -t ext2 -o rw /dev/block/mmcblk0p2 /data/sdext2
Click to expand...
Click to collapse
Sent from my GT-S6102 using Tapatalk 2
crash.override said:
How about install-recovery.sh in /system partition
When I opened it with root explorer there is a command to mount 2nd partition
Sent from my GT-S6102 using Tapatalk 2
Click to expand...
Click to collapse
hi did you find your answer ? id like to do the same , mount a folder to another folder before the ui and apps get started

Link2sd / foldermount not working

Morning all,
I'm having the usual issues with internal space on my (rooted) s5360. I have tried:
Foldermount - won't work because /data/data isn't seen.as being on the internal SD card?!?
Link2sd - works on a fat/fat sd card only, then after reboot says "invalid argument" and won't mount. I've used Easus, Minitool and CWM to partition, but to no avail.
Directorybind - doesn't see any folders in /data
Are there any other ways to move / symlink monster apps like games and facebook to my SD?
Sent from my GT-S5360 using xda app-developers app
With link2sd you need a kernel that can support ext4 partitions
steps to follow if on stock based rom
flash hells fusion #50 kernel
copy contents of sd card to pc
goto recovery mode on phone
in cwm partition sd card with at least 1024mb ext partition
swap is not required
restart phone
open link2sd
create mount script as ext4
Restart
Open link2sd & check 2nd partition now shows
copy everything back to sd card
restart
Having had to restore with Odin after messing about with kernels / roms (I need to run stock rom to avoid phone nework cutoff) I'm not keen on this approach.
I can't see why l2sd would work after a reboot with ext4 when it won't with fat.
Is there no other app that can be used as an alternative?
What about manually creating symlinks?
Sent from my GT-S5360 using xda app-developers app
thephatmaster said:
Having had to restore with Odin after messing about with kernels / roms (I need to run stock rom to avoid phone nework cutoff) I'm not keen on this approach.
I can't see why l2sd would work after a reboot with ext4 when it won't with fat.
Is there no other app that can be used as an alternative?
What about manually creating symlinks?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Because it needs kernel support
you won't have any problems running stock rom with hells fusion #50 kernel as long as you are not using DDMD1 baseband as that requires a different ramdisk
Install REPENCIES ROM PLUS REPENCIES KERNAL it has all support u need.
U cank also use darktremer app2sd . Its much better then link2sd & can transfer delvink also to sd.
Seach xda you will find everything
Thank you for helping me

[How-To][P3100][CM11][dataOnExt] use second partition of external SD-Card as /data

Hi,
I was looking for a tutorial how to use a second partition of the external SD card as /data partition. 1 day and about 10 complete system wipes later...
How I mounted the second partition oft my sdcard as /data:
You have:
a P3100 (not tested on others yet)
Cyanogenmod 11 Rom
a fast micro sdcard -32GB
Step 1 prepare the sdcard: you need a fat32 partition and a Ext4 partition (use a PC with a cardreader and gparted or something like that)
Step 2 For the sake of simplicity, I am going to assume you already installed your rom and the tablet is rooted
Form a terminal with su:
create a directory
Mount the second partition (/dev/block/mmcblk1p2) on that directory
copy -a -v /data/* yourDirectory/
Step 3 - modifing the rom and fstab.espresso
Now you have to extract the boot.IMG Form your rom, using dsixda's Kitchen
In case you have no idea how to use this kitchen (like me) here is someone doing exact what we need
After changing in the BOOT-EXTRACTED directory, you have to edit the fstab.espresso...
simply replace the mount source of
Code:
/data
with
Code:
/dev/block/mmcblk1p2
save the file and rebuild the rom
Step 4 install your new rom with cwm and reboot...
If everything went well the second partition of your sdcard is now mounted as /data
My internal storage is now (in the storage view of settings) about 20GB big and i will never have to use link2sd or apps like that again
Nice side effect the access to the highspeed sdcard is a bit faster than the access to the internal storage
You have to modify all updates oft your rom in the same way before installing them
ToDo write a script to automate the process
PS.: plz tell me if something is unclear or not understandable or this is the wrong place for this thread OR you know a shorter way to do this (thats my first post here)
Farbdose said:
...
In case you have no idea how to use this kitchen (like me) here is someone doing exact what we need
..
Click to expand...
Click to collapse
Happy modding! Feel free to quote any or all of the thread, just give credits where it is due
On a related note - have you confirmed this to be working in your device? And does your device use a part of the /data partition as internal SD Card (/data/media fused to be /sdcard)?
OK thank you,
Yep its working, the complete /data is on the sdcard now including /data/data and /data/media, my internal storage is now about 20gb big xD
I am not really sure if there are crazy symlinks in /data but atm i have no problems
The "real" sd partition is still fat32 formated and used as before the modification, and because i didn't mount the second partition anywhere (only as /data) the rest of the system doesn't know that it exists...
(problem: there is now a unused /data partition on my internal tablet storage and i have no real idea how to use this free storage)
Sent from my GT-P3100 using XDA Premium 4 mobile app
You can mount it to /data/dalvik-cache - check my thread
Sent from my GT-N7100 using XDA Premium 4 mobile app
thats indeed a usefull usage oft the old data partition thx
Sent from my GT-P3100 using XDA Premium 4 mobile app

Categories

Resources