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

Sony Xperia Bootloader Unlock Tutorial

Share if the site was helpful

Sony Xperia Bootloader Unlock Tutorial

unlockbootloader_phones

Sony just like many other manufacturers has there own Bootloader Unlock program.  This program is designed for Developers but can be used by anyone to get greater control over there Android device.  In most cases unlocking the bootloader on your Sony Xperia device will void the warranty. The best practice is to fully test the operation of your device before you unlock the bootloader. Most of the time when you unlock your bootloader it will wipe data factory reset the device so make sure you backup everything of importance before starting this process. Now that the WARNINGS are out of the way lets get into this tutorial.

Directions you will need to unlock the bootloader on your Sony Xperia device

Install the Android SDK or just the ADB and fastboot files extract the adb and fastboot files to a folder.

If you are on windows you may need the drivers for your device also and HERE is a great place to look for them

adb fastboot files

 

In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.

Tap Service info > Configuration > Rooting Status. Check if Bootloader unlock allowed says Yes. Also write down your IMEI from this screen.

Screenshot_2016-06-05-06-05-13Screenshot_2016-06-05-06-05-24

Now that you have your files setup and your IMEI number written down you can go to the SONY DEVELOPER UNLOCK BOOTLOADER SITE

Select your Sony Xperia device from the list at the bottom of the site and click continue.

On the next page you need to enter your email address so that Sony can verify that you arent a bot and sent you a link with your unlock code.

Open your email account and look for email from Sony with this in it. “You have requested to unlock the boot loader of your Xperia™ device. To verify this, click the following link: Click Here To Proceed”

Once the website loads up you will need to enter your IMEI number that you wrote down earlier or dail *#06# from the phone dailer to view your IMEI number.

IMEI2

Once you submit your IMEI you will get the rest of the directions to unlock the bootloader like below.

sony commands

Now that you have the full directions from Sony its time to unlock the bootloader on your Xperia device.

These direction will be for windows but it is basically the same for mac and linux.

  1. Turn on developer Options on your device and enable adb debugging. outlined in picture above.
  2. Open your adb and fastboot folder. Then with your mouse right click and select open a command window here. Alternative is to open command prompt and CD to the adb and fastboot folder.
  3. Now enter this command ( adb devices ) in the command window. you should have a popup on the phone to allow adb from this computer. allow it
  4. run command ( adb devices ) again this time you should see your serial number followed by the word device. if you get this far it means that your drivers and adb are working properly.  See picture below

adbsss

5.  From here lets reboot the device to bootloader mode with command ( adb reboot bootloader ) or follow sonys lead by powering off the device then press the Volume up button at the same time as you connect the other end of the USB-cable.  Either method will reboot the device to bootloader mode.

6.  Now run command ( fastboot devices ) again this will return with your device serial number and say fastboot after it.

fastbootssss

7.  Finally we can send the Unlock command that we got from Sony. Mine is ( fastboot -i 0x0fce oem unlock 0xE30FD3E75A61F33C ) but yours will very.

8.  look at your phone and follow any directions that come up on the screen and then thats it your done.

Once the process has fully finished then you can send command ( fastboot reboot ) to boot the device back up again. First boot up will take much longer then normal, it could take as long as 10 minutes to boot up.

Now that you have unlocked your bootloader you can easily install custom roms with cool hacks and mods. Root access and using root apps is in your near future. If you want to learn more about your sony device check out some of my video tutorials HERE

RootJunky Out

TWRP 3.0.0-0 Released with new features

Share if the site was helpful

TWRP 3.0.0-0 Released

Screenshot_1970-04-22-23-14-54Screenshot_1970-04-22-23-14-25Screenshot_1970-04-22-23-14-39

New features in TWRP 3.0.0-0:

  • Completely new theme – Much more modern and much nicer looking (by z31s1g)
  • True Terminal Emulator – Includes arrow keys, tab and tab completion, etc. (by _that)
  • Language translation – It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
  • Flashing of sparse images – On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
  • Adopted storage support for select devices – TWRP can now decrypt adopted storage partitions from Marshmallow
  • Reworked graphics to bring us more up to date with AOSP – includes support for adf and drm graphics (by Dees_Troy)
  • SuperSU prompt will no longer display if a Marshmallow ROM is installed
  • Update exfat, exfat fuse, dosfstools (by mdmower)
  • Update AOSP base to 6.0
  • A huge laundry list of other minor fixes and tweaks

WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new TWRP 3.0.0-0 for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

Team Win Recovery Project has been my favorite recovery ever since it was released. Dees_Troy and his team have done one amazing job at keeping up with this custom recovery and i am really thankful to them for all there hard work. If you love TWRP as much as i do please send then a little donation to say thanks 🙂

Donate to TWRP HERE

Going a quick search of the TWRP site it looks like there are already a bunch of official supported device that have builds of TWRP 3.0.0-0 available today and more to come soon i am sure, here are some of them.

Nexus 6P, Nexus 5X, Nexus 9, LG G4, Moto X Pure Edition, Moto G 2015, Galaxy Note 5. Many more are available these are just some of the mosts popular.

Click HERE to see if this new version of TWRP is available for your device.

 

Flashing ROMs like My Wife Drives.

Share if the site was helpful

The Connections Between Chris Lacy, Muggles and Flashing ROMs like My Wife Drives.

 

1412563521652

It may be hard to see how Chris Lacy is connected to my wife’s driving skills.  I can understand if you are confused, Chris comes from the land down under while my wife’s driving takes place in the Great White North.  Geographically Australia and Canada are rather far apart but if you throw in Muggles and some ROMs to flash it all starts to connect.  Let me explain.

For those that have read my posts before, know that I am a big fan of the RootJunky website.  I guess that is obvious as I always post on his site.  I also visit other tech site that interest me and I enjoy podcasts. One of my favourite podcasts is the blerg, from Chris Lacey .  I have been listening to his podcast for a few months now and I really enjoy it.  He does seem a little harsh toward OEMs, from time to time, but he does it without bias towards any operation system or equipment manufacturer.  I would call him “tech agnostic”, not sure what he would say about that but that is how he comes across to me.  He is an accomplished developer and if anyone is allowed to dish out some harsh criticisms from time to time, it is an accomplished developer.  Dursleys-from-Harry-Potter

Anyway, I have heard him use the term Muggles when referring to people like me, newbs or the uninitiated.  As many of you may know the term Muggle comes from the Harry Potter book series, a Muggle is a person who lacks any sort of magical ability and was not born into the magical world. Muggles also do not have any magical blood. That’s a quote from Google.  Chris uses it to reference those who lack any sort of programing ability and were not born into the computer world or do not have any magical programming blood.  In the Harry Potter books it is a derogatory term, that the privileged few have for their lesser.  I don’t think that Chris uses it in that negative way. I actually like the way he uses it and I think it fits.

I remember the feeling of magic that fell upon me when I followed that first XDA thread, allowing me to flash slimROM on my aging Samsung tablet.  Installing Odin on my PC was done during a new moon.  The recovery was flashed while I danced naked with the witches of Salem.  Booting up the new ROM for the first time I sprinkled the blood of a Unicorn across the screen for good measure.  Just like magic or maybe because of it…….. my tablet booted up and ran like a dream.  It still runs to this day and runs really well on slimROM.  This whole process is very magical to me, so the term Muggle fits.odin-header

Chris Lacy can call me a Muggle anytime and I am OK with that.  I have magical friends like RootJunky to help me out when things go wrong.  Youtube is filled with great videos and XDA is always there.  If you have a problem chances are RootJunky has a video about it or the solution is waiting for you at XDA.  If you follow their magical directions you will be able to work miracles.  This bring me to my wife’s driving.

My wife is a great driver.  She is confident behind the wheel and has a good sense of the road.  A few years back when we were looking for a new vehicle, it was obvious that she would have preferred a high end sports car; too bad that was not in our budget, I would have preferred that too.  Sadly the Corvette in the photo is not ours.  Cars that had stronger engines, stiffer suspension and steering that let you feel the road was where her choices gravitated.  It was really interesting to watch her go through the process of testing cars because I happen to be a mechanical wizard.  To me she is an automobile Muggle.  Someone that is unaware of the magic that lies under the hood. Now just because my wife is a automobile Muggle please don’t think she can’t drive.  She may not understand the difference between 2 stroke and 4 stroke engines or understand what is taking place when you shift gears, but put her behind the wheel and she more than competent, perhaps even talented.  That is exactly how a thought I flashed ROMs, more than competent, perhaps even talented.  That is what I thought but I am not so sure now.

To me, guys like the RootJunky are wizards, Chris Lacey is like a level 20 Magic user and Chainfire is from another dimension. It is funny how many people there are like me.  We flash a few ROMS and then think that we can take down governments with our hacking abilities.  I really have no idea of what I am doing half the time and this became apparent a few weeks back.  When modding my phone, I follow the road as my wife does when she drives but I don’t instinctively hit my apex in the corners.  I would love to tell you how I have become one of the few, someone capable of magic but really I am just good at following directions.  In that respect I guess my wife’s driving is much better than my flashing.  She at least has an inborn talent for understanding space and the car’s place in it.  I am just good at following directions.

My ability to follow direction and my lack of any really Android knowledge became very apparent about two weeks ago.  I wanted to give Cyanogen 13.0 a try but I wanted to try out the CAF variant.  This took a little bit of magic and I…….I am just a Muggle.  I did get CM 13.0 CAF running on my phone but my actual phone app was crashing on me all the time.  Not much of a smartphone if you can’t make phone calls.   After a number of wipes and reinstall things were not getting any better.  So I did what I do best, I followed directions on XDA.  I started from scratch and got my phone back to stock Android. Oh the defeat and shame that I felt.  

It was at this time of defeat that I listened to Chris Lacey’s podcast and heard him used the term muggles again.  That is when all the connections hit me: Chris Lacy, Muggles, flashing ROMs, my wife’s driving and this post was born.

My phone is currently running well with CM13.0, but not the CAF variant.  I have decided to stay away from that.   It was a tough week for this muggle as I struggled through my phone issues. It was a little disappointing realizing  that after a year or two of flashing ROMS I am still driving without really knowing what is happening under the hood. I may never be at the level of a developer but as I have fun in the world that XDA has shown me I will improve day by day.  

Who knows, one day I may be able to flash ROMs like my wife drives!

2uH9acf

By

Episode Tuesday

Amazon Fire 5th gen SuperTool

Share if the site was helpful

Amazon Fire 5th gen 7in tablet SuperTool

amazon fire 5th

NOTE This tool has been Tested and built for the Amazon Fire 5th gen 7in tablet. some features may work on other 5th gen tablets but use it at your own risk.
Features
WINDOWS VERSION
1. ADB driver install and test
2. Install Google play store plus remove ads on some fire os versions
3. block ota updates
4. boot device to twrp recovery 5.0.1 and below
5. Install FlashFire App
6. root amazon Fire 5th gen on android 5.3.1 and below
7. replace stock fire launcher with Nova launcher
8. remove lock screen ads on fire os 5.3.1 and below
9. Update SuperTool Files

Screen Shot 201

LINUX AND MAC VERSION
Install Google play store plus remove ads on some fire os versions
block ota updates
Install FlashFire App
root amazon Fire 5th gen on android 5.3.1 and below
replace stock fire launcher with Nova launcher
remove lock screen ads on fire os 5.3.1

New Version of SuperTool available as of 10-5-16

Link to Supertool HERE

video instructions HERE

Big thanks to all the devs that have put is some awesome work on this device.

 

please comment and let me know if it has any problems or if you have a feature you would like added

Thanks RootJunky

 

If you like this SuperTool then you should really check out some of my other Supertools batch scripts HERE

WileyFox

Share if the site was helpful

WileyFox The New CyanogenMod Phone

WileyFox is the name of a new OEM coming to town that will be offering two phones. Swift is the phone shown above and is there budget friendly model at just $200.00 US.  The Storm is there flagship devices at just $300.00 US. But the best part about this new WileyFox company is that these 2 phones will come with CyanogenMod 12.1 on them and will be supported by CM. This reminds me of the OnePlus one and i am really looking forward to checking out the WileyFox Swift for sure and maybe even the Storm. Now that you know CM is the OS you are probably wondering what are the specs on these Foxy phones. Scroll down. I dont see anything really grown breaking in these specs but for the price and the OS it should still be a interesting device.

storm-back

 

SWIFT

BODY Dimesions 141.15 x 71 x 9.37 mm Weight 135g Sim Dual SIM

DISPLAY Type HD, IPS, Full Lamination Size 5 inches Resolution 1280 x 720 pixels (~294ppi) Multi-touch Yes, 10 points, Glove mode Protection Corning® Gorilla® Glass 3

PLATFORM OS Cyanogen 12.1 Chipset Qualcomm® Snapdragon™ 410 8916 CPU 64-bit Quad-core 1.2GHz GPU Adreno™ 306

MEMORY Card slot Yes, expandable up to 32GB Internal 16GB ROM, 2GB RAM

CAMERA Primary 13MP AF Samsung S5K3M2 BSI, Dual LED Flash Features Face detection, touch focus, zero shutter lag, panorama, HDR, geo-tagging, auto exposure and antibanding customisation Video 1080p@60fps slow motion capture, high speed capture Secondary 5MP

SOUND Alert types Vibration, Multi-colored LED Notification Loudspeaker Yes 3.5mm jack Yes

COMMS WLAN Wi-Fi 802.11 b/g/n, 2.4GHz Wi-Fi Bluetooth v4, A2DP, BLE GPS Yes, with A-GPS, Radio Yes USB microUSB

BATTERY Removable 2500mAh battery Stand-by Up to 200 hrs Talk time Up to 10 hr (2G), up to 8 hr (3G)

MISC Sensors 3D G-Sensor, Proximity Sensor, Ambient Light Sensor, Gyroscope, E-Compass Color Sandstone Black

REGULATORY Certifications CE / ROHS / EAC / REACH /GMS NETWORK Technology GSM / HSPA / LTE 2G bands GSM 850 / 900 / 1800 / 1900 3G bands HSDPA 900 / 2100 4G bands LTE 800 / 1800 / 2600 Speed LTE CAT 4 up to 150mbps GPRS Yes EDGE Yes

 

STORM

BODY Dimesions 155.6 x 77.3 x9.2 mm Weight 155g Sim Dual SIM*

DISPLAY Type FHD, IPS, Full Lamination Size 5.5 inches Resolution 1920 x 1080 pixels (~400ppi) Multi-touch Yes, 5 points

PLATFORM OS Cyanogen 12.1 Chipset Qualcomm® Snapdragon™ 615 8939 CPU 64-bit Octa-core 1.5GHz GPU Adreno™ 405

MEMORY Card slot Yes, expandable up to 128GB* Internal 32GB ROM, 3GB RAM

CAMERA Primary 20MP AF Sony EXMOR IMX220 BSI, LED Flash Features Face detection, touch focus, zero shutter lag, panorama, HDR, geo-tagging, auto exposure and antibanding customisation Video 1080p@90fps slow motion capture, high speed capture Secondary 8MP, LED Flash

SOUND Alert types Vibration, Breath LED Notification Loudspeaker Yes 3.5mm jack Yes

COMMS WLAN Wi-Fi 802.11 b/g/n, 2.4GHz Wi-Fi Bluetooth v4, A2DP, BLE GPS Yes, with A-GPS, GLONASS Radio Yes USB microUSB

BATTERY Non-removable 2500mAh battery Stand-by (Information coming soon) Talk time (Information coming soon)

MISC Sensors 3D G-Sensor, Proximity Sensor, Ambient Light Sensor, Gyroscope, E-Compass Color Sandstone Black

REGULATORY Certifications CE / ROHS / EAC / REACH / GMS NETWORK Technology GSM / HSPA / LTE 2G bands GSM 850 / 900 / 1800 / 1900 3G bands HSDPA 900 / 2100 4G bands LTE 800 / 900 / 1800 / 2600 Speed LTE CAT 4 up to 150mbps GPRS Yes EDGE Yes

Slots: Dual SIM/Single SIM+MicroSD

Android Factory Reset Protection

Share if the site was helpful

Android Factory Reset Protection

What are the pros and cons of Android factory reset protection? This is a new feature that is included with Android version 5.1.1. First, I have to state that any security measures that can be added to your android device will only improve the safety of your personal data. That being said, you as the owner of the device, should also have the option and control to turn these features on and off as you choose. For example, unlocked bootloaders, carrier unlock, factory reset protection, and Write Protect to name just a few.

Pros

1. Device will not even boot to lock screen without the correct password. Kernel level password check.

2. Using Android device manager, you can remotely locate and/or wipe the data on your device.

3. If your device is lost, stolen, or wiped, only someone with your Google account or screen lock information can use the device.

 

Cons

1. Device protection is automatically turned on when you add a Google account and setup a lock screen password. I list this as a con because it is automatic.

2. If you have Factory Reset Protection turned on and you mess something up, it will not boot or you forgot your password, then you will also not be able to reset it in stock recovery. The only way to fix this is to use a tool like odin, rsd lite, fastboot, or lg flash tool to restore the factory firmware.

3. If you can’t provide your Google account information during the setup process, you won’t be able to use the device at all after factory reset.

 

Sprint put together a great little walk through explaining how to turn on and off Factory Reset Protection. HERE IS THE LINK

Another great read on this subject from Google  HERE

Important: If you reset your Google account password and need to do a factory reset, you need to wait 72 hours after changing your password to reset your device. This is for security purposes.  

 

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

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

Google Epic Failure

Share if the site was helpful

Google Epic Failure

epic fail

 

Google was supposed to have released the Android 5.0 Lollipop factory images for all the Nexus devices back on 11/3/14.  Well it’s been one week now and the factory images still haven’t been released.  I have heard that there is a battery bug that made Google stop the release. Come on Google you can figure out a little battery bug in one week. The Source code or AOSP has been release and developers are already releasing there own Lollipop roms based on AOSP which is really awesome. One of the reasons everybody buys a Nexus devices is to get the new Android version first, before everyone else. There have already been leaks of android 5.0 on the Moto X and LG G3 but for the Nexus line up, NOTHING. Google did release the factory firmware for the new Nexus 9 and Nexus player but not the Nexus 6 yet. Speaking of the Nexus 6 what a failure the preorder process was, the device went out of stock instantly and a week later is still out of stock. If you missed the 3 minute release from Gogole Play and the Motorola 1 hour release then you are out of luck at this time.  GOOGLES EPIC FAILURE

ON THAT NOTE GOOGLE GIVE ME MY FACTORY IMAGES NOW LOL

When the factory images / Firmware are released you will be able to get them HERE

 

Android 5.0 Lollipop Factory Images Delayed

lollipop