Related
ext3 partition doesnt support on gingerdx......
please give me instruction how to make it support??? please....
cwc partition wont support.................
EXT3 partitions is supported. I'm currently using GingerDX v006 with an 8GB card with 2 partitions (first FAT32, second EXT3).
Partitioned and formatted in Windows environment.
If you are coming from stock rom or other rom you should do full wipe and also re-format the ext3 partition.
Any help? I partition sdcard with fat32(primary) and Ext3 around 470mb(primary) in Windows then install rom and everything alright then install some apps. Then, when i reboot, its stuck on boot logo. I'm using Froyobread23b and I also tried partitioning with CWM (512mb ext), Zero swap, and again everything fine at first Installed apps, I looked at root explorer data/app and it save on sd..then after some time I reboot then stuck on logo again I've done it about 6 times already and i'm tired any help???? Is it not ok with FroyoBread??
moaj said:
Any help? I partition sdcard with fat32(primary) and Ext3 around 470mb(primary) in Windows then install rom and everything alright then install some apps. Then, when i reboot, its stuck on boot logo. I'm using Froyobread23b and I also tried partitioning with CWM (512mb ext), Zero swap, and again everything fine at first Installed apps, I looked at root explorer data/app and it save on sd..then after some time I reboot then stuck on logo again I've done it about 6 times already and i'm tired any help???? Is it not ok with FroyoBread??
Click to expand...
Click to collapse
try with swipe 32
ithunter said:
try with swipe 32
Click to expand...
Click to collapse
what swipe 32?
Use CWM, it worked for me. Backup data on sd card first. And please set swap to 0.
SpyderX said:
Use CWM, it worked for me. Backup data on sd card first. And please set swap to 0.
Click to expand...
Click to collapse
Yes it also works for me. But after some time when i reboot it's stuck on logo again, and i need to reflash the rom
So I decided to upgrade to 4.2 and didnt think to check if i needed a special recovery. but i wiped and flashed as usual. The Rom (Clean Rom 2.5) works perfectly, but stickmount doesnt work with 4.2 so i planned on recovering my backup of 4.1.2
Problem 1: CWM cannot find my backup files, presumably because the file tree change
Problem 2: I wiped and flashed 4.2 a second time, as i could not restore my old one, creating a filesystem as follows...
/storage/emulated/0/0
now, the first /0 is where my current rom saves everything, and /0/0 is where all my old stuff is.
Can anyone advise as to how I can get this back to either 4.1.2 or just back to a regular-ish 4.2? I hear I should be using TWRP
Thank you
wudien said:
So I decided to upgrade to 4.2 and didnt think to check if i needed a special recovery. but i wiped and flashed as usual. The Rom (Clean Rom 2.5) works perfectly, but stickmount doesnt work with 4.2 so i planned on recovering my backup of 4.1.2
Problem 1: CWM cannot find my backup files, presumably because the file tree change
Problem 2: I wiped and flashed 4.2 a second time, as i could not restore my old one, creating a filesystem as follows...
/storage/emulated/0/0
now, the first /0 is where my current rom saves everything, and /0/0 is where all my old stuff is.
Can anyone advise as to how I can get this back to either 4.1.2 or just back to a regular-ish 4.2? I hear I should be using TWRP
Thank you
Click to expand...
Click to collapse
I had the same problem flashing ClearRom 2.5. You can use root explorer to cut and merge your files and folders to the root of the internal sd and see if that works. When I did it and entered CWM it had gone back to the 0 filepath.
Give it a try mate cause I know it has worked for some others on here.
Paul
Just update Stickmount. Today's update allow full read/write access to external storage.
Groid said:
Just update Stickmount. Today's update allow full read/write access to external storage.
Click to expand...
Click to collapse
Awesome. Are you running a custom kernel for write access? I can only read info
i tried flashing M - Kernel but as far as stickmount/otg goes it didnt change anything. how did you get it to write??
Stock, stock kernel, rooted, 4.2, latest Stickmount. Yes, I have read/write access to OTG attached storage formatted as fat32. I have to use Astro to see it though. I created a folder on a thumbdrive and copied something from internal to it. Even Root Explorer doesn't see it until they get out an update. Some of the recently updated apps, like MX Player or Doubletwist do see the attached storage. It is going to take a while for all the devs to get on board with these recent changes.
Hello.
I've had my SGS 4 (I9500) for about 10 days, and have some problems (not critical but anoying), I don't know if they are related.
1) I use a microSD of 64 GB, the same I was using in my previous SGS 3 without any problem. In the SGS 4, sometimes the microSD is reported as damaged (even at boot, or during usage). It has happend several times, and fixed with a reboot. When this happends, the microSD can't be readed by the file explorer (neither ES explorer or Solid Explorer). I have formatted the microSD with the SGS 4, but didn't help.
2) I can't mount, format neither backup on the microSD from Recovery, even using Recovery that claim "backup / restore folders fixed". I need to backup on external SD in order to free the little space available on the internal SD!!
3) I can't find the folder where the backups made from Recovery are! Recovery says the path is sdcard/clockworkmod/backup, but I browse to that path in Solid Explorer, and it only has one file: .recovery_version. (I have activated the option "show hidden files"). I need to find these folders for at least move/copy the backup files to my PC, if I can't store them on the external SD.
At the beginning, I thought it was a generic problem of the SGS 4 that would be fixed with custom kernels or ROMs, but so far nothing has helped!
Any help or ideas would be appreciated.
Thank you.
Javier.
jolivera said:
Hello.
I've had my SGS 4 (I9500) for about 10 days, and have some problems (not critical but anoying), I don't know if they are related.
1) I use a microSD of 64 GB, the same I was using in my previous SGS 3 without any problem. In the SGS 4, sometimes the microSD is reported as damaged (even at boot, or during usage). It has happend several times, and fixed with a reboot. When this happends, the microSD can't be readed by the file explorer (neither ES explorer or Solid Explorer). I have formatted the microSD with the SGS 4, but didn't help.
2) I can't mount, format neither backup on the microSD from Recovery, even using Recovery that claim "backup / restore folders fixed". I need to backup on external SD in order to free the little space available on the internal SD!!
3) I can't find the folder where the backups made from Recovery are! Recovery says the path is sdcard/clockworkmod/backup, but I browse to that path in Solid Explorer, and it only has one file: .recovery_version. (I have activated the option "show hidden files"). I need to find these folders for at least move/copy the backup files to my PC, if I can't store them on the external SD.
At the beginning, I thought it was a generic problem of the SGS 4 that would be fixed with custom kernels or ROMs, but so far nothing has helped!
Any help or ideas would be appreciated.
Thank you.
Javier.
Click to expand...
Click to collapse
look in data/media/clockworkmod
samersh72 said:
look in data/media/clockworkmod
Click to expand...
Click to collapse
Excelent!!! :victory:
And I even found a efs_Backup, that I was wondering how to do!!
Thank you very much! :highfive:
(Now I just need to solve the problems with the external SD) :fingers-crossed:
Greetings,
Javier.
jolivera said:
Excelent!!! :victory:
And I even found a efs_Backup, that I was wondering how to do!!
Thank you very much! :highfive:
(Now I just need to solve the problems with the external SD) :fingers-crossed:
Greetings,
Javier.
Click to expand...
Click to collapse
use dd command to backup efs and you must also backup m9kefs partitions
samersh72 said:
use dd command to backup efs and you must also backup m9kefs partitions
Click to expand...
Click to collapse
aham... sorry, I don't know how to use "dd command". :silly:
Do you mean the efs_Backup folder isn't a full backup of the efs?
Sorry for my ignorance, and thanks again.
jolivera said:
aham... sorry, I don't know how to use "dd command". :silly:
Do you mean the efs_Backup folder isn't a full backup of the efs?
Sorry for my ignorance, and thanks again.
Click to expand...
Click to collapse
i think you backuped efs partition with recovery, that is fine.
NV_DATA must be secured also, they are included in other partition, they are not included in efs partition so make a backup for them see this.
Hello guys.
Can anybody help me with the external SD issues? :fingers-crossed:
Thanks in advance.
Solution to Recovery access to external SD
As I thought, the issue with the Recovery access to external SD was solved with a new version of Recovery. The Cofface Recovery V 2.0 made the magic! :victory:
I thought this would solve the issues with the esternal SD in general, but I keep having the error "SD is damaged", and when I try to mount it, it is detected as empty. I let the phone alone, and some minutes later the SD card is detected and mounted itself. :silly:
I hope this to be a release problem, and be eventually solved with new versions of kernels or ROMs. :fingers-crossed:
help
samersh72 said:
look in data/media/clockworkmod
Click to expand...
Click to collapse
Am sorry for hijacking your thread OP, but am having the same problem as you had cant seem to find that backup folder, I want to transfer it to my pc to save some memory, when I saw this reply "data/media/clockworkmod" I was so happy but when I went no luck whatsoever I get "data/com.mdc.ustv (that's it) and I can find "media/audio/notification" .
whenever I do go to restore in recovery mode it does show directory sdcard/clockworkmod/backup
any help would be greatly appreciated
DsmEvo said:
Am sorry for hijacking your thread OP, but am having the same problem as you had cant seem to find that backup folder, I want to transfer it to my pc to save some memory, when I saw this reply "data/media/clockworkmod" I was so happy but when I went no luck whatsoever I get "data/com.mdc.ustv (that's it) and I can find "media/audio/notification" .
whenever I do go to restore in recovery mode it does show directory sdcard/clockworkmod/backup
any help would be greatly appreciated
Click to expand...
Click to collapse
I found the clockworkmod backup in the described path. Are you reaching the memory root?
The sound/norifications folder is in system/media path.
Good luck.
jolivera said:
I found the clockworkmod backup in the described path. Are you reaching the memory root?
The sound/norifications folder is in system/media path.
Good luck.
Click to expand...
Click to collapse
thanks! got it.. I was searching in internal sdmemory via pc got it now!
correct path for deleting cwm backup files
... thanks, with your help I was finally able to delete my unneeded image.zip backup file that was not recognized by the recovery / mod manager clean up tool. Some other posts suggested to reach it under /mnt/shell/emulated/clockworkmod/backup which is basically correct for accessing it, but even with root permission you are never allowed to delete it there (symlinks?). However, /data/media/clockworkmod was finally the correct path to physically remove it :victory:
Okay, I don't know how many people are facing this issue but here it goes.
I've just restored back my Nandroid backup rom which is root stock 4.4.2 TW Poland from CM11. Everything is as it should be except for one thing, my INTERNAL storage suddenly become READ ONLY, not REWRITABLE.
To me this is weird as most people I've search on this board has external SD issues, but my external SD are working fine. I can transfer apps and even do Titanium Backup on it no problem.
Can someone enlighten me what seems to be the problem? What has CM11 done to the internal storage permission?
syazwanimator said:
Okay, I don't know how many people are facing this issue but here it goes.
I've just restored back my Nandroid backup rom which is root stock 4.4.2 TW Poland from CM11. Everything is as it should be except for one thing, my INTERNAL storage suddenly become READ ONLY, not REWRITABLE.
To me this is weird as most people I've search on this board has external SD issues, but my external SD are working fine. I can transfer apps and even do Titanium Backup on it no problem.
Can someone enlighten me what seems to be the problem? What has CM11 done to the internal storage permission?
Click to expand...
Click to collapse
I have exactly the same issue now.
Hoping there is a fix
Same issue, had to flashed stock firmware again to fix it.
I noticed in es file explorer, internal sd is mounted as "legacy" after restoring while it was mounted as "0" in stock tw before CM11.
stonedead said:
Same issue, had to flashed stock firmware again to fix it.
I noticed in es file explorer, internal sd is mounted as "legacy" after restoring while it was mounted as "0" in stock tw before CM11.
Click to expand...
Click to collapse
Did you flash via Odin or via CWM?
Mobile odin..
stonedead said:
Same issue, had to flashed stock firmware again to fix it.
I noticed in es file explorer, internal sd is mounted as "legacy" after restoring while it was mounted as "0" in stock tw before CM11.
Click to expand...
Click to collapse
stonedead said:
Mobile odin..
Click to expand...
Click to collapse
Perhaps that's the way to go - sorry for 20 questions - did you flash a pre-rooted version or just plain stock via mobile odin?
Hammer_drum said:
Perhaps that's the way to go - sorry for 20 questions - did you flash a pre-rooted version or just plain stock via mobile odin?
Click to expand...
Click to collapse
Plain stock. I just tick the everoot and reset data and cache...don't mind re-install everything as I don't have many apps and games.
You can try flash it without clearing data and cache, that might work..
stonedead said:
Plain stock. I just tick the everoot and reset data and cache...don't mind re-install everything as I don't have many apps and games.
You can try flash it without clearing data and cache, that might work..
Click to expand...
Click to collapse
I seem to have been able to get it working again.
I went into CWM - wiped Storage, Data, then the usual full data reset etc and flashed a rom.
Permissions are ok now.
Last time I install CM11...
Marshmallow had a new cool feature of adopted storage but all the flashoholics had trouble in changing roms because they have to format sd card every time they change roms .
I have a solution.
1:- while flashing rom wipe system dalvik cache and cache but dont wipe data .
2:- flash the rom and let it optimize apps .
3:- after optimizations most probably you will be in bootloop , simply boot into recovery and wipe data and reboot.
4:- your phone will optimize apps again and this time it will boot up and you can access sd card as adopted storage without need to format it again as internal.
This trick worked for me and should work for you guys too.
There's another method that is :-
1:- navigate to root folder
2:- copy all the files from data/misc/vold to somewhere in SD card
3:now boot to recovery wipe everything except SD card and flash new ROM .
4:- now using twrp's file manager move the files you from step 2 to the same folder I.e. data/misc/vold
5:-reboot
According to twrp dev, you can use this trick ' Note, if you factory reset and leave the key present in /data/misc/vold, then Android will still detect and use the adopted storage on the next boot.'
https://gerrit.omnirom.org/#/c/15921/
Thanks! Worked for me! :fingers-crossed:
PoseidonKing said:
Thanks! Worked for me! :fingers-crossed:
Click to expand...
Click to collapse
Dirty Flashing....and adopted sd card
If I dirty flash a rom by just clearing the cache and dalvik cache, will the old adopted sd card setting work or will I have to follow your procedure even then also?
[email protected] said:
If I dirty flash a rom by just clearing the cache and dalvik cache, will the old adopted sd card setting work or will I have to follow your procedure even then also?
Click to expand...
Click to collapse
It'll work, according to the trick mentioned here
[email protected] said:
If I dirty flash a rom by just clearing the cache and dalvik cache, will the old adopted sd card setting work or will I have to follow your procedure even then also?
Click to expand...
Click to collapse
Yup but most probably you will get boot loop if you have installed significant number of apps....so clean flash is advised......and use the trick mentioned
Sent from my Moto E using Tapatalk
Abhimanyu Shekhawat 121 said:
Yup but most probably you will get boot loop if you have installed significant number of apps....so clean flash is advised......and use the trick mentioned
Sent from my Moto E using Tapatalk
Click to expand...
Click to collapse
can you explain? why this bootloop?
pls do read my post here http://forum.xda-developers.com/showpost.php?p=66353859&postcount=1784
does this sound familiar?
i had 39 apps installed so you can say i have lots of apps
but this never happened to me before i flashed 13th april nightly...
ultimately i had to wipe everything, do a clean flash and use this method to save the sdcard
booo159159 said:
can you explain? why this bootloop?
pls do read my post here http://forum.xda-developers.com/showpost.php?p=66353859&postcount=1784
does this sound familiar?
i had 39 apps installed so you can say i have lots of apps
but this never happened to me before i flashed 13th april nightly...
ultimately i had to wipe everything, do a clean flash and use this method to save the sdcard
Click to expand...
Click to collapse
I don't know the exact reason but as long as you have only 10-15 apps you won't get bootloop .....I always get bootloop while dirty flashing updates
Sent from my Moto E using Tapatalk
will this also work on other phones? i have an i9505
k2828 said:
will this also work on other phones? i have an i9505
Click to expand...
Click to collapse
It will
Sent from my Moto E using Tapatalk
booo159159 said:
can you explain? why this bootloop?
pls do read my post here http://forum.xda-developers.com/showpost.php?p=66353859&postcount=1784
does this sound familiar?
i had 39 apps installed so you can say i have lots of apps
but this never happened to me before i flashed 13th april nightly...
ultimately i had to wipe everything, do a clean flash and use this method to save the sdcard
Click to expand...
Click to collapse
Use latest RR.......RR not giving booloops on dirty flash
Sent from my Moto E using Tapatalk
Sorry for bringing up this old thread again, but I've an issue where I had to hard reset in order to get root on my Moto X Pure. I didn't think about whether or not I should make any backups of my sd or nand.
I thought I could just continue using the sd as adopted storage on my new ROM.
Anyways, when doing this trick do I leave the sd card inside?
ZoneBlaze said:
Sorry for bringing up this old thread again, but I've an issue where I had to hard reset in order to get root on my Moto X Pure. I didn't think about whether or not I should make any backups of my sd or nand.
I thought I could just continue using the sd as adopted storage on my new ROM.
Anyways, when doing this trick do I leave the sd card inside?
Click to expand...
Click to collapse
Yes SD card should be inside.
Sent from my Moto E using Tapatalk
well it works. you can also switch from cm13 to cm14.1, but the option migrate data, to migrate from internal to adopted is missing afterwards
please help , i can see the .key file in the vold folder but i don't know how to save it so that i can RE USE the adoptable storage AFTER FACTORY RESETTING my Phone.
PLEASE PLEASE help me out !
yaxir0 said:
please help , i can see the .key file in the vold folder but i don't know how to save it so that i can RE USE the adoptable storage AFTER FACTORY RESETTING my Phone.
PLEASE PLEASE help me out !
Click to expand...
Click to collapse
Just copy it to your SD card using file manager. Then when you flash ROM, go into twrp file manager and copy-paste it back to vold folder.
However, if you are on a nougat ROM then you don't need this entire trick at all! Just flash ROM without this trick. The .key will take care of itself automatically without any problem.
Vikrant Desai said:
Just copy it to your SD card using file manager. Then when you flash ROM, go into twrp file manager and copy-paste it back to vold folder.
However, if you are on a nougat ROM then you don't need this entire trick at all! Just flash ROM without this trick. The .key will take care of itself automatically without any problem.
Click to expand...
Click to collapse
thanks for you reply , Vikrant
my problem is , my SD card does NOT appear in TWRP fiile manager , since it was formatted as internal. my phone's stuck in boot animation. so i have no access to the phone's OS to retrieve my VERY precious data.
please help me out ... i would explain the issue in detail but i have already made a post here ;
https://www.reddit.com/r/linuxquestions/comments/62m1p6/decrypting_a_sd_card_on_ubuntu/
kindly take a look and suggest possible solutions.
Many thanks !
yaxir0 said:
thanks for you reply , Vikrant
my problem is , my SD card does NOT appear in TWRP fiile manager , since it was formatted as internal. my phone's stuck in boot animation. so i have no access to the phone's OS to retrieve my VERY precious data.
please help me out ... i would explain the issue in detail but i have already made a post here ;
https://www.reddit.com/r/linuxquestions/comments/62m1p6/decrypting_a_sd_card_on_ubuntu/
kindly take a look and suggest possible solutions.
Many thanks !
Click to expand...
Click to collapse
Well, in TWRP file manager, don't you see the option 'sdcard' ? Go to TWRP > Advanced > file manager > sdcard.
I'm also using SD as internal and flashing ROMs and stuff without using this trick (on nougat).
Vikrant Desai said:
Well, in TWRP file manager, don't you see the option 'sdcard' ? Go to TWRP > Advanced > file manager > sdcard.
I'm also using SD as internal and flashing ROMs and stuff without using this trick (on nougat).
Click to expand...
Click to collapse
i see. you're using Android 7.0 (Android N) ... i was using CM13 , Android 6.0 (Android MarshMellow) oh and infact , i downloaded the ROM from xda forums ...
here's the EXACT ROM that was running on my phone before disaster struck ;
https://forum.xda-developers.com/galaxy-mega/development/rom-aicp-11-0-mm-6-0-1-t3457130
i DID use the TWRP File Manager but i don't remember exploring that particular 'sdcard' folder . but do tell me , what did you see in your 'sdcard' folder in file manager ?