I'm still having a problem flashing this I have same error that you did before and i did all the reboot into recovery and wiping multiple times and instill get a failure same one u did
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
I'm still having a problem flashing this I have same error that you did before and i did all the reboot into recovery and wiping multiple times and instill get a failure same one u did
roadkill42
Android Expert
u using twrp
roadkill42
Android Expert
try one of the other ROMs then do a factory reset then try to flash this one again that's what I did
Got slim flashed with the help of this post thank you bro
Everything smooth for me! I was certain the 4.4 rom hadnt installed because it was so fast ! Sure enough it was good to go and all is smooth. Flashed GAPPS as well. Im a little confused on how to make a recovery image though. Backup just gives me basic backup stuff like data/cache and a few others. I also dont have access to my titanium back-ups either. No biggies.
DsyMnapTic
Android Expert
When you make a backup all you essentially need anyhow is system, data and a boot image.
Flash twrp which i believe you would of needed to install this in the first place. There is a separate thread for twrp located here. Just flash through which ever recovery you are currently using. I wrote a post up above this that tells you how to enable the advance reboot menu. As far as titanium flash the latest supersu binary from here. I personally have been using nandroid manager more then titanium backup lately. The best ultimately though if you flash a lot is to make your own update.zip with all your backed up apps and data.
I have not been able to make my own update.zip lately because i run out of space on internal storage so the zip becomes corrupted / broken. I might head over to xda for another option for that. I have noticed there is a lot of system rom space left over with these 4.4.4 builds and unfortunately there are some tha don't have native support to move to sd and google has made a lot of changes them self that as far as i can see prevents a lot of apps from seeing the sd data like it was in older versions of the os. Because of this i integrate as much of the updates as i can back into the rom which is very few since i don't use the gapps listed in the 4.4.4 threads but this one here. I just basicly add google voice, maps, and gmail afterwards. probably a gapps out there that is up to date that does that already. I don't mind adding them quickly though. Removing all the other google play apps like music takes longer. I also move the apps i use the most to system to free up lot's of space. It is trial and error though as some apps / roms don't like certain programs in system. I hope this helps someone else get some ideals to make things easier on them. Maybe in the future i will make a more detailed guide on how to easily switch roms and restore apps and data quickly. Peace! Nap time lol.
DsyMnapTic
Android Expert
I got a flash error with only this ROM something about symlinks not setting properly and update binary stuff. I really can't remember what it said and don't know how to record it so I can look at it once I restore my backup.
roadkill42
Android Expert
what I did was flash one of the other ones then flashed slim
DsyMnapTic
Android Expert
I'll try though I'm not sure why that would make a difference.... Maybe I just had a bad download...
dragonhart6505
Android Expert
anyone figure out the obb on sd isue
roadkill42
Android Expert
its the only way I could get it to flash
stolikat
Well-Known Member
Can you provide a link or explain what this is to a noob? I am running this ROM and love it.
JHell
Android Enthusiast
Means everything u download goes on ur internal SD instead of the external one
modhatter6811
Android Enthusiast
To add to this, normally you can specify a download location within any browser, however, I've found that it never sticks like it should. I have to specify the SD card every single time. Also, apps get their info stored here too, it creates a lot of problems. Mostly just for games, but a few other apps take issue with it too. Its the only thing holding me back from running it for the time being, and sadly, I'm not sure its something that can be fixed. As far as I've read, its some change that's supposed to "close" some sort of loop hole dealing with apps trying to read folders and info that doesn't belong to them. They should have just left permission management in there, or made a more detailed one like what you get with Xprivacy. Would have saved worlds of trouble.
stolikat
Well-Known Member
I have been transferring apps via link2sd. It is the first time I have used it. Should I see the apps in the partitioned part of my SD card? I only see a lost+found folder.
So know I am not sure if the apps are on my SD as link2SD is telling me or still on the internal drive.
dragonhart6505
Android Expert
Sigh...you keep getting it wrong...
I HAVE the files backed up and am placing them manually to the external storage. The issue is that the applications are NOT READING the external sd and keep saying that the files need to be downloaded, which THEN it will downloaded to the internal sd which in most cases there isnt enough space. So using an app like foldermount or Link2Sd has to be used and resolves that problem, but its kind of a pain sometimes.
Now the other issue is OGL. There has to be some porting done to get it to work right. Games like Dead Trigger 2 have graphical errors and others like most of the ones from Gameloft dont even boot. Hopefully this can be looked at.
I know my issue seems to concern gaming on this thing...and you'd be right mostly. May seem selfish but without these resolved other graphical issues may arise down the line. The CM11 roms are nearly perfect in every way with the exception of these 2 problems. Phenomx4 is incredible
I HAVE the files backed up and am placing them manually to the external storage. The issue is that the applications are NOT READING the external sd and keep saying that the files need to be downloaded, which THEN it will downloaded to the internal sd which in most cases there isnt enough space. So using an app like foldermount or Link2Sd has to be used and resolves that problem, but its kind of a pain sometimes.
Now the other issue is OGL. There has to be some porting done to get it to work right. Games like Dead Trigger 2 have graphical errors and others like most of the ones from Gameloft dont even boot. Hopefully this can be looked at.
I know my issue seems to concern gaming on this thing...and you'd be right mostly. May seem selfish but without these resolved other graphical issues may arise down the line. The CM11 roms are nearly perfect in every way with the exception of these 2 problems. Phenomx4 is incredible
modhatter6811
Android Enthusiast
From, External Storage Technical Information | Android Developers
"The default platform implementation of this feature leverages Linux kernel namespaces to create isolated mount tables for each Zygote-forked process, and then uses bind mounts to offer the correct user-specific primary external storage into that private namespace.
At boot, the system mounts a single emulated external storage FUSE daemon at EMULATED_STORAGE_SOURCE, which is hidden from apps. After the Zygote forks, it bind mounts the appropriate user-specific subdirectory from under the FUSE daemon to EMULATED_STORAGE_TARGET so that external storage paths resolve correctly for the app. Because an app lacks accessible mount points for other users' storage, they can only access storage for the user it was started as.
This implementation also uses the shared subtree kernel feature to propagate mount events from the default root namespace into app namespaces, which ensures that features like ASEC containers and OBB mounting continue working correctly. It does this by mounting the rootfs as shared, and then remounting it as slave after each Zygote namespace is created."
It goes down to the kernel level. This process is forcing apps to check our internal storage for obb data. So, regardless of what's done to it, ex. folder mount, symlinks etc. the original target gets resolved back to emulatedstorage0 first, before anything else. And since it does this first, Gameloft games are just seeing the nonexistent obb data, before the symlink redirects it to the SD, which it then gets denied access to, because the app its self didn't make the "original" directory. (this whole process also doesn't play nice with the way cm11 is set up) Hence why folder mount works for most apps, but not all of them. Its also why adding the external write permission doesn't fix it for us. If someone can make the mount process grab our external storage as the primary storage, rather than the internal side, it should in theory, fix the issue. Then again, newer apps might break from this if the target version it was originally developed for is 4.2+ There's a petition in place for them to NOT implement these changes any longer in android with the release of android L. Devs are pretty pissed off about it. Hopefully they'll fix it. Sorry if it sounds confusing as hell, I have a very good idea of what's going on, I'm just not very good at putting things in human readable terms sometimes. Hopefully somebody understands what I'm trying to say.
"The default platform implementation of this feature leverages Linux kernel namespaces to create isolated mount tables for each Zygote-forked process, and then uses bind mounts to offer the correct user-specific primary external storage into that private namespace.
At boot, the system mounts a single emulated external storage FUSE daemon at EMULATED_STORAGE_SOURCE, which is hidden from apps. After the Zygote forks, it bind mounts the appropriate user-specific subdirectory from under the FUSE daemon to EMULATED_STORAGE_TARGET so that external storage paths resolve correctly for the app. Because an app lacks accessible mount points for other users' storage, they can only access storage for the user it was started as.
This implementation also uses the shared subtree kernel feature to propagate mount events from the default root namespace into app namespaces, which ensures that features like ASEC containers and OBB mounting continue working correctly. It does this by mounting the rootfs as shared, and then remounting it as slave after each Zygote namespace is created."
It goes down to the kernel level. This process is forcing apps to check our internal storage for obb data. So, regardless of what's done to it, ex. folder mount, symlinks etc. the original target gets resolved back to emulatedstorage0 first, before anything else. And since it does this first, Gameloft games are just seeing the nonexistent obb data, before the symlink redirects it to the SD, which it then gets denied access to, because the app its self didn't make the "original" directory. (this whole process also doesn't play nice with the way cm11 is set up) Hence why folder mount works for most apps, but not all of them. Its also why adding the external write permission doesn't fix it for us. If someone can make the mount process grab our external storage as the primary storage, rather than the internal side, it should in theory, fix the issue. Then again, newer apps might break from this if the target version it was originally developed for is 4.2+ There's a petition in place for them to NOT implement these changes any longer in android with the release of android L. Devs are pretty pissed off about it. Hopefully they'll fix it. Sorry if it sounds confusing as hell, I have a very good idea of what's going on, I'm just not very good at putting things in human readable terms sometimes. Hopefully somebody understands what I'm trying to say.
dragonhart6505
Android Expert
THATS an explination. Thanks
X
x000x
Guest
this is one thing that i wish for with android. many times in the past i've wished for a 'plug and play' feature that basically allowed me to store all my selected apps and games on a sd card and to be able to seamlessly hot-swap and switch between my phone and tablet at whim.
Ok Ive had about a week with this ROM and all I can say is OMG! The battery life on this is literally triple that of my stock device! And this is with both cores running at 1.72ghz on itellidemand. Kit Kat is awesome imo. I have a nearly a half gb of RAM free while streaming Tune In and using NAv. And did I mention the ******* battery life? The reason im so in tune with my battery life is the reason i have to ditch this phone. Ive figured out that charging my phone kills all functionality. I get road noise when audio is plugged in and charging on 1 amp battery/car/wall or 2.1 amp wall/car. So all i have is 2.1 amp output on our tablet powerbank. NAH! But i have to say, that this is going to make a sick Kit Kat media device.