Showing posts with label easy. Show all posts
Showing posts with label easy. Show all posts

Thursday, 15 October 2015

Easy to follow Root Steps for Stock Android 6.0?



Hi Everyone

I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.

Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?

Thanks in advance!



Sunday, 11 October 2015

Is the windows 10 upgrade easy or should I keep waiting for windows 10 stock



I ordered a windows 10 version of this tablet over 3 weeks ago and it just isn't coming in stock where I ordered it but I see that they do have a windows 8.1 version in stock. From what I have seen upgrading to windows 10 doesn't look like a lot of fun. Can you comment on your experience and if you think I should just keep waiting for one with windows 10 already installed to come into stock.



[GUIDE] [Easy Method 100% Working) Replace Kinguser Or Kingroot With SuperSU



Personal Experience

I Rooted My Samsung Galaxy Grand Via Kingroot v.3.3.1.apk but the problem is that Sometimes Kinguser Doesn't Grant Permission to the Apps, Also Very Irritating
Many Apps Requires SuperSu Support.So I had Done this Method


Method :
Note : Custom Recovery Must Be Installed (CWM or TWRP)
Before Proceeding This Method

1)Open Kinguser App
2)Go In Kinguser Settings And Remove Root Permission
3)Use Any File Manager And Create A Zip File e.g.SuperSu.apk to SuperSu.zip And. Put It In Your External SD Card
3)Now Go Into In Recovery By Vol Up+Home+Power Key
4)Now Flash The Zip File (Install zip from Sd Card And Select From SdCard1 SuperSu.zip) It Show An Error Because It Is User Created Zip
5)Before Flashing It Shows Your Phone Is Not Rooted "Root Now"
6)Select Yes
7)Now Reboot Your Phone
8)Install SuperSU.apk Normally
9)Open SuperSU And Install Su Binary Normally
10)Go In SuperSu Settings And Install SuperSU in System
11)Reboot Your Device
12)Congrats,You have Replaced Kinguser With SuperSU

Download The Latest Version Of SuperSU.apk

Hit,Thanks If This Method Works For You



Saturday, 10 October 2015

[APP][4.0+][Material] Easy Lock - Double tap status bar/nav bar to sleep



Easy Lock
Double tap status bar/nav bar/lockscreen/notification shade to quickly put your device to sleep!
App icon
  • Especially useful in devices where power button is hard to reach

  • Often faster and easier than using the power button

  • Reduce the wear and tear of power button :)

_
Requirements
  • Android 4.0 (ICS) or higher

  • NO root required


_
Screenshots

_
Downloads
Get it on Google Play

All features of the app are available for free, without any ads. If this app has been helpful, there's an option to donate via an in-app purchase. This does NOT unlock any new features. Thank you for your support. :)

Please do not mirror without permission. Link to this thread or play store page if you want to share this app elsewhere. So that users will know where to check for updates and get support from.

Please note: Hopefully it won't come to this, but just in case, to uninstall the app, you'll have to deactivate device admin permission first (Settings -> Security -> Device Admin -> Easy Lock).

_
Permissions explained
  • Admin permission is required to turn of the screen and put the phone to sleep

  • Lollipop smart lock is not supported by Device Admin. It's an Android system limitation. However, smart lock is supported by Easy Lock if you have root access. If you see a prompt for root access, this is what that's for.

  • Draw over other apps permission is required to detect double taps.

  • App Usage Statistics (in Lollipop and above) is required if you enable the option 'Try to avoid soft key presses'. This permission will be requested only if you enable this option.

_
Source code
Source code is distributed under Apache v2 license. Source repository: https://github.com/aravindsagar/EasyLock

_
Developed by
Aravind Sagar
Find me in G+



Thursday, 8 October 2015

Is the graphite color more easy to scratch? (versus other color)



I dont know if my question is ask correctly (i'm french), but will it be easier to scratch the graphite color versur the frost/silver. Do we know what's the aluminium quality?



Wednesday, 7 October 2015

Galaxy S6, S6 Edge(+) Missing menu button SOLVED! (well an easy work around) =)



Here is the temp fix guys the problem is a lot of apps detect if there is a hardware menu button and omit showing the soft 3 dot button common in a lot of apps. The S5 has no dedicated menu button but it does have the long press home button option to launch the More options/Menu button, however out Galaxy S6 models do not have this option. BUT some apps still detect it and delete their in app button.

Here is the fix I figured out that works in this situation and it would be good to pass this on or write up a document.

Go to phone settings => Accessibility => Dexterity and interaction => Assistant Menu.

At the top right slide the off button to on to enable the Assistant menu icon on all screens. Then click on the Edit option. In the edit menu deselect all the buttons you do not need by hitting the red negative on the icons (-) in the upper part of the screen. (note it has two buttons that you cannot remove Home Screen, and Menu Settings) on the bottom half of the page hit the green plus sign (+) on the More Options button (It has 3 dots). (note there are lots of other buttons you can add)

Now on all screens is a little round button with 4 dots on it, it appears on all screens in all programs and is floating. There is the More options button now which is the software menu button we are missing =). You can just go back and disable Assistant menu afterward or like me leave this handy button on because I have multiple programs that do this.

Hope this helps guys Cheers! :good:



How To Disable Force Encryption - Nexus 6 - FED-Patcher v7 [ 7 Oct 15 ] (Easy)



I seen a lot of Discussion On this topic, and found a really simple way to disable Forced Encryption and it also removes the warning at boot. This in NO WAY is my work at all. I am sharing this [FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher) which was posted by @gladiac. Absolutely make sure you head over to his forum and hit the Thanks button. This works great


Preparation


1. Download fed_patcher_v7-signed.zip and check here to verify the latest version
2. Download [BETA][2015.10.06] SuperSU v2.50 by @Chainfire
3. Download Whatever ROM you are going to use. I am currently running [ROM]【6.0】LightROM - Marshmallow【MRA58K】- Oct 7c



Instructions

1. Backup your SD Card, during this process, everything will be erased during the process
2. Reboot into TWRP, this is important that you actually have TWRP
3. Perform a Full Wipe by doing the following:

  1. Press Wipe

  2. Press Advanced

  3. Click every check Box

  4. Wipe 3x for good measure

  5. Press Home button

  6. Press Wipe

  7. Press Format Data

  8. Type yes in the box to perform the format

  9. Perform this 3x for a good full wipe

4. Unplug your usb cable and plug it back in
5. On the computer, open My computer
6. Navigate to and open the Nexus 6 Drive
7. Drag the Zip files to your Phone - 1) fed_patcher_v7-signed.zip, 2) BETA-SuperSU-v2.50.zip, 3) ROM Zip
8. Flash your ROM 1st (DO NOT BOOT AFTER FLASHING)
9. Wipe Dalvick Cache/Cache 3x
10. Flash fed_patcher_v7-signed.zip
11. Wipe Dalvick Cache/Cache 3x
12. Flash BETA-SuperSU-v2.50.zip
13. Reboot and Enjoy with no more red error sign during boot and no encryption


Supported Devices
  • Motorola Nexus 6 (shamu)




Version History
  • v1 - Initial version with HTC Nexus 9 WiFi (flounder) support

  • v2 - Added Motorola Nexus 6 (shamu) support

  • v3 - Added support for HTC Nexus 9 LTE (flounder_lte)

  • v4 - Added support for signed boot-images

  • v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.

  • v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.

  • v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.



What Do I need To Make This Work?
  • A supported device (Your nexus 6)

  • An unlocked bootloader

  • An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)

  • A recovery that includes busybox (TWRP, CWM)


How Do I Use it?
  • Follow Instructions above - This is the basic need to know information

  • Make a thorough, conservative backup of your data if there is any on your device

  • Go into your recovery (TWRP, CWM)

  • Flash fed_patcher-signed.zip

  • If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.



IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.

Is It Dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.

All Thanks To:
  • @gladiac - For Putting the OP together for the Nexus 9 and sharing this

  • @rovo89 - for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.

  • @pbatard - for making (un)mkbootimg (dunno if he is on xda)




Does this mean root on Marshallow will not be as easy as ADB?



http://www.xda-developers.com/a-look...complications/

I just read this and the part that stuck out the most to me was this.

"If you want root today, on Android Marshmallow (6.0), you’re going to need to use a modified boot image."

Does this have anyone else concerned? I was excited to get back into the Nexus game so I could power on my new 6P and be rooted 10 minutes later.



Tuesday, 6 October 2015

[Guide] Flash 6.0, root, and no-forceencrypt from stock (easy method)



Hope this helps.

1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2. Download latest stock image for Nexus 9 from google: https://developers.google.com/androi...s/images?hl=en
3. Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nexu...overy-t2944788
4. Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a. I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexu...alpha-t2931657
b. A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexu...t3218290/page3
5. Download the latest supersu files: https://download.chainfire.eu/696/SuperSU
6. Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7. Unzip the 6.0 stock image into a folder and open a command window in the folder.
8. Type the following:
a. adb reboot bootloader, wait until nexus boots into bootloader
b. fastboot oem unlock
c. flash-all, now wait a few minutes while the stock image flashes
9. At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a. adb reboot bootloader, wait until nexus boots into bootloader
b. flashboot flash recover twrp.img (or whatever the image filename is from the twrp download).
10. Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11. Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12. Now type adb push <supersufilename.zip> /sdcard/<supersufilename.zip>, make sure you’re typing from the correct directory.
13. Install supersu via the install menu on TWRP.
14. You now need to install a kernel with the no-forceencrypt flag set:
a. If you want to install a custom kernel (like elementalx), type adb push <customkernelname.zip> /sdcard/<customkernelname.zip>, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b. If you want to install the modified stock boot.img then boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step.
Reboot and you’re good to go.