Related
hey boys
so I finally gave it and did the whole adb rooting thing... lots of command lines and so on but finally it works so I got rid of Universal Androot..
so now my problem is still there though...
I run the update.zip and I get this:
assert failed: apply_patch_check(“system/app/GenieWidget.apk”,”(insert tons of digits here″,”(insert tons of digits here)″)
“E: Error /sdcard/update.zip
(Status 7)
Installation aborted.”
Anybody got a solution?
My phone and its changes:
Stock Nexus One 2.2
Rooted word-per-word via http://forum.xda-developers.com/showthread.php?t=736271
Uninstalled Amazon MP3 and "News & Weather" (genie widget?)
I figure maybe reinstalling News & Weather would fix it ... but Titanium backup does not recover it even if I did back it up first... (useless??)
I downloaded the APK and instaled it, but still the same thing.
What else what else...
thanks
I'm only posting this here because I, too, have an error and am in no way trying to thread-jack. I got the 2.2.1 OTA the other day and went ahead to update. Unfortunately, I use AndRoot also and when I got halfway through the OTA, I got an error during installation. I pulled the battery, rebooted, and I was still 2.2 rooted. I unrooted with AndRoot and now seemingly have no way of acquiring the update OTA. Any advice, OP?
OTA seems absolutely random to me ... so I would download the update (found in this very forum) and rename it to update.zip and put it in the root of your sd card and run the update as prescribed on many sites...
as for my problem... damnit damnit damnit is all I can say. I know 2.2.1 is generally useless, but I want to be sure I can install Gingerbread when it comes out!!
damn so I tried 2 different versions of GenieWidget installations (it's news and weather)
seems I get the same error everytime.
I know the "simplest" thing is to run a full reinstall of my phone (recover console?) but I don't want to redo all my apps/settings... can't there be a way to recover 1 or 2 components only? in this case, amazon mp3 and geniewidget, just so that the 2.2.1 update works...?
I had the same issue with com.amazon.mp3.apk not being found (I remember deleting it as soon as I got root)... well I had to put it back under /system/app/ (meaning you can't do it via the market - only manually)
Note: the exact version that was shipped with froyo has to be installed. You can check that you have the right apk by computing its sha1 sum (that's the second "insert tons of digits here" MitchRapp refers to)
*UPDATE*
oh snap.
my friend has the same nexus one as me ... so I copied his GenieWidget.apk and .odex into my /system/app and so far so good... i got another error (com.amazon.mp3) so I'm going to copy that too
update to follow...
hey it worked!
after a (seemingly) endless "X" animation bootup... 2.2.1 is there.
now I lost the root access I just made with adb shell something something.... that's normal I guess, so I'll redo it
Uh oh, I removed amazon mp3 too...;(
toss the .apk back in /system/app and reboot and update... it worked!
now for re-rooting... that wont work damnit.
I'm doing the rageagainstthecage thing word-for-word and the thing is, when I try
./busybox cp busybox etc...
it says file already exists
and the chmod commands only give me a "read-only" error
cuz I already rooted earlier using the .freenexus style .......
what can I do for this?
Anyone happen to have the2.2 Amazon apk and willing to share?
Sent from my Nexus One using XDA App
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
bennettm89 said:
Anyone happen to have the2.2 Amazon apk and willing to share?
Click to expand...
Click to collapse
Sure.
sha1sum is c3b285c13db4b7f8fcfb72372d77b388157bf6cd
MitchRapp said:
I do, what's your email
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
I used superboot (1.1-FRF91-nexusone-superboot) - worked like a charm.
I had an issue with settings.apk , had used universal androot and metamorph to make changes to the battery meter.
After getting the ota , the installation was aborted due to changes in settings.apk . i downgraded to android 2.1 erd79 ( had the passimg.zip file from few months ago).
Once downgraded never got OTA for further updates ( eg ere27 , frf91 etc).
had to manually update to frg83.
Jony, Thank you.
OP, thank you anyway, I got it from Jony. Now to find the update.zip...
God bless it. Went to go install from SD, I don't have twitter. I hate twitter. Anyone have it...
MitchRapp said:
anyone know how to re-root 2.2.1 using the rageagainstthecage without it telling me everytime that busybox file exists and is in read-only... i followed the steps to the letter...
Click to expand...
Click to collapse
The rageagainstthecage step-by-step is missing a couple steps that will cause it to give the errors you're seeing. I ran into this and posted the solution, with follow-up and confirmation by others, later in the thread. Check out
http://forum.xda-developers.com/showthread.php?t=792016
In a nutshell, the /system partition needs to be mounted for both read and write in order to set permissions on the Superuser.apk and su files. Also, if you already were rooted and have Superuser.apk, su, and busybox installed, you don't have to copy them back to the phone--you can just set the permissions on the existing files.
Ohhhh jony! Can you post the twitter APK pl0x
bennettm89 said:
Now to find the update.zip...
Click to expand...
Click to collapse
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
bennettm89 said:
Ohhhh jony! Can you post the twitter APK pl0x
Click to expand...
Click to collapse
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
jony22 said:
There it is: http :// android.clients.google.com/packages/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
Hre you go - sha1sum is 2acade940a14e65abcb93ff7fc68b0a95b733113
Click to expand...
Click to collapse
Thanks buddy, I appreciate it.
I'm not really happy with the update. Lost root ( I knew I would ) but the most upsetting thing is that I removed my work email from my phone. I had to update security settings to authorize the remote administration of my device through my exchange server at our HQ which is not happening. I know it doesn't have to be done but I was getting increasingly angry just looking at it in the notification bar 24/7.
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...
Hello gentlemen,
I'm back, with a what I hope is a minor issue. I hope someone can help me.
I have the following head unit (Universal Model):
KLD Universal model S07 - RK3181 (quadcore)
800x480 resolution - KK 4.4.4_23072015
MCU version MTCB-KLD2-V2.67 (Jul 09 2015 19:15:51)
Kernal version 3.0.36+ [email protected] #396 (Wed Jul 22 17:40:16 CST 2015)
Build number RK3188-ENG4.4.4 23072015.09:09:11
CPU ARMv7 1.6Ghz (x4)
It is rooted via the factory settings method. But other than that it is pretty much still stock (I added a cooling fan). The only other apps I add where PowerAmp, PowerAmp Toast, Xposed Framework, XposedMTC, and Lucky Patcher (I believe this app fully unlocks the PowerAmp app). I have had no issue with it for the last 7 months.
However, the other day it took a long time to bootup. Now I have some google service errors: "the process com.google.process.gapps has stopped"
I have to keep on clicking "OK" in order for the error pop-ups to close. I have to repeat this several times until all the pop-ups finally stop. Other than that, everything else is working properly. Although I notices that Xposed and PowerAmp Toast do not start (no icons on the top notice bar).
I tried going to Settings/App Manager/Google Service Framework - and then I click Forces Stopped it, Disable, Clear Data, Clear Cache, Enable. Then I reboot, but I still get the same google service errors.
Can someone please help me fix this? Any help will be greatly appreciated.
Thanks,
Galo
PS - One other thing. This is related to the XDA website in general. How can I get rid of that stupid side panel (Analysis & Opinion / More XDA New). It keeps on automatically scolling and gets in the way of reading and typing. It is really annoying. Can someone tell me how to switch this off. Thanks again
Lucky Patcher has a "clear cache" option. Maybe try that? Should force all the Android apps to optimize at boot and maybe fix your issues.
Hello BullGawd,
I already tried that. I also tried going into Settings/App Manager and clearing the cache for Google Services Framework.
I even tried by pressing the small reset botton on the face of the head unit. I am trying to avoid doing a factory reset from the recovery screen.
Has anyone had this issue with this these head units? How did you get this error fixed.
Thanks,
ggee
Hi guys,
My unit is stock. But I think I am just going to flash a newer version of the factory firmware (kitkat 4.4.4). In the old threads there used to be two repositories. One was the huifei-fileserver, and the other was a Google Drive site. Now I only see the huifei-fileserver.
Anyways, I downloaded the latest KLD RK3188 800x480 firmware:
http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/
However, it looks like the firmware .img file is made up of two parts. Both are zip files and each one contains a .img file.
-Am I supposed to merge both of these files into one .img file? If so, how do I do this?
-Or am I supposed to put both of these .img files into the root of the sd card (then insert to the gps slot)?
I know how to flash and update the firmware. However, I have only ever seen this process done using one .img file - not two. Can someone please clarify what to do with these two files in order to flash them properly. I do not want to gamble and brick my unit.
Thanks,
ggee
is one an mcu.img file? If so, remote that and only flash update.img
Dave
TT_Vert said:
is one an mcu.img file? If so, remote that and only flash update.img
Click to expand...
Click to collapse
Hello,
The first zip file says Part1 and its 204MB in size. This zip contains one update.img (634MB when extracted). The second zip file says Part2 and its 91MB in size. This zip also contains one update.img (yet it is the same size when extracted - 634MB). This is confusing and should be something easy and straight forward.
I am not sure if both of these files need to be merged. If they are supposed to be merged, how would you do this (what app does this).
-OR-
I am not sure if both update.img files need to be copied to the root of the sd card. However, both files cannot have the same name within the same directory, otherwise one file will overwrite the other. One file name will need to be changed. But I believe once you change the name, the head unit will not recognize it as a firmware image anymore.
Can someone please clarify this.
Thanks,
ggee
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
TT_Vert said:
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
Click to expand...
Click to collapse
Hello,
Yes, these are winrar files and I also use the winrar software. Sorry, I tend to use the word "zip" when talking about compressed file formats in general. Both files I am speaking about are winrar (Part1 and Part2). And each has an update.img file. How do I combine the files? Is there a special function within winrar?
BTW - do you have any idea about my original problem (google services stopped working)? Since I have not gotten a definitive answer, I was thinking about either doing a factory resetting, or just updating the firmware and mcu. I decided to update and that is why I'm stuck on these two "winrar" files, and how to combine them.
Thanks,
ggee
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Dave
TT_Vert said:
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Click to expand...
Click to collapse
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
There is no fix but myself and another person did try a bunch of different versions so search for it to find the most stable version.
gguevara said:
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
Click to expand...
Click to collapse
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
vinpee said:
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Click to expand...
Click to collapse
sciux said:
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello guys,
Yes. I was able to correct the problem.
All I did was re-flash the stock firmware rom. You can either re-flash your current version (if you have the update.img file for your head unit model). Or you can find the post in the Android Auto forum that lists most of the stock firmware roms. Make sure you select and download the correct one for your head unit type and model. I simply went back to the seller and asked them to send me the latest official stock firmware rom.
If you have certain apps and setting that you want to keep, make sure you make a back up before re-flashing the rom. Otherwise you will have to reinstall the apps and setting. Since I am basically keeping my head unit in a stock status (except for normal root), I just skipped the back up step and re-flashed the rom.
Extract the .zip or .rar of the firmware rom image. Then copy it to an SD card and insert it into you head unit. Reboot the head unit into recovery mode. Make sure to clear caches while you are in the recover mode, before re-flashing the rom. Then follow the menus for flashing the rom.
Later,
ggee
Hi there anyone!
This is my first post ever so I'm sorry if it's not the right place, but I really need help with this thing.
I used to have XPosed Framework running on my old Doogee DG550, and it was real fun. Now I got a Doogee F5 running Android 5.1 and I decided to put XPosed it too.
However, I'm finding it extremely difficult, as I got "stuck" while trying to follow the guide in this post.
I've installed the XPosed Installer just fine, I can see it in my apps, but of course it still says I need to install the Framework. So I downloaded the version mentioned in that post, which is xposed-v85-sdk22-arm64.zip and then the Official TWRP App I found on the PlayStore.
Then I simply tried to open the app and find the file while searching through my folders, but the app couldn't recognize it. So I tried extracting it in a folder and then pointing out the entire folder to the app, and this failed too. I tried opening every single folder within the .zip file, but yet no usable file was found.
Now I'm kinda stuck: I don't really know what I'm doing wrong, and as you might have already figured out I'm a real noob at this.
If any of you people can help, that would be great!
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.