Magisk Systemless Root Manager

Share if the site was helpful

In the wake of Chainfire selling SuperSU, Magisk has stepped in to fill the void. The best part about it is that this new root management solution is open source which SuperSU was lacking. The good part about this tool is that the root manager does still work with supersu, if you have already rooted with it. So if you just want to check out Magisk just go ahead and install it on your Supersu rooted device. Magisk is systemless root only which is nice for those of use that still want to use Android Pay or any other apps that check for root access on the device. Also because it doesn’t change anything on the system partition you can still take OTA updates without any problems. Just follow these directions below and you to can install it on your device as long as you have TWRP available for your device.

Installation Instructions
Before Magisk installs anything on your device, please note that magisk will create a boot image backup in /data/stock_boot_<sha1>.img.gz
If anything goes wrong (e.g. bootloop), you can either use the uninstaller (recommended) or decompress the backup and manually restore your boot image
It should ALWAYS bring your device back to life (supposing you have a custom recovery that can decrypt your /data)

If you’re already rooted with MagiskSU or Latest Official Systemless SuperSU

If you’re not rooted, or something went wrong and you need a clean start

  • (Recommended) Restore your boot image back to stock (flash uninstaller if Magisk is previously installed)
  • Download the latest Magisk zip file
  • Reboot to a custom recovery
  • If you choose to use SuperSU (only support Android 6.0+), flash SuperSU in systemless mode now
  • Flash Magisk zip
  • Reboot. Update the stub Magisk Manager to the latest from Play Store

Features

  • 100% fully open source and easy to build! 
  • Magic Mount:
    Allow you to do any system (vendor) modification without actually tampering the partitions.
  • MagiskSU: Open Source Root Solution
    Root your device with MagiskSU, based on phh’s Superuser, which is based on CM Superuser.
  • Magisk Manager:
    MagiskSU Root Management, Install / Upgrade Magisk in-app,
    Manage, Upgrade, Download, Install Magisk Modules within a few taps.
  • Magisk Hide:
    Hide Magisk from detection, including SafetyNet, which is used in Android Pay, Pokemon GO, Mario Run etc.
  • Resetprop:
    Allow you to do any modifications to system props (build.prop), including read-only props.
    It is also used for tricking the bootloader state, and (for Samsung) the KNOX state
  • Multiple Entry Points:
    Provide several entry points to developers, reliably pausing the boot process before everything is done.
    Include post-fs (cache) mode, which happens even earlier than data is mounted (used to replace Boot Animation etc.)
  • Standard Stuffs:
    Remove dm-verity, forceencrypt; includes a super complete busybox to guarantee consistent behaviour, and can also be toggled to be used universally.

Downloads

Latest Magisk
Latest Uninstaller (Support v1+)
Magisk Manager

If you have installed Magisk on your device please comment blow and let me know your thoughts.

Phonlab E-Campus Free Course

Share if the site was helpful

Phonlab E-Campus free Chromebook Support course

I have been working with Phonlab for many months now and we decided to bring everyone a FREE course on Chromebooks to help techs and repair shops trouble shoot and fix customer devices. If you want to get access to this FREE course just head over to Phonlab.Teachable.com and enroll. Once you enroll in the Chromebook Support course you will have access to all the lessons. We hope you enjoy them and if you find them handy you may want to check out Phonlab E-Campus where we cover smartphone repairs and security.

 

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

R1 HD Amazon Bootloader unlock

Share if the site was helpful

R1 HD Amazon Bootloader unlock

BOOTLOADER UNLOCK METHOD 1

Hi Guys thanks to a team effort the Amazon R1 HD has root access with SP Flash Tool and TWRP recovery image.
I went ahead with the help of jcase and unlocked the bootloader because i wanted full access.

What i did is put together this script that will walk you through the steps to unlocking your Amazon R1 HD bootloader.
Steps are simple you just download this script that i created and click on the batch file once you have extracted it to your desktop. Follow the script it will walk you through everything.
Note Root access is required to use the script and you can watch a video on how to root the device below. My Script as been updated to work on Linux Mac or Windows

Download Files Here
BLU-R1-HD-Amazon-Bootloader-Unlock.zip

How to unlock the bootloader video

How to root and install twrp recovery video

Here are the steps to check if your bootloader is unlocked since people are asking. With the device turned on and adb debugging working. Run these commands in terminal or command window
adb reboot bootloader
Once in fastboot mode run this command to check if unlocked.
fastboot getvar all
It will return yes for unlock and no for locked.

BOOTLOADER UNLOCK METHOD 2

Steps
1. Download SP-Flash-Tool-bootloader-unlock.zip
2. Extract the SP-Flash-Tool-bootloader-unlock.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_Unlock.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete which should take seconds you can unplug the device and reboot it. Congrats you can now unlock the bootloader like any normal device now.

WARNING UNLOCKING YOUR BOOTLOADER WILL WIPE DATA FACTORY RESET THE DEVICE
How to unlock the bootloader now that you have turned on this feature.
1. power off the device
2. holder volume up and power until you are at the boot menu with recovery fastboot and normal as options scroll with volume up to fastboot then press power button to select
3. once in fastboot mode you will need to option a command window on your computer and make sure you have your adb and fastboot files
4. cd to the folder with your adb and fastboot files then run these commands
5. to maks sure your devices are working correctly
fastboot devices
6. to unlock the bootloader
fastboot oem unlock
7. follow the directions on your device screen. once it is finished unlocking you can check it with
fastboot getvar all
8. Next to reboot the device use
fastboot reboot
thats it your bootloader is unlocked
Note: if you have twrp recovery install and unlock your bootloader with METHOD 2 the device will try and boot to recovery and wipe data which will fail because you and twrp installed.
The only way to fix this is to boot to fastboot mode and run this command
fastboot format userdata
then just reboot out of fastboot mode and the device will boot up.
fastboot reboot

Need help with these commands check out this video jump ahead to 6min 45sec to see commands above

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

100,000 Subscriber Thank You

Share if the site was helpful

100efault

100,000 Subscriber Thank You

After four years and over 750 YouTube video’s I have finally reached 100,000 Subscribes on my channel. 🙂 This has been an amazing journey to get to this point. I have learned so much along the way and have met so many awesome subscribes and viewers. I want to take this time to say a big thank to all of you, but especially to those that have been really close to me and have helped so much.  For starters,  Matt who taught me how to write batch scripts. I am sure many of you have used my SuperTools and loved them, you can all thank Matt for those. Also, Kenn for writing on this site and he is also the brains and person behind all of the device rebuild videos on this channel. I can’t forget Hendrix who helped me up my video and audio quality along the way and who made some awesome videos for the channel as well.  Episode Tuesday is another awesome guy who also writes for this site. This guy has some of the best posts around and very fun to read. This is just four of the hundreds of friends I have made in the Android community these last four years.

androiddev

I can’t forget all the awesome developers that have been able to work with like Hashcode, dhacker, beanstown, chainfire, Jared Rummler, Gatejunoir, des troy, Wug fresh, Jcase, just to name a few and the list goes on and on. These guys have been super awesome in teaming up with me to bring all of you some of the best and coolest android hack and mod videos tutorials around. 🙂 Thanks Android developers; without your dedication and hard work this channel wouldn’t exist.

I also have to thank those guys that were in my first Android community on XDA developers back in the day when I got my first Android device the Motorola Droid X2. John M. and Ash H. along with sd shadow.  They were my best buds and super helpful and awesome to hang with on XDA. I can forget to mention some other good friends like Alex, Sam, and Fred that I talk with almost every week, you guys are the best.

Here is the first youtube video I ever made. Its almost at 1,000,000 views by the way

Here is one of my latest. I think you can see the progression 🙂

Of course i can’t forget the youtubes that I hang with like Droidmodderx, bane tech, zedo maxx, wwjoshdew, qbking77. These guys inspire me and drive me to keep making better and better Android and tech content for all of you.

Last but not least I would like to thank my wife Jackie for putting up with all the time I spend researching and making these videos, without her support RootJunky.com wouldn’t exist at all. Thanks Babe. 🙂

Can’t wait to get another 100,000 subs and see who I meet along way. If you haven’t already Subscribed to my channel go do it now. CLICK HERE

RootJunky Out

Comments welcome

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

Marshmallow Headache

Share if the site was helpful

Marshmallow Headache

 

Google defines Hyperglycemia as:

A high blood sugar. An elevated level specifically of the sugar glucose in the blood.

The Mayo Clinic advised me that symptoms of hyperglycemia develop slowly over several days or weeks. The longer blood sugar levels stay high, the more serious the symptoms become. Early symptoms of hyperglycemia can be fatigue and Headache.  Fatigue and Headache!

So why are we discussing blood sugar levels? Why do i have fatigue and headache? Well I think that I may have a small case of hyperglycemia brought on by the sweet, sweet goodness of Marshmallow.  Please allow me to explain.

android-6.0-marshmallow

So a few weeks back I had no headaches and no regrets, but i wanted some more, something sweet.  At that point in time my trusty Nexus 5 was consuming a fruit and fiber diet of Cyanogen Mod 12.1.  There was also a sprinkling of Xposed modules to guarantee a well balanced diet.  Then Rootjunky (ohhh, such a fitting name to someone who deals in the drug of modifications), came along with his tempting video for rooting Android 6.0 Marshmallow.

I thought to myself, this is great, I will enjoy the sweetness of marshmallow along with root access. I decided to leave the bland taste of CM12.1 for Android 6.0 Marshmallow.  Afterall, there is s’more to love.  I honestly really like it.  My Nexus 5 seems smoother, and somehow more refined.   Battery life was never the N5’s strongest point so the doze feature on Marshmallow created battery drain as slow and sweet as molasses.  The honeyed improvements to the “do not disturbed feature” are greatly appreciated.  It is similar to what Lollipop had to offer, it has just been processed a little finer. I personally use this feature a lot at work and find it very handy.  Everything was so sugary. Even the new boot animation was like watching someone pulling multicolored taffy.

It was like saying “trick or treat”, when I held onto that home button to turn on, Google Now on Tap.  Each time I was blessed with a little treat.  Sure there were some instances where it do not provide me with anything.  I wish I could have thrown eggs at those time; like I would have at delinquent household, refusing to join in the Halloween candy giveaway.  Most of the time I was happy with the added functionality.  Using any app for the first time was sugared with permission checks.  Each time I consented to give access, I found the sweet taste of marshmallow was in the air.  

Sounds good so far, right?  Well this is when the gooey, softy, sugary sweetness of Marshmallow Android 6.0, started to cause fatigue and headache.  The first time I precieved Marshmallow was maybe too sweet for me, occurred when I noticed and new app from Chainfire call [root] LiveBoot.   Not sure how long this app has been around for but it was the first time that I noticed it.   I have been a big fan of his SuperSU and 500Firepaper apps so I knew that this would be worth the download.  I installed and tried to run the app but nothing……. It did not work with Marshmallow!  The new OS was simply too sweet and the LiveBoot app could not handle it.

White_Marshmallows

I should mention that sometime last week Chainfire brought the fibre.  He was like bowl of All-Bran; regulating sugar levels, as his update allowed the app to work with Marshmallow.  Not a moment too soon as far I am concerned. The app is really cool.  I have developed a habit of turning my phone off and booting it up in front of family and friends just to show off the app’s boot animation.  I let them think that I am some kind of supper moder who can read and understand the animation!

Turning my phone off and on made me notice another aspect of Marshmallow that was too sweet for my blood.  Powering the phone down only gave me one option – power off.  What happened to my enhanced menu with reboot options?  I know that with root access I can make that happen again but then I have to endure the bitter taste of finding just the right app to do that for me.  Before it was just there.

The sweetness of Marshmallow just became stronger as I stuck with it.  A new cyanogen theme was available for Halloween.  It looked really cool and guess what?  It does not work with Marshmallow, it is for Cyanogen.  For some reason with Marshmallow, Star War’s commander will not sync up with my Google play account?  I had a level 8 town hall, I am not going back to the beginning now!  All this Marshmallow sweetness and it is sweat, is giving me Hyperglycemia.  I have the symptoms, fatigue and headache.  Now what will I do?

First off, if I am honest it is really not that bad. There are apps that I can install to get back some of the functionality I had.  With Rootjunky’s help my Marshmallow is rooted so I have room to play.   I have also seen lots of hints that CM13 may not be too far off.  That is quite the accomplishment. I was not expecting anything before Christmas but looks like the Cyanogen crowd are working hard.

I guess I was like a kid during Halloween with Marshmallow candies.  I don’t not think of the consequences, I saw something sweet and went for it.  Now I am suffering with a sugar headache but you know what?  I will do it all over again next year.

By

E. Tuesday

 

 

P.S.

Have you ever installed something sweet and regretted it later?  Tell me about it in comments area.

 

P.P.S.

So while playing with Marshmallow and writing this article a few ideas came to mind.  Would you like to see a post about comparing stock Marshmallow to CM12.1 or CM13 when it arrives?  I am thinking of comparing two identical phones, one with stock and the other with a custom ROM (Maybe even kernal).  We could look at benchmark programs for performance and battery life.  We can also do some real world tests to see what if any difference there is.  What do you think leave me some encouragement below if you would like to see a post like this.