So yesterday, I flashed a custom ROM which is MERE [Most Epic Rom Ever] in my O+8.92 Android phone
Info:
Android 4.2.2 JB
Kernel 3.4.5
MediaTek MT6582
There were no problems at all until I noticed that I cannot move any single app into SD Card [Sandisk 8GB] either Movable or Not Movable it only says "Couldn't move app" I tried apps like Link2SD and etc. But it says [ERROR-FAILED-INSTALL-CONTAINER] (iirc)
Although the Entire content of my SD Card are still present after I flashed MERE ROM every apps that I installed go directly to Phone Storage (before) and now its labeled as SDCard0 while my external SD is called SDCard1.
Also the files associated with each apps goes/read/or create to the PhoneStorage[SDCard0] even my SDCard[SDCard1] has the files already.
Info about the ROM
Build #: MFS140802
I really need help with this I've been searching for whole day and nothing worked upon the methods I came across with.
Thankyou in advance.
Up
Related
Hi,
i've recently got a new Xperia Ray. I have unlocked the bootloader and flashed a kerner and rooted it. But when i download apps from Google Play i recieve an error "“Could Not Install On USB Storage Or SD Card". (this happens mostly with purchased apps. Free apps get installed ).
I tried to unmount the sd card and install the app to the phone. It worked. BUT when i try to move the app to sd card i receive an error "Couldn't move app". Tried this with App2sd and the phone app manager but it doesn't work. Tried with Link2SD (gave it poweruser access) but it give me an error : " Failure, Segmentation Fault".
I tried a couple of solutions i found on google like deleting a file called smdl2tmp1.asec from android_secure folder, but this file doesn't exist.
Help me fix it please, what can i do ?
Info:
Sony Xperia Ray
Model Number: ST18i
Android Version: 4.0.3
Baseband Version: 8x55A-AAABQOAZM-203028G-70
Kernel Version: 2.6.21.9 -perf, [email protected]#1
Build Number: 4.1.A.0.562
Thanks in advance.
i know it sounds simple mate but have you tried a new SD card? I swapped out the original card that came with the ray and chucked in some old 8gb sdhc card i had laying around... it went belly up after about 6 months (when i started flashing roms it seems). It could just be damaged.
Failing that, if it's not the original card, is there any chance it could be incompatible? (total stab in the dark, not sure if phones have manufacturer incompatibility issues with sd cards like pc motherboards / ram makers do)
Hi
developers
i have a clone S5 its a mediatek device have android 4.4.2 its not showing SD card in manage apps and don't move apps to SD only install to internal memory which is very low so i tried all the method available on XDA and via Google including modifying platform.XML also sdfix kitkat as well don't install it says older SDK but nothing seems to work if anyone can help me i will really appreciate that
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
Hi everyone,
I'm getting a very annoying issue on my Wiko Cink Five (clone of the MMX A116) when I'm flashing a new ROM : the memories are swapped directly after flashing any ROM without having the swap memory file applied. I was running 4.4.4 [CM11][PORT][UNOFFICIAL] CyanogenMod 11 For Canvas HD V0.1 - NxtGen when I decided to go back to a stable OS (for HW decoding/video recording issues) so I flashed this one : [ KitKat 4.4.2 ] ROM for Micromax A116 [UNOFFICIAL]
In the first ROM (CM11) there was the swap applied by default in the package of the ROM and I knew the swap was actually in. In the oldest versions of the CM11 ROM (before the "nextgen v 0.1) the swapp wasn't included and i swapped the memories with the memory swap for CM11. When I flashed the new stable ROM in 4.4.2 (without swap in it) after total reset ("clean to install a new ROM" option in Philz recovery), I found that the internal memory was recognized as the SD card and inversement. I was using Solid Explorer and it showed me my sdcard content instead of the internal memory content at /storage/sdcard0, which is not normal because no swap was applied. I pulled back the SD card and rebooted the phone and in settings/storage there was for only choice of storage the SD card. The internal memory wasn't mentioned anywhere. I was too unable to copy or move file from one memory to another but I was able to copy or move files on one memory. That issue made me unable to restore backups from Titanium Backup that was telling me all the time "unknown package" when trying to install apps (installing them directly from the TB saves .gz files in the SD card did work but not the data restore).
What I tried to solve the issue :
- apply the memory swap restore for CM11 on the not CM11 ROM (which was a bad idea but I tried...) ---> stuck on boot logo !
- install another ROM (the White1 4.2.1) after clean reset ---> memory still swapped !
- reflash the CM11 ROM and apply the swap restore ---> bootloop !
Then I was out of ideas...
I do not have any problems with the recovery, it shows me my SDcard when I want to backup or restore from my SDcard in /storage/sdcard1 and shows me too my internal memory at /storage/sdcard0 so no problems in recovery, the issue only comes when using a ROM...
About the kernels, i never flashed any kernel in addition of a ROM package except for the not CM11 ROM, the 4.4.2 one which was the New Hyper Kernel (link in the thread of the ROM).
I restored the CM11 ROM from a backup because this is the best working one as I don't have any of the writing issues caused by the memory swapped as she is working well with it but I'm still unable to use another ROM and so record videos, have Bluetooth and WiFi turned on together or watch HD videos...
So this is it !
I don't have much more informations to give and hope that is enough clear to understand. I'm French for those who speak French so don't expect an very good English quality, being sorry for that too.
Best regards, Hast0n.
Hi everyone,
I'm getting a very annoying issue on my Wiko Cink Five (clone of the MMX A116) when I'm flashing a new ROM : the memories are swapped directly after flashing any ROM without having the swap memory file applied. I was running 4.4.4 [CM11][PORT][UNOFFICIAL] CyanogenMod 11 For Canvas HD V0.1 - NxtGen when I decided to go back to a stable OS (for HW decoding/video recording issues) so I flashed this one : [ KitKat 4.4.2 ] ROM for Micromax A116 [UNOFFICIAL]
In the first ROM (CM11) there was the swap applied by default in the package of the ROM and I knew the swap was actually in. In the oldest versions of the CM11 ROM (before the "nextgen v 0.1) the swapp wasn't included and i swapped the memories with the memory swap for CM11. When I flashed the new stable ROM in 4.4.2 (without swap in it) after total reset ("clean to install a new ROM" option in Philz recovery), I found that the internal memory was recognized as the SD card and inversement. I was using Solid Explorer and it showed me my sdcard content instead of the internal memory content at /storage/sdcard0, which is not normal because no swap was applied. I pulled back the SD card and rebooted the phone and in settings/storage there was for only choice of storage the SD card. The internal memory wasn't mentioned anywhere. I was too unable to copy or move file from one memory to another but I was able to copy or move files on one memory. That issue made me unable to restore backups from Titanium Backup that was telling me all the time "unknown package" when trying to install apps (installing them directly from the TB saves .gz files in the SD card did work but not the data restore).
What I tried to solve the issue :
- apply the memory swap restore for CM11 on the not CM11 ROM (which was a bad idea but I tried...) ---> stuck on boot logo !
- install another ROM (the White1 4.2.1) after clean reset ---> memory still swapped !
- reflash the CM11 ROM and apply the swap restore ---> bootloop !
Then I was out of ideas...
I do not have any problems with the recovery, it shows me my SDcard when I want to backup or restore from my SDcard in /storage/sdcard1 and shows me too my internal memory at /storage/sdcard0 so no problems in recovery, the issue only comes when using a ROM...
About the kernels, i never flashed any kernel in addition of a ROM package except for the not CM11 ROM, the 4.4.2 one which was the New Hyper Kernel (link in the thread of the ROM).
I restored the CM11 ROM from a backup because this is the best working one as I don't have any of the writing issues caused by the memory swapped as she is working well with it but I'm still unable to use another ROM and so record videos, have Bluetooth and WiFi turned on together or watch HD videos...
So this is it !
I don't have much more informations to give and hope that is enough clear to understand. I'm French for those who speak French so don't expect an very good English quality, being sorry for that too.
Best regards, Hast0n.