Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
View 5 RepliesWith root/unlocking, the finger print sensor will be somehow disabled?
View 2 Replies View RelatedIf I was to unlock my bootloader and root my phone, should I still grab ota updates?
View 4 Replies View RelatedI used Wugfresh nexus root toolkit and went through the unlocking and root process. It unlocked fine, went through the reboot process. Then when I selected root and recovery I got to TWRP, swiped to apply the zips, it rebooted and never got back into system. Now it just hangs on the google logo. I can get into bootloader and stock recovery still as I attempted to reflash stock through the toolkit.
View 10 Replies View RelatedWill rooting my nexus 5 without unlocking the boot-loader void my t mobile warranty? My Phone is an LG Nexus 5 running the latest Version of lollipop and the only reason i want to root it is to be able to connect my ps3 controller to it and play emulators or minecraft...
View 1 Replies View RelatedTo unlock the bootloader in order to root the Nexus 6?
I don't really care about custom ROMs, but there are a few root apps I would like to use.
For example, I'd like to enable touch to wake. That would make the phone perfect for me.
But I just do not want to brick the phone.
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
I came from getting my nexus 6P and I wanted to install twrp and etc... So I went to into developer mode, I check USB debugging and enable OEM unlock.
I head to my computer open a commend prompt that's has the fastboot and adb drivers. I connected my nexus 6p and I enter the following commends
Adb reboot bootloader
Fastboot devices
(Showed me my devices)
Fastboot OEM unlock
And just after I hit that I got the following
...
Failed ( remote : commend not found)
Finish 0.18
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
[Code] ....
Message shown :
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
[Code] .....
Ok, so I just got my awesome new 6P. Here's what I've got so far:
I have the SDK, ADB and Fastboot components installed, drivers listed, and everything like I've been reading here and other forums.
So far I've been able to verify that ADB and Fastboot both seem to see my device OK so I know the drivers are good.
USB debugging mode is enabled in the Developer menu, and the option for 'allow oem unlocking' is enabled as well.
From what I'm seeing this all adds up to 'should work', but it isn't.
I originally tried the 'fastboot oem unlock' command found in older posts, and when that didn't work found (from what I'm able to determine) the latest command of 'fastboot flashing unlock'. Unfortunately, all this gets me is this: [URL] ..... (wont let me just link the image since I just had to make a new account. Been too long since I last logged in apparently ...
So I think I know the answer but wanted to validate. If I leave the bootloader locked on my device and download a factory image from Google, cannot I just put the zip on the sdcard storage and run it through recovery to update? I don't think that I need to unlock the bootloader do I? I am trying to keep everything stock for now, but updates are a big reason I wanted this phone. Also don't want to break Android Pay.
View 4 Replies View RelatedIs there a way to remove the warning on boot, after the bootloader has been unlocked.
View 8 Replies View RelatedI haven't received mine yet, but probably one of the first things to do is unlock the bootloader. Does the fingerprint verification/ unlock still works with an unlocked bootloader.
View 2 Replies View RelatedI am already unlocked and rooted, but I would like to relock the bootloader assuming that I can unlock it for future updates without losing data. The Nexus 5 had a boot locker app in the App Store which allowed this, but I do not find an option for the 6 P.
View 2 Replies View RelatedAfter i unlocked my bootloader and rooted my phone, everytime i boot up my phone i have this msg and then the phone start, how do i get rid of this msg?
View 10 Replies View RelatedI noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main:
finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Cannot seem to flash factory image from Google. Trying to do it via adb but cannot push onto device. Says "cannot open no such file or directory". What can I try?
View 7 Replies View RelatedLast year I bought the nexus 6 and for the first time (I've had a lot of android phones) in my phone was also disabled force encryption after the bootloader unlock, twrp and root. So I decided to decrypt it because reading on the nexus 6 forum some devs suggested this to increase the phone performances.
I read that now twrp supports encryption and that Google increased the phone performance also with force encryption enabled.
Is it possible to unlock bootloader, root, flash twrp and somehow flash the stock rom? If yes, where can I get the rom files for flashing with twrp?
View 9 Replies View RelatedThe Volume Down button is jammed (the phone fell and landed on its edge slightly crushing the frame where the volume down is). Curiously the Volume Up button still increased the volume.
After turning the phone off the problem came when turning on the phone as it now only boots into the bootloader as a result of the jammed Volume Down button. Once in bootloader mode, the volume up/down buttons do not change the reboot options - it appears the stuck Volume Down button is causing this.
The way to fix this is to take the phone apart (as per the Youtube clips) and physically straighten the frame. This is no easy task, so the question: is there a way around this so that the phone can boot?It's rooted and fastboot commands work. (I installed TWRP but can only boot to recovery with adb).
If I root phone would I still get update over OTA or when I root it I can put recovery and flash it trough there?
View 4 Replies View RelatedAs the title states, what is a system less root ? This is my first nexus so I'm getting used to the mods, ROMs and bits n bobs.
View 10 Replies View RelatedI noticed that recently in "Battery"'s "History details", "Awake" is pretty much solid all the time( I do _NOT_ have "root", How should I go about finding which app is keeping my phone awake? I did not install any new apps recently, however I do update my apps all the time..
View 10 Replies View RelatedI have been using an app called adguard on my un rooted phone. Exploring other adblocking apps....
View 1 Replies View RelatedI know saw a rom that already had systemless root in it but I can't find it now.
View 3 Replies View RelatedIs this possible?
View 7 Replies View RelatedI know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
So I'm rooted on stock 2.66 what's the modifications I could make to enable it?
View 10 Replies View RelatedWould it be possible to root my phone and just use Adblock to modify my hosts file and then unroot it? I'll obviously have to keep my bootloader unlocked. I'm just wondering if I'll have any issues with Android Pay and the monthly security updates. Can I take updates with a modified hosts file?
View 8 Replies View RelatedI'm having issues with DPI change, I used ADB to change the DPI using a simple adb shell wm density 460 && adb reboot, all good, only issue is a few things are.. weird.. For instance the "top apps" icon, little blue thinggy in the playstore is awkwardly big, it's larger then the font, but I didn't use the phone stock so I don't know if that's just how marshmallow is or if that's a dpi problem. I also noticed when loading The Sims FreePlay, the EA boot logo it extremely over scanned, the letters EA barely fit on the screen, the eBay app, the user display picture is cut off and only shows the bottom right corner on an icon that's huge and again over sized, as well as snapchat sending all of my snaps with extremely small font, yet on my screen before sending they look just fine.
So after looking into this further, the build.prop was never changed, it still says dpi 560, but I know for system files I need to mount /system in order to write to it without root. So I booted to recovery as that allows me write access to system, mounted system, says mounted /system at the bottom of the log, open adb, run adb devices, nothing comes up, it's not found, reboot phone, run adb devices, works fine. What's the deal? I can't get the 6p to work from recovery when mounting /system, it says it's mounted but on the computer end nothing is happening.
I also want to keep this phone as stock as possible, kind of a purist douche bag like that so I don't want to run TWRP, or at least I'm not committed to this DPI change being this important that I want a custom recovery.why I can't mount /system in the stock recovery? or rather, why I can mount it but why it's not working?
How to get back to stock rom with root n able to get OTA updates from google
View 4 Replies View Related