Database Develop

Nexus 6 - Can't boot TWRP recovery

I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.

simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.

briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention

So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?

simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.

No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.

ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.

nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.

50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.

ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.

Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.

ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.

So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.

ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?

Stuck in fastboot

Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?

Olikay said:
Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?
Click to expand...
Click to collapse
sounds like you should flash a factory image.
ok, heres the problem. to flash a factory image, you need to unlock your bootloader. to unlock your bootloader, you have to enable to oem unlock setting in developer options. which means, you need to try to boot again, 40 times if need be. when you boot up, you need to go into settings, about phone, the press build number 3 times in a row. that will enable the developer options. go back one page, scroll up, and youll see it. go in there and enable oem unlock. now you can flash a factory image.

Yea dude, that doesn't look good at all. Have you ever installed any mod of any kind on the device before? Or was this just random and happened while 100% stock? Your best bet as Simms said, would be to try and get into your developer settings and turn on "allow oem unlocking" and "USB debugging". Then flashing a stock image.
Sent from my Nexus 6

There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.

Olikay said:
There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.
Click to expand...
Click to collapse
Damn, that's awful dude, I wanna say your Nexus isn't recoverable. Might have to send it in for repair to Google. If there was no modification to it at all, bring that up! You might get it fixed cheaper or free!
Sent from my Nexus 6

It's really sad, and it makes me think why the USB debugging mode is not enabled on default on every device for this very reason.
I did not root the device yet, as I did not wanted to risk to lose the warenty which it still should be under. So I guess I have no choice than to send it in.
I will try one last thing, and that is to hook it up to a Ubuntu powered computer, let's see if I can mount the phone' s drive with it.
I'll keep you folks updated.
UPDATE: negative on the Ubuntu idea, there is nothing mountable (Disk utility)

It works again! At least it seams for now...
This worked for me video ID: 0nDLvy8F5qk on youtube "Nexus 6 Hard Factory Reset Fastboot Bootloader Recovery Mode" from Jamie Wagner (I am not allowed to post links yet)
But I needed 20 tries to boot into factory reset.

if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.

Yourgodtim said:
if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.
Click to expand...
Click to collapse
Definitely! I would highly recommend just unlocking your bootloader and leaving it unlocked, with USB debugging on! This does not affect OTA updates at all and really, it's a last resort form of protection! My opinion of course!
Sent from my Nexus 6

unlock tbe bootoader
that the best thing youll do for your device, just in case. you dont have to modify anything, and itll still be unmodified.

Nexus 6 bootloader troubles

ok i have a bit of an issue.
simply put i was attempting to remove xposed, root, busy box. really just about any and all modifications. so i attempted to flash a stock 5.1.1 from google... i think i flashed the wrong one. because everything went fine through the flashing, but the phone wont boot past the google splash screen.... well as the derp i am. i locked the boot loader after because i was planning on sending it back to at&t. well now. im attempting to try a few different 5.1.1 images. (which in writing this im thinking... that isnt probably the best course of action.)
well i guess what this leads to is..... first.... which image do i use.
i was running 5.1.1 before all the modifications. so i just attempted to flash a 5.1.1 for all carriers cept T-moblie
i used shamu from this site https://developers.google.com/android/nexus/images#shamu
i also want to toss it out that the phone has been dropped....so internal damage might be a possibility, but i doubt thats it since it was fine before the flash.
so over what image should i flash? and is there a way to unlock the bootloader without going into the settings and chekcing the OEM box under dev options? because accessing the phone is basically limited to boot loader and recovery right now.

If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.

Strephon Alkhalikoi said:
If you locked the bootloader, you cannot flash factory images. If you still have a custom recovery installed, install a custom ROM. Otherwise, you need to find the Android N Preview 1 OTA zip, which should be on these forums, and flash it through stock recovery. The OTA is a complete system image, and will update your system regardless of whether the bootloader is locked or not.
Regardless of which way you install a ROM, reveal the Developer Options menu and check "Enable OEM Unlock". Then you can unlock the bootloader and flash a fresh Android 6.0.1 factory image from Google, which is carrier agnostic.
Click to expand...
Click to collapse
ok well first i appreciate the reply
so basically the set up is i am running stock recovery with a locked boot loader.
if i use this Android N Preview 1 OTA zip. this will allow me access to the dev options which then i can boot up to check the bootloader box? then i can flash 6.0.1.
if that's right then awesome! i appreciate the help. so just so i don't fall back into this mistake. i have the AT&T version of the Nexus 6.
so if there is a specific Image i need, could you please point me to it?
I'd rather not have this happen again lol. the reason i ask is because the site i posted in my Original post has like 4 version of the 6.0.1 image that i can choose from. and since my track record of doing this hasn't panned out all that well so far i figured id just ask for specifics before attempting anything because clearly i messed up and have very little understanding of what im doing.
again. i really appreciate your advice

"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.

Strephon Alkhalikoi said:
"Carrier agnostic" in my previous post means it doesn't matter what carrier you have. With Android 6.0.1, the system images no longer have carrier customization within them. The carrier-specific stuff is downloaded when the phone is set up with the SIM inserted.
As for your current setup, install the Android N preview OTA by sideloading it in recovery, boot into Android, enable developer options, and enable OEM unlock. From there, you need to make sure you have on the PC drivers for the Nexus installed, as well as Fastboot and ADB. Unlocking the bootloader as well as installing the Android 6.0.1 system image require it. If you need a walkthrough, there should be tutorials for both installing the Android N OTA as well as installing a system image in the General section of the Nexus 6 forums.
Click to expand...
Click to collapse
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.

So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.

Strephon Alkhalikoi said:
So where are you getting stuck? The OTA needs to be copied to internal storage and installed from there. You shouldn't need ADB or Fastboot until after you install the N preview.
Click to expand...
Click to collapse
ok so im lost now. i need to take the tgz file and put it on my phone then when i go to the recovery i need to sideload it?.. dont you do that by having it sideload the file from your PC? right? well my issue now is that i cant get it to show its storage on my PC. when booted into recovery the device wont even show up on my PC at all and when it boots into fastboot it regesters, but i cant do anything because the bootloader isnt unlocked i also cant unlock it via command because the OEM checkbox hasnt been checked. and i cant check the oem box via usb debugging because my device doesnt regester when in recovery.
so im not sure. where to go from here. is there a way to place the file on my phones storage via fastboot or usb debugging? preferably fastboot because ADB commands dont seem to regester to my phone at all.

You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Age135 said:
well when using the adb devices command... my device wont show up. i can get it to show up when i reboot into bootloader and use fastboot devices, but it wont register in the recovery. could it be because i dont think i have ADB debugging checked? since i flashed new image on it and now i cant access the menus i cant chenc the debugging box either.
Click to expand...
Click to collapse
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.

simms22 said:
you can only use fastboot, while you're in the bootloader, to do anything.. unlock it, flash a factory image, flash a custom recovery. adb will do nothing and see nothing.
Click to expand...
Click to collapse
yeah thats what i was thinking. the other guy was saying to sideload using recovery, but tbh i wasnt sure how to sideload and i didnt wanna be rude and act like you guys were my personal helpers. so i googled how to just to get a general idea. the idea that i got was that you needed to sideload anything by downloading it to your PC then using adb to install it.
apparently i dont know as much as i think. hes helping me out alot, but im not sure how to pull a file onto a phone that wont boot. i thought maybe i could transfer it via adb,but i think that boat is gone. since it seems i can only use fastboot, but idk of a way to transfer a file onto my phone via fastboot.
i appreciate the help though. thanks

Strephon Alkhalikoi said:
You need to start reading, which I recommended if you needed a walkthrough.
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.

Age135 said:
ok. so all of these say i should download it to the phone so i can sideload it using the recovery.... well this is the issue. the phones storage wont register on my PC. so transferring a file normally isnt gonna be possible (unless im doing something wrong and theres a way to make it show up). is there a way i could transfer it onto the device via fastboot?
Edit:
after doing some reading. i have found out i may not have adb drivers installed... ive looking into how to install them, but the only option i found was through a downloader which seems to stop after a bit of the download saying its waiting for something... so im completely lost as to what to do from here.
Click to expand...
Click to collapse
Try these drivers from Googles site.
https://developer.android.com/sdk/win-usb.html

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk

New to nokia, not android/adb/etc

So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks

jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.

Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse

Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse

Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse

jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.