Related
I have xposed running on my Nexus 5 lollipop 5.0.1.
After downloading and enabling a couple modules my phone is now stuck in a bootloop.
I tried clearing dalvik and cache it didn't help.
Is it possible to disable xposed from recovery?
EDIT: Solved.
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/xposed/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/xposed/disabled
Click to expand...
Click to collapse
Didn't work. Still stuck in bootloop.
bseos said:
Didn't work. Still stuck in bootloop.
Click to expand...
Click to collapse
what modules you have activated?
or
mv /system/lib/*.*.orig /system/lib/*.*
mv /system/bin/*.orig /system/bin/*
opssemnik said:
what modules you have activated?
Click to expand...
Click to collapse
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
very good
bseos said:
It was between two modules. Can't remember the first one but the last one was XInstaller.
Anyway, got it solved using the below method:
Boot into Recovery (Power + Volume Down)
TWRP > Advanced > Terminal command
Create a file /data/data/de.robv.android.xposed.installer/conf/disabled, which causes Xposed to be bypassed as well:
Code:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
Click to expand...
Click to collapse
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
.Ryker said:
XInstaller seems to be causing a few issues, and I don't think its the app itself but the apps it allows you to install instead. I had the same issue after installing xInstaller. But now that you figured this out maybe I can try a few other apps out like xstana which for somereason refuses to install on lollipop devices...
Click to expand...
Click to collapse
After disabling it I flashed the new xposed-arm-20150308.zip and installed XposedInstaller_3.0-alpha2.apk (I was on alpha1 previously)
Re-enabled xposed (deleted "disabled" file) and all is working fine now.
This thread definitely either needs to be made a sticky, or the contents needs to be in one of the already made sticky threads IMHO
Cheers
//edit
I tried this out on my phone to test (my xposed stuff is working just fine) but it doesn't seem to have disabled xposed at all?
Ex, app settings still functions (set my play store to be at 480 DPI and it's still opening in 480 DPI as it should...)
I made the necessary file you said with fx file manager, not through TWRP recovery though... I don't think it should make a difference though how I made the file, just that it's there.
Maybe my permissions on the file are messed up, I just thought of that..
//edit 2
Yup my perms were messed up, xposed is now disabled for me. Cheers for the info, now I know what to do when some shady looking module backfires on me lol
Thank you so much!!! This worked perfectly on Sprint LG G3 using Candy5 ROM!! Saved me!!
Just to report that the method failed on a Samsung Galaxy S6 Edge (SM-G925F).
I created succesfully the disabled file, but I was still having bootloops.
So I thought I forgot to set the file to 755, but then TWRP told me:
Code:
Updating partition details...
...done
E: Resource (font)-(fixes) failed to load
Kernel does not have support for reading SELinux contexts.
MTP Enabled
Now I hope to fix everything by reflashing the firmware again...
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Nokiacrazi said:
After successfully disabling xposed in order to get the device to boot, how do we reenable it? Because after uninstalling the module which caused the problem the framework is "not active". A reboot did not work.
Click to expand...
Click to collapse
Delete the "disabled" file in the folder op showed
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Nokiacrazi said:
Silly question but how can I delete it? I tried locating it using HTC file manager and es file explorer but cannot locate it.
Is there a command I can use using terminal emulator or something?
Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
jkyoho said:
You need you use Root explorer or Es file explorer that supported Root and locate to /data/data/de.robv.android.xposed.installer/conf
Method 2:
You can even delete the "disabled" file in recovery by using file management, if you are using TWRP. Same as previous method, just locate to /data/data/de.robv.android.xposed.installer/conf
Click to expand...
Click to collapse
Thanks, method 2 worked a treat.
For some reason, even though I have root access, it wasn't showing in either root explorer or es file explorer, however, when looking through TWRP file management was all there.
jkyoho said:
Delete the "disabled" file in the folder op showed
Click to expand...
Click to collapse
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
cybercop007 said:
can you please explain the process.
i entered the twrp and advanced and terminal command and went through the shown path yet i didnt see the file "disabled"
he has said to create a file; how could i create a file??
please explain the process...
Click to expand...
Click to collapse
If you can't normally boot to system, boot to recovery(twrp or some other custom recovery which has file management function)
Try copy a small file like host or something, paste it the that /data/data/dev.*****installer/conf folder and rename it "disabled".
flashable zip´s
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
these will be very good to have! thank you!
starbase64 said:
flashable zip´s
Click to expand...
Click to collapse
Thank you!!!
Given the situation that I needed to unlock bootloader and install TWRP inorder to be able to do full image backup (i.e. Nandroid), I have been wondering what are the underlying security issues to be faced after unlocking and installing TWRP (without moving onto root) in a specific situation where the device is lost or stolen?
Lets say if I am on stock OOS with encryption enabled + Fingerprint and password/pin set on lock screen + USB debugging disabled + locked bootloader + stock recovery, in the unfortunate event where my device were to get lost or stolen, I can expect my personal data to be safe from prying eyes since the person who has gotten a hold of my phone will have to do a factory reset to get into the phone or unlock bootloader which all meant my personal data will be wipe. So that's a good outcome in an unfortunate one.
But let's say if now I were to (i) unlock my bootloader and (ii) install TWRP (but retaining it as read only without system modification), (iii) restore all app, data and settings, and go on to (iv) perform a nandroid backup. And after that, proceed to (v) disable USB debugging and (vi) re-enable encryption and (vii) set fingerprint and password on lock screen. And I shall stopped there without rooting or flashing dm verity. Can I still expect my personal data to be safe from prying eyes in the event of lost or stolen? Meaning that whoever gets a hold of my device will likewise need to wipe it clean before he/she is able to use it? Is this the case or can the person access my data using some hacks now that the device runs custom recovery?
An interesting guide I had came across contained various means of accessing personal data (read - https://forum.xda-developers.com/showthread.php?t=2620456) by bypassing android password, patterns, etc set on the locked screen, and some methods required USB debugging to be enabled while some required custom recovery installed.
To be sure if I am still able to protect my personal data when device is stolen/lost with an unlocked/TWRP installed device, my curiosity took me on an investigative path using an old Samsung Note 3 to unlock bootloader and install TWRP, then proceed to enable encryption and disable USB debugging and set lockscreen password. And now for the next couple of days where I can find free time, I will try out all 7 methods to see if an unlocked Note3 with TWRP is susceptible to these security compromise. I will come back to this thread later to update my findings.
I really welcome any information or inputs too!
To summarize, the state of my old Note 3 used in this investigation is as follows:
1) Bootloader unlocked
2) TWRP (3.0.2) installed as "read only" without system modification
3) ROM (CM13) encryption enabled
4) Locked screen password set
5) Device not rooted
6) USB debugging disabled
When I boot into TWRP, I realized that even if I set it to read only, any person who has gotten hold of my device can set it to system modification since TWRP is not password or pin protected. Therefore setting to "read only" is sort of irrelevant in this investigation to find out how vulnerable the device is right now.
The second thing I realized, is TWRP will ask me for android password to mount my internal sdcard since my ROM is encryption enabled. This is a good thing, since in this case TWRP internal file manager will not be able to access my device internal sdcard containing some of my personal data.
The 1st method I tried is:
METHOD I
Solution For Everyone With Recovery (Cwm, Twrp, Xrec,Etc...) Installed:
INSTRUCTIONS:
1. Download this zip Pattern Password Disable (Download from attachments) on to your sdcard (using your PC, as you cant get into your phone, right )
2. Insert the sdcard into your phone
3. Reboot into recovery mode
4. Flash the zip
5. Reboot
6. Done!
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
The steps I took:
A) Set TWRP to system modification
B) When TWRP asked me for password to mount partition, I choose "cancel" since I am trying to imitate the person who has gotten hold of my device won't be able to guess my password
C) Flashed the pattern password disable zip file
And voila!... my password on locked screen is still intact. Meaning that entering any random password does not gain access into android. Only the original password can.
Good news certainly. Don't know why this hack doesn't work, probably it is outdated or probably due to my system is still encrypted when I flashed the hack zip file.
As to the 2nd method, I didn't try out as I don't know how to use Cygwin...
METHOD 2
Solution For Everyone Without Recovery Installed - ADB :
What You Need:
=>A computer running a Linux distro or Windows+Cygwin
=>USB cable to connect your phone to the PC
=>Adb installed
How to install adb:
1. Open Terminal
2. Type:
Code:
sudo apt-get install android-tools-adb
Hit [Enter]
3. Follow the instructions until everything is installed.
INSTRUCTIONS:
1. Connect you (turned on) Phone to the Computer via USB.
2. Open a terminal window.
3. Type:
Code:
adb devices
adb shell
cd data/system
su
rm *.key
4. Done...Now You Just Have To Reboot.
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
Method 3 is irrelevant to this investigation therefore it has been omitted.
METHOD 3
Solution For Everyone Before Lock Accident :
SMS Bypass - Download Link - Install It On Your Device (Download from attachments)
This App Allows You To Remotely Bypass Your Phone's Screen Lock By Sending A SMS.
It Removes Your Gesture Pattern Or Password After Receiving A Preset Keyword Along With A Secret Code Via SMS.
SMS Bypass App Requires Root.
INSTRUCTIONS:
1.First, make sure you give permanent root access to the app.
2.Change the secret code to your preferred choice. The default password is : 1234
3.To reset your screen lock, send the following message from another phone:
Code:
secret_code reset
Example:
Code:
1234 reset
Note 1 : There is a space between your secret code and reset. Also the secret code is case sensitive.
Note 2 : There is an option available to change the preset keyword. Default is : reset - Your phone will restart and your lock screen will be reset.
Note 3 : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
Given that method 5 is in fact similar to method 2 therefore it has been omitted as well.
METHOD 5
Solution For Everyone Via Adb - File Removal :
INSTRUCTIONS:
=>Type This Command In Your Terminal (CMD Prompt) :
Code:
adb shell rm /data/system/gesture.key
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
Method 6 will not work since that hack required USB debugging to be enabled.
METHOD 6
Solution For Everyone With USB Debugging Enabled :
INSTRUCTIONS:
Primary Step for all method:
Download & Extract to anywhere - Bypass Security Hack (Download from attachments)
Open SQLite Database Browser 2.0.exe in SQLite Database Browser.
Run pull settings.db.cmd inside By-pass security Hacks folder to pull out the setting file out of your phone.
Drag settings.db and drop to SQLite Database Browser 2.0.exe program.
Navigate to Browse data tab, At table there, click to list down the selection & selete secure
Instruction To Remove Pattern Lock:
Now, find lock_pattern_autolock, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove PIN Lock:
Now, Find Or Create lockscreen.password_type, double-click & change it's value to 65536, Apply changes!
Now, find lock_pattern_autolock, Delete Record, If doesn't exist, Ignore
Close & save database
Run push settings.db.cmd and reboot your phone
Instruction To Remove Password Lock:
Now, find lockscreen.password_salt, Delete Record
Now, find lockscreen.password_type, Delete Record
Close & save database
Run push settings.db.cmd and reboot your phone
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
I then tried out method 7 using the Aroma file manager however all these 3 versions (Version 2.00 [BETA1]- KACAPI, aromafm-1.91, and aromafm-1.90) does not open up after flashing the zip with system modification enabled on TWRP. Mostly likely these outdated versions of the Aroma file manager are not supported by the latest version of TWRP (3.0.2) since the developers have ceased all work related to it.
METHOD 7
Solution For Everyone With Recovery Installed :
INSTRUCTIONS:
1.Download and Copy Aroma File manager.zip (Download from attachments or http://forum.xda-developers.com/show....php?t=1646108) to your memory card.
2. Open your recovery (press volume Down + Power button or it can be different according to the phones. Generally the phones who have press able button on the middle they have to press all three buttons. Google for you pattern there are lots)
3. There’ll b an option in recovery called “mount”. Go in that option and then mount all the cache and everything it is there.
4. Then select “update” and select “apply update from SD/external” and select aroma file manger.zip file that you downloaded using above QR code above.
5. After Flashing or updating, the aroma file manger will open. Use volume keys for up/down and power button 2 select like you use to get into recovery.
6. In aroma File manager , Go to menu , which is located in bottom strip and then select Settings.
7. Go to bottom n select “mount all partition in startup ” then exit from aroma file manger.
8. Now after exit , re-update that aroma file again and it will open again.
9. Go to data >> and then System.
Then find ‘gesture.key’ (for pattern lock) and ’password.key’ (for password lock) then long touch on gesture.key or password.key and sum option will be prompted , choose delete and delete that file and restart.
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
And now onto the last method which is method 4 using SQL command. After starting adb daemon, adb devices are not found and hence the following steps could not be taken. I think this could be due to the device having USB debugging disabled. Hmmm...
METHOD 4
Solution For Everyone Via Adb - SQL Command :
INSTRUCTIONS:
=>Type This Commands Separated In Your Terminal (CMD Prompt) :
Code:
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
=>Now You Just Have To Reboot.
Note : If You See The Gesture Pattern Grid Or Password After Restarting, Don't Worry. Just Try Any Random Pattern Or Password And it Should Unlock.
After going through all these methods, I am inclined to think that personal data is still protected in an unlocked/TWRP installed device as long as USB debugging is DISABLED and ROM is encrypted and fingerprint/password set on lock screen. What do you think?
As long as your data is encrypted, it is safe and not accessible to any 3rd party.
But with an unlocked bootloader, you are open to a new forms of attacks like:
1. someone could steal your phone, modify your system to leak your data / password and then return it to you. Since dm-verity is OFF, you will not know, that your system is compromised.
2. someone could use a remote exploits (to launch his code and gain root privileges) to modify your system and leak your data / password and since dm-verity is OFF, you will not know, that your system is compromised.
+ with the unlocked bootloader, FRP is not working, so a thief can just reset your phone and sell it.
If your data security is a huge concern to you, DO NOT unlock the bootloader.
If you are a potential target to a hacker attacks, DO NOT use a OnePlus phone. Get a Nexus 6P or a Pixel.
Also make sure, that your apps are not leaking your data. Apps with a storage permission and access to the internet could leak your data.
Michalko5896 said:
As long as your data is encrypted, it is safe and not accessible to any 3rd party.
But with an unlocked bootloader, you are open to a new forms of attacks like:
1. someone could steal your phone, modify your system to leak your data / password and then return it to you. Since dm-verity is OFF, you will not know, that your system is compromised.
Click to expand...
Click to collapse
Many thanks for your response! This is very useful information to me.
Am I right to assume that even if my device is unlocked but with encryption enabled and no root, the person who has gotten hold of my phone will still be able to flash "dm-verity and forced encryption disabler" zip and supersu zip files to root my device in TWRP even when he fails to enter the password prompted by TWRP?
And this force encryption disabler as the name suggest only disable force encryption and it does not decrypt my already encrypted personal data? Which means he still does not have access to my data and after he had done the system modification and returns the phone back to me, the first thing I should do is to wipe clean every partition and restore back my nandroid which would consist of backups to all partitions. So it seems this is an acceptable risk all for the convenience of performing nandroid backup via the unlock/TWRP route.
2. someone could use a remote exploits (to launch his code and gain root privileges) to modify your system and leak your data / password and since dm-verity is OFF, you will not know, that your system is compromised.
+ with the unlocked bootloader, FRP is not working, so a thief can just reset your phone and sell it.
If your data security is a huge concern to you, DO NOT unlock the bootloader.
If you are a potential target to a hacker attacks, DO NOT use a OnePlus phone. Get a Nexus 6P or a Pixel.
Also make sure, that your apps are not leaking your data. Apps with a storage permission and access to the internet could leak your data.
Click to expand...
Click to collapse
Very good point here. May I ask in what ways are Nexus 6P and Pixel more secure than Oneplus? Pixel seemed quite an attractive phone.
I am on OOS 3.5.3, is there anyway to find out what apps have access to internet and restrict that?
The app permission section of settings only allows changing permission to storage (among others) but I couldn't find any internet access permission.
The main security risk is that it allows anyone to flash something harmful without you knowing on to your system. Your data may be encrypted and protected but they can still flash something onto another partition.
You could be happily using your phone unaware there's a rogue app capturing and sending data to someone.
Zegnalabel said:
Many thanks for your response! This is very useful information to me.
Am I right to assume that even if my device is unlocked but with encryption enabled and no root, the person who has gotten hold of my phone will still be able to flash "dm-verity and forced encryption disabler" zip and supersu zip files to root my device in TWRP even when he fails to enter the password prompted by TWRP?
And this force encryption disabler as the name suggest only disable force encryption and it does not decrypt my already encrypted personal data? Which means he still does not have access to my data and after he had done the system modification and returns the phone back to me, the first thing I should do is to wipe clean every partition and restore back my nandroid which would consist of backups to all partitions. So it seems this is an acceptable risk all for the convenience of performing nandroid backup via the unlock/TWRP route.
Very good point here. May I ask in what ways are Nexus 6P and Pixel more secure than Oneplus? Pixel seemed quite an attractive phone.
I am on OOS 3.5.3, is there anyway to find out what apps have access to internet and restrict that?
The app permission section of settings only allows changing permission to storage (among others) but I couldn't find any internet access permission.
Click to expand...
Click to collapse
Your data is safe, it can't be decrypted, even with an unlocked bootloader And yes, if you wipe every partition, lock the bootloader and got no dm-verity error, after your stolen phone was returned to you, you should be safe.
Both Nexus 6P and Pixel are much safer than OnePlus, because they are getting a complete security patches every month. OnePlus is getting an imcomplete security patches and much later after their release.
You can limit access to internet via app settings. Open "about app", data usage and there you can turn off both access to wifi and mobile data.
Upgrade to OOS 4.0, it cointains important security patches and enhancements.
Michalko5896 said:
Your data is safe, it can't be decrypted, even with an unlocked bootloader And yes, if you wipe every partition, lock the bootloader and got no dm-verity error, after your stolen phone was returned to you, you should be safe.
Both Nexus 6P and Pixel are much safer than OnePlus, because they are getting a complete security patches every month. OnePlus is getting an imcomplete security patches and much later after their release.
You can limit access to internet via app settings. Open "about app", data usage and there you can turn off both access to wifi and mobile data.
Upgrade to OOS 4.0, it cointains important security patches and enhancements.
Click to expand...
Click to collapse
Thank you so much! Found the data usage setting and updated to 4.0. :laugh:
Michalko5896 said:
As long as your data is encrypted, it is safe and not accessible to any 3rd party.
But with an unlocked bootloader, you are open to a new forms of attacks like:
1. someone could steal your phone, modify your system to leak your data / password and then return it to you. Since dm-verity is OFF, you will not know, that your system is compromised.
2. someone could use a remote exploits (to launch his code and gain root privileges) to modify your system and leak your data / password and since dm-verity is OFF, you will not know, that your system is compromised.
...
Click to expand...
Click to collapse
Quick question, does the latest systemless SuperSU still leave dm-verity OFF ? It was my understanding that using it you don't need to flash the dm-verity-OFF script, is that true?
xclub_101 said:
Quick question, does the latest systemless SuperSU still leave dm-verity OFF ? It was my understanding that using it you don't need to flash the dm-verity-OFF script, is that true?
Click to expand...
Click to collapse
For root, you need to unlock the bootloader. And with the bootloader unlocked, dm-verity is not working and thus attacker could modify your system.
Michalko5896 said:
For root, you need to unlock the bootloader. And with the bootloader unlocked, dm-verity is not working and thus attacker could modify your system.
Click to expand...
Click to collapse
The bootloader being locked/unlocked should have little to do (directly) with dm-verity, dm-verity is only hash-checking the system partition.
That being said after some checking various detailed threads from Chainfire apparently SuperSU is still removing the dm-verity on the system partition since other than rooting in itself most rooted people also tend to touch the system partition with stuff like busybox and so on, so I guess this is it.
xclub_101 said:
The bootloader being locked/unlocked should have little to do (directly) with dm-verity, dm-verity is only hash-checking the system partition.
That being said after some checking various detailed threads from Chainfire apparently SuperSU is still removing the dm-verity on the system partition since other than rooting in itself most rooted people also tend to touch the system partition with stuff like busybox and so on, so I guess this is it.
Click to expand...
Click to collapse
well, google is stating, that unlocking bootloader will turn off the dm-verity.
This is an interesting discussion- I have a Nexus 5X, but I use a custom configuration:
1) locked bootloader
2) verity turned on for the system partition so that I can check the key fingerprint and verify integrity.
3) customized cm recovery - I installed my adb keys so I can connect to it. I also changed the signing keys, so I have to sign any roms that get flashed.
4) encrypted userdata with pattern protection. I think a password would be stronger, but I'm using a larger, complex pattern. Fingerprint unlock is turned on, which has its own attack surface.
I think the fingerprint sensor is the biggest risk. This is mitigated at reboot since the pattern will be required. If I built the recovery properly, the only way to flash anything would be to have access to my signing keys or adb keys. Of course, this is all still vulnerable to any unpatched exploits.
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Hgt45 said:
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Click to expand...
Click to collapse
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Rom said:
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Click to expand...
Click to collapse
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Hgt45 said:
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Click to expand...
Click to collapse
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Rom said:
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Click to expand...
Click to collapse
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Hgt45 said:
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Click to expand...
Click to collapse
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Rom said:
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Click to expand...
Click to collapse
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Hgt45 said:
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Click to expand...
Click to collapse
Hello,, any sugestion. ?
Have a great day.
H.
: (
Sent from my SM-N910P using Xposed Modules
Hgt45 said:
: (
Sent from my SM-N910P using Xposed Modules
Click to expand...
Click to collapse
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
samep said:
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hello Samep, I'm impressed and thankful on how you describe everything, I know its takes lon time and dedication to write,, THANKS A LOT, I know these will be the most comprehensive for many many users... I will try to do what you explained. ..
Also thanks to Rom and others for your suggestions and help.
Have a great weekend.. all the best wishes for all.
Regards
Herm.
slm note 4
note 4 I am using n910c 6.0.1. I have installed the device rooted twrp but I do not know which xposed i will install. I write armv7l in the kernel.
I do not know how many sdk I have to help you rejoice
THIS PROJECT IS NO LONGER SUPPORTED.
# Magisk Manager for Recovery Mode (mm)
## LEGAL
Copyright (C) 2017-2019, VR25 @ xda-developers
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
## DISCLAIMER
Always read/reread this reference prior to installing/upgrading this software.
While no cats have been harmed, the author assumes no responsibility for anything that might break due to the use/misuse of it.
To prevent fraud, do NOT mirror any link associated with this project; do NOT share builds (zips)! Share official links instead.
## DESCRIPTION
- Manage your Magisk modules from recovery (e.g., TWRP) -- run "sh /sdcard/mm" on recovery terminal.
Features list
- Automatically fix magisk.img (e2fsck -fy)
- List installed modules
- Toggle
- Core only mode
- Magic mount
- Disable
- Remove
## PREREQUISITE
- Magisk 17-19
## SETUP
- Install
1. Flash live (e.g., from Magisk Manager) or from custom recovery (e.g., TWRP).
- Uninstall
- Use Magisk Manager app or mm itself (supports `uninstall.sh`, too).
## USAGE
- First time (right after installing/updating) - run `mm` or `sh /sdcard/mm` on recovery terminal.
- Next times (while in recovery) - no need to re-flash the zip; simply run `sh /sdcard/mm` on recovery terminal.
- Follow the instructions/wizard. Everything is interactive.
- Pro tip: lazy people can try running `*/mm` instead of `sh /sdcard/mm`.
## LINKS
- [Donate](https://paypal.me/vr25xda/)
- [Facebook page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git repository](https://github.com/Magisk-Modules-Repo/mm)
- [Telegram channel](https://t.me/vr25_xda/)
- [Telegram profile](https://t.me/vr25xda/)
- [XDA thread](https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165)
## LATEST CHANGES
**2019.4.4 (201904040)**
- Complete redesign
- Magisk 17-19 support (including `uninstall.sh`)
- Toggle core only mode
- Updated information (copyright, documentation, and module description)
**2018.8.1 (201808010)**
- General optimizations
- New & simplified installer
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk 16.6).
- Updated documentation
Archive
Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man
BackToAndroid said:
Hey not sure whether this is right thread to ask, if not please redirect me.
I'm on AOKP, banking apps are detecting root and not allowing to access it, so I was asked to use Magisk.
Can you tell me how do I install it? Can I just download Magisk Manager and Magisk flash it via twrp? I'm noob to all rooting man
Click to expand...
Click to collapse
Yeah... You took a serious wrong turn.
Start by reading these threads:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
And if you need help, post here (with lots of details):
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk
Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).
Nitram08 said:
Sorry, maybe for my language, but I can not understand what this module is doing.
Enviado desde mi MI 5s Plus mediante Tapatalk
Click to expand...
Click to collapse
You should at least have basic understanding of what Magisk is and how it operates before jumping onto this thread. If you don't know what I mean by "Magisk Manager for Recovery Mode," then you've been skipping steps. I can't help you before you help yourself.
manos78 said:
Hi,
Great idea! I'll check and comment. :good:
Please, add it to the official repository.
It includes one option to enable/disable Magisk Core Mode Only?
And one suggestion: provide a ZIP file for launch directly the "mm" command without opening the Terminal (or use Aroma Installer).
Click to expand...
Click to collapse
Currently limited to the features listed. New capabilities will be added over time. The ability to manage Magisk settings is already in the works. Repo submission status -- awaiting approval.
Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?
dodgyme said:
Firstly, thank you. I've used another mod that allows using terminal to get rid of modules but it's not as fluid in usage as this one. However, i have one question; While i was able to use it in recovery, I'm not sure I understand clearly about whether or not this can be used while the system is fully loaded. I tried accessing the app through the os terminal but it acts as if I'm entering the wrong command. In twrp i did as you said and typed "mm" and it pulled right up. Yet, when i try the instructions that follow afterward to access the module while in the os, it tells me it can't be found. Am i missing something or is this only available through recovery?
Click to expand...
Click to collapse
The "module" part is only meant for updating the tool through Magisk Manager.
So, you don't have to constantly check XDA/GitHub for newer versions.
@Nitram08, if that's what you meant, sorry about the first answer! Next time, PLEASE give more detail, or you might get very similar reactions.
A basic rule of thumb:
- Poor info = "nothing happened -- bad post".
Hmmmmm
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...
dodgyme said:
So, just to clarify, it can only be used in twrp? If not, what's the exact command to use when I'm actually in the Android system using whatever terminal app I might be using...???
I ask because this part of your instructions confuses me:
"Else (after installing & rebooting) -- run `. /data/magisk/mm`."
My understanding suggests I can use it while in the actual system but when I use my terminal app it tells me it's not found...
Click to expand...
Click to collapse
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /data/magisk/mm" on terminal.
VR25 said:
Yeah... that line should be "after installing & rebooting into recovery". So, this is built for use in recovery mode only.
Instead of re-flashing every single time you need it, you simply run ". /data/magisk/mm" That is "dot space /magisk/mm".
In short
- First time (right after installing/updating) -- run "mm" (on recovery terminal)
- Next times (while in recovery) -- no need to re-flash the zip; simply run ". /magisk/mm" on terminal.
Click to expand...
Click to collapse
Understood, I appreciate your feedback and this little gem greatly. Thank you!
Type wrong, please ignore
I just want to thank Op for this. I can't tell you how many times I have gotten a bootloop from a faulty module making me have to delete magisk.img (always trying new things ). This makes it so much easier. Thanks much OP.
Thanks a bunch OP. This will be a life saver for those who don't take TWRP backups in TWRP before flashing a module, including me.
Sent from my Honor 8 Pro using XDA Labs
Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x
Amazing module, allows me to manage magisk in TWRP without issue. This is an essential module for every magisk user - if you can't boot after a module install, you can just remove the module and not worry about restoring a backup.
As an aside, also always have the Magisk uninstaller zip handy, it'll save your ass when your phone / tablet goes to **** when you're flashing modules like a meth addict.
Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...
Disable modules
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?
iqubik said:
Magisk log: "e 432:569 sendfile failed with 2: No such file or directory"
Any Modules can not find after install this
New modules installs but not works and not shows on list of android magisk manager.
Very Poor soft! Need to repair system after that!
Unistall_magisk.zip not repair this error!
I lost my system???
Android AOSP (Aex) latest 7.1.2
Xiaomi redmi 4x
Click to expand...
Click to collapse
Really good way of providing "useful" information...
You're dealing with different issues not related to this module in the first place. Could you describe exactly what you did and what actually happened afterwards?
njascgil said:
Great module, but I found something weird on my phone...
Is there any reason why a removed/disabled moduled would appear as such in the current TWRP session or just after rebooting from TWRP to recovery, but reappear after powering off and then booting to recovery via bootloader?
This (strange) thing happened to me minutes ago and the only way to remove the module (and boot Android again) was uninstalling and then reinstalling Magisk...
Click to expand...
Click to collapse
Odd...
Could you describe in details what you did to remove/disable the module in question?
beavis5706 said:
I'm trying to disable a module but I don't entirely understand the commands. I start Magisk Manager and select "e" to enable/disable modules. Then it shows:
<Toggle Module ON/OFF>
Greenify4Magisk (ON)
aik-mobile (ON)
mm (ON)
Input a matching WORD/string at once
- Press RETURN when done (or to cancel)
-- CTRL+C to exit
What command do I have to use to disable Greenify4Magisk?
Click to expand...
Click to collapse
You simply type a "matching WORD/string" and press ENTER. For example, to disable Greenify4Magisk, I would input "Green" or "4" or "Magisk" (whatever is unique to Greenify4Magisk).
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
You need to enter twrp and select the module causing the card machine to be deleted in the twrp advanced options, file management and data / ADB / modules directory
https://lanzoui.com/b03c2iqbi Password: han
This is the self-help brick rescue module generator made by our domestic great God. After you choose to set it, click OK to automatically brush it into the mask manager! However, you cannot select a language! You can translate screenshots by yourself! The general description of the function is to find that the card machine module regrets trying the boot mode several times. If it still fails to boot after reaching the number set above, all modules will be automatically disabled to achieve the boot effect
ruffpl said:
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
Click to expand...
Click to collapse
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Check from the section "Disabling/uninstalling modules manually". Maybe this will help
Thanks all for help I got it working. I read that all I need to do is just restart phone from safe mode and when phone will boot magisk will be disabled and it worked . I had open magisk app,removed module, flashed magisk boot image and its ok for now. Only problem that still exists is with some modules - when I want to install zip file I got extract error.
Safe mode has side effects. It's better to uninstall and install! After putting on the mask, brush in the automatic brick rescue module provided by me, and you can do it at will
If you don't understand, open the application, click the three vertical bar options on the right and directly click to confirm the default!