Database Develop

[Q] Topogigi 1.7 - market problem

Hello
I post my problem here because i am new and so cannot use the official threads in dev part...
So I just install the topogigi 1.7 release and now each time I try to access the market to install anything it fail with a message that my device to not have enough free space.
As it's a fresh install, it's of course not the case ...
I did a df using adb, /data as 1Gb free ...
df
Filesystem Size Used Free Blksize
/dev 185M 32K 185M 4096
/mnt/asec 185M 0K 185M 4096
/mnt/obb 185M 0K 185M 4096
/system 338M 283M 55M 1024
/data 1G 92M 1G 4096
/mnt/extasec 185M 0K 185M 4096
/lgdrm 2M 2M 398K 2048
/mnt/sdcard 5G 874M 4G 32768
/mnt/secure/asec: Permission denied
/mnt/sdcard/_ExternalSD 3G 2G 1G 32768
/mnt/extsecure/extasec: Permission denied
Any ideas ?
thanks

Hi,
Yes, this a known problem, do a reboot after the first configurations, and all will be ok then.

It's probably not enough space on /cache that it's complaining about.

Indeed, I reboot the phone and now market is ok to install software
I did not find that info in the original post (which is quite huge I must agree)
Thanks for your answer

if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys

Rusty! said:
if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys
Click to expand...
Click to collapse
So if I just edit the build.prop file, will I get access the all the apps that have been missing from the market? It's a weird mix that is missing - various games like NOVA2, and even the tvguide.co.uk app.
If this works, your'e a hero!

I actually meant to put that in the other Topogigi Market problem thread, but yeah you might well find it fixes that.

Thanks for your help, will try this later

Rusty! said:
if you want to know, open your build.prop file and look for a line that starts:
ro.build.fingerprint
Here is what CM uses:
Code:
ro.build.fingerprint=lge/lge_star/p990/p990:2.2.2/FRG83G/lgp990-V10b.2ED2ADCFFC:user/release-keys
Click to expand...
Click to collapse
I noticed that Paul spoofs the Nexus S fingerprint in his Gr2
ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys
Will that give a better range of market compatibility or will I lose Tegra specific apps? There is a ro.board.platform=tegra so that might take care of that.
I guess I'll just experiment.... but it's amazing how much you can learn from a few tweaking experts here on XDA.... one day I'll have to try doing a proper custom rom for myself

rmein said:
I guess I'll just experiment
Click to expand...
Click to collapse
That's the best option.
Even with the 2.2.2 CM fingerprint, I had no trouble getting Sprinkle from the Market, which requires 2.3

Rusty! said:
That's the best option.
Even with the 2.2.2 CM fingerprint, I had no trouble getting Sprinkle from the Market, which requires 2.3
Click to expand...
Click to collapse
Experimentation done!
Spoofed Nexus S and CM fingerprint won't let me download Galaxy on Fire or Sprinkle and can't even find NOVA2, but tvguide.co.uk is OK.
Back to Fr19 Let's hope Paul's Gr3 will help me out.

Misread, oops!

Sorry what is this topigigi?
Sent from my Optimus 2X using Tapatalk

Workaround mabye
rmein said:
Experimentation done!
Spoofed Nexus S and CM fingerprint won't let me download Galaxy on Fire or Sprinkle and can't even find NOVA2, but tvguide.co.uk is OK.
Back to Fr19 Let's hope Paul's Gr3 will help me out.
Click to expand...
Click to collapse
You can install tegra games from the www marked, just installed sprinkle

@hd2000
Topogigi is a custom rom, one of the best I would say (IMO)
http://forum.xda-developers.com/showthread.php?t=1254359

[Q] How to enable fast charging(PROMETHEUS KERNEL)

Hello,
I have a problem to enable fast charging.
Using PROMETHEUS KERNEL(Version7- Linaro(on speed 767)) and as I checked "FAQ & SOURCES" in that thread this option is allowed by siple modification:
"echo 1 > /sys/class/power_supply/battery/fast_charge"
But I am not allowed write to "/sys/class/power_supply/battery/", return error is:
"cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory"
Directory "/sys/class/power_supply/battery" exist, but I don't have a permission write.
Any idea why I cannot do this?

Did you type 'su' in the terminal?
Sent from my HTC Desire C using XDA Premium 4 mobile app

smoza said:
Did you type 'su' in the terminal?
Sent from my HTC Desire C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, this is complete command which using:
[email protected]:/ # su
[email protected]:/ # echo 1 > /sys/class/power_supply/battery/fast_charge
sh: cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory
1|[email protected]:/ #
but of course, directory exists:
130|[email protected]:/ # ll /sys/class/power_supply/battery/
-rw--w---- root root 4096 2013-09-06 13:45 audio_stat
-r--r--r-- root root 4096 2013-09-06 13:45 batt_attr_text
-r--r--r-- root root 4096 2013-09-06 13:45 batt_current
--w--w---- root root 4096 2013-09-06 13:45 batt_debug_flag
-r--r--r-- root root 4096 2013-09-06 13:45 batt_id
.....

I'm sorry but I really don't know how to help you
Sent from my HTC Desire C using XDA Premium 4 mobile app

BlaMa said:
Hello,
I have a problem to enable fast charging.
Using PROMETHEUS KERNEL(Version7- Linaro(on speed 767)) and as I checked "FAQ & SOURCES" in that thread this option is allowed by siple modification:
"echo 1 > /sys/class/power_supply/battery/fast_charge"
But I am not allowed write to "/sys/class/power_supply/battery/", return error is:
"cannot create /sys/class/power_supply/battery/fast_charge: No such file or directory"
Directory "/sys/class/power_supply/battery" exist, but I don't have a permission write.
Any idea why I cannot do this?
Click to expand...
Click to collapse
I talked with nikhil (the maker of Prometheus ) and he told me that he will enable it in the next version then he left it was like a month ago or before so I think you must do something inside the kernel to enable it then you must type what you said above
Edit: I meant cm10 kernel not sense

webhijacker said:
I talked with nikhil (the maker of Prometheus ) and he told me that he will enable it in the next version then he left it was like a month ago or before so I think you must do something inside the kernel to enable it then you must type what you said above
Edit: I meant cm10 kernel not sense
Click to expand...
Click to collapse
Hello, thank you for explanation.
I am using Sense version, but maybe this is a reason why I can not use this feature.
Due my account limitation, I can send my post only in this general forum and not directly in Prometheus kernel thread.
Say my thanks also to developer and thank you one more time.

[Tutorial] Kernel building instructions for Xperia Z2

hello folks!
i have been working on kernels for various xperia devices (around 22 devices or so ) since the Xperia X10...
FIRSTLY the kernel building instructions given by Sony in the README_Xperia are WRONG!!!
huge thanks to @Kali- to fix the dtbTools issue (Z2 needs v2 dtb)!
specific instructions on how to build kernel for Xperia Z2 can be found here:
Instructions for MSM8974AB
I have a very detailed thread with information on how to build kernels for various xperia devices:
[Tutorial] Kernel building instructions for Xperia devices
Please use this thread to post your feedback and incase you need any help with building kernels for this device!
regards,
DooMLoRD

Same makefile fixes are for msm8x28?(Xperia T2 Ultra)
Cheers,
AJ

Abhinav2 said:
Same makefile fixes are for msm8x28?(Xperia T2 Ultra)
Cheers,
AJ
Click to expand...
Click to collapse
havent tested but should work

DooMLoRD said:
havent tested but should work
Click to expand...
Click to collapse
OK thanks sir I'll try and report. Currently trying to somehow root on locked bootloader but couldn't find any vulnerabilities which I can exploit. Will do some more tests to see if I can get something.
Cheers,
AJ

Abhinav2 said:
OK thanks sir I'll try and report. Currently trying to somehow root on locked bootloader but couldn't find any vulnerabilities which I can exploit. Will do some more tests to see if I can get something.
Cheers,
AJ
Click to expand...
Click to collapse
no vulnerabilities currently work... I have been testing on T, SP, Z, Z1, Z2... nothing so far...

DooMLoRD said:
no vulnerabilities currently work... I have been testing on T, SP, Z, Z1, Z2... nothing so far...
Click to expand...
Click to collapse
We can still execute scripts from /data/local/tmp. So as I understand, we need to properly mount system partition as 'rw' with that script?
EDIT: But I guess even for mounting it as rw we need su, so it pretty much comes back to it.
EDIT2: @DooMLoRD, can we put a script in /data/local/tmp, chmod it 0755, and then use it to grep default.prop and change, ro.secure=1 to ro.secure=0? And then with insecure ramdisk(obviously without rebooting or else, it'll load the default value, i.e. , 1), can we try to root it? (But I guess it is read-only also, so is there a way we can change the owner and group to allow changing it as rw?)
Cheers,
AJ

Abhinav2 said:
We can still execute scripts from /data/local/tmp. So as I understand, we need to properly mount system partition as 'rw' with that script?
EDIT: But I guess even for mounting it as rw we need su, so it pretty much comes back to it.
EDIT2: @DooMLoRD, can we put a script in /data/local/tmp, chmod it 0755, and then use it to grep default.prop and change, ro.secure=1 to ro.secure=0? And then with insecure ramdisk(obviously without rebooting or else, it'll load the default value, i.e. , 1), can we try to root it? (But I guess it is read-only also, so is there a way we can change the owner and group to allow changing it as rw?)
Cheers,
AJ
Click to expand...
Click to collapse
It's not that easy...
Sent from my D6503 using XDA Free mobile app

[MODS] Useful Mods for R

To Do List:
Create stock System.img for restoring to stock in preparation for Lollipop.
Post batch tool to simplify everything
Work on getting busybox working to expand capabilities
Android Wear Lollipop?
MODS:
Increase Vibration Strength:
Code:
adb shell
su
echo 85 > /sys/class/timed_output/vibrator/amp
echo 120 > /sys/class/timed_output/vibrator/driving_ms
Don't set amp over 100, and don't set driving_ms over I would say 200 max. Our dory friends set it around 160ish. The higher the number the stronger the vibration, at a cost of power and perhaps decreased vibration life?
I found the best way to do this was to setup adb over bluetooth so you could feel what the setting feels like by setting a timer or something.
Increase DPI to Make Analog Keyboard Useful
For those who want to mess with it this makes the Microsoft analog watch more useful by increasing the ppi a lot. It messes up text in almost every other spot besides the keyboard area, so now you can actually hit the enter key, barely though. Just gonna post this til I have something better figured out.
Build.prop link
Analog Keyboard Download - Follow install instructions found in zip
Put build.prop where you have adb located. Stock DPI is 240 if you want to edit it back.
Code:
adb push build.prop /sdcard
adb shell
su
mount -o rw,remount /system /system
cp /sdcard/build.prop /system
reboot

tonu42 said:
MODS:
Increase Vibration Strength:
Code:
adb shell
su
echo 85 > /sys/class/timed_output/vibrator/amp
echo 120 > /sys/class/timed_output/vibrator/driving_ms
Don't set amp over 100, and don't set driving_ms over I would say 200 max. Our dory friends set it around 160ish. The higher the number the stronger the vibration, at a cost of power and perhaps decreased vibration life?
Click to expand...
Click to collapse
Can you tell me what the default/stock settings are? I used the settings you posted and it is much better but i am curious what the factory settings were.

jimmydigital00 said:
Can you tell me what the default/stock settings are? I used the settings you posted and it is much better but i am curious what the factory settings were.
Click to expand...
Click to collapse
Amp was at 80 and driving_ms was at a pitiful 20 or 30 I think......
Thinking about it I should have written them down because I don't think a system.img install will revert it.
Can someone do a cat driving_ms for us?

Untouched original:
[email protected]:/ # cat /sys/class/timed_output/vibrator/amp
80
[email protected]:/ # cat /sys/class/timed_output/vibrator/driving_ms
20

zvieratko said:
Untouched original:
[email protected]:/ # cat /sys/class/timed_output/vibrator/amp
80
ro[email protected]:/ # cat /sys/class/timed_output/vibrator/driving_ms
20
Click to expand...
Click to collapse
Thank you good sir. Boosting driving_ms a lot seems to be the best way to increase the strength.

Works
This works great! Thanks!

OP updated with another mod.

Hi all ,
are there any rooting instructions for the LG GWATCH R in order to use the adb commands ?
regards
Achim
Gesendet von meinem SM-N9005 mit Tapatalk

For sake of completeness, all the defaults:
Code:
/sys/class/timed_output/vibrator/amp
80
/sys/class/timed_output/vibrator/braking_gain
100
/sys/class/timed_output/vibrator/braking_ms
0
/sys/class/timed_output/vibrator/driving_ms
20
/sys/class/timed_output/vibrator/enable
0
/sys/class/timed_output/vibrator/n_val
127
/sys/class/timed_output/vibrator/warmup_ms
0

How can I set these parameters?
I'm not expert about this device and I don't know what I have to do.
Can you explane me step by step?
THX

cybermungo said:
Hi all ,
are there any rooting instructions for the LG GWATCH R in order to use the adb commands ?
regards
Achim
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
The root guide is in another thread.
Sent from my A0001 using XDA Free mobile app

Work the vibration mod on new update 5.01? I think it should or?

coyote_f said:
Work the vibration mod on new update 5.01? I think it should or?
Click to expand...
Click to collapse
Yes, I need to modify this guide, TBH though I might try to create an android wear app to just do a one click and set.

tonu42 said:
Yes, I need to modify this guide, TBH though I might try to create an android wear app to just do a one click and set.
Click to expand...
Click to collapse
I tried last night, and running the commands in the OP didn't do anything. Is that why you're saying you need to modify the guide? Running lollipop btw

nickmilla15 said:
I tried last night, and running the commands in the OP didn't do anything. Is that why you're saying you need to modify the guide? Running lollipop btw
Click to expand...
Click to collapse
Yea that's why I need to change it. I'll change it maybe later tonight. But for some reason the changes don't stick after reboot. I'll look into it.
Sent from my A0001 using XDA Free mobile app

tonu42 said:
Yea that's why I need to change it. I'll change it maybe later tonight. But for some reason the changes don't stick after reboot. I'll look into it.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Wicked. I look forward to it ?

tonu42 said:
Yea that's why I need to change it. I'll change it maybe later tonight. But for some reason the changes don't stick after reboot. I'll look into it.
Click to expand...
Click to collapse
changes to anything in /sys are lost on reboot. sysfs, like procfs (/proc) is not a persistent filesystem.
you would need to add your changes to a boot script so they run on boot everytime
-fg

fg said:
changes to anything in /sys are lost on reboot. sysfs, like procfs (/proc) is not a persistent filesystem.
you would need to add your changes to a boot script so they run on boot everytime
-fg
Click to expand...
Click to collapse
Yep already on it. I'm making a proper rootboot.IMG like the original G watch. Also adding into the kernel a script to edit the files for vibration.
Sent from my A0001 using XDA Free mobile app

tonu42 said:
Yep already on it. I'm making a proper rootboot.IMG like the original G watch. Also adding into the kernel a script to edit the files for vibration.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Awesome!

Remove all LG watchfaces, I'm using facer
adb shell
su
mount -o rw,remount /system /system
cd system
cd priv-app
rm -r Lge*
Or, if you want, you can delete only any of these..
---------- Post added at 11:22 PM ---------- Previous post was at 10:28 PM ----------
Sorry admin... But my suggestion is like a mod...
It's not a question...

[Kernel][Sony5.x][Z5C]Zombie[12.11.16]

Zombie is a Kernel which extends the Xperia Z5C's capabilities.
It is aimed at including only useful and strictly tested features, enhancements and optimisations,
Important: I do not accept Bug reports when you are running a modified Rom or using Xposed!
Changes compared to Stock-Kernel:
* Important bug fixes / security patches
* CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
* Underclocked both Cluster to 1,344/1,536 GHz respectively
* Custom brightness scaling (reduced min. brightness, increase max. brightness)
* Hold Power-Button for 5 seconds to reboot into bootloader
Security Patch-Level: November
Todo:
* -
App to check your device's Panel Manufacturer:
SonyKitakamiPanelInfov1.0 Download
Downloads:
Kernel Zip Package:
Latest Build: Zombie-b9
Installation:
* Unpack ZIP and flash Kernel via Fastboot
Sources:
Zombie-MM Kernel Source at Github
PanelInfo-App Source at Github
XDA:DevDB Information
Zombie, Kernel for the Sony Xperia Z5 Compact
Contributors
Tommy-Geenexus
Kernel Special Features:
Version Information
Status: Testing
Created 2015-10-13
Last Updated 2016-11-12

Reserved
Code:
// nothing to see here

Great, hope there will be a continous work on these thingies as this device is rather new and we need every bit that can help. Even for Locked Bootloaders...

Since it is insecure (ro.secure=0), will adbd run as root?

nilezon said:
Since it is insecure (ro.secure=0), will adbd run as root?
Click to expand...
Click to collapse
Nope, it needs also ro.debuggable=1 and a modified adbd binary in ramdisk.

Tommy-Geenexus said:
Nope, it needs also ro.debuggable=1 and a modified adbd binary in ramdisk.
Click to expand...
Click to collapse
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Edit:
I'm trying to compile your kernel but am getting a weird error:
Code:
CC mm/filemap.o
mm/filemap.c: In function 'grab_cache_page_write_begin':
mm/filemap.c:2306:1: internal compiler error: Segmentation fault
}
Using aarch64-linux-android-4.9 toolchain from Google.
Do you have any pointers for me?

nilezon said:
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Click to expand...
Click to collapse
One could implement su and all needed files in the ramdisk and copy them over, however i'd vote for someone to build TWRP.
I have not much experience in shell scripting, and having a working recovery would be the optimal solution.

nilezon said:
Thank you.
I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?
I need that root shell
Edit:
I'm trying to compile your kernel but am getting a weird error:
Code:
CC mm/filemap.o
mm/filemap.c: In function 'grab_cache_page_write_begin':
mm/filemap.c:2306:1: internal compiler error: Segmentation fault
}
Using aarch64-linux-android-4.9 toolchain from Google.
Do you have any pointers for me?
Click to expand...
Click to collapse
Had exactly the same issue.
I suppose you cloned the GCC from Google like me, just checkout the marshmallow branch, the master branch has some issues.
Otherwise i can upload my GCC (latest AOSP toolchain) and link it.

Tommy-Geenexus said:
Had exactly the same issue.
I suppose you cloned the GCC from Google like me, just checkout the marshmallow branch, the master branch has some issues.
Otherwise i can upload my GCC (latest AOSP toolchain) and link it.
Click to expand...
Click to collapse
Got it working using marshmallow-release branch.
THANK YOU!

nilezon said:
Got it working using marshmallow-release branch.
THANK YOU!
Click to expand...
Click to collapse
Np, feel free to contribute if you find any useful stuff, always good to have some dev's around.

Tommy-Geenexus said:
One could implement su and all needed files in the ramdisk and copy them over, however i'd vote for someone to build TWRP.
I have not much experience in shell scripting, and having a working recovery would be the optimal solution.
Click to expand...
Click to collapse
Hey @Tommy-Geenexus.
1.) Great work btw.
2.) Have you run
Code:
$. su
#. cat /proc/emmc
(or similar) On your Z5C yet?
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
3.) Have you attempted to/had any luck compiling your kernel with any tool chain other then GCC 4.9 from marshmallow branch?
Regards
Joeisgood99.

Joeisgood99 said:
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
Click to expand...
Click to collapse
You can use
/dev/block/platform/soc.0/by-name/***
if you need it for fstab.
https://github.com/AndroPlus-org/an...ob/TWRP-28.0.A.8.251-karin/rootdir/twrp.fstab
I posted test TWRP build for E6653 before in Z5 forum, but no one has interest....
http://x.andro.plus/1OrEQ7i
[EDIT] @nilezon
It's for E6653, but differences are only configs in default.prop and kernel modules in sbin in recovery ramdisk, so you can use it on other Z5/Z5C after editing codenames and lcd_density and overwriting kernel modules.

AndroPlus said:
You can use
/dev/block/platform/soc.0/by-name/***
if you need it for fstab.
https://github.com/AndroPlus-org/an...ob/TWRP-28.0.A.8.251-karin/rootdir/twrp.fstab
I posted test TWRP build for E6653 before in Z5 forum, but no one has interest....
http://x.andro.plus/1OrEQ7i
Click to expand...
Click to collapse
Good job!
Does the E6653 recovery work with E5823, or could you recompile it for suzuran, please?
Edit @AndroPlus
Thank you. I'll get the Z5C in a few days and will take the recovery for a spin then.

Joeisgood99 said:
Hey @Tommy-Geenexus.
1.) Great work btw.
2.) Have you run
Code:
$. su
#. cat /proc/emmc
(or similar) On your Z5C yet?
Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.
3.) Have you attempted to/had any luck compiling your kernel with any tool chain other then GCC 4.9 from marshmallow branch?
Regards
Joeisgood99.
Click to expand...
Click to collapse
Not yet, but here is the output of "cat /proc/partitions":
Code:
major minor #blocks name
254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 2048 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 81920 mmcblk0p3
179 4 128 mmcblk0p4
179 5 128 mmcblk0p5
179 6 1 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 256 mmcblk0p9
179 10 1 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 8 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 256 mmcblk0p19
179 20 256 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 65536 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 512 mmcblk0p34
259 3 1 mmcblk0p35
259 4 512 mmcblk0p36
259 5 102400 mmcblk0p37
259 6 10240 mmcblk0p38
259 7 16384 mmcblk0p39
259 8 307200 mmcblk0p40
259 9 204800 mmcblk0p41
259 10 24182784 mmcblk0p42
259 11 5384192 mmcblk0p43
179 32 4096 mmcblk0rpmb
179 64 31166976 mmcblk1
179 65 31162880 mmcblk1p1
The names are missing, however from my first research there is no recovery partition (I guess thats what you're interested in).
Regarding TC'S, 4.8 did not work, 4.9 works fine, haven't tested anything higher though.

i saw this recovery in z5 forum, i've used android kitchen on windows to unpack and edited the lcd density etc in the default.prop and repacked file
but havent done anything to the kernel modules. dont know how to
anyway here's the thing i've done for now. it's the recovery i've played with
https://db.tt/tqhL9Qba

shafiq01 said:
i saw this recovery in z5 forum, i've used android kitchen on windows to unpack and edited the lcd density etc in the default.prop and repacked file
but havent done anything to the kernel modules. dont know how to
anyway here's the thing i've done for now. it's the recovery i've played with
https://db.tt/tqhL9Qba
Click to expand...
Click to collapse
Hey thanks @shafiq01
But that link takes me to a picture of your settings menu.
Thanks @Tommy-Geenexus for the partition table! Thats a great help.
Are you able to get the partition names?
Regards
joeisgood99.

Here is a repack of @AndroPlus TWRP.
Anyone with an E5823 and unlocked bootloader can try it out using:
Code:
fastboot boot recovery.img
I still have no phone, so it is not tested.
Download:
https://mega.nz/#!pgIy2bYR!G-Hemo8rZdh9GBG_hIQOxHnPhdweFZNGpcQdAWPT1t8
All credit to @AndroPlus !

nilezon said:
Here is a repack of @AndroPlus TWRP.
Anyone with an E5823 and unlocked bootloader can try it out using:
Code:
fastboot boot recovery.img
I still have no phone, so it is not tested.
Download:
https://mega.nz/#!pgIy2bYR!G-Hemo8rZdh9GBG_hIQOxHnPhdweFZNGpcQdAWPT1t8
All credit to @AndroPlus !
Click to expand...
Click to collapse
Screen is blank, ADB controls work though.
However mounting /data failed, something must be up with the twrp fstab.

Tommy-Geenexus said:
Screen is blank, ADB controls work though.
However mounting /data failed, something must be up with the twrp fstab.
Click to expand...
Click to collapse
Thank you for testing.
I'll get the phone tomorrow and will fix the bugs then.

Joeisgood99 sorry, i uploaded to dropbox while battery on laptop was dying hehe... socopy wrong url
anyway, now i see nilezon has done it. so no reason to i also try
anyway a bit of topic (but then again we all aim to get root in the smartest way and avoid loss of drm at the same time)
have to wait a bit and see if we in some way can root before unlocking bl
i saw in another thread that if we flash userdebug dev firmware, then we could use adb commands such as 'adb remount' 'adb disable-verity' and then 'adb root'
i'll try to flash userdebug firmware first and see what outcome it gives, hence i have access to that but last time i didn't managed to pack it correctly in flashtool
but i will give it shot more