Moto X pure WILL NOT show up in device manager - Anniversary Update? - X Style (Pure) Q&A, Help & Troubleshooting

Hey, my moto bricked itself today, for unknown reasons (see my post in the RR thread) and after several failed attempts to get out of the bootloop I've accepted I'm just going to have to wipe it totally clean. But I've been trying for hours to get it to show up with
Code:
fastboot devices
and Windows is having none of it.
I installed the Motorola Device Manager which supposedly comes with the drivers, and when that didn't work I tried reinstalling the drivers in Program Files\Common Files\Motorola Shared\Motorola Drivers\Motorola Driver Installer.exe. Also installed the Universal ADB drivers and those didn't help. I read that the fastboot drivers are different from the adb drivers, (and since I can't actually boot my phone to use adb), I downloaded the 15-second ADB/fastboot drivers. This was the only one that actually brought up the Windows prompt to install a "new device" or whatever.
However there's still nothing in device manager. No "Android ADB devices" category and nothing under portable devices. Yet when I get into fastboot and plug in the USB, the text at the bottom changes to indicate "Transfer Mode: USB Connected". Is this a new thing with the Anniversary Update? I can't think of anything else because I think I've literally tried about everything. I'm honestly considering selling this phone, seems like I seriously can't use anything but stock without having major problems.
EDIT: nevermind. Tried a different USB cable and bingo. Go figure, lols.
But twrp still reboots after sitting for 5 seconds at the welcome screen. Any suggestions for that?

Not sure about TWRP rebooting. Anniversary update?

Have you tried wiping dalvik and cache?

Yeah I wiped the cache. Not dalvik though but I'm not sure it would have made a difference - when I used the back to stock tool, it still hung on the big M start screen (it just showed the M, but didn't animate the little stitches or anything).
Anyways after multiple hours of trying to get it out of the NEW bootloop, I finally flashed the stock rooted ROM (update 4) and although the radio didn't work I flashed the TruPure February update radio and at least the phone works now.
But man, that was an aggravating process. I was yelling at my computer last night, I was at my wit's end. Messing with this phone in any way has gotten progressively more on my nerves

jDally987 said:
But man, that was an aggravating process. I was yelling at my computer last night, I was at my wit's end. Messing with this phone in any way has gotten progressively more on my nerves
Click to expand...
Click to collapse
This phone and its problems got on my nerves so much that i actually bought an iPhone. I don't really regret it either.
Sent from my iPhone 6S Plus using Tapatalk

Related

Corrupted bootloader, memory?

I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
erica_renee said:
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
Click to expand...
Click to collapse
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
mateorod said:
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
Click to expand...
Click to collapse
yea there is only one storage device inside the nexus.. its all symlinked
If you could get the driver going, send a adb reboot-bootloader command, the bootloader should work then.
Will the next nexus have a longer screen?
Same problem here.
mateorod said:
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
Click to expand...
Click to collapse
Hi, everyone!
I've got the same problem with my Motorola Razr D3 (XT920). After a system update, something bad happen while the system tried to install the last patch realeased by Motorola. I still can access the bootloader but nothing is working.
So I wonder if any of you guys have figured out how to reinstall the bootloader.

Need help... cannot figure rooting out

Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
lordmuggins said:
Hi all,
Long story short, I accidentally bought a Kindle Fire HD 7. I was hoping to root it but I've had nothing but difficulty. Can anyone help me with the things below? ** Please don't reply if you can't - the disorder and unmoderation of this forum is part of the confusion problem **
- The apps that are given on this site mostly don't work for 7.2.3. Is this an issue with the version?
- I kept getting permission denied errors. Nothing that pushes over, pushes successfully - yet it says it does
- When I finally got something "rooted", my status bar and home bar (at the bottom) are all gone. I can pretty much do nothing with it
- I can't figure out how to restore. I can get into FastBoot mode fairly easily, but when I try to do anything I get "waiting on device" errors. Any ideas?
- I'm a Mac guy, but running Windows 7 to do this. I've tried various versions of drivers posted on the board, but W7 is just a PITA to work with. When it goes into Fastboot, it comes up as an "unrecognized device" in Device Manager. Would this be part of the problem? I've tried to associate drivers with the unknown device, but it keeps saying the driver it has is the best (even though I've removed it).
And while I admit, an emotional rant after spending way too long having to do the above..:
- This forum is a complete mess.. can people with KF HD 8.9's get out of the forum and quit replying or giving advice on the wrong device? Mods, please shut down or move KFHD 8.9 posts. For people trying to find out info, it's seriously a mess.
Click to expand...
Click to collapse
Ok what is the state of your KFHD? 7"? I would try to use this toolhttp://forum.xda-developers.com/showthread.php?t=1951254 to restore your kindle and getting back to a working state. If you have any questions post them in here or that forum and I will try to guide you through anything. You should not try to use an automated root tool if it isn't for your specified version(7" 7.2.3) and using a automated tool, I think personally, is just not good in general. What does the device manager specifically say when you are in fastboot? It shoulde look like this:
Thanks for getting back to me. I have indeed also tried that, but I encounter the Fastboot problem mentioned above. I can get it into FB mode fine, but when I go to do anything, it gets stuck at "waiting for device". I'm wondering what I'm doing wrong?
I'm using Windows 7 (gah)... just for the purpose of this. Believe me, it reminds me why I've left Windows looonngg ago
PS All automated tools were specific to my model and version #.. i wouldn't do otherwise.
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
lordmuggins said:
And I forgot to say, it shows the yellow triangle warning signs.
I have however installed all the right drivers that I got on various places on the forums. Any ideas why it's doing that? (USB debugging/ADB is enabled of course)
Click to expand...
Click to collapse
Try to reinstall the appropriate drivers.. first uninstall the ones you have now then reinstall.. if you have the yellow triangle in device manager the drivers are not installed correctly
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
lordmuggins said:
I've tried that.. not sure what I need to do now. (I hate Windows)
The drivers appear fine when not in Fastboot (ie regular ADB) just not when in Fastboot
Click to expand...
Click to collapse
You do know that ADB and Fastboot are different.. Correct? They are two different cmd lines to execite comds to your kindle..does your kindle boot? What is its state? what are you seeing or does it even run at all>
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
lordmuggins said:
I thought I made this clear in other posts, sorry
My Kindle boots fine normally, but in my attempts to root it, it's screwed something up (my menubar doesn't appear). I wished to restore it using the tool above.
I can get it into Fastboot, but I can't actually perform any actions due to it saying "waiting for device". Most ADB functionality works fine, i.e. to push apps. But I also can't get it rooted.
My issue is that when it is in Fastboot...not when it's not. That is what I'm trying to figure out.
Click to expand...
Click to collapse
Have you tried Kindle Fire First Aide tool and the restore option of you version?
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
lordmuggins said:
Yes, I have.
And my issue remains - when in Fastboot mode, it also gets stuck on "waiting for device".
When normal boot, ADB functions are fine. It communicates.. things happen
When in fastboot (I have a WordArt looking 'fastboot' logo on the screen) then nothing appears to communicate, and my Device Manager claims it has an "Unknown Device" that it wont let me manually install drivers for.
Windows 7 is x64 if that makes a difference
Click to expand...
Click to collapse
Try a factory reset on the device and if that doesn't work go to Chris's thread, KFFirstAide and post your problems that you having with the software. He will help you figure out if something is wrong with your device or its the software. I would think its user related, in the nicest way possible. A lot of times we get are selves all worked up over this stuff and forget to specific steps, I am guilty as well. Maybe take a step back for a few hours and then give it another shot.. Sorry I couldnt help more but I currently don't have my KFHD bc I just got a new one shipped to me and still waiting for it to arrive.. If i had my device in front of me I would probably be able to find you a solution.. Its been three weeks since I have seen a Kindle and my memory is vanishing
How do you propose I do a factory reset?
lordmuggins said:
How do you propose I do a factory reset?
Click to expand...
Click to collapse
right.. menubar is gone.. how the F did that happen.. I don't get all these people having so much problem with rooting their devices and $hit disappearing.. Can you download soft keys? I don't remember if you need to be rooted or not too..
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
lordmuggins said:
If I knew the answer to that question, I wouldn't be here. I do not see how I can download soft keys.. unless they're in the Amazon store?
Click to expand...
Click to collapse
Hey man just trying to help you.. I'm not the one with the problem, although I am making my problem bc I am trying to help. Go over to either thread KFFirstAide or KFHD system.img resotre tool and post your problem.. good luck
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
lordmuggins said:
So I got it restored; I had to execute the app open in adb to get into Settings. Still can't figure out how to get the Win 7 to recognize it in Fastboot mode.. I just get "waiting for device"
Click to expand...
Click to collapse
Do you mean you get that when you select the option to reboot into fastboot mode, or that you are already on the fastboot screen but nothing is happening?
I had the exact same issue with missing status bar and softkeys, cazy annoying. So hopefully I can remember exactly what I did, depending on your answer to my question though
In regular mode, I had missing status bar and softkeys. I restored factory settings (by using adb to get into the settings screen). They are now back.
Now, I have it rooted (well, I have Superuser loaded at least and it appears to be working)... but that is all. It still feels half-done to me.
With the FirstAide tool I'm getting into Fastboot and then I was going to use it to restore it using the Restore Tool here: http://forum.xda-developers.com/showthread.php?t=1951254
But it doesn't work.. I can load into the Fastboot screen (wordart logo) but it doesn't connect to the device... I just get "waiting for device" and that's where it stops. The WIndows 7 PC I'm using just says that an unknown device has connected and leaves it there.
Ideally, I wish to load Google Play etc, but I can't do that using the First Aide tool. It throws a lot of permission denied errors at me.. reboots several times, says it has been successful but none of the apps are there.
Ideas? I feel like I'm getting closer... perhaps..!
Have you tried running a app that needs root and seeing if the "grant permission" window pops up when you run it. There is a root checker app that you could install from the Noobs Guide to rooting, which should do the trick. SUChecker.apk http://forum.xda-developers.com/showthread.php?t=2069117
If you have managed to get the UI bars back, how come you want to use the restore tool to reset the whole kindle?
If you root is working fine, and you want to install google play then follow the Alternative Manual Install from here http://forum.xda-developers.com/showthread.php?t=2069329 instead of using the first aide tool, which seems to be giving a few issues at the moment.
Another random solution is make sure you are using a usb2 port instead of a usb3 port(if you have one)

[Q] Fastboot/ADB/sideloading issues

I flashed a 4.4 stock rom on my 2012 32g N7, and unfortunately, didn't notice until too late that it was also overwriting my custom recovery with the stock. Also, in the flashing process I received an error while flashing GAPPS. When I first booted the tablet, everything was fine except for no GAPPS, but I figured it would be simple to just download an APK or two and load them - well, when I tried that with several play store APKs I got "cannot open file" error.
I have now resorted to ADB to "sideload" the apks (and a custom recovery) to the tablet. At first I had trouble with the drivers, but I have followed numerous tutorials and have a solid grasp of how ADB works now. (more on that later)
I also tried WUG's toolkit, but no matter what I tried (or how many drivers I un/installed) I could never get past the "no fastboot device" error.
I used a second version of the ADB from another XDA thread, and was finally able to get my PC at the command prompt to communicate with the N7, and recognize it with "ADB devices" - the result was "<serial> sideload". This is of course when I have the tablet in the stock recovery "adb sideload" mode.
I about yelled for joy, when after six hours of rebooting and tutorials, I was able to get "adb sideload update.zip" to load, but the joy was short lived - as it consistently hangs at "sending: 'sideload' 53%"
I have tried several different zips, of varying names. and even some APK's (which hang at 78%)
Any assistance which can be offered to get this N7 functional again would be greatly appreciated!
SOLVED
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Notable said:
I was using a company computer, for which I did not have administrator rights......
I just face palmed so hard I gave myself a well deserved concussion.
Click to expand...
Click to collapse
If you're flashing the stock KitKat, you shouldn't need to flash a separate gapps package. Aside from making sure you have UAC control, make sure you update boot to 4.23, if you haven't already done so. Flashing 4.4 is easy, as long as you don't make the mistake of ever owning another An droid device and plugging it in to your pc... Dealing with missing/conflicting Windows drivers might require a vacation day and a fist-full of xanax,
Sent from my Nexus 7 using Tapatalk

[Q] looped N7, computer doesnt recognize it...

stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
fixed it..wooooohoooooo
Vishnuisgod said:
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
thank you for the tips ! the tool kit actually worked i had no os (deleted everything).
and used the 9 option (flashing stock) it worked !

Messed up 6P ROM flash

I used to do a fair bit of modding and participated here a few years ago. Here I am again a little bit wiser and a fair bit behind the times for modding and finding my way around XDA.
My son upgraded his Nexus 6P and gave it to me to play around with. I decided to try modding again and while I have been partially successful, I am now a bit stuck.
I have ADB up and working.
I have TWRP v3.3.0 (?) installed and seemingly working
Following the posted instructions, I installed the statix_angler-20190321-0315-9-v2.0-OFFICIAL image and reboot
Sadly, after showing a coloured G O O G L E which then rotates into a colourful G, it seems to hang (left it over night)
Then, in an attempt to load a different image, I somehow managed to (mistakenly) wipe everything such that the device says there is no OS.
While I can boot to TWRP consistently, I can't seem to get much farther.
When installed via sideload (TWRP) Statix, RR, AOSP get to the logo then all stall.
Much appreciation in advance.
Vicntc said:
I used to do a fair bit of modding and participated here a few years ago. Here I am again a little bit wiser and a fair bit behind the times for modding and finding my way around XDA.
When installed via sideload (TWRP) Statix, RR, AOSP get to the logo then all stall.
Much appreciation in advance.
Click to expand...
Click to collapse
So some progres has been made. After downloading RR-P-v7.0.2-20190422-angler-Official.zip and sideloading, I have a bootable device.
I did get a few E:recv error on uevent messages soi I'm not 100% positive it's working 100%.
I didn't like the icon set of the RR so I'll try a few more and see if I can find a version that can be installed and run properly.
Vicntc said:
So some progres has been made. After downloading RR-P-v7.0.2-20190422-angler-Official.zip and sideloading, I have a bootable device.
I did get a few E:recv error on uevent messages soi I'm not 100% positive it's working 100%.
I didn't like the icon set of the RR so I'll try a few more and see if I can find a version that can be installed and run properly.
Click to expand...
Click to collapse
I might be a **** for assuming, but did you read the op for statix? You used the twrp they have listed in the op, and formatted your data like it tells you to since it uses file based encryption instead of full disk?
Thanks for the responses but this effort is well and truly dead now. The cat came by while the device was USB connected and thought the cord was a plaything. Phone ended up on the floor. Well and truly "bricked" now. Literally. No more ROM fun, just the recycle bin.
Vicntc said:
Thanks for the responses but this effort is well and truly dead now. The cat came by while the device was USB connected and thought the cord was a plaything. Phone ended up on the floor. Well and truly "bricked" now. Literally. No more ROM fun, just the recycle bin.
Click to expand...
Click to collapse
Apparently, "What Is Dead May Never Die" applies to more than the Knights Watch. I was able to get the Nexus 6P back together, charged and booted into TWRP.
Now installing AospExtended-v6.2-OFFICIAL. Guess we'll see if it's really back or not shortly.
Vicntc said:
Apparently, "What Is Dead May Never Die" applies to more than the Knights Watch. I was able to get the Nexus 6P back together, charged and booted into TWRP.
Now installing AospExtended-v6.2-OFFICIAL. Guess we'll see if it's really back or not shortly.
Click to expand...
Click to collapse
If using the StatixOS ROM and get stuck at logo again you might try this per OP for Pie 9.0.
"Install the official ROM, GApps and then wipe your internal data partition.
- THROUGH TWRP
Wipe > Format data
- OR THROUGH FASTBOOT
Code:
fastboot -w"
https://forum.xda-developers.com/nexus-6p/development/rom-statixos-t3832438
Also, per other comment, use the recommended TWRP version. Glad to hear you got the phone back up.

Categories

Resources