So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
You flash the images, then you flash TWRP, then you do a factory reset in TWRP, and install SuperSU (http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip), and then boot. You'll now have 4.4 Rooted.
binaryfalcon said:
So I just flash the factory image through fastboot, and the boot?
Flashing latest TWRP after that, which method is best to root afterwards? Thanks.
Click to expand...
Click to collapse
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
wickdc said:
How long does it take to flash the image-occam-krt16o.zip? I have been waiting for 20 minutes now. This is my output from the command window
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.076s]
writing 'bootloader'...
OKAY [ 0.298s]
finished. total time: 0.375s
Click to expand...
Click to collapse
You can run the flash all command, or you flash everything separately. Go to efrant's guide on how to do that here on xda. You have now flashed the bootloader succesfully, now you will have to flash the other images as well.
Sent from my Nexus 4 using xda app-developers app
why don't you install cwm/twrp first? it's a lot easier to flash in my opinion (not if you want to install the image from your computer)
but normally it just takes a few moments/minutes
Related
Hi,
I recently got a nexus 10, and started working on rooting. I have unlocked it, installed CWM recovery and booted it twice. I have not rooted it yet. Now I realized, that everytime I entered the CWM recovery mode, it automatically reboots back into recovery or normal boot in about 30 seconds or so. (this is not the main problem!)
But one booting up second time, I got a notification of sytem update for 4.2 jellybean (please note initially the device was on 4.2 JB JVP15P), I clicked on install, it booted into CWM recovery, but then it failed to continue with installation, as it complained about authentication failure for the zip fle or something of that sort. So I chose to boot the device without installing the update, now it entered a boot loop. I have tried erasing cache and userdata (both using fastboot commandline, and options in the CWM - in the 30 secs I get). It did not work.
After trying it for a few times, I tried restoring some backups I had made. Initially it complained about MD5 mismatch, and then later on it complained about unable to mount cache/* and unable to mount sdcard.
I have read around and the universal solution seems to be to restore stock images. Is that the solution for me as well?
Any help would be greatly appreciated, and I am noob in this area, so pardon me if I act like one.
cheers,
brickin
I'd like to know part of the answer to this as well. The tab is running fine and TWRP works fine, but CWM constantly reboots and I have the same mounting problems within both CWM and TWRP. I've tried flashing stock image and recovery but it's made no difference.
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
I was having a similar issue with cwm. This explains everything.
Blueback22 said:
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
brickin said:
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
Click to expand...
Click to collapse
If I were you, I would use WugFresh's toolkit to flash back to stock. Then I'd flash TWRP and start from scratch.
I don't know if TWRP will fix your issue all together, but I do remember hearing that there's an issue with CWM on the N10 right now.
Your CWM backups won't work on TWRP IIRC.
Here is where you can get stock images:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using Tapatalk 2
Hi Blueback22,
Thanks for the help. I was able to fix the problem.
Here are the questions I had and the answers I found, please correct me if I am wrong.
1. My JB version is JVP15P, is it ok to flash JOP40C stock recovery image?
ans: yes
2. Does TWRP work perfectly with nexus 10?
ans: Atleast in my case it did, I was able to root my device, and was also able to take backups.
3. a. CWM complains E: Can't mound /sdcard !
b. CWM Keeps restarting within 30 secs or so !
c. My device is stuck in bootloop !
ans: First, try to wipe your cache, and userdata and reboot. If it does not solve, then flash stock factory image for your device and flash TWRP recovery image.
4. CWM complains E: can't mount /cache/*
ans: Wipe your cache, userdata and reboot.
Reiterating blueback22's point:
DO NOT USE CWM WITH NEXUS 10. USE TWRP INSTEAD.
Cheers,
brickin
BRICKED: OLd bootloader version wont update
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
ginsboon said:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Can you get into the boot loader and flash TWRP to see if that fixes it?
Sent from my Galaxy Nexus using Tapatalk 2
ginsboon said:
returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time. After going to the latest, cwm has been stable. No more random reboots.
Link to download the latest version...
http://www.clockworkmod.com/rommanager
cowabunga said:
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time.
I tried to flash cwm 6.0.2.3 and twrp but failed. Still searching for some clues.
Click to expand...
Click to collapse
For OP and other N10 users with stock 4.2 JB Build JVP15P experience:
Is it possible to use the available toolkits (Wug's or mskip's) to unlock the bootloader and root a N10 with the configuration above? Both toolkits ask for Build JOP40C. I've searched the developer forum for this build and found nothing. Thanks!
I am depressing now. I have been doing a lot of googling in the past few days, but all I found doesn't work for me.
I have formatted everything in my nexus 7 using clockworkmod recovery by accident, and I don't have access to it by using USB or OTG cable. I have tried Adb, found drivers from different tutorials (they are the same driver), but when I try the command adb devices, it seems my computer is not recognizing it. then I tried again with another computer, Don't work either. The problem maybe is that I can't Enable usb debugging on my device, since the android system has been formatted by me.
What else can I try at this point? thank you in advance!!!
so I can't get into ADB because I can't change my bricked device to USB debugging mode. is this mean, I can't do anything else to fix it??
thank you for the fast reply.....
I saw someone mentioned Nexus Root Toolkit, and tried it, can't get into adb..but fastboot shows my device....but I can't flash anything into my device without adb
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot.exe flash recovery cm-10.1.2-grouper.zip
sending 'recovery' (159175 KB)...
OKAY [ 21.062s]
writing 'recovery'...
FAILED (remote: (InvalidSize))
finished. total time: 21.111s
fastboot flash recovery recovery.img (where recovery.img is the name of the recovery file that you have downloaded, either TWRP or CWM).
That last command was invalid.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
You can also try downloading the factory image and flash it via fastboot.
sgt. meow said:
fastboot flash recovery recovery.img (where recovery.img is the name of the recovery file that you have downloaded, either TWRP or CWM).
That last command was invalid.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
You can also try downloading the factory image and flash it via fastboot.
Click to expand...
Click to collapse
thank you.. I have CWM before....after do that, CWM is gone. I have that figured out....but even with CWM, I can't do much.
C:\an>fastboot.exe flash recovery openrecovery-twrp-2.4.1.0-jewel.img
sending 'recovery' (7936 KB)...
OKAY [ 1.068s]
writing 'recovery'...
OKAY [ 0.502s]
finished. total time: 1.574s
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.106s]
finished. total time: 0.108s
C:\an>fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
sending 'recovery' (7964 KB)...
OKAY [ 1.069s]
writing 'recovery'...
OKAY [ 0.506s]
finished. total time: 1.578s
C:\an>fastboot.exe devices
C:\an>fastboot.exe devices
015d24bc5c0ff218 fastboot
C:\an>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.106s]
finished. total time: 0.108s
C:\an>fastboot.exe flash recovery openrecovery-twrp-2.6.3.1-grouper.img
sending 'recovery' (7766 KB)...
OKAY [ 1.034s]
writing 'recovery'...
OKAY [ 0.514s]
finished. total time: 1.551s
I did it. I got TWRP installed, and is able to see my using OTG USB, and saw my backup file, but my backup file is made using CWM. will it works??
megapig said:
thank you.. I have CWM before....after do that, CWM is gone. I have that figured out....but even with CWM, I can't do much.
Click to expand...
Click to collapse
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
sgt. meow said:
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I can't use adb in cwm. I have tried, and CWM can't mount OTG USB drive. So now I am trying to copy my CWM backup file to sdcard using TWRP's file manager , and later delete TWRP and reinstall CWM and try to see if I can restore my device..thank you so much
sgt. meow said:
In cwm you should be able to use adb. Otherwise flash the factory image.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
there is an usb mounting option in 6.0.4.1 version of CWM. I was using 6.0.3.1, and.. I am restoring ...
Unbrick!!! restored using OTG USB!!!!
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Your command is wrong, The command to use is: fastboot flash recovery twrp.the name of your file.img
Just like @jawmail said, you're flashing twrp on the bootloader """slot""
-fastboot flash recovery ***TWPR***.img
-fastboot reboot-bootloader
When your phone reboots, using your volume keys, search for "recovery" and using the power button, confirm it.
PROFIT
bauwoo said:
Hello. I am on 6.0.1 MMB29M trying to flash TWRP. I get this error message while doing this.
c:\angler>fastboot flash bootloader twrp-2.8.7.2-angler.img
target reported max download size of 494927872 bytes
sending 'bootloader' (16880 KB)...
OKAY [ 0.392s]
writing 'bootloader'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.414s
Bootloader is unlocked as well as debugging. I have followed a lot of different guides but can't get passed this error. I had TWRP working on MDB08K but the camera was not working for some strange reason. If anyone can help me get TWRP on MMB29M, that would be great.
Click to expand...
Click to collapse
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Haha. Thanks. Yeah I am really lucky. My phone is working now thanks. Just coming from the S6 Edge. Very different rooting method from that, so yeah I should be way more careful. Thanks for the awesome guide, btw Heisenberg. Running PureNexus with ExperimentalX kernel. Such an amazing combo.
Heisenberg said:
Whoa! Does your phone still boot to the bootloader? If so, you're extremely lucky. Flashing a non-bootloader image to the bootloader is pretty much the only way to hard brick a Nexus. You need to take much greater care when doing these things.
Click to expand...
Click to collapse
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Puck24 said:
Update: nvm, figured it out myself.
I have a similar problem. I flashed the TWRP recovery and it booted into it. Made a nandroid and an EFS backup. Copied the backups to my PC. Wanted to flash the systemless root zip. Issued adb reboot recovery and I get the little Android on his back and saying "no command". Tried flashing recovery again, got this:
sending 'recovery' (16880 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.238s]
finished. total time: 0.756s.
And still, I can't boot into twrp by either method. Getting the "no command".
What gives?
Click to expand...
Click to collapse
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Heisenberg said:
Please explain how you fixed your problem so the info is there for folks in future.
Sent from my Nexus 6P
Click to expand...
Click to collapse
guess it's a corrupted file?
Actually, I just tried flashing it one more time, rebooted to the bootloader with the phone, not with the command. Then I also used the phone to enter into recovery, not by issuing commands. And it works
Sent from my Nexus 6P using XDA Free mobile app
FIXED
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Did you download the right image from here?
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
irule311 said:
Did you download the right image from here?
Click to expand...
Click to collapse
Yep, straight from the Angler section. I've tried the latest one, as well as a few older ones. Nothing.
Soulfly3 said:
Are you following THIS guide, TO THE LETTER?
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Specifically step 10
Click to expand...
Click to collapse
Hi, I followed the steps exactly, before updating my 6P to N developer preview, I had previously flashed the factory image. Thanks!
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Rxpert said:
Unzip it yourself and flash em each manually.
Make sure you have the lastest fastboot tools. Im going to go out on a limb and say yours are out of date
Click to expand...
Click to collapse
Tried that as well. Everything flashes, except the system.img.
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
The logs make me feel like the file you downloaded is corrupted. Check the md5 maybe?
Sent from my Nexus 6P using Tapatalk
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
Probably a corrupt download, did you check the MD5 after downloading?
g4slyness said:
Tried that as well. Everything flashes, except the system.img.
Click to expand...
Click to collapse
It looks like you are not in the directory with the boot.img, et al. (your post shows no boot.img,, ... ) Make sure you unzipped the image. There are 2 files you need to unzip, the one containing the bootloader and radio. In that unzipped folder will be another zip. Unzip that second folder and you'll see the boot.img, cache.img, et al. The change in to that folder from your terminal or move those files into the folder you created (if following Heisenberg's guide), then proceed.
g4slyness said:
Hi all! Been a member of XDA for a few years now, but only just had the pleasure of becoming a nexus user. Yesterday I decided to install the Android N preview to try it out, but decided I didn't want it on my phone. So when I got home, I wiped the phone and proceeded to flash the factory image, but no matter which image I flash it, it says "error: update package missing system.img". I have tried manually flashing each file in fastboot as I have seen in many threads, but nothing is working. I have tried restoring old TWRP backups and flashing custom ROMs in TWRP, but nothing is working. Help!
This is what the Command Prompt is saying:
sending 'bootloader' (3526 KB)...
OKAY [ 0.106s]
writing 'bootloader'...
OKAY [ 0.206s]
finished. total time: 0.314s
rebooting into bootloader...
OKAY [ 0.118s]
finished. total time: 0.119s
< waiting for device >
sending 'radio' (48600 KB)...
OKAY [ 1.151s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.327s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate -1733501396 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
I think you are using an old version of fastboot. Update it and try again. Problem was fastboot couldn't allocate enough system ram to hold the whole image or something. In the newer fastboot the file transfer was broken in to several segments.
Maybe try another USB port too won't hurt.
Gytole said:
Had the same problem when ai first got it.
Wugs toolkit fixed me up!
http://forum.xda-developers.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493
Click to expand...
Click to collapse
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
g4slyness said:
Thanks!!! It actually worked. Not sure what was wrong before, seemed as though every file I downloaded off of the google website was corrupted. Cheers!
Click to expand...
Click to collapse
You're welcome!
Like I said I had the same problem back in November. It ended up being an outdated version of fastboot like others have stated. I coyld flash my friends Moto X Pure but not my Nexus 6P..mit was awful and brain racking. Glad all is good!
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from here and it's still not giving me root after flashing SU to the device.
KevinDel said:
So I tried to flash a custom recovery and got this
C:\Users\kevin>fastboot flash recovery twrp.img
sending 'recovery' (13134 KB)...
OKAY [ 0.432s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.453s]
finished. total time: 0.886s
Was curious if it flashed or not?
EDIT: I got the SU from and it's still not giving me root after flashing SU to the device.
Click to expand...
Click to collapse
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
I got the TWRP to actually work now, now it's trying to get SU to work. I got TWRP from here I can't get majisk or SU to run at all though now.
Moderi said:
From what I've seen so far, you may be trying to flash a custom recovery that is not made for your device, which variant are you using? (ex: XT1760, XT1764, you can see them as SKU in fastboot mode)
Also, from where did you download the twrp?
Click to expand...
Click to collapse
Also it's the XT1768 model.
Try installing magisk the new way (without a custom recovery). There are instructions in the main magisk thread.