Database Develop

The superb SuperHero Mass (wifi problem)

Hi all,
I installed the SuperHero V3 Mas in my G2 (magic 32b) and it run so good and faster than all of others roms that I have tried. The problem that is the wifi cant turn on (it's normal this rom is made for G1).
Someone can help me to solve this problem and make this rom able to all G2 users.

The trick is to get and push the working wlan.ko (I think its in the sperhero 3 thread already) now why don't you tell me the trick you did to make this the fastest so I can try it

try pulling the wlan.ko file from a magic rom and pushing it through adb to /system/lib/modules, and im guessing its the fastest because he might have the magic that has the 288mb ram instead of 192, so virtually identical to the hero.

thank you for your response, I will try this right now

Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root

co2gaz said:
Thas is not work
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
I tried to change file access using chmod and I go this message:
failed to copy 'wlan.ko' to '/system/lib/modules/wlan.ko': Read-only file system
please help
Ps: adbd is already running as root
Click to expand...
Click to collapse
Try "adb remount" to mount /system as writeable.

Thank you for this information.
I tried it. the copy work OK, but the wifi problem steel here

I should have been more clear because pulling the file from any Rom isn't how you go about it. It has to match the kernel you are on and often even be further modified to the build. I think I heard either the wlan from superhero2 or the one from an earlier jachero worked. I just forget what one. Give me some time ill upload it. I had fixed and re-released this build.
Edit: Wlan.ko attatched. Belongs in system/lib/modiules

I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work

Hi, I tried with JCAHero and it's same, very great rom, run so good on my magic G2, but the wifi not work

co2gaz said:
I thank you so math for your help,
I putted the file in my phone and i restart it, but wifi steel not work
Click to expand...
Click to collapse
Use the one I posted in this thread. I edited the post above ya. It should work then.

Thank you, I putted the new wlan.ko on my phone. now it seems better but it not work, now when I want to start wifi it show wifi is turning on during 4 or 5 sec, after that it show unable to start wifi.
if it was some link to explain how I can modify wlan.ko, maybe I can do some things (I'm java developer and I think it's native kernel file)

2.2.1 Update error

hey boys
so I finally gave it and did the whole adb rooting thing... lots of command lines and so on but finally it works so I got rid of Universal Androot..
so now my problem is still there though...
I run the update.zip and I get this:
assert failed: apply_patch_check(“system/app/GenieWidget.apk”,”(insert tons of digits here″,”(insert tons of digits here)″)
“E: Error /sdcard/update.zip
(Status 7)
Installation aborted.”
Anybody got a solution?
My phone and its changes:
Stock Nexus One 2.2
Rooted word-per-word via http://forum.xda-developers.com/showthread.php?t=736271
Uninstalled Amazon MP3 and "News & Weather" (genie widget?)
I figure maybe reinstalling News & Weather would fix it ... but Titanium backup does not recover it even if I did back it up first... (useless??)
I downloaded the APK and instaled it, but still the same thing.
What else what else...
thanks

I'm only posting this here because I, too, have an error and am in no way trying to thread-jack. I got the 2.2.1 OTA the other day and went ahead to update. Unfortunately, I use AndRoot also and when I got halfway through the OTA, I got an error during installation. I pulled the battery, rebooted, and I was still 2.2 rooted. I unrooted with AndRoot and now seemingly have no way of acquiring the update OTA. Any advice, OP?

OTA seems absolutely random to me ... so I would download the update (found in this very forum) and rename it to update.zip and put it in the root of your sd card and run the update as prescribed on many sites...
as for my problem... damnit damnit damnit is all I can say. I know 2.2.1 is generally useless, but I want to be sure I can install Gingerbread when it comes out!!

damn so I tried 2 different versions of GenieWidget installations (it's news and weather)
seems I get the same error everytime.
I know the "simplest" thing is to run a full reinstall of my phone (recover console?) but I don't want to redo all my apps/settings... can't there be a way to recover 1 or 2 components only? in this case, amazon mp3 and geniewidget, just so that the 2.2.1 update works...?

I had the same issue with com.amazon.mp3.apk not being found (I remember deleting it as soon as I got root)... well I had to put it back under /system/app/ (meaning you can't do it via the market - only manually)
Note: the exact version that was shipped with froyo has to be installed. You can check that you have the right apk by computing its sha1 sum (that's the second "insert tons of digits here" MitchRapp refers to)

*UPDATE*
oh snap.
my friend has the same nexus one as me ... so I copied his GenieWidget.apk and .odex into my /system/app and so far so good... i got another error (com.amazon.mp3) so I'm going to copy that too
update to follow...

hey it worked!
after a (seemingly) endless "X" animation bootup... 2.2.1 is there.
now I lost the root access I just made with adb shell something something.... that's normal I guess, so I'll redo it

Uh oh, I removed amazon mp3 too...;(

toss the .apk back in /system/app and reboot and update... it worked!
now for re-rooting... that wont work damnit.
I'm doing the rageagainstthecage thing word-for-word and the thing is, when I try
./busybox cp busybox etc...
it says file already exists
and the chmod commands only give me a "read-only" error
cuz I already rooted earlier using the .freenexus style .......
what can I do for this?

Anyone happen to have the2.2 Amazon apk and willing to share?
Sent from my Nexus One using XDA App

I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...

bennettm89 said:
Anyone happen to have the2.2 Amazon apk and willing to share?
Click to expand...
Click to collapse
Sure.
sha1sum is c3b285c13db4b7f8fcfb72372d77b388157bf6cd

MitchRapp said:
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
I used superboot (1.1-FRF91-nexusone-superboot) - worked like a charm.

I had an issue with settings.apk , had used universal androot and metamorph to make changes to the battery meter.
After getting the ota , the installation was aborted due to changes in settings.apk . i downgraded to android 2.1 erd79 ( had the passimg.zip file from few months ago).
Once downgraded never got OTA for further updates ( eg ere27 , frf91 etc).
had to manually update to frg83.

Jony, Thank you.
OP, thank you anyway, I got it from Jony. Now to find the update.zip...

God bless it. Went to go install from SD, I don't have twitter. I hate twitter. Anyone have it...

MitchRapp said:
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
The rageagainstthecage step-by-step is missing a couple steps that will cause it to give the errors you're seeing. I ran into this and posted the solution, with follow-up and confirmation by others, later in the thread. Check out
http://forum.xda-developers.com/showthread.php?t=792016
In a nutshell, the /system partition needs to be mounted for both read and write in order to set permissions on the Superuser.apk and su files. Also, if you already were rooted and have Superuser.apk, su, and busybox installed, you don't have to copy them back to the phone--you can just set the permissions on the existing files.

Ohhhh jony! Can you post the twitter APK pl0x

bennettm89 said:
Now to find the update.zip...
Click to expand...
Click to collapse
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
bennettm89 said:
Ohhhh jony! Can you post the twitter APK pl0x
Click to expand...
Click to collapse
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113

jony22 said:
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
Click to expand...
Click to collapse
Thanks buddy, I appreciate it.
I'm not really happy with the update. Lost root ( I knew I would ) but the most upsetting thing is that I removed my work email from my phone. I had to update security settings to authorize the remote administration of my device through my exchange server at our HQ which is not happening. I know it doesn't have to be done but I was getting increasingly angry just looking at it in the notification bar 24/7.

Never mind. I'm going to do it the hard way. :) Mods please close. Thank you.

I need help from you genius developers. I'm 99% done porting a rom over to release it here. I'm having issues with changing Phone.apk. I did the following:
1) Decompiled Phone.apk with apktool
2) Modified the manifest to add the permission I needed to add
3) Compiled it with apktool
4) Used 7zip to put my new manifest into the original apk
5) Used 7zip to put my new apk into the rom's zip
6) Flashed it and immediately after boot, got FC's on com.android.phone because it says the signature doesn't match the previously installed version and it will be ignored.
I found that if I place my modified Phone.apk on the sdcard, install the cpts binary (copies and retains the destination timestamp) in /system/xbin and set perms, I can do this:
Code:
adb remount
adb shell
# cpts /sdcard/Phone.apk /system/app/Phone.apk
I'll get this output and it'll work fine:
Code:
cpts /sdcard/Phone.apk /system/app/Phone.apk
Original ts:1290546488
Allocated 8388608 bytes.
But if I try to pull it from the phone, stick it back in the rom zip, it won't work when flashed clean.
I've beaten my head against the wall with this and any help will be appreciated.
TIA!

I think this needs to go in Q/A, since it's a question.
J/k. Have you tried Apk Manager 4.9? I've used it to mess with system apk's and data apk's, and it has options for both, which it handles differently.

PonsAsinorem said:
I think this needs to go in Q/A, since it's a question.
J/k. Have you tried Apk Manager 4.9? I've used it to mess with system apk's and data apk's, and it has options for both, which it handles differently.
Click to expand...
Click to collapse
LOL! I tried Apk Manager first and it wouldn't even decompile it without giving me errors.
I'll add some screenshots of what I've got so far. Maybe it will motivate someone to help!

Signatures aren't matching with what was previously installed.
Basically what you're doing is this:
Stock-Phone.apk has signature=1. (for example)
Your-Phone.apk has signature=2.
When you "hot-swap" them, it goes something like this:
Android: Hey, Stock-Phone.apk, what's your signature?
Stock-Phone.apk: It's numba 1, like me!
Android: Cool cool, *writes down. Go ahead and run!
*hot-swap here
Android: Hey, Your-Phone.apk! *looks at paper, ah, I have it written down! Your signature is 1, go ahead.
Your-Phone.apk: Hee hee!​
Your-Phone.apk will use the cached signature to pretend like its signature=1.
However, putting it in a zip and flashing clean will not allow Android to cache any signatures. So Your-Phone.apk will read signature=2, and fail.
It'll go something like this:
Android: Hey, Your-Phone.apk, what's your signature?
Your-Phone.apk: 2!
Android: Sorry man, we only allow 1s in here, no execution for you!
Your-Phone.apk: FC FC FC FC FC!​
I could never solve this problem without a two-zip flash and a full boot in-between, but some other devs might've managed to solve it.
PS I hope you enjoyed that analogy! xD

gmichaelow said:
Signatures aren't matching with what was previously installed.
Basically what you're doing is this:
Stock-Phone.apk has signature=1. (for example)
Your-Phone.apk has signature=2.
When you "hot-swap" them, it goes something like this:
Android: Hey, Stock-Phone.apk, what's your signature?
Stock-Phone.apk: It's numba 1, like me!
Android: Cool cool, *writes down. Go ahead and run!
*hot-swap here
Android: Hey, Your-Phone.apk! *looks at paper, ah, I have it written down! Your signature is 1, go ahead.
Your-Phone.apk: Hee hee!​
Your-Phone.apk will use the cached signature to pretend like its signature=1.
However, putting it in a zip and flashing clean will not allow Android to cache any signatures. So Your-Phone.apk will read signature=2, and fail.
It'll go something like this:
Android: Hey, Your-Phone.apk, what's your signature?
Your-Phone.apk: 2!
Android: Sorry man, we only allow 1s in here, no execution for you!
Your-Phone.apk: FC FC FC FC FC!​
I could never solve this problem without a two-zip flash and a full boot in-between, but some other devs might've managed to solve it.
PS I hope you enjoyed that analogy! xD
Click to expand...
Click to collapse
I DID enjoy the analogy! Thanks G! That makes perfect sense. I tried signing it myself with testsign.jar and it still didn't match the original. I may have to try the two-zip flash method.

have you tried playing with the one that inc does ported over?
the only thing that didnt work was wifi. if i remember correctly.

wes342 said:
have you tried playing with the one that inc does ported over?
the only thing that didnt work was wifi. if i remember correctly.
Click to expand...
Click to collapse
Thanks for the reply Wes. Yes, I tried using his Phone.apk file and it was missing the same permission. His port had more issues, like not being able to hang the phone up. So far, this is the last thing not working in my port.
Without this permission, when u get an incoming call, while the screen is off, the phone can't unlock the screen.
EDIT: And reading internal memory isn't working, but I'm not worried about that yet. It's 5:50am and time to go to work for me. I think I just needed some sleep as I spent too many hours on this last night. Today's a NEW day!

That's a pretty nice looking rom. Yea I gave you a bump because I like the lock screen.
Sent from my Incredible using XDA App

Gahh Its Lee said:
That's a pretty nice looking rom. Yea I gave you a bump because I like the lock screen.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Thanks Gahh! It's real fluid at unlocking too.

No need to bump this anymore. I'm going to bite the bullet and set up a proper kitchen and see if it'll make this easier.
Thanks for all of the responses..

[SCRIPT] Soft Brick Recovery

For Windows users, I've created a script based on designgear's thread on steps for recovery from a soft brick.
designgear's original thread on soft brick recovery:
http://forum.xda-developers.com/showthread.php?t=966405
-----
This script is all-inclusive. It will temp. root (no need to use SuperOneClick), create a /data/recovery folder, push services.jar, framework.jar, and framework-res.apk to the /data/recovery folder, and then copy them to /system/framework
Instructions:
USB debugging needs to be ON.
Unpackage the .7z archive
Execute "Run Me - Atrix Soft Brick Recovery"
Let the script run, and wait for the phone to reboot.
(Reboot might take a few moments, leave your phone alone and wait it out!)
Download:
Temporarily Removed. Will return soon...
Thanks go out to:
designgears
PAulyh0ffman
YellowGTO
Standard disclaimer...,yada yada yada, Use this at your own risk.

nice work, ill be a little for adventurous with snooping around the /system and trying to get rid of motoblur.

Good job, hope i won't need it

Awesome work. If this is not stickied, moderator please do so. I thank everyone involved. DG, I'm sorry to see you go. I thank you for your involvement thus far and any future help you contribute.
Sent from my MB860 using XDA App

added to the sticky

How do i use it, if my phone is stuck in the "M" screen?
Tried to run while in Early USB enumeration - didn't work.
Any other option from recovery / fast boot / SRD - that may work to un-brick?
Thanks in advance

The best way I can figure is to force the phone out from the moto screen. Put the phone into early usb enumeration. using Adeo0.7z click install as soon as the phone mounts. That got my phone to boot up yesterday. Once you hit the power button, to lock or turn off, reboot. It'll just go back to the moto screen and hang.
Sent from my MB860 using XDA App

tomerbn said:
How do i use it, if my phone is stuck in the "M" screen?
Tried to run while in Early USB enumeration - didn't work.
Any other option from recovery / fast boot / SRD - that may work to un-brick?
Thanks in advance
Click to expand...
Click to collapse
It looks like I'm having a problem with the shell root.
---
Use this temporary solution (which utilizes SuperOneClick), until I can get a chance to fix things.
1. Download SuperOneClick from shortfuse's site: http://www.shortfuse.org/
2. Download my temp script, and unpack
3. Unpackage and run SuperOneClick
4. Boot the Atrix into FastBoot, and enable Early USB enumeration
5. When you see "Reading ODM fuse: 1", plug your phone into the computer and run Shell Root with SuperOneClick
6. Once rooted, run the temp script "Run Me - Atrix Soft Brick No Root"
Your phone will boot into Android, and then reboot. Leave things alone until that reboot happens, and you no longer have the blinking red light.
Download:
Temporarily Removed. Will return soon...
Sorry 'bout this, I hope to get my original script fixed asap.

I used this script because I wanted my stock notification bar back so I used it. However I followed the instructions from the previous post and it still gave me a boot loop. I figured out that there was something with the services.jar and the framework.jar in the 7z file because I used those files the manual way and it still looped. So i replaced those files with these here http://hotfile.com/dl/108780455/13cd9f6/recoveryfiles.zip.html and it worked!

I just checked both scripts, and MD5 is verified against retail dump:
Blur_Version.4.1.26.MB860.ATT.en.US
If you pushed a different working file, can you send it to me so I can look at? I've ran pushed these framework files multiple times to my phone now.
Thanks,

olieebur said:
I used this script because I wanted my stock notification bar back so I used it. However I followed the instructions from the previous post and it still gave me a boot loop. I figured out that there was something with the services.jar and the framework.jar in the 7z file because I used those files the manual way and it still looped. So i replaced those files with these here http://hotfile.com/dl/108780455/13cd9f6/recoveryfiles.zip.html and it worked!
Click to expand...
Click to collapse
MD5 from my phone & Odexed Retail Dump
Framework:
9E59AA29AD0C068B52D966BF7F82F8DE
Framework-res.apk
8DA2B8AFE971C23E65C94B316BFEAFDD
Services.jar
5AD492B7C1B82A10ECA2A406FE4C8A70
Yours
Framework:
CE777AA13FEBE9B7438D99A045D93335
Framework-res.apk
8DA2B8AFE971C23E65C94B316BFEAFDD
Services.jar
5AD492B7C1B82A10ECA2A406FE4C8A70
Is there anything special with your phone that you've done?
EDIT:
I've redownloaded the Odexed retail dumped, and checked my files again & they match.
http://ponack.net/designgears/atrix/dumps/

Turns out the services.jar was fine. The framework seemed to be the problem. The only thing that didn't match was the framework Don't think I did anything different to my phone.
Sent from my MB860 using XDA App

Just pulled both downloads for now until I can look into this. Like I had mentioned before, my framework.jar matches the retail dump...? Going to collect some other framework.jar and see what I can find...

How do you turn on debugging? My .7z is Chrome7z. Is this sufficient? Where do I go to execute "Run Me - Atrix Soft Brick Recovery?"

norcal einstein said:
Just pulled both downloads for now until I can look into this. Like I had mentioned before, my framework.jar matches the retail dump...? Going to collect some other framework.jar and see what I can find...
Click to expand...
Click to collapse
I soft bricked my bell atrix...can you post ur scrit so i can try to run it??
Thanks

Any chance this thread gets updated?

demens13 said:
Any chance this thread gets updated?
Click to expand...
Click to collapse
i guess not???

Hello when are ou going to return the download links ?

manyelski said:
Hello when are ou going to return the download links ?
Click to expand...
Click to collapse
Wtf?!?! This threads over a year old... why the hell would you post here?
Sent from my CM7 Atrix 4G

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...