Database Develop

Building Milestone Roms

I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.

dynamite1985 said:
I've been at this for a few weeks, and its bugging me.
I've been looking up on how to build/port ROMs for the Milestone (A853), and there is almost nothing that points me in the right direction. I want to be able to install it via OR's update menu.
This is what I've done so far:
Gotten, and set up HTC Android Kitchen by dsixda.
Downloaded the rom I want to port.
Extracted the rom system and boot images.
Replaced the boot.img-kernel with a stock Milestone boot.img-kernel taken from a nandroid backup. (I know all about the locked bootloader)
Rebuilt the kernel
Modified the build.props
Rebuilt the *.zip
Copied to Open Recovery/updates
Applied update.
So here's where it gets sticky. According to the output, the ROM installs fine. No errors nothing. However, after the first reboot, it goes directly to the bootloader screen with an error of: a5,69,4E,00,23 or something like that.
I'm royally stumped and would really like to get this going in the same way CM or Crono's is installed. Any ideas or advice would be GREATLY appreciated.
Click to expand...
Click to collapse
Is that meant to work for the milestone? I dont see milestone listed on supported devices.
Is this the kitchen you are referring to?

ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.

dynamite1985 said:
ya thats the one i was referring to.
I know its not supported, but I was looking at the outputs of the zips it creates, and comparing them to some ROMs out there (notably CM6.1 and Cronos) and they are pretty much the same. The only thing that I have noticed thats different is that the Milestone doesn't use the updater-script that this particular kitchen generates. So, if I pretty much leave the updater-script alone, it will install, up until I reboot, and I get the error code I mentioned before.
If I let the kitchen generate the updater-script, the installation aborts, usually with a 'Status 4' or 'Status 7' error.
Click to expand...
Click to collapse
Sorry buddy. I ain't a developer. Try sending a PM to Luca or Kabaldan or Feeyo ( on cronosproject ) and see if they can help.

The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.

kabaldan said:
The boot.img contains kernel and rootfs with init and its scripts. Nothing in it can be directly changed if you want the Milestone to be able to boot.
The kitchen obviously rebuilds the boot.img - err a5,69,4E,00,23 means that the boot.img signature check failed.
You can't do this on Milestone - that's why the sh-hijack + 2nd-init are used in custom compiled ROMs for Milestone to be able to use customized init scripts.
Click to expand...
Click to collapse
so I'm a little confused...
it seems to me that I should be compiling the kernal with the 2nd-init attack, which confuses me because of the BL issue. or is the stock boot.img used with a customized system.img?
i've tried the latter part, and gotten the noted error.

[APP] MakeUpdateZip-20110303 **Multi-file capable**

This is not only my first Android app, but this is also my first dive in Java. Please be gentle as I expect there are several uncaught / improperly handled exceptions.
This app will backup selected files to a zip file that can be restored via cwm. For now, that is all it does. It can be handy for the oc/uv crowd since it will allow you to keep a backup of a good S_volt_scheduler init file to flash in case your new setting are too aggressive. It does not currently restore permissions, nor does it assume root permissions.
todo:
Obtain root to copy any file
Integrate a file selector so read permissions will not be an issue.
Detect/Restore permissions
Possible feature additions:
Create a restore.zip from current files based on an update.zip you want to apply. Could save you from boot loops when messing with system files.
Create a restore.zip given a file, a target directory, and permissions.
I will probably add this to the market once I get through the todos and initial bugs.
Changelog:
20110303
Multi-file capable. OIFileManager does not yet support multi-select, so each file must be selected seperately
Exception caught for mission OIFileManager
_delete.zip file seems to work correctly in recovery
Since I am not yet using root and OIFileManager will not assume root, there are some directories that cannot be viewed, /data/app for example. There are also some files that can be selected but cannot be copied due to their permissions.
Requires OIFileManager

Nice, will be useful

This looks like it could be a useful/powerful app. It could definitely benefit from some features (more than one file/location would be great) but I can see myself using this.
Thanks!

gibson3659 said:
This is not only my first Android app, but this is also my first dive in Java. Please be gentle as I expect there are several uncaught / improperly handled exceptions.
This app will backup 1 file to a zip file that can be restored via cwm. For now, that is all it does. It can be handy for the oc/uv crowd since it will allow you to keep a backup of a good S_volt_scheduler init file to flash in case your new setting are too aggressive. It does not currently restore permissions, so the uses are currently limited.
todo:
Figure out why the _delete.zip does not delete the target file when run via cwm.
Detect/Restore permissions
Possible feature additions:
Enable backup/restore of multiple files
Create a restore.zip from current files based on an update.zip you want to apply. Could save you from boot loops when messing with system files.
Create a restore.zip given a file, a target directory, and permissions.
I will probably add this to the market once I get through the todos and initial bugs.
Requires oifilemanager.
Click to expand...
Click to collapse
Can u load the java app here? I can try to look into that and see if I can improve on the exception handling part.

fantastic idea
good job

Thanks for taking a look. Have anyone of you actually tried it?

It fc. On me... :'(
Sent from my SGH-I897 using XDA App

Do you have oifilemanager?
Sent from my SGH-I897 using XDA App

gibson3659 said:
Do you have oifilemanager?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Forgot that
Sent from my SGH-I897 using XDA App

Works like a charm! thank you so much! Perfect cause I love the stock music player and not all rims have it so this is great for installing it!
Sent from my SGH-I897 using XDA App

I am working on multiple file support, so look for a new version in a day or two.
Sent from my SGH-I897 using XDA App

just installed it, however it force closes as soon as I try to choose a source or destination file (happens as soon as I press the buttons.
Herp derp Captivate XDA app.

Make sure you install OIFilemanager from the market. I need to catch this exception and provide a link to OIFileManager.

Great App
Want to say thank you for making this. I've had all sorts of trouble getting apps from different roms to install to the system folder on my current rom. Now I can mix and match different apps easily without much pain. Thanks!

bpurkapi said:
Want to say thank you for making this. I've had all sorts of trouble getting apps from different roms to install to the system folder on my current rom. Now I can mix and match different apps easily without much pain. Thanks!
Click to expand...
Click to collapse
You are welcome. I actually have another app in mind to fully address that need, but I want to get further along with this one first. Since I am working on these on stolen time (I don't have any free time), it will take a while.
Since the apps seem to restore without permission issues, I may put that on the back burner. After I complete multi-file support, which of the future features from the op would you like to see first.

gibson3659 said:
Make sure you install OIFilemanager from the market. I need to catch this exception and provide a link to OIFileManager.
Click to expand...
Click to collapse
And I need to learn how to read through a thread for answers to my problems before I post about them.

New Version
Changelog:
20110303
Multi-file capable. OIFileManager does not yet support multi-select, so each file must be selected seperately
Exception caught for mission OIFileManager
_delete.zip file seems to work correctly in recovery
Since I am not yet using root and OIFileManager will not assume root, there are some directories that cannot be viewed, /data/app for example. There are also some files that can be selected but cannot be copied due to their permissions.

Can I get a gauge on the interest level for this app? Should I move this to the I9000 forum?

I think it's really useful when working whit OC/UV.

gibson3659 said:
Can I get a gauge on the interest level for this app? Should I move this to the I9000 forum?
Click to expand...
Click to collapse
I think you should get with rom devs, this should become an integrated feature for all rom upgrades, regardless of phone
at least get with the AIO dev, if you arent already

Finally a fix for 2-3 call delay!

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?

[BOOTSTRAP] Custom Safestrap v1.08f Released - 4-16-2012

Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u

i need this about 6 hrs ago lol.

Quite useful mate cheers.
=smc

Thank you so much for sharing this file. Your work is greatly appreciated.

This is a nice little(big)addition to safestrap! Thanks for adding it in!

I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!

Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.

TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.

I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium

Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.

redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium

Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!

ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium

Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^

orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???

@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.

I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.

This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!

Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.

Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!

Stock N910F - de-googled?

Hi all.
Noob here on the forum, my very first post so i am not allowed to post this where i imagine this would belong - the 'Original Android development'. That's why it is posted here.
First of all, i wish to express my sincere gratitude to all you people that work hard on making it possible for rest of us mortals to make the best of those small devices that somehow managed to become so big parts of our lives.. I have been following the forum for a while and been using some things posted here to fiddle with several devices without actually bricking any of them as yet. And this is the first time i felt the need of actually asking for help and/or guidelines.
Anyhew - here's the thing: i still run a N910F on stock marshmallow as my main device. (Please no lectures about this). And lately i came to really, really resent mr.Google. I did make a Lineage version of the Android Pie work together with microG (without google), and that actually is rather sweet, runs smooth as silk. I run that on my backup N910F device. (Ok, so i am a Note 4 freek, sue me).
But for different reasons, actually mainly because i really appreciate the s-pen, i want to continue using stock rom on my daily driver so now i am looking for a google-free version of the stock marshmallow for the N910F (trlte) model. I tried to find it here on the forum, but i couldn't, or i couldn't understand the terminology. Haven't found in the rest of the internet either. So i would appreciate if somebody here could either:
1. point me to the direction of such a version if it's already existing, or
2. give me very specific information as to how i could de-google the stock rom by myself. Either on the device or in Windows. I haven't used adb or fastboot yet, but perhaps i could learn if i don't have to take a class in engineering first…
Or could i simply use Titanium backup and just delete (freeze first of course) all the apps that have 'google' in their name?
The third option is perhaps that some kind sould de-googles the stock rom for me and lets me download it. I would donate, of course.
I would really appreciate all the pointers you could give me.
Regards,
prkfsz

Nope, the N910F stock firmwares are definitely not de-Googled. Flash one for yourself and see. I would recommend flashing a LineageOS/AOSP-based ROM, they are generally Google-free.
If you are really insistent on running stock, then do this to completely de-Google it:
In Titanium backup, search for 'goo', this will find almost all Google apps on the ROM. Uninstall them.
Also, download the latest OpenGapps ARM 6.0 nano zip from opengapps.org. Extract the gapps-remove.txt file from the zip. Use the contents of that file as a reference, find all the files listed in it, manually delete them. The reason for this is that Titanium will miss some things.
Now you should be mostly if not entirely Google-free.
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
I'm running Resurrection Remix Nougat v5.8.5 (Android 7.1.2), SPen works fine here. Every app I've tested that can use the pen, works fine. There is really no reason to stay with stock just for pen functionality. I also like the huge amount of customization options that RR has compared to stock. And I can use Substratum (no go on stock) with all black themes, for battery savings.

Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.

prkfsz said:
Thank you! Wasn't aware of the google-remove.txt file within gapps. Will definitelly use it. Otherwise it's like i thought: use Titanium and just go loose on everything that starts with 'go'...
I know about microG and use it regularly. Happy customer…
I do like stock marshmallow on note 4 and want to run it as long as it can go. I will perhaps try the RR nougat you suggested on the backup unit. Even tho i am in no particular need of customisation.
Thanx again.
Click to expand...
Click to collapse
You might find this of some interest.
https://forum.xda-developers.com/android/general/guide-degoogle-device-install-microg-t4058743

I'm afraid i got stuck here and i need a bit further assistance.. :-/
Coming from stock marshmallow on Galaxy Note 4. I uninstalled google things first using Titanium. Then manually cleaned some leftovers using file manager in TWRP (not sure i did the right way), altho it looked quite empty in the /system map. Another time erased just the Google Play-services before going to TWRPs file manager and it looked just as empty. At both occasions i lost auto-rotate. Is this normal?
After deleting all the google (and in the second try only google play services app) i tried just for the heck of it to run the Nanodroid patch file but i got an error message that it couldnt deodex services.jar file, which was pretty much expected. My skills are not sufficient for deodexing files so i tried other approaches for patching. Smalipatcher - the damn thing couldn't even see i had admin privileges in Win no matter what i did and just refused to run alltogether.
Then i tried the link that was put here by @MrJavi in the post above (thank you sir!). Did everything as the tutorial says, got no error message, everything seemed to run smooth and the apps i chose were installed. (altho TWRP did freeze a couple of times during aroma setup so i had to reset by taking out the battery). When i wanted to set up the microG settings, the microG icon and the app is nowhere to be found. The modul named NanoDroid exists and is activ in Magisk, but it's not possible to open it.
Last, but not least of course, i tryied patching with fake gapps module in Xposed, but Xposed of course does not want to play nice with mr.Samsung. Even when i try and run Xposed from Magisk...
Not sure how to proceed from here.. I'm thinking of switching my starting point to the already deodexed version of marshmallow i thought i saw around here, because it would be easier to patch.
If it's still out there available for download, which i don't take for granted anymore nowadays..
But i would like to make it work on my device anyway. So, if anyone has any ideas, they will be so welcome.

Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456

Mr. JAVI said:
Perhaps Samsung knox is causing issues with Xposed framework/installer. The link below is for a different "Samy" but the the Knox remover is a flashablw .zip made specifically for the Note 4 .
https://www.google.com/amp/s/forum....-how-to-deodex-root-remove-knox-t3458921/amp/
https://www.google.com/amp/s/forum....al/toad-source-android-deodexer-t3848307/amp/
Always take a full Nandroid backup by checking all partition beforehand and save to your external sd card. You can then choose to flaah an Aroma Google debloater .zip .
https://forum.xda-developers.com/android/software-hacking/aroma-google-services-debloater-t3668456
Click to expand...
Click to collapse
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.

AnonVendetta said:
Once you have done that, you can optionally patch your ROM for signature spoofing support, and install MicroG, which is an open source Google Play Services alternative. These 2 steps are optional, your choice.
Very simple. I've done this before, things will work fine overall. But some things (apps) requiring Google components may not work correctly, if at all. MicroG can help mitigate this to an extent. You've been warned.
Click to expand...
Click to collapse
HOW?! did you manage to patch it??

prkfsz said:
wow, those were really some good links! thanks, @mr.javi. However....
tried the first link and to work with firmware but the ext4uninstaller does not want to recognize the ext4 file (wtf??), regardless from where i download the software and regardless what ext4 file and from what firmware (tested a few), and without that part working it was pretty much impossible to go on. So i ran only the deknoxing tool through twrp. No error. But still when i try and install the xposed - boom! it will not boot. Not even damn zip uninstaller for magisk will work as it should..
Tried the second link with the TOAD. Weird: some versions get recognized as malware by my antivirus and windows does not want to run other versions for safety reasons. Strange..
Tried the third and that de-googling script is rather sweet.
But my conclusion from all this is that it is not so hard to exorcise the google, but to patch the rom in the next step... If i understand correctly i have to get the rom deodexed first to be able to patch it with nanodroid?
I tried some deodexing tools on pc, but i'm not really sure if i'm doing it correctly. I take it i have to copy some folders (/apps, /framework and one more) from the phone to the computer to work with them there, but i get error message when i try to copy files through file manager in twrp. Am i supposed to do it some other way? And can you do that directly in the phone? I tried an app called 3c -all in one-toolbox that has native option of deodexing but i get error message there, something about classes i think, i don't remember and i can't see it now cause the phone is just being reflashed..
Any more thoughts and ideas? As usual, grateful for anything you can give me.
Click to expand...
Click to collapse
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://how-to-easily-deodex-android-stock-rom-without-pc/

Mr. JAVI said:
You're very welcome @prkfsz
https://mtkcustomroms.com/deodex-stock-rom-custom-rom-without-pc-2018/
https://************/how-to-easily-deodex-android-stock-rom-without-pc/
Click to expand...
Click to collapse
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.

Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
prkfsz said:
Thanx again, @Mr. JAVI! :good:
Both links are about the same app and i've tried that one recently, so it seems like we think rather alike.
I get the exact same error message like the guy that wrote that one comment at the bottom of the second link (error saying "needs rebuild classes.dex").
And strangely enough when i open the deodexing window in the app it says that of the number of apps in the rom not all are odexed (says something like "deodexed 124/187"), which is rather perplexing because it's on the freshly installed stock (from nandroid backup directly after factory reset). So I tried to fool the app and get all the apps odexed first, but that didn't fly either..
Btw, thanks for the advice before - i always back the device upp (all partitions) before messing with it.. I forgot to do that on one device before and instantly regretted it..
-------------------------------------------
Edit: the second link in your last post was dead so i tried to correct it in my message, but xda forum doesn't like that.
Tried to post in the right link here in the message too, but that didn't work either for some reason.
but searching the phrase 'how to easily deodex Android stock rom without pc' will give you the first search result.
Click to expand...
Click to collapse
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .

Mr. JAVI said:
Oat2dex.jar
https://www.google.com/amp/s/forum....eral/tool-deodex-tool-android-l-t2972025/amp/
https://github.com/testwhat/SmaliEx/releases
---------- Post added at 01:14 PM ---------- Previous post was at 12:43 PM ----------
Well to tell you the truth, even a full Nandroid backup couldn't fix a dm-verity/drk issue on one of my Note 4's. Up until then I have always recovered from softbricking my devices. Stubborn as I am, I spent hours and hours and hours o no avail. I connected my other N4 but still kept trying to revive my old N4. It wasn't until a year and a half later, assisting another member that I came across a possible solution and it worked. Spent more time than my old N4 was worth but my record is untarnished non the less. lol I sure hope you never ever encounter either of thoughts @prkfsz .
Click to expand...
Click to collapse
And i thought i was stubborn for this, insisting on tweaking an age-old os and spending hours on looking for solutions.. thank you!
Not sure about what that issue you mentioned was, since i'm not really on that experience level, but i'm sure it was a mean one.. lol Good job of fixing it! I ended up a few times in similar situations (not with that high level issues apparently) and i just couldn't let go untill i resolved them or bricked them completelly... Luckily haven't bricked anything even tho i play mostly with older devices so it wouldn't be such a waste. But as you too apparently feel - unblemished record is a matter of pride..
And yes, i too recently understood that nandroid backup isn't allmighty - it can't for instance save certain safety settings, fingerprints and such. I always thought of nandroid backup like a 'clone' feature on PC. Loved that..
Aanyhew - back to business.
I hit the wall here again, the same one as with Fulmics deodexer. It's not that it isn't working, it's that i don't know how to point it to the right maps for deodexing.
As far as i understand, i have to copy those 3 folders from the phone to the PC, do the deodexing on the pc, and then move back to the phone and replace the original folders. Is this correct? I tried doing this in TWRPs file manager using micro sd card, but i gott error message that it wouldn't copy all the files for some reason. Should i use some other method of copying those folders to the PC?
Perhaps a stupid question but is there any way to let the deodexer on the pc find the folders directly on the phone?
As always - a huge thank you from the struggling noob, @Mr. JAVI. :good:

Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.

Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344

Mr. JAVI said:
Perhaps this is the Xposed framework and installer that might be compatible with your N910f
https://forum.xda-developers.com/note-4/themes-apps/unofficial-xposed-v87-3-magisk-v18-t3897017/amp/
As far as TWRP you might be able to patch it and save internal data with Tipatch apk. The drawback is you backups will be much larger.
https://www.google.com/amp/s/forum....pp-twrp-tipatch-backup-internal-t3831217/amp/
PS: Thsnks for the compliment my friend but I'm still learning. Modifications is just a hobby of mine. We learn from each other here on XDA.
PC : skills are not my strong point . Your skills with PC far
exceed your ability. I actually bought a laptop years ago, just so I could flash TWRP Odin and root . The complete ssd laptop cost alot more than my Note 4. I port or create my own flashable .zips. Although, I've never been faced with having to deodex a custom rom, simply because there readily available from the developers on xda for the n910p. Sucks there hasn't been one developed for your n910f.
Click to expand...
Click to collapse
Laptop cost way over Note 4? I see i'm not the only one..... ehh, let's say determined bloke around here haha.. Hope it was worth it.. And btw creating your own flashable zips is way above my level of skills, i can tell you that, my friend. Never did that, nor am i planning to. But since i am stubborn (or so i've heard.. lol) and i feel uttermost distaste for mrGoogle and, like you said, noone has apparently done the deodexing the stock N910F - I am simply forced to take matters into my own hands. Flashing a pie and microG is ... apparently too easy. Besides, i am already running that on one of my spare Note 4s.. And i appreciate xda, just like you say people can give each other a hand. What i dislike tho is lots of dead download links... Oh, well..
ok, back to business again.
I guess i am going to need a more detailed help now.
I tried with that version of Framework you linked to. At that page the link for Xposed installer app for Magisk is dead. Tried to play a little with the other file, the version 87.3 of Xposed and just flashed it in TWRP, but nothing happens.
As far as the Tipatch, excuse my ignorance but i have to ask here: what difference would it make for deodexing to be able to copy internal storage? I am thinking it's other folders that need to be copied, like /system.
Apart from that, i love the idea of Tipatch! Will install it anyway.
--------------------------------------------------------
I am beginning to realize that there are not many reasonable options left, since i'm not sure it is worth much more time and effort on my part. I am not going to be an engineer over this..
So there is but one more question to perhaps get solved before i run out of options and go with custom Pie anyway.
And that is - how do i copy the needed 3 folders intact to PC for deodexing software? I can't find that information anywhere together with this pc based deodexers.
Oh well. I have vague memory of ES file manager being mentioned somewhere. So i guess that will be my last attempt before i give up. Unless some new solution emerges.

Mr. JAVI said:
Something posted by @IBNobody
"Anything past Magisk v15.3 will not pass SafetyNet on QI5.*
Magisk v15.4+ added a check in its Magiskhide subsystem that looks a service (logd) to be loaded. That service is not running on our stock or slightly modified QI5 build. If this service check fails, Magiskhide does not get loaded. If Magiskhide is not running, it can't hide Magisk from the SafetyNet checks.
(You'll know if this is affecting you because the Magisk Manager app won't remember any settings you make in the Magisk Hide tab.)*
Our only options are:
1. Build our own fork of Magisk that skips this check.
2. Enable logd by modifying the init.rc file in boot.img. (logd is commented out. I have not tried un-commenting it.)
3. Remain on v15.3."
DQ15 is the Sprint firmware 6.0.1 and not n910f but it could be the same with yours as well.
A slightly lower version Xpoaed framework api 23
https://androidfilehost.com/?fid=529152257862685344
Click to expand...
Click to collapse
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you

prkfsz said:
Ok, i managed to actually copy the system directory from the phone to the pc using Root explorer app. And none of the deodexers work. Fulmics says it needs smali and baksmali versions over 2.2 even tho i fed it with versions 2.4. SVADeodexerforart runs through all the files without actually doing anything. Logfile shows error 'cannot acces jar file' on all 300+ files.
So i believe this is it for me at this point. I just can't see how further struggle would be meaningsfull since it would just take even more time and i already invested way too much of it on this. But i guess being stubborn has it's price.. :silly:
I want to extend my sincere gratitude, @Mr. JAVI, for your patience, tips and guidelines. I think if it wasn't for you i would given up much quicker.. Which perhaps would've been a smart thing to do... But i wouldn't learn anything..
We will probably bump into each other more times here, since we seem to share the common affection towards a certain gadget.
all the best to you
Click to expand...
Click to collapse
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz

Mr. JAVI said:
I am just one of the "common folk". One of my hobbies is modifying my rooted Note 4. I have learned from my failures as well. The creating custom zips is not as hard as you think, in fact it was a failed camera .zip fash that ended in FC's. I came up with an idea to take the previous working camera .zip. left the meta-imf and replaced tge rest with an N7 camera from another rom and fkashed it. It's much easier explained with screen shots.
One of my favourite apps is ZArchiver apk. Downliad it and you'll see why. Ext4, tar, zip, roms, jar, apks and more. Freaking Awesome!!!
https://play.google.com/store/apps/...pk&pcampaignid=APPU_1_YUIBX4STE-aD9PwPh7ylmAg
Its like gold and did I mention free? lol
Welcome to XDA @prkfsz
Click to expand...
Click to collapse
Why thank you good sir, @Mr. JAVI! :good:
Every noob should get this friendly a welcome..
See? All that meta-inf, FC-talk is a bit over my lever right now. But i will check out your tool. Might come in handy for some future project. And free it is you say? Sold! haha
As for this project i had, i had to abandon it for now. I realized it wasn't the degoogling that was the problem, but the patching afterwards, and the deodexing that turned out to be downright impossible to get done. And it just gotten too time-consuming in relation to how much time i actually have and how much win i would get out of it. So i took the easy way for now and i went with the custom Pie. I do want the audio from the headphones..

@prkfsz: I used Tingle patch to integrate signature spoofing. You have a few options:
Tingle patch (requires deodexed framework.jar)
Needle patch (requires deodexed framework.jar)
Nanodroid patcher (requires deodexed services.jar)
Haystack patch (requires deodexed services.jar)
Smali patcher (services.jar can be odexed or deodexed, it will deodex and patch the file for you)
FakeGApps (requires Xposed)
Options 1/2/4/5 require a PC. Options 3/6 can be done on device without PC.
Hope this helps!

I don't really have a lot of time to go into detail, but if either of you are looking for a comprehensive way to properly deodex a ROM, check out SuperR's Kitchen. There a free and paid/donate versions. The free version can do what you want just fine.
I had recently used this to deodex the latest stock MM UK firmware for the N910F. In addition to deodexing, the Kitchen can also customize your ROM, and even build a zip that you can flash in TWRP. It flashed and booted fine for me. Once you have done this, you can debloat the ROM (or let the Kitchen do it for you). It won't remove all Google stuff by default, but you can configure it to delete pretty much any file/directory in the system partition. My advice is to use the Kitchen's debloater/Knox removal features, then use gapps-remove.txt and a root file manager to delete the rest. Once you have debloated/deodexed, you can then easily signature spoof patch with any of the tools I mentioned in my previous post.
I have also discovered that you can also run the Tingle patch without a PC, by using QPython3 app. Just supply the deodexed framework.jar and build.prop, it will do the rest. Grab the Tingle master zip from GitHub, unpack it into QPython3's scripts directory on the internal storage, then provide the 2 files into input folder, and run main.py from within the app. You will find the patched jar file in output folder, replace your ROM's framework.jar with the patched one. Use Signature Spoofing Checker to confirm that it worked. I don't think root is required, but it's better to have it anyway, just enable root in QPython3 settings.
Some last notes: don't use Titanium to debloat Google apps, it may also remove some needed shared library files that Android uses. Namely, a library file called libgnustl_shared.so, which will cause autorotation to not work. Use Titanium to determine the locations of Google apps, then delete them manually. This will keep the shared library files while still deleting the apps. On top of this, use gapps-remove.txt.
But while you are debloating, there may be 2 Google apps present that you should not remove, period:
/system/app/WebViewGoogle
/system/priv-app/GooglePackageInstaller
The first is needed by Android and apps to provide webview functionality (this might not sound important, but it is). The 2nd is needed to install apps, remove it and you won't be able to install any app from anywhere (Play Store, manual APK install, etc).
On the subject of Xposed, do *NOT* install the Xposed installer from the Magisk Manager downloads. It isn't designed to work on stock Samsung MM firmware, you won't be able to boot. Use the custom Xposed by wanam (available on XDA). Or you can google for "Xposed kevintm78", this will come up with an AndroidFileHost link that you can install from Magisk. The latter is just a systemless Magisk version of Wanam's Xposed.