[LolliPop][Prerooted flashable zip][23.1.A.0.690][Z2 tablet SGP511]

[pixbuf]

External SD card not writable

Thanks very much for providing this zip file for us. It works great...except for one thing: the external SD card is not writable. I tried various apps from the play store and they all fail. I write-enabled the SD card in fx file manager, but it doesn't seem to be actually write enabled. Titanium Backup fails to back anything up with the message "insufficient free storage space".
Any ideas?

 

[kulvertti]

Thanks very much for providing this zip file for us. It works great...except for one thing: the external SD card is not writable. I tried various apps from the play store and they all fail. I write-enabled the SD card in fx file manager, but it doesn't seem to be actually write enabled. Titanium Backup fails to back anything up with the message "insufficient free storage space".
Any ideas?

You are welcome. Sorry to hear you have problem but I can't reproduce it. First time I use sd card with this firmware it ask if I want to use it and after that it works just fine. Any chance that you have SanDisk card that just stop working? Anyone else have this problem?

 

[CAL7]

You are welcome. Sorry to hear you have problem but I can't reproduce it. First time I use sd card with this firmware it ask if I want to use it and after that it works just fine. Any chance that you have SanDisk card that just stop working? Anyone else have this problem?

Me, but I thought it was expected (until [NUT] provides us r/w access, which would allow a utility like sdfix to provide user app access to the sdcard). If there's another way, I'd like to try it.

 

[pixbuf]

Me, but I thought it was expected (until [NUT] provides us r/w access, which would allow a utility like sdfix to provide user app access to the sdcard). If there's another way, I'd like to try it.

I thought that only pertained to r/w access to /system, not to /storage/sdcard1. (or whatever that was).

 

[T-junk]

Not exactly sure what the -installer.zip version is but ill trust you! Downloading it now

[NUT] delivers a flashable zip package for his recovery but also a installer zip package which has ADB etc. inside and some more fancy tools. If you have a rooted firmware, which this one is thnx to Kulverti. You always have the possibility to use the installer zip package which comes directly available along the flashable zip package

flashable package == on-device flashing where the installer zip has to be run from a command prompt on your PC. I hope this clears things up a bit. Just PM me then i can try to give you a more in-depth explainatory, as i don't want to clutter this thread.

The pre-rooted package works like a glove btw, Kulverti. Thanx for being 'quick' hehe.

 

[galupo]

Can't install Busybox can any one assist?

 

[kulvertti]

Me, but I thought it was expected (until [NUT] provides us r/w access, which would allow a utility like sdfix to provide user app access to the sdcard). If there's another way, I'd like to try it.

I thought that only pertained to r/w access to /system, not to /storage/sdcard1. (or whatever that was).

Thanks for feedback. In KK Google deside to restrict app´s acces to external sd card or more like other app´s folder´s in there. In LP this is kind of fixed by adding app developers possibility to update their apps to support again writing acces to external sd card. So in LP firmware there shouldn´t be problem to write external sd card if your app is up to date.

Mentioned Sdfix app and similar´s need to write acces to system partition to chance how apps are allowed to have write acces to external sd card. So if you want to try that or similar you have to wait.

 

[kulvertti]

Can't install Busybox can any one assist?

As mentioned at the moment we only have read acces to system so we have to wait [NUT] update Dualrecovery to work also with LP firmware. And by the way, if you are using Dualrecovery, don´t install any other busybox because one wich come with Dualrecovery works fine and you might end to troubles with other one.

 

[kulvertti]

Op updated. Now we have system read / write acces. No working custom recovery yet.

 

[GalaxyWhy]

I have one bug - dunno if its coz i dirty flashed or not.... but my status bar is blue in apps that dont have status bar coloring instead of the standard black :/ weird

 

[galupo]

Op updated. Now we have system read / write acces. No working custom recovery yet.

Is a working busy box included in this build?

 

[kulvertti]

Is a working busy box included in this build?

Yes it is.

 

[thecrunked]

that is normal as far as i can tell. i did clean install and mine looks like that too. my wife has a z3 compact, i cant remember but im pretty sure hers looked like that too after i installed lollipop on her phone

 

[Kussie]

Is there a way to get system rw if we flashed it before it was updated to include it? I dont want to have to reflash and get everything back up and running again

 

[GalaxyWhy]

that is normal as far as i can tell. i did clean install and mine looks like that too. my wife has a z3 compact, i cant remember but im pretty sure hers looked like that too after i installed lollipop on her phone

Are u talking about the blue status bar? Its really annoying

 

[thecrunked]

Yah that's the one. I find it distracting and out of place. Maybe once e we get a working recovery it can be removed via xposed tweaks

 

[WarCow]

Yah that's the one. I find it distracting and out of place. Maybe once e we get a working recovery it can be removed via xposed tweaks

Yeah, that could be nice. I changed the color by changing to a grey theme..looks less distracting

 

[BLiapis]

As said I don't see any reasons to wait. As long you have nandroid backup of your kk firmware and rootable version of your device firmware no matter what happen with recovery you don't loose anything and are able to try what ever you decide.
Here is link to .314 firmware (ftf) which is rootable. https://mega.co.nz/#!kcxxjaLA!itErjRi2fYPPswal-c7XasF_lAvPKyY4GwEzY3xgHZ0

Since xposed is no longer compatible with 5.0(?),ill wait up for a newer update. Thanx though :good:

 

[MJFox78]

Since xposed is no longer compatible with 5.0(?),ill wait up for a newer update. Thanx though :good:

there's already an alpha2 version of xposed for lollipop: http://forum.xda-developers.com/showthread.php?t=3034811

I'm using it on my HTC One M8 and didn't encounter any problems

but since we don't have a custom recovery on the tablet yet we can not install xposed, right?

 

[kulvertti]

I have one bug - dunno if its coz i dirty flashed or not.... but my status bar is blue in apps that dont have status bar coloring instead of the standard black :/ weird

Might be annoying but more like feature. Have you tried different themes as @WarCow mentioned or different home launchers? As @thecrunked taught Xposed with right module could fix this.

Is there a way to get system rw if we flashed it before it was updated to include it? I dont want to have to reflash and get everything back up and running again

With unlocked bootloader yes. With locked bootloader maybe. Problem here is that you have to find a way to kill Sony ric when your device boot. Dualrecovery do it for you by installing busybox and @[NUT]´s disable ric script wich needs busybox to work. Here is the link for flashable script to disable ric if you are interested:

https://mega.co.nz/#!EEwwyTCK!A9mukPNmnuULXCXaU_mmwmvfxLXxythip2PGqd-u4DI

So with locked bootloader you basicly need to push those files (busybox + script) to system partition without write acces to system. Maybe possible with ADB. Or you may found another way to kill Sony ric. With Sony Lollipop there is also problem with SELinux wich is the cause we don´t have custom recovery for locked bootloader at moment. It doesn´t influence to system r/w though. Let see if @[NUT] found solution to this.

Since xposed is no longer compatible with 5.0(?),ill wait up for a newer update. Thanx though :good:

As my bro @MJFox78 said there is xposed for Lollipop. It is alpha version and there might be problems with it. First one is how to install it without custom recovery. With locked bootloader it can be done by flashing it right after you have flashed prerooted firmware but before you boot your device first time. There are some report saying it´s working and some it isn´t. Someone report that it works only if you wipe dalvik cache on every boot. With unlocked bootloader it most likely is much easier. At the moment it might be good idea to wait that xposed is developed further and we have working recovery for locked bootloader unless you are not afraid of hickups.