yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] defiant07:
Tried changing maxdepth from 2 to 1 and got the same results as before - bugginess reemerges following power off/on, but not after reboots and most of the chmod and chown values are mismatched. In addition, following the power off/on I did immediately after making the 2 to 1 edit I got around 20 copy errors (cp - can't make 'blah blah package name'), but those errors never reoccurred in the subsequent several reboots and power off/on's I did to test and confirm my findings.
[Android Software/Hacking General [Developers Only]] mixednuts:
Well, if the jars weren't patched then it would make sense that the script was saying that it wasn't patched, but when I patched there were no errors, so not sure what's happened.

Did the before and after smali makes sense?
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
I face this before but maybe different patching. Im using the JAR patcher for windows.. Run the bat file to patch. All goes smooth until the end of the transferring services.jat process to the phone, I saw error on the command prompt that Java out of memory.

What I did was, download latest Java and install it. Since your phone cannot boot up due to services.jar corrupted. Do a bad flash if u dont want to lose anything. Then reboot phone.

Repeat the patching step.

Hope it help..
[Android Software/Hacking General [Developers Only]] otterbvrn:
Hi zep, I dont know what is wrong, I've got this problem since bdrc2..

I only use your mod in my phone, supercharger, kak, 3gturbo

I set detailing 4boots, fom 3.5hr, fixa on boot, bulletproof 30mins, kernel rock hard...

Both (bdrc and beast) are going well for couple days, after that, something happens...

My phone keeps rebooting, after unlocking sim pin, less than a minute, all my app, even system app force close, then reboot...

If I do not enter the pin, in less than 5mins, my phone reboots

And I tried to power off/reboot recovery after unlocking pin, didnt work, phone keeps rebooting

I can access recovery by adb

And my method is backing up current rom, full wiping (except sdcard), restoring my backup, then fixing permission by tool recovery

Can you identify what's the matter?

I dont know how these things happen, cause all the matters (on bdrc and beast) happened when I left my phone charging and I took a sleep...

Do I have to turn off the fixa?

Thankyou so much
[Android Software/Hacking General [Developers Only]] zeppelinrox:
ok those numbers are right.

I'll debug that false alarm.

Try with no spaces in folder names.

Do you mean it happens with RC11 too? Even tho RC11 used to be fine?

put this in terminal: $((`free | awk '/Mem:/{print $2}'`/1024))

I think that's giving you the error... but I dunno why, really.

You can try $((`free | awk '/Mem/{print $2}'`/1024))

(without the colon)

Actually, also do ls -l `which sh`

All I meant was that I don't think I have to use my own busybox compile since it's not that hard to make commands compatible across all busybox builds.

I used that stat applet as an example - it has fewer options/switches available if not compiled in desktop mode.

Same goes for the ps applet.

Having said that, most of the time, I find that the code that you come up with to be overly convoluted.

If I wanted to put a certain folder first in the $PATH, I'd just put it in there - it don't matter if, for example, /system/xbin is in there twice.

Like so:

PATH=$(dirname `which busybox`):$PATH

The result...

# echo $PATH
echo $PATH
/sbin:/system/sbin:/system/bin:/system/xbin
# PATH=$(dirname `which busybox`):$PATH
PATH=$(dirname `which busybox`):$PATH
# echo $PATH
echo $PATH
/system/xbin:/sbin:/system/sbin:/system/bin:/system/xbin

But... say you don't want it in there twice... do:

PATH=$(echo $(dirname `which busybox`):$PATH | sed 's@:'$(dirname `which busybox`)'@@g')

The result...

# echo $PATH
echo $PATH
/sbin:/system/sbin:/system/bin[COLOR=Red]:/system/xbin[/COLOR]
# PATH=$(echo $(dirname `which busybox`):$PATH | sed 's@:'$(dirname `which busybox`)'@@g')
PATH=$(echo $(dirname `which busybox`):$PATH | sed 's@:'$(dirname `which busybox`)'@@g')
# echo $PATH
echo $PATH
[COLOR=Red]/system/xbin[/COLOR]:/sbin:/system/sbin:/system/bin

How's that work?

Well, if you're looking for /system/xbin or whatever and it isn't first in the PATH, it will have a colon ( : ) in front of it... so just delete :/blah/blah after putting /blah/blah: in front of $PATH ;)

Well, the previous changes would still be in effect since changing maxdepth to 1 will not bother to look at a depth of 2.

So to kill a few birds with one stone, I'm gonna change this:

busybox find $file -type f -maxdepth 2 ! -perm $PERM -exec chmod $PERM {} ';'
busybox find $file -type f -maxdepth 1 ! -user $NEWID -exec chown $NEWID {} ';'
busybox find $file -type f -maxdepth 1 ! -group $NEWID -exec chown :$NEWID {} ';'

To this:

for i in $file/*; do Get_PWN $i
if [ "$PWN" != "$NEWID $NEWID $PERM" ]; then apply_permissions $NEWID $NEWID $PERM $i; fi
done

No need to worry about spaces in folder names when not going 2 levels deep and no need to worry about chown syntax.

Havent had a chance to look yet.

Any chance you got a logcat?

But ya see if its fine without fixA and fixE for now until next version.
[Android Software/Hacking General [Developers Only]] hoholee12:
damn, i forgot to use that command, thanks for reminding me.

and, yeah its true that i make it complicated because im still a noob at bash commands.

i guess ill have to go back to teh basics again lol:p
[Android Software/Hacking General [Developers Only]] huseinn:
Auto re-generate script case closed by unsupercharging, delete the whole V6 folder, and supercharge from zero ------ ehehehe :silly:

but the "fentropy enforcer NOT in effect" still there.... :rolleyes:

:highfive::laugh:
[Android Software/Hacking General [Developers Only]] hoholee12:
Personally i think using things like zipalign always somehow causes trouble.

Me? i just stick with the temporary tweaks that never touches my precious apps.
[Android Software/Hacking General [Developers Only]] otterbvrn:
No... I just have less than a minute before it keeps rebooting after unlocking pin

Okay... will try only zipalign, and monitor for couple days
[Android Software/Hacking General [Developers Only]] zgmfx20:
hi zepp

your latest script works fine after 1st zipalign on boot. But every after reboot some apps like superSU had it's settings reset,

Just a while ago I wiped cache and dalvik cache. Now all apps force closes.

deleting fixalign.sh in init.d and fixing permissions in recovery didn't fixed my problems.

Restored from backup. I think I need to go back to bdrc2. :crying:

I didn't face any problem even zipalign in bdrc2.
[Android Software/Hacking General [Developers Only]] Najuto9tail:
Xperia Ion Super Charged! :D
[Android Software/Hacking General [Developers Only]] khan.orak:
I already have busybox but 1.20. Will flashing the BusyBox 1.9 replace the older one?

Also can I flash this through TWRP recovery instead of CWM?
[Android Software/Hacking General [Developers Only]] defiant07:
By previous changes do you mean those instituted by prior runs of fixA? If so, I had turned off fixA before trying the maxdepth edit and things were functioning normally. Therefore, it seems any changes made by previous runs of fixA had been undone. Turning fixA off and rebooting more or less resets things to an untouched state right?

At any rate, I tried replacing those three lines with the new code and there is still quite a bit of bugginess. There are a lot of stat errors and blank 'was' values; I attached the log should it be of interest.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
when I started using dirname and basename it almost felt like cheating because it makes it so much easier :p

But the main thing is to see if there is any way to get to the point faster.

do:

stat /dev/*random*

I don't mind trying to make existing boot scripts faster/better/smarter.

So far there hasn't been any apps missing with the latest zepalign - which won't slow down boot and only looks at apps that have been recently installed while reapplying the originals permissions to the zipaligned one.

OK.

I'm not sure that its caused by fixA since its fine for a couple of days.

Post the Ran* file tho.

just wiping caches has caused that for some users in the past so it may be that.

Try and see.

Tho 1.20 is newer than 1.19

damn.

Forgot to check if $i exists (ie. the folder is not empty)

Try:

for i in $file/*; do
if [ -f "$i" ]; then Get_PWN $i
if [ "$PWN" != "$NEWID $NEWID $PERM" ]; then apply_permissions $NEWID $NEWID $PERM $i; fi
fi
done

also run this command:

mount | grep asec
[Android Software/Hacking General [Developers Only]] Jettubby:
Thanks for the help. :confused:
[Android Software/Hacking General [Developers Only]] defiant07:
Still buggy...tried clearing data and cache and did multiple reboots and power on/off...second chown values and chmod values mismatched.

Attached command output and bootlog.
[Android Software/Hacking General [Developers Only]] hisname:
I am back zep! whew finally settled my personal matters and some other crappy stuff. will test the script after I flash the leaked 4.3 rom:p. I wonder will supercharger still work... I will be the first to report :D

edit:bleh, leaked version of Android doesn't like to see /system/xbin/su. gives me bootloop whenever I inject superuser binary. can't test for ya
[Android Software/Hacking General [Developers Only]] huseinn:
finish... screenshot here :)
[Android Software/Hacking General [Developers Only]] thewaywardgeek013:
Hi zep, thanks for your work on this wonderful script! I've been using it on my GB Devices and they feel so good! Anyways just upgraded to a JB Rom(CM Jellytime R30 for DHD), and tried patching the services.jar Ultimatically, but to no avail, so I opted to follow the "MANUAL" Way of patching the services.jar (STEP 6), but there seems to be something missing because I also checked your Patcher and there are added entries in there that I can't quite follow so just want to ask if there is an Updated Manual Way of patching the Services.jar ;)
[Android Software/Hacking General [Developers Only]] mixednuts:
OK... let me know if there's anything else you need. Although, considering the million attachments I provided in my initial post regarding the issue, you probably have everything you're looking for :p

Now I gotta figure out why my LG Optimus Black (p970) lags after I run SuperCharger... especially after running Chrome using WiFi. Lower minfrees on slot 3, perhaps? :o
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Actually, not all of them are the same and are supposed to be mismatched - those in app-data and asec apps.

The permissions of your asec apps seem to be way too high too.

I don't think they can be changed tho since they aren't on an ext partition (vfat file system).

If the rom is rooted, wouldn't it already have su?

Post the 4.3 services.jar tho.... heh

Not in effect.

Did 99SuperCharger run on boot?

Should be /data/Ran* and if you have init.d support, /data/BootLog* files too.

What the hell does "no avail" mean?

Use latest ultimatic and in offline mode if need be.

Try different settings.

Did you enable 3G TurboCharger Enhancement?
[Android Software/Hacking General [Developers Only]] hisname:
nope the rom can't be rooted.blocked it in their kernel. say please and I might consider posting it:

edit:bleh I have access to adb shell, can the script run? if so how?

edit: I am having a bunch of error. even though my rom is a stock Google experience rom, its running a custom touchwiz kernel(funny eh?) .AOSP rom with touchwiz kernel. anyway... my custom kernel has init. d support, but how come supercharger tells me that it can't be loaded on boot. I am also using busybox 1.22

edit:WTF??!! how come there is a negative number in FOM??
[Android Software/Hacking General [Developers Only]] zeppelinrox:
And why on earth would you think anything could possibly work if its not rooted?

Until then, you're SOL.

Oh about FOM... When increasing one thing, another thing goes down.

Like a seesaw.
[Android Software/Hacking General [Developers Only]] hisname:
no, actually you misunderstood me, I am running 4.2.2 Google experience rom now, not 4.3 and no there are no missing apps, so that's good news?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Ah.

Well there is no init.d folder that's why v6 says that you saint have init.d working

Create an init.d folder, reboot, try again.

Maybe the reboot will help with the read only errors.

FYI if you see read only errors.. Expect lots of other errors.
[Android Software/Hacking General [Developers Only]] Lord_Flaya:
Hi all. First of thx to zep for this great work. :) I've used this since GB and always been pleased. Now running CM10 4.1.2 and after hours

Searching for a solution i decided to post for help. It seems i cant patch using ultimatic jar patching. I run win7 with java installed. Also have adk and sdk. The patcher starts bit after starting daemon it halts. It sits there for ever but nothing happens. Anyone know what it might be? I have usb debugging on and charge only set. My phone is a moto defy red mb525 red lense. Thx in advance. :)
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Which ultimatic version?

Try with latest and if it still hangs just do offline mode and install it manually or with jelly iscream parlor
[Android Software/Hacking General [Developers Only]] hisname:
this is a zip file, you have to unzip it.
[Android Software/Hacking General [Developers Only]] Lord_Flaya:
I run the latest version. Will try the file from hisname and report back. :)
[Android Software/Hacking General [Developers Only]] eushaun99:
Lol I think that was for zep.
[Android Software/Hacking General [Developers Only]] defiant07:
Yeah, I thought the values were mismatched in earlier versions of fixA, but was not a 100% sure as I never spent much time looking at those logs since I did not have any issues.

I am kinda confused regarding the relevance of asec apps being that none of the asec apps were being buggy...the problem apps (e.g. Icon Themer and full!screen+) are totally on my internal storage (/data/app).

But I guess my big question is: will my device likely no longer be compatible with fixA in future updates of V6?

Am I the only one still having issues with fixA? [MENTION=5113073]eushaun99[/MENTION] - I am curious did any bugginess reemerge for you following the busybox edit and clearing data?
[Android Software/Hacking General [Developers Only]] Lord_Flaya:
Tried with the file from hisname, but no luck. Now the phone goes to cyanogenmod bootanimation and no more. :( Oh, anyway.. I start from scratch, and hopefully i make it work someday. :P
[Android Software/Hacking General [Developers Only]] eushaun99:
Actually I did not have any bugginess issues with any apps except SuperSU. It keeps prompting me even though I set it to always allow. Other than that, nothing, just fixA script showing the chown thingie. Anyway, I just flashed a new ROM so I'm not using supercharger currently. Too scared to run fixA lol.
[Android Software/Hacking General [Developers Only]] hisname:
THAT WAS NOT MEANT FOR YOU!! IT'S FROM ANDROID 4.3,IT WILL NEVER WORK ON YOUR DEVICE. PLEASE READ THE POST CAREFULLY!
[Android Software/Hacking General [Developers Only]] Lord_Flaya:
My bad.. :P Tired from 36h work pass.. hehe no harm, no fault.. :P not that big of a deal to reflash since I have nothing on that defy anyways.. that's the benefit of having 2.. ;)

Edit: Got it working. :) Problem turned out to be me choosing to run as root. Lol :p now it is working fine. :)
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Should be fine in future. I think the bugginess has to be from the busybox find maxdepth 2 thing and spaces in folder names 2 levels down.

Both things are covered in the changes you made to FixA.

What if you just reinstall those buggy apps?

btw did SuperSu act buggy?

oh... and asec apps were uneffected anyway :p They were all mounted read/only as shown by your mount | grep asec output and I hadn't mounted all those read/write.

Even if I had remounted r/w, permissions can't be set because they're on a vfat filesystem.

Permissions can only be changed if apps are on a ext partition.

You know that the other boot scripts like zipalign/fixE/fixA/vac aren't actually part of supercharging, and are optional, right?

ah so on the same rom, NOT choosing to run as root was the solution for you?
[Android Software/Hacking General [Developers Only]] mixednuts:
Always run 3G TC ... I guess you referring to WiFi Afterburner, right?

EDIT: Actually, running stock, not sure how helpfull WiFi Afterburner would be.
[Android Software/Hacking General [Developers Only]] defiant07:
Good to know.

If I recall correctly, SuperSU seemed okay with the busybox and maxdepth edits, but would be really slow in granting permissions sometimes and give me constant toasts sometimes like eushaun99 previously mentioned with both versions of BD6 and the two edits where the three problematic lines of code were replaced.

I will try turning on the revised fixA and uninstalling/reinstalling the problem apps :fingers-crossed:.
[Android Software/Hacking General [Developers Only]] 1droidmod:
"@WHOEVER-KNOWS-FOR-SURE!!!"

So i used my Terminal Emulator app for this and dang thing went off with out a hitch... shi%n scripts patched my service.jar too "which I was not expecting" Fantastic Job putting this together... Although Iam NOT sure if this is appropriate for this ROM? YES/NO?? I Tried this out of bord-um-ness... I do recall v6 in some 4.0.4 ROMS I flashed back in the day, I think?? So benefit or Not?? Thãnks-

XT912 CDMA PAC-man05 4.2.2
[Android Software/Hacking General [Developers Only]] eushaun99:
I know, its just that when I run v6, I want to run all the options together. Plus I'm too lazy :p

Apparently my ROM is starting to slow down. Guess I have to supercharge soon.
[Android Software/Hacking General [Developers Only]] mixednuts:
Definitely true for Detailing and Fixalign :p
[Android Software/Hacking General [Developers Only]] zeppelinrox:
I was referring to the V6 option.

Oh forgot to mention.

Seems like you have both free and pro supersu apps... Maybe they're wrestling to grant su permissions?

Been tweaking the fixA, fixE and zepalign scripts - bug hunt and better asec compatibility (won't bother with asec if those apps are on a vfat filesystem)

nobody knows for sure what you're talking about.

But feel free to be a guinea pig since you're bordumed.

hey at least detailing is totally bug free :) uh... did I just jinx it...
[Android Software/Hacking General [Developers Only]] 1droidmod:
[MENTION=3357461]zeppelinrox[/MENTION]...**PIG still has a pulse indeed... Experimenting is what Iam doing as I have reached a point "Frustration" with my DROID RAZR XT912 CDMA... OP states clearly "It works on all android devices-Custom Roms or Stock Roms, Phones or Tablets, it doesn't matter.." What i was getting at is, Sure this works on all Android devices but will this always be more effective in a positive way on all Android devices and Custom Roms, Custom Kernels, as many tweaks have been implemented in Custom Roms, Kernels!! I Currently do NOT have Anything on my device posted in OP... Do You recommend An app or what not (please) i can use as far as without/with OP mods to gauge/compare/evaluate effectiveness? No Iam NOT Trying to be smart with you or test your patients, I just want what everybody wants, fast, smooth, responsive, reliable device.. Ty**

XT912 CDMA PAC-man05
[Android Software/Hacking General [Developers Only]] hisname:
so.... zep, is there any changes in android 4.3 services.jar?
[Android Software/Hacking General [Developers Only]] huseinn:
yap, double check both files, and confirm my init.d support working, even after using " su -c 99super " fentropy still not in effect :rolleyes:

:D:highfive:
[Android Software/Hacking General [Developers Only]] defiant07:
Naw, that's just the way SuperSU is...you have to install the free apk and an unlocker apk, which enables the pro features like logging and you need to keep the unlocker installed.

Dunno if it is pertinent information, but I did a reboot and power on/off with only turning on the revised fixA (i.e. without un/reinstall of apps) just out of curiosity and I noticed SuperSU's logging function was broken.

So I uninstalled and reinstalled the most noticeable problem apps (SuperSU, Icon Themer, and full!screen) and bugs were reincarnated :(. It was strange the bugs came back kinda incrementally :confused: - at first it was Icon Themer being inconsistent and by the fourth reboot/power on/off many of the same bugs had come back: fullscreen not enabling on boot, SuperSU logging broke, icons not sticking anywhere. Thanks for the suggestion anyway.

If I am the only one having issues, feel free to forget about me...damn random tablet. I am happy with BDrc2, but will still test future releases or suggestions and let you know the results ;).
[Android Software/Hacking General [Developers Only]] Lord_Flaya:
Yes. And now my defy is flying a mile high. :)
[Android Software/Hacking General [Developers Only]] mixednuts:
D'you even need to ask... of course I have to 3g tweaks enabled in V6 lol

Actually, I did try SuperCharging with all other tweaks disabled and the lag still persisted with SuperMinFree calculated values.

Just to clarify... the lag issue is with my LG Optimus Black (p970) running stock ICS. The patching problem I mentioned a little while back, with all the attachments, is with my Acer a500 running CM10... which I suspect is a kernel issue as you pointed out some time ago with earlier releases of ROM from the same developer (damn shame).
[Android Software/Hacking General [Developers Only]] zeppelinrox:
evaluate?

DIY

I provide the poll with results for all to see.

dunno yet.

This black dog has bitten me in the ass so been fiddling with the boot scripts.

post the bootlog.

try installing supsu as system app?

try different minfrees.

Some report better results with lower minfrees.
[Android Software/Hacking General [Developers Only]] defiant07:
Negative. Similar results as prior test - first reboot following turning on fixA Icon Themer was inconsistent and then after a power off/on the rest of the previously mentioned bugs resurfaced.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
OK post the logs.

I'll probably put in an exception for superau
[Android Software/Hacking General [Developers Only]] defiant07:
Attached the logs.

Sorry if this is trivial and a bit verbose, but I found it exceedingly bizarre and I think it may hold a clue as to why the new version of fixA dislikes SuperSU.

I had turned off fixA following the previous test and did not save the logs. So obviously I had to turn it back on in order to recreate the logs and upon rebooting following enabling fixA immediately after unlock I was greeted with a superuser permission dialog for init (yes that's right, init, the boot program)! Never had that happen before...never even read about something like that. It caught me a bit off guard and I granted the permission. I did some tinkering around with root explorer and terminal. I then opened SuperSU and it's logs were working. So next I had SuperSU 'forget' the permission. Did some more root tinkering and logging was broken again...I wish I had saved the logs and done a logcat, but I was bewildered and not thinking. I then did power off/on and all the bugs were back, but I did not get an init superuser request - the attached logs are from this boot process.
[Android Software/Hacking General [Developers Only]] mixednuts:
Read up on the material, but just wanna make sure - lower the minfrees of slot 3, right?