Related
Yesterday I helped my gf to root her phone. Because she would like to keep her stock ROM and not wanting to use stock ROM, I used CF-Root (http://forum.xda-developers.com/showthread.php?t=1158197) to root the phone.
After that, I install DT A2SD (http://forum.xda-developers.com/showthread.php?t=715940) and run it on stock rom. I moved dalvik cache and data to sd card. After rebooting, the phone slows down alot. Media scanning took few minutes and the phone performs laggy. So, I thought moving dalvik cache to sd card is not a good idea, i moved it back to internal. The result is still the same. I moved back the data too to internal. And still, laggy and media scanning took very long.
Oh, I partitioned the sd card with CWM. 1gb for partition
Can anyone guide me?
TL; DR ver.
1) Gf wants to keep stock ROM and move data to SD card since apps are taking up spaces
2) So, CF-rooted it and installed dt a2sd, moved dalvik n data to sd.
3) Phone performance quite slow and took long time for sd card finish scanning.
4) Moved back dalvik n data to internal, doesnt help at all..
DXKPB 2.3.4
There's a Tweak manager included from Cf-root, but I dont know whether I should meddle with it.
Is there anyway to remove the lag?
the class rating of your sd card is too low ie too slow.
what is the speed of the sdcard? higher class means higher read/write speed eg class 6 is faster than class 4
btw install and use this to completely disable media scanning when boot and when unmount device from pc. reopen the app when u wanna trigger media scan. that app helps me alot by making boot much, much faster because media scanning is disable
Her sd card class : 4
Sometimes running some apps or playing music, the loading time is long. =\
Funny that Im running on cm7 kang + dt a2sd with sd card class only 2 and I dont experience similar problem.
Hmmm anything could be possible then e.g. too many apps attempting to startup together during bootup. One can only tell by using an app like Autostarts.
I have tried using an sd-ext partition when i was on the rfs file system and things weren't slow to make me frustrated but certainly no complaints appreciating the speed increase after changing the file system to ext4 overall.
I did a quick search and found this thread.
http://forum.xda-developers.com/showthread.php?t=1344542
Saw your link there to convert rfs file sys to ext4. But before that, how do I check my stock rom is rfs type? Just wanna take precaution not to brick the phone..
if its stock, its sure is rfs.
WishFinder` said:
I did a quick search and found this thread.
http://forum.xda-developers.com/showthread.php?t=1344542
Saw your link there to convert rfs file sys to ext4. But before that, how do I check my stock rom is rfs type? Just wanna take precaution not to brick the phone..
Click to expand...
Click to collapse
i used ext4manager from ketut in his CF Root thread. Since you are on CF Root kernel, it will show you whether you are on rfs or ext4. this is actually a pointless exercise cos as anonymous pointed out, it is almost confirmed for sure that you are on rfs. Anyway this ext4manager allow you to do an one click conversion to ext4 file system too. i think that should interest you even more.
ok, so i have installed ketut's modified app and tried that but it seems like ext4 manager is showing no ext4 partitions found. Then I tried CF's original ext4 manager app. This time, it shows no ext4 part found but the "convert rfs to ext4" is clickable. after clicking it, it rebooted into CWM and failed to convert it. Everything happened too fast on CWM screen. I saw "installation aborted".
edit: it also shows "CF kernel not found"
edit 2: I reinstalled ketut's app. and this time it works. Successfully converted to ext4. But it does not improve the performance. Still very slow and laggy when running apps.
why dont you install autostarts and expand event called after startup to see how many apps are jostling to startup?
happily1986 said:
why dont you install autostarts and expand event called after startup to see how many apps are jostling to startup?
Click to expand...
Click to collapse
well because I dont experience such similar problem before rooting and installing dt a2sd. If there are 20 apps jostling to start up without problem before, I wonder what's the prob that caused the lag and slow prob after root and a2sd since they are the same 20 apps earlier
Disabled some apps. Prob still persists.
I think sd partition via CWM is buggy. Faced similar prob. I'm gonna try format the sd card and repartition it via Minitool
ok for me i did my partition not via CWM. I am going to hazard a guess and say that you created an ext3 sd-ext partition in CWM. As far as i know, CWM makes ext3 partitions.
try using mini tools and inform us of your progress.
Okay. So I partitioned 1st as FAT32 and 2nd as ext4. Both also Primary. Now ended up bootlooping. -.- gah. dont know what's wrong with it.
edit: wth.. The phone auto switch back on even I off it via CWM.
WishFinder` said:
Okay. So I partitioned 1st as FAT32 and 2nd as ext4. Both also Primary. Now ended up bootlooping. -.- gah. dont know what's wrong with it.
edit: wth.. The phone auto switch back on even I off it via CWM.
Click to expand...
Click to collapse
If it doesn't work , try partitioning using CWM .
For that power off in CWM , it's bugged
Sent from my GT-S5830 using XDA App
I already partitioned that at first. I think it's not compatible and makes things slow?
Hi! guys i decided to do an ext 4 with mini tools and when i hit apply it shut s down my LT and started to do the partitioning, when it was done my F:\ disappeared now i m getting dreaded code 10 error in my device manager and the worst part was when i inserted the sd into the ph it could'nt read the card luckily i could get CWM to reformat and partition as it was a new 16gig. I had to reinstall my rom again and had it sent via BT to the phone so i could flash and i had to do it twice as the rom i was using had a flash over update. Right now i m still figuring how to get over the code 10, tried disabling,uninstalling,update software drivers u name it. Right now i m waiting for someone to sent me an adaptor could be it is corrupted as well. sigh!!
If your sdcard is like this , use Gparted to rewrite the partition table
Sent from my GT-S5830 using XDA App
i am not sure whats going on with my galaxy, but it doesn't mount memory partitions; right now i am using checkrom V6 + siyah kernel. i had this SAME problem with vk rom, so i exclude it's anything rom related, like a bad rom or what.
i shall say that both these roms are XWLA4 based, and i never ever experienced the same issue with every other rom i used before XWLA4 came out.
it just happens randomly; i installed the whole system, removed a few apps, installed a few others, used the phone for some days with various reboots and all was good.
all of a sudden, after booting there are no memory partitions mounted, none of them -internal and external-
doing a cache + dalvik cache wipe doesn't help; after wiping, system mounts memory partitions correctly but the following boot messes everything again.
flashed again siyah 2.6.11 and 2.6.12 - didn't help.
when booting in recovery, i can browse memory partitions without any problem, which leads me to exclude any hardware failure.
help needed, please.
Unless its on stock rom its probably not hardware .
If you are using ICS based rom its a rom built on a leaked buggy test rom problems are part of beta .
Full wipe and install of official stock rom with custom rom counter zeroed and it is back under warranty .
jje
well, XWLA4 means it is based on official samsung build, so it's no beta ics thing.
what do you mean by "install of official stock rom" ? do you mean official samsung release without any root?
it seems that waiting a few secs after phone boots resolves it, although i am almost sure i tried waiting some other times but it didn't help..
Hi,
Did you try to use another SD card? Maybe it's "just" a card issue...
Sent from my GT-I9100 using Tapatalk
uhm no, i didn't try using another sd card, it's just that when phone doesn't mount memories, it doesn't mount both internal and external ones, so i am confident it's not an issue of the micro sd car; it should be something on the software side..
at the moment, waiting a few seconds after phone boot resolves it.
well, thank you both for your replies.
So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Irradium said:
So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Click to expand...
Click to collapse
Good to read a thread with a quick "happy ending"!
Good work mate!
// Ohamn
:crying: well, as you may read I had bricked my nook tablet of 16 GB, i was installing cm 10 , it worked fine but I forgot to do the factor reset to delete Google apps, so I had my nook tablet with CM 10 and then upgraded the screen so it could have 10 sensitive points, but it would not open youtube or the market, after realizing this i tried to install gapps WITHOUT deleting the ones already installed, (i know stupid) so now the tablet would not launch cm 10, it would stay stuck on the start-up with the blue circle of cm. Then i would only go into CWM and i managed to install and run cm9 but i could not use the touch screen, I thought it was because of the screen upgrade, stupidly i formatted partitions and wipe data and cache and messed with things i shouldn't thinking i could make it work, so yeah after that i could only get to cwm without the ability to install anything becase either 1) it wouldnt work, 2)it would say something about ext4 or fat32, or 3) It would say it could not open the package because it was corrupted. Tired of all this i sured into the web and tried some things that didn't work , i tried these :
http://forum.xda-developers.com/showthread.php?t=1657159
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
And some others that i tried but i dont remember them, but the most important was this one : http://forum.xda-developers.com/showthread.php?t=1605664 , it said it could repair ANY Brick but it just made my semi-bricked nook into a Total death Nook brick, (I'm not saying anyone is responsable for this im just saying)
I tried this many times with a sandisk 2gb and pretty much sure i had tried all how to less the ones that use a sdcard of more than 2 gb because i dont have.. anyone knows how to fix this?? i cant use a bootable CM, already tried and didnt worked,
PD: I think my partitions are messed up too because when i am in cwm from a bootable sd , my serial number is "00000000000" , and i dont have a backup... My Nook has been brike for almost a month , And sorry if i said something with no sense, i had not fully learned the language, i speak it very well but this is kindda harder :crying:
djjean19 said:
:crying: well, as you may read I had bricked my nook tablet of 16 GB, i was installing cm 10 , it worked fine but I forgot to do the factor reset to delete Google apps, so I had my nook tablet with CM 10 and then upgraded the screen so it could have 10 sensitive points, but it would not open youtube or the market, after realizing this i tried to install gapps WITHOUT deleting the ones already installed, (i know stupid) so now the tablet would not launch cm 10, it would stay stuck on the start-up with the blue circle of cm. Then i would only go into CWM and i managed to install and run cm9 but i could not use the touch screen, I thought it was because of the screen upgrade, stupidly i formatted partitions and wipe data and cache and messed with things i shouldn't thinking i could make it work, so yeah after that i could only get to cwm without the ability to install anything becase either 1) it wouldnt work, 2)it would say something about ext4 or fat32, or 3) It would say it could not open the package because it was corrupted. Tired of all this i sured into the web and tried some things that didn't work , i tried these :
http://forum.xda-developers.com/showthread.php?t=1657159
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
And some others that i tried but i dont remember them, but the most important was this one : http://forum.xda-developers.com/showthread.php?t=1605664 , it said it could repair ANY Brick but it just made my semi-bricked nook into a Total death Nook brick, (I'm not saying anyone is responsable for this im just saying)
I tried this many times with a sandisk 2gb and pretty much sure i had tried all how to less the ones that use a sdcard of more than 2 gb because i dont have.. anyone knows how to fix this?? i cant use a bootable CM, already tried and didnt worked,
PD: I think my partitions are messed up too because when i am in cwm from a bootable sd , my serial number is "00000000000" , and i dont have a backup... My Nook has been brike for almost a month , And sorry if i said something with no sense, i had not fully learned the language, i speak it very well but this is kindda harder :crying:
Click to expand...
Click to collapse
Well if you can load into cwm I would factory reset/wipe data, clear cache, clear dalvik cache. Trying flashing CM10. If you can't internally use the SDC version. Boot up CM and go to firmware flasher to change your touch back to stock. If you cannot do this I have various methods of "unbricking" collected from different sources. Its in this thread so Adam Outler Reflash method may be the path you have to take.
I tried the first method but in data/wipe factory reset it tells me : ''E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2'' but then it said ''data wipe complete'', reflashed cm10 and rebooted but it just shutted down the device it didn't rebooted, so im trying next method
djjean19 said:
I tried the first method but in data/wipe factory reset it tells me : ''E:format_volume: make_extf4fs failed on /dev/block/mmcblk1p2'' but then it said ''data wipe complete'', reflashed cm10 and rebooted but it just shutted down the device it didn't rebooted, so im trying next method
Click to expand...
Click to collapse
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
datallboy said:
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
Click to expand...
Click to collapse
mmcblk1 is the external sdcard.
datallboy said:
I may be wrong but mmcblk1p2 is a ext4 partition on the internal storage. Don't know what it does at all though. Continue with the different methods and see what works.
Click to expand...
Click to collapse
I tried most of the methods (except adam outlers method and R3 method given that my biggest sdcard is a 2gb sdcard) they didnt work, however , i mánaged to run cm 10 on a sdcard , but i cant find the firmware flasher to return the touchscreen to stock... I like this of running a OS from a sdcard though and i would use it , but cm10 is too unstable , so i will turn touchscreen back to stock to run cm7 which i think es more stable
Hi there, try this out http://forum.xda-developers.com/showthread.php?t=2179403
The second file will be about 510 mb.
I also formatted some partitions... bad idea. I tried Ray Waldo's method but it didn't work. Perhaps this one will work for you?
djjean19 said:
I tried most of the methods (except adam outlers method and R3 method given that my biggest sdcard is a 2gb sdcard) they didnt work, however , i mánaged to run cm 10 on a sdcard , but i cant find the firmware flasher to return the touchscreen to stock... I like this of running a OS from a sdcard though and i would use it , but cm10 is too unstable , so i will turn touchscreen back to stock to run cm7 which i think es more stable
Click to expand...
Click to collapse
The firmware flasher is one of the apps that comes with CM10.
SomeDoofusLover said:
Hi there, try this out http://forum.xda-developers.com/showthread.php?t=2179403
The second file will be about 510 mb.
I also formatted some partitions... bad idea. I tried Ray Waldo's method but it didn't work. Perhaps this one will work for you?
Click to expand...
Click to collapse
I was about to try this, but accidentally booting into cm i booted into internal boot instead of sdc boot, for my surprise it was loading cm 10 :laugh: , and way more stable than the sd card, so i went to the storage and i got 4 Gb of storage for apps, weird given that my Nook has 16Gb but still happy, it run smoothly, ad i will stick to it, i figure out that maybe my boot partition is damaged so I need the sd boot to go to the internal boot, , I'm making a thread of this , this may help someone else with a dead nook :good:
@datallboy : I figured that out somewhat late, it comes with cm 10 from version 11/14 or so , i was using version 11/08 because i didn't knew there was a new one, now i'm running version 12/31 Internally and it is stable , thanks , i wouldn't figured this out without your help
Flashing CM12.1 on one phone causes baseband & IEMI to become "Unknown"...
Hey,
So, I've flashed 2x Samsung S2 GT-i9100 devices and one worked perfectly but the other has an issue...
I flashed I9100XWMS2_I9100VODLSF_VOD.zip onto each device via Odin [Successful]
I flashed CWM-KitKatCompatible-i9100.tar & I91001GB_6GB.pit which is a 1GB system partition, 6gb data partition and remaining goes to internal storage via pit files.zip simultaneously via Odin [Successful]
I rebooted into recovery (cwm) and flashed Apolo-8.0-CM-Beta9_Regular-TWRP.zip via CWM in order to get access to TWRP. [Successful] - I have tried without this step but the same thing happens.
I rebooted into recovery, mounted internal storage and USB Mounted. I formatted internal SDcard via Windows. [Successful] - I have tried without this step but the same thing happens.
I rebooted into recovery again and flashed cm-12.1-20151006-NIGHTLY-i9100.zip and tk_gapps-modular-micro-5.1.1-20150927.signed.zip [Successful]
I rebooted into the ROM which loaded and as soon as it finished loading one phone showed there was "No SIM" which remained there all though initial setup and setup told me to insert a sim card even though there is a working SIM card inserted in it already, I went into settings and it showed mobile connection disabled, if I go down into About, the basedband and IEMI are both unknown, where as the other phone has a baseband of I9100BULS3, an IEMI and works perfectly. [Partial Success]
If I flash back to stock partition tables and then flash I9100XWMS2_I9100VODLSF_VOD.zip then the baseband returns, IEMI returns and mobile connectivity works perfectly...
How/what am I doing wrong and how do I fix this?
Thanks
Bump, could really do with some help!
Try using stock partitions rather than 1gb for system and 6gb for data. 1gb for system and 4gb for data works well on my phone, so you could try that. I'm pretty sure 1gb for system and 6gb for data was bugged on some roms, that's why it wasnt working for you.
That obviously means that you need to use a smaller gapps.
Regards, gsstudios
gsstudios said:
Try using stock partitions rather than 1gb for system and 6gb for data. 1gb for system and 4gb for data works well on my phone, so you could try that. I'm pretty sure 1gb for system and 6gb for data was bugged on some roms, that's why it wasnt working for you.
That obviously means that you need to use a smaller gapps.
Regards, gsstudios
Click to expand...
Click to collapse
Stock partitions have a system partition too small, that's why the custom PIT is required. Remember I did the exact same proceedure on another GT-i9100 and it worked fine...
Everything works on this one that it's not working correctly on except for the mobile data connection (no phone, data... etc)
Bump
Bump, can't find anything
Just an idea but how about you try to restore the working nandroid backup from one phone to the other phone?
Muthzer the One said:
Just an idea but how about you try to restore the working nandroid backup from one phone to the other phone?
Click to expand...
Click to collapse
How is that able to fix the problem, isn't a nandroid a device specific backup because of the EFS folder?
Also, If I flash stock partitions & rom the mobile connectivity starts working again...