yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] ondrejvaroscak:
This can be by wrong permission for the apk file...
[Sony Cross-Device General] ondrejvaroscak:
Recommend following procedure:

1. Clean your eyes

2. Read the text again

3. If it doesn`t help use vocabulary or translator

4. Ask friend who speaks English

5. Ask for help with "IF --- THEN" logical construction.

Now really, seriously, is it so complicated to understand? IF you find these files, delete them. It means, if you find NO such files, it is also OK.
[Sony Cross-Device General] new_world_2006:
what should i do ? i dont have any module , my SU version is 2.46 is that the problem ?
[Sony Cross-Device General] ondrejvaroscak:
Request for help

Guys, I am at almost at the end of my patience. Really. If you need help and assistance because something with the fix doesn't work, then:

1. Try to repeat the installation with fresh, clean installed ROM, without ANY modification except for SuperSU and XZDR

2. Provide device model and firmware version, together with XZDR and SuperSU version numbers

3. Try to use sony_fix version 3.0b if xposed_leak fix doesn't work for you, because sony_fix has ability to log booting process so you can read the log and figure out what may go wrong

4. There are also two logs from XZDR to look at
[Sony Cross-Device General] new_world_2006:
i have provided you with full history of my experience , if you point me with your reply

any way , where i can find the log files ?
[Sony Cross-Device General] ondrejvaroscak:
I am pointing anybody who requests help to provide relevant information in ONE post, not spreaded into 12 diffrents posts. So far I know just that you have LP 5.0.2 - but everybody has LP 5.0.2 - nothing about your fw version, nothing about your recovery. SuperSU 2.46 is ok, because almost everybody with PRFC prerooted fw has SuperSU 2.46. Then you write that you think it may be because old module, but you did full wipe ... WTF? So did you full wipe or you have an old module installed?

I would recommend you to do EXACTLY this:

1. Download LATEST vanilla stock ROM from Xperifirm for your device.

2. Create ftf in Flashtool from downloaded ROM

3. Create prerooted firmware in PRFC using SuperSU 2.46 and XZDR 2.8.12

4. Boot recovery, do a FULL WIPE - system, cache, data, internal media (user data), dalvik

5. Flash prerooted flashable firmware created in 3, dont reboot, SWITCH OFF

6. Flash ftf you created in 2, EXCLUDING SYSTEM

7. Boot

8. Update all apps

9. Boot recovery, flash sony_fix 3.0b

10. Flash xposed-arm.zip

11. WIPE CACHE and DALVIK

12. Reboot

13. Reboot AGAIN

14. Install xposed APK and reboot

15. Download, install and activate ONE module and soft reboot

16. Repeat 15 for any other module
[Sony Cross-Device General] mionica:
Hi dude,

I'll have a diagnostics .zip up shortly; I'll want the log from that.
[Sony Cross-Device General] baha76_s:
Guys, realy realy calm down.

I saw many many thread here in xda forum with alots of dump questions and alots of "basic skills people" but I didn't saw such intense environment, please guys calm down and take a snicker its good for you.

And at the other hand guys common, this forum is professional forum not spoon-feeding one, there is 2 roles you must did before posting:

1. Learning (I said learning the basic not all).

2. Searching.

Then IF (I say IF) there is no suitable answer for your problems, then ask with a proper question not a vague one with no details.

Please please let's this thread as professional as possible and avoid or ignore all inappropriate posts.

Read the thread one two three even ten times before posting something that will qualifies as stupid by others users.

And finally I ask (only asking) from the OP,any moderators here to do massive cleans up to lets only the professional and useful posts (even mine if you find it usefulness).

Thanks

Envoyé de mon D6603 en utilisant Tapatalk
[Sony Cross-Device General] GretaLewd:
[MENTION=6351145]ondrejvaroscak[/MENTION] , [MENTION=1103233]mionica[/MENTION] :

I've been following this thread since it started. For me it's been like reading a detective story or an episode of Aircrash Investigation where we find, from hard work and logical investigation, the answer to (or cause of) a problem. I may not understand all the code produced, but it has still been fascinating.

:good:

Sadly, there are many posting here who see this thread, and XDA in general, as an extension of Google Play Store. They expect you, the developers, to be providing working "Apps" and full instruction manuals to go along with them. Some of these people shouldn't even be here...it's like letting a clown loose in a nuclear power plant.

Reading some of the questions posted makes you loose faith in democracy - to think that some of these guys will be able to (or maybe already do) vote to choose a government is worrying.

:eek:

I've felt like this for a while - but, like you [MENTION=6351145]ondrejvaroscak[/MENTION], I've now had enough and had to "let of steam" :(

A BIG THANKS to you and all involved in investigating this problem and providing a workaround for the majority of users (including me :))

Over & Out
[Sony Cross-Device General] ondrejvaroscak:
YEP, exactly!
[Sony Cross-Device General] new_world_2006:
I know this is dump question , but where i can find the LOG file
[Sony Cross-Device General] ptmaniac:
This is pretty much how i installed my rom, your fix and xposed and got everything working fine.

Everyone who is having problems should follow this steps exactly, it may take more time but it'll ensure you have a fresh system with no leftovers from previous roms/mods that can cause trouble.
[Sony Cross-Device General] hassanmahmood:
What's PRFC? And when you say flash, do you mean from recovery or flashtool?

Thanks!
[Sony Cross-Device General] ondrejvaroscak:
Thats exactly what I am talking about. Not learning anything, not even a bit of own effort to find out. Just sitting here and waiting for everything to get served right under the nose.

PRFC is Pre-Rooted Firmware Creator

flash - it denpends what are you flashing. zip files are flashed in Recovery (exactly they are "processed"), ftf files in Flashtool.

Now you can maybe ask if you should use Sony or Androxyde's flashtool :)
[Sony Cross-Device General] ric69:
Relax man, thanks for your effort :good:

I'm the one of 20% who have bootloop between point 14&15 (And I follow your steps, even with ZXDR 2.8.14), after that I went to recovery, reflashed xposed, fix, wipe cache&dalvik and now I'm having Xposed installed but in red : "Installation is only possible manually via recovery" :p

TRY AGAIN LOL ... you should write "not for newbies" in first post because it's really not :cyclops:
[Sony Cross-Device General] Bartekreaper:
You have active app_process (61) and xposed bridge (64)? If yes, all work.

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] hassanmahmood:
I actually did try searching to figure out the acronym.

And I don't know how I was meant to search for the answer to my second question.

If you don't want to answer questions, then don't, but being snide and snarky isn't going to get anyone anywhere.

We're all trying to learn or we would not be here.

Thanks for answering my questions.
[Sony Cross-Device General] ondrejvaroscak:
learning is good thing but there are many who try to jump in middle of the sea without learning to swim. why people get into alpha software experiments when they don't know basics? the result is then the threads are full of the same repeated questions.
[Sony Cross-Device General] ric69:
Yes I have, so it's working

So restart from step1 is not needed :silly: just need to reflash fix if bootloop ?

thanks button pressed [MENTION=6351145]ondrejvaroscak[/MENTION] [MENTION=6181775]Bartekreaper[/MENTION] :good:
[Sony Cross-Device General] ondrejvaroscak:
because this thread presumes that people have enough knowledge about Xposed alpha, for example that automated install from apk is not possible and must be installed by flashing xposed zip in recovery... as long as you have framework and bridge version numbers green in xposed apk is all good
[Sony Cross-Device General] mickyw1980:
Seriously eveytime I look at this thread its over taken by errors, same questions how to install etc etc. Is it so hard to read, read and read again then follow the instructions throughout this thread. Everything you need is here, clearly written. I'm no expert and class myself a noob really, but I can read and follow instructions. Thanks mionica and ondrejvaroscak and everyone else for everything
[Sony Cross-Device General] mionica:
New release of everything

Hi guys,

News:

xposed-uninstall v1.1

removes Xposed altogether (no parts left behind :D)

removes the Xposed app

removes leakplug, leak_workaround and/or sonyfix

wipes Dalvik cache and /cache

resets XZDR settings to no-initd / enforcing SElinux

xzdr-busybox-enable v1.0 - this enables all the applets of the XZDR busybox so you won't need an installer app

xposed-leakplug v1.1 (formerly xposed-leak_workaround) - now with the same debug capabilities as sonyfix, which is now deprecated

.

Anybody who is still having

any kind of issues

, for whatever reason, please do the following:

get into TWRP;

install, in this order, without rebooting:

xposed-uninstall-v1.1.zip

xzdr-busybox-enable-v1.0.zip

xposed-sdk21-arm-20150426.zip

xposed-leakplug-v1.1.zip

(for your convenience, you'll find all 4 attached to this post)

copy the logs to the PC, over USB:

uninstall_xposed.log

install_busybox.log

install_leakplug.log

each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)

reboot to system :)

<rant target="noobs>

Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.

If you didn't do exactly like I said, and it isn't working, please ask in another thread; this one is for people who are able to follow instructions.

If you can't understand what you have to do, then this is NOT for you - please wait for the Xposed bugfix instead.

All help requests will be ignored unless they have the following files attached: uninstall_xposed.log, install_busybox.log, install_leakplug.log

</rant>
[Sony Cross-Device General] McBane87:
There are additional init.d-Scripts.

Do you have a custom ROM/Kernel installed on your device?

If so, maybe your Kernel has already init.d-Support included, which would cause this workaround to be loaded twice.

First time from XZDR and second time from Kernel. In this case you have to disable init.d-Support of XZDR.
[Sony Cross-Device General] mionica:
Ummm no. I don't know what the ric thing is, but 01SomeScript and 99SuperSUDaemon are installed by XZDR and SuperSU, respectively. And I expect there's a chance 98ric comes from an older version of XZDR.
[Sony Cross-Device General] McBane87:
Well 01SomeScript was a Dummy-File from my XZDR-Init.d-Enabler flashable. It's doing nothing. Just an example file.

And 98ric/99SuperSUDaemon I don't have in my init.d Folder if I install pure XZDR from [NUT]. Or do you mean it's from your flashable. Just didn't check the last versions yet :)
[Sony Cross-Device General] mickyw1980:
The only file I've got in init.d folder is flimit. And I've got latest xzdr installed and fully working xposed with no reboots whatsoever.
[Sony Cross-Device General] Bartekreaper:
I using RockZ1L rom, based-stock, Venkat kamesh (author) make dualrecovery from source from NUT. (Dualrecovery 2.8.12) And yes, rom has init.d support.

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] McBane87:
Then if you still having reboots/problems you should disable init.d-support of XZDR in /storage/sdcard1/XZDualRecovery/XZDR.prop

EDIT:

You have to do this every time you flash this workaround, because as far as I know, it is activating init.d support of XZDR again.
[Sony Cross-Device General] Bartekreaper:
Not needed because when I yesterday flash xposed workaround and xposed(26.04) everything is okay. No reboots and bootlop.

Wysłane z mojej Z1 compact przy użyciu Tapatalk
[Sony Cross-Device General] baha76_s:
Problem: Random reboot (always after calling and using the message app).

Procedure: Exactly as you described above.

Resulting logs: Attached with this post.

Thanks for your efforts and take your time :good: .
[Sony Cross-Device General] mionica:
Those files look good. Is this a new problem, or was it around for a while?

Oh one more thing. Would you consider flashing a prerooted 23.1.A.0.726 before going further? I've seen somebody around here reporting just recently that his Xposed problems lessened a lot when he switched to .726: here.

Also, please provide the script's boot log, it's /tmp/01_flimit.log. If you dont' have a file manager that can see that folder, get Total Commander off Play Store - that's what I'm using.

Finally, please confirm your hardware is actually D6603; I've talked to a lad who had installed D6603 firmware on a D6653...
[Sony Cross-Device General] e_mc_square:
Flash XZDR 2.8.12 again after step 5.

I believe your preroot.zip have older version of recovery.

Or always flash XZDR 2.8.12 before flashing the Xposed workaround zip
[Sony Cross-Device General] hispanico957:
Mionica i see a lot of news in your post #123 and i need, if possible, some clarification:

1- i see new file xposed-uninstall v1.1 that at this point unistall "ALL".... for the old file i can use separately, if i want for example unistall only xposed

2- last question: i unistall Busybox app (not unistall files installed) and install your release from v1 to last xposed-leakplug v1.1. So it advise install again your new file xzdr-busybox-enable ??

Thank

Hispa
[Sony Cross-Device General] e_mc_square:
Old version of XZDR might inside your preroot.zip

Flash XZDR 2.8.12 again after step 5.

I believe your preroot.zip have older version of recovery.

Or always flash XZDR 2.8.12 before flashing the Xposed workaround zip
[Sony Cross-Device General] ondrejvaroscak:
see point 3
[Sony Cross-Device General] mionica:
here, except it's #sillyquestions not #samsung.
[Sony Cross-Device General] ondrejvaroscak:
Guys, I swear I was never rude, I never wanted to be rude, but some people here simply make me. Exactly like on that picture :) That's not about being noob, but about sheer ignorance.

I tried my best, I am finished answering repeated questions. This forum has enough search and indexing functions for people to use. I simply don't have time and nerves for "kindergarten".
[Sony Cross-Device General] eskamhl:
I'm on a stock prerooted UK 23.1.A.0.726 fw and still have some random reboot here and there. I'm using the 20150308 xposed zip and xposed-leak_workaround right now, XZDR 2.8.12 and no other scripts in init.d folder ( random reboots seem even increased from the previous version :eek: today it's already happened two times ) .

It's just to inform you that those problems probably are not firmware dependent, this evening or tomorrow I'll do the "xposed-leakplug v1.1 procedure" in order to provide some logs if it still results in random reboots :good

Anyway, thank you for all :D

PS: D6603 firmware on D6603 hardware
[Sony Cross-Device General] baha76_s:
thanks for your replay.

1. this problem is around from a while.

2. my device is xperia z3 (D6603) i flashed it with a prerooted zip which i prepared myself from the original firmware of my region (switzerland), so my firmware is 23.1.A.0.690 as you see in the SS, and i didn't faced any problem even with the xposed framework (exept the bootloob with evey normal reboot) but now i never have bootloop but random reboot.

3. in my /tmp folder there is no such file (01_flimit.log) only if you means by (flimit.log) which i had and attached, and also i attached the other 3 logs in /tmp (logcat0.log, logcat1.log and dmesg.log).

4. for clarification, after i did your procedure 20 min ago, i didn't have sudden reboot til now, but i will provide you all the logs files in the /tmp folder as soos as possible during or exactly after the reboot.

thanks :good:
[Sony Cross-Device General] mionica:
What scares me is this bit:

If the thing reboots after every call or received message, that's anything but acceptable.

I'd understand 4 reboots a day if you're on Facebook, Facebook Messenger, Twitter, Skype and Spotify, with 20 Xposed modules activated and 5 email accounts set to push mode - resource exhaustion is apparently proportional with the number of app resumes. But systemathic crashes, that's different.

I suggest you switch to leakplug when you get a chance - but that's optional, since the flimit resolution hasn't changed from leak_workaround, so there will be no benefit in that respect (I did the leakplug thing to unify the useful features of sonyfix with the best-in-class workaround, already present in leak_workaround.
[Sony Cross-Device General] baha76_s:
yes i completely agree with you, and i told you before that when i installed the very early version of your masterpiece, i had about 2-3 random reboots every hours, but now i only the reboot with the massive resource manipulation by the device (call, message, installing/uninstalling apk).

by the way i never had reboot with using facebook or facebook messenger :D, and i have a device configuration like you (about 16 Xposed modules-lollipop compatible activated, 4 email accounts with push mods).

thanks
[Sony Cross-Device General] eskamhl:
For me it's not systematic but it happens usually when updating/installing apps, only three modules running but around 130 apps in data. Maybe the newest xposed zip will help, I'm not facing too many reboots ( max 4/5 in a day ) but it's frustrating eheh

I'll provide some logs as soon as I can
[Sony Cross-Device General] mionica:
2 -> Swiscomm already released 23.1.A.0.726.

However, there's two version newer than that: 23.2.A.0.278 (Telekom.de, DE), 23.1.A.0.740 (Orange - FR, PL, RO, SK, ES). I would strongly suggest you upgrade to one of these, preferably the DE version - using the same method; don't worry, they all support French, and none of the apps specific to the Swiss edition will go away (because those were copied to /data, from /system/etc/product/applications).

I should mention that I lived quite well on two PT builds, in English not Portuguese :) - one KK one LP, before LP was released for CE1 (I'm on the D6633) - so I wouldn't expect you encountered any problem.

Oh, and please use XZDR 2.8.14 instead. It's what I'm on, and it's rock stable :)

3 -> right, that the file I was looking for.

NOW. I'm not surprised you're having massive trouble; that log file is messed up pretty bad - it looks like the init file is started twice!!! see this:

[i] 01_flimit starting...
[i] =====================
[v]
[i] waiting for the zygote process to spawn...
[b][color=red][i] 01_flimit starting...[/color][/b]
[b][color=red][i] =====================[/color][/b]
[b][color=red][v] [/color][/b]
[b][color=red][i] waiting for the zygote process to spawn...[/color][/b]
[i] > found at PID after 1000ms
[i] waiting for the system_server process to spawn...
[b][color=red][i] > found at PID after 1900ms[/color][/b]
[b][color=red][i] waiting for the system_server process to spawn...[/color][/b]
[i] > found at PID 1877 after 6500ms
[v]
[d] checking for byeselinux...
[d] > already loaded
[v]
[i] seting system_server's flimits to 4096 4096
[b][color=red][i] > found at PID 1877 after 6500ms[/color][/b]
[v]
[b][color=red][v] [/color][/b]
[b][color=red][d] checking for byeselinux...[/color][/b]
[b][color=red][d] > already loaded[/color][/b]
[v]
[b][color=red][i] seting system_server's flimits to 4096 4096[/color][/b]
[b][color=red][v] [/color][/b]
[i] waiting for boot to finish...
[b][color=red][i] waiting for boot to finish...[/color][/b]
[i] > boot completed after 43s
[v]
[b][color=red][i] > boot completed after 43s[/color][/b]

So - can you tell me exactly what files do you have in /system/etc/init.d ?

We can also tell that one instance starts ~0.9s before the second - we see one waiting for 1.9s for zygote to show up, whereas the second only has 1s to wait.

Since you followed my procedure, I am sure you don't have 2 copies of that file - but check anyway.

Which leads me to assume you upgraded XZDR at least once since flashing your system :D

The most sensible course of action is to cook yourself a 23.2.A.0.278 build with SuperSU 2.46 and XZDR 2.8.14 - if you do that, your problems will be solved.

In the mean time, I'll release v1.2 of xposed-leakplug, which will prevent double-running even on your current setup (I'll require you to go through the exact procedure again - sorry about that).

PS. We're close to fixing this ;)

---------- Post added at 05:58 PM ---------- Previous post was at 05:49 PM ----------

Wait for 1.2 - I just found a problem on systems where the user manually upgraded XZDR. :)
[Sony Cross-Device General] mionica:
xposed-leakplug v1.2

It seems during an XZDR upgrade, chargemon's could get messed up - which might result in the init.d scripts running more than once.

I have modified xposed-leakplug to behave even under these circumtsances - that is, I made it refuse to start more than once.

Version 1.2 is attached.

Many thanks to [MENTION=851091]baha76_s[/MENTION] which helped me identify the problem.
[Sony Cross-Device General] baha76_s:
hi,

1. i have unlocked device so i used the (Customized CH 23.1.A.0.690), and for the upgrade, i don't know, i will think about this thing, and i don't worry about any swiss specific apps, because i don't have any.

2. I already used the XZDR v2.8.14 and yes it is rock stable and i never had problem with it (flashing, backup/restore/mounting/remounting .....etc)

3. about the flimit.log, yes i notice the double entries (double activities) in it since (xposed-sonyfix-v3.0.zip) and above.

4. in my /system/etc/init.d folder ther are 6 files:

1. 01_flimit: your file

2. 99SuperSUDaemon: from serajr super user xposed module (i think)

#!/system/bin/sh
/system/xbin/daemonsu --auto-daemon &

3. 08setperm: set permision for init.d folder from term-init script

#!/system/bin/sh
#set correct permissions to /system/etc/init.d folder
mount -o remount,rw -t auto /system
chmod -R 777 /system/etc/init.d
mount -o remount,ro -t auto /system

4. 99_at_sd_cache: set sd cache to 2048 from system tuner pro

#!/system/bin/sh
if [ ! -e /sys/block/mmcblk0/queue/read_ahead_kb ]
then
sleep 60
fi
chmod 666 /sys/block/mmcblk0/queue/read_ahead_kb
echo "2048" > /sys/block/mmcblk0/queue/read_ahead_kb
chmod 666 /sys/block/mmcblk1/queue/read_ahead_kb
echo "2048" > /sys/block/mmcblk1/queue/read_ahead_kb
chmod 666 /sys/devices/virtual/bdi/179:0/read_ahead_kb
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb

5. 99_at_io_scheduler: set sd io schedule to row from system tuner pro

#!/system/bin/sh
if [ ! -e /sys/block/mmcblk0/queue/scheduler ]
then
sleep 60
fi
chmod 666 /sys/block/mmcblk0/queue/scheduler
echo "row" > /sys/block/mmcblk0/queue/scheduler
chmod 666 /sys/block/mmcblk1/queue/scheduler
echo "row" > /sys/block/mmcblk1/queue/scheduler

6. 99_at_entropy: set entropy to 1024/2048 threshold from system tuner pro

#!/system/bin/sh
/data/data/ccc71.pmw.pro/binaries/arm/sysctl -w kernel.random.read_wakeup_threshold=1024
/data/data/ccc71.pmw.pro/binaries/arm/sysctl -w kernel.random.write_wakeup_threshold=2048

thanks
[Sony Cross-Device General] infinitylook:
Will disabling init d support on prop file help in preventing restarts? Workaround zip is stable but sometimes reboots when phone doing a lot of stuff