Universal Samsung FRP Bypass

Share if the site was helpful

Universal Samsung FRP Bypass

nexus2cee_frp (1)

Here are the steps to remove factory reset protection / Google previously synced account lock from your Samsung device.

  1. Download and install RealTerm program
  2. Download and copy com.rootjunky.frpbypass-1.0.apk to the device micro sdcard or download once into the device
  3. start phone and connect to WIFI also plug into the computer with your usb cable
  4. start RealTerm on your pc and under pisplay check the box HALF DUPLEX
  5. right click on my computer and select manage once it opens click device manager then modems
  6. under modems you should see a Samsung device. right click it then select properties
  7. once the properties window opens select modem tab and see what port it is on like com5 for an example
  8. now that you know the com port number close all device manager windows and open RealTerm again
  9. under the ports tab in RealTerm enter your port number then click change.
  10. next click the send tab. you will need to send these two commands with the Send ASCII button
  11. first at+creg?\r\n
  12. then atd1234;\r\n
  13. look at your phone and the dailer will pop up.
  14. Know watch the video below to see the rest of the steps and please comment below on your success or failures. thanks

NOTE: If you dont have a SDcard and are getting the sparse ERROR in es file explorer then you can buy a OTG flash drive like this one and load the FRPbypass.apk to it from your computer then plug it into the phone. once plugged in navigate to it in es file explorer and install the frp bypass app that way. You can also put this address into your ES file Explorer app https://www.androidfilehost.com/?fid=24665542585483676

 

 

If you are still looking for more new FRP Bypass methods make sure you check out Phonlab. All of my latest research on FRP is going to be exclussively on Phonlab along with Samsung Reactivation lock bypass and so much more. Check it out!!!!

Rooting: Advantages, Disadvantages and Myths

Share if the site was helpful

Rooting: Advantages, Disadvantages and Myths

hydroponics-myths-570x321

So you got a new phone and you’re wanting to delve into the world of Android rooting. A lot of questions are probably going through your mind. Should I root it? Should I not root it? What could happen if I do? These are all very logical questions that I’m sure the majority of us have asked ourselves at one point or another. So in this article, we’re going to dive head first into the world of Android root, and hopefully make things a little more clear for you.

 

Some of you may be asking, “Well what does root really mean?”

To root your phone basically means to have administrator rights over the system partition on your phone. It can somewhat be compared to having administrator rights on your Windows PC. Basically this means that you can install, and uninstall whatever you want on your phone. Sounds good right? It is. However, there are a couple valid reasons why your phone does not have this access right out of the box. Supposed you’re new to Android and notice that upon turning your phone on, you instantly have access to every system app and system file that is available on your phone. Woah! Careful though, you have no idea what you can or cannot delete without messing something up. You’re smart though, you can use common sense to get you through this. Next thing you know your phone no longer boots up, it won’t even charge! This is one of the many valid reasons that your phone does not come out of the box with superuser access. Believe it or not, it’s disabled to actually protect you!

So now that we’ve got that out of the way, you’re probably thinking “Well should I or shouldn’t I?” The answer to that question is entirely up to you. So let’s go through the advantages AND the disadvantages of rooting your Android device.

Advantages:

Debloat. Bloatware apps are usually carrier specific apps that come preinstalled on your device. They can be helpful, or they can be a nuisance. Keep the ones you want, get rid of the ones you don’t, permanently. NOTE: permanemtly deleting apps bloatware from your device can some times make ota updates fail.

Install and use those “root required” apps. Such as MyBackup Pro, Root Explorer and many more! These apps can become very useful tools in the rooting world and give you so much more control over your device.

Mods, tweaks and themes. Want to have your clock centered? Well that requires root to be able to install or flash a modified SystemUI.apk.

Custom ROMs. ROMs are basically packages of custom made Android software that you can install on your device to have all the nice little features that custom ROMs come with. Rooting is the first step in being able to flash ROMs.

Control “startup apps.” With root permissions, you can even control what apps start automatically when you turn your device on!

These are just some of the very very many advantages to rooting your Android device. Now let’s take a look at some of the disadvantages. (Yes those actually exist.)

Disadvantages:

You may soft brick, or perma brick your device. “Bricking” has 2 forms basically. Softbrick, which is where your phone either bootloops or won’t boot at all, but you still have access to Recovery and/or Fastboot. “Permabrick” or “hardbrick” is exactly how it sounds. You’re phone is a paperweight. It will not boot, it will not charge, and you have no access to Recovery and/or Fastboot.

You’re opened up to making a lot more mistakes, such as deleting your phone.apk, your Settings.apk. You’d be surprised at how much it actually happens. (However, this is why we have websites such as Rootjunky.com and XDA!)

Ok so now we got those out of the way as well, let’s get into some rooting myths!

Myths:

“Once you root, you will no longer receive OTA updates.” – This is simply not true at all. You will still receive the OTA update on your phone if you’re still on the stock software, and you can still install that OTA update as well. However, you WILL lose root access. This can be a pain if your bootloader is not unlocked. You will have to wait for someone to verify that root access is still possible on the new software version.

“Rooting voids your warranty.” – No. No. No. Rooting absolutely does not void your warranty. The absolute only way that root voids your warranty, is if it can be proven :-), that rooting was the direct cause of your issue. However, this is also a confusing subject. Some carriers don’t really care what you do, and some do. Those that do, will not hesitate to deny you any service or replacements if your phone is rooted. Some do not check at all and do not care. Then again, this also varies between OEMs (Motorola, LG, HTC, Samsung). Some OEMs follow the rule I posted above, and some will not grant you any repairs if your device is rooted. The main reason that some places do not care is because of one simple thing, rooting, can in now way at all, damage your device. All rooting does, is install 1 app (Superuser app of choice) and install 1 file (usually in /system/xbin). That’s it. It can in no way cause your touchscreen to stop working, cause your wifi to stop working, cause you to lose mobile data, none of that. It simply can’t do it, unless YOU mess with something after the fact. Keep in mind what I said before though. This is exactly why we have websites like Rootjunky.com and XDA. If something happens, you have a very good chance of recovering your device.

So there you have it. Some advantages, disadvantages, and even some myths about Android rooting. The choice is always up to you if you root or not. That being said, let me leave you with some tips!

1.) Always always always do your research first! Find out what Android version your device is on, find out if it has been confirmed to be able to be rooted.

2.) Try to stay away from Toolkits and “one-click” methods. I’m not saying that the people that make such methods don’t know what they’re doing. What I’m saying is, if you’re going to get into this world, learn the way it used to be done! Learn your adb commands, learn your fastboot commands! Don’t take Android modding away from it’s roots.

3.) When you find a guide about rooting your device, FOLLOW ALL INSTRUCTIONS TO THE “T!!!” Do not cut corners, do exactly what the guide tells you to do!

4.) Last but not least, always make sure you perform backups before flashing ROMs. Always make sure you have a recovery plan before doing ANYTHING to your phone.

Well hopefully this article helped you learn something, and hopefully it made the decision a little easier on you. The Android community is very amazing community that is just filled with people willing to help others out when they’re in need. We’re a community that you absolutely WILL NOT find anywhere else. On that note, be safe, be smart, read, read some more, and have fun!!

 

BY

Gary H

 

Android 5.1 Launches On Nexus Devices

Share if the site was helpful

Android 5.1 Lollipop Arrives

This week on the Official Android Blog, Android Lollipop 5.1 was announced with some minor, but well deserved modifications to Lollipop 5.0.

Dum_Dums_Lollipops

 

A small list of some of the changes:

  • Voice-Over-LTE (Currently supported on T-Mobile and Verizon)
  • HD Voice (Currently supported on T-Mobile and Verizon)
  • Device Protection (Remote locking similar to iCloud lock on iOS products)
  • Better Wi-Fi and Bluetooth Quick-toggles
  • Support for Multi-SIM devices

Android 5.1 is currently being pushed to Nexus 5, 6, 7, 10. If you want this latest firmware the best place to download it is from HERE

Source from Official Android Blog

A couple things i have noticed with android 5.1 are that it runs much smoother on my Nexus 6. Apps and browser windows load quicker which I really like. It also seems like the encryption on the Nexus 6 kind of slowed down the device but with Android 5.1 it is working normal again even with the encryption.  There are also a lot of little animations that make it a much nicer experience.

Samsung “Next Is Now” S6/Edge

Share if the site was helpful

Samsung Galaxy S6 and Edge

Plastic.

Band-Aid.

Cheap.

Just some words that many have used to describe Samsung’s Galaxy line of phones in the past. This year, Samsung has changed that notion and flipped the tables on its design philosophy.

 

The Samsung Galaxy S6 in the flesh.
The Samsung Galaxy S6 in the flesh.

 

 

The Samsung Galaxy S6 and S6 edge are made out of metal and gorilla glass 4, which wraps the front and back sides of the devices, with the metal around the sides where one would hold the phone. Obviously to most, the name isn’t the only difference between Samsung’s flagship variants, but two curved edges come with the S6 edge. Unlike the recent Galaxy Note Edge which was slanted on one side and took away button real-estate, the S6 edge also is only partway skewed, giving the user room on the sides to hold the device comfortably along the metal sides.

It’s not just the outside that changed though; Samsung has opted for their own silicon this time around using an 2.1 Ghz 14nm Exynos Octa-core processor (64 Bit of course). They’ve also become the first smartphone to include DDR4 memory and UFS 2.0 storage. Without getting nitty gritty in the nerd speak here, this means insanely fast storage with speeds never before seen in a smartphone’s flash memory, faster operations, and much improved battery usage overall.

Samsung has stuck with a 16MP shooter, but are now using Optical Image Stabilitzation (OIS) for un-shaking those photos and an F1.9 lens. Again, not getting down and dirty with specs, the low light quality on this should be insane, and the camera a noticeable improvement over the Galaxy S5. The same lens is also on the 5MP front facing wide-angle camera.

Real life battery usage will take time to see. The Galaxy S6 rocks a 2550 mAh battery while the S6 Edge a 2600 mAh, only a trivial  50 mAh difference. The big change this time around, Samsung has built in a competitor to Qualcomm’s Quick Charge technology. They are claiming 4 Hours of battery life in only 10 minutes on the charger, quite a claim to make! Another inclusion is Wireless Charging and not just one, but two technology are inside. What this means for the end user, is any wireless charging station is going to work just fine, and no more worrying about what a “Qi” is.

Some other additions are Samsung Pay, a serious competitor to Apple Pay and Google Wallet. Not only does it support NFC payments, Samsung Pay supports MagStripe Transfer. Any place that accepts sliding a credit card, will accept Samsung Pay. This is amazing news, with many locations blocking NFC payments for nefarious or unknown reasons. The other addition a new fingerprint scanner, now touch based rather than swiping. This is a key part of Samsung Pay, since it encrypts everything with your fingerprint stored locally on your device, never going to some untrustworthy server.

Overall, Samsung has made some serious strides, but as you may have noticed they have discontinued external storage, water resistance, and removable battery support. This may seem like a deal-breaker to some, but with new charging methods and 3 storage options the Galaxy S6 and S6 Edge seem like the phone to want, as of today.

 

 

Specs List:

2.1 Ghz Octa-core Exynos Processer (14nm Process).
16MP F1 w/ OIS back facing. 5MP F1 front facing.
3GB DDR4 memory.
UFS 2.0 storage in 32GB/64GB/128GB configurations.
Wireless charging and NFC.
2550 S6/2600 edge mAh battery.
5.1″ 1440p SuperAMOLED display.
Fingerprint scanner (touch based).
Colors: White Pearl, Black Sapphire, Gold Platinum, Blue Topaz.

The Galaxy S6 and S6 edge are planned to launch April 10th, 2015 in 20 countries initially.

US Cell Phone Carrier Unlocking Policies

Share if the site was helpful

US Cell Phone Carrier Unlocking Policies

unlock carrier

Policies: Verizon | AT&T | Sprint | T-Mobile | US Cellular

First what is carrier unlocking and why might I want this for my device? If your device is carrier unlocked then you can put any carriers sim card in your phone and it will work as long as the device you are using supports that carriers network frequencies. On the other hand if your cell phone is carrier locked then it is stuck on whatever carrier you have and will not work on any other network.

Note: Most people confuse bootloader unlocking with carrier unlocking. These are to very different things carrier unlocking has to do with the Network and bootloader unlocking has to do with freedom to flash custom firmware / OS to your device.

Above you will find linked all the policies for these major carriers. Check to see if you meet the requirements and can get your device carrier unlocked for free through there programs. If you aren’t eligible then start Googling carrier unlock and you will find that there are many free and paid for services out there that can accomplish this task of unlocking your phones networks for you. Most cost 25 dollars or less some are even free.

As of today Feb 11th 2015 the FCC and CTIA is forcing all carriers to allow customers to unlock there phones if they meet the requirements listed. So go check out your carriers policy and see if you are eligible.  Now you will be able to bring your device to any carrier and not have to buy a new one if you don’t want to. As a customer you bought the device and you should fully own it and have full control not the OEM or the carrier.

Other Important Links:  FCC device unlocking FAQ | CTIA Consumer Code for Wireless Service

 

Motorola Firmware Restore

Share if the site was helpful

Motorola Firmware Restore Plus Unbrick

In this tutorial i will be covering restoring and unbricking your motorola device by flashing the stock fimware. We will be using RSD lite (Motorola Program) along with using fastboot and a batch file. This tutorial will be for windows user only since i dont have a mac. First lets cover the older Motorola droid devices that use RSD lite

WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.

RSD Lite Firmware flash Requirements

1.  Motorola device

2.  USB cable for device

3.  Download the Motorola Drivers and install them your PC

4.  Download RSD lite Program and install it on your PC

5. Download your devices latest firmware. (NOTE) The best way to find out what device and firmware you need is to go into phone settings then about phone. Look at System Version plus build number. Between these you should be able to figure out the firmware you will need. Another good thing to find out is the device code name. Normally a quick Google search can accomplish this task. If you dont know this info and your device is bricked then start Googling it. You can get your motorola firmware from my server or Motofirmware.com

Flashing firmware

(NOTE) It is highly recommended that your device is fully charged before starting this firmware flash. Older devices have small batteries and can die during the restore which would be bad. The only way to fix a dead bricked motorola android device is with this factory cable that can send power to the device even with a dead battery. This cable comes in really handy at times and can be picked up from amazon if needed.

1. Place your phone into AP Fastboot Mode. Turn off the device then press and hold both volume up and down then hold power, now wait 5 seconds and release then buttons. You should now see a screen like this one.

ap fastboot

2. Now connect the USB cable to the device and let the motorola drivers you downloaded and installed on the PC, install for the device. This may take up to 5 minutes.

3. Open the RSD lite program and make sure it sees your device like in the picture below

RSD lite

4. click on the 3 dots where it says file name and select your firmware you downloaded. (NOTE) if the firmware is in a zip then just select it. If you extracted the firmware already, then select the XML file

XML

5. Click start button on RSD lite and sit back and wait for the device to finish the restore. Once the device has finished it will reboot and you will see the setup screen. Now you have unbricked and restored your stock firmware to your Motorola device.

(NOTE) Do not bump or unplug the device while flashing the firmware. This could cause a hard brick and your device will be dead. Also, if  the device gets stuck in a bootloop on reboot, just boot the device into stock android recovery, then wipe data factory reset the device. This will fix the bootloop. Below is a video on this process.

HERE IS A GREAT POST ON XDA THAT COVERS THIS EVEN MORE

 

 

 Fastboot Firmware Flash Requirements

1.  Motorola device

2.  USB cable for device

3.  Download the Motorola Drivers and install them your PC

4.  Download Fastboot and ADB files 

5.   Download your devices latest firmware (Note) best way to find out what device and firmware you need is to go into phone settings then about phone. Look at System Version plus build number between these you should be able to figure out the firmware you will need. Another good thing to find out is the device code name. Normally a quick Google search can accomplish this task. If you dont know this info and your device is bricked then start Googling it. You can get your motorola firmware from my server or Motofirmware.com

Flashing firmware

(NOTE) It is highly recommended that your device is fully charged before starting this firmware flash. Older devices have small batteries and can die during the restore which would be bad. The only way to fix a dead bricked motorola android device is with this factory cable that can send power to the device even with a dead battery. This cable comes in really handy at times and can be picked up from amazon if needed.

1. Place your phone into AP Fastboot Mode. Turn off the device then press and hold both volume up and down then hold power, now wait 5 seconds and release then buttons. You should now see a screen like this one.

bootloader mode

 

2. Now connect the USB cable to the device and let the motorola drivers you downloaded and installed on the PC, install for the device. This may take up to 5 minutes.

3. Extract the firmware and fastboot / adb files you downloaded to the same folder on your desktop like the picture below.

fastboot plus firmware

 

4. Click on the file in the folder ending in .bat This is a batch file that will open and flash all the firmware in this folder. Once the firmware is flashed and if you dont have any errors, then in fastboot mode on the device, select normal power up and the device will power up and be fully restored.

(NOTE) Using a batch file and fastboot to restore your device is the preferred method over RSD lite. RSD lite sometimes hangs on some steps in the XML and can be a real pain. Here is a video of me using a batch file to restore one of my Motorola Android devices.

 

CyanogenMod 12 Lollipop

Share if the site was helpful

Official CyanogenMod 12 Lollipop

CM12 roms are starting to show up on CyanogenMod.org which means many Android enthusiast with be getting there hands on one of the best Lollipop custom rom experiences. I recently installed CyanogenMod 12 Lollipop on my Motorola Nexus 6 and it is running nicely. Something new that i noticed in this version of CM is that Root access is turned of by default. Come to find out you can turn it back on by entering developer Options in the devices settings and then selecting Root access mode. here you will find a couple options: enable for apps only, enable for adb only, or enable root for both apps and adb which is the option i selected. Having root mode off by default i think is a really bad idea since most Android fans that install CM12 really want root. But i guess that is up to CyanogenMod.

Here is a little Video i made talking about how to turn on said Root access mode

So if you are looking to install Official CyanogenMod 12 Lollipop on your android device then check out there download page HERE If you cant fine your device listed you may want to check XDA developers site because there are many unofficail CM12 roms in the forums that work just fine. Good luck and lets start rocking some Lollipop Android 5.0

Moto E Super Tool

Share if the site was helpful

Moto E Super Tool

This is a little script tool I made up for the Moto E XT1023 The Firmware restore will only work on the XT1023 but all other options should work on all the variants of the Moto E
It is really simple. But requires a unlocked bootloader video HERE If you need help with bootloader unlock
Click image for larger version</p><br />
<p>Name:	tool1.PNG<br /><br />
Views:	2147<br /><br />
Size:	59.8 KB<br /><br />
ID:	2791689

Download the Moto E Super Tool
extract the tool to your desktop
Turn on usb debugging mode on the device
install the Motorola drivers
Run the Moto E 1 Moto-E-Restore-XT1023.bat file
then just select what you want to do
1. Root your Moto E
2. Flash TWRP Recovery
3. Flash Stock Android Recovery
4. Flash CWM recovery
5. Remove the unlocked bootloader warning
6. Fully restore the Moto E to stock
7. Fully restore plus Relock the bootloader

Newest release V2
Change Log

Vision 1 first release
Version 2
updated TWRP
Updated Supersu.zip

DOWNLOAD SUPER TOOL

Hope this will help out some noobs

Android 5.1 Rumors

Share if the site was helpful

Android 5.1 Rumors

Statue

Android 5.0 (Lollipop) isn’t even available for most Android phones yet, but Google may already be working on an update for the software.

A new version of Android called 5.1 is reportedly coming in February, according to the blog “Android Pit

The blog claims to have spoken with two “trusted sources” familiar with the situation.

Based on the reported list of new features coming in the update, it sounds like some minor improvements and bug fixes are coming.

One notable fix, for example, seems to be the addition of a silent mode to Lollipop.

When Android 5.0 was initially released in November, users complained about the lack of a “silent mode” for notifications. Rather, users can choose from three options when it comes to notifications: None, Priority, or All.

“None” keeps your phone entirely silent, which also means your screen doesn’t light up when you get a text or notification. “Priority” mode silences almost everything except for alarms, and only allows notifications from certain designated contacts to come through. And “All”, as you can imagine, just allows all notifications to come through normally with sound.

Here’s a list of features and bug fixes that will supposedly come with Android 5.1.

  • Silent mode added after missing on Android 5.0
  • General improvements in system stability
  • Improved RAM management
  • Fixes for sudden app closures
  • Improved battery management
  • Excessive consumption of network devices when used Wi-Fi fixed
  • Issues with wireless connections fixed
  • Problems with Okay Google function solved
  • Notifications problems solved
  • Some sound problems experience by certain devices fixed
  • Other improvements and changes
  • Changes in the Material Design color palette (after users complaints, possibly for a higher version though)

Keep Following closely as we will update you on any Android 5.1 rumors and News

By: Gary H.

LiveBoot App

Share if the site was helpful

[ROOT] LiveBoot

Live boot

 

LiveBoot is a boot animation that shows you logcat and dmesg outputs on-screen as they happen. Output configuration includes logcat categories, whether to show dmesg, and the amount of lines that should fit on your screen. For Pro users there’s also the option to make the output transparent and overlay the default boot animation.A feature is built-in to test your current configuration without rebooting. The lines shown in test mode may be limited and relatively static, this does not reflect exact boot time behavior as much as it just shows you that it works and how big the text will be.Note that LiveBoot will only show up after the data partition is mounted. If you need to enter a decryption key or pattern at boot, it will not show up until you have done so.RootThis app does not only require root, it requires specifically SuperSU version 2.40 or newer, due to how the boot-time code is launched.

Compatibility

Officially the app supports 4.3+ and newer, but really it is aimed at 5.0 firmwares. Regardless of 4.3, 4.4, or 5.0, the app may work on your device or it may not. I’ve gotten it to work on a bunch of my own devices on various firmwares, but not on all. Even if the test run functionality works, this does not necessarily mean it will actually work during boot. It usually does, but not always.

This does indeed also mean I cannot guarantee continued operation – even if it works for you today, it may fail your next firmware update. If that is an issue for you, then you should definitely not update to Pro.

The risk of bootloops is extremely low, but not completely non-existent. Should a bootloop occur, removing either the app’s APK or /system/su.d/0000liveboot through recovery should fix the problem.

The app writes to /system, as such your firmware must allow this. There is no recovery-based install option at this time.

Pro

There’s an in-app purchase to upgrade to Pro, which supports my developments, and unlocks the transparency option.

Of course, if you have one of the paid variants of the old live logcat or live dmesg boot animations from all those years ago installed, this will also enable Pro mode.

Like some of my other apps these days, if you don’t have Google Play but still managed to install the APK, this will also enable Pro mode.

Last but not least, if you simply don’t want to pay for it, there’s also a button to enable Pro mode.

Script

If /system/su.d/0000liveboot.script exists (chmod 0644, not 0700 like other files in /system/su.d/ !), this script will be run instead of logcat and dmesg, and its output will be shown in white (stdout) and red (stderr).

Discussion/support/etc

Please see the official app thread on XDA-Developers.com here: http://forum.xda-developers.com/android/apps-games/liveboot-t2976189

Also check out Chainfires post on Google Plus here: https://plus.google.com/+Chainfire/posts/G4GjETEQhR1

This is one really cool Liveboot App that will be really helpful for developers to use. Go check it out for yourself

Download the app here from Google Play LiveBoot