hello,
I have a samsung galaxy tab a.
this is a nice device but only has 8 gb of internal memory. it runs android 5.1
I'm trying to switch the internal and external sd memory. (to get more internal memory)
first of all the device needed to be rooted. I have done this, without any problem..
then I started searching how to switch the memory. I have tried different apps for this but they where not working.
after this I tried to swap the memory manually. I read somewhere this can be done in the vold.fstab file.
I didn't found this file.
after reading more about the topic I found out that the mounting for android 5.1 is done in the boot.img file.
I looked for how to unpack this file, and I'm doing this now with cygwin and android kitchen 0.224
I can unpack the boot.img but have a few questions.
1) the mounting should be done in fstab.<devicename>...... the device name is Galaxy Tab A (2016) but I can not find fstab.galaxy Tab A (2016), but fstab.goldfish and fstab.sc8830 is it possible the mounting is done in one of thes files ? (they are found in the root of the boot.img
2) what should I change in these files?
3) afther I have changed the mounting, how can I with android kitchen repack the boot.img
thank for any help
best regards,
Bart
Related
I just installed Beanstalk 4.4 ROM on my Samsung Galaxy S3 i747m. Everything is working fine and I am almost done but I just noticed one peculiar problem which i can't seem to correct.
When i boot into recovery (CWM), the files that i see in SD card is whole different set of files that i see in ES Explorer on phone or on my computer. I tried reinstalling the ROM to no avail. I know the files are there because i used the same files to reinstall ROM and Gapps.
Now, any file i copy to SDcard through computer or download doesn't show in recovery. In system storage, it says I am using 4GB of storage while only showing about 122MB of files. I am only using internal storage and no SD card.
Any help will be really appreciated and let me know if you need more info.
dont know if this is the right place to post my question but since im a noob the forum doesn't let me post anywhere else and this is the first time ive posted here because i usually find what im after in this forum so thanks for that !
ive read alot about the Read Write issues being experienced with Google's Android unwilling to let you use your external SD card for storage of Apps and writing to it , ive followed some tutorials about the net and even tried jamisons pre-rooted Rom for SM-T120 and everytime i get nowhere with it all .. my tab3 is now rooted but i cant write to the card .. is this going to be possible or does anyone know something i haven't tried ...
so i will tell you what ive tried for now
editing permissions.xml
loading the pre-rooted firmware
changing permissions to vold.fstab file
is there something out there !
thanks for any suggestions and help .. much appreciated Paul :good:
im running 4.1.2 Android Version and its Rooted - Build JZ054K.T210XXAMG2
I think that is not enough. I did the same ... in my research I came across the void.fstab in some devices is possible in the galaxy 3 do not know what the correct code.
I found universal files vold.fstab, but without success
riverskin said:
I think that is not enough. I did the same ... in my research I came across the void.fstab in some devices is possible in the galaxy 3 do not know what the correct code.
I found universal files vold.fstab, but without success
Click to expand...
Click to collapse
I may have just found a solution , the root method is fine by jamison ... then once that has been flashed and the tablet has restarted , go into oden again and flash the CWM recovery the same way as you do for the pre rooted firmware .. then follow these instructions i found posted by stefan !
Ok, I fixed the issue:
- Mounted USB storage (external SD) in CWM
- Backed up all files from my external SD (except a strange folder named µATA, which could not be read at all)
- Formatted the external SD under Windows
- Copied back my files to the external SD
- Restarted Android
Now the external SD is mounted r/w. Also in Root Explorer I can see that the external SD is r/w and not r/o as before.
hope this works for you as i think its working for me as ive just been able to delete a folder from widows via the USB cable .. where i didnt have access before
formula1245 said:
I may have just found a solution , the root method is fine by jamison ... then once that has been flashed and the tablet has restarted , go into oden again and flash the CWM recovery the same way as you do for the pre rooted firmware .. then follow these instructions i found posted by stefan !
Ok, I fixed the issue:
- Mounted USB storage (external SD) in CWM
- Backed up all files from my external SD (except a strange folder named µATA, which could not be read at all)
- Formatted the external SD under Windows
- Copied back my files to the external SD
- Restarted Android
Now the external SD is mounted r/w. Also in Root Explorer I can see that the external SD is r/w and not r/o as before.
hope this works for you as i think its working for me as ive just been able to delete a folder from widows via the USB cable .. where i didnt have access before
Click to expand...
Click to collapse
The device recognizes the sd as storage for apps?
I always had access to my sd on windows with USB cable, except in recovery, i use the TWRP, in recovery i can't mount SD with USB cable, but i think is an issue of TWRP or CWM.
My problem is to enable the move app to sd or recognize it has internal memory. I know that in SGS3 is possible to recognize sd card as internal memory changing the script in vold.fstb, in tab 3 it should not be so different.
PS: is a shame... i can't post links yet :angel:.
riverskin said:
The device recognizes the sd as storage for apps?
I always had access to my sd on windows with USB cable, except in recovery, i use the TWRP, in recovery i can't mount SD with USB cable, but i think is an issue of TWRP or CWM.
My problem is to enable the move app to sd or recognize it has internal memory. I know that in SGS3 is possible to recognize sd card as internal memory changing the script in vold.fstb, in tab 3 it should not be so different.
PS: is a shame... i can't post links yet :angel:.
Click to expand...
Click to collapse
yes i could see the SD external card in windows but i could not write to it in windows or delete any folders or files in windows .. but with the method used posted above i can write to the Ex sdcard and delete with no write access problems at all ... i updated to the latest firmware tonight to see if it was still working but it didnt and became like it was before ... so i tried to just flash the recovery file back on it again only and now i have access to the SDcard again and its again rooted ! ... no changes to any file
how did you root yOur device? can u give me a link please... am using tab 3 Sm T210 and ver 4.1.2
Ever wanted to try an Android ROM on your RK3188 device but don't want to flash it and risk bricking your device? Or maybe you've currently installed Linux and want to try Android? I've created a tool to create a bootable SD card that can run Android directly from the SD card.
You will need a PC running Linux and an SD card of 8 GB or more, at least class 10 speed, and your Android ROM(s). In this example I've downloaded Radxa Rock's Kitkat ROM 'radxa_rock_android_kitkat_140909_update.img' from 'http://radxa.com/Rock/prebuilt_images'.
Download the tool from 'https://drive.google.com/file/d/0B99O3A0dDe67b3dBUjFzcUoyLWs'. After unzipping you will see a shell script called 'create-android-sdcard' and a directory called 'Tools'.
First load your SD card into the PC and use a command like 'blkid' or 'lsblk' to identify its device name (e.g. /dev/sdc).
Now run the program and pass the name and location of the Android ROM you want to install onto the SD card, e.g.:
./create-android-sdcard radxa_rock_android_kitkat_140909_update.img
The program will prompt you to confirm the name of the device for the SD card. Once confirmed it will then unpack the Android ROM, create partitions on the SD card that mimic the ROM including a 'user' partition that will use the remaining space of the SD card. It will then install the Android ROM to the SD card and notify you when complete.
Finally just take the SD card and insert into your RK3188 device and power on to enjoy Android.
The initial boot is very slow so be patient. For some ROMs this actually seems like a very long time, so be extra patient! Subsequent boots however are faster.
Everything should work 'out of the box' for Kitkat ROMs. For 4.2.2 ROMs as internal storage is implemented slightly differently, I did find one specific ROM where 'Explorer' didn't recognise the internal storage but 'ES File Explorer' did. All other 4.2.2 ROMs worked fine.
In theory it should work with any Android ROM packed as an image. My program uses standard RK tools which are included in the 'Tools' directory. I've included checks to ensure the ROM's format follows the traditional build layout so if the ROM, and in particular, the 'parameter' file is substantially different then YMMV.
Enjoy!
I'm going to try this on my Timing Power RK3188 Mini PC later today. Thanks!
Any idea why it's telling me cannot create kernel image?
Type password to decrypt storage.
I downloaded the rom as from ricomagic
FW_141208:S/N from 201307**** till now
First I installed the rom in Nand and then created the sd card as described( with the same rom). After few seconds after booting , android shows the message :Type password to decrypt storage.
Passwords like p, root ... does not work. Any hint or direction to search for?
Thank you for all well done work.
Edit:
I got a better aproach at (Linuxium) - 21 de jun de 2014
First form official rikomagic web site i installed the latest stock firmware
MK802IV_AP6210_141208. (kitkat)
Then I downloaded make-rkm-mk802iv.7z and create a linux sd-card
Thank you for your great work!
Murilo
can i do it with a usb instead of sd card because my android box do not have a sdcard port
thank you
can i try on any box or its only specific box?
Linuxium said:
Ever wanted to try an Android ROM on your RK3188 device but don't want to flash it and risk bricking your device? Or maybe you've currently installed Linux and want to try Android? I've created a tool to create a bootable SD card that can run Android directly from the SD card.
You will need a PC running Linux and an SD card of 8 GB or more, at least class 10 speed, and your Android ROM(s). In this example I've downloaded Radxa Rock's Kitkat ROM 'radxa_rock_android_kitkat_140909_update.img' from 'http://radxa.com/Rock/prebuilt_images'.
Download the tool from 'https://drive.google.com/file/d/0B99O3A0dDe67b3dBUjFzcUoyLWs'. After unzipping you will see a shell script called 'create-android-sdcard' and a directory called 'Tools'.
First load your SD card into the PC and use a command like 'blkid' or 'lsblk' to identify its device name (e.g. /dev/sdc).
Now run the program and pass the name and location of the Android ROM you want to install onto the SD card, e.g.:
./create-android-sdcard radxa_rock_android_kitkat_140909_update.img
The program will prompt you to confirm the name of the device for the SD card. Once confirmed it will then unpack the Android ROM, create partitions on the SD card that mimic the ROM including a 'user' partition that will use the remaining space of the SD card. It will then install the Android ROM to the SD card and notify you when complete.
Finally just take the SD card and insert into your RK3188 device and power on to enjoy Android.
The initial boot is very slow so be patient. For some ROMs this actually seems like a very long time, so be extra patient! Subsequent boots however are faster.
Everything should work 'out of the box' for Kitkat ROMs. For 4.2.2 ROMs as internal storage is implemented slightly differently, I did find one specific ROM where 'Explorer' didn't recognise the internal storage but 'ES File Explorer' did. All other 4.2.2 ROMs worked fine.
In theory it should work with any Android ROM packed as an image. My program uses standard RK tools which are included in the 'Tools' directory. I've included checks to ensure the ROM's format follows the traditional build layout so if the ROM, and in particular, the 'parameter' file is substantially different then YMMV.
Enjoy!
Click to expand...
Click to collapse
download??? link please
For starters, my phone is the Samsung Galaxy on5, model G550T.
I have followed as many guides as I can find through Google. I've rooted my phone (which is a prerequisite for using the app Link2SD). I can successfully partition the SD card (32gb, partitioned 16 for internal and 16 for portable storage as FAT32). However, when I try to use Link2SD, I get this error:
Mount script error
Mount script cannot be created.
mount: No such file or directory
I'm no tech wiz, but I've researched as many solutions as I could, all of which suggest maybe partitioning it as ext2, 3, or 4 rather than FAT32. However no matter which one I do, I still get the same error.
I think the closest lead I have to figuring out the problem is that in one of the solutions I attempted, they mentioned a init.d folder in their system fills. Upon following the same path, I saw that I do not have such files. Is that the reason maybe? And if so, what can I do to fix it? This phone has atrocious memory (4.12gb! About 1.5gb being taken up by other apps already!) and does not support adoptive memory, which is why I am trying so hard to get this to work.
If anymore details are needed, I will comply happily! Thanks in advance for your help.
Some specifications:
Phone: Samsung Galaxy on5, G550T
Stock ROM, rooted
Running Marshmallow (android 6.0.1)
If they type of SD card is relevant, I'm using a UHS-1 SD card.
Hi guys! I have a problem with my Samsung Galaxy J2 Prime (SM-G532M). It had 16GB of internal memory, until it flashed with an internet firmware. After that it is only recognizing 8GB of internal memory. After a lot, a lot, but a lot of research, I did not find a firmware that made available the 16GB and not a PIT file. I studied a bit about PIT files, but nothing that enabled me to edit the various partitions, with their "strange" values. I even tried to use the Samsung Galaxy J2 Prime TV PIT file (SM-G532MT) believing it to be 16GB (but I used the SM-G532M's PDA). But compared them I realized they were the same! Please help me! Having more 8GB of internal memory and not being able to use it is lousy!
I have the same problem, I noticed that using the app file explore it only finds 2gb only, this is very strange. I also downloaded several firmware and can not change
Having the same problem here, and it's making me insane! Can someone help? After flashing the stock rom the phone tells me i have only 8gb internal storage instead of my actual 16gb.
I solve it; although I'm not sure how.
Mr. Mascarenhas said:
Hi guys! I have a problem with my Samsung Galaxy J2 Prime (SM-G532M). It had 16GB of internal memory, until it flashed with an internet firmware. After that it is only recognizing 8GB of internal memory. After a lot, a lot, but a lot of research, I did not find a firmware that made available the 16GB and not a PIT file. I studied a bit about PIT files, but nothing that enabled me to edit the various partitions, with their "strange" values. I even tried to use the Samsung Galaxy J2 Prime TV PIT file (SM-G532MT) believing it to be 16GB (but I used the SM-G532M's PDA). But compared them I realized they were the same! Please help me! Having more 8GB of internal memory and not being able to use it is lousy!
Click to expand...
Click to collapse
I made multiple attempts, until I could find the "recovery mode", there I did all the "wipes" and then I gave "mount storage". Then, after the restart I already recognized the storage of 16 Gb.
Here are my hypotheses: 1) The ROM was not completely installed. Well, until he finally entered the recovery; did not finish working the "android". 2) Simply, complete cleaning is necessary after installation of the ROM STOCK. 3) I did not recognize the storage because the extra storage was not "mounted" for which the ROM was not prepared that we invented (it may be prepared for the 8 GB version). 4) I forgot the fourth hypothesis. Excuse me. Greetings, I hope you find it useful. That was the only reason to answer here.