deleted .
Finally ! That bug was very annoying to me.
I'll try the fix asap, thanks a lot!
e: works like a charm!
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section
thanks a lot for post here
great job
kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?
jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Tried on UD3.3.0 wont boot... :s
People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.
Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?
jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.
The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420
Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.
j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks
Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?
Related
Hello, I installed CyanogenMod 5.0 lastnight and the market and a few other applications are not there, im guessing that is the google addon can anyone tell me in detail how to install that? Thanks
You need to flash to ER27 Google add on pack here:
http://forum.xda-developers.com/showthread.php?t=623496
Current link: http://www.mediafire.com/file/jmmzywtlnjd/gapps-passion-ERE27-2-signed.zip
thanks...How do i flash it?
I would like to know also. I've gone into recovery and added the file to the SD card than tried to run it, only to tell it me it's not a zip. So I renamed it and also tried compressing it as zip(just to make sure) and I get an error.
E: signature verification failed
Installation aborted
Download the add on from that page listed, place it on the root of your sdcard, reboot into recovery, flash it in recovery (the same way you flashed the ROM, but do not wipe), then reboot your phone.
That is exactly what I did. I sent a pm w/ more details. I tried covering all grounds just to make sure if one failed the other one would'nt.
Edit: Should USB debugging be on/off? Don't know if that makes a difference
Edit: Figured it out. Everytime i would downlad the file on my mac it would not be a .zip file so renaming it and compressing it did nothing. I downloaded it on my pc and voila, it works fine..weird...
thirdshiftdj said:
Edit: Figured it out. Everytime i would downlad the file on my mac it would not be a .zip file so renaming it and compressing it did nothing. I downloaded it on my pc and voila, it works fine..weird...
Click to expand...
Click to collapse
This is because you enable auto open files in Safari. The actual zip file is in your Trash lol.
To disable it (and u should), open Preferences > General > Uncheck Open "safe" file after downloading
THANK A MILLION, FROM NEWBIE NOOB .
ME/ sob sob ......so glad .
can i use it for cyanogen 6.1
hey can i use this for 6.1. if no please give me a link
yrdito said:
hey can i use this for 6.1. if no please give me a link
Click to expand...
Click to collapse
You managed to root your phone, install a custom recovery, flash cm6.1, but you can't find the Google apps? REALLY????
http://forum.cyanogenmod.com/index.php?/files/category/2-nexus-one/
How to install the Google Addon?
You have to change the name of the file (ex: "gapps-mdpi-20101020-signed.zip") to "update.zip". Move it to your SDcard and then install from recovery.
gonzalodutto said:
How to install the Google Addon?
You have to change the name of the file (ex: "gapps-mdpi-20101020-signed.zip") to "update.zip". Move it to your SDcard and then install from recovery.
Click to expand...
Click to collapse
You don't need to be in "Debuggin mode", neither to rename to "update.zip".. Just use ROM manager provided by cyanogenmod and go wiki :
http://wiki.cyanogenmod.com/index.php?title=Nexus_One:_Full_Update_Guide
Hope it will help you!
david1171 said:
Download the add on from that page listed, place it on the root of your sdcard, reboot into recovery, flash it in recovery (the same way you flashed the ROM, but do not wipe), then reboot your phone.
Click to expand...
Click to collapse
Hello Dacid1171,
I installed Cyanogenmod 7.0.0, with no google apps of course.
I used gapps-gb-20110307-signed pack, went to recovery and chose "Install from SD card", just like I would if I was flashing new ROM.
After that the phone wouldn't book. Logo of cyanogenmod would appear with the circular arrow moving around it, after 3 round it stops and restarts all over.
It was kept that way for a very long time hoping that the phone will come to life. It wouldn't.
What did I do wrong?
yashago said:
Hello Dacid1171,
I installed Cyanogenmod 7.0.0, with no google apps of course.
I used gapps-gb-20110307-signed pack, went to recovery and chose "Install from SD card", just like I would if I was flashing new ROM.
After that the phone wouldn't book. Logo of cyanogenmod would appear with the circular arrow moving around it, after 3 round it stops and restarts all over.
It was kept that way for a very long time hoping that the phone will come to life. It wouldn't.
What did I do wrong?
Click to expand...
Click to collapse
Try flashing it again but this time clear cache and dalvik cache.
Flash cm7 rom again follow by the gapps than reboot.
I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???
Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!
Explanation of what OpenPDroid is and does: http://forum.xda-developers.com/showthread.php?p=34190204
If you want to mod your favorite rom with OpenPDroid but you have no idea how to compile from source, follow these steps:
Download Auto-Patcher-ApG: http://forum.xda-developers.com/showpost.php?p=31648393&postcount=690
Place it in a folder at the root of your harddrive, example C:\AutoPatcher\
Run it once and allow it to update.
Download your favorite rom, example: http://forum.xda-developers.com/showthread.php?t=2008894
Open ApG and choose your downloaded rom.
Select OpenPDroid and AOSP (for this example rom).
Press Start.
Once the program is done, you'll have two new zips. One will install OpenPDroid while the other removes it and restores the original rom files.
If you already have the rom installed, simply use the OpenPDroid installer zip. Otherwise, install the rom and then the OpenPDroid installer zip.
Once you have booted up in your modded rom, install PDroid Manager: https://play.google.com/store/apps/details?id=net.digitalfeed.pdroidalternative
Use the app to set the permissions for your apps.
To remove OpenPDroid, simply use the restore zip and uninstall PDroid Manager.
From start to finish, it should only take 5-10 mins. ApG does not work on all roms, but it should work on most (AOKP, AOSP, CM, and PA).
Please post the roms you try and what the results are. Thanks.
I'm currently using LBESM. Will give PDroid/OpenPDroid/PDroid Manager a try. I'm guessing I need to repatch each time I flash a new build of my ROM due to updated system framework and stuffs? Also, repatching should not reset the permissions of apps that I have set?
Yes, when you install a new rom, you'll need to make a new patch using Auto-Patcher. The permissions are set and saved by the PDroid Manager app. So they will be saved even if you change roms. The app has a function where you can export the permissions to the SD card if you need to fully wipe. You can also use TitaniumBackup or the like to preserve the permissions.
PDroid Manager keeps saying it cannot find/communicate to PDroid or OpenPDroid after I have patched and flashed the patched OpenPDroid installer zip. I'll keep trying if I can figure out what's wrong. By the way, I'm running AOKP ROM (4.2.2) on the SGS3.. Sorry wrong forum, but thought this would work on AOKP ROM.
Did you make sure to flash the correct zip? The first time I tried this, I accidentally flashed the "restore" zip and ran into the same issue. And remember, Auto-Patcher doesn't change the rom zip. It creates two new zips. Did you get any errors while patching the rom? Did you select AOKP in the Auto-Patcher settings?
Yeah I flashed the installer zip instead of the recover zip. Problem was I ran autopatcher in cygwin on Win7. I ran it using APG and that worked. Now setting up permissions for all apps.. That's gonna take a while .
hallo,
can anyone help me whats the problem is? It's my first time that i patch a rom by myself. I think i forgot something?!
Log file link:
http://codepad.org/9aEqTNhp
Thank you
I want to patch the actually SlimBean
Junglist86 said:
hallo,
can anyone help me whats the problem is? It's my first time that i patch a rom by myself. I think i forgot something?!
Log file link:
http://codepad.org/9aEqTNhp
Thank you
I want to patch the actually SlimBean
Click to expand...
Click to collapse
Important
Do not run ApG under Windows directories such as C:\, C:\Windows, C:\Program FIles\* and so on.
Some even reported errors while running ApG from their desktop.
In case you're having any download errors (ApG or its packages) please verify your antivirus is disabled and you're not running from the above folders.
If ApG still fails to download packages or sync with GitHub, try running it as an admin.
Click to expand...
Click to collapse
That is why I suggested running the program from C:\AutoPatcher\. See if that fixes your problem.
hm ok, that problem is, I have not so much notion of pc and all .. i dont know what is mean with "Do not run ApG under Windows directories such as C:\, C:\Windows, C:\Program FIles\* and so on." how can i start this without C:\
Junglist86 said:
hm ok, that problem is, I have not so much notion of pc and all .. i dont know what is mean with "Do not run ApG under Windows directories such as C:\, C:\Windows, C:\Program FIles\* and so on." how can i start this without C:\
Click to expand...
Click to collapse
I think he means don't run the program from the root of C:\, as in C:\ApG.2.6.0.2.exe. If you place the exe in a secondary directory that is not a windows directory, you should be fine. Try C:\AutoPatcher\ApG.2.6.0.2.exe
It Works! Thank you so much mate Now im happy but Facebook not :good:
Thanks!
Sent from my Nexus 4 using xda premium
failed patching stock rom
specifically this:
http://forum.xda-developers.com/showthread.php?t=2147281
anyone ?
ido said:
failed patching stock rom
specifically this:
http://forum.xda-developers.com/showthread.php?t=2147281
anyone ?
Click to expand...
Click to collapse
You should post any errors on the autopatch thread and include your AP log.
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...
** Got Verizon Note 4 Dev Edition to work with Alliance T-Mobile ROM!! Data, calling, sms, mms work ! I smell a daily driver! I am not a developer, but this manual port taught me a lot. This was a personal project of trial and error, and research that turned into a stable ROM. Thought I'd share how I did it. I do not take credit for this ROM or kernel**
DISCLAIMER: Your warranty is now void. Please be careful make a nandroid of your current Verizon ROM. I am not responsible if you break your phone or lose data on your device! Read this whole OP!
**This is using the BETA version of Alliance ROM for T-Mobile Note 4. Download the Alliance BETA and read the thread: http://forum.xda-developers.com/not...-0-1-allianceromn910t-18-themes-huge-t3085560 to get an idea of the features of this ROM. Give lacoursiere18 and hsbadr a thanks and donate to them for making this great ROM and kernel.
Follow these steps one after the other and don't stop**
1. Make sure you are on a OAF Lollipop ROM without xposed installed. I think I used Rick's OAF Lollipop ROM originally. Download the most recent multisystem kernel. I am on BOG modem so I'm pretty sure any Lollipop modem will work with this.
2. On your Verizon Lollipop ROM make copies on your SD card of:
- system/buildprop.xml & cscversion.txt
- system/etc/apns-config.xml
- system/etc/permissions/verizon_net_sip_library.xml & vzwapnlib.xml
- system/lib/libril.so & libsec-ril.so
- system/apps/VzwActivationAgent, vzwapnpermission & **SecSetupWizard2013**
- system/framework/VZWAPNLib.apk
- system/privapp/VZWAPNService & secmms_candy folders
- system/csc folder
4. Reboot into recovery and make a TWRP backup of everything except SD card.
5. While in recovery dirty flash Alliance ROM BETA on top of your lollipop ROM OAF (Wipe everything EXCEPT data, internal storage, and SD). Then flash the most recent multisystem kernel.
6. Once booted up and apps are optimized wait until the screen turns off by itself. Download root browser and delete system/privapp/diagmonagent.apk and system/lib/libdiagmonagent.so because at startup it was sending some kind of diagnostics and thought it was messing with the data drop. Ever since these changes and a reboot data has been stable!
Reboot
7. Using root browser, swap those copied files in the appropriate file location. Change them to the correct permissions (the folders get 0755 and the files 0644, compare with other files and folders that are in place already. Make sure you change the permissions on all folders copied over and their contents. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.). Let apps optimize. **Longest Step**
Reboot
8. Edit feature.xml in the system/csc folder and add:
<CscFeature_RIL_ForceConnectMMS>true
</CscFeature_RIL_ForceConnectMMS>
Above the two bottom tags:
</FeatureSet>
</SamsungMobileFeature>
This enables auto download mms when data is toggled off !
Reboot
9. Perform a factory reset within the settings. Let phone relax for like 10 mins after it boots. Go through the setup wizard and then reboot.
Reboot into recovery
10. Make an backup in TWRP and you have your own custom ROM
I'm pretty sure this ROM is not compatible with xposed but it is very customizable, smooth, and it comes with a lot of features built in.
**READ ME**
Bugs:
- Silent mode is only available using the toggle. Volume down only goes to vibrate.
**
- Battery section in settings is missing
- No way to remove battery percentage in status bar
(Workaround: Download "Battery Usage Shortcut" from the Playstore to access the battery section and to remove battery percentage)
**
- No way to uninstall 3mint battery mod without messing the systemui up **(see update at the bottom)**
- Now that the mobile network settings are correct the advanced calling option is avaliable but it force closes and messes up your data connection. A reflash of everything will be needed so don't click on it! (I have a feeling a Verizon app is missing)
- My volume titles are not correct (Ringtone, media, notifications, and system.) when I press the volume buttons. (**Workaround download Noyze Volume Panel for free from the developer
http://forum.xda-developers.com/android/apps-games/app-noyze-volume-panel-replacement-t2875501
Give Tombarr a thanks for developing such a slick and customizable app**)
11/18/15:
- Just started using voicemail for the first time in 6 years. Good thing because today I experienced a glitch that it would not let me hang up the phone after listening to voicemails for some reason, but it didn't do that when I was clearing voicemails. (Hangs up automatically after a certain amount of time) Maybe it happens to new voicemails. Also I'm assuming since the verizon voice mail app isn't installed I get a weird unreadable verizon text when I get a new voicemail.
- One hand mode is not in the settings. Not sure why
Any suggestions or thoughts about these current bugs would be helpful.
I cannot guarantee all Alliance settings will work (stay away from performance), but most does work and it's awesome!
This manual port is now stable and buttery smooth! All basic phone functions work. Let me know if you come across any bugs or issues not related to Alliance settings. I will try to help fix it.
Thanks Stedrocklp for taking the time to try and get this working. Jal3223 thanks for sharing that key porting info!!! Wouldn't be possible without your help! Thanks hsbadr for developing Multisystem kernel ! Thanks lacoursiere18 for creating this ROM !
UPDATE:
To update Alliance settings to the most recent version and remove 3mintbattery mod download the newest T-Mobile Alliance ROM v1.1
1. Use ES File Explorer and click on the Alliance ROM you just downloaded to open the archive.
2.
- Extract system/privapp/SystemUI/SYSTEMUI.apk
- In the system/app folder extract AllianceControl folder (towards the top) and all the loose apps without folders at the bottom to a folder on your sd card.
3. Make a system and data backup in TWRP just in case things go wrong. Reboot system
4. Swap all those files and folders in their appropriate file locations and change the folder permissions to 755 and files to 644. Take this step slow and make sure the old files are renamed to .old or overwritten. If a permission is incorrect or you leave a file out there can be issues and a restore might be needed.
5. In system/app folder delete the old loose Alliancecontrol.apk, and delete 3mintbattery.apk
6. Reboot and enjoy!
This is the final release of this ROM so we are all up to date ! :good:
Wondering if this will work for sprint or any rom
dyra502 said:
Wondering if this will work for sprint or any rom
Click to expand...
Click to collapse
I'm pretty sure it would but you need to figure out the sprint specific apps to make the system happy. And flash your sprint kernel after you dirty flash. The dirty flash skips the setup which makes it possible to boot correctly.
Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!
Romans8vs1 said:
Would you mind sharing the Rick's ROM that you used? I looked at his thread, but the download links are no longer available. Thank you in advance for your help!
Click to expand...
Click to collapse
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!
jcip17 said:
Damn thats not good. I do not think I am allowed to share the ROM, as it's not mine. But I do not know how to share it anyways. I would just odin back to 4.4.4. and go through the upgrade process to OAF. Or you can try to de-xpose MoRom after a clean flash. I think there are two things you need to remove one being the xposed installer and the other I don't know the exact name but use root browser, search for xposed in the system folder, delete it, and reboot. No sure if it will messed anything up but I don't think it will. Then dirty flash the alliance beta and continue from there. Let me know how it goes!
Click to expand...
Click to collapse
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!
Romans8vs1 said:
Thank you for your response. I ODIN'd back to OAF and went through the steps in your tutorial. My phone booted up and I then proceeded to replace the files/folders and set permissions. I thought I was careful, but once I tried to reboot, the phone would not come back up.
Is there a way to make the changes (file permissions and replacing them in the ROM) on a PC?
Is there a way to share your edited files so that we could simply paste them into the ROM?
Just thought I would ask. Thank you in advance for your assistance!
Click to expand...
Click to collapse
Damn thats a bummer. Even if I shared the files you would still need to change the permissions. I think it is possible unzip a verizon ROM and unzip Alliance rom and replace the files and then zip it back up on the computer and then dirty flash that but everytime I zip it back up it never flashes. It seems that when I zip it back up it adds an extra folder that makes it unflashable but haven't taken the time to figure out how to make it work. Try starting over and getting the ROM to boot then make a nandroid of that so you have something to restore. This is what I did when I was trying to get everything working. Next time try not adding the camera files and .jar file and add them after a reboot. Let me know how it goes.
Added the setup as one of the files to copy over so a factory reset can be performed to make sure you're starting with a fresh system. This is the first day I did this and I had to pull the battery twice due to freezes after I factory reset. I didn't let the phone sit and let it settle. I would recommend you let it sit and relax for like 10 mins. I have not had any lock ups since this morning. Lemmi know how it goes!
After the factory reset the ROM is flying. As for the battery I cannot say yet but I know I did not have the best battery life on this ROM before. It did get me through the day so I was happy about that. I calibrated the battery but that is about it. If any devs knows any battery optimizations that can be made to the system without xposed please share!
I heard from a user that Xposed works on this ROM. I personally do not use it though. As for battery life I've noticed better results after I disabled automatic check for updates in the settings. Settings > About device > Software Updates and uncheck auto check for updates. This ROM for some reason does not have the audio issues that I experienced on MoROMs ROM. I am happy about that. Now that we finally have the 5.1.1. update I am going to try and port a ROM that looks good. If anybody wants to give this a stab with me that would be great to test multiple ROMs from different carriers and see which one gives us the best results. Thanks
Got something amazing in the works!
Nandroid backup
Can someone send me a nandroid backup of this I'm worried about messing up my phone up
Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk
TheRock40359 said:
Can someone send me a nandroid backup of this I'm worried about messing up my phone up
Click to expand...
Click to collapse
That's a big file idk how I would be able to distribute that lol
Romans8vs1 said:
Is there a way to install this rom in the same manner as the kyobi note 5 port? I'm running that now, but would like to try this one out. I've tried a few times but just can't seem to get this one up and running.
Thanks in advance and have a blessed day!
Sent from my SM-N920F using Tapatalk
Click to expand...
Click to collapse
It's not that simple. A data fix would need to be made and that is out of the scope of my knowledge. But when I have some free time, possibly this weekend, I can attempt to come up with something for you to try.
jcip17 said:
That's a big file idk how I would be able to distribute that lol
Click to expand...
Click to collapse
Could upload it to dropbox
Anyone with a Developer addition phone willing to help us none developers get root/unlocked bootloader? New exploit found but we need an .aboot from a developer phone: http://forum.xda-developers.com/note...ition-t3346422
Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.
stajam said:
Since I am currently on BPA1 5.1.1 running the Kyubi ported ROM and this is a 5.0.1 ROM, will I have to do downgrade my device or anything or will I be good to go to dirty flash? Thanks in advance.
Click to expand...
Click to collapse
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.
jcip17 said:
I don't recommend dirty flashing from Kyubi. You should try clean flashing MoRom then copying those files from the system. Then dirty flash Alliance, then multisystem kernel:
http://forum.xda-developers.com/not...opment/kernel-multiystem-kernel-v1-0-t3105603
And just follow the OP instructions.
Click to expand...
Click to collapse
Yeah ,I am trying to pull the files I need from my stock ROM backup that I just freshly installed on my device. I stumbled upon a forum here today called Guides There seems to be ALOT of usefull stuff in here about Porting and Building ROM's. I don't know if you have ever come across it or not.