[GUIDE] MTP connection Lost after rooting the device (Solved).

SAFI_AFRIDI

Senior Member
Jan 14, 2015
159
100
0
Peshawar
www.youtube.com
Dear Redmi 4 Prime User Many device looses it's MTP connection after Rooting. Its just because the latest SU binary has a comparability issues and it disabled this option when you are using the latest SU Binary. here i will Show 3 Methods for Recovering it Again.

1st Method : Restore it by Adding the Following Lines in the Build.prop.
ro.adb.secure=0
persist.adb.notify=1
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb

Now reboot the Phone and it should be working.


2nd Method: Recover MTP setting by Installing MTP Enabler

This Application provides the following functionalities.
1: Option for deactivate MTP/PTP, when device will be locked(screen off) adhoc or after preset delay
2: Option for reactivate MTP/PTP after unlocking device
3: Option for blocking MTP/PTP, when USB is connected to untrusted PC.
This Application don't touch any system-file (no init component is touched or needed)! - But it needs a rooted device!


3rd Method: By Unrooting and Installing Magisk Manager

For this Option your Devices Must be Unlocked Bootloader and Installed TWRP.
Follow these Steps.
1: Open the SU Manager and Click on Full Unroot.
2: Then Install Magisk Manager.
3: Open the Magisk Manager and select Download and Install. it will download the Latest Magisk Binary on the Device. but dont install it now.
4: Reboot the Device in TWRP and Install the Latest Magisk Binary and Reboot the System and you are now rooted with the MTP enabled.


Hit Thanks if this really Help you.
 
Last edited:

T3sla

Senior Member
Jan 14, 2012
448
107
73
Thessaloniki
Problem is google removed magisk manager from playstore.Also i think you should add two more lines in the first method to work, at least in my case :

ro.adb.secure=0
persist.adb.notify=1
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
 
Last edited:

psykkuno

Senior Member
Aug 23, 2016
392
469
0
Athens
Μπορεις να κανεις backup το apk και να το κανεις παλι Install μολις χαθει αλλα πρεπει να ξανακνεις Install το zip μεσω TWRP(για να ξαναεχεις root)
 
  • Like
Reactions: T3sla

T3sla

Senior Member
Jan 14, 2012
448
107
73
Thessaloniki
Μπορεις να κανεις backup το apk και να το κανεις παλι Install μολις χαθει αλλα πρεπει να ξανακνεις Install το zip μεσω TWRP(για να ξαναεχεις root)
Problem is i can't make backup cause i haven't installed it.

(Γεια σου πατριδα! νομιζω οι κανονες του xda δεν επιτρεπουν να γραφεις σε αλλη γλωσσα περα της Αγγλικης)
 

psykkuno

Senior Member
Aug 23, 2016
392
469
0
Athens
Problem is i can't make backup cause i haven't installed it.

(Γεια σου πατριδα! νομιζω οι κανονες του xda δεν επιτρεπουν να γραφεις σε αλλη γλωσσα περα της Αγγλικης)
(Αραξε για μια φορα δεν λενε κατι)
In case you 've installed it xD,Otherwise you can install it(I can send you the apk) if you're interested
 

deidovalds

New member
Jun 23, 2017
1
0
0
Problem is google removed magisk manager from playstore.Also i think you should add two more lines in the first method to work, at least in my case :

ro.adb.secure=0
persist.adb.notify=1
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Thanks, big help! Now I can use my device's USB!
Just an addition, do you really need to turn on USB Debugging? Is it possible to bring it back to be like the original behavior?
No need to Enable USB Debugging?
 

Naermorth

New member
Jun 12, 2017
4
0
0
Hey. First solution worked like a charm at first but, after another restart, my usb is not working again. I have checked the build.prop and everything is still written tho, I seem to be unable to re-edit build.prop even though I have no issue with the root (I can change anything else, just not build.prop).

Also, I had tried writing a new one (copy-pasted, changed) to internal storage and, overwritten the system/build.prop file with it and restarting after. I had a boot loop and had to re-install everything from scratch.

Any suggestions? Thanks in advance.
 

SAFI_AFRIDI

Senior Member
Jan 14, 2015
159
100
0
Peshawar
www.youtube.com
Hey. First solution worked like a charm at first but, after another restart, my usb is not working again. I have checked the build.prop and everything is still written tho, I seem to be unable to re-edit build.prop even though I have no issue with the root (I can change anything else, just not build.prop).

Also, I had tried writing a new one (copy-pasted, changed) to internal storage and, overwritten the system/build.prop file with it and restarting after. I had a boot loop and had to re-install everything from scratch.

Any suggestions? Thanks in advance.
Try to fix the permission of the Build.prop after editing, if you faces such error again. Then I will suggest you the Majsik as it is the best option for now as they are using the latest binary.
 

menachg

Member
Sep 22, 2015
15
0
0
I had the same problem and after using method 1 I can connect to the computer like normal.
but I still face a problem that I can't enable the "usb tethering" option in the settings
even when I try to enable tethering from adb shell using commands from Here
did anyone else have this problem and do you have a fix for that?
--update--
after using it a bit I noticed that still normal usb behavior wasn't restored with method 1 it just made a connection in a specific way and no way to change it(no mtp connection without adb no tethering etc)
and after reading a bit more,many people reported it's a bug in supersu after updating from v2.65
so I did full unroot from super su app(WARNING:causes bootloop after reboot with access only to fastboot)
than I booted into twrp recovery from img in the pc using "fastboot boot twrp.img" command and just flashed supersu v2.65 from here like rooting from scratch and after reboot the phone worked fine with no problems at all with mtp or tethering
hope this helps anyone else who has this problem
(maybe even add downgrading to v2.65 as a 4th solution)
 
Last edited: