Related
Enable Copy & Paste on the Nook Tablet
Background
The lack of copy & paste functionality on the Nook Tablet is one of the most annoying "features" of the B&N firmware and it affects not just geeks like me but also the average user. This thread and this thread are two of many, many threads complaining about the missing copy & paste. This thread proposes a "fix" by combining the Hacker's Keyboard and Swype, but is still really lame.
The method I will describe here solves the problem by replacing /system/framework/framework.jar which contains the code for Android widgets like text fields. I have merged into the stock /syste/framework/framework.jar the code responsible for copy & paste from the Android source code.
Instructions
Video walkthrough: http://www.youtube.com/watch?v=7V70a3FYbt4
0. Before you proceed, know that THIS IS EXPERIMENTAL SOFTWARE THAT PROBABLY VOIDS YOUR WARRANTY AND MAY PERMANENTLY OR TEMPORARILY BRICK YOUR TABLET. Even though it worked for me, it may not work for you, and worse, it is quite possible that it could cause your tablet to boot-loop or die. I AM NOT RESPONSIBLE FOR ANY POSSIBLE DAMAGES TO YOUR TABLET / ANYTHING ELSE CAUSED BY THIS METHOD. BY USING IT YOU AGREE TO ASSUME ALL RESPONSIBILITY FOR YOUR ACTIONS.
1. Your tablet needs to be rooted for this to work. If you have not rooted it yet, search this forum for instructions.
2. Since we will be copying files to /system, you will need to install ES File Explorer or Root Explorer or whatever other app that allows you to do that.
3. Download the file that corresponds to your OS version from below:
1.4.2 (16GB/8GB): http://www.mediafire.com/?5pf2aegq02194lq MD5: ef35d35daffd0d9574f48a43ccc4b58c1.4.0 (16GB): http://www.mediafire.com/?es6gd31wzr7yk8a MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
The 1.4.0 version has been reported to cause boot loops for some people, while it has worked for others. You have been warned.If you're on a different OS version, post the file /system/framework/framework.jar form your tablet and I will make a package for it.
4. Extract file contents to microSD card, and insert microSD card into the tablet.
5. Using ES File Explorer / Root Explorer, copy the extracted file framework.jar.new to the directory /system/framework/. (If you're using ES File Explorer, make sure "Up to Root", "Root Explorer", and "Mount File System" are checked in settings.)
6. Copy the extracted file uim-sysfs to /system/bin/.
7. Go to /system/bin/, and change the permissions of the file uim-sysfs to executable. (If using ES File Explorer, long press -> Properties -> Change -> Check everything under "execute".)
8. Power off tablet and power on again. The tablet should take much longer to boot this time than normally, so no need to worry. When the tablet boots up, you will most likely see lots of force close dialogs. This is normal.
9. Wait one minute. You could be stuck in a boot loop if you don't wait.
10. Power off tablet and power on yet again. This time it should also take much longer to boot; the boot times will return to normal after several reboots.
11. Profit.
Force close issues
The first time you run some (read most) apps after applying this hack would likely result in force closes. While annoying, there is no way to get around it due to how the Dalvik VM caches references to /system/framework/framework.jar. In addition, every time you install new apps or update apps, you will have to reboot the machine before those apps are usable; you will get a force close when you try to use those apps until you reboot.
The solution is simply to reboot your tablet each time you get a force close error from an app that worked fine before this hack. The force close error for that particular app should go away following a reboot. If you get a force close from another app after that, just reboot again.
How it works
The information below is for people interested in understanding how this stuff works. If you just wanted to enable copy and paste on your tablet, you can stop reading.
This hack is based on the exploit explained at http://forum.xda-developers.com/showthread.php?t=1534518. The uim-sysfs script in the attached file saves the stock /system/framework/framework.jar, copies over my modified framework.jar.new, and restarts the zygote process. After the zygote process has loaded my framework.jar.new, the uim-sysfs script restores the stock /system/framework/framework.jar so that /init will not bail on the next boot.
To enable copy & paste in /system/framework/framework.jar, I decompiled the stock implementation and merged in related code from AOSP. The two classes I changed are android.widget.TextView and android.widget.EditText. For android.widget.EditText, I simply used the AOSP implementation because the only difference between the two was in the enabling of copy & paste. I manually merged android.widget.TextView because there appears to be B&N enhancements in it in addition to disabling copy & paste.
The exact steps I took as well as a diff of my modifications are documented in post #12.
Disclaimer
Again, this is experimental software. That it worked for me does not mean it will work for you, or that it won't brick your tablet. I am not responsible for any possible damages resulting from using this method.
Here i post framework.jar from stock 1.4.0 rooted
~ Veronica
lavero.burgos said:
Here i post framework.jar from stock 1.4.0 rooted
Click to expand...
Click to collapse
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
16gb Nootlet with 1.4.0 rom, rooted, OTA blocked yada yada.
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
Lots of FC, the last persistent one was the launcher (ADW ipaidforthis version)
Powered off and on again after waiting way longer than 1 minute.
Second boot forever at "read forever" screen so far.
If it comes back to life I'll try the 1.4.0 version & let you know.
[Edited to add}
... time passes ...
Any way out of the "ADWLauncherEX" force-close loop? Does Android have a "safe mode" boot option like Windows? (sorry)
No, I haven't installed CWM recovery yet. Remind me to do that if this thing ever gets over its mental breakdown.
jichuan89 said:
OK. Looks like the framework.jar from 1.4.0 is different from 1.4.2; I've merged in the same changes. If you're feeling brave, the package I've made for 1.4.0 is here.
MD5: 99d2e7eff173fbdc77c79b4f4a6ff53c
Can you confirm whether this works?
Click to expand...
Click to collapse
Thanks can't test right now 'cause im finishing another project and then i have to test the tun.ko module for CM9 busy bee .
~ Veronica
cellhead said:
Stayed at the "read forever" screen almost forever, then finally started up. Fellow victims take note, it isn't dead so be patient.
...
Second boot forever at "read forever" screen so far.
Click to expand...
Click to collapse
Thanks for mentioning this. Will add to instructions.
cellhead said:
Any way out of the "ADWLauncherEX" force-close loop?
Click to expand...
Click to collapse
Getting FC's is normal - as the instructions state you probably have to reboot a number of times before all FC's disappear. Any luck so far? If not, please let me know and I will post a recovery SD card image that will allow you to undo this hack.
Also - as I said clearly in the instructions (Compatibility section), before you try this out on your 16GB, you should post your /system/framework/framework.jar so I can verify that this works on the 16GB. I don't have the 16GB tablet so I don't know if this works on it at all. Anyone?
Thanks. You may want to feature the version info prominently in the OP. I got my issue solved in a roundabout way when it finally went into a boot loop and triggered the factory reset. That got me back to 1.4.0 unrooted, and without the FC problems. Reran indirect's rooting script and I'm back to some semblance of normality.
Ain't complaining, I took on the risk of trying your copy/paste fix and went on an unplanned adventure. Such is life as a RL software tester ;-)
I'll wait and see how things shake out. You're onto something good here, so once it's a little safer for the normals to apply it, I'll give another go.
For the record, 16g Nook tablet, rooted via indirect, OTA blocked, v1.4.0
cellhead said:
You may want to feature the version info prominently in the OP.
Click to expand...
Click to collapse
You're right...really sorry about that.
On the other hand, did you try the files in the original post, or did you use the files for 1.4.0 I posted in the 3rd post?
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Sent from my BNTV250 using xda premium
cellhead said:
The ones in the original post. Then I read the third post, but was unable to get it to boot far enough that I could replace the files and try again.
Click to expand...
Click to collapse
The files in the original post are modified from 1.4.2 and would most certainly not have worked on 1.4.0...I should have made that clearer. Sorry.
The files in the 3rd post though are modified from 1.4.0 (thanks to lavero.burgos) and should work for you. Any chance you could test them out?
--- EDIT ---
Also - I've made a bootable SD card that will remove this hack and fix the tablet even if something goes wrong and you cannot boot into the system to remove the files directly. I can post it if someone needs it.
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
pfalcon said:
Cool hack, but why all these doubts and asks for 16gb's framework.jar ? What users have on devices comes from vendor firmware package(s), and you can see at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Tablet/379003187/ that there's no separate versions for 8gb vs 16gb. That page (and pages for other releases) should be also the authoritative place for getting framework.jar .
Click to expand...
Click to collapse
Thanks for the link! I went and downloaded the update archive and extracted it, and can confirm that the /system/framework/framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2., which confirms my hypothesis in posts #11 and #14 in http://forum.xda-developers.com/showthread.php?t=1517513&page=2. The bizarre thing is that if you unzip the files they produce the exact same content; it looks like they differ only in some sort of signature. But this means that my framework.jar will work on both the 8GB and 16GB on 1.4.2. So thanks again for the link!
pfalcon said:
On the related note, would you care to provide exact instructions how to make framework.jar with c&p functionality? That would help to keep it updated across vendor upgrades, and also for making sure that new framework.jar contains only changes related to c&p and nothing else ;-). Granted, such instructions would be long and boring, so writing them in the shell script language rather than English would be a good idea ;-).
Click to expand...
Click to collapse
What I did was this. You need zip, unzip and a tool called apktool. I'm assuming the framework.jar from the Nook is called ~/framework.jar.nook and the framework.jar from vanilla Android (AOSP) is ~/framework.jar.aosp.
1. Extract framework.jar into a directory z:
Code:
$ unzip framework.jar -d z
2. Use apktool to disassemble framework.jar.nook:
Code:
$ apktool d ~/framework.jar.nook
3. Disassemble framework.jar from AOSP.
Code:
$ apktool d ~/framework.jar.aosp
4. Compare and modify framework.jar.nook.out/smali/android/widget/{TextView,EditText}.smali against framework.jar.aosp.out/smali/android/widget/{TextView,EditText}.smali. My diff file can be downloaded here. Apply diff with
Code:
$ cd framework.jar.nook.out; patch -Np1 < jichuan89_nook_text_hack.diff; cd ..
5. Recompile Nook's framework.jar:
Code:
$ apktool b framework.jar.nook.out
6. Repackage modified Nook's framework.jar into ~/framework.jar.new
Code:
$ cp framework.jar.nook.out/build/apk/classes.dex z/classes.dex
$ cd z; zip -r ~/framework.jar.new META-INF classes.dex preloaded-classes; cd ..
framework.jar in that archive (which I'd assume is the same as on the NT 16GB/1.4.2) is different from the same file on my NT 8GB/1.4.2
Click to expand...
Click to collapse
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b. Anyway, good news that contents were the same in your case too. It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
What I did was this.
Click to expand...
Click to collapse
Thanks for the instructions and the diff! I with that all hacks posted on the forum came in such form ;-)
pfalcon said:
I just tried to compare framework.jar I have on my device after 1.4.2 OTA update vs downloaded from B&N site - they turned out to be the same, md5sum is 795ae49e2b05b05c999a424a7d84b36b.
Click to expand...
Click to collapse
Nice - thanks for confirming this. That's really helpful to know.
pfalcon said:
It might be that 8Gb's initial in-flash 1.4.2 indeed was packaged differently than 16Gb's 1.4.2 update (that's idea somehow backed by the fact that 16Gb's initial in-flash 1.4.0 is not available on B&N site). Again, good to know that actual contents are the same, so 1.4.3 would be common either (which makes full sense, otherwise B&N just makes it harder on themselves).
Click to expand...
Click to collapse
Right - it would make economic sense for B&N to make the software on the two tablet models to be as close as possible. I do hope they'll make their and our lives easier by just using the same version of the same damn files in the next update for the two models, as you said.
Sent from my Nook Tablet using XDA
I can make CWM flashable zip with original framework.jar for the ones having troubles until is fully tested. Tomorrow i'll jump back to stock 1.4.0 to test this hack and report back.
~ Veronica
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
CRE said:
A flashable zip would be cool if for no other reason than simplicity and reduced panic on the part of newcomers and when re-flashing the stock ROM.
I'm going to try this, so with me luck, but first: Do I need to boot into CWM to do this?
Click to expand...
Click to collapse
No - this is for the stock firmware. CWM should have copy & paste already because it doesn't use B & N's framework.jar.
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
CRE said:
CWM as in ClockWorkMod not CM7 as in CyanogenMod v7.
EDIT:
To clarify, I didn't know if I could do this while the NT was booted normally or if I needed to boot with ClockWorkMod to ensure that the OS didn't try to access that file.
Click to expand...
Click to collapse
No. If there were requirements I would have put them in the instructions. It doesn't matter how you boot.
Sent from my Nook Tablet using XDA
Thank you. I guess I'll repartition first then get this out of the way too.
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
johnwaynegacy said:
I would like to opt out of the alleged ota. I renamed my otacerts.zip file, is that enough. I have read all sorts of things, from what I have done, to changing the build fingerprint in the build.prop. Is what I have done enough. I am obviously using the stock rom.
Click to expand...
Click to collapse
probably delete the OTA apk files in /system/app
con247 said:
probably delete the OTA apk files in /system/app
Click to expand...
Click to collapse
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
johnwaynegacy said:
all I saw was htcCOTAclient.apk and .odex and I renamed them, thanks. Hopefully I don't get annoyed by the update notification.
Click to expand...
Click to collapse
I deleted those from my /system/app directory. The previous OTA did not ever come through my phone, so I think you'll be OK.
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
Good call!
instructions, pls?
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
krelvinaz said:
On the Kindle Fire, the easiest way to prevent the OTA which is a forced update (you don't get a choice), was to remove the /system/etc/security/otacerts.zip file. Physically moving it elsewhere (like to the sdcard) worked.
I note that the Rezound has the same files.
Click to expand...
Click to collapse
i just did this on rezrom, thanks!
why is this file included with a custom rom?
michaelbsheldon said:
Can someone who knows ADB give short recipe/commands
to reach that OTA file we want gone, Please.
Click to expand...
Click to collapse
If for what ever reason you cant use root explorer and do have busybox (i think you need it) installed
It has been a really long time since I have used adb for anything, but this should work unless it denies you because system is mounted as read only.
adb shell
su
rm /filepath/file.apk
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
FabianaS said:
I am also looking to block this "alleged update" BUT am completely stock right now.. have been holding off on doing anything so far.. How would I do this?
Click to expand...
Click to collapse
If you are stock unrooted, the best you can do is to say no if it asks. If for some reason it is a forced OTA, I don't think you can without staying in airplane mode.
Via Rezound using XDA Premium
Thanks, that is what I was wondering, if it asks or if it's forced? I don't remember how my past updates have been and for some reason I feel like they were forced!?!
This is NOT made by me
Most of the guyz may have came across this.
Original Thread
http://forum.xda-developers.com/showthread.php?t=1574401
Click to expand...
Click to collapse
Click here to thanks rovo89
Click to expand...
Click to collapse
What is xposed installer?
It is a framework!
It allows you to install little apps by which you can mod your XL.
Read Advantages for more info.
Only you will be responsible if anything happens to your phone!
Advantages:
No need to modify any APKs. This means:
No need to decompile, change things in smali, compile, sign, ...It will work for odexed and deodexed ROMs.Your mod is not bound to a specific version of the ROM. Unless there is a major change in the methods called for a certain functionality, your mod will continue to work even when you upgrade your ROM. Hell, it will probably even work with different ROMs.Multiple mods can be installed at the same time, even if they change the same package. So you can use these battery icons and those quick toggles. Even hooking the same method twice is possible. Of course, this only works properly if the mods are not trying to do incompatible things.
It does its magic at runtime. That means you can implement options to let the user decide if they prefer the bikeshed to be painted in red or blue. Or you can have some extra logic for certain ROMs without building different mod versions.
It can be disabled easily without having to reflash.
It's open source.
Download:
You can download the installer from the attachment or from thread mentioned above
How to install:
First step for everything you do: Create a nandroid backup and make sure you know how to restore it!
There is also the risk to soft-brick your device. In such a case, restoring a backup is the easiest way to get rid of it
Download XposedInstaller.apk and install it
Launch the Xposed Installer and click on "Install/Update"
Reboot
Done!
In case you get into a boot loop:
You can flash the attached Xposed-Disabler-CWM.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
You could also create a file /data/xposed/disabled, which causes Xposed to be bypassed as well.
Modules:
You can find modules collection here-
http://forum.xda-developers.com/showthread.php?t=2327541
Click to expand...
Click to collapse
Installation process-
Download .apk and install it
Launch the Xposed Installer and go to the "Modules" tab (you will also get there if you click on the notification warning you that the module is not enabled yet)
Enable the module by checking the check-box
Reboot
Done!
Please let me know which Modules are working perfectly on Canvas 2 and I will add in my post
Download Section
1. XposedInstaller_2.1.4_apk
2. Xposed-Disabler_CWM
Please let me know which Modules are working perfectly on Canvas HD and I will add in my post
ENjOy...!!
Don't forget to hit the thanks button for sharing this and rate 5star..!
Working module list
I don't have Canvas HD so please let me which module is working and I will add those here!
Full collection
http://forum.xda-developers.com/showthread.php?t=2327541
Click to expand...
Click to collapse
Installation guide of microG services in three ways:-On ROMs with signature spoofing option.
-On Deodexed ROMs without signature spoofing option.
-On Odexed ROMs without signature spoofing option.
I'm using win10 all the time here, and this guide is for Nougat ROMs only.
Hi everybody! Two months ago I discovered the awesome world of microG, a life without original google play services, without any of my data on google and with better battery life (we all know how google services drains battery). For more general information, refere please to these threads and forums:
https://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616
https://microg.org/
https://shadow53.com/no-gapps/
Today I present you my guide (none of this work is done by me, I'm just showing the way I install these services) to install microG features.
The first thing we need is a ROM without gapps included. Then is needed to know if it supports signature spoofing out-of-the-box, you can see if the ROM is present on this list: https://forum.xda-developers.com/android/general/index-list-custom-roms-offering-t3557047 or ask developer in his own thread. If it supports it, you can directly go to the instructions num 1) . If else, you need to know if the ROM is odexed or deodexed, for this, you can ask on the dev thread or unpack the rom yourself.
How to unpack the ROM:
You can unpack it with 7-zip and then decompress it with this tool: https://forum.xda-developers.com/android/software-hacking/tool-tool-unpack-repack-dat-img-v2-0-t3284806. You must place the system.transfer.list and the system.new.dat you'll find in the decompressed folder in the Input_dat folder of the tool given, then open the tool with usage permission and mark option 1, then wait until process is finished and you'll have the output in the System_unpack folder.
Then you only need to go to the /system_/framework/ folder and see if there's any arm, arm64, folder with .oat files inside. If there isn't, congratulations, your rom is deodexed and you can follow path 2). If there is any of these folders mentioned with .oat files, your rom is odexed, and you'll need to follow path 3).
Note: on all this process we will be using the @Shadow53 files placed on https://shadow53.com/no-gapps/downloads/, I personally use the "microG with playstore" and the "calendar and contacts" flashable zips (I've modified the calendar and contacts zip because of some issues with sync that i don't know if were solved, I let the modified flashable zip later in this post) please, before asking or complaining, read his page fully, his work is awesome.
1) ROMs with signature spoofing option:
This is the easy way. We only need to install the clean ROM and then flash the microG and the sync packages we've donwnloaded before. Once booted, we only need to active signature spoofing option and check microG Self-Check and we are ready to go. In order to install backends for network location, please, refer to proper threads.
2) Deodexed ROMs without signature spoofing option.
Here we will follow the steps as if we had a signature spoofing option (as the previous paragraph) but obiously we won't active nothing when booted and we will use this tool: https://forum.xda-developers.com/android/development/tingle-fork-needle-t3438764 (please, read carefully before asking) if your ROM is deodexed and you follow the steps carefully, you'll have patched the ROM in a few minutes. Then you just need to reboot and check with microG Self-Check.
3) On Odexed ROMs without signature spoofing option.
This is my "original" way, as nobody explained fully how to do it. Here, you need to deodex the framework folder and then flash the rom with the tingle patch already applied. Let's begin.
First, you need to get the /system_/framework and the build.prop you unpacked when checking if the rom was or not odexed. Then you need to deodex it by using this tool https://forum.xda-developers.com/android/software-hacking/tooll-03-12-fulmics-deodexer-1-0-t3512081 (I have to say sometimes it only works for me the 1.1 version) it's easy, you'll need to download the tool and the backsmali, smali 2.2 or later (already compiled in .jar, I let them later in this thread) and run it.
Once you have the framework deodexed (erase the arm, arm65 and oat folder if there is any left) you just need to get the framework.jar and patch it with tingle (option 2 in the script, the patched file will be in the output folder), then replace the patched framework in the deodexed framework folder.
Now you just need to pack it in a flashable zip that must erase the current framework folder of your ROM and then place the one you deodexed, for this, I let you all a flashable zip I made modifying the one the ZIPme app made. Yo must unpack it and replace the framework folder in "system" with the deodexed one with the patched file and repack it.
Then you just need to flash the clean ROM and afte that the framework-replacer.zip and all microG flashable zips you need, once booted you can directly check microG and you'll se it is already patched.
Suggestions are welcome on this guide!
Many thanks to all devs and people made all this possible:
Marvin for microG.
Shadow53 for his guide and flashable zips.
ale5000 for tingle.
xpirt for fulmics deodexer.
Kritsada Chaitan for his unpacking tool.
Primokorn for his signature spoofing support list.
JRummy Apps for ZIPme.
kevinkvothe (I gess)
Anyone else feeling he/she should be on this list, please, tell me.
Downloads.
https://mega.nz/#F!id1jlZoS!6Su8IJeGQnYO_3olQmQMTg
Reserved
Pole
Thanks for the concise, resource-rich guide. I've been trying to patch an odexed ROM for the past few weeks, and never thought to try and flash it with the patched framework.jar. Cheers! I'm going to give this a try first thing tomorrow!
Thx for this guide, worked for me...
Best regards
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
That was one hell of a long ride but I got the signature spoofing working.. Thanks a lot.
I got the Error [RH-01] with play store but after rebooting it was fixed somehow.
ikzouhetnietweten said:
That was one hell of a long ride but I got the signature spoofing working.. Thanks a lot.
But my Play Store aint working! it says Error [RH-01] , I tried everything from deleting cache, data, enabled google device registration in micro settings, enabled google cloud messaging.. etc etc Everything is checked in Self checked.
Click to expand...
Click to collapse
Enable "Google device registration" in micro settings, then clear data of Play Store, termintate it and remove it from recent apps.
Then run it again.
ale5000 said:
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
Click to expand...
Click to collapse
I tested it once, when I started to learn about microG and it didn't work, but I'm not sure all was working and if I had signature spoofing support so... I'll test it when possible.
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit.
ale5000 said:
@kevinkvothe
Hi,
have you tried my Google Sync Add-on?
It would be nice to know if it is working for everyone.
Click to expand...
Click to collapse
thank you
xiiihyou13 said:
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit.
thank you
Click to expand...
Click to collapse
It depends what you mean, both are flashable zip so as simplicity should be the same.
kevinkvothe said:
I tested it once, when I started to learn about microG and it didn't work, but I'm not sure all was working and if I had signature spoofing support so... I'll test it when possible.
Click to expand...
Click to collapse
In the latest version I have fixed permission problems, so it will most likely work out of the box.
xiiihyou13 said:
Hi all,
I'm using RR + Magisk + NanoMod which can achieve this faster. However, I was dumbfounded when I couldnt get sync properly to work, however flashing the google sync adapter work. I urge anyone who want to use microG to use nanomod version, as it is simpler. you only have to flash via twrp and let it sit
thank you
Click to expand...
Click to collapse
But unfortunately Nanomod Patcher does not work on odexed and deodexd ROMs, I don't know yet if mine is odexed or deodexed but will have to check It's the unofficial LinageOS 14.1 for lt03lte - the official nightly does unfortunately not detect my external SD Card!
Juat FIY, now that nougat supports xposed, this is much easier when using Fakegapps module [emoji106]
Lähetetty minun MI 5 laitteesta Tapatalkilla
Seems like noone mentioned this but microG have own fork of LineageOS with already build in microG services.
https://lineage.microg.org/
Only for OP7T PRO MCLAREN EDITION (5G) T-MOBILESomeone is experiencing issues in android 11 in op7t pro MClaren Edition 5g (T-mobile). If your phone is bricked or you want to downgrade to stock android 10 - please follow the procedure below.....
1. Download the zip from here - op7t pro mclaren 5g - android 10
2. Unzip it.
3. Install qualcom driver from L2 drivers folder (If needed)
4. Run as administrator - MSMdownload Tool v.4 - from hotdogg_13_A.01_210311_repack folder.
5. Log in as other.
6. Power off your device . Hold volume up and down together and connect usb through original usb cable || You will be connected in EDL mode.
7. If com port is connected than start the flash from above left corner.
Tips : If com port is not connected try to power off your device and try again to enter into EDL mode (Do that until com is connected) .
TRY THIS TO DISABLE UPDATE:
adb shell pm disable-user --user 0 com.oneplus.opbackup
This information has been posted in another, much more detailed thread for over a year...
And I wouldn't trust that file either
Suspicious, no?
I have provided the official stock and final android 10 rom. Thank you.
and how do you then disable the updates? from being pushed to you
botN3t said:
and how do you then disable the updates? from being pushed to you
Click to expand...
Click to collapse
Turn on developer options tapping build number constantly and than turn off automatic update there. That's it, enjoy.
Nabil Prodhan said:
Turn on developer options tapping build number constantly and than turn off automatic update there. That's it, enjoy.
Click to expand...
Click to collapse
That doesn't work anymore; that's why everyone is complaining that they are being force updated to OOS11.
I know there's a better way, such as finding the right app and disabling it, but you can block the host it gets the updates from using an adblocker like AdAway. Updates come from
https://android.googleapis.com/packages/ota-api/
so if you block that (add it to your hosts file), you should be good.
starcms said:
That doesn't work anymore; that's why everyone is complaining that they are being force updated to OOS11.
I know there's a better way, such as finding the right app and disabling it, but you can block the host it gets the updates from using an adblocker like AdAway. Updates come from
https://android.googleapis.com/packages/ota-api/
so if you block that (add it to your hosts file), you should be good.
Click to expand...
Click to collapse
I try to add to host but it still download update any another way or web i can use ?
meovoz said:
I try to add to host but it still download update any another way or web i can use ?
Click to expand...
Click to collapse
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Edit: The "correct" way of stopping it would be to find the service which controls updates and kill it. But since I've not an issue with OOS11 (it actually fixed my broken SA 5G and HD call functionality that I lost due to using the NSG app. MSM restore and persist restore couldn't fix it. Never ever install that app on this phone) I never looked into it.
starcms said:
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Click to expand...
Click to collapse
Well if i add https://android.googleapis.com/packages/ota-api/ it still can download but if i add https://android.googleapis.com/ it will not but it also can't signin google acc anymore
meovoz said:
Well if i add https://android.googleapis.com/packages/ota-api/ it still can download but if i add https://android.googleapis.com/ it will not but it also can't signin google acc anymore
Click to expand...
Click to collapse
Omg, are you serious? That's obnoxious. But you should be able to block only the full url successfully. What AdBlock app are u using?
And see my edit in post above
starcms said:
That's the only simple way I could think of making it impossible to download the update so it would then just fail to update. You sure you have the option on in Magisk settings in addition to whatever app you are using?
Edit: The "correct" way of stopping it would be to find the service which controls updates and kill it. But since I've not an issue with OOS11 (it actually fixed my broken SA 5G and HD call functionality that I lost due to using the NSG app. MSM restore and persist restore couldn't fix it. Never ever install that app on this phone) I never looked into it.
Click to expand...
Click to collapse
Is there anyway to view what correct host it connect to
starcms said:
Omg, are you serious? That's obnoxious. But you should be able to block only the full url successfully. What AdBlock app are u using?
And see my edit in post above
Click to expand...
Click to collapse
I use adaway to block it
meovoz said:
I use adaway to block it
Click to expand...
Click to collapse
Yep, that's what I use and was gonna suggest...
Hmm, hehe, try this...
It downloads the OTA package to
/data/ota_package/payload_metadata.bin
If there's a file there, delete it, then create a blank file named payload_metadata.bin and remove all permissions from the file (--- --- --- or 0000) so the system can't overwrite it.
starcms said:
Yep, that's what I use and was gonna suggest...
Hmm, hehe, try this...
It downloads the OTA package to
/data/ota_package/payload_metadata.bin
If there's a file there, delete it, then create a blank file named payload_metadata.bin and remove all permissions from the file (--- --- --- or 0000) so the system can't overwrite it.
Click to expand...
Click to collapse
It only have metadata and payload_properties.txt
meovoz said:
It only have metadata and payload_properties.txt
Click to expand...
Click to collapse
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
Well i never create a magik module
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
Is there anyway to view where it download from i still like the way block with host file
meovoz said:
Is there anyway to view where it download from i still like the way block with host file
Click to expand...
Click to collapse
It downloads a long, "random" named file from https://android.googleapis.com/packages/ota-api/ I told you this already
starcms said:
Create a file named payload_metadata.bin and remove all permissions.
But here's a better plan:
Use Magisk to "over-write" systemlessly /system/etc/security/otacerts.zip with a blank file named otacerts.zip
Then the system can't verify the updates and they will fail
Click to expand...
Click to collapse
I did it let see it can last long
meovoz said:
I did it let see it can last long
Click to expand...
Click to collapse
Let us know!