Not quite sure how to setup and use our Android Call Recording feature? Or maybe you HAVE set it up and even recorded a call, but when you listened to the recording something just didn’t sound right..
If we’ve hit the mark, then you’ll be glad to know that in this post we’ll show you how to maximize the chances of getting a perfect recording every time.
(If you are interested in iPhone Call Recording, we cover it in another post)
So let’s begin!
Finding The Best Android Call Recording Source
To better understand why call recordings aren’t always clear, you should understand how our Call Recording feature works.. Basically, when FlexiSPY first activates it tries to automatically find the best call recording method, and it has several sources to choose from.
Usually the microphone source works best, and it may choose that. But – there may be a better recording source for your device.
Better Results Through Manual Settings
FlexiSPY sometimes can’t automatically find the best audio source. The reason is complicated, but the short version is that there are so many variations of android devices, all running on different networks, that FlexiSPY sometimes gets it wrong.
You’ll know that this happened if:
Only one side of the conversation gets recorded.
You can only hear static
The recorded voices sound distant
Fortunately, this is where manually setting the audio source can help. Through the manual settings you can test which source works best for the device that FlexiSPY is installed on.
Here’s how to manually set the audio source:
1. Log into your online portal.
2. Click Control Center.
3. Click Call Controls.
4. Click Set Audio Recording Source.
All the possible call recording sources will then appear.
Here’s a breakdown of the sources:
Microphone
This is the call recording source that FlexiSPY uses by default.
(Samsung devices work well on this setting)
Voice Call
This source uses both directions (known as uplink and downlink) to increase the chances of recording both sides of a call. It may not work with all devices though – if it fails it will result in the recording of only one side of the call.
AOSP
This is a proprietary recording source for all devices.
(non-rooted Motorola and Huawei Android devices should choose this source for best results.)
Legacy
This is the oldest and most stable form of call recording. But on newer Android devices both sides may not be recorded.
(If all other call recording sources produce unsatisfactory results, then use this.)
ALSA
This source is for rooted Android devices only.
So if you’re unhappy with Call Recording and the device is unrooted you’ll want to:
Deactivate & Uninstall FlexiSPY from the device
Root the device
Reinstall & Reactivate FlexiSPY
Set ALSA as the Call Recording source
Conclusion
There’s no universal Call Recording source that works for every Android device. But if you try all the sources we mentioned in this article, there’s a good chance that your recordings work just fine!
Here at FlexiSPY we have put our trusty Samsung Galaxy S4 through many things other Android devices would never wish to endure in order to write articles or find out new things about rooting and firmware or even just for testing FlexiSPY itself.
That is why we felt that the Samsung Galaxy S4 deserved a little love and it seems that official Android L firmware for the Samsung Galaxy S4 has been leaked and released and this guide will show you how to install it.
But first, a few things to note.
Disclaimer:
You perform the steps in this guide at your own risk. Whilst the guide is correct at the time of writing FlexiSPY is not responsible for any issues or errors that may occur once this firmware has been applied to the phone.
Now, a few things to note about our device that was used and the ROM itself.
We used an international Samsung Galaxy S4 whose model number is GT-I9500.
We are not responsible if you try this on any other model other than what we have listed above and it breaks your device.
The ROM itself is official, Android OS is 5.0.1 but there are a few things to be wary of.
The ROM is essentially leaked from the Chinese market version which means that many things in the ROM are Chinese or Chinese related even though the ROM has an English option when you set up the device for the first time.
This means that things like the Download Mode text that is usually in English is now in Chinese.
This ROM can be rooted using Odin which we show below.
This ROM DOES NOT have Google applications installed such as the Play Store or Gmail, you must install them manually (see the end of the guide for how to do this).
And finally, and most importantly, in case you missed it.
FlexiSPY is not officially compatible with Android L (OS 5.0.X) in any way at this time.
This guide is for research purposes only.
Now that we have mentioned all that, for those who cannot wait for Android L to be rolled out for their S4 (GT-I9500) by their carrier in their region can follow these steps to upgrade and try out the latest and greatest version of the Android OS.
Download the Android L ROM file
You need to download the ROM file to your PC if you wish to upgrade your Samsung Galaxy S4 (GT-I9500) to Android L.
You can download it from here.
Once downloaded save it to an easy to find location such as your desktop.
Once downloaded you will have a zip filed called GT-I9500.
When you extract it to its own folder and then open that folder it should look like this.
Inside here you have each component that makes up an Android ROM.
Please make sure you have BACKED UP YOUR DEVICEbefore you attempt to perform this guide.
Download the Odin rooting tool
In order to flash the downloaded ROM to your device you must download Odin. You can get Odin from here.
Once you have downloaded it extract it to its own folder.
Download and install the USB drivers for the Samsung Galaxy S4 (GT-I9500) to your PC
So that Odin can recognise your Samsung Galaxy S4 when you connect it to your PC please download and install the USB drivers which you can get from here.
Download the file and then run it to install the USB drivers on to your PC.
Now that you have done that, as well as having backed up your device, it is now time to put the device in to Download mode.
Make sure the device is turned off completely
Press and hold the Volume down key, the main button and power
When the device turns on, if it is in download mode, it should look like this
Press the Volume up button to continue it should look like the picture on the right.
The device is now in Download mode so connect it to your PC via the USB cable and run Odin.
Providing you have installed the drivers for the Samsung Galaxy S4 on your PC Odin should look like this.
As you can see the device has been recognised as you can see Added!!.
Now it is time to add the Android L ROM to Odin.
Click the BL button and browse to the BL part of the Android L ROM and then click Open.
It will now be added to Odin.
Click the AP button and browse to the AP part of the Android L ROM and then click Open.
It will then be added to Odin. This may take some time so please be patient.
Click the CP button and browse to the CP part of the Android L ROM and then click Open.
It will then be added to Odin.
Click the CSC button and browse to the CSC part of the Android L ROM and then click Open.
This will then be added to Odin.
When you have added all parts Odin should look like this.
Click Start to begin the flashing process.
DO NOT REMOVE THE DEVICE FROM YOUR COMPUTER OR RESTART YOUR PC IN ANY WAY
Once it has been done Odin will say PASS and the device will restart itself.
You can now disconnect the device from your computer and wait for it to boot up in to Android L for the first time. This may take some time so please be patient.
Now that you have upgraded your Samsung Galaxy S4 you need to follow the setup steps that appear on the screen of your device to set the device language, internet settings and such.
Once you have completed the setup wizard on the device the device is then ready to use.
Install a custom recovery and root the device
If you wish to root your Samsung Galaxy S4 running the new Android L OS you need to flash a custom recovery to the device.
Download the file to your computer and save it to your desktop.
Now you need to put the device in download mode again as you did before and connect it to your PC and run Odin.
With Odin open click the AP option and browse to the recovery file you just downloaded.
Odin should look like this.
Click Start to flash the custom recovery and then Odin will say PASS when done and the device will restart itself and it should be rooted.
You can test for root by looking for an application shown called SuperSU. If you see this then the device has been rooted as we show below.
Install Google Apps
The final thing to do is to install Google applications on to the device as these are not preloaded on to the device due to the version of Android L being for the Chinese market.
Save the file to your PC and then extract it to its own folder.
Now that you have downloaded the file to your PC you now need to copy it to the Samsung Galaxy S4.
To do that simply connect the phone to your PC using the USB cable and it should be recognized in Windows.
Browse to an easy to find location on the device, such as the Downloads folder and then copy the file you downloaded to that folder so it should look like this.
Now that you have done that disconnect the device from the PC and turn off the device completely.
Hold down the Volume Up, Main button and Power button together until the Samsung logo appears.
When the screen goes black let go of the buttons and, after a few seconds, the phone recovery mode should appear.
With the phone in recovery mode do the following.
Tap Install Zip.
Tap Choose zip from /sdcard
Tap the folder where you copied the file to (such as the Downloads folder).
Tap the file.
Tap Yes and then wait for it to be applied.
Once done restart the device.
The device will restart and update the applications installed and you should now see many Google Apps such as the Play Store.
You can then sign in to the Play Store on the Samsung Galaxy S4 using your Google ID to install additional Google applications such as Gmail which is not installed using the steps above and has to be done using the Play Store alone.
After you have done that your Samsung Galaxy S4 is ready for use with Android L.
[box type=”warning”] We no longer maintain rooting guides on our blog. This means that your phone might not be compatible with this guide. If you’re not sure, please consult our rooting team, who will root your phone, and install FlexiSPY for you, for a fee.
Click here to learn more about our rooting service[/box]
This guide will show you how to root the Xolo Q1010i phone.
Disclaimer: FlexiSPY is not responsible for rooting the Android device in any way. Before performing any of these steps make sure you back up your Android device completely.
What do you need to root the Xolo Q1010i?
In order to root the Xolo Q1010i you will need the following:
The Xolo Q1010i you wish to root in your hand
A PC
Step 1 – Download and copy Framaroot to the Xolo Q1010i
Rooting the phone is done using Framaroot which you can get from here. Save the file to your computer in an easy to find location on your PC
You now need to copy Framaroot on to the phone which is done as follows:
Connect the Xolo Q1010i to Your PC
Copy the file you downloaded onto the phone in an easy to find location such as the downloads folder.
Step 2 – Root the Xolo Q1010i
You can now install Framaroot on the phone and root it. This is done by doing the following:
Disconnect the Xolo Q1010i from your PC.
On the phone, browse to the download folder and run Framaroot (you may need to install a file manager from the Play Store to do this; enable installation of unknown sources if asked).
Install Framaroot on to the phone.
Run Framaroot and tap Install Superuser
Tap Boromir and wait for the rooting process to complete.
Reboot the device when asked.
When the Xolo Q1010i has rebooted look for the SuperSU icon which means that you have successfully rooted the phone.
Sometimes you might want to change a capturing setting in the FlexiSPY control panel. Maybe you’d like to activate our Ambient Recording feature, or change what app’s you’re monitoring. Whatever the case, you’re given the option to choose the method that FlexiSPY will use to send the changes to the phone.
There are three ways to for sending commands to your Android device using FlexiSPY.
Network (FREE, works on all mobiles)
Push Notification (FREE, but not available on all mobiles)
SMS commands (requires purchase of SMS credits, works on all mobiles)
SMS credits are an optional way to send commands to FlexiSPY. They are used within Control Center in your online account to make sure time sensitive commands are processed immediately (e.g. Send Immediate – to send all data not yet uploaded immediately to your online account.)
The default is push notifications, or network. But these are sometimes slow, and can take an hour to arrive – which is perfectly fine for most users.
SMS commands arrive instantly, and are appropriate for professional use, where timing is important. You can always send SMS commands from your own mobile device, so you don’t ever need to buy SMS credits.
But for those users who value convenience, and the best possible performance, we give them the option to buy credits directly from inside the account portal inside your account tab.
Let’s take a look at how push notifications work;
Everything takes place inside the Control Center in your online account.
Just browse to the category for the command you wish to set and set the options you want to change.
Click Sync Now when done and wait for the push notification to be sent to the Android TARGET device.
With the push notification sent to the device the changes will then be applied.
Disclaimer: Flashing a custom recovery is done at your own risk. Whilst these steps are correct at the time of writing FlexiSPY is not responsible for the custom recovery flashing process in any way and you do this at your own risk.
This article will show you how to install a custom recovery on to your Android phone. The custom recovery will replace the default recovery mode that comes with the Android phone as standard.
Please note that installing ClockworkMod requires rooting your device first. When you root an Android device, especially Samsung handsets, the root process installs ClockworkMod automatically as part of the process.
This guide is for those phones that are rooted but for which a custom recovery was not also installed as part of the rooting process such as HTC, Sony or Motorola devices.
What is recovery mode?
Recovery mode comes as standard on all Android phones and allows for recovery tasks to be performed such as installing zip files that are stored on the SD card to flash a custom ROM or to wipe the phone cache for example.
However the standard recovery mode on most Android phone is somewhat limited in what it can do which is why many Android users, especially when it comes to rooting an Android device, will flash a custom recovery instead and replace it.
If it has not been rooted then ClockworkMod cannot be installed.
How can I access recovery mode on my Android device?
To access recovery mode on any Android device simply perform the following steps:
Make sure the phone is turned off completely.
Hold down Volume up, Home and Power until the phone starts up and recovery mode should appear.
If your Android phone does not have a Home button then simply hold Volume up + Power instead.
The phone will boot up in to recovery mode and the standard options are limited.
The standard options are:
Reboot system now – Reboots the system out of recovery mode ready for normal use.
Apply update from ADB – If you have connected your Android phone to your PC and you have installed ADB then you can use ADB to ‘push’ files to your Android phone such as custom ROMS.
Apply update from external storage – For any zip file you want to install on the phone such as a rooting file to root the phone or a custom ROM.
Wipe data/factory reset – This does exactly as it says. ALL DATA WILL BE DELETED after choosing this option.
Wipe cache partition – This wipes data from the cache partition of the phone. Useful if the phone is stuck in boot loop or the manufacturer logo.
Apply update from cache – Apply any update file from cache.
How to install ClockworkMod for the first time on a rooted Android phone
Now that we know how to access recovery mode it is time to improve it by installing ClockworkMod.
To do this, on your Android phone, open up the Play Store and browse to ROM Manager.
Once you have downloaded and installed ROM Manager, open it.
Simply tap the Flash ClockworkMod Recovery option.
Choose your correct phone from the list – make sure that the model number matches.
Wait for the custom recovery to be downloaded and installed.
How to reboot in to the newly installed custom recovery
Now that you have successfully installed a custom recovery you can boot in to it either doing the steps listed above previously or, this time, you can now open up ROM Manager and tap the Reboot into Recovery option.
How to upgrade the current version of ClockworkMod custom recovery on a rooted Android phone
If you find that the currently installed version is older than the latest recovery version simply tap the Flash ClockworkMod option and it will install the latest version.
Sometimes it is great to install (flash) a custom ROM on to your Android device in order to tweak it for better performance or to utilise features of the handset that otherwise is off limits by the manufacturer or network provider.
But what makes people want to do this?
Popular custom ROMS have become a part of everyday life for Android users and an example of this would be Cyanogen who recently made installing their ROMs as simple as downloading an installer to your computer and connecting your phone.
Surely there are risks involved in modifying the phone software?
The days of being afraid to install custom ROMS for fear of damaging the phone are long gone as long as you take precautions. Taking precautions applies to many more things than just IT but it is always good to be safe and not sorry whatever the situation may be.
But there are times when you may need to install the ROM that the phone came with (known as the stock ROM).
Applying a firmware update that you are not happy with
You want to sell the phone
You want to send it in for repair and want to return everything to factory settings.
The thing to learn from this article is that there are times when factory reset is a necessity and that it is important to make sure the phone data is backed up also. The rest of this post discusses how to flash your Android device with a stock ROM, effectively restoring it to the ROM version that it came with when purchased.
Disclaimer: The information contained in this article is for research purposes only. In no way at all is FlexiSPY responsible for any misuse of your device through following the actions contained in this document. By reading forward of this notice you are agreeing that FlexiSPY is not responsible in any way for any actions that may result from following the instructions contained hereafter
Doing this involves three main tasks.
Backing up any phone data you wish to keep
Finding the correct stock ROM
Flashing the phone with the stock ROM successfully
We recommend backing up the phone data to a secure location (such as in the cloud) or just to your computer using the likes of the EFS Professional which is available for free and provides a comprehensive suite of backup options to make sure that all your important data will not be lost.
In order to use EFS professional you must have first rooted the Android phone and also installed BusyBox on to it from the Play Store.
To backup the EFS partition we will use a program called EFS Professional which is a PC program that allows us to backup the EFS partition to a computer to keep it safe.
On the Samsung Android phone go to the Play Store and download and install BusyBox as this is required for EFS Professional to work.
Simply grant root access when asked and then tap Install to start the installation process.
With BusyBox installed and the Samsung Android phone rooted simply plug the phone in to your PC using the USB cable it came with and run EFS Professional.
When you run EFS Professional it will perform checks on the phone itself first to make sure USB debugging is enabled (to enable USB debugging, on the phone itself go to Settings > More > About Device and continue to tap Build Number until the Developer Options option is shown. Once inside Settings > More > Developer Options make sure that USB debugging is checked.)
Simply tap OK on the phone when asked.
Back on the PC if you run EFS Professional it will make sure the phone is rooted and BusyBox is installed and it should look similar to this.
Tap the Backup tab.
Make sure EFS Professional looks like this. You can see that All Partitions is selected.
Click Backup to start.
Once the backup process is complete disconnect the phone from the PC and reconnect it again.
Using Windows Explorer browse to the SD card of the phone and you will find the backup folder titled EFSProBackup.
Simply copy this folder to your PC and keep it in a safe place.
Congratulations! You have successfully backed up the phone
So we have backed up the ROM now comes the fun part. This is the part that most people find difficult.
Finding the correct ROM to use is not as difficult as many would have you believe but it is not without risk.
If you pick the wrong ROM and flash (install) that to the phone then it can have dire consequences.
Luckily there are several websites available that help make finding the correct ROM as easy as possible. One such site that we recommend is SamMobile and their firmware section (http://www.sammobile.com/firmwares/).
Whilst on the above site click the Check Your Firmware link and fill in the information.
Once you have found the ROM for your particular phone version and country download it to your computer. You then need to download and install Odin on to your computer also as that is the software you are using to flash the phone.
If you have downloaded and extracted both Odin and the ROM to your computer you should have something that looks like this.
When you open Odin it will look like this.
As you can see from the message window no phone has been added yet. This is because, in order for Odin to see the phone you need to first of all put the phone in to download mode.
To do that you do the following.
Turn the phone off completely
Hold down the volume down key
With the volume down key held, press the main button
With the volume down key and main button held hold down the power button
This means you need to press all three keys at the same time in the order mentioned. You will know that you have done it properly when the following appears on the phone screen after it boots up.
Press the volume up button to continue and the phone screen will now look like this.
Connect the phone to your computer using a USB cable and now it will be seen by Odin.
If your phone is in download mode, connected to your compute but Odin does not see it then make sure you have installed Samsung Kies on to your computer first.
Without Samsung Kies installed (not open and running) the drivers for Windows to recognize the phone will not be installed and so Odin will not be able to see anything.
Backed up the phone data you wish to keep to your computer
Downloaded Odin and the ROM you are going to use for flashing
Installed the Samsung phone drivers to your computer by installing Kies
Put your phone in download mode
Connected the phone to your computer via the USB cable
Opened up Odin
If all has gone well it will look like the previous screenshot.
The final process of flashing the ROM to the phone is all that is left.
Click the AP button inside Odin.
You then browse to the firmware file. You will know if the file is correct because you will be able to see it inside the Windows Explorer menu and click on it.
It will also have the file extension MD5.
If you have downloaded the stock ROM but only see a zip file then it means you need to unzip the file first. Only after having done that will you get the correct MD5 file that Odin can then recognize and use.
Simply double-click the ROM MD5 file and it will be added to the AP section of Odin.
When you see Please wait… and the program says it is not responding (see screenshot below) do not be alarmed.
This is normal. Do not be alarmed, your phone is fine.
It just takes time for Odin to verify the firmware contents as it is such a large file.
During this time you must wait and it may look like the program is not responding but it actually is.
The ROM will be added to Odin once it has been checked.
Once you have done that click Start to begin.
Make sure the phone is not touched in any way or the USB cable disconnected from the computer or Odin closed whilst the flashing is in progress.
After a few minutes Odin will continue and the firmware file will be written to the phone.
You can tell this is in progress because, on the phone itself, a blue progress bar will be slowly going from left to right on the phone screen and in Odin you will also see a green progress bar.
When both Odin and that progress bar get to the end Odin will look like this.
Odin will also say Removed! because the phone restarts and so the USB connection is terminated and thus Odin sees the phone as having been removed. The phone will restart as normal and will boot in to the new OS for the first time – this will take some time.
Give the phone a few minutes and then, once it has booted up, it will now be running the stock ROM that you flashed to it.
You can then configure the phone as you did when you first bought it from the factory and it will be ready for use.
However if, after several minutes, the phone is still stuck on the Samsung logo or the phone may keep displaying the Samsung logo over and over and rebooting then read the steps below to resolve this.
But do not be alarmed, this is easily fixed.
To do this you need to boot the phone in to Recovery mode.
This is similar to how you got the phone to boot in to Download mode and involves holding down several buttons as the phone powers on.
Remove the battery and reinsert it
Hold down the volume up key
With the volume up key held, press the main button
With the volume up key and main button held hold down the power button
If you have done it properly the Samsung logo will appear as normal, wait two seconds and let go of all the keys.
If you have timed it properly the phone will boot in to Recovery mode and the phone screen will look like this.
You will also be presented with a menu with several options to choose from. To select an option use the volume up and down keys to move up and down and press the Power button to select the option.
What we need to do is delete the user cache and delete all factory data (it now makes sense why we backed up the phone first).
The recovery menu looks like this.
First, choose wipe data/factory reset and select it.
Scroll all the way down to Yes – delete all user data and select that.
The data will be wiped.
Second, choose wipe cache partition and select that.
The cache partition will be wiped.
If you have done it correctly, on the screen, in yellow text, it will say the following:
— Wiping data… Formatting /data… Formatting /cache… Data wipe complete.
If you are looking to root an HTC phone then the first thing you will need to do is actually unlock the bootloader. HTC, by default, lock down the bootloader to avoid tampering with system software that may permanently damage the phone if used incorrectly.
Rooting requires access to those very same files which is why unlocking the bootloader is required for rooting most HTC phones.
Unlocking the bootloader will void the warranty on the device once you have successfully done it.
Disclaimer: FlexiSPY is not responsible for any damages that may occur through following these steps. These steps are correct at the time of writing. Unlocking the bootloader is your responsibility and FlexiSPY is not responsible in any way. Please back up the phone completely before performing any of these steps.
Unlocking the bootloader may void the warranty on the device.
What is needed to unlock the HTC bootloader?
To unlock the bootloader on an HTC phone you will need the following:
The HTC phone whose bootloader you want to unlock in your hand
Access to a PC
Step 1 – Download the Android SDK
You will need to use ADB to unlock the bootloader and you get this through downloading the Android SDK.
You can read our article on how to set up ADB here.
Once you have set up and installed the Android SDK and you have confirmed that ADB works on your machine then it is time to proceed to the next step.
On the device itself, go to Settings > Power and make sure the Fast Boot option is not checked.
If you do not have an account you need to register first and then log in.
Once you have logged in please follow the steps.
Click Unlock Bootloader.
Then Click Get Started.
From the drop-down menu choose your HTC phone and then click Begin Unlock Bootloader.
If your device is not listed click the ‘All other supported models’ option instead.
Once you have chosen your phone and started the bootloader unlocking process the disclaimer will appear, Click Yes to proceed.
Agree to the legal terms (please read them carefully) and then click Proceed to Unlock Instructions.
Step 3 – Unlock the bootloader on the phone
The bootloader instructions will appear.
The steps and downloads may differ according to the HTC device whose bootloader you wish to unlock.
The first thing you must to is put the HTC phone in Fastboot mode.
Turn off the phone completely
Hold down the Volume down button and the power button together
Wait for the phone to power on
When it powers on select Fastboot from the menu (use the Volume up and Volume down keys to navigate and the Power button to select).
Now that the HTC phone is in Fastboot mode connect it to the PC.
Keep proceeding through the HCTDev wizard until you get to step 8.
On the PC, open up a command prompt in the folder where you installed the Android SDK and Fastboot window and type and press enter:
fastboot oem get_identifier_token
If done properly the unlock bootloader token ID will appear.
You only need to select the letters as the mosaic above illustrates.
Inside the HTC Developer unlock bootloader wizard paste the token ID where asked and then click Submit.
After a few moments you should get an email from HTC (the email is sent to the email address you used for registration on the HTC Dev website when you logged in to get started).
The email will contain an attachment, a file called unlock_code.bin
Download this file from the email and save it to your computer in the same folder that you installed ADB and the Android SDK.
Once you have done that (remember the HTC phone is still connected to the PC via USB running Fastboot mode) type the following and press Enter when done.
fastboot flash unlocktoken Unlock_code.bin
After pressing Enter, on the HTC device itself you should see the following screen.
Tap Yes (use the Volume Up and Down key to select and Power to confirm).
The HTC phone will reboot and it will boot up again. This process may take longer than usual so please be patient.
Once the phone has booted up the bootloader on the HTC device will have been unlocked so you are now ready perform advanced tasks on the phone such as root the device or install a custom ROM.
Disclaimer: While installing ADB is a safe process, please follow all the steps carefully. FlexiSPY is not responsible for any damage or data loss through following this article and all steps are correct at the time of writing. Create a Windows system restore point at any time if you are unsure. Performing these steps is your own responsibility.
If you are a casual Android user who just uses their phone for Facebook, Clash of Clans, calls and emails then you most likely won’t be interested in ADB or what it is. But for those who like to tinker with the plethora of Android customization options available to the platform ADB is an integral part of the experience.
But what is ADB and why should Android owners become familiar with it?
When you plug in your Android phone or table to your PC Windows will happily display the contents of the phone for you to work with. This can be internal storage or external storage from an Sdcard you have inserted. But surely you must have wondered, what else is on my phone and how can I get access to it?
ADB is the answer
ADB stands for ‘Android Device Bridge’ and is a set of tools for your PC that allows you to interface with your Android phone at the very lowest level in terms of system and processes. You essentially can access all areas of your Android phone and its filesystem instead of the areas deemed safe by the manufacturers that only Windows can see.
ADB allows you to perform advanced operations on your Android phone that you would otherwise normally not be able to.
But what are these ‘advanced operations’ you mention?
Usually ADB is commonly used for rooting. An Android phone software is powered by the Android OS which is based on Linux. On Linux there are certain levels of user responsibility, the highest being superuser which allows you to change anything.
Your Android phone is the same. By default the filesystem of the phone is locked down by the phone manufacturer but you can gain full and complete access to the device by gaining root (hence the term ‘rooting’). This lets you do anything you want on the phone and ADB helps make this happen.
So if you want to root an Android phone or perhaps install a custom ROM or basically just perform advanced tasks on your Android phone then you’ll need ADB so let’s install it.
What is needed to install ADB?
To install ADB you will need a PC. You will need to download and install the Android SDK which you can get from here.
Once you have downloaded the Android SDK save it to an easy to remember folder, for this article we are going to use C:\Android on the PC we are using to write this article.
Here we have downloaded the Android SDK to the desktop.
We will now extract the contents of the folder.
The above screenshots show what is inside the extracted SDK. We will now make a new directory on our C drive called Android and we will copy the three folders shown above.
If you are wondering, you simply navigate to SDK > platform-tools and ADB will be shown along with Fastboot which is also needed if you are rooting
Note: You will not see a platform-tools folder after you extract the SDK. You must install it first which we discuss now.
How do you configure ADB?
To configure ADB and make sure you have the right packages installed launch SDK Manager.
Because you are running it for the first time it will ask you which packages you wish to install, we must install Platform-tools because this is what contains ADB.
Just make sure Android SDK Platform-tools is checked, click Accept and then click Install.
Installing all the packages may take some time – please be patient.
When all packages are install the SDK Manager should look like this.
As you can see, Android SDK Tools and Android SDK Platform Tools are both installed.
Set the Windows ADB path variable
Based on which version of Windows you have (we are using Windows 8.1) the steps here may be a little different. Basically we need to tell Windows that the SDK actually lists and has its own unique path. That way, when ADB is invoked by a program (e.g. a rooting tool) it knows where to find the required file inside your SDK installation folder.
Because you are modifying system variables and paths you may want to create a Windows system restore point first.
You need to access Advanced System Settings.
To do this (on Windows 8.1), press the Windows key + S to bring up the search box and type Advanced System Settings and click the entry that appears.
On the menu that appears click Environment Variables.
The environmental variables window will appear and this is what we need to edit.
Under System Variables, scroll down to Path and click Edit.
Note: Do not delete the variable value field in any way.
Instead, append it. At the end, add the following line (include the ; at the start):
Note: Remember that we installed our Android SDK to C:\Android? Your SDK folder location may be different so please make sure you update the variable value field with the correct path.
Click OK when done.
Now that you have done that you need to install the Android USB drivers.
Installing USB drivers using the SDK Manager
For many Android phones, once you have connected them to your PC, they require their own special set of drivers for Windows to be able to recognize them and allow you to interface with it using ADB.
To do this, inside SDK Manager, scroll down to Extras.
Make sure Google USB Driver is selected and then install it.
The Google USB driver should work for most Android devices once they are plugged in to your PC but not all phone manufacturers require the use of ADB however you should always make sure that you have installed the latest USB drivers for the Android device you wish to root on to your PC.
Now that you have done that there is one more final thing to do.
Test that ADB works correctly
Now that we have set up ADB and installed the Android USB drivers it is time to test it all work.
Plug in any Android phone to your PC using its USB cable.
On the Android phone enable USB debugging. To do this go to Settings > About Phone (or About Device) and tap build number until the Developer Options menu is enabled.
Once inside the Developer Options menu make sure USB Debugging is checked.
On your PC open up a Windows command prompt by opening Run (Windows key + R) and then entering cmd and then press Enter.
In the command prompt window type adb devices and press Enter.
If everything is working properly the command window will display the device data as shown below.
Congratulations! You have now successfully setup and configured ADB for your Android phone and you can perform many additional tasks such as rooting, OS upgrading, OS downgrading and other custom options.
No doubt, if you are a regular reader of the FlexiSPY Blog you will see that we have a new section called ‘Android Rooting’. The purpose of this section is to provide helpful and up-to-date rooting guides for the most popular Android phones.
But many people are not entirely sure what rooting actually is. Furthermore they also think that rooting is a requirement to run FlexiSPY. This is not true. You can install FlexiSPY onto any Android device running Android OS 2.3 up to 4.4.2, and if it is not rooted then FlexiSPY can still be installed and it will run just fine – except you will not get access to specific root only features.
Basically, rooting an Android phone has many additional benefits besides being able to use the root only features of FlexiSPY.
What are the main reasons to root an Android device, besides FlexiSPY?
Free tethering – Tethering is where you can use the internet connection on your phone to access the internet on your PC or other device. Right now, for example on Boost Mobile, this costs $5 a month. On a rooted device, using Android Wi-Fi Tether it costs you nothing.
Increase battery life and speed – On a rooted device programs such as SetCPU allow you to overclock your phone (make it faster) for better performance or underclock it (make it slower) for better battery life.
Remove ‘bloatware’ – On any Android phone, especially ones tied to a carrier, there are always extra programs installed that you may not want to have (for example ‘Galaxy Gift’ on Samsung devices). Usually these cannot be removed but on a rooted phone, using Titanium Backup, running in root mode, they can be which makes your device not only run faster but also gives you additional storage space.
Remove adverts from applications – On the Google Play Store many applications are free and the reason behind this is because they serve you adverts. On a non-rooted phone you must either suffer the adverts or pay money to remove them. On a rooted phone there are programs (AdFree for example) that will remove the adverts for you for free.
Extensive customization – Unlike other device manufacturers (e.g. Apple, Windows Phone, and BlackBerry) who lock down the operating system meaning you cannot really customize, it a rooted Android phone gives you customization options to literally customize the entire phone to look and behave as uniquely as you wish it to. This includes installing custom ROMS, custom keyboards, and custom launchers – the works.
Install apps from the Play Store that are prohibited – If you have ever tried to download an application from the Play Store only to be told that you cannot because it is not available in your region or it just does not appear in the Play Store at all then a rooted device can solve this. You can sideload applications to bypass the Play Store restrictions.
What does rooting require?
To root an Android device you will need a PC and the Android device itself that you wish to root. Because every Android phone is different (make, model, manufacturer, OS version, firmware, kernel, etc..) there are a number of different ways you must root the same looking phone because of its configuration.
So, rooting a USA T-Mobile Samsung Galaxy S5 running Android OS 4.4.2 may not be the same as rooting a UK O2 Samsung Galaxy S5 running Android OS 4.4.2. Rooting requires a lot of research to make sure that you get the right rooting guide for the Android device that you wish to root.
Mac users who wish to root an Android device are out of luck. No rooting tools are available for Mac which means that Mac users must either run Windows on their Mac to perform rooting or they must get access to a PC to follow the rooting instructions.
Usually, when you want to root an Android device you need three pieces of information along with the device itself in your hand and access to a PC.
The model number
The manufacturer
The OS version
You can find that information on any Android device by going to Settings > About Device and the information will be listed.
So based on the details above, if we wanted to root this Samsung Galaxy S4 we would type ‘how to root Samsung Galaxy S4 GT-I9500 OS 4.2.2’ in to Google
FlexiSPY, in conjunction with Spy Phone Review, already provides tried and tested rooting guides for many popular Android devices and you can find links to them in the next section.
Do you have a rooting guide for my Android device?
You can find a complete list of all the rooting guides that we offer here.
If you wish to request a guide is written specifically for your Android device, for example, if your device is not listed please tell us in the comments and we will create one for you.
All rooting guides we offer are provided by Spy Phone Review and they are tested and correct at the time of publication.
How do I know an Android device has been rooted successfully?
Once you have rooted an Android device successfully there will always be a new icon visible called SuperSU. This is how you can tell if an Android phone has been rooted, by being able to see this icon in your main applications list.
If I root the phone won’t they find out because of the visible SuperSU icon?
Rooting will install a visible icon called SuperSU. While many people may be thinking that this icon will lead to discovery please understand that as part of the installation process on a rooted Android device FlexiSPY asks if you wish to hide the SuperSU icon or not.
Simply tap Yes and the SuperSU icon will be hidden completely. This means that there will be no traces of the software visible on the phone if you choose to also hide the FlexiSPY software icon as well.
What are the risks involved from rooting?
Rooting will void the warranty of the Android device in 99% of cases. That is why it is very important to find the correct rooting guide that you need for your specific Android device. As ever though it is recommended to backup the Android device first before performing rooting to make sure that you have a copy of it should anything go wrong.
On a rooted phone you also cannot upgrade the Android OS version any more. If you try to upgrade the OS version on a rooted phone then it will fail. The only way to upgrade the OS version is to perform a full unroot (explained later on) and then, once done, upgrade the OS and root the phone again while running on the newly updated OS version.
But rooting is a fairly simply process. Samsung based Android devices are the easiest to root overall because Samsung use Odin which is a simple to understand application allowing you to interface with any Samsung Android device once it is in Download mode.
In contrast to this, HTC requires that you unlock the bootloader of the Android device first before you can root the device. This is quite technical and it does void the warranty once it has been done.
Once a phone has been rooted you also cannot upgrade the OS version any longer.
If you have rooted an Android device and you wish to get the latest and greatest version of the Android OS that was just released specifically for your device then unfortunately, when you go to the Software Update option on the phone itself it will say that this operation cannot be performed.
On many Android phones you can unroot the phone to return the phone to its original non-rooted state. This is done by going in to the SuperSU application on the Android device > Settings > Full Unroot. Performing a full unroot means that you should be able to still maintain your warranty although, if rooting your particular Android device trips a counter that Android manufacturer technicians can access (as we explained with Samsung Knox) then it may not be enough but it should always be tried first.
On a rooted Android device, if you perform a factory reset, ALL DATA WILL BE DELETED on the device but the root will still remain. You can only remove rooting by performing a full unroot which is explained above.
What FlexiSPY features won’t I get if I do not wish to root the phone?
If you do not wish to root the Android device, that is fine, you can still install and run FlexiSPY on the device without issue – you just won’t get the following features.
Spycall– Listen to the Android device surroundings in real-time using your own phone – FlexiSPY EXTREME
Call intercept – Listen in to the Android device phone calls in real-time using your own phone – FlexiSPY EXTREME
IM capturing – Capture IM’s on the Android device from popular services such as Facebook, LINE, Whatsapp etc. – FlexiSPY Premium/FlexiSPY EXTREME
Email capturing – Capture emails on the Android device – FlexiSPY Premium/FlexiSPY EXTREME
Hide SuperSU – Hide the rooting icon on the Android device if you do not wish for it to be shown – FlexiSPY Premium/FlexiSPY EXTREME
Password grabber – Capture the application and email passwords for all accounts set up on the Android device as well as any passcode/lock pattern set
What is the difference between FlexiSPY running in FULL or LIMITED mode?
On a rooted Android device, FlexiSPY may run in FULL mode (root permission granted, all features working) or LIMITED mode (root permission may or may not be granted, limited functionality).
In LIMITED mode the following features will not work:
Spycall
Call intercept
For the reasons behind why FlexiSPY may run in LIMITED mode only on your Android device please read below.
Why does FlexiSPY only run in LIMITED mode in Android OS versions higher than 4.4.2?
The cause of LIMITED mode is dependent on the OS version of the TARGET device.
From Android OS version 4.3 onwards SELINUX was changed from PERMISSIVE to ENFORCED. What this meant was that even if the Android device is rooted, the changes to the OS software itself are prohibiting FlexiSPY from getting full access to the system software (the OS) on the phone for all features to work.
Unfortunately getting around SELINUX is not easy which is why even though FlexiSPY supports up to OS 4.4.2 this is only on devices whose manufacturer still sets SELINUX to PERMISSIVE and the only way you can get this information is to physically check the device itself.
There are three ways you can try to get around SELINUX being set to ENFORCED.
In the above screenshot you can see the About Device page of a Samsung Android device running OS 4.4.2 with SELINUX set to PERMISSIVE.
How can this be?
They installed a custom ROM to bypass the restriction as you can see by the device name.
But there is more.
On Samsung phones, running Android OS 4.3 or higher, Samsung added a new security program called Samsung Knox which locks down part of the phone OS software so that it can be used in a corporate environment (essentially allowing you to switch your phone from your personal phone to your company phone and back again as you require).
If this feature is enabled on a Samsung Android device then you may not be able to root it.
If you can root it then Knox keeps a record of it (called the ‘Knox counter’) and Samsung aftersales refer to this counter value if you ever take the phone in to be repaired. If the counter is not 0 then most likely your warranty will be void because Samsung will immediately know you tried to tamper with it by attempting to root the Android device.
They simply have to put the phone in to Download mode and look for the Knox Warranty Void value. If it is 0 then the warranty is valid. If it is 1 then Knox has been tripped and the warranty may no longer be valid.
The method to root a device with Samsung Knox enabled is complex. You essentially have to ‘cook your own ROM’ which means you are basically re-engineering the firmware OS file to not include Knox and you then flash that to the phone (meaning that the phone will be exactly the same, just without Knox) and you can then root it as normal. This is a process not many Android device owners will wish to do as it is complex, it will void the warranty and you will need to backup the device first as otherwise all data will be lost.
This method is also not available for all Android phones because it only applies to Samsung Android devices and not all Samsung devices can be upgraded to a newer Android OS version (e.g. OS 4.3.x and above) which Knox is compatible with which is why they are easier to root.
Ultimately, all of the issues here such as SELINUX and Samsung Knox, is beyond FlexiSPY’s control which is why we cannot guarantee all features will work if you are installing the software on to an Android device running that is not running an OS version from 2.3 to 4.4.2.
Samsung Knox is only available on Samsung Android devices. This is just one reason FlexiSPY may not run in FULL mode, for all other manufacturers (e.g. HTC, Motorola, Sony etc.) it would be the SELINUX setting that stops that from running in FULL mode on an OS version higher than 4.4.2.
Why can’t my Android device be rooted?
Not every Android device can be rooted.
It really depends on the configuration of the hardware and software inside the Android device for an Android phone to be able to be rooted or not and some are easier to root than others. Also, the more popular Android devices, from established manufacturers, are usually quicker to be rooted than a manufacturer that nobody has ever heard of.
Rooting takes time and patience. Many new Android phones get harder and harder to root. With Google now ready to near enough launch OS 5.x (Android Lollipop) it means a whole new challenge to make sure that this OS can be rooted. Unlike iOS for iPhone where all devices are pretty much the same configuration it means that it may be some time before rooting Android L based phones is possible and, when it is, it will only apply to the most modern handsets to start with as older devices may not be able to or eligible for running Android OS 5.0.
So while rooting is something that can be looked upon as being complex it really depends on the device itself. If you are interested in FlexiSPY and you want the root extra features then we recommended the following devices for best compatibility.
Samsung Galaxy S3 – GT-I9300 – OS 4.2.x or below (SELINUX should be PERMISSIVE)
Samsung Galaxy S4 – GT-I9500 – OS 4.2.x recommended (SELINUX should be PERMISSIVE)
Google Nexus 4 – OS 4.4.2 (SELINUX should be PERMISSIVE)
Google Nexus 7 – OS 4.4.2 (SELINUX should be PERMISSIVE)
Samsung Galaxy S5 – SMG900H – OS 4.4.2 (SELINUX should be PERMISSIVE)
FlexiSPY cannot test each and every Android handset and its configuration so the above handsets are known for best compatibility overall. Please also remember that the above devices include a very specific model number so please make sure that the device you want to install the software on to has the same model number.
For example, if you want to install the software on to a Samsung Galaxy S4 and its model number is GT-I9505 then it may not work correctly with the software at this time and it highlights just how fragmented the Android OS system is compared to Apple and iOS which is more unified (but this comes at a price of less control and customization).
If you want to install the software on to an Android device running an older OS version such as OS 4.x – 4.2.x) then you have a higher chance of complete compatibility plus the device will be much easier to root as well.
If you are not wanting the root extra benefits then any Android phone running OS 2.3.x – 4.4.2 will run FlexiSPY without any problems. Please remember that on an unrooted Android device, whileFlexiSPY will display a visible icon, the ability to hide the application from the Application Manager list is something that can only be done if you have rooted the phone before installing the software.
Here on the FlexiSPY blog we love to customise our devices and root them and jailbreak them but we understand that this does not come without risk. Therefore, in this article we will explain how you can quickly and safely backup the entire contents of your Android phone.
The benefits of doing this are numerous such as if you decided to downgrade the OS or install a custom ROM for example – backing up the Android phone can often be a lifesaver.
Disclaimer: FlexiSPY is not responsible for any loss of data or damages incurred from following the directions given. The directions were accurate at the time of writing. Please make sure you follow the rooting guide correctly if you need to root your phone first and make sure your phone has enough storage space to perform a backup before proceeding.
What is needed to backup the Android phone?
To backup the Android phone you will need the Android phone in your hand and, depending on the method of backup (discussed later) a PC may also be required.
What is the easiest way to backup an Android phone?
The easiest way is on the device itself and even though you think that means you do not need a PC it actually does. This is because you need to have rooted the Android phone first to install a custom recovery on it and it is through booting in to this custom recovery that you can then perform a full backup of the phone.
Usually this is to the SD card that you have inserted but what if you do not have an SD card? You can save the backup to the internal memory of the Android phone but if the phone is restored or reset you risk losing the backup so you still need a PC to transfer the backup file (which can often be large such as several gigabytes) to a PC for safekeeping.
To backup the Android phone itself, as mentioned, you will still need a PC to transfer the backup file from the Android phone to the PC for safekeeping once the backup is complete. However you also need to make sure that the Android phone you want to backup, on the device itself has been rooted as well.
Why is this?
Because rooting a phone is what installs a custom recovery. It is the custom recovery that has the feature that allows for the Android phone to be backed up directly to the device to start with.
You can find out more on what rooting is and why it can be a good thing by reading this article.
Essentially backing up the phone directly to the device consists of three steps.
Root the phone (this installs the custom recovery mode)
Backup the phone using the device itself and custom recovery
Transfer the backup file to a PC for safekeeping
For the sake of this article we are going to assume that you have already rooted your Android device. If you haven’t and you want to know how to root some of the more popular Android handsets then be sure to check out rooting help here.
So how do you backup the phone to the device itself?
First of all you must boot the phone in to recovery mode.
To do this you do the following:
Turn the phone off completely.
Hold down the Volume Up, Home and Power buttons together.
Wait until the phone boots up.
Providing you have done this correctly the phone will boot up and it will look like below. If your phone does not boot in to custom recovery mode then it most likely has not been rooted so please remember to root it first otherwise this article cannot be followed.
Use the volume up and volume down keys to select and the power button to confirm.
From the main menu choose backup and restore.
On the menu that appears choose the backup option.
The backup process will start – please be patient, this may take some time.
Once it is complete you need to transfer the backup file to a PC for safekeeping.
This is done by doing the following:
1. Reboot the phone after using the recovery mode to backup the phone. – The Android phone will be recognised by Windows.
Double click Phone. The contents of the phone internal memory will be displayed.
Double-click the clockworkmod folder.
Inside the clockwork mod folder you’ll find that there are no backup files of any kind.
So where are they?
This is why you need root access.
The clockworkmod backups are actually located on the Android phone in /mnt/shell/emulated/clockworkmod/backup.
We will show you how to find the backup files using ES File Explorer which is freely available on the Play Store.
Simply search for ES File Explorer on the Play Store and install it.
Once it’s installed, run the program
You now need to get root permissions from the application to find the hidden location where the backups are stored. This option is found in the Tools menu.
In the Tools menu set Root Explorer to ON and grant root permission when asked.
Once root permission has been granted browse to the original file location – /mnt/shell/emulated/clockworkmod/backup
This time the folder will not be empty and the backups will be listed.
If you open up any backup folder you can verify the contents.
But now that we have found the backups how do we get that folder on to our PC for safekeeping?
By copying the backup folder to a folder on the Android phone that the PC can access such as the Downloads folder.
To copy the folder press and tap the folder icon and then tap Copy that appears at the bottom of the screen.
You then need to browse to the main downloads folder.
When you have reached the Download folder tap the Paste button to start copying.
Wait for the copying process to be completed – this may take some time.
Now that you have copied the backup file to a folder that your PC can access on the Android phone we can now copy it to our PC for safekeeping.
To do this make sure that you have plugged your Android phone in to your computer. Once it is plugged in simply browse the phone until you reach the Download folder.
Inside there will be the backup file we copied previously
As you can see, backup folders are there. Simply copy these folders to a convenient place on your PC for safekeeping and everything is complete.
You have now successfully backed up your phone entirely. We will discuss how to restore these backups in a separate article.
This guide will show you how to downgrade the Samsung Galaxy Note 3 from OS 4.4 to OS 4.3.
Disclaimer: Please understand that this guide is provided ‘as is’. FlexiSPY is not responsible for it or its contents and you perform the downgrade procedure entirely by yourself and at your own risk. FlexiSPY is not responsible in any way for any damages that may incur through following this guide and by reading past this notice you agree to the notice given above:
For this guide we are using a Note 3 whose model number is SM-N900
Please make sure your Samsung Galaxy Note 3 model number matches the one used above as not all versions of the Note 3 can be downgraded.
What is needed to downgrade?
In order to downgrade the Note 3 you will need the following:
The Note 3 that you wish to downgrade in your hand
A PC.
Why downgrade the OS of the Note 3?
If you have rooted the Note 3 already what happens is that you no longer receive official system updates from Samsung so what happens if you want to change the OS version to an older one for performance reasons?
All you have to do is backup the Note 3, download the ROM that you want to downgrade to and then flash the ROM to the phone using your PC and Odin.
For one thing downgrading the Android OS to an older version can allow Galaxy Note 3s running OS 4.4.x to run FlexiSPY in FULL mode which means that, once the device is rooted, all FlexiSPY features will function provided you have rooted the phone before installing FlexiSPY.
Running an older OS version can also add features that were removed in newer version or improve stability and reliability, especially if the new OS has just been released and so can be subject to bugs and issues.
Backup the phone first
Before you do anything make sure that the phone has been backed up first. We have discussed how to do that here (the steps are the same even though the phones are different) and the software used is EFS Professional (to backup all partitions – especially EFS as this is the most important).
Once the phone has been completely backed up to your PC you now need to download the Samsung Galaxy Note 3 ROM for your country that is running OS 4.3.x.
Download the 4.3.x ROM you need for the Note 3
Now that you have backed up the phone completely (especially the EFS partition – we cannot stress that enough!) it is time to get the ROM you need.
If you want to downgrade a Samsung Galaxy Note 3 running OS 4.4.x to 4.3.x or below in order to run FlexiSPY here is what you need to do.
1. Browse to http://www.samfirmware.com/
2. Click the Firmware tab at the top.
3. Click the Check your firmware option. 4. Search for the Samsung Galaxy Note 3 using the dropdown menu. It should look something like this..
5. Click Check firmware when done.
Note – In this example using the Note 3 we chose Thailand as the country but you would choose your own country (e.g. USA or UK) which means that the model number (SM-N900) may also be different.
6. Click Download – click the Download button again when ready to proceed (you may need to register a free account on Sammobile before you can download ROMS).
7. Click the Download button once more to start the download process and save the ROM file to your PC.
The filesize is 1.3GB so the download may take some time. Once downloaded save it somewhere that is easy to access such as the desktop.
Download the unlocked Note 3 bootloader
When Samsung released the Note 3, on many variants of the model, they have now locked the bootloader. This means that you cannot downgrade at all as you cannot unlock the bootloader on all versions of the Note 3 which is why this guide is for the Samsung Galaxy Note 3 model SM-N900 only.
You can download the unlocked bootloader from here.
Save it to your PC in an easy to find location such as the desktop.
Get the Samsung Galaxy Note 3 Ready
In order to flash the ROM to your Samsung Galaxy Note 3 you must perform a few tasks on your PC first.
1. Download Samsung Kies for your PC so that the phone is recognised by Odin when you connect it using the USB cable.
2. Download Odin.
3. Put the Samsung Galaxy Note 3 in recovery mode
a. Turn off the Samsung Galaxy Note 3 completely
b. Hold down the volume down, home and power buttons together.
c. Wait for the phone to turn on and it should boot in to download mode
If you have done it correctly it will look like below and you then press the Volume up button to continue and it will be in download mode.
4. Connect the Samsung Galaxy Note 3 to your PC using the USB cable.
5. Open Odin and it will look like this if everything is done correctly (ADDED means that the phone has been successfully recognized by Odin.)
You now have to add the bootloader file you downloaded in to Odin.
Click the BL button
Browse to the bootloader zip file and choose it.
Once added and Odin confirms it is okay simply click Start to start the flashing process – this can take some time and please do not remove the phone from your computer in any way.
Once done successfully Odin will look like this.
The Samsung Galaxy Note 3 will reboot and you can disconnect it from your PC.
Booting up for the first time using the OS may take some time so please be patient.
Once it boots up disconnect it from your PC. You now need to boot it in to recovery.
Turn off the Samsung Galaxy Note 3 completely
Hold down the volume up, home and power buttons together.
Wait for the phone to turn on and it should boot in to recovery mode.
Once in the recovery menu choose to wipe data/factory reset and also wipe the cache partition – THIS WILL DELETE ALL DATA ON THE DEVICE.
After that reboot the phone back in to normal mode and then turn it off. You now need to boot in to download mode.
Turn off the Samsung Galaxy Note 3 completely
Hold down the volume down, home and power buttons together.
Wait for the phone to turn on and it should boot in to download mode.
Connect the phone to your PC and it should be recognised by Odin.
You now have to add the ROM file in to Odin.
Click the AP button
Browse to the ROM file and choose it.
Once added and Odin confirms it is okay simply click Start to start the flashing process – this can take some time and please do not remove the phone from your computer in any way.
Once done successfully Odin will look like this.
How To Fix Any Issues After Downgrading
If the Samsung Galaxy Note 3, after you flash the ROM, is stuck on the Samsung logo or constantly reboots then do the following.
Turn off the phone completely.
Hold down the Volume up, home and power buttons together.
Wait for the phone to display the Samsung logo and then let go
It will now be in recovery mode which looks similar to this.
Using the Volume up and down keys scroll to Wipe data/factory reset and press the Power button to confirm
Scroll down to Yes and press the Power button on that to confirm, the Samsung Galaxy Note 3 will then perform a factory reset.
When it is back on the screen shown above select Reboot and the Samsung Galaxy Note 3 will restart and boot up – this may take some time when booting for the first time so please be patient
If, after the phone has booted up you find that you no longer have a cell signal and that your IMEI number is incorrect – e.g. 004999010640000/01 (Settings > More > About Device > Status > IMEI) then you need to download the modem file from sites such as XDA forums, save it to your PC and extract it.
Put the Samsung Galaxy Note 3 in to download mode again and connect it to your PC and run Odin (see above for more information).
Click the CP button and then point to the Modem binary file that you downloaded and extracted.
Click Start to flash the modem and wait.
DO NOT DISCONNECT THE SAMSUNG GALAXY NOTE 3 FROM THE PC OR TURN IT OFF IN ANY WAY
Once it has been done wait for the Samsung Galaxy Note 3 to reboot and you should now have your working IMEI back and successfully downgraded the OS version.
As ever this guide is provided as is so if you have any issues or questions about this simply let us know in the comments and we will do our best to assist you.
Recently, on our Samsung S4 downgrade article, we were asked whether or not the steps in the article would work on a Note 3. Our answer that was, in theory, the process of backing up the EFS partition of the phone, downloading the older ROM and then flashing it using Odin should work because both phones are manufactured by Samsung and so they process is near enough the same.
But before you downgrade the OS version there are a few things you need to consider.
1. Downgrading the OS will mean that ALL data is wiped from the phone.
2. Downgrading the OS to an older version means you will lose new OS features or updates.
3. If you downgrade and then root the phone you can no longer upgrade to new OS versions because software update is disabled due to the device being rooted.
Why downgrade the Android OS?
For one thing downgrading the Android OS to an older version can allow Android phones running OS 4.4.x to run FlexiSPY in FULL mode which means that, once the device is rooted, all FlexiSPY features will function provided you have rooted the phone before installing FlexiSPY.
Running an older OS version can also add features that were removed in newer version or improve stability and reliability, especially if the new OS has just been released and so can be subject to bugs and issues.
What Does an Android OS Consist Of?
If you want to take a closer look at what an Android OS consists of then backing up the Android phone using software such as EFS Professional can be used to tell you more about the software that runs the device.
The main Android OS partitions are as follows:
BOOT – This contains information allowing the phone to boot up. Without this the phone will not start.
SYSTEM – This contains the OS itself. This can be wiped and you can still use the phone in download mode to flash as new ROM because the information from the BOOT partition is still present.
RECOVERY – This contains the recovery information. This allows you to perform alternate boot and maintenance options.
USERDATA (or DATA) – This contains your user information such as contacts, SMS messages, settings and applications installed. Wiping this partition alone is the same as a factory reset.
CACHE – This is where the Android OS stores frequently accessed applications components or data. Wiping this is fine, it automatically gets rebuilt once the device reboots.
MISC – This is important as it controls miscellaneous settings including but not limited to the network carrier configuration and settings and USB information. Wiping this will result in parts of the phone no longer working.
SDCARD – This is the SD card. Wiping this deletes all data on the SD card. On the Galaxy S devices this refers to the internal SD Card partition and not the actual SD card you insert which uses another partition.
We can examine more about an Android OS using backup tools such as EFS Professional.
In the above screenshot we have four partitions selected.
EFS– Contains the CSC information used in Odin (see below).
BOOT– Contains the bootloader information used in Odin (see below).
RADIO– Also contains important carrier information and settings.
SYSTEM– The actual OS itself that is currently installed.
How are Samsung OS ROMS flashed to the device?
Every Samsung phone has an operating system. This software is known as a ROM. When you downgrade the ROM the ROM you download can be one of two formats.
1st Possible Format – All in one – An all in one file that contains all the ROM partition information and is the easiest to flash.
2nd Possible Format – Separate parts (see below) with a file for each part and a PIT file to put it all together
As you can see above there is quite a difference between an OS ROM that is all in one and one that is separated but for either case you will need Odin, a PC based program, to flash the ROM and downgrade it.
The main buttons that you need to work with on Odin are as follows.
PIT – This is the partition information table. For some ROMS, even if you flash individual parts it will not work without the corresponding PIT file that tells the phone how everything is separated and laid out.
BL – Flash files to the device that only pertain to the bootloader (what happens when the phone boots up).
AP – Flash the main ROM file. This is the option most people will need to focus on.
CSC – This is the file that contains all the carrier and network information such as access point names and settings and other carrier/network related information.
An Android ROM (often several gigabytes in size) is partitioned (split) in to different sections with each section responsible for different features and functions which have been explained above.
So now that you know what an Android ROM is and what it consists of what happens next?
Always backup the Samsung Android device first
Before you do anything always back up the Samsung Android device first, just in case.
This can be done in a variety of ways but we prefer using EFS Professional.
To use this software you must make sure of three things:
1. The Samsung Android phone you want to backup has been rooted by you.
2. You have installed BusyBox on the Samsung Android phone from the Play Store.
3. You have installed the Android SDK on your PC correctly and ADB works.
Once you have made sure that the Samsung Android device meets the requirements download and run EFS Professional. We explain how to backup the phone and do all this here.
With the phone backed up to your PC using EFS Professional the backup file will look like this.
All successful backups are stored in the EFSProBackup folder and all the backups have the model name, as well as date and time of when the backup occurred.
At the time of writing this article the date is 9th September 2014, so, just to prove this works. We will backup the phone we are using for this article (Samsung Galaxy SIII – GT-I9300) using EFS Professional.
As you can see we have selected just the EFS partition this time to backup and this will be explained why in the next section.
We click the Backup button and the process starts – this can take some time and depending on how many applications you have installed and such the backup filesize may be large so make sure you have enough space on the phone itself or inserted SD card before starting the backup.
As you can see from the screenshot below the backup was successful.
And the saved backup folder on the PC is shown here which contains the EFS partition information.
As you can see the backup archive data matches the time of writing (9th September 2014) and the device name is that of the Samsung Galaxy S3 that we are using (GT-I9300).
When it comes to backing up a Samsung Android phone before downgrading the OS the only partition you really need to backup is EFS as we have done above (we still recommend you back up everything just to be sure) and we will explain why in the next section.
Find the ROM that is correct for your Samsung Android device
We touched upon this in our Samsung S4 downgrade article and showed the site to use to get the OS ROMs you are looking for.
So, for example, if you want to downgrade a Samsung Galaxy Note 3 running OS 4.4.x to 4.3.x or below in order to run FlexiSPY here is what you need to do.
4. Search for the Samsung Galaxy Note 3 using the dropdown menu
So, it should look something like this.
Click Check firmware when done.
Note – In this example using the Note 3 we chose Thailand as the country but you would choose your own country (e.g. USA or UK) which means that the model number (SM-N900) may also be different.
You would obviously choose the Samsung Android phone model and country that applies to you which matches the Samsung Android phone whose OS you wish to downgrade.
5. The latest firmware will appear.
Click Download
6. Click the Download button again when ready to proceed (you may need to register a free account on Sammobile before you can download ROMS).
7. Click the Download button once more to start the download process and save the ROM file to your PC.
As you can see, the filesize is 1.3GB so the download may take some time. Once downloaded save it somewhere that is easy to access such as the desktop.
Get the Samsung Android phone ready
In order to flash the ROM to your Samsung Android phone you must perform a few tasks on your PC first.
1. Download Samsung Kies for your PC so that the phone is recognized by Odin when you connect it using the USB cable.
3. Put the Samsung Android phone in recovery mode
— a. Turn off the Samsung Android phone completely
— b. Hold the volume down, home and power button together
— c. Wait for the phone to turn on and it should boot into download mode.
If you have done it correctly it will look like below and you then press the Volume up button to continue and it will be in download mode (this is using an S4 as an example but all Samsung Android phones will look the same in download mode).
4. Connect the Samsung Android phone to your PC using the USB cable.
5. Open Odin and it will look like this if everything is done correctly (ADDED means that the phone has been successfully recognized by Odin.)
You now have two ways to add the ROM file into Odin.
1. If the ROM file is one file do the following:
a. Click the AP button
b. Browse to the ROM zip file and choose it.
2. If the ROM file is in more than one part do the following:
— a. Click PIT and add the PIT file.
— b. Click BL and choose the BOOT file.
— c. Click CP and choose the CODE file.
— d. Click CSC and choose the MODEM file.
Either way, once you have selected the correct way to flash the phone simply click Start to start the flashing process – this can take some time and please do not remove the phone from your computer in any way.
Once done successfully Odin will look like this.
The Samsung Android phone will reboot and you can disconnect it from your PC.
Booting up for the first time using the OS may take some time so please be patient. Once it boots up you have successfully downgraded your Samsung Android phone.
How to fix any issues after downgrading the OS
If the Samsung Android phone, after you flash the ROM, is stuck on the Samsung logo then do the following
Turn off the phone completely.
Hold down the Volume up, home and power buttons together.
Wait for the phone to display the Samsung logo and then let go.
It will no be in recovery mode which looks similar to this.
Using the Volume up and down keys scroll to wipe data/factory reset and press the Power button to confirm.
Scroll down to Yes and press the Power button on that to confirm.
The Samsung Android phone will then perform a factory reset.
When it is back on the screen shown above select Reboot and the Samsung Android Phone will restart and boot up – this may take some time when booting for the first time so please be patient.
If, after the phone has booted up you find that you no longer have a cell signal and that your IMEI number is incorrect – 004999010640000/01 (Settings > More > About Device > Status > IMEI) then you need to download the modem file from sites such as XDA forums, save it to your PC and extract it.
Put the Samsung Android phone in to download mode again and connect it to your PC and run Odin (see above for more information).
It will look like This Picture once connected as we have seen before.
Click the CP button and then point to the Modem binary file shown in the last screenshot
Odin should now look like This Picture . You can see the Samsung Android phone has been added and the modem file is selected.
Click Start to flash the modem and wait.
DO NOT DISCONNECT THE SAMSUNG ANDROID PHONE FROM THE PC OR TURN IT OFF IN ANY WAY
Once it has been done wait for the Samsung Android phone to reboot and you should now have your working IMEI back and successfully downgraded the OS version.
As ever this guide is provided as is so if you have any issues or questions about this simply let us know in the comments and we will do our best to assist you.
This article will show you how how to downgrade from the Android L developer preview to Android OS 4.4.4 on a Nexus 5.
Disclaimer: FlexiSPY is not responsible for the steps inside this article. However all care has been taken to make sure that the information contained here is as accurate as possible. Please read and follow the instructions carefully and remember that downgrading the OS is entirely your own responsibility and FlexiSPY is not responsible for it in any way.
Why downgrade?
We’ve already published articles on how to install the Android L developer preview on a Nexus 5 here.However Android L is still under development which means that certain features, functions or software may not work entirely as expected. It is also not recommended to run an OS that is currently in development on your main phone for reasons mentioned above.
This means that ultimately you may wish to downgrade back to the latest version of the Android OS which is stable and works. In this case, for the Nexus 5, this is Android OS 4.4.4 and the process for downgrading from the Android L developer preview back to Android OS 4.4.4 on a Nexus 5 is actually not as hard as you may think.
What’s needed to downgrade?
In order to downgrade the Nexus 5 from Android L you need the following:
The Nexus 5 running Android L
A PC
The Nexus 5 OS 4.4.4 recovery image
On the PC that you will be using to downgrade you must have first of all set up the Android environment correctly such as installing the Android SDK, setting the Windows path for Fastboot, making sure the bootloader of the Nexus 5 is unlocked and installing the correct Google USB driver so that the Nexus 5 is recognised completely by your PC when you plug it in.
This article is written assuming that you have done this already. If you have not then you can learn more about setting up the Android environment needed by reading the first article in this series detailing how to upgrade to the Android L developer preview which you can find here.
Step 1 – Download the Android OS 4.4.4 image
The first you need to do is download the Android OS 4.4.4 image from here. Google provides these images for you so that you can easily downgrade the Nexus 5 should anything go wrong or reinstall the current OS version if the Nexus 5 is running OS 4.4.4.
Please make sure that you download the correct version for the Nexus 5 model you are working with.
Once you have downloaded the image file save it in a convenient location such as your desktop.
Once you have saved the image file to your computer you must extract it to gain access to the files that are required to start the flashing process.
Once you have extracted the files inside the downloaded image file it should look like the picture below.
Step 2 – Flash the Android OS 4.4.4 image to the Nexus 5
We already mentioned that we assume you have already set up the Android development environment on your PC but again, if you need a refresher, read the article here.
To flash the Android image you first need to put the Nexus 5 in Fastboot mode.
This is done by doing the following:
Make sure the Nexus 5 is turned off completely.
Connect the Nexus 5 to your PC using the USB cable
Hold down the volume down button and the power button together to turn it on.
If done correctly the Nexus 5 will turn on in Fastboot mode and it will look like the picture below.
With the Nexus 5 in Fastboot mode and connected to your PC browse, on your PC, to the folder where you saved the Nexus 5 Android OS 4.4.4 ROM.
Simply double-click flash-all.bat and wait for the Nexus 5 to complete the steps and, once done properly, the Nexus 5 will restart and it will be running OS 4.4.4 again.
This article will show you how to install the Android L preview on to a Nexus 5.
Bear in mind that the latest version of Android, Android L, is still under development.
The version we are installing in this article is subject to change and you perform the steps in this guide at your own risk.
While everything has been done to make sure the steps are accurate, FlexiSPY is not responsible for the contents of this guide or any damage that may be incurred from following this guide.
What is Android L?
Android L is the newest version of the popular Android OS. It will be Android OS version 5.0.
As is the tradition with Android OS versions being named after desserts (Android OS 4.x (K) was named Kitkat for example with Jelly Bean and Ice Cream preceding them) many people believe that the ‘L’ will stand for lollipop but this is not confirmed (nor denied) by Google at this time so we just have to wait and see what Google decide to do.
With the new Android OS not being scheduled for release until at least the end of 2014 it comes as no surprise that only a few select phones are eligible to be running this version currently.
Luckily, here at FlexiSPY, we like to keep on top of all things tech which is why we have just installed the Android L developer preview on our Nexus 5 and we are going to show you how you can do the same in just a few quick and simple steps.
What you need to install Android L
In order to install the Android L developer preview on to a Nexus 5 you will need the following:
A Nexus 5 phone
The Android L developer preview image
A PC
Step 1 – Backup the Nexus 5
Because this is still development software we highly recommend that you back up the phone first completely before proceeding.
To do that you, first of all, install the Nexus root toolkit which you can find here.
Once you have downloaded the Nexus toolkit connect the Nexus 5 to your PC using the USB cable it came with. After that, you need to put the Nexus 5 in USB debugging mode before it will be seen while connected to the PC using the Nexus root toolkit program.
To enable USB debugging on the Nexus 5 simply do the following:
Tap Apps
Tap Settings
Tap About Phone
Scroll down to Build Number and keep tapping that until you read you are now a developer. The Developer options menu has now been unlocked.
Tap the new Developer Options Menu.
Make sure Stay Awake is checked
Make sure USB debugging is checked.
You also need to make sure you have installed the Nexus 5 USB driver otherwise even with USB debugging enabled the PC will still not recognize the phone. To learn how to do that click here.
If, after enabling USB debugging and installing the USB driver and the Nexus 5 is still not recognized then try a different USB port on your computer because sometimes that can make the difference.
Also make sure that, with the Nexus 5 connected to your PC, no on-screen notification on the Nexus 5 is visible asking you to accept USB debugging on the PC (you have to accept otherwise the PC will not find the phone).
With all this done the Nexus 5 should now be recognized when you run the Nexus toolkit and it will look similar to this.
As you can see the Nexus root toolkit has identified the Nexus 5 and Android OS version so the next thing that we need to do is start the backup.
The root toolkit takes care of the entire backup process, so click the Backup button to start.
We want to create a complete backup of the Nexus 5 before we install anything on to it so simply click Create Android Backup File.
There is quite a lot of text to read but essentially you just need to tap OK and then you can proceed to the next step.
The next step will ask you where you wish to save the backup file to on your computer. Simply pick a convenient location and then the next window will explain more about the backup process and what will happen.
While the backup is in progress make sure the Nexus 5 is not interrupted.
Once the backup is complete the Nexus root toolkit will inform you.
Downloading the Android L developer preview
Google makes downloading the developer preview as simple as possible however there are some prerequisites first. You must make sure you have installed the Android SDK on your PC first.
You must also make sure that, within Windows, you have set the path variable for Fastboot to match the location where you save the downloaded Android developer preview too.
For more information how to install the Android SDK please see the details here.
When you have successfully installed the Android SDK to a folder of your choice on your PC, it should look like this (we have installed the Android SDK to C:\Android for easy reference).
Here you can see the SDK (the SDK folder) has been installed and we have put all of this in a folder located at C:\Android for easy access as mentioned.
You can download the Google L developer preview from the link here.
Make sure you download the correct one for the Nexus 5 and then save the downloaded folder in the same folder as the SDK as shown below. We named our folder android for easy reference also.
Inside the android folder, you must extract the contents of the developer preview so it looks like this:
Next, connect the Nexus 5 to the PC using the USB cable.
Make sure it is powered off and the hold down the volume down button and the power button to turn it on and it will boot up in Fastboot mode which looks like this.
The final thing that needs to be done is within Windows which is to set the Path of Fastboot so that it points to the Android SDK Fastboot files which we have located in C:\Android\SDK\Platform-Tools on our PC (for you it will be different).
To set this do the following:
On the Windows desktop (in this case Windows 8) open up file explorer. Right click your computer and then click Properties.
With the system properties menu open click Advanced System Settings and the System Properties window will appear.
With the System Properties window, open click Environment Variables and the menu that appears will look similar to what is shown below.
In the Environment Variables window select Path and then click Edit.
Add a semicolon, as shown in the example, and then type the full path to the Android SDK (in this example we use C:\Android as mentioned).
Now that we have everything set we need to make sure the Nexus 5 is ready.
The Nexus 5 should be connected to your PC.
The Nexus 5 should be running in Fastboot mode.
You should have installed the Android SDK on to your PC in an easy to access location.
You should download the Android L developer preview image and saved it in a folder where you saved the Android SDK for easy reference.
Now that you have done all these four things you simply run the flash-all.bat file inside the Android L developer preview folder.
If all you see inside your Android L developer preview folder is a zip file you must extract it first to view all the files.
The Android L preview image will be flashed to the Nexus 5. This may take some time.
DO NOT DISCONNECT THE NEXUS 5 FROM YOUR PC OR TURN IT OFF OR DO ANYTHING THAT WILL INTERRUPT THE FLASHING PROCESS IN Anyway.
Once you have flashed the Android L developer preview the Nexus 5 will boot up for the first time. This may take some time also so please be patient. Once it boots up Android L will be fully ready for use.
This article will show you how how to successfully downgrade a Samsung Galaxy S4 from OS 4.4.2 to 4.3
Disclaimer: Please understand that this guide is provided ‘as is’. FlexiSPY is not responsible for it or its contents and you perform the downgrade procedure entirely by yourself and at your own risk. FlexiSPY is not responsible in any way for any damages that may incur through following this guide and by reading past this notice you agree to the notice given above:
Our Samsung Galaxy S4 is model number GT-I9500.
These steps may not work on the GT-I9505 version of the Samsung Galaxy S4 and you perform them at your own risk.
Why Downgrade?
FlexiSPY is not yet fully compatible with OS 4.4.2 and so if your target device is running OS version 4.4.2 and you want FlexiSPY Extreme features such as spy call and call interception to function then you need to downgrade.
Not only that but downgrading may actually cause a performance increase due to the S4, which is getting on in years, not being able to fully run the latest Android OS version as well as something such as the Samsung Galaxy S5
Please note also that in certain geographical regions the S4 may not yet be able to run OS 4.4.2 and that depends entirely on the network providers and Samsung themselves.
What is needed to downgrade?
To downgrade the Samsung Galaxy S4 you will need the following
The Samsung Galaxy S4 you wish to downgrade which is running OS 4.4.2
A PC.
The USB cable that cmae with the Samsung Galaxy S4
The OS 4.2.2 firmware file for your S4 according to your country (see later)
A backup of the EFS partition of the S$ (see later)
The modem binary file of the S4 (see later)
The rooting software for PC called Odin (see later)
Now that we have all the necessary equipment it’s time to get started!
Step 1– Check the Android OS version is 4.4.2 on the Samsung Galaxy S4
On the phone itself go to Apps > Settings > More > About Device and the OS version will be listed. You can see our S4 is running Android version 4.4.2 in the screenshot below.
Step 2– Backup the EFS partition of the S4
Basically, without getting too technical (we will discuss more about the EFS partition later) it is always safe to make sure you backup the phone first before you downgrade.The EFS partition is responsible for allowing the phone to have carrier functionality and make calls such as getting the network identified and IMEI number
Without this data the phone cannot function as a phone
To backup the EFS partition we will use a program called EFS Professional which is a PC program that allows us to backup the EFS partition to a computer to keep it safe
On the Samsung Galaxy S4 go to the Play Store and download and install BusyBox as this is required for EFS Professional to work. You must have rooted the Samsung Galaxy first to install BusyBox and you can head on over to Spy Phone Review here for assistance with that.
Simply grant root access when asked and then tap Install to start the installation process.
With BusyBox installed and the Samsung Galaxy S4 rooted simply plug the S4 in to your PC using the USB cable it came with and run EFS Professional.
When you run EFS Professional it will perform checks on the S4 itself first to make sure USB debugging is enabled (to enable USB debugging, on the S4 itself go to Settings > More > About Device and continue to tap Build Number until the Developer Options option is shown. Once inside Settings > More > Developer Options make sure that USB debugging is checked.)
Simply tap OK on the S4 when asked.
Back on the PC if you run EFS Professional it will make sure the S4 is rooted and BusyBox is installed and it should look similar to this.
Tap the Backup tab.
Make sure EFS Professional looks likeThis Picture . You can see that All Partitions is selected but only the four partitions related to EFS are selected to be backed up, then Click Backup to start.
Once the backup process is complete disconnect the S4 from the PC and reconnect it again.
Using Windows Explorer browse to the SD card of the S4 and you will find the backup folder titled EFSProBackup.
Simply copy this folder to your PC and keep it in a safe place.
Step 3 – Download the Android 4.2.2 OS for your country and S4 version
The next thing that is required is to download the Android 4.2.1 ROM that we will flash to the S4 to downgrade it.
Click Firmware Database to be taken to the page below.
Under TYPE, OS, MODEL and COUNTRY select the values that match your S4
Click the 4.2.2 ROM you want to download
Make sure the details are correct for the S4 you are wanting to downgrade and then click the Download button
Once it has been downloaded extract it to your computer as shown in This Picture
Please note that the ROM files can be several gigabytes in size and downloading them may take some time.
Step 4 – Flash the 4.2.1 firmware on to the S4
You now need to flash the firmware that was downloaded on to the S4.
To do this you will need a program called Odin which you can download from here
You need to put the Samsung Galaxy S4 in to download mode which you do so by doing the following:
• Turn off the S4 completely
• Hold down the volume down, home and power buttons together
• Wait for the S4 to turn on and it should boot in to download mode
If you have done it correctly it will look like below and you then press the Volume up button to continue and it will be in download mode
Now you have downloaded Odin connect the Samsung Galaxy S4 to your PC and Windows should download the drivers automatically.
Once you launch Odin, if all is successful and the S4 is in download mode, it should say Added! as shown in This Picture
You now click the AP button and browse to the firmware file you downloaded and extracted from the previous step.
Click the firmware file and click Open.
The firmware file will be checked and then added to Odin so it looks like the screen below. Due to the filesize of the ROM this can take some time.
When Odin looks like the screenshot below you are ready to flash the ROM file because the ROM file has been checked successfully by Odin.
All you need to do is click Start to flash the ROM.
Flashing the ROM can take up to 15 minutes and will take some time
DO NOT DISCONNECT THE S4 FROM THE PC OR TURN IT OFF IN ANY WAY
When the process is finished Odin will say PASS and the S4 will restart and boot in to the newly flashed ROM
Step 5 – Resolving any issues – unable to boot up
If the S4, after you flash the ROM, is stuck on the Samsung logo then do the following
• Turn off the S4 completely.
• Hold down the Volume up, home and power buttons together.
• Wait for the S4 to display the S4 logo and then let go
It will now be in recovery mode which looks similar to this.
Using the Volume up and down keys scroll to Wipe data/factory reset and press the Power button to confirm
Scroll down to Yes and press the Power button on that to confirm.
The Samsung Galaxy S4 will then perform a factory reset.
When it is back on the screen shown above select Reboot and the S4 will restart and boot up – this may take some time when booting for the first time so please be patient
Step 6 – Resolving any issues – Loss of IMEI
If, after the phone has booted up you find that you no longer have a cell signal and that your IMEI number is incorrect – e.g. 004999010640000/01 (Settings > More > About Device > Status > IMEI) then you need to download the modem file from here, save it to your PC and extract it.
Put the Samsung Galaxy S4 in to download mode again and connect it to your PC and run Odin (see step 4 for more information).
It will look like This Picture once connected as we have seen before
Click the CP button and then point to the Modem binary file shown in the last screenshot
Odin should now look like This Picture . You can see the S4 has been added and the modem file is selected.
Click Start to flash the modem and wait.
DO NOT DISCONNECT THE S4 FROM THE PC OR TURN IT OFF IN ANY WAY
Once it has been done wait for the S4 to reboot and you should now have your working IMEI back and successfully downgraded the S4 from 4.4.2 to 4.2.2.
As ever this guide is provided as is so if you have any issues or questions about this simply let us know in the comments and we will do our best to assist you.
All spy software products promise to be “completely hidden,” “undetectable,” “totally invisible” or similar. But are they really? If your spy software isn’t truly hidden, not only will it ultimately fail in the end, but you may also end up seriously busted.
Stealth is important when purchasing Spy Phone software
In this series of Visibility articles we discuss the importance of stealth operation and investigate how well each application truly remains hidden.
We’ll be looking at StealthGenie, MSpy, Mobile Spy and MobiStealth, and comparing each of these with FlexiSPY. We’ll also give you screenshot examples of what we found. This series compares the major spy software and monitoring apps for the Android platform.
Stealth operation comes down to a handful of important questions such as:
Is the application itself well hidden or can it be easily found and disabled by the user? Is it found by anti-virus and security apps?
Does the monitoring app interfere with normal use of the phone?
Does it eat too much battery or consume noticeable amounts of data?
Does it bring attention to itself in other ways?
Stealth operation is more than just hiding an icon. All of FlexiSPY’s competitors are only partiallyhidden at best. Whether advertised as discreet, hidden or even fully invisible, the software can still be found in numerous ways. Sometimes it’s even easier than you’d expect.
Sometimes an app may be found directly from the Application Manager itself. From there an experienced user can track its resource and data usage, kill its running processes or even uninstall it.
Another monitoring app may be spotted by an antivirus utility, notifying the user with a warning to the screen and an offer to automatically uninstall it.
Other apps may leave behind the icon to a rooting utility that was installed as a dependency.
If not hidden properly, a wealth of system utilities can also report on the app’s percentage of battery, CPU time, memory and total data usage.
FlexiSPY’s Visibility series deals with the actual visibility level of the main spyphone competitors in five basic areas. You can find these articles on SpyPhoneReview here, or directly at the links given above.
For even more information, we’ve also conducted in depth reviews covering visibility and more which can be found here.
Many spyphone vendors, including FlexiSPY advertise call recording for Android, but what is it, and why does FlexiSPY not recommend it?
To recap, Android local call recording is where you set a recording schedule from inside a dashboard, and a TARGET Android device will then start recording calls or surroundings and save them locally to the device.
At some point later, the recording is sent to the server where it can be listened to.
So why does FlexiSPY not recommend this? The answer has many parts.
Firstly, setting a schedule for environmental recording is essentially a blind exercise. Unless you know that something interesting is going to happen, the results will not likely be useful. Who wants to hear a toilet flush, or the sound of the TARGET’s legs rubbing against the device?
A much more useful scenario is to be able to listen in at will, and if something interesting is happening, then invoke the recording. Only FlexiSPY can offer this, because we recommend spycall to first listen, and then record, using the FlexiRECORD option if things sound juicy.
Unfortunately this is not possible with Android local call recording.
Secondly, and what most vendors WON’T tell you, is that the Android Local Call Recording technique is inherently unstable and is extremely platform dependent. You will find that mostly it does not work, or if it does, you only hear one side of the conversation. This limitation also applies to FlexiSPY, however, we have a unique call interception system that works on Blackberry, iPhone, Android, and Nokia Belle.
With the addition of the FlexiRECORD product, all call recordings are automated and saved to PC.
We suggest to our customers to try the Android local call recording first, and if that does not meet their needs, we can provide a full or partial refund, or a discount on FlexiRECORD.
FlexiSPY currently offers Android local call recording as part of its EXTREME product, but as its viability has decreased, we will be offering this feature as part of PREMIUM in the very near future.
Summary of Android local call recording Issues
1. Local call recording is for Android only
If the TARGET device you whose calls you want to record is not an Android phone then unfortunately local call recording is not available as it only works on Android phones only.
2. Local call recording works better on some Android phones than others
The performance of local call recording on an Android phone varies from model to model. There is no uniform standard. This means that it may work well on one Android phone but not so well on another.
3. The quality of the local call recording will vary depending on Android handset.
Android devices are exceedingly customizable and this means it is problematic to have local call recording work correctly on every single version of every Android handset. We already mentioned that call recording performance is dependent on Android model but what does this mean and why?
When you perform local call recording you essentially want to record both sides of the conversation. This would be the TARGET device and the person that they are currently talking to when the local call recording takes place.
Unfortunately, whilst it may sound easy to record two sides of a conversation and then upload it it really does depend of a certain number of factors which include but are not limited to:
Android OS version running on the phone
Android phone make and model
Furthermore, when you do record a call and it gets uploaded to your online account the factors above all contribute to the quality of the recording and the recording will be in one of three states.
You hear both sides of the conversation
You hear only the TARGET devices side of the conversation
You hear only the third party’s side of the conversation
This means that local call recording is essentially a lottery in terms of how well it will record calls and the quality of the recording because of the sheer amount of differing Android phones and Android configurations available.
So what can you do to ensure that you hear both sides of the conversation at all times and that you can record the conversations of any kind of TARGET phone, not just an Android phone?
FlexiRECORD is a companion product to FlexiSPY Extreme. In order to operate it you need the following:
A TARGET device running FlexiSPY Extreme
A PC
Your own Android phone
You install FlexiRECORD on to your PC and your own Android phone. You then access FlexiRECORD on the PC and enter the details of FlexiRECORD on your Android phone. With those details in place you simply leave your PC and your own Android phone connected to FlexiRECORD at all times and whenever the TARGET device makes or receives a call using FlexiSPY Extreme FlexiRECORD will automatically record it and save it to your PC so you can listen to it later.
Recording calls with FlexiRECORD has numerous benefits.
You can record calls from any TARGET device – not just Android phones
You always record both sides of the conversation
Recorded calls are saved as MP3 not AMR which means better quality
FlexiRECORD also allows you to record ambient surroundings as well and even remotely control the TARGET phone running FlexiSPY Extreme directly from your own computer.
So if call recording is something you really want out of spy phone software don’t be content with local call recording now that you know its limitations get FlexiSPY Extreme and FlexiRECORD today to see the true power of call recording.
Under the right circumstances, RemCam can be super powerful. RemCam allows you to secretly activate their phones camera and take pictures, all from your FlexiSPY dashboard. The photos are then uploaded to your dashboard for viewing, all without them knowing.
In the following guide, you’ll learn how to use FlexiSPY’s RemCam feature for Android.
Getting Started
Step 1 – Log in to your FlexiSPY dashboard.
Step 2 – Click the RemCam tab.
Step 3 – Click the RemCam button.
Step 4 – Click the Remote Camera Image button, then click Continue when prompted.
Confirmation will appear that the command was sent successfully. Click Close.
Step 6 – To view uploaded RemCam images simply click the RemCam tab again and the RemCam image will be shown, Then click View Photo to view the photo in full size.
Done
That’s all there is to it, and you should now successfully be using FlexiSPY’s Remcam feature for Android.
Of course, if you have any questions about this feature, or any other FlexiSPY feature, feel free to let us know in the comments section below, or through our social media!
If you’re worried about who your children or employees are communicating with – of if you need to protect your personal device from unauthorized access – there are lots of variables you need to be watching. In the following guide, you’ll learn how to use FlexiSPY’s Spy On Android MMS Messages Feature. Let’s get started.
Spy On Android MMS Messages – Getting Started
Step 1 – Login to your FlexiSPY Dashboard via the Portal
Step 2 – Click the Messages tab and then click MMS.
Step 3 – View the MMS messages captured for your viewing.
Done
That’s all there is to it, and you should now successfully be spying on MMS messages. Of course, if you have any questions about this feature, or any other FlexiSPY feature, feel free to let us know in the comments section below or through our social media!
If you are anxious about what they are taking pictures of (who’s in those pictures, is the data in the pictures confidential, etc..) Then you’ll need to be monitoring the images on their phone.
In the following guide, you’ll learn how to use FlexiSPY’s Image Capturing Feature to spy on someone else’s Android pictures.
Getting Started
Step 1 – Login to your FlexiSPY Dashboard via the Portal
Step 2 – Click the Control Center tab.
Step 3 – Click Photo Controls and then click Historical Media.
Step 4 – Set Get Image to On.
Step 5 – Click Sync Now.
Step 6 – View the confirmation that the command was sent successfully.
Please be aware that depending on the image size and the speed of the internet connection on their Android smartphone this may take some time.
Step 7 – After that click the Media tab and then click Photos.
You’ll then be shown a thumbnail of the images
Step 8 – To get the full picture click Get File and wait for the picture to be uploaded from their Android smartphone to your FlexiSPY dashboard.
Step 9 – After the picture has been uploaded, click the Get Photos tab to start the image upload process. Then Click View Photo to see the photos in full size
Done
That’s all there is too it, and you should now successfully be spying on Android phone images.
Of course, if you have any questions about this feature, or any other FlexiSPY feature, feel free to let us know in the comments section below, or through our social media