Need help rooting- - Nexus 6 Q&A, Help & Troubleshooting

I am having a hell of a time rooting this phone. (Motorola Nexus 6 XT1100)
I am trying to follow this guide: https://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
If anyone can offer some suggestions, they would be greatly appreciated.
I managed to get as far as unlocking the bootloader in fastboot mode.
The next step, obtaining root, is where all my problems started.
I downloaded CF Root and extracted the files, as instructed, allowed the root tool to run, (I'm using Linux, if it matters).
When the process was finished, and my phone attempted to reboot, it got stuck on the Google screen with the little lock (showing unlocked).
I allowed the phone to stay in this mode for around 30 minutes thinking it just needed time.
It never did anything. I attempted to let it try and start up again (a couple times actually) and it never goes past the Google lock screen.
I powered down the phone and restarted in fastboot mode, and attempted to run the CF Root tool again, with the same result.
I am currently stuck with only having access to fastboot.
I tried to flash a recovery and boot into that, but it won't allow that either. Perhaps this isn't even possible (YET), as it's not in the instructions to flash a recovery until after the rooting process, but I thought I would try it anyway.
I have tried flashing TWRP and Lineage recovery. No success with either, although the terminal is saying
sending 'recovery' OKAY
writing 'recovery' OKAY
But when trying to reboot recovery I get hit with
unknown reboot target recovery
Anyone know what's going on and how I can get this resolved? I just want to install a recovery and flash a custom ROM.

In that guide you can follow my journey to root starting in post# 929. I had & have had a LOT of help from my fellow XDAers. They're great & thank you all.

Thanks!
I'll check it out.

Boy, oh, boy.
I don't know what is going on.
I finally managed to get out of the bootloader screen.
I don't know what/how it worked. I downloaded Nexus Root Toolkit to a windows computer and tried the Flash Stock + Unroot option.
It keep saying waiting on device or device not detected or something ( I cant remember exactly, it was hours/many error screens ago!)
Next, I tried the option for Root + Add a Custom Recovery and directed it to where my TWRP file.
Again it acted like it was doing something. Even found my connected ADB device. Went through a couple processes, said it would need to restart a couple/few times. Everything was trucking along just fine until suddenly, it got hung up 'Waiting on device"
Not sure what happened, but all of a sudden, it could no longer find my device.
For chits and giggles, I decided to try and reboot recovery from the bootloader screen. I had attempted this many times and all it did was start back up in bootloader, BUT, this time, it actually started up in some recovery program I have never seen before. It wasn't stock and it certainly wasn't TWRP!
At this point, I hooked my device back into my computer running Linux and attempted to push TWRP, and reboot in recovery.
It worked!
Now that I had a recovery I was comfortable using, I proceeded to push my ROM.
Wanted to try Lineage with MicroG, but I am not advanced enough to go that route. I could not get a fake app store to work.
Guess I'll have to stick with what I know. I love the idea of MicroG, but it apparently doesn't work with Pure Nexus.
Anyway, just wanted to post some closure for this thread. I know the Motorola Nexus 6 is an old phone, but I like it. This is my second one. My first one, screen finally cracked and it was cheaper to just purchase a new one from Amazon than to replace the screen.

Related

[Q] Nexus One stuck at X/ No recovery

First of all, I have checked around quite a bit on this forum as well as others to try and avoid having to ask a question that's already been answered. Here's my problem/ what happened. I was rooted (one-click with locked bootloader) and had tried out several roms for a couple of months now. A few days ago I reverted back to an old stock 2.2 backup. My phone received two ota updates and I'm pretty sure I lost root. I had just went on using the phone for about two days when I ran into a problem today. After shutting the phone off I have now become "stuck" at the initial "X" screen (not animated). I pulled the battery and tried again several times. I then tried to reboot into recovery from the bootloader/ 3 skateboards screen with no luck. Any time I hit recovery it simply takes me back to my stuck "X" screen. I have an entire backup of my SD card from earlier as well as at least 4 nandroid backups (one of which was the stock 2.2 before the latest ota). I am thinking I need to somehow put clockwork recovery back on my phone so I can restore to one of my backups. I do not know how to do this. Sorry for the lengthy post but I want to provide as much information as possible. Any help at all would be greatly appreciated.
Just like you restore to stock 2.2. You should have used recovery.img. use adb fastboot to put the stock or anom recovery. I am not am expert but I have had the same problem few times. Always use adb commands
Sent from my Nexus One using Tapatalk
Does my n1 have to be in usb debugging mode because it's acting like it's not connected or something. I get the message "error: device not found." I'm on the fastboot screen on my n1 and using terminal on a mac. I usually didn't leave debugging mode on
No it doesn't but you have to have the drivers installed as well as the SDK with dependencies.
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
fastbook oem unlock
install Amon RA recovery
flash new rom.
Caseyp789 said:
Whew! Thank God! I ended up getting a FRG33 stock rom onto the sd card and the bootloader detected it. I'm not sure what happened but when I tried recovery after that it took me to the android with an "!" point (meaning no recovery?) and then back to the X. This time however it loaded on through and went right back to the way it was before it was stuck. Again, not sure what happened but thanks for the replies and help.
Click to expand...
Click to collapse
The exclamation mark is just the stock Android recovery - it was re-installed when you loaded the stock FRG33 ROM.
Performing OTA updates requires you to have the stock recovery installed. Simply reverting to a stock 2.2 nandroid isn't sufficient, so trying to install those OTAs (which should have failed without stock recovery) may have broken something there.
GldRush98 said:
fastbook oem unlock
install Amon RA recovery
flash new rom.
Click to expand...
Click to collapse
This is by far the easiest (and safest) way. Google/HTC provided us an easy and safe method for gaining full access to our phones.... Why so many people refuse to use it is beyond me. If you root it the proper way (with fastboot oem unlock), it will make recovery from any further issues a lot more simple.
From what I can tell, I am having the same symptoms as the topic creator. I believe the problems started during a failed flash of cyanogenmod 6, but I am not sure by what means the flashing took place.
I can't boot the phone normally, it hangs on the X splash screen and the same occurs when trying to enter recovery mode.
I have tried the passimg approach to fix this, it either doesn't recognize my zip or starts loading it and freezes on a loading bar.
Fastboot flashing recovery completes, but doesn't fix the issue.
I can fastboot flash every image partition except system or radio, both hang.
As danger rat and dude random both know, I have posted this problem on the nexus one forums but I thought I'd post here to have some more minds look at it.

[RESOLVED] Unlocked XT1058; Bootloop & Failed System Flash

Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...

[Q] Please help with Flashing Recovery on on Rooted VS980

I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
usafmunk said:
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
Click to expand...
Click to collapse
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
mjones73 said:
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
Click to expand...
Click to collapse
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
usafmunk said:
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
Click to expand...
Click to collapse
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
usafmunk said:
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
Click to expand...
Click to collapse
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
TheOriginalKyle said:
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
Click to expand...
Click to collapse
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
usafmunk said:
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
Click to expand...
Click to collapse
Well new update: I was able to fix it! The problem was my own ignorance. I was following some Googl'd instructions to get the device into download mode that were incorrect. Once I saw the correct ones, I was able to get into Download Mode and revert to stock from there.

[Q] Nexus 6 not booting up after random shut down

Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.

Tried to install OTAvwith TWRP, phone boots normally but then reboots to recovery

I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!

Categories

Resources