ChromeBook Recovery Hacks and Tricks

Share if the site was helpful

A Chromebook can be a great purchase even if you never step outside of Google’s trusted environment. They are some of the best web machines ever built, require almost no software maintenance, and come in a myriad of different styles and price points. Now that the latest models also come with Google Play Store and support thousands of apps where are some amazing devices.

But like anything electronic, sometimes it’s fun to push the envelope and do things a little outside of the intended use. Sometimes that means hidden features in the software, sometimes it means altering the software, and sometimes it means replacing the software entirely. We’re familiar with people doing just that with Android, but it’s also pretty easy to do with your Chromebook. The best part is that it’s also very easy to go back.

Create a Chromebook recovery image

Before you start doing anything it’s always a good idea to have a path back to a time when everything worked. Luckily, that’s fairly easy when we’re talking about a Chromebook. Google has an official tool that will install the factory-issued software to your Chrome device on a 4GB or larger USB stick or SD card. You can then use this media to restore your Chromebook just like it was fresh out of the box. Thanks Google.

Directions

 

Step 1: Install the Chromebook Recovery Utility app

  1. On the working computer (Windows, Mac, or Linux) and (not the Chromebook with the error), install the recovery app.
  2. Open the app.

  1. In the screen that appears, type in the model number of the Chromebook you want to recover. Note While in recovery your device will display the model see picture below for details.
    You can find this number at the bottom of the error message on your Chromebook.
  2. Click Continue.

Important: All the information on the USB drive or SD card will be deleted. Make sure you’ve backed up those files.

  1. On the working computer, insert your USB drive or SD card into an open port. The recovery app will show all storage devices connected to your computer.
  2. Use the dropdown menu in the app to select the correct storage device.
  3. Click Continue.

To create a recovery image:

  1. Click Create now.
  2. The tool will create the recovery image on your USB drive or SD card. Don’t remove the storage device yet.
  3. When you see a message saying that your recovery media is ready, remove the storage device from your computer.

Open the Chromebook you want to recover.

If you have anything connected to this Chromebook (such as a mouse, SD card, or external hard drive), remove it.

Enter recovery mode:

  • On a Chromebook: Press and hold Esc + Refresh Refresh, then press Power Power. Let go of Power. When a message shows on the screen, let go of the other keys.
  • On a Chromebox: Turn it off. Using a paper clip or similar object, press and hold the recovery button. Press the Power button to turn the Chromebox back on. When you see a message on screen, release the recovery button.
  • On a Chromebit: Unplug it from power. Using a paper clip or similar object, press and hold the recovery button. Plug the Chromebit back in to power. When you see a message on screen, release the recovery button.

You’ll see one of these messages:

  • “Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card.”
  • “Please insert a recovery USB stick or SD card.”

Insert the recovery media you’ve created (SD card or USB drive).

Follow the on-screen instructions.

Reboot and enjoy your factory-fresh software!

STOP WRITE HERE AND CREATE THE RECOVERY IMAGE NOW BEFORE CONTINUING.  

If you are still having problems check out this info HERE

Change to the beta or dev channel

This is really simple and something I recommend. By default, your Chromebook runs on the stable release channel for your model. This means everything has been tested, things run pretty smoothly, and there usually aren’t any critical bugs to trip you up.

That’s absolutely no fun.

The good news is that we all can be testers by switching the software channel in the settings. Click the Chrome OS wrench icon in the lower right and open the settings. Choose About Chrome OS > More Info. Click the Change Channel button and choose between Stable, Beta and Dev – Unstable channels in the popover window that appears.

 

Both the beta and the dev channel give you access to upcoming (both default and experimental settings — see below) features that aren’t in the stable channel just yet. I’ve always found the beta channel to work pretty well, but expect issues and glitches on the dev channel along with the latest features.

If you just want everything to work, switching back to the stable channel is just as easy — choose it from the same list!

Tweaking the settings

Chrome — both the operating system and the stand alone browser for Windows Mac and Linux — has an entire page filled with “experimental” settings. Some will absolutely break things, others might improve your experience. Find them is simple.

Fire up the browser and enter chrome://flags into the Omnibox (a fancy name for the URL bar in Chrome) then hit enter.

You’ll be faced with a huge list of features that you can enable or disable at will. All of them are experimental, some are serious security holes, others are potential oh-crap-I-need-to-reload-EVERYTHING bringers of doom. We don’t recommend you just jump in and start enabling things. Instead, talk to people who are using the same model of Chromebook that you are and find out what works and what doesn’t.

It’s also worth remembering that these experimental flags can disappear at any time. Some may be merged into the OS, others will just up and disappear. If you do enable something, lets say for example, GPU compositing, and it breaks everything (yeah, I’ve been there), you have your recovery media you made earlier to save your bacon.

Install Linux

One of those complicated things that has been made simple by the work of great developers, installing Linux on your Chromebook is a great way expand its capabilities. Chrome OS is a flavor of Linux, but it’s been trimmed down and many features have been removed. We’re going to look at the simple (and in my opinion the best) way to build a dual-boot environment so you have both Chrome OS and Ubuntu LTS using David Schneider’s excellent tool called crouton (Chromium OS Universal Chroot Environment).

You’ll need to enable developer mode on your Chromebook, and the method varies from device to device. You may need to flip a hidden switch, or enter a key combination during boot. You can find exactly how to enable developer mode for your Chromebook on Google, and once you’ve done that everything else is the same no matter which model you use.

Once you’re a developer (or at least in dev mode) you’ll need to head to the crouton project page at github and download the script from the top of the page. Save it to your Downloads folder and you’re ready to get started.

Open a terminal (I told you Chrome OS was Linux) by pressing Ctrl+Alt+T and enter the word shell to open a shell.

Next, run crouton to see all the help text and examples like this:

sh -e ~/Downloads/crouton-master

Read everything you find there, as these are your options and tell crouton what to install. If you don’t understand an option, ask someone. Also, read the help section at the crouton github page for examples and hints.

Once you have crouton set up, you’ll be able to swap between Chrome OS and a full fledged install of Linux (Ubuntu LTS) at will.

While I like the flexibility of having both Chrome OS and Ubuntu on the same machine, you may want to be rid of Chrome OS completely. If you’re interested in replacing Chrome OS with Ubuntu, have a look at the ChrUbuntu project here. If you want to replace Chrome OS on your Pixel with Debian Wheezy, grab a beverage and have a look here.

These are just a few of the neat hackery tricks you can do with your new Chromebook. And like everything else, it may turn out that none of it is for you and you prefer things that just work as intended. That’s cool, and sometimes when I’m staring at the screen of a device that won’t boot, I’m right there with ya.

If you do want to dive in and have a go at Chrome OS, this is how I do it. Tell me how you do it in the comments, I’d love to hear about it!

RootJunky

How to set up SuperSu root manager after root

Share if the site was helpful

How to set up SuperSu root manager after root

If you have SuperSu on your device you must be familiar with rooting. So what is SuperSu application and what can you do with it? In general it is the tool which manages root permissions for all the applications on the phone which require root, with SuperSu you can select which apps have root access and which do not.

Lets have a look inside SuperSu, inside you have 3 sections: Apps, Logs and Settings.

The 1st section (APPS) shows you list of  applications installed on the device which asked for root access.

Click on app to open menu: next to option ACCESS you can select PROMPT, GRANT or DENY, depending if you want application to gain root privileges. Try to keep list of apps with granted permissions as short as you can, allow permissions only for the apps which either work with root only or have more privileges with it.

Next option is NOTIFICATIONS, you can choose options: “Global Default” to see  notifications if app is gaining access on the screen or “Disabled”, to switch off annoying dialog for specific app.

The 2nd section (LOGS) Shows you which app asked for root permission, time and which action was taken (allowed or denied) in case you switched on Logging option in settings. Pretty simple. Let’s move further!

The 3nd section (SETTINGS) Settings is the largest one and the most important – Settings. Correct set up is of great importance to avoid problems.

Enable SuperSu – switches on/off root on the phone, should have checkmark for root t work;

Re-authentication – disabled in case you do not want SuperSu to ask permissions again in case app is reinstalled or upgraded. If option was enabled SuperSu will always ask again permissions for the app after upgrade/reinstallation. I keep it disabled to avoid annoying dialogue pop-up.

Default access – selects default root access for all apps in case no option was chosen when prompt appears. You can choose GRANT / PROMPT/DENY.

Auto deny countdown (available for PRO version only) – gives you option to set up countdown time on SuperSu prompt asking to grant or deny access, basically that is how long user will see prompt on the screen to decide the destiny of app, in case no option selected – default value is chosen. Keep in mind that setting the countdown more than 10 seconds may cause crashes for apps which are written not in perfect way. As for me it is a bit useless:)

Show notifications – you have two options to select: “Global Default”  – if you wish to see notifications in notification menu bar about gaining access, “Disabled” – in case notifications are annoying for you and you want to get rid of them. I always select second one.

Logging – if you are not a developer, do not plan to be developer and do not need to get debug logs from SuperSu or even do not know what it is  – select option NONE, otherwise if debugging is important choose GLOBAL DEFAULT. Keep in mind it may cause crash of the application in case root permissions are asked great deal of times and logs are saved, stored, fill up memory of the phone.

Clear logs after – time-frame during which SuperSu logs are saved in case Logging is enabled. Otherwise option is grayed out.

Logs date format – choose format of date displayed.

 The Auto-refresh apps and logs tab allows the phone automatically refresh apps and logs tabs as new entries are added. Detection depends on access and notification settings.

PIN code (Pro version only) – gives option to protect SuperSu with PIN, may be useful in case Multiusers option was enabled and different users use device.

Enable Su during boot – applies all permissions during boot in case option enabled. Otherwise, permissions are applied randomly after the boot. Better to keep option enabled for boot settings to be set up properly. This option is disabled by default – make sure you switch it on.

Launcher icon – gives you variety of SuperSu  logo options, also you can select INVISIBLE to hide icon.

Theme – select dark or light theme of SuperSu interface

Language – gives option to select convenient language from the list of available.

Install SuperSu into /system – option to make SuperSu system app, in this case you will not be able to remove it from regular application manager. To delete SuperSu you will need to use either Alternative App manager (Titanium backup), or use ADB, one more option – factory reset of the phone.

Trust system user – option to give root access to the apps that are located in /system/app (System applications).

Reinstall – designed to fix SuperSu crashes (SuperSu has stopped), click on it to clean up previous installation, then install from PlayStore. Not advised to use this option if no SuperSu issues occur.

Switch Superuser app – designed to change root manager, will clean up SuperSu. As for me SuperSu is the best app to manage root access, however if you prefer another one or just want to experiment – can try, that is your choice. Note that root can be lost during process and you will need to start all over again.

Full unroot – important option but tricky. Allows you completely remove root from device. Be careful with it – it can softbrick phone, I am seriously. Before clicking this button very important to switch off option Enable SuperSu, on the top of settings. Once done you can unroot, but not before unless you wish to flash stock firmware.

Pretty wide variety of options. Cannot really skip mentioning what to do if you selected option for SuperSu icon to be invisible.

In case the icon was hidden and you need to launch SuperSu there are a few options:

1) Dial one of codes on the dial pad, one of them may work:*#1234#* or *#*#1234#*#* or *#7873778#* or *#*#7873778#*#* (does not work on Android 6.0)

2) Download Enable_SuperSU.apk  (google it) and manually install on the phone. Once you launch it app will ask root access > hit GRANT. You will see pop-up with options to Enable Su and Make it visible (100% working).

3) Open PlayStore – find SuperSu and follow steps: Uninstall > Install > Open (sometimes may cause issue with updating binaries).

4) Use adb terminal (phone and adb drivers should be installed on PC) and type adb shell am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity (100% working)

You can also use Terminal emulator (available on PlayStore) and type there am start -a android.intent.action.MAIN -n eu.chainfire.supersu/.MainActivity

No need to type “adb shell” as you are already in shell 🙂

 

What if you rooted phone with the other application and now have KingUser or SuperUser but SuperSu is in your dreams and you cannot sleep even because of that.

There are several options how you can change root manager app. Keep in mind is not safe.

There are 2 options:

1) Download SuperSume application from PlayStore it costs 4$ approximately. Install it on the phone and launch > you will  get prompt asking root access > hit ALLOW. Then click on large blue button with Android guy and wait, process takes up to 5 minutes. In case nothing happens in 5 minutes – reboot phone and try again.

Phone may be rebooted automatically during process, do not panic. In case you see SuperSu after reboot  – means operation was succeed.

Open SuperSu – application will ask to update binaries – hit Continue and select Normal installation. Updating binaries may take up to 5 minutes, in case it is taking longer – reboot and try again.

In case update was successful – will get notification about that – restart the phone and use SuperSu, you are done and awesome.

In case you get error during binaries update – reboot and try again. Make sure KingUser/Kingroot was removed from the phone, if no – disable it from Application manager and try updating binaries again.

In case Kingroot/SuperUser was removed but SuperSu was not installed – try installing the one from PlayStore.

Keep in mind this method can cause bootloop and is not very safe, in case you do not want such thing to happen to your phone and have headache restoring it  think carefully why do you want to change root manager, what is purpose. Strongly NOT recommended for Alcatel, Huawei, ZTE and other Chinese phones.

2) Use adb or Terminal emulator and script to change icon. This method is more safe, but more difficult.

Firstly download mrw folder, place it in the internal storage of the phone.

Then  download ADB and drivers on the PC, connect phone and make sure it is recognized with adb. Then type: adb shell

In case you do not want to use PC/do not have it try Terminal Emulator from PlayStore on the phone> open it and ALLOW root access.

Now type following in the command line (both, PC or phone):

su

Hit enter, you will get prompt to allow root permissions, hit ALLOW.

The command line will move to next line and you will see # sign.

Now type:

sh /sdcard/mrw/root.sh

hit Enter, you will see code is running, some errors may appear but do not pay attention, SuperSu will be automatically launched in case of Success, application will ask to update binaries – hit Continue and select Normal installation. Updating binaries may take up to 5 minutes, in case it is taking longer – reboot and try again.  Make sure KingUser/Kingroot was removed from the phone, if no – disable it from Application manager and try updating binaries again.

In case update was successful you will get notification about that – restart the phone and use SuperSu. You are done and awesome.

In case SuperSu was not launched after script – check manually if you have it on the phone. If nothing appears – guess what? You are right – reboot and try again from the very beginning.

Note, script will not work in case mrv folder is located in the other location, different from specified /sdcard/mrw/root.sh

-Diana Lisovenko

Amazon Ads & Bloat Removed from the Motorola Moto G 4th gen

Share if the site was helpful

Amazon Ads & Bloat Removed from the Motorola Moto G 4th gen

Hey Guys as soon as i heard that Amazon was offering a device with ads for a lower price to amazon prime member i was pumped and ready to remove those ads as soon as i got the device in hand.
well Amazon has made it really easy for us in many ways.
You can just flash one file that i have put together to remove the ads and all of the amazon apps in one shot.

Requirements

Moto G 4th gen tested on the XT1625 may work on other models i dont know.
Motorola Drivers installed
Motorola program RSDlite 6.2.4
The Files and remove-amazon-bloat.xml file i created HERE

Steps

1. Boot device into bootloader / fastboot mode by powering down then holding volume down and power until it boots
2. Open RSDlite 6.2.4 and select the remove-amazon-bloat.xml
3. press START and wait for device to reboot thats it once rebooted your amazon apps and lock screen ads are gone.

 

NOTE If you are having problems with RSDlite and windows 10 use this XT1625-Amazon-Bloat-Ads-Remover-Without-RSDLITE

Rootjunky out

NOTE The Bootloader can be unlocked through the Motorola bootloader unlock site which is awesome. BOOTLOADER UNLOCK VIDEO HERE

NOTE I put together a script that will install twrp and systemless too in one click if anyone wants it after they unlock there bootloader

If you want Amazon Underground apps back check HERE

Creating your first Android Icon Pack

Share if the site was helpful

Creating your first Android Icon Pack

app icon

Notiflux a youtube fan contacted me the other day to see if i would like some custom Icons to go with my RootJunky logo and colors. I told him, I would love it.  From there Notiflux created me some awesome icons using Gimp a photo editing program. You can also use programs like Paint.net and Adobe Photoshop which is my favorite. With these cool new icons in hand I had to take on the task of creating a Icon Pack App for them.

 

paint.net

Creating your first Android Icon Pack can be a little challenging but I hope that this post will help you along the way. One of the first things you need to do it download and install the Android SDK which is included in Android StudioAfter installing Android Studio you will need to update the Android SDK to get the latest version, check this post for help.  NOTE  I used Eclipse to build my apps as that is want i am use to but if you are just getting started it is highly recommend to use Android Studio. 

eclipse

Creating your first Android Icon Pack is really easy if you use Apex Icon Pack Sample as your template. This is really helpful in getting everything to need setup and running.  Open Android Studio or Eclipse and Import the Sample app. Once done you can go ahead and make some quick edits to it and have your own icon pack app.  While editing I have found it easier to look at the XML files instead of the Graphical layout or resource views, its is much more logical this way.

A couple really good recourse to help you in editing the Apex Icon Pack Sample can be found Here and Here. The main files that you will be editing are the files in folder RES and SRC the rest of these files can me left alone for the most part. You can put your edited Icons in the drawable-xhdpi folder. Once you have make all your edits you can either run the app on a connected phone over adb or you can export the app to a APK file and then install it on any device you want to.

It you have a day or to to read through all the this information and get a Icon Pack of your own, it can really be a lot of fun. Use your imagination and there is no telling what awesome things you might create. If you would like to Check out my Icon Pack that works with a bunch of Android home launchers like Apex and Nova click here and you can download it from the Google Play Store.

Extra Credit

Link to the files i used in my app can be found here, should be a great help if you need to compare some code like i did.

RootJunkySDL.com

Thanks to Notiflux for all his help

RootJunky Out

Please Comment and Share if you found this post helpful.

NVIDIA SHIELD Android Gaming System

Share if the site was helpful

NVIDIA SHIELD Android Gaming System

459087-shield-controller-remote-credit-nvidia

 

Today we are taking a look at Nvidia’s Version of a Android TV box setup. We have already seen the Nexus Player, Ouya, Fire TV and many others but none of them compare to the Nvidia Shield android TV box.  The processing power and specs on this iteration of Android tv box is really amazing and really aimed at the gamer.  The Nvidia shield box will come with a Tegra X1 processor sporting 256-core maxwell GPU, 3GB of ram and be able to display in 4K ultra HD.  This device will be a Android Gamers dream.

Just like all the other Shield device Nvidia has made you will be able to stream games with Nvidia Grid. What’s more is that NVIDIA has worked with partners to port major game titles to Android, specifically for devices powered by the X1 processor. Games like Crysis 3, Doom 3: BFG Edition, Borderlands 2, Borderlands: The Pre-Sequel, The Talos Principle, Metal Gear Solid: Revengeance and Resident Evil 5 among others.

Now the best part off all about this device is the price just $199.99 this includes the Nvidia Shield android tv Box, shield remote, and shield controller. The release date is in may 2015 in the us. I for one cant wait to check this device out.

images

 

Nvidia Shield Android TV Specs

  • NVIDIA Tegra X1 Processor with 256-core Maxwell GPU
  • 3GB RAM
  • 4K Ultra-HD Ready with 4K playback and capture up to 60fps (VP9, H265, H264)
  • Audio Features: 7.1 and 5.1 surround sound pass through over HDMI, High-resolution audio playback up to 24-bit/192kHz over HDMI and USB, High-resolution audio upsample to 24-bit/192hHz over USB
  • 16GB on board storage, MicroSD slot supporting 128GB
  • Wireless: 802.11ac 2×2 MIMO 2.4 GHz and 5 GHz Wi-Fi
  • Bluetooth: 4.1/BLE
  • Interfaces: Gigabit Ethernet, HDMI 2.0, Two USB 3.0 (Type A), Micro-USB 2.0
  • IR Receiver (compatible with Logitech Harmony)

Check out Nvidia Shield console official page HERE along with a cool video on it

HTC One M9

Share if the site was helpful

HTC One M9 Plus VR Powered by VALVE

Official-HTC-One-M9-renders-price-and-almost-full-specs-allegedly-leaked

HTC One M9

I am sure many of you have seen or even owned a M7 or M8 and know that it is one premium device made of a nice metal unibody build. The HTC One M9 isnt any different but this time HTC added a two tone look to it that i kind of like. The back still has the silver brushed metal but the edges have a nice looking gold metal shine. I think this just adds to the premium look and feel of the M9. Other big changes to note about the M9 is that HTC finally got rid of there back ultra pixel camera and now has a 20mp back camera which i think will be a very big improvement. For those of you that love the ultra pixels, you are also in luck since HTC just moved that camera to the front. Lets talk speed this bad boy will be rocking a Snapdragon 810 octa core CPU based on the 64-bit architecture. The M9 will also have 3GB of ram giving this new HTC device some real processing power and of course it will still have those amazing boomsound speakers we all love. I cant wait to get my hands on this device. make sure you subscribe to my youtube channel for full coverage of the M9 along with any hacking rooting and modding i will be doing on it.

htc_one_m9_2_render

Here is HTC’s official page for the HTC One M9.

 Basic Specs

  • CPU Speed

    • Qualcomm® Snapdragon™ 810, octa core
    • 64-bit, 4 x 2.0GHz + 4 x 1.5GHz
  • Memory1

    • ROM: 32GB / RAM: 3GB
    • Extended memory: microSD™ up to 128 GB
  • Camera

    • Main camera: 20MP with sapphire cover lens, auto-focus, BSI sensor, f/2.2, 27.8mm lens, 4K video recording
    • Front camera: HTC UltraPixel™, BSI sensor, f/2.0, 26.8mm lens, 1080p video recording
  • Display

    5.0 inch, Full HD 1080p

  • Sound

    HTC BoomSound™ with Dolby Audio™

  • Battery3

    • Capacity: 2840 mAh
    • Talk time: Up to 25.4 hours for 2G/ 21.7 hours for 3G
    • Standby time: Up to 391 hours for 2G/ 402hours for 3G

HTC VR powered by VALVE

htc-vive-pr-630

 

Here is a picture of the New HTC VR that is in developement. check out the official site HERE

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.

Xposed Framework Lollipop

Share if the site was helpful

Xposed Framework Lollipop Alpha

nexusae0_ic_launcher_thumb

NOTE: That this is still an alpha version and for Lollipop on ARMv7+ devices only. Please install it only if you’re willing to take the risk of boot loops. Just because it’s working fine and stable for me doesn’t mean it will work for everyone the same way. If this brakes your device you may have to flash the firmware to fix it make sure you know how to do that before installing.

How to Check out ARM Version and see if it is 7 or above

  1. Install Android Terminal Emulator  app on your device and open it
  2. Type the followng: getprop ro.product.cpu.abi  OR getprop ro.product.cpu.abi2
  3. It will return with your Arm Version. see picture below

Screenshot terminal

Downloads: Get all files need HERE
xposed-arm-20150213b.zip: Must be flashed with a custom recovery to install the framework.
XposedInstaller_3.0-alpha1.apk: Must be installed to manage installed modules.

Screenshot_2015-02-15-16-20-11Screenshot_2015-02-15-16-20-16Screenshot_2015-02-15-16-20-22

Known issues:
– It seems to boot loop on Samsung stock ROMs. I have received a file which I can use to analyse this issue, but it might take some time.
Update: There’s a difference in the format of *.oat files on Samsung ROMs. I’m trying to find out more

– If everything is working fine, but the app_process version is not displayed, it’s just a display error that can be ignored (will be fixed later).

– Nexus 6 only works if you set selinux to permissive and soft reboot from within the xposed framework app. you can us this Google Play app to change the selinux to permissive.

XDA XPOSED FRAMEWORK OFFICIAL THREAD

Sony Firmware Restore

Share if the site was helpful

Sony Firmware Restore

Today we will be talking about using FlashTool-0.9.18.4 to restore your Sony android device to stock firmware also to unbrick your device if needed.

Flashing Firmware with Flash Tool Requirements

1. Sony phone or tablet

2. USB cable to connect device to your computer

3. Sony Drivers downloaded and installed

4. Download FlashTool-0.9.18.4 and install

5. Some time. I would plan on 1 hour depending on your internet speeds of course.

Instructions

1. Open FlashTool-0.9.18.4

Flashtool start

2. click on devices then check updates scoll through the options and pick your device family

pick device

3. look thought this next list for your model. If you right click on branding you can check release and it will show you the version

model 2

4. once you have the version you want then click that file and it will download

downloading firmware

5. After downloading and extract the firmware along with some decryption you will see this page

extracted firmware

6. select all files and click arrow moving them all to the other side like the picture below then click create. once the FTF restore file is created you can flash it.

create firmware button

7. click flash button on the tool that looks like a Lightning bolt. then choose Flashmode. pick your newly pulled firmware from the list and click the flash button.

flash firmware

8. the flash tool will tell you to unplug your device and plug it back in while you are holding the volume down button. keep holding volume down until the flash starts. once 100% the device will reboot it self or you can unplug and manually boot it back up and you will be restored and unbricked. NOTE: if you dont want to wipe out your apps and data uncheck the wipe section boxs.

 

Will add to this post as i learn more.

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.