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.
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
Μπορεις να κανεις backup το apk και να το κανεις παλι Install μολις χαθει αλλα πρεπει να ξανακνεις Install το zip μεσω TWRP(για να ξαναεχεις root)
psykkuno said:
Μπορεις να κανεις backup το apk και να το κανεις παλι Install μολις χαθει αλλα πρεπει να ξανακνεις Install το zip μεσω TWRP(για να ξαναεχεις root)
Click to expand...
Click to collapse
Problem is i can't make backup cause i haven't installed it.
(Γεια σου πατριδα! νομιζω οι κανονες του xda δεν επιτρεπουν να γραφεις σε αλλη γλωσσα περα της Αγγλικης)
T3sla said:
Problem is i can't make backup cause i haven't installed it.
(Γεια σου πατριδα! νομιζω οι κανονες του xda δεν επιτρεπουν να γραφεις σε αλλη γλωσσα περα της Αγγλικης)
Click to expand...
Click to collapse
(Αραξε για μια φορα δεν λενε κατι)
In case you 've installed it xD,Otherwise you can install it(I can send you the apk) if you're interested
T3sla said:
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
Click to expand...
Click to collapse
Thanks. Amendment has been done.
T3sla said:
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
Click to expand...
Click to collapse
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?
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.
Naermorth said:
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.
Click to expand...
Click to collapse
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.
I've tried methods from MIUI Forum. The build.prop method didn't worked for me as it lacked some lines, but worked when I booted into TWRP. On second note, downgrading SuperSU to a lower version 2.65 solved the MTP issue as stated in MIUI Forum thread. Currently using SUperSU 2.82 came installed with Epic ROM.
Thank you very much.It worked for me
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)
Hi, someone help me out plz..
I have Redmi 4x and after rooting it lost mtp support.
So in order to fix it, i thought moving to stock rom will solve my problem and after flashing stock rom now my phone has become UNROOTED and TWRP is also now flushed out.
Now to use above 3 methods i need....
Root ------(But since there is no mtp support i can't install TWRP using adb to install magisk to root my phone).
Now since ROOT is not there i can't edit buil.prop file to enable mtp in it.
And since there is no MTP support i can't connect my phone to pc or any other rooted phone to use adb....
And also tried to flash TWRP img file from magisk but after rebooting it get replaced by stock recovery everytime.
Plz if someone know a solution to it plz reply.
I don't care if my data gets lost or the solution may brick my phone.
TheDeaDKiLLer said:
Hi, someone help me out plz..
I have Redmi 4x and after rooting it lost mtp support.
So in order to fix it, i thought moving to stock rom will solve my problem and after flashing stock rom now my phone has become UNROOTED and TWRP is also now flushed out.
Now to use above 3 methods i need....
Root ------(But since there is no mtp support i can't install TWRP using adb to install magisk to root my phone).
Now since ROOT is not there i can't edit buil.prop file to enable mtp in it.
And since there is no MTP support i can't connect my phone to pc or any other rooted phone to use adb....
And also tried to flash TWRP img file from magisk but after rebooting it get replaced by stock recovery everytime.
Plz if someone know a solution to it plz reply.
I don't care if my data gets lost or the solution may brick my phone.
Click to expand...
Click to collapse
Try to Install twrp in Fastboot and connect your mobile in twrp and transfer magisk and flash it. And upon restart you will get a rooted device.
SAFI_AFRIDI said:
Try to Install twrp in Fastboot and connect your mobile in twrp and transfer magisk and flash it. And upon restart you will get a rooted device.
Click to expand...
Click to collapse
Bro mtp is not supporting...I can't use fastboot mode
TheDeaDKiLLer said:
Bro mtp is not supporting...I can't use fastboot mode
Click to expand...
Click to collapse
Power off device and then power on holding volume (-) down button. And there is no need of mtp. Fastboot mode working without a problem.
What will i get by taking my phone in fastboot mode when i can't connect my device to pc to flash something via fastboot methods.
Or if u r trying to say that..."boot into TWRP after booting in fastboot mode"...Let me tell u that i have already tried this but stock recovery is replacing TWRP again and again.
If I am wrong plz suggest something else...
THANKS
Hello Everyone..!
I Am Using Samsung M30s [Rooted]
4 To 5 Months Ago My Phone MTP Stopped Working.
My Device Can't Be Recognized As A MTP Device By Any PC Via USB.
I Tried Many Cables And Many PCs.
Finally I Saw This Thread And Thought It Would Help.
But I Found This Thread Is Talking About Redmi And Also Started Long Ago.
So If Anyone Can Help Me It Would Be Nice.
And One More Thing My Phone Doesn't Show Fast Charging Since It Started Not Recognized By PC.
Thank You.!
Related
Hi I install one application (host name changer) and restart the phone and it stop working. Stops at HONOR screen. I enter to bootloader, open multi-tool and change recovery. Unfortunately bootloader not eorking ok, because when I wanted to upload IMG files to unbrick the phone, I get the error in Multi-tool. I decided to format/clean all data (I use CWM recovery and later also TWRP recovery). Again uploaded stock recovery and try use 3 buttons. Unfortunately installation start and after one second failed.
I also try to use QTADB to upload updata.apk but it not working - there is problem with bootloader. Also Minimal ADB not working - doesn't see Honor.
How can I upload / install rom now?
Is it possible instal ROM from external SD card? I try but on external card (using CWM) I see no files?
You can't use other recovery than the stock one to use 3 buttons. If the phone is not recognized by adb I'm not sure if you can restore it.
I used 3 buttons with stock recovery, and installation failed.
Did you replaced build.prop and local.prop with the original ones before 3 buttons?
Las night installed B310 without any problems.
I did not replace build.prop and local.prop because I install some other app which - I guess - modify build.prop and this is why I have that problems. Afert I reboot phone it brick on HONOR loco and Minimal ADB do not response. When I connect USB cable and enter to bootloader the PC see the phone, Hisuite start but can not connect. So I have problem with bootloader - it does not response using Minimal ADB. Onlu Multitool lets me change recovery. All I can do now is enter to recovery, bootloader, change recovery (only with Multitool), start install ROM (using 3 buttons) but it failed immediately.
Try to install stock dev rom 4.x.x
4.x.x roms have not prop checker so you can install them via 3btns
But how to upload this rom to HH? All I can do is using Minimal adb (not all function, but sometime I can use pull and push functions);
[email protected] said:
But how to upload this rom to HH? All I can do is using Minimal adb (not all function, but sometime I can use pull and push functions);
Click to expand...
Click to collapse
Put it on a SD Card?
If you can enter fastboot and your bootloader is unlocked you can try to flash the system.img via fastboot. But since you have CWM it shoul be unlocked
Finally the Multi-tool stoped responding (I couldn't upload img files to unbrick - there was an error).
But suddenly the Minimal ADB started responding, and I uploaded build.prop and after that I flash recovery.img, system.img, boot.img and cust.img.
Thanks for help.
The following is irrelevant. Just to share.
I messed up honor 6 plus once. It booted then it permanently hanged. Black screen, home launcher does not respond, no navigation bar. Power button worked with the options to reboot and power down.
Before I messed it up, I have unlocked the boot loader and flashed cwm and rooted by install zip.
I tried to fix it by cwm wipe data, wipe cache, wipe dalvik but that did not help.
Later I found that I was able to boot into fastboot mode and managed flashing back stock recovery. Then I downloaded a full stock ROM, decompressed the dload and copied it to root of a sdcard. Then I applied three finger update. It worked and fixed the problem.
HmMarques said:
Did you replaced build.prop and local.prop with the original ones before 3 buttons?
Las night installed B310 without any problems.
Click to expand...
Click to collapse
What are build.prop and local.prop ? Where to replace it ? How to get these type of file ?
Please help me my Honor 6 H60 L02 is bricked and I cant understand anything..
Devandrogeek said:
What are build.prop and local.prop ? Where to replace it ? How to get these type of file ?
Please help me my Honor 6 H60 L02 is bricked and I cant understand anything..
Click to expand...
Click to collapse
Read this thread carefully: http://forum.xda-developers.com/honor-6/general/honor-6-stock-roms-t2963180
There you have all information.
Search here for your buil.prop and local.prop : https://www.mediafire.com/folder/o3tgl8z4u21dz/STOCK_build.prop_&_local.prop
HmMarques said:
Read this thread carefully: http://forum.xda-developers.com/honor-6/general/honor-6-stock-roms-t2963180
There you have all information.
Search here for your buil.prop and local.prop : https://www.mediafire.com/folder/o3tgl8z4u21dz/STOCK_build.prop_&_local.prop
Click to expand...
Click to collapse
Actually my question was, how to get a stock recovery and how to set permissions ?
Devandrogeek said:
Actually my question was, how to get a stock recovery and how to set permissions ?
Click to expand...
Click to collapse
Well to set permissions you must use either root explorer or ES filexplorer, personally I use the last one with root privileges on.
after you move the files to correspondent folder you need to click on it for a few seconds and then go to properties/permissions and check only left column all 3 and middle column the first from above.
As for stock recovery go to the thread of Honor multi-tool, there you have how to and were to download stock recovery.
http://forum.xda-developers.com/honor-6/general/honor6-multi-tool-t2963060
HELP HELP HELP!!! Please!!! I cant put my Honor in fastmode!!! I tried to put cwm in Marshmallow 6.0 and bricked!!! I was able to use but I did a factory reset and it just dont pass the honor screen at the beginnin!!! Please Somebudy help!!! Sorry for my bad english!!!
Hi all, bricked my honor 6 plus firmware b133 after updating it with OTA b334 to b503 (marshmallow 6.0) RU.zip
Now after powering on there is bootlogo only for a second, and black screen after with flashing led lights with green and red.
Can't enter to recovery mode, only fastboot mode is available when connecting to pc.
Can flash without errors all files from fastboot: system.img, recovery.img, cust.img, boot.img but it can't help to fix phone
Will buy you some beer for successful solution
Thank you
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
JanSpatschek said:
I have a huge problem. After having a lot of issues rooting my device, I downgraded to COS11s and was finally able to root and install TWRP.
After that I tried to install Sultan's latest build, which failed. I then installed the latest CM12.1 Nightly (which is what he recommends if the installtion failes) and right after that his build, which worked - finally. I installed Gapps and rebooted.
I noticed I hadn't installed supersu and wanted to reboot to recovery to do so - but now it just won't boot into recovery! My phone turns on and boots straight to the lockscreen. I tried the button combination, the advanced reboot menu - everything. It just won't boot into recovery. I even reinstalled the recovery via fastboot (which supposedily was successful), but the problem remains.
Flashify doesn't even show an installed recovery!
HELP!
Click to expand...
Click to collapse
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
[deleted]
Ducter said:
Tried using adb yet? If you haven't, give it a try. If you don't have it set up, you can find several threads on how to do it, from full installs to small zip files. Considering you have fastboot working I assume abd also. Make sure USB debugging is on, plug your phone up and allow USB debugging when the prompt is displayed on your phone. Then adb reboot recovery.
Not familiar with what build you are on, some require you to enable root access mode from developer options, might check that also.
Click to expand...
Click to collapse
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
JanSpatschek said:
Thanks for you answer. I have adb set up. USB debugging is on. I will try adb reboot recovery. The weird thing is, it doesn't even boot into stock recovery (My first thought was that the phone replaced twrp with CM recovery somehow).
That's a good point, I will turn on root access and try again.
Click to expand...
Click to collapse
Another option, if nothing else seems to work is start over. I generally use nexus devices and flash factory images, looks like you can do that also on the one..
Hello,
I have the same problem. I unlocked my OPO, flashed the TWRP 2.8.7.0 and everything went good and smooth. Then I flashed CM12.1 and it worked. Now I wanted to downgrade TWRP to the TWRP 2.8.6.0 because of some issues with the latest version and after flashing the older version it will not boot to recovery at all...
Please help.
Thank you
EDIT: SOLVED!!
Okay, so I managed to get it back working again.
How I proceded:
1. http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and do everything that is said in the 3rd point of the first OP post. (+download the file for your OPO - either for 16GB or 64GB model - after you have it downloaded unpack it)
2. flash all the files listed in the 3rd point of the first OP post
3. boot in the OS, enable developer settings and enable USB debugging and allow it
4. get back in the fastboot mode and flash either TWRP 2.8.6.1 or later versions (because of Lollipop compatibility)
5. enjoy!
God bless you.
Hello,
I used Shuame from my PC to root my Digiflip Pro XT 801 via USB Debugging. It was able to root, and installed KingUser as the SU App. But when I restart the device, this app looses it's root status ( the app shows that the device is not rooted after I restart the device)
So every time I root using the Shuame, it has rooted status as long as device is not rebooted.
However I wanted to flash the custom ROM to restore the purity for my device. Now this ROM had worked earlier, but now it shows the signature verification error when I try to manually flash it.
Till now USB Debugging is working from my PC.
So, I wanted to change the Android Recovery to Clockwork to load the Custom Rom where I could explicitly disable signature verification option.
But Clockwork was not available for my device.
So I did something really stupid.
I searched clockwork version for a device that had almost the same spec in terms of architecture as well. I found Lenovo K900 having the same Intel Atom Chipset which is in my Digiflip Pro XT 801.
So I downloaded the Clockwork for that and installed on my tablet. Gave it the root authorization. In the app, clicked on Install Recovery. The device rebooted and nothing happened. No option for recovery showing in fastboot or a way to get into clockwork recovery.
However something unusual happened. Now USB Debugging is not working. When I enable USB Debugging, there is no sign for tablet being plugged in PC ( without enabling USB Debugging, the device is listed in Device Manager under Portable Devices and I can transfer files). With USB Debugging enabled the tablet is listed nowhere in PC, not even in the device manager with an exclamation symbol. And obviously the ADB Commands don't work from the terminal as the they say device not found.
Also saw some option to disable the signature verification of Android Recovery, by changing the code of "script-updater" in META-INF from ROM Zip file ( it was mentioned to remove the code till first semicolon ). Still I am getting the same error code in Android Recovery.
All I want to do is flash the custom ROM to bring everything to factory default. As I don't have the USB Debug feature, I cannot root once again. Neither I have any other Recovery like Clockwork or TWRP installed.
Please help........would be forever indebted !!!!!!!!
shashwat.vikram50 said:
Hello,
I used Shuame from my PC to root my Digiflip Pro XT 801 via USB Debugging. It was able to root, and installed KingUser as the SU App. But when I restart the device, this app looses it's root status ( the app shows that the device is not rooted after I restart the device)
So every time I root using the Shuame, it has rooted status as long as device is not rebooted.
However I wanted to flash the custom ROM to restore the purity for my device. Now this ROM had worked earlier, but now it shows the signature verification error when I try to manually flash it.
Till now USB Debugging is working from my PC.
So, I wanted to change the Android Recovery to Clockwork to load the Custom Rom where I could explicitly disable signature verification option.
But Clockwork was not available for my device.
So I did something really stupid.
I searched clockwork version for a device that had almost the same spec in terms of architecture as well. I found Lenovo K900 having the same Intel Atom Chipset which is in my Digiflip Pro XT 801.
So I downloaded the Clockwork for that and installed on my tablet. Gave it the root authorization. In the app, clicked on Install Recovery. The device rebooted and nothing happened. No option for recovery showing in fastboot or a way to get into clockwork recovery.
However something unusual happened. Now USB Debugging is not working. When I enable USB Debugging, there is no sign for tablet being plugged in PC ( without enabling USB Debugging, the device is listed in Device Manager under Portable Devices and I can transfer files). With USB Debugging enabled the tablet is listed nowhere in PC, not even in the device manager with an exclamation symbol. And obviously the ADB Commands don't work from the terminal as the they say device not found.
Also saw some option to disable the signature verification of Android Recovery, by changing the code of "script-updater" in META-INF from ROM Zip file ( it was mentioned to remove the code till first semicolon ). Still I am getting the same error code in Android Recovery.
All I want to do is flash the custom ROM to bring everything to factory default. As I don't have the USB Debug feature, I cannot root once again. Neither I have any other Recovery like Clockwork or TWRP installed.
Please help........would be forever indebted !!!!!!!!
Click to expand...
Click to collapse
I suggest you to go back from the start and flash your custom ROM via so flash tool.. In that way you'll have a clean device & ready to flash other custom roms
I have problems with my pantech discover magnus P9090, the problem is that the phone is completely bricked and dead. When i turned on the phone, it simply just shows BLACK SCREEN ( No Logo and nothing else). My assumption is that there is no OS inside or something causes it to be bricked. I have done almost everything by using Android Recovery (Not custom recovery) to do factory reset and wipe cache. I rebooted it and it doesn't work either. So i found a solution which is by using apply update from ADB. I understand the process but the only problem is
The device is not detected by ADB when i type "adb devices" it could be two problems:
a. No drivers for this phone installed (While i try to update driver, it fails)
b. USB Debugging off (Since phone can't get into OS, so im confused how to turn it on via other ways)
I got the Custom rom and CWM recovery image but how can i install the recovery and ROM if ADB isn't detecting the phone. I can't even use sideload command.
My plan to fix this is by installing CWM with the command "fastboot flash recovery [filename]" and then using CWM to push the file ROM into phone and install zip in SD card. However, it links back that i need the phone to be detected first. Anyone can help me? Thank you so much. Im so badly want to revive this phone. :good:
There's no other way until pantech usa release pdl file for restore discover..
Sent from my ZTE N986 using XDA-Developers mobile app
Installing CWM Recovery + Rooting Samsung Galaxy J7 prime ( SM-G610F/SM-G610M )
Tested & WorkingKnow Issue
SDCARD & EXTSDCARD not mounting in CWM ( Not being able to flash/install ZIPs )
FixI suggest you to Install zip using sideload, here's a step by step guide :
First boot up your phone into CWM recovery
Go to Install zip update package and select Install zip from sideload
Now connect your android device to your computer
Download this and extract it.
Open command prompt in the ADB folder (mfastboot-v2 folder) by right clicking in the empty space of the folder while holding the Shift key.
Copy the Zip file you want to install on your device to the ADB folder, for example Xposed.zip.
Run the following command to sideload zip to your phone : adb sideload <filename.Zip>
Example adb sideload Xposed.zip
Voila! That's how you can flash Zip files
First Part: Installing CWM Recovery
NOTE BEFORE
Please make sure to follow the guide carefully and thoroughly as i won't be responsible for any damages caused to your device and also keep in mind that rooting your phone will automatically void your warranty.
MUST READ
Before you start, please note that this root has only been tested on the SM-G610F and SM-G610M variants of the Samsung Galaxy J7 prime, so kindly check your phone's variant before proceeding.(Check the back of your device)
Required Files:
CWM & ROOT
Samsung USB Driver
ADB USB Driver
How to install CWM Recovery
After downloading the required files make sure your system has an active Samsung USB Driver or you can simply download it from here
Also don't forget to Enable USB Debugging & Unlock OEM, this can be done by going to Developer Options and make sure to have these 2 boxes checked.
Then go to Lockscreen and Security under Settings and enable Unknown Sources.
With these done we are ready to kick-off!
Step by Step Instructions
STEP 1 : Connect your phone to your computer & Allow access to your device when the MTP Connection box pops up
STEP 2 : Now go to the ROOT J7 PRIME(2016) folder ( you will need to extract the rar file) you just downloaded and run 1-EnterDownloadMode.bat
STEP 3 : Wait for the phone to reboot into Download Mode ( If nothing happens after running 1-EnterDownloadMode.bat then you might need to disconnect and reconnect your USB cable and Allow USB Debugging (Check Always allow from this computer) when it prompts you. With this done, your device should automatically reboot into Downloading Mode.
STEP 4 : In Downloading Mode Run Odinv3.10.7.exe (Found in ROOT J7 PRIME(2016) folder) and click on AP and open
SM-G610_cwm.tar from ROOT J7 PRIME(2016) folder
After this go to Options in Odinv3.10.7.exe and uncheck both Auto Reboot & F Reset Time and finally click on start to execute the installation of CWM recovery. Wait for it to finish (When it says 'PASS!') and after that press and hold the Volume Down, Power and Home Button together ( To get out of download Mode ) and when you see the phone gets rebooted press and hold Volume Up, Power button and Home button to boot into CWM Recovery
STEP 5 : Enjoy! You now have CWM recovery installed
Second Part: Installing SuperSU
MUST READ
Use Volume buttons and power button in CWM Recovery to navigate through and select the different options.
How to Root
STEP 1 : In CWM Recovery, go to install zip package and then select install zip from sideload.
At this point you will have to connect your device to your computer and once done run ROOT.bat from ROOT J7 PRIME(2016) folder and wait for it to finish.
STEP 2 : Now run 3-Reboot.bat from ROOT J7 PRIME(2016) folder and you should see your phone get rebooted.
STEP 3 : Enjoy! You have just rooted your phone!
If you want to flash the stock recovery just repeat the steps for installing CWM but select SM-G610F_stock_recovery.tar or
SM-G610M_stock_recovery.tar instead of SM-G610_cwm.tar
P.S You now have a voided warranty
Cheers!
Just FYI before you catch flak from a mod, the work you are linking, the adfly shortened links are a no go on xda.
ShinySide said:
Just FYI before you catch flak from a mod, the work you are linking, the adfly shortened links are a no go on xda.
Click to expand...
Click to collapse
rlly?
Oh ok since it is against the rules i'll kindly remove them
Thanks for letting me know btw
Thanks a lot,but flashing supersu from cwm without running .bat wouldn't work?my pc is in repair i can only use the pc on my work office and i dont have admin privilege,cmd is disabled and i doubt .bat would work i only can install odin
fakih.m7md said:
Thanks a lot,but flashing supersu from cwm without running .bat wouldn't work?my pc is in repair i can only use the pc on my work office and i dont have admin privilege,cmd is disabled and i doubt .bat would work i only can install odin
Click to expand...
Click to collapse
It should work i guess but i recommend you to flash the ROOT.bat since it was tested and working 100%
HaxerProz said:
It should work i guess but i recommend you to flash the ROOT.bat since it was tested and working 100%
Click to expand...
Click to collapse
let it be the first test,i will flash supersu and if it fail i will try to run .bat,i already have a stock rom of j7 prime in case if anything went wrong
fakih.m7md said:
let it be the first test,i will flash supersu and if it fail i will try to run .bat,i already have a stock rom of j7 prime in case if anything went wrong
Click to expand...
Click to collapse
Ok but have you flashed CWM through Odin yet?
HaxerProz said:
Ok but have you flashed CWM through Odin yet?
Click to expand...
Click to collapse
no
fakih.m7md said:
no
Click to expand...
Click to collapse
You should do that first to be able to root..you know right?
absolutely i flashed a lot of custom recoveries before even in this mobile i have flashed twrp but root failed because of touch issue in twrp
fakih.m7md said:
absolutely i flashed a lot of custom recoveries before even in this mobile i have flashed twrp but root failed because of touch issue in twrp
Click to expand...
Click to collapse
You tried to flash twrp on J7 prime? The official TWRP isn't available as far as i know
HaxerProz said:
You tried to flash twrp on J7 prime?
Click to expand...
Click to collapse
yes i used mouse via otg to fix touch issue but adb sideload didn't work
fakih.m7md said:
yes i used mouse via otg to fix touch issue but adb sideload didn't work
Click to expand...
Click to collapse
k let me know how's it going btw
You tried this http://forum.xda-developers.com/galaxy-j7/how-to/guide-root-galaxy-j7-prime-twrp-t3503926 i guess..yea the touchscreen isnt responding we gotta wait for official twrp
HaxerProz said:
k let me know how's going btw
You tried this http://forum.xda-developers.com/galaxy-j7/how-to/guide-root-galaxy-j7-prime-twrp-t3503926 ?
Click to expand...
Click to collapse
yes and i visited this post more than 10000 times since 20 november to look for a solution to root j7 prime
fakih.m7md said:
yes and i visited this post more than 10000 since 20 november to look for a solution to root j7 prime
Click to expand...
Click to collapse
me too....till i finally came up with a solution after hours of testing
HaxerProz said:
me too....till i finally came up with a solution after hours of testing
Click to expand...
Click to collapse
thanks a lot,you're great
fakih.m7md said:
thanks a lot,you're great
Click to expand...
Click to collapse
You're welcome
I booted into recovery and installed CWM. It passed as well. However, when I boot into recovery, I still dont get CWM recovery. I have made sure I have set OEM UNLOCK properly. Please help!!
archer797 said:
I booted into recovery and installed CWM. It passed as well. However, when I boot into recovery, I still dont get CWM recovery. I have made sure I have set OEM UNLOCK properly. Please help!!
Click to expand...
Click to collapse
Just repeat all the steps from the beginning and see if it works..
Btw you are supposed to boot into Downloading mode and from there flash CWM Recovery using Odin..i don't know what you have missed.