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 RepliesIs 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 RelatedIs there a way to remove the warning on boot, after the bootloader has been unlocked.
View 8 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 was trying to install a ROM and things got a bit messed up. I wiped system/cache/dalvik/data via TWRP. I then went to install the ROM but it failed due to only supporting hhz12h bootloader.
So now I'm kind of stuck. I can't update the bootloader because fastboot/ADB won't list the device in TWRP. Is there any way to launch an ADB server in TWRP so I can fastboot the bootloader? Doesn't look like there is.
If there's not: Is there a TWRP zip-install hhz12h bootloader I can use? Looked around, couldn't find one.
If not I'll have to try and find/flash the original image..but fastboot is not going to happen so I have to find a zip installable one that'll work with hhz12d bootloader...which hopefully is around. Otherwise I could install literally anything just to get an ADB server so I can fastboot the hhz12h bootloader in there.
I just got my second hand Nexus 6p and the bootloader came unlocked and TWRP is installed. The updates don't work when TWRP is installed so I want to go back to the stock recovery.
Build number: MMB29P
Android 6.0.1
January 2016 patch.
I was running Pure Nexus and decided I would install Chroma today. I made a full backup in recovery with TWRP. I then installed Chroma and Gapps. Upon booting it told me I needed to update my vendor image. I couldn't remember how I did that the last time so I decided to just go back to my Pure Nexus and restore it. When I tried I got this error: "E: Cannot restore System -- mounted read only". How to fix this so I can restore that backup? I've searched and didn't find a solution. Also, couldn't find exactly how to flash the update vendor.img. Should have written all this down when I did it back in November.
View 6 Replies View RelatedIm using twrp 2.8.7.2, can flash cm13 but when im trying to flash gapps i get error 64,I've tried all kind of gapps and nothing work, why???
View 2 Replies View RelatedI tried to create a backup with TWRP of PureNexus the 29M build with EX kernel and it has given me an error.
It says 'E:createTarFork() process ended with ERROR=255'
Why can I not create a backup? I really need to back it up!!!!
I was rooted on 6.0 and wanted to keep my user data, so I downloaded the 6.0.1 factory image and individually flashed the different pieces with Fast boot.
I also updated to the latest TWRP.
My phone now boots to 6.0.1 and works normally, but when I go into recovery TWRP can't access the internal SD card and just shows 0 bytes, so I can't reflash SuperSU.
After manually flashing files to upgrade to 6.0.1, I flashed TWRP 2.8.7.0. But I am not able to flash supersu from sdcard because when I browse to the folder, it looks empty. Why this is happening?
View 3 Replies View RelatedI unlocked my bootloader, flashed Chainfire's systemless boot.img, flashed TWRP twrp-2.8.7.1-angler.img and when I took into recovery TWRP is asking me for a password to decrypt. I don't remember setting a password and don't know if there is a default one.
View 10 Replies View RelatedI can't seem to find my way to FULLY wipe when I want to flash or try a new ROM. I just installed an RRO that resulted in SystemUI crash, I then went to reflash the ROM, same results. Decided to WIPE in TWRP and reflash the rom, the SystemUI FC is still there ! Wipe, Flash ROM, then Wipe, same result... What's wrong with my TWRP ? I am on the latest. I just restored an old backup, and I have the same FC of system UI !
View 2 Replies View RelatedI'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] .....
I'm running the latest TWRP 3.0.0.0. I noticed when taking a backup, and it asks which partitions I'd like to back up, I notice a couple new ones I've not seen before. System image, vendor image, right below, system, and vendor. I notice the "image" partitions are slightly larger than regular system and vendor. What are these, and should they be included in a regular backup?
View 2 Replies View RelatedOn Chainfire's thread there is a link to a boot image for the MDB08K build of our phones, but nothing else. I personally have build number MDB08L and when I tried rooting the phone and flashing TWRP, I became stuck in a bootloop that I was eventually able to recover from. That was using the stock boot image for the MDB08L build number from Google's site.
My question simply is, how can we root any version other than the MDB08K build because we don't have a modified boot image of any other build.
I tried to update my phone to the latest version. I hit install from the notification, my phone reboots goes into TWRP recovery.... does nothing, then I have to "reboot into system" and then the phone boots up like normal. Without updating to 6.0.1.
View 4 Replies View RelatedFastboot recognizes my device, gives me confirmation of flash, but the device itself is not registering the commands and is stuck on "Connect USB Data Cable". I don't have my OEM cable and am using the iOrange-E C-A cable. I've tried different USB ports, restarting, etc.
fastboot says that the flash is successful, but the device never takes.
As the title states, I flashed the lastest Cataclysm (stable) and ElementalX kernel(also TWRP asked me that SuperSU wasn't present and to flash it so I did, that might've messed it up), phone booted up fine and set my fingerprint password and everything. I decided to reboot my phone and the phone encrypted itself and now the ROM is force closing and I can't do anything. It asks for a password every time the recovery starts up (I tried default_password, no go) and TWRP won't let me decrypt.
So my question is, is there a way to decrypt without erasing userdata? Would really like to keep my internal storage. I have lots of important pictures and files.
Having issue with TWRP not erasing/flashing roms properly..I have a dark theme installed Domination Theme with the extras (MMS, contacts, etc) and i did a very clean install, normally I go Wipe > Advanced and select all partitions and format it.After flashing another rom, I noticed some parts are still dark themed like the MMS, Google search bar, contacts, etc
View 3 Replies View RelatedI saw the cm website had a new cm13 nightly for angler, so I decided to try it out, so I downloaded it and gapps, and rebooted into twrp, then I wiped everything besides for internal storage and then I proceeded to Install cm, it took a few minutes, and then when it was done I rebooted. The first sign of something weird was that after the regular your device can't be checked for corruption message it went black and then said that my device is corrupt in red letters, then it started the cm boot animation, I waited about 5 minutes and nothing happened so I rebooted into recovery and it asked me for an encryption password...
My device was not previously encrypted and I didn't require a password to Install cm, so I tried wiping everything besides for internal storage, and then I was about to flash again, but non of my files were there so I had nothing to flash.... So I rebooted into my bootloader and fastbooted stock and now I'm on stock, but all my files and backups are gone. I guess that's why it's good to have an external sd, because that never got wiped by installing a rom before, and if I would have one, I would have all my pictures, music, and app backups. But now I have to start from scratch all because I tried a new build cyanogen mod
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 RelatedSo I flashed the latest firmware, after being unlocked, then rent back to bootloader, flashed recovery, went to recovery and installed file. Then restarted...now stuck in boot loop. It booted before I went to flash recovery in the new firmware just fine.
Do you need to flash something else when you flash recovery?
it says device is corrupt when I restart, but I was under the impression that screen comes up when bootloader is unlocked, so not sure if it means anything...
The title pretty much explains it. I just finished installing CM13 on my Nexus 6P, but realised I'd downloaded the wrong GApps, so booted up into CM13 (Worked fine) and then downloaded the newest GApps into internal storage (Which was NOT empty when I connected over USB to my PC) yet when I went to flash the new GApps, TWRP tells me that I have nothing in my internal storage folder. I'm confused as to how that could happen.
View 3 Replies View RelatedI forgot my unlock pattern and I don't have my device in ADM ... But the bootloader is unlocked, so I think I can install any image I want, right? Could this be a way to get into my device? So any solution to unlock my device without doing a hard reset?
View 5 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 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.
