Related
A very good vnc solution that is *actually* useable....It's beyond me as to why this isnt on the market (maybe its the $25?)
Play around with it...its quite fun...
Where's the link?
Is this it: http://code.google.com/p/android-vnc-viewer/ ?
Android VNC Viewer
So last night i saw a post on googles own vnc viewer which is coded to work on the g1 and the android emulator.
Well, I forwarded my ports correctly and setup my server accordingly. I am using TightVNC as well as UltraVNC at seperate times.
I am able to establish a connection through all services on my g1, (3g edge and wifi). Only when I arrive on the connection
I am greeted with only a black screen. I switch to mouse control on my g1 by pressing trackball and can see me moving the pc mouse from my g1.
So my connection is working flawlessly but my only error is that i cant see anything on my g1.
Is there a special mirror driver i must install??? somebody please help me for i use remote desktop as a part of everyday life
Latest androidVNC viewer
As long as none of these are shown as released on http://code.google.com/p/android-vnc-viewer/ I'll keep compiling and placing them here. I'll edit this post with the current latest so it's easy for everyone to download without spending the time getting eclipse up and working.
r17 allows saving of multiple servers for quick-connect profiles.
I do not know if you need to uninstall the previous version before installing this one. I always uninstall before installing the new one with a project that changes as much as this one has recently.
Thanks buddy!
Thanks so much! I hope this app gets the development it deserves. This, and an rDesktop app are needed badly!
ultimind said:
This, and an rDesktop app are needed badly!
Click to expand...
Click to collapse
So I am not the only one who thinks this!
Android-VNC Viewer Compile?
How do I go about compiling the source code for the Android-VNC Viewer located at (http://code.google.com/p/android-vnc-viewer/).
I looked around and seen a post that said I would have to compile it on linux / mac... I do have Ubuntu setup on this machine as a separate OS but I'd rather not boot into Linux just to do that...
Anyone run native Linux that can compile the APK and add a link? If not then I will as long as I know how
just download the apk they have for download and use that.
The APK that is on there is far outdated compared to where the project currently is. For instance, there is a post that links r17's release on it which allows you to save settings, change color mode and a few other nice features... The current build is up to r28 now so I'm sure better support and newer features were added since then.
http://forum.xda-developers.com/showthread.php?p=3199765#post3199765
I think that build is only a few days old.
r31 is now the latest and the developers have released it directly:
http://android-vnc-viewer.googlecode.com/files/androidVNC_build090125.apk
They compiled it this time around so I didn't have to
Thank you! Cant wait to try it. =)
Hmmm, I tried the linked apk and it won't install. The older version still works.
I checked out the trunk but it is the same as the previous release.
I checked out the antlersoft branch but it doesn't compile: package com.antlersoft.android.dbimpl does not exist
Has anyone else tried the latest version apk or compiling?
I've tried it, and it won't connect for me. However, I haven't tried any previous versions, so I may have it set up incorrectly.
The R17 build won't work for me, so chalk it up to that. Or my stupidity.
Well I downloaded it to my laptop and then installed via adb and it worked.
Usually I download with steel and install from the sdcard. But that didn't work this time for some reason. (new JF1.41 or new vnc or user error?)
This wouldn't install for me from the sd card. Any ideas?
Yeah it wont install for me either, I tried both AppsInstaller from SDcard and adb - neither were successful... I noticed the build is now at 33, any chance we can get someone to compile it? Maybe the issue was fixed but not repacked?
There's an "official" build/apk out on http://code.google.com/p/android-vnc-viewer/. The filename calls is 090125 which, I assume, means January 25th I downloaded it and tried to install it from my phone (not via adb) and it failed to install for me (BTW, so does the -17 version in the first post). Could be that the key is installing via adb, I don't know. I'll try it later when I have a chance but I thought everyone owuld be interested in the update.
I reported this as an issue on the project, however after fully uninstalling the previous app and downloading the file directly from my G1 it installed successfully. I did not use the SDcard / AppsInstaller or ADB - I just used the traditional method of going to the site on my phone and installing it from there, after I uninstalled the previous version.
Hopefully this works for you guys as well.
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
someone needs to close this thread before this flame war gets any bigger
tekgek said:
Hello, all,
I have recently taken an interest in developing Android 2.1 ROMs. So far, my work on 2.1 has been going well, except I cannot seem to get Android Market to install. I have tried re-signing the apk file, but the result is the same.
Can someone help me out on this? This has probably been answered before, but I cannot find anything truly relevant to this question. Any help is greatly appreciated.
Click to expand...
Click to collapse
Have you tried just pushing with adb? By development do you mean cooking or compiling your own?
Please be respectful of others ...
I taken the time to cleanup this thread and move to Q&A where it should have been. If someone has an answer post a reply; plans to respond using trolling tactics are ill-advised.
If the thread goes OT again, a moderator will be forced to close it and likely remove it ... would be nice if it didn't have to come to that.
Regards,
I am building this directly from AOSP, from scratch. Thanks to the mod for cleaning up the flame war, by the way
Oh, from AOSP. How are you adding them in? AOSP does NOT include the Google Apps by default, I'm not expert in ROM building but I am sure there are some .libs needed (I know GTalk requires some) and possibly need the other Google Apps as well.
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
./adb install alpha-1-signed/system/app/Vending.apk
898 KB/s (1274068 bytes in 1.384s)
pkg: /data/local/tmp/Vending.apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Click to expand...
Click to collapse
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
EDIT: For all of you who are currently viewing this thread, how many of you would like a very fast (possibly faster than OpenEclair), stable, no-frills Android 2.1 ROM? I would like your opinions, because this will give me a good idea of how many people would be interested in this kind of thing.
Tekgek
tekgek said:
And this is why I love this place . What you said about libraries and what carz12 said about adb helped a lot.
Here is what I knew:
AOSP does not include the Google Apps, including the market. The market is somewhat difficult to install to an aosp build, and I think needs to be resigned with another RSA key.
What the forum helped me figure out:
The advice about trying the adb shell gave me some help. When I tried to push the market app to the phone, I got this:
This tells me that I am missing some libraries. But I'm also missing some other stuff. I'll recompile from source, install the libraries, and report back after I flash this to the phone. Until then, if anyone thinks any of my conclusions are wrong, please tell me so I don't waste my time, or yours.
Tekgek
Click to expand...
Click to collapse
It's good to know that you are missing libraries
Your best bet is to compile your rom, and then compare it to a rom that already has the google apps included (WesGarner build, CSDI, etc...) and see what libs are missing from yours, add them in and then try again
I was having the same problem too. I am gonna try this too.
And ya besides the libraries, the aosp build doesn't include some of the framework files and permission files too, like the framework files relating to gtalk and google maps should be added as well to the system/framework folder and the permission files in system/etc/permissions relating to gtalk and maps should be added as well.
I tried with all the missing libraries but with no luck...there must be some other files tooo. Gonna continue on Thursday.
Did you try resigning the apk file?
Not really. I am gonna try that too. Got coll tomorrow so may be later tomorrow. By the way did you got the video working?? I tried pushing some libraries from supereclair. But not workin till date. it works in his build though.
College is more important than android, imho. whenever you get the chance .
I hope to get video working in the future, but not right now. My primary computer (the core i7 rig I use for all my computer work) needed an OS reinstall, so I have made no progress since my post on ADB. My fist priority is to get the basics working, then I'll work on the other issues, like video playback and the camera. However, as of right now, I am re-downloading the source, and hopefully building it in the very near future, expect an update tomorrow, and maybe even a finished product (keep in mind that this is ALPHA, so don't expect anything wonderful).
Alright, I got it... mostly. The market appears installed, now all I need to do is make it not crash. Whenever I select the market app, I get a white screen, and then the home screen. I'm also getting a force close on the gapps process. What am I doing wrong
How did you got market show up???
The gapps framework file is also missin in the /system/framework folder in AOSP build.
Did you tried pushing the missing file?
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
tekgek said:
I downloaded openeclair, pulled all the apps that had the word google in them, resigned the the market with another key, integrated them into a rom package, flashed, and voila, the market appears. I also added in a couple framework files, but I think I'm still missing something. Do you know what the name of the file is? I'm not sure what or where it is.
Click to expand...
Click to collapse
ya its com.google.android.gtalkservice.jar
okay, added it in, still getting a force close on the gapps. Where to go now???
As i mentioned earlier there are some files missing in system/etc/permissions. Did u tried pushing those files.
All permission files are in place, all gapps are resigned. The framework is in place. The setup wizard i also resigned, which now crashes. If anyone has any suggestions please post them. I am at my wit's end here.
**NOTE FOR VEGAN TAB USERS** Steps 1-5 are no longer necessary for you, as the build.prop file in your /system directory has a working market fingerprint out of the box. Just apply the standard Market Fix (steps 6-8) and you are good to go.
I've seen several people complaining that the "full market" we had on G Tablet after the established market fixes wasn't quite full. Well, I've solved that problem, through a mixture of reading what others have done with other devices and experimentation. I will not promise that this gives you *everything*, but I do believe it gives you apps that otherwise required the release-keys status. Some of the apps you get may of course not work. But several applications I looked for before (TV.com for example, with streaming CBS video content) were not available with the previous market fix, and are now available with this fix. In fact, TV.com even works, except for a very minor video glitch in the upper left corner of the screen, and it's a cool app to get some quick streaming video content going on your G Tablet.
**NOTE** I take no responsibility for you screwing up your G Tablet. Please backup your system in Clockwork Recovery before doing any of this!
**EDIT** Removed unneccessary steps after feedback in this thread. Process is now very simple. Edited step 1 to clarify you need paid version of Root Explorer.
Here's how to do it:
0) Backup in Clockwork Mod. Please. I don't want you mad at me if this messes up your ROM.
1) Get the paid version of Root Explorer installed on your G Tablet. Apparently the free version lacks a text editor. If you only have the free version, the text editing step will need to be done in a separate program, or you will need to copy build.prop to your desktop, edit it there, and copy it back. Or use adb to push an edited build.prop to your tablet. Just buy Root Explorer though, it makes this very easy.
2) Browse in Root Explorer to /system. Then click on Mount R/W.
3) Long click on build.prop and click on Open In Text Editor.
4) Scroll down to the line ro.build.fingerprint=....
You are going to replace that with the following text:
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O.
6) Now you are going to re-do the original Market Fix. I used the simple version illustrated here: http://www.youtube.com/watch?v=7l-nySibzeA&feature=related First, make sure Market is running, and browse around in it for a few seconds. If you don't do this, there may be no cache to clear and for some reason the market fix may not work. Then, go to Settings->Applications->Manage Applications->Running and scroll down to Market. Then hit Clear Cache, followed by Force Stop **DO NOT CLEAR DATA FOR MARKET, JUST CACHE**. Then go back, scroll down to Google Services Framework, hit Clear Data, then Force Stop.
7) Now try starting Market again and you get the famous Market Error. Now shut down the G Tablet, then turned it back on. Wait for Wifi to connect to your network before doing anything! I forgot to do that on the first try, so I rebooted again, waited for wifi to connect this time.
8) Now restart Market again. It seems to have sourced the fingerprint from build.prop somewhere in steps 6-7. Searches for previously missing apps now show up. Voila! A truly full market!
And steps 6 and 7 can almost certainly be replaced by the equivalent steps using Titanium Backup that I know a lot of people have been using, particularly with TNT Lite. I am running ZPad 2.2 here, so YMMV with TNT Lite. Please keep me informed if this works/doesn't work for you if you try it!
Credit goes to: Paul at Modaco for hacking on the Advent Vega and making the Market work fully on that device and for coming up with a working build.prop for the Advent Vega, Roebeet for inspiring me to look at the Vega ROM stuff with his current work on the VEGAn ROM, Rothnic for his excellent work on the ZPad ROM that I'm currently using. Basically, I'm just hacking and slashing here, this wasn't any sort of rocket science.
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
roebeet said:
Paul from Modaco is awesome -- and you are as well, for making this post!
Any apps in particular that you found after this, that were missing before? I might want to try this on my device. Thanks again!
Click to expand...
Click to collapse
The only specific things I can tell you off the top of my head are TV.com which I know wasn't there because I searched for it a few hours ago. Also, I tried searching Market for Handcent before and found 14 or 15 results, and after this process I was able to retrieve 24 results.
There were a bunch of random apps I saw in the Top Apps list that I don't remember seeing earlier today. So that was enough to convince me that most of the missing 10-20% of apps are there now.
And thanks for the compliment, especially coming from the guy who made the G Tablet useful!
short/y said:
FWIW my Nexus One running a CM 6.0 nightly from 2 days ago has
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Note the more up-level version (2.2.1) and build (FRG83). I haven't tried this on my GTab yet but I will as soon as I can get it up and running.
Click to expand...
Click to collapse
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
rcgabriel said:
I'm sure that will work too, though the FRF91 build string seems to match the existing data in the ZPad ROM at least. I'm guessing the two signatures will produce essentially identical Market results.
Click to expand...
Click to collapse
Yeah. I may be somewhat overoptimistic going with FRG83. The build and version numbers identify the version of the system code so apps may read them and make some assumptions as to certain API characteristics. We're probably closer to FRF91 than FRG83 on TnT Lite.
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Is that from the Samsung Tablet? That may be closer to what we're really running.
short/y said:
Is that from the Samsung Tablet? That may be closer to what we're really running.
Click to expand...
Click to collapse
Yes this is Galaxy Tab. Probably better a Tegra tab once a full market one comes out.
I did the following:
1) Edited build.prop as described in step 4, rebooted and searched for tv.com - no results
2) I preformed the edits in step 4a, rebooted and searched for tv.com - no results
3) I stopped Market & Google Services Framework & wiped Google Services Framework, rebooted after getting Market Error, waited for wifi and opened Market to search for tv.com - no results.
I can't say if it works. I haven't had trouble finding apps, but I can't find tv.com before or after the steps above. Perhaps, I missed something.
Wait!!!! It does work. I tried again after posting and it's there! Thanks!
Is it possible to post the TV.com app? I don't want to do the mod but would love that app!
Great post man worked like a charm, I can get my slingbox app from the market now.
Edit: dammit I can't get the downloaded sling client to launch even after trying it many times which usually worked.
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
jdnyc said:
I'm going to give it a shot but being a newbie I'm not clear on this step:
5) Now you are going to click on Save and Exit. And then remount the /system directory as R/O
Will "remount as r/o" be an option to select at this point? If not, can you provide more detail.
The rest of the mod is easy enough to follow.
Thanks.
Click to expand...
Click to collapse
No worries its just a button on root explorer, download it and you will see it fairly quick.
NM..........
Fixed
Thanks works great
Can't get this to work. When I toto building.prop there s no option to open it in text editor. Only toopen as text. But then there is no way to edge the sentence.
ewitte said:
This one worked ok for me
ro.build.fingerprint=samsung/SGH-T849/SGH-T849/SGH-T849:2.2/FROYO/UVJJB:user/release-keys
Click to expand...
Click to collapse
Replaced this line only, did the Market fix via Settings and it worked like a charm. And Swype continues to work as well.
-=Sent from my ViewSonic G Tablet using Tapatalk=-
Worked perfectly thanks! Steps 4a and 6 are not necessary as you precicted
I searched the forums and the Nook forums specifically but could not find an answer (not that I would know if I saw one).
I am a pharmacy student and I was trying to install the Lexi-Comp app free trial. The app says that my device ID could not be found. I called their support line and they said only cell-enabled devices for Android were supported at installation because only they have a device ID.
Is there a way to add a device ID to the Nook so I can run this app?
I am running CM 7-080420011-NIGHTLY-encore.
I hope this is something simple. I am stupid about computers and I bought this thing expressly to use Lexi-Comp on rotations (there is no mention of cell-only Android devices anywhere on their website).
Eldric IV said:
I searched the forums and the Nook forums specifically but could not find an answer (not that I would know if I saw one).
I am a pharmacy student and I was trying to install the Lexi-Comp app free trial. The app says that my device ID could not be found. I called their support line and they said only cell-enabled devices for Android were supported at installation because only they have a device ID.
Is there a way to add a device ID to the Nook so I can run this app?
I am running CM 7-080420011-NIGHTLY-encore.
I hope this is something simple. I am stupid about computers and I bought this thing expressly to use Lexi-Comp on rotations (there is no mention of cell-only Android devices anywhere on their website).
Click to expand...
Click to collapse
Find the IMEI Generator and ROM patcher thread.... but I'd wait an hour or so... should be an update by then.
No worries about waiting an hour. I think it will take me all weekend to figure out what to do with that.
Eldric IV said:
No worries about waiting an hour. I think it will take me all weekend to figure out what to do with that.
Click to expand...
Click to collapse
Actually, its quite simple... just run the app... it will generate an IMEI for your nook.
You can use In Place (updating ROM already installed) or update a dev's ROM before flashing it (useful for nightlies)
DizzyDen said:
Actually, its quite simple... just run the app... it will generate an IMEI for your nook.
You can use In Place (updating ROM already installed) or update a dev's ROM before flashing it (useful for nightlies)
Click to expand...
Click to collapse
So, if I am understanding this, I:
1. Download the zip
2. Run the zip
3. Done?
I ran the zip (on my Nook) and it rebooted my Nook but nothing seems to have changed.
I see lots of mention to "adb" but I do not have that. Is it necessary?
Edit: So I managed to get adb(Wifi) established (greatly expedited thanks to the adbWireless app, as I was completely unable to install the Google USB drivers) and then ran the .exe in the zip on my PC instead of my Nook (I told you I was stupid about computers). Lexi-Comp is currently installing its databases on my Nook. The well-being of my patients has profited from your labors. I thank you kindly.
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.