[Android Software/Hacking General [Developers Only]] zeppelinrox:
Hey Hey What Can I Do...

I was REALLY exhausted last night after doing nightly updates so didn't reply to anything posted yesterday so...

Yep, I blame you for jinxing it! lol

I searched your past posts... It's a strange issue with your ROM that's for sure.

It doesn't seem that your rom uses local.prop (the only values in there are the MEM and ADJ entries that I put there - the script created the local.prop)

But if they get entered into build.prop (update 9 beta 5), you get bootloops...

Maybe you can find out from your ROM's developer if there is another system file that applies MEM and ADJ values...

Of course, if you want to take the risk, you can clear dalvik cache and use U9b6's option to use build.prop instead.

Maybe you will get lucky and have it work this time.

Don't worry about the chmod /system/bin/build.prop error... I forgot the put the if/else condition on that...

btw, I think I will HAVE to use the term OOM Stick somewhere... (I do actually use the variable name oomstick lol)

edit: Oh wait I just re-read your post... you DID use build.prop?

That's VERY strange.. please post your build.prop file...

Does SuperCharging stick after reboot?

If so, just leave it alone.

If not, try changing it to match the other scripts.

I tried putting it to the more conventional 755 but had additional reports of the script not sticking while having no reports of additional successes so reverted back to 777.

With BusyBox Installer, did you try installing BB to bin or sbin instead of xbin?

If not, try that.

What do you mean by "structures?

If you're running the latest update9 beta, all the files are indeed backed up to your sdcard and you can auto restore them via menu option...

22. Re-SuperCharger!{Restore Prior V6 Settings}

The only system file modified is local.prop and/or build.prop

All other changes are made done with newly created files.

It's not a task killer... use less aggressive minfrees for better multitasking.

Disable system persistent. I dunno what prevent force close actually does. I don't think you need to apply it tho.

Hmmm... another Sensation...

Which busybox are you using?

Does 99SuperCharger get created?

Does local.prop get modified successfully?

Try the x10 forum thread... I'm sure there is a supercharger thread in there...

NICE! How much horsepower do you have on that beast?

I'm NOT a woman... I'm a MAN, man!

Oh wow... that must be the reason for so many bootloops with betas using build.prop... an empty build.prop... geez...

Important question: So, it successfully creates a backup successfully in the same location (/system/build.prop.unsuper) and yet it does NOT successfully modify build.prop, right?

If so, it's not a mounting r/w issue so that's a good thing... hmmm...

Which busybox are you using?

The build.prop that copied to the sdcard is 0 bytes because it backs up file after they are supercharged for use with option 22.

Don't worry about the "/system/bin directory error" since you don't have that file.

I'll look into that reboot thingie some more :)

Oh yeah, I imagine everything is fine if you use U9Beta6?

Ya it's good :)

Get the update that I come out with next... I'll add the /sbin thingie lol

It's ABOUT TIME somebody said that!! :D

Apart from the AWK error, everything looks ok? Does it spit out the correct bb version?

I wouldn't mind seeing the output of the entire run after you apply a setting :D

If you were to run the script that eoghan2t7 posted, that would actually be great!

But only if you don't mind being taken advantage of as a beta tester lol

I'm pretty sure there is a supercharger thread specific to the gts5570