Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Smali Patcher
WHAT THE HELL IS THIS THING? ::
To sum things up this is an application I developed that pulls the android framework from your device, applies what I (or other users) consider useful patches to the sourced files and then finally generates a magisk module applying the patches system-lessly.
The unique thing about Smali Patcher is it sources the framework files from your device, in an attempt to provide maximum compatibility across the entire android device family.
While I have your attention I wanted to throw out a massive thank you to all the people who have provided support to the project and the thread over the years, you guys are absolute champions. I can't thank you enough and couldn't have done it without you, here's to ya!
PATCHES ::
Mock locations - Hide mock locations status, allowing apps like Pokemon GO to treat them as genuine location updates.
Mock Providers: Allow creation of mock providers without mock permissions.
GNSS updates: Disable all GNSS (GPS) location updates.
Secure flag - Allow screenshots/screensharing in secure apps.
Signature verification (as-is, legacy support only) - Disable signature verification allowing modification/execution of signed system apps.
Signature spoofing (as-is) - Enable signature spoofing app permission.
Recovery reboot - Reboot directly back into recovery from powermenu.
Samsung Knox (as-is, legacy support only) - Bypass Samsung Knox trip protection, only confirmed working for secure folder.
High volume warning - Disable high volume popup dialog.
Any patches marked "as-is" are no longer maintained and only kept in for legacy device support only, not recommended to be used on newer android versions (10/11).. use at your own risk.
GPS SPOOFERS / FUSEDLOCATION / RUBBERBANDING NOTICE ::
FusedLocation API GPS spoofers are NOT compatible with the mock location patch.. your required to use a traditional GPS spoofer! Spoofed location updates will be fed into fusedlocation all the same, meaning you don't need to disable the service.. which means while your not spoofing you still gain the benefit of fusedlocation which is all around more accurate location updates!
REQUIREMENTS ::
PC with at least 3GB+ of RAM.
.NET Framework 4.7.1 or later installed
Java installed
Android device running 6.0 or above.
INSTRUCTIONS (ADB METHOD/AUTOMATED - RECOMMENDED):
COMPATIBLE WITH BOTH ODEX & DEODEXED ROMS! WILL AUTOMATICALLY DEODEX REQUIRED FILES IF NECESSARY.
Backup device.. safety first kids.
Enable USB debugging in developer settings on your device and connect via USB to your PC.
Authorise USB debugging connection on your phone.. example of popup.
Run "SmaliPatcher.exe", First startup will automatically download the latest necessary binary's.
Select your desired patches.
Hit "ADB PATCH" button (yes without browsing for a .jar file).
Once the process has completed, magisk module will be generated in the same directory as "SmaliPatcher.exe" named: "[email protected]".
Install the generated magisk module either in recovery mode or from the magisk app.
Enable smali patcher module in magisk.
INSTRUCTIONS (ALTERNATIVE METHOD - FOLLOW ONLY IF ADB METHOD FAILS) ::
Backup device.
Enable USB debugging in developer settings on your device and connect via USB to your PC.
Authorise USB debugging connection on your phone.. example of popup.
Run "SmaliPatcher.exe", First startup will download the latest necessary binary's.
Browse to your "/system/framework" directory. Easiest way to obtain these files is from your rom img/zip.
Select your desired patches.
Hit the "PATCH" button.
Once the process has completed, magisk module will be generated in the same directory as "SmaliPatcher.exe".
Install the generated magisk module either in recovery mode or from the magisk app.
Enable smali patcher module in magisk.
YOU ARE STILL REQUIRED TO HAVE A DEVICE CONNECTED TO YOUR PC IF YOU USE THIS METHOD.. THE PATCHER WILL NOT PROGRESS OTHERWISE.
A ADB DEVICE IS REQUIRED TO EXTRACT CDEX FILES.. IF YOU'RE PARANOID/SAVY ENOUGH, YOU CAN USE A ANDROID EMULATOR.
BEFORE REPORTING ANY ISSUES ::
You have tried running the patcher as administrator.
You have accepted the USB debugging connection & ticked "Always allow from this computer".
You have tried running the patcher with phone booted in recovery mode with /system mounted.
shoey63 said:
Adb method works flawlessly on android 8.1 for Sony AOSP roms on X and XZ premium. The trick is to run the program in recovery (with system mounted obviously), to avoid permission issues.
Awesome tool!
Click to expand...
Click to collapse
UPDATING MODULE INSTRUCTIONS:
Disable/uninstall any active smali patcher modules before generating a new one! If you generate a module with a older version active there's a chance the outdated patches will carry over to the new module.. I do my best efforts to prevent this, but it may still happen. Before reporting issues, make sure you have tried this.
CHANGELOG ::
7.4
Modified patch - GNSS updates: now correctly handles protected methods.
7.3
First pass of android 11 patch updates: mock provider, gnss update & secure flag patch updated.
7.2
Modified patch - Secure flag: revert a change I made, should solve issues on some devices.. hopefully.
7.1
New patch - GNSS updates: Disable all GNSS (GPS) location updates.
Modified patch - Secure flag: tested & working on Samsung devices running android 10.
7.0
New patch - Mock Providers: Allow creation of mock providers without mock permissions.
6.9
Allow devices booted in recovery mode through ADB check.
6.8
Made patches "compatible" with the latest android 11 beta (pixel).. none of which have been tested on android 11. BACKUP! BACKUP! BACKUP!
6.7
Removed "magisk-module-template" dependency.
6.6
Fixed patch - Magisk reboot: was not being applied when selected.
"Magisk reboot" patch renamed to "Recovery reboot".
6.5
Updated patch - Magisk reboot: now compatible with Samsung One UI 2.0 (android Q).
6.4
New patch - Samsung Knox: Bypass samsung knox trip protection, only confirmed working for secure folder.
6.3
ADB error checking: require a ADB device to be present even while patching "browsed" for framework dumps.
Framework error checking: display an error if no odex, vdex or oats are found.. incomplete framework dump.
Display hints for common mistakes made by users, hopefully reduces the amount of "error" reports by people that don't follow instructions.
6.2
ADB error checking: unauthorized ADB device check.
6.1
Error handling - Verify required files are found during deodex process.
6.0
Fixed index out of bounds crash.
Revert mock location patch to the original.
5.9
Mock location patch updated. Reverted patch back to the original, new patch failed.
Adapted back end functions to support multi-file patches.
Browse for .jar has now been changed to browse for "/system/framework" directory.. no longer requires a deodexed file to be targeted, will deodex necessary files if required.
5.8
Check if patcher is being ran with administrator privileges, otherwise display a warning.
Fixed a possible false positive error during cdex extraction.
5.7
Error handling - verify classes.dex is found during cdex extraction.
Added few more status updates to assist error checking.
5.6
Changed binary download percentage behaviour: avoid users reporting false "stuck on XYZ percent".
Updated mock location patch to support android 10/Q.
Updated reboot behaviour patch to support android 10/Q.
Save/restore selected patches when browsing for a JAR.
5.5
Fixed force close during vdex extraction.
5.4
Modified secure flag patch - need testing & feedback.
Modified java detection to allow more runtime environments.
5.3
Suppress false positive "magisk download failed" errors.
Verify patched APK's have been generated before creating module.
5.2
Modified secure flag patch.
Added paypal donation button.
5.1
Removed signature verification "class not found" error report, false positive on legacy android versions.
5.0
Adapted backend functions to support multi-file patches.
Require at least one patch to be enabled before proceeding.
Fix download percentage status updates.
Popup explorer window to output directory on completion.
Modified signature verification patch (android P).
When browsing for a JAR only display compatible patches (preparation for multi-file patches, services.jar must be named "services.jar" from this point onward for verification purposes.. otherwise no patches will be displayed).
New patch - disable high volume warning popup.. this has annoyed me so much recently! I was only able to test this on android P, if you find the patch does not work on your device please supply a deodexed services.jar so I can investigate further.
4.9
Fixed a crash when applying magisk reboot patch to a already patched target.
Improved magisk reboot patch, removed the potential to not reboot back into magisk.
Redirect output for certain binary functions with working status indicators.
Fix mock location patch that I broke in the most stupid way possible.. if you're updating from 4.8, make sure you disable/remove any installed smali patcher magisk modules before updating.
4.8
Display command line window until inbuilt patcher status updates are fixed to prevent user confusion.
4.7
Secure flag patch update (based off 9.0).
Signature verification patch update (based off 9.0).
4.6
Dynamically calculate base directory.
Modify output loop to ensure all output is displayed.
Magisk reboot patch (Galaxy S10 only).
4.5 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Force unix config formatting.
4.4 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Magisk "installation failed" fix.. (I shouldn't have been lazy and read all the module documentation.. probably could of avoided this).
4.3 [UNTESTED - I OWN A S10 WHICH CURRENTLY IS NOT MAGISK COMPATIBLE.. USE AT YOUR OWN RISK]
Magisk v19.0 compatible (magisk template download failed fix).
4.2 [TESTING]
Potential slowdown fix?
4.1
Allow the patcher to run without having any patches selected for testing purposes.
Force a single classes.dex to be generated when applying signature spoofing patch.. (potential slowdown fix?)
Remove irrelevant debug output.
4.0
Modified ADB error checking function to fix false error reports.
3.9 ::
ADB error checking: verify a single ADB device is connected before proceeding.
Added few more status updates to assist error checking.
Updated magisk template & URL.
3.8 [TESTING] ::
Potential slowdown fix?
3.7 ::
Modified java detection.
3.6 ::
Added some more error checking.
3.5 ::
Verify Java is installed & detected before proceeding.
3.4 ::
Amend legacy dummy file to generated magisk module config.sh.
3.3 ::
Create dummy file in magisk module (legacy devices).
3.2 ::
Fixed a issue calculating file paths on legacy devices.
3.1 ::
Added "/system/system" path to dumping functions.
Added output filter to avoid user confusion when spitting out harmless errors.
3.0 ::
Updated dependencies.
Reworked some core functions to attempt to fix unknown caused crash for certain users.
2.9 ::
Reworked some functions, made them dynamically detect file names to avoid potential issues.
2.8 ::
Verify dexpatcher patches are found, otherwise re-download.
Change patch button text to indicate patching mode.
Error handling - verify classes.dex is found before recompiling.
Error handling - verify services.jar is found before recompiling.
Error handling - verify input files are not dummy's.
Conditional dead end bug fix while patching multi-class jar's.
2.7 ::
Re-added signature spoofing patch.
Added dexpatcher as a dependency.
2.6 ::
Added support for Android P.
Modified binary download function to prevent crashes.
2.5 ::
Added support for multi-classes.dex.
2.4 ::
Improved binary download function - verify binary size, will attempt to re-download if necessary.
Improved binary URL grabber function - should now fetch correct address.
2.3 ::
Improved de/odex detection function - should now allow generating a module with no mods selected (debugging purposes)
Improved error checking & reports.
2.2 ::
Android 8.0-8.1 compatibility.
2.1 ::
Corrected missing variables in config.sh for magisk module (lollipop bootloop fix) - full credit to @Eng.Raman
2.0 ::
Prevent false "detected api" message.
Play's nice with android lollipop - full credit to @Eng.Raman
1.9 ::
Potential fix for random crash aka. dumping framework freeze/crash.
1.8 ::
Handle "permission denied" error when pulling build.prop.
1.7 ::
Improved framework base directory detection.
1.6 ::
Framework base directory detection.
1.5 ::
Improved error checking - added more debug info which hopefully will make diagnosing bugs a little easier.
Proper API detection using rom build.prop.
Improved a search function used for locating framework files.
1.4 ::
Improved error checking - verify's services.odex size detecting if module already active.
Potential fix for "magisk download failed" that certain user's are experiencing.
1.3 (BETA) ::
Added in ADB libary which allows us to now pull/push files to the device.
Added in smali & baksmali which allows us to now deodex.
One click function to pull all the required files from the device, deodex (if necessary), patch and finally generate a magisk module! (I plan to code in a function that pushes the module to the device upon completion in the future - fully automated baby woohoo)
If you would like to use the adb method of patching, make sure you have "USB debugging" enabled in developer options otherwise it simply won't work.. you obviously need to plug in your phone to the PC and authorize the USB connection on your device.
1.2 ::
Updated to Magisk v15.
Improved error checking & reports.
1.1 ::
Removed signature spoofing for the time being - causing bootloop for some users, need to rework the patch when I have time.
1.0 ::
Improved patching function: should now be compatible with even more unique service.jar's.
Improved patching function: now reports errors for each independent patch, should make diagnosing patch errors a little easier.
Fixed some debug code I left from previous release which may have prevented patch process from completing. (whoops.. sorry about that!)
0.9 ::
Added new patch: signature spoofing.
0.8 ::
Improved patching function.
0.7 ::
Merged projects together - Mock locations, secure flag & signature verification.
Assembly version used as module version and in generated module zip name.
Fixed minor bug when selecting a JAR named something other than "services.jar".
0.6 ::
Error handling for failed downloads of magisk module template.
Updated to Magisk v14.0.
0.4 / 0.5 ::
Potential spaces in file path error fix - unsure as I have been unable to reproduce this issue, so it's been very difficult to fix.
0.3 ::
Increased default Java memory heap size - fixes "out of memory" error on lowend PC's.
0.2 ::
Simplified patching process.
Fixed reboot issue with certain GPS spoofers.
Verify's target JAR is deodexed before proceeding with patch.
0.1 ::
Initial release
Cheers,
Honorable mention to @Eng.Raman & @A30NI_Y, who has been kind enough to patch service.jar's for tons of users who lack the knowledge to deodex (despite my best efforts of writing out clear instructions!)... the smali patcher user base thanks you for your service!
PRECAUTIONS / TERMS OF USE ::
You must backup your device prior to flashing the module, I am not responsible or providing support to recover any devices stuck in bootloops.. if for what ever reason you find yourself in this situation, simply uninstall magisk and reinstall.. doing this will reset your installed modules.
PLEASE READ FAQ IN POST 2 & SEARCH THE THREAD BEFORE ASKING QUESTIONS, CHANCES ARE THEY HAVE BEEN ANSWERED ALREADY AND YOU CAN FIND YOUR ANSWER IMMEDIATELY.
Rather then making mirrors of the download link, please redirect traffic to this thread to ensure they are always using the latest version! Oh hi reddit.
DOWNLOAD MIRRORS
Google drive
FAQ
HELP! I'M STUCK IN A BOOTLOOP, HOW DO I UNINSTALL ::
Boot into TWRP
Advanced -> File Manager
Navigate to: data -> adb -> modules -> select the module directory (in this case "fomey.smalipatcher") -> Folder icon (bottom right of screen) -> Delete
Alternatively you can just uninstall/reinstall magisk to clear all your modules.
MAGISK TEMPLATE DOWNLOAD FAILED ::
Run the patcher as administrator, may not have read / write access to drive.
Verify you have a active internet connection.
Verify firewall is not blocking the patcher.
Verify your not running a outdated .NET framework.
MOCK LOCATION RUBBER BANDS TO REAL LOCATION ::
Set device only in location method settings (Settings -> Location -> Location method).
Disable improve location accuracy settings (Settings -> Location -> Improve accuracy).
If you are still experiencing rubber banding after trying everything above, try a different spoofer.
INVALID OR CORRUPT JAR FILE BIN ::
Delete the "bin" directory and restart the patcher to re-download the binary files.
Corruption is caused by a unreliable internet connection.
HOW DO I CLEAR A MOCK LOCATION WHILE USING A GPS SPOOFER ::
Exit the app by pressing the "back" key, you may have to press this a few times. Any good spoofer should clean up after itself, by removing any mock providers on exit.
MAGISK TEMPLATE FAILED TO DOWNLOAD ::
Make sure you're using the LATEST release of the patcher.
If you are using the latest version already.. a update will be available shortly to fix this issue.
UNSUPPORTED MAJOR.MINOR VERSION XX.X ::
Use the Java Uninstall Tool to clean up out-of-date java versions and reinstall the latest java release.
W: COULD NOT FIND RESOURCES ::
This is a harmless warning, you can safely ignore it.
!!! ERROR: BASE DIRECTORY NOT FOUND ::
You did not accept the USB debugging permission popup on your phone.. the patcher can't do anything without this permission (example of popup).
The permission popup should be displayed after hitting the "ADB PATCH" button.. or as soon as you connect your phone to your PC.
If you can't see the permission popup: go to settings -> developer options -> revoke usb debugging authorisations.. disconnect and reconnect your phone and try again.
Make sure you tick "always allow from this computer".. otherwise you may have to confirm the popup multiple times during a single patch.
!!! ERROR: XYZ CLASS NOT FOUND ::
The patch is most likely not compatible with your android version/device, if a patch is marked "as-is" no further support is provided.
If you are browsing for a services.jar - it's most likely not deodexed.. try the "ADB METHOD".
If you are using the "ADB METHOD" and you receive this error, post a reply to this thread including as much information as you can. Useful information: android version, patcher log and the directory named "adb" in the patcher folder (upload this directory to google drive).
Reserved 3
Thank you very much for your smali patcher. I am using your mock location for a while now. Will it be compatible with Android Oreo?
flyfire04 said:
Thank you very much for your smali patcher. I am using your mock location for a while now. Will it be compatible with Android Oreo?
Click to expand...
Click to collapse
I have not tried it with a oreo services.jar, test it out let me know how you go.. if you run into issues please upload your deodexed services.jar.
Hey, could you make it just a zip that would do all the patches? I don't have a windows machine but I really want the screenshot thing I... Also I can do any testing that you want on the Oreo.
Thank you mate!!!
Awesome! Thank you!
Hi devs, sorry for interrupt. I have some problems while patching it here. I choose all three patch and run the patcher, However it suddenly stops and saying jar is not deodexed. When im untick all 3 patch and run the patcher, it runs well until completed. The problems only happens when I choose all or either one of the patches.
Im using samsung note 4 with custom deodexed rom :crying:
TheBuduLord said:
Hi devs, sorry for interrupt. I have some problems while patching it here. I choose all three patch and run the patcher, However it suddenly stops and saying jar is not deodexed. When im untick all 3 patch and run the patcher, it runs well until completed. The problems only happens when I choose all or either one of the patches.
Im using samsung note 4 with custom deodexed rom :crying:
Click to expand...
Click to collapse
Has anyone tried this on the Google pixel XL? Also when I download it and try to open it it tells me it can not be open ed
@fOmey Sir, when Smali Patcher on Linux and Android devices?
um, is this tool still not compatible with nougat's services.jar?
The patch button doesn't do anything at all.
Edit: nvm, restarting the program fixed it
HI !
When I extract my zip rom, I don't see any "system" folder ... (It's pixel ROM for nexus 5)...
Any ideas ?
Thanks.
AvisAile said:
HI !
When I extract my zip rom, I don't see any "system" folder ... (It's pixel ROM for nexus 5)...
Any ideas ?
Thanks.
Click to expand...
Click to collapse
This thread will help you out: https://forum.xda-developers.com/an.../how-to-conver-lollipop-dat-files-to-t2978952
rawimagee said:
Hi, i took my "services.jar" from my framework folder (OnePlus 5) and it says it is not deodexed. I have tried programs that will make the jar file to work in your flasher but it still does not work. Can you like write a little tutorial to me? Thanks
Click to expand...
Click to collapse
Copy the systems folder from your smartphone. (I copy it to the download folder, zip it, copy it and unzip it on the computer).
use Fulmics Deodexer (xda), download smali and baksmali from here https://bitbucket.org/JesusFreke/smali/downloads/ point fulmics deodexer to those files in the settings. Look for your systems folder with fulmics deodexer and only tick the frameworks box (the other ones are unneccesary for this task). then proceed with the smali patcher
@fOmey
I can not start your program. Can you make this pacher for me on my services.jar file so that I can put it into the framework system? My file with S7 edge nougat 7.0 Stock.
https://files.fm/u/j388jjj5
Tested on Oreo and it works great
The app crashes after i hit the start making path button on windows 10.. any help ??? Got the bins downloaded and my services.jar loaded in youre app/program.
rawimagee said:
I did that and but it still seems to not work, it said that it processed the "services.jar" file but it still says the same in the patcher;(
edit: do i pick the normal "services.jar" file from the normal folder or do the "edited" file get placed somewhere else?
Click to expand...
Click to collapse
OP5 is on Nougat, so I don't think this will work.
Sent from my OnePlus3 using XDA Labs
Dear fellow mixers,
I try to achieve the combination of:
MIUI 9 Android 7.0 either from EpicROM or xiaomi.eu
Installing Magisk systemless root
Installing Xposed for magisk
3 Questions:
Anyone achieved this already? If yes, can you tell us which version/release of MIUI, which variant of Magisk & Exposed did you use?
If someone didn't do it, but knows which combination of MIUI, Magisk and Xposed (especially which versions and mods) should work in theory, can you say so?
To my understanding this should help to *not* trip safetynet and allow us to run Snapchat?
My research so far:
According to this post, Unofficial Xposed 88.1 for MIUI9 SDK24 should work
According to this post, 88.1 works and xmiui also has a magisk zip
Another guide that seems to be written before 88.1 was released with MIUI 9 compatibility. So I'm confused which guide to follow, which combination of systemless xposed/magisk will work?
Edit:
I'll use my experiences and document them here to later create another how-to for systemless magisk/xposed on miui9 and another guide how to properly backup second space apps.
Second space backup:
Using Titanium Backup installed and started in First Space will only backup first space apps. Installing Titanium Backup in Second space also didn't work properly for me for some apps like LINE messenger.
Actually there are two (somethimes three) places that need to be backed up:
1. App APK (the installation files itself)
/data/app/<appname>
for both spaces, because they use the same app installation, as no user data is saved here, so it's in a single location, no matter how many android user accounts or MIUI spaces you have.
2. App's user data (like LINE Messenger database etc. normally not visible to you but important):
First space: /data/user/0/<appname>
Second space: /data/user/10/<appname>
This is unique for every user account (or miui space), here individual data is being saved, like two different LINE messenger accounts, or FB accounts.
3. User's accessible app data (where your app stores things that you produce in your apps and are visible to you when connecting your phone to your PC or checking your sdcard/internal storage):
First Space: /storage/emulated/0/<folder>
Second Space: /storage/emulated/10/<folder>
the folder names can be a mess here, whatsapp names their user data folder simply Whatsapp. Here they store your chat history DB, your downloaded pictures, videos and audio. Other apps can basically name their folder however they want and sometimes it's difficult to find out what folder your app stores files in. The app "Magix Pro Screen Recorder" as a fictional example could store your screen recordings in /storage/emulated/0/Movies/recordings/
To properly backup whatsapp in second space:
copy /storage/emulated/10/whatsapp folder to your PC
in new rom/phone create second space, then copy the backup form your PC to the same location as above in your new rom/phone
install whatsapp from play store, open it and it should recognize the backup and ask you to directly restore it
To properly backup a more complex app that uses all three folder types described above I take Naver LINE Messenger as an example:
backup /data/user/10/jp.naver.line.android/ *
backup /data/app/jp.naver.line.android-1 *
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install terminal emulator and delete the previous LINE settings by using the following commands:
su
sqlite3
/data/user/10/jp.naver.line.android/databases/naver_line
delete from setting;
.quit
if you don't have the sqlite3 binary, you can try to find it online for android (arm64 binary), paste it to your /bin folder and try again, or open the file on your computer with an sqlite explorer
if available, delete the following xml:
/data/user/10/jp.naver.line.android/shared_prefs/jp.naver.line.android.settings.xml
open the Line app and it will ask you to enter your user and password
Alternative method:
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
use an sqlite editor on your phone or on your pc to empty the following database:
/data/user/10/jp.naver.line.android/databases/naver_line
start line
My preferred method:
on old phone, install device id changer pro in second space and open it
note down device ID
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install device id changer pro in second space and open it
enter the previously noted down device ID and set it
start line
* creating proper backups of the two LINE folders is a whole procedure again, we need to use tar gz to preserve permissions when copying and pasting:
- enable developer mode and usb debugging
- connect to pc
- install minimal adb & fastboot on your PC
- start cmd, execute:
adb shell
- accept popup on device, then type into cmd:
su
- accept supersu on device
- type:
cd /data/user/10/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-10-jp.naver.line.android.tar.gz .
cd /data/user/0/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-0-jp.naver.line.android.tar.gz .
cd /data/app/jp.naver.line.android-1
tar -cvpzf /storage/emulated/0/app-jp.naver.line.android-1.tar.gz .
- copy the 3 backup tar.gz files into your first space internal storage, and type:
cd /storage/emulated/0/
tar xpvzf user-10-jp.naver.line.android.tar.gz /data/user/10/
tar xpvzf user-0-jp.naver.line.android.tar.gz /data/user/0/
tar xpvzf app-jp.naver.line.android-1.tar.gz /data/app/
Reported Psyman version seems work and sometimes... latest build officialy released by Rovo works... then u need made a backup and try to flash a magisk version, lastest will have more chance to work because include all report from git...
And a lot of xposed module need to be updated....
cheers
I wasn't unable to make xposed 88.0 or 88.1 to work with the latest N MIUI 9 Epic rom using magisk. the only version that worked for me was V87 xposed but somehow gravity box didn't seen to work well when enabling setting and applying theme, that is gravity older version not the newest the newest version require xposed 88 and newer which didn't activated on N MIUI 9 Epic newest rom, exMIUI did work though
Ok, some news...
Lastest stable from Xiaomi.eu (9.1 - 7.0 - SDK 24) works with magisk and xposed... only need good version and right apk...
Cheers
Copying instructions that were in the miscellaneous thread while we were waiting for a proper sub forum. Keep in mind that the program to get TWRP onto the phone is in Chinese and will trigger an antivirus warning. Also TWRP will be in Chinese so users have to press the button on the right in the 1st screen to enable English.
TWRP is working for Nubia Z20 Chinease, Europe and American version
Download TWRP from this link
[Mod Edit] Download link removed due to GPL incompliance
Installing TWRP steps:
1. Enable usb debugging in nubia z20
2. Connect your mobile to the computer
3. Disable Anti-virus on your computer
4. Copy paste TWRP application to C:/adb
5. Click the only button on the TWRP interface
6. On the next screen, click the only button (fastboot twrp) on the screen
7. mobile will reboot to bootloader
8. reboot to recovery
9. if you have security code, input your security pin.
10. change language by clicking right side button
11. In twrp, you can flash global rom and magisk for root
For Rooting Nubia (all version)
1. Install TWRP from the above link
2. From TWRP, you can install magisk manager (latest) and reboot to system.
3. From Magisk application, download riru modules (core & hook) install and reboot.
4. Insatll Edxposed for xposed modules
Custom modules working for Nubia:
1. Gravity Box (working only for global roms)
2. Face unlock (Magisk module)
3. Instant Face unlock (Xposed module)
4. Pixelify (Magisk module0
5. Force touch enabler (Xposed module)
6. Xposed edge (Xposed module)
7. AR core patcher (Magisk module)
8. Google cam (Gcam shared earliet posts with attached xml scripts)
9. Youtube vanced
10. Whatsapp emojis
11. L Tweaks
Linux?
What should Linux users do?
Cheako said:
What should Linux users do?
Click to expand...
Click to collapse
Switch to windows? Seriously...at least for a short time. I'm a Linux user myself but always have a Windows machine handy for flashing
n1tro said:
Switch to windows? Seriously...at least for a short time. I'm a Linux user myself but always have a Windows machine handy for flashing
Click to expand...
Click to collapse
Thanks! I haven't used Windows since the late 90s and every time I try what you're suggesting I have a horrible time. It's not worth any amount of effort to have Windows for running this one application that does something ultimately resulting in Malware. That is to say running this program is analogous to running an application that, I not only don't have the source too, but indeed can't even explain what it does. That's the vary definition of malicious software, running software that has no explainable purpose.
It piss me off why every nubia TWRP is a .exe can you just install it yourself and make a backup of your recovery partition and send us the img ?
its here ***
[Mod Edit] Download link removed due to GPL incompliance
GPL Violation.
This program is obviously linked with a compiled image of TWRP, witch is GPL. The exe is encrypted, a form of UPX. Regardless it's against copyright to distribute without source.
RomanLeFrais said:
It piss me off why every nubia TWRP is a .exe can you just install it yourself and make a backup of your recovery partition and send us the img ?
its here ***
[Mod Edit] Download link removed due to GPL incompliance
Click to expand...
Click to collapse
Looks like a boot image, but triggers the same error on my device. From another thread we are discussing the differences of V1.x(NON-EU) and phones from the EU that are V2.x. The images I've found and have been using are V2.x and the phone is from US Amazon, not that you can't purchase EU phones from there. It's unknown what version my phone is.
I've been pointing out everywhere the GPL violations and that also applies here.
Tell me if I'm wrong but the only difference beteween eu and non-eu are the radio frequency and maybe some minor adjustement that don't affect the way TWRP work, and the only difference between 1.x and 2.x are the system update it also don't affect the way TWRP need to be compiled except for the included magisk install ect in the advanced tabs that Scarlet-glass added
If you want to have your own clean version you can always compile TWRP yourself to not deal with a GPL issue (Isn't it the GNU Free software license ?) Scarlet-glass released the device tree
UPX is a compression algorithm lol, to check if its obfuscated run Detect-it-Easy on it, I did and its not obfuscated take a look at my binwalk output
https://pastebin.com/7Ut6E5Zz
The executable maybe came from the person that make the "Global" ROM for all the aliexpress seller by removing the chinese app and installing google, they left their "weibo VIP channel" in /etc on the system part but I don't know how to join.
So anyway I doubt they copyrighted their TWRP image and its normal that the recovery image appear as a boot image because it is one lol
Apparently this device is not the same for EU users as America or China, that is to say one model for EU and another model for NON-EU(presumably China, India, Japan, Canada, US, ect). I was using V2.x(EU) files, but my phone is V1.x(NON-EU). The major version numbers are more like part of the model number than like a version indicator. Here is the full dump where I got the boot and recovery images, it's 2.2GB compressed
https://www.filehosting.org/file/details/835328/NX627J_NubiaEmergencyDownload_V103.7z
I'll try and post just the boot/recovery images here: https://mikemestnik.net/archives/
Code:
SHA256 (NX627J_NubiaEmergencyDownload_V103.7z) = bd412eeab191c001a4ee5b11bda8a2ec7273257ccd2e1d024e60e8c6a1bd174b
SHA256 (NX627J-stock-1_03.7z) = f53a120dc7e8029bf2bb0fb7a462d027376d63bb39e4b7f2ae2f55ae2bcba9ae
RomanLeFrais said:
Tell me if I'm wrong but the only difference beteween eu and non-eu are the radio frequency and maybe some minor adjustement that don't affect the way TWRP work, and the only difference between 1.x and 2.x are the system update it also don't affect the way TWRP need to be compiled except for the included magisk install ect in the advanced tabs that Scarlet-glass added
If you want to have your own clean version you can always compile TWRP yourself to not deal with a GPL issue (Isn't it the GNU Free software license ?) Scarlet-glass released the device tree
UPX is a compression algorithm lol, to check if its obfuscated run Detect-it-Easy on it, I did and its not obfuscated take a look at my binwalk output
https://pastebin.com/7Ut6E5Zz
The executable maybe came from the person that make the "Global" ROM for all the aliexpress seller by removing the chinese app and installing google, they left their "weibo VIP channel" in /etc on the system part but I don't know how to join.
So anyway I doubt they copyrighted their TWRP image and its normal that the recovery image appear as a boot image because it is one lol
Click to expand...
Click to collapse
The file you are talking about and the one that is currently posted are nothing alike.
Code:
[email protected]:~/Downloads$ binwalk nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Microsoft executable, portable (PE)
372399 0x5AEAF SHA256 hash constants, little endian
4642204 0x46D59C MySQL ISAM compressed data file Version 10
13113062 0xC816E6 gzip compressed data, last modified: 2019-08-30 09:47:28
42228777 0x2845C29 End of Zip archive, footer length: -25518
42279022 0x285206E PARity archive data - file number 7950
42571120 0x2899570 XML document, version: "1.0"
This reminds me to add checksums to my uploads!
Cheako said:
The file you are talking about and the one that is currently posted are nothing alike.
This reminds me to add checksums to my uploads!
Click to expand...
Click to collapse
I first decompressed with upx
Code:
upx -d nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
Edit: I downloaded 1.03 and 2.03 and try to look for diff in some files with
Code:
vimdiff <(xxd "EUROPE-ASIA/file" ) <(xxd "US/file" )
and they are a little different I didn't try the android files (system,vendor,boot etc) because they are too big though
RomanLeFrais said:
I first decompressed with upx
Code:
upx -d nubia\ Z20-for\ Android\ P-TWRP-3.3.1.exe
Edit: I downloaded 1.03 and 2.03 and try to look for diff in some files with
Code:
vimdiff <(xxd "EUROPE-ASIA/file" ) <(xxd "US/file" )
and they are a little different I didn't try the android files (system,vendor,boot etc) because they are too big though
Click to expand...
Click to collapse
help me please i am some speak english. my nubia z20 brick . i need stock rom my phone global en v203 i want to chinese rom but my phone brick.
i need rom i need help
Not working for me.....
Not able to install TWRP.
Have also tried to install img.
Have typed in "adb reboot bootloader" in command window, and the phone reboot.
But when typing "fastboot flash recovery recovery.img", it get stuck on "waiting for device".
Anyone have the correct USB driver?
Or is the problem windows 10?
Btw, USb debugging is on, and OEM unlocking is on.
Ui is CNCommon_V2.17.
The China special with no update function, beside update by usb-c OTG, wich don't work.
Why can not create backup from TWRP, both to the internal memory and to the flash card via OTG, writes an error.
Olfoss said:
Not able to install TWRP.
Have also tried to install img.
Have typed in "adb reboot bootloader" in command window, and the phone reboot.
But when typing "fastboot flash recovery recovery.img", it get stuck on "waiting for device".
Anyone have the correct USB driver?
Or is the problem windows 10?
Btw, USb debugging is on, and OEM unlocking is on.
Ui is CNCommon_V2.17.
The China special with no update function, beside update by usb-c OTG, wich don't work.
Click to expand...
Click to collapse
please answer me
n1tro said:
Copying instructions that were in the miscellaneous thread while we were waiting for a proper sub forum. Keep in mind that the program to get TWRP onto the phone is in Chinese and will trigger an antivirus warning. Also TWRP will be in Chinese so users have to press the button on the right in the 1st screen to enable English.
TWRP is working for Nubia Z20 Chinease, Europe and American version
Download TWRP from this link
https://drive.google.com/file/d/1rpyehWTPdzzNLhZVqvOuaPmoZ0bG0gak/view?usp=sharing
Installing TWRP steps:
1. Enable usb debugging in nubia z20
2. Connect your mobile to the computer
3. Disable Anti-virus on your computer
4. Copy paste TWRP application to C:/adb
5. Click the only button on the TWRP interface
6. On the next screen, click the only button (fastboot twrp) on the screen
7. mobile will reboot to bootloader
8. reboot to recovery
9. if you have security code, input your security pin.
10. change language by clicking right side button
11. In twrp, you can flash global rom and magisk for root
For Rooting Nubia (all version)
1. Install TWRP from the above link
2. From TWRP, you can install magisk manager (latest) and reboot to system.
3. From Magisk application, download riru modules (core & hook) install and reboot.
4. Insatll Edxposed for xposed modules
Custom modules working for Nubia:
1. Gravity Box (working only for global roms)
2. Face unlock (Magisk module)
3. Instant Face unlock (Xposed module)
4. Pixelify (Magisk module0
5. Force touch enabler (Xposed module)
6. Xposed edge (Xposed module)
7. AR core patcher (Magisk module)
8. Google cam (Gcam shared earliet posts with attached xml scripts)
9. Youtube vanced
10. Whatsapp emojis
11. L Tweaks
Click to expand...
Click to collapse
please can you improve twrp for android 11 this way
I can't. I'm not a developer. The information above was done by someone else before the forum was created. I only copied the content over.
This phone has almost no support unless you are using the Chinese version. Nubia does not care about the global market as they make enough money selling phones within China in my opinion.
n1tro said:
I can't. I'm not a developer. The information above was done by someone else before the forum was created. I only copied the content over.
This phone has almost no support unless you are using the Chinese version. Nubia does not care about the global market as they make enough money selling phones within China in my opinion.
Click to expand...
Click to collapse
i will never buy a nubia phone again.
I upgraded to android 11 beta for nubia z20, it installed without issue, but I was not satisfied with the upgrade because I could not access my contacts. I tried to reinstall the standard ROM back, it loads the nubia logo and then shows the warning “Device is corrupted. It can't be trusted and won't boot. " I have flashed the Nubia z20 unbrick tool v1.03 and this does not help either, please help
Root your device virtually without unlock bootloader/twrp/magisk
No need to panic..it will not destroy your color os..it's a virtual os.
Check here
After enable root in vmos .. power off vmos and again open vmos. Install root checker in vmos and verify
Followed above method and rooted the vmos..
Planning to install v4a Apk..will update.
Update:: installed successfully and working fine
V4A does not work on VMOS + root ..already checked the same..
it force closes for all versions alpha/beta and stable versions
Regards,
Diaz
I m using VMOS Virtual Root Android on Android Double System_v1.0.42_apkpure.com
Have installed v4a 2313 version successfully
Need to copy some lib files to vmos system manually and then install v4a.. install busy box too
Check this
Hi Akash,
When u say copied some libs can u let know what libs and to which location was it copied....
Also if u can link up the APK for version u m etioned would be good
Regards
Diaz
Check this
https://forum.xda-developers.com/lg-g3/themes-apps/app-viper4android-v2-4-0-1-lg-g3-t3311403
Use the lib files from here..
Search 2313 version from Google and install
Also install busy box
Viper 4 android for RUI
https://forum.xda-developers.com/realme-xt/themes/viper4android-rui-finally-t4124633
After trying nfqttl and failing, I decided to go on my way and, in the process, I found the definitive solution.
Steps:
1) unpack boot.img
2) patch kernel image
3) repack boot.img
Flash
the patch is simple:
In the linux kernet in ip_forward.c this function is called to decrease the TTL of every forwarded packet:
static __always_inline int ip_decrease_ttl(struct iphdr *iph){ u32 check = (__force u32)iph->check; check += (__force u32)htons(0x0100); iph->check = (__force __sum16)(check + (check >= 0xFFFF)); return --iph->ttl;}
All I did is to patch the kernel not to do so.
return iph->ttl;
You can easily do it in this way:
Bash:
magiskboot unpack -h boot.img
magiskboot hexpatch kernel C9220039C816007968F24039E8002836 1F2003D51F2003D568F24039E8002836 # tested on Redmi Note 10 Pro
magiskboot hexpatch kernel A0160079A022403900040051A0220039 1F2003D5A0224039000400511F2003D5 # tested on Redmi 4X
magiskboot repack boot.img
Then you can just boot it (for testing) or flash it directly.
fastboot boot new-boot.img
or
fastboot flash boot new-boot.img
result:
pinging google from the phone:
Bash:
$ ping google.com
PING google.com (142.250.179.142) 56(84) bytes of data.
64 bytes from ams17s10-in-f14.1e100.net (142.250.179.142): icmp_seq=1 ttl=106 time=115 ms
pinging google from windows connected to the phone (works both with wifi or usb tethering)
Code:
C:\>ping 142.250.179.142
Pinging 142.250.179.142 with 32 bytes of data:
Reply from 142.250.179.142: bytes=32 time=127ms TTL=106
As you can see the TTL is the same.
Before the patch it's one less, obviously.
Magisk module:
https://github.com/Zibri/ttl_fix/releases/download/V4/ttl_fix.zip
If you have magisk installed you can also just copy and paste this line of code in your adb shell:
Install patch:
Bash:
su -c "curl -s https://raw.githubusercontent.com/Zibri/ttl_fix/master/customize.sh | sh"
Remove patch:
Bash:
su -c "curl -s https://raw.githubusercontent.com/Zibri/ttl_fix/master/remove.sh | sh"
Note: remove nfqttl from your phone if you want this to work correctly.
Also: this patch should for any ARM64 android kernels.
how to run/execute? :
magiskboot unpack -h boot.img
magiskboot hexpatch kernel C9220039C816007968F24039E8002836 1F2003D51F2003D568F24039E8002836
magiskboot repack boot.img
i try via adb but failed.
magiskboot it's part of magisk software.. anyway, when I have time I will make a magisk module.
Zibri said:
magiskboot it's part of magisk software.. anyway, when I have time I will make a magisk module.
Click to expand...
Click to collapse
You mean like this?
GitHub - cyborg-one/nfqttl: Magisk module change ttl.
Magisk module change ttl. Contribute to cyborg-one/nfqttl development by creating an account on GitHub.
github.com
simkad said:
how to run/execute? :
magiskboot unpack -h boot.img
magiskboot hexpatch kernel C9220039C816007968F24039E8002836 1F2003D51F2003D568F24039E8002836
magiskboot repack boot.img
i try via adb but failed.
Click to expand...
Click to collapse
here you go...
magisk module just made.. please tell me if there are any problems.
https://github.com/Zibri/ttl_fix/releases/download/Release/ttl_fix.zip
Laptapper said:
You mean like this?
Click to expand...
Click to collapse
No.. that's rubbish and does not work at least on my phone (MIUI 13 and 12)
Remove nfqttl from your phone if you use my module.
Zibri said:
No.. that's rubbish and does not work at least on my phone (MIUI 13 and 12)
Remove nfqttl from your phone if you use my module.
Click to expand...
Click to collapse
And what's about this?
TTL Value Editor - Apps on Google Play
Wifi distribution from the phone, TTL editor for modem mode
play.google.com
What are the pros of yours?
Zibri said:
here you go...
magisk module just made.. please tell me if there are any problems.
https://github.com/Zibri/ttl_fix/releases/download/Release/ttl_fix.zip
Click to expand...
Click to collapse
thanks for the module.. install it via magisk manager but got error unzip failed, im using magisk 25.2, my device redmi note 10 pro (sweet), rom eliterom 13.0.12, kernel QuantumKyaru.
simkad said:
thanks for the module.. install it via magisk manager but got error unzip failed, im using magisk 25.2, my device redmi note 10 pro (sweet), rom eliterom 13.0.12, kernel QuantumKyaru.
Click to expand...
Click to collapse
ive unpack n repack (zip only files not folder) this module, now can install.. already test, but i dont think its work for me. Tether from phone to pc via wifi hotspot, ttl on phone 116, ttl on pc 115. Anybody else test?
I repackaged the release.
and added a final reboot to the script.
p.s. this works on stock MIUI V13.0.12.0 or any xiaomi stock kernels i tried.
simkad said:
ive unpack n repack (zip only files not folder) this module, now can install.. already test, but i dont think its work for me. Tether from phone to pc via wifi hotspot, ttl on phone 116, ttl on pc 115. Anybody else test?
Click to expand...
Click to collapse
I patched the boot image for your rom,
you can test it without flashing it:
fastboot boot boot_ttlfix.img
or you can flash it:
fastboot flash boot boot_ttlfix.img
Laptapper said:
And what's about this?
TTL Value Editor - Apps on Google Play
Wifi distribution from the phone, TTL editor for modem mode
play.google.com
What are the pros of yours?
Click to expand...
Click to collapse
It happens at kernel level. no other software needed.
It affects ANY packet from ANY source.. wifi, usb tethering, bluetooth tethering...
It works for me... I just thought to share it.
But I never did a magisk module.. so if anyone wants to check it, is welcome.
All it does is to put 2 NOPs (1F 20 03 D5) where the decremented ttl is finally stored.
Note: this patch applies to any ARM64 kernel. Not only our redmi note 10 pro.
What exactly does this do? Ican't find any useful information or something i can understand about this "TTL" thing
VoidedKN0X said:
What exactly does this do? Ican't find any useful information or something i can understand about this "TTL" thing
Click to expand...
Click to collapse
If you theter a device to your phone, the provider can spot it and slow you down or deny the service or bill you differently.
With this mod, any packet coming from any device tethered to your phone will appear to your provider as it is coming from the phone.
In many cases this causes a faster speed for tethered devices.
In other cases will have no impact.
Updated and tested the zip file.. now it works.
https://github.com/Zibri/ttl_fix/files/9790000/ttl_fix.zip
Hello.
I installed the module from you.
During installation, the phone itself rebooted.
That's why I don't know if the module is fully installed?
But still, I checked the work on the distribution and the module works.
Should the phone itself reboot during module installation?
evgehae said:
Hello.
I installed the module from you.
During installation, the phone itself rebooted.
That's why I don't know if the module is fully installed?
But still, I checked the work on the distribution and the module works.
Should the phone itself reboot during module installation?
Click to expand...
Click to collapse
Yes.. it was a quick and dirty test...
Anyway, try this:
from adb shell ping a google address like:
ping 172.217.18.46
and take note of the TTL field.
then from another phone or pc connected to your phone in tethering, do the same..
ping 172.217.18.46
if the patch was successful the TTL value will be the same. otherwise it will be one less.
New version. Tested on "santoni" and "sweet".
Release TTL FIX · Zibri/ttl_fix
Added a second patch for other phones... More will come.. Download
github.com
Donwload