Related
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
I have a stock Verizon Moto X (XT1060) that was running 4.4.4. I was on a flight Friday using the phone in airplane mode to run Spotify and Podkicker - noticed the phone was running a little hot so I shut the apps down for a while. Anyway, upon landing I take the phone off airplane mode and the usual minor flood of emails/texts/updates comes in. About 30 seconds after this the phone begins alternately flashing "Process android.process.acore has stopped" and "Process android.process.media has stopped." These cycled for about 5 displays of each, then would disappear for about 45 seconds, then start again. Tried resetting the phone, letting the battery die, no success.
Saturday I tried to navigate into settings to do a factory reset, but the screen froze whenever I tapped on the "backup and reset" menu. Could access all the other menus from settings (until the error cascade started again....). I was able to boot the phone into recovery mode and wiped the cache - nothing. Went back into recovery mode to do a factory reset and now I appear to be stuck in a boot loop - the Moto logo pops up, buzzes, and then does nothing for about a minute or two before trying again. I can get it into recovery mode and tried to wipe the cache and factory reset again, but still nothing.
Any thoughts? Tried looking at other threads but didn't seem to find anything like this. Thanks!
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
hbenz2008 said:
Try this cmd in fastboot
fastboot oem fb_mode_clear
http://forum.xda-developers.com/showthread.php?t=2738055
Click to expand...
Click to collapse
No luck, unfortunately. Still stuck on the Moto screen. I can force the phone to reset by holding down the power button and then get it into fastboot, my computer recognizes the fastboot device, and the code seems to have run fine. Thanks for the idea - any other thoughts?
If you can still get into fastboot mode you can try flashing only the stock 4.4.4 system.img via mfastboot. That will not wipe your data. If that does not work I would do a full return to stock via mfastboot or you can use rsd.
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
cmcgowan said:
Thanks Travis I'll give it a shot. I never enabled USB debugging and never unlocked my phone before this happened - I imagine I'll need to try and unlock the bootloader first, no?
Click to expand...
Click to collapse
No, don't need to unlock boot loader to flash the system.img just enable USB debugging in developer options. Tap build number 5 times to enable developer options. If you have never flashed anything before via fastboot rsd might be easier for you.
Thanks - I've used fastboot before on an older phone but never enabled USB debugging on this phone and now can't get to enable it since I'm stuck with this boot loop. Downloading the files from Moto now so will give it a shot tonight anyway. Can't really break it more than it's already broken since all I've got now is a shiny light up paperweight.
You will still need to download the stock images for 4.4.4 for Verizon and extract them. You can flash via rsd or simply flash just the system by running the command "mfastboot flash system system.img"
You will have to have the image file in the same folder as your mfastboot.exe I usually keep all mine in platform tools.
Sigh. Got everything downloaded but when I tried to flash either the boot image, recovery image, or system image, I ran into errors
Here's what displayed (sub boot/recovery for system - same basic error):
c:\{Path}\mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
sending 'system' (262144 KB)...
OKAY [16.793s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.756s
I was following option 5 from mark @ cdma forum's guide to return motox to stock (can't link b/c I don't have enough posts...) . No issues until I got to the flash boot boot.img step.
I'm assuming this is due to not having USB debugging enabled prior to my phone eating itself, though I'm not sure. Willing to try other things since I love my Moto X but my cheap replacement phone arrives tomorrow (hopefully) so at least its not the end of the world...
You are sure you got the 4.4.4 images? You did not try to downgrade right?
Yup. Definitely got the 4.4.4 images (went back to the Moto site and it will let me download the 4.4.4 immediately but made me request authorization for 4.4.2) and I know I was running the most recent version since I checked for an upgrade on my phone last week in the hope that Moto had released 5.0.
You are following this guide? http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
If USB debugging is not on you can manually boot you device to boot loader mode. Then fastboot or rsd should work fine.
---------- Post added at 11:36 PM ---------- Previous post was at 11:32 PM ----------
Moto X Restore and unbrick for any major US carrier: https://youtu.be/jhhktIkwi7Q
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
cmcgowan said:
I appreciate the help...but still no luck. That's basically what I've been doing and I went back through following those instructions - at every step I get the "variable not supported" error and then it fails at the flash boot step with the error message I described earlier.
Click to expand...
Click to collapse
You are opening the cmd screen from the same folder as your images and fastboot and mfastboot.exe correct? From your error it looks like your cmd screen is directed to your "C" drive.
Sorry, just didn't type out the whole thing - the cmd path is to the platform-tools folder where all of the files are also located...
Damn was hoping it was something simply like that. Have you tried rsd?
I haven't - didn't enable USB debugging and for whatever reason the package I downloaded from Moto doesn't include the XML file of instructions. Most of the links from the youtube video and some of the links from the XDA guide earlier are also dead so seems like I'm pretty much out of options. Thanks for all of your help - guess I'm going with the $80 replacement till I'm up for an upgrade!
Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp
PurpScurp said:
Yesterday, some bad things happened when I went to switch ROMs. Eventually, I ended up erasing my internal storage and re-locking the bootloader. I am aware that mistakes were made and I take full responsibility for my foolish actions.
So right now the problem is that I can't unlock the bootloader with the fastboot command because the "Allow OEM unlocking" box is not checked. The main problem here is that I can't simply boot into the OS and check this. I have no OS because I wiped my internal storage, including all my backups (Yes, I am an idiot.).
The phone is currently stuck on the bootloader screen. Rebooting into recovery just makes the Google splash screen flicker and it goes back to the bootloader immediately. I've seen similar threads but I haven't seen anything that mirrors my issue.
Is the phone bricked until we find a way to bypass the "Allow OEM unlocking" checkbox?
Thanks,
-PurpScurp
Click to expand...
Click to collapse
Yes you are bricked.
http://forum.xda-developers.com/nexus-6/help/lock-bricked-nexus-6-t3056401
What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.
R4INS said:
What recovery is on it?
Have you tried booting a recovery image if you don't have stock recovery?
fastboot boot recovery.img
I'd try to boot twrp may not work with the lock
fastboot erase cache got me out of trouble but I didn't relock my boot loader.
Wish I had a nexus stuck in this situation to fiddle with.
Click to expand...
Click to collapse
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.
Yep it does that if you wipe the OS. There's nothing you can do at the moment.
PurpScurp said:
I don't believe that command works with a locked bootloader. It had TWRP. Rebooting into recovery doesn't work at all. It just flickers the Google screen then goes back to bootloader menu.
The only thing that the phone does now is show the bootloader screen.
Simply powering on the phone brings it to the bootloader menu. I don't even have to hold power + vol up/down.
Click to expand...
Click to collapse
Does a PC recognize it when connected? Can you get fastboot to see the device?
Evolution_Freak said:
Does a PC recognize it when connected? Can you get fastboot to see the device?
Click to expand...
Click to collapse
Yes he can. His bootloaders is locked though so he cannot unlock it.
rootSU said:
Yes he can. His bootloaders is locked though so he cannot unlock it.
Click to expand...
Click to collapse
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.
Evolution_Freak said:
Oh, ouch. I must have missed that part. So it's basically the same issue so many others have run into.
Click to expand...
Click to collapse
Unfortunately so.
Hello XDA,
Ok, so I'm going to try to explain the best I can. My roommate has a Nexus 6 (Project Fi if that matters). She went to install an update, although I'm not sure which one. She said she thinks it was "7 something". I'm assuming it was 7.1.1 since that is the one that I was last notified about on my phone and she said the notification appeared only a few days ago. After she installed it the phone was stuck in a bootloop (the spinning colored balls screen).
I Googled solutions and tried wiping system cache from recovery mode. That didn't work, so I asked if she had anything important on the phone and if I could do a factory reset. She said I could go ahead and do it, however that did not work either. So then I plugged the phone into my computer and fired up a terminal session to flash a factory image to the phone. I entered "fastboot oem unlock" so I could proceed . It came back with the "see developer options" message. Ok, cool, but I can't get into the settings app to enable OEM unlocking.
So since I did the factory reset and can't boot into the OS, is there any way to enable OEM unlocking from the bootloader? I'll keep looking for answers in the mean time.
Thanks in advanced.
EDIT:
Found a thread with the OP having similar issues. I tried "fastboot format cache" and "fastboot format userdata" which both failed with "Not allowed in locked state!". Even though I got the errors I tried (out of desperation) to boot to TWRP with "fastboot boot ~/Downloads/twrp-3.1.0-0-shamu.img" which failed with "FAILED (remote failure)".
EDIT2:
Tried downloading 7.1.1 OTA image and sideloading via "adb sideload shamu-ota.zip" from the bootloader recovery mode. Failed with "error: no devices/emulators found".
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Strephon Alkhalikoi said:
Sideload an OTA image. That should resolve the bootloop so you can enter Android to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the reply. I tried it and it failed with "no device found". The command "adb devices" gives me an empty list. Not even ????????.
If ADB isn't seeing the device you potentially have a hardware issue.
i got same problem.
no oem unlock cuz is in bootloop
locked
erasing
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Strephon Alkhalikoi said:
@luisq93: Yours is a different issue. The solution for you is to do...nothing.
The erase part of the factory reset MUST complete, or you may end up with unusable internal storage until an uninterrupted factory reset is completed. So all you can do is be patient.
Click to expand...
Click to collapse
like 2 month and half patient?
cuz the erasing changed language 2 months ago and nothing more... from italian to English, maybe i should just wait... thanks for the advice.
@luisq93: How long did you leave the N6 running the very first time the device started erasing? I'm willing to bet you only gave it a few minutes, became impatient, shut the device down to restart it and upon restarting encountered the erase mode again. Consequently you thought it bootlooped and put it in your drawer.
Until you let erase mode complete, every time the device boots it will immediately enter erase mode, because the erase must complete to avoid corrupting the internal storage. Erase mode, especially on an encrypted phone, may take a while. I had one instance on another of my devices take an hour.
So the solution to the erasing "bootloop" is to do nothing except plug the N6 into its charger and leave it alone.
I was gifted a Nexus 6 after my 5X died. As far as I know the device has never been OEM unlocked, much less flashed with anything. I've unlocked developer options and allowed USB debugging and OEM unlock but when I try to use power+Vol(-) to get into fastboot mode nothing happens, the screen is just black. When I bridged the device using ADB I could see the serial number and tried using the boot into recovery mode command and it rebooted to the same black screen. When I used fastboot commands on the black screen I could see the device and tried running fastboot oem unlock, it did something but wasn't successful in unlocking it. I'm not prepared to just start running fastboot commands blind like that without being able to see what's happening on the device's screen.
It's a curious problem, has anyone ever heard of it happening before? I can't find anything similar when I google it.
All I really want to do is clear the Dalvik cache and flash the latest factory image because currently, even after doing a factory reset, the device is very slow and laggy.
Is there anyway I could clear all the caches etc without going into fastboot mode or does anyone know of any fixes I could use so I can see the recovery menu?
If you boot to bootloader mode, then "fastboot boot <TWRP.img>" you might be able run twrp on your pc and clear caches. If it works, I'd consider factory resetting. You can get twrp here: https://dl.twrp.me/shamu/
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
connorjolley said:
I have considered that. But that requires OEM unlock, no? I still haven't managed to unlock it yet. The first time I tried, I said yes to unlock (it involves using the rocker to select a response, which I can't see the options for) but in the command window it said it failed (can't remember the error message though). I was going to try again today but because I couldn't see the options when I tried it said I'd cancelled the operation and I was too scared to try again in case something went wrong.
But, do you think I should try the fastboot oem unlock command again? I definitely need OEM unlock to install TWRP, right?
Click to expand...
Click to collapse
To install twrp yes, you need an unlocked bootloader. This doesn't install twrp on the device. I believe it should work. It certainly shouldn't hurt. I've been unlocked since the N6 came out so I can't double check for you.
If it doesn't work, I'd be a bit inclined to just flash a factory image thus ensuring everything is stock and current. You might want to wait for others to chime in, but it's what I would do.
You may consider downloading Nexus Root Toolkit, works like a charm : ).
I can't just flash the stock bootloader without OEM unlock, right?
connorjolley said:
I can't just flash the stock bootloader without OEM unlock, right?
Click to expand...
Click to collapse
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
ktmom said:
Correct, you need to be unlocked to flash a factory image, that includes the bootloader. See Google's instructions. Don't get confused by the "fastboot oem unlock"
vrs "fastboot flashing unlock" we are an older device and use oem unlock. The other is for the 6P and newer devices.
Click to expand...
Click to collapse
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
connorjolley said:
Successfully unlocked. TWRP didn't help, still can't see the bootloader menu to access the recovery. I'm flashing the factory image now, hopefully a new bootloader will fix it. If not, is there anyway to clear the Dalvik cache using fastboot commands now the phone is unlocked?
Click to expand...
Click to collapse
I think the command is "fastboot erase cache". Also, unlocking will have wiped the device.
connorjolley said:
UPDATE
Still a black screen even with a new bootloader flash. I'm assuming now this must be a hardware problem
Click to expand...
Click to collapse
Why not just flash the entire factory image you got the bootloader from? What can it hurt? It would be really odd for this to be hardware if you can boot into the ROM and the screen works.