Last Updated on September 18, 2024 by Mathew Diekhake
When I first got into tech writing, I thought it was cool. I didn’t get into it because I was forced to or it was any necessity to pursue due to a lack of other work choices. I just realized that it was something I enjoyed doing. Sites like Redmond Pie, who were rolling out around ten articles per day from various authors with that content being surrounded by banner advertisements was like a future compulsive gambler arriving in Las Vegas for the first time and looking up at the lights of a nighttime. I was awestruck, and I had just been introduced to a universe of a lot of things I knew nothing about, but I knew enough to know that I was fascinated by it, and I wanted in. I need to be a part of what I was seeing.
In an attempt to try to rationalize a reason as to why it might be possible for me to get into developing one of these websites, I asked one of my experienced blogger and developer friends what was the difference between sites like Redmond Pie and us. He replied “nothing, just a lot of hard work. But we can do everything they are doing. We have the knowledge to do what they are doing. It just doesn’t change the fact that you need to be writing pretty much all day”. So I had been informed that I had everything in place to create one of these things that I wanted, and essentially the only thing that stood in my way was hard work. Having being criticized in the past for having what people consider a poor work ethic, I took on the challenge.
From then on I was met with two unique classes of people and their opinions on what I was doing. There were those who thought I didn’t have the ability to do what I do now and then there were the other people who didn’t believe there was any money in this industry. Neither of those views is right at all, and it’s a shame they were the only two judgments I was greeted with. It isolated me, and I took the challenge head on. I sat in a room for roughly three years writing day in and day out until I had developed not only enough of a base product for a business, but also enough knowledge to truly know what I had gotten into.
I can tell you that anyone who hasn’t done what I do for at least several years, does not have the slightest idea of what it is that I really do. Knowing that, your negative faces and awkward conversations about how much you don’t believe in me aren’t phasing me at all.
Sitting here now into my fifth year, I can tell you that this is looking something that is similar to a game of darts. You can throw a few and you might hit a bullseye, or you can throw all day and not hit any bullseyes. The thing about writing online is that you can calculate these bulleyes. It’s not done through physicality at all but mentality. That means you can tackle this job either one of two ways and be successful at it: either calculate your throws so that a high percentage of them land on bulls eyes or just throw heaps of darts all day long and as long as you aren’t half bad at throwing you will land on a few bulls eyes.
I tell you all this to take you on a part of my journey to get me to where I am today. I can tell you that I’ve written nearly more rooting guides than anyone in the world and the world of device customization is what I enjoy writing on most for several reasons. With that said, the Samsung Galaxy J7 smartphone is a device I know really well, and I’ve already covered the device in many articles. I’ve also held several conversations with Chainfire, the developer of the rooting tool we are using in this guide. The result is you can follow this guide with confidence.
The CF-Auto-Root tool in this guide is based on the LMY48B.J700MUBU1AOI2 firmware. That same firmware has rolled out to at least one area in the world. It doesn’t matter if you are running that same firmware version on your Samsung Galaxy J7 smartphone or not. The developer, Chainfire, just gives it to us so we can use the information as an indicator.
Files You Need
- Download the new CF-Auto-Root for the SM-J700M smartphone running Android 5.1.1.
- Sometimes the Samsung Galaxy J7 smartphone will get new software updates rolling out over the air to people’s notification panels — it’s the same way for just about every Samsung device. These new firmware updates can bring new bootloader with them and on occasion the new bootloaders can prevent a device from booting or flashing might fail. In those times, you should head over to the official Chainfire CF-Auto-Root thread and the developer will see the message and fix the problem.
Rooting the Samsung Galaxy J7 SM-J700M 4G Duos smartphone running the Android 5.1.1 Lollipop update
- Enable the Galaxy J7’s USB Debugging Mode so you can connect it to the computer and use the flashing tool.
- Extract the rooting package to the computer and have it on the desktop.
- Install the Samsung USB Drivers so the J7 smartphone can get connected to the flashing app when we open it up soon.
- Double-click the Odin flashing app and wait for the user interface to open — do not make any changes from the default settings found from the Odin user interface.
- Boot the Samsung Galaxy J7 up into download mode and then connect it to the computer with the USB cable.
- Check the drivers are working by looking for a blue or yellow ID: COM port color from the Odin user interface.
- Click the AP button once you know the ID: COM port is showing your device is connected.
- Upload the J7’s tar.md5 rooting file that is on the desktop of the computer.
- Click the Start button and wait for the rooting to complete.
- Wait until you can see the Samsung Galaxy J7’s smartphone display say that it is now installing the SuperSU application, cleaning up the cache partition and then flashing the stock recovery back on your device.
In conclusion, that’s how to root the Samsung Galaxy J7 smartphone with the SM-J700M model number running on the Android 5.1.1 Lollipop software updates using Chainfire’s CF-Auto-Root tool. The flashing of the stock recovery during the last step is an important one because Chainfire — the developer of the CF-Auto-Root tool — says that your device will not be rooted unless it gets into recovery mode. You can fix that problem for any device that did not get into recovery mode by manually booting into recovery mode instead.
Furthermore, anyone who is still suffering from problems should try installing one of the other available Odin flashing apps and see if that helps the problem. It’s been reported several times that some people find one version of Odin doesn’t work for them, so they try another version, and it did work.