Related
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.
I've followed all of the steps from this guide: http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
I've got to the end where I am running the code snippets to flash everything, but everything fails. The error stated is FAILED: remote failure. I am not sure if this is related to my developer options being turned off, but I think it might be.
Is there a way to turn developer options on while in fastboot mode or perhaps a way around this error? The reason I am stuck in the fastboot is because the boot image can't be validated, I am not at the fastboot by choice, haha.
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Strephon Alkhalikoi said:
No. If your recovery is still stock, flash the Android N Preview 1 OTA or an Android 6.0.1 OTA image from Google. One of those will restore your Nexus to operating condition, and from there you can try again. If your recovery is TWRP, flash a custom ROM.
Click to expand...
Click to collapse
I apologize for my ignorance since this is all new to me, but could you explain a few things to me.
Is this what you're referring to when you say Android N Preview 1 OTA: 'https://developer.android.com/preview/download.html'
Secondly, in order to flash these, am I still following the steps I was before, or should I be following a new set of steps?
You don't need the N Preview anymore. Download your Android 6.0.1 image from the Google page and flash using the instructions given on that page.
I went to the page and followed the directions. Still doesn't work. The flash-all script reboots after the first two commands, which lock the phone. But even then, it is still giving the error FAILED:remote failure.
me too!
I seem to be having the exact same issue! i just bought a Nexus 6 online that wasn't booting, it would only show a green led when plugged in. so here I am doing everything I can think of to fix the issue but then I get hit with the "remote failure" when i try to oem unlock the bootloader! (and since the phone wont't boot i can't check the "unlock bootloader" box in the developer options) so yeah I am going to keep researching this but if anyone has any good ideas about to get around the bootloader being locked please jump right in.
anyways I may have deeper issues, the battery will not charge. i know this because when i load up the fastboot menu, which i have to do by holding the buttons while plugging it in, it should say battery charging but all it says is battery ok
I also can't load recovery because when im in the fastboot menu and i choose recovery the phone freezes and the green led comes back on... *sigh*
They have the full ota packages posted on Google site now you can and push through the stock recovery
Here just make sure you get the shame version
https://developers.google.com/android/nexus/ota#hammerhead
Sent from my Nexus 6 using XDA-Developers mobile app
I have the OTA. I also installed Wugs toolkit.
My phone is in fastboot mode due to the boot image not being able to be validated. I didn't voluntarily open up fastboot using the shortcut.
The phone is UNLOCKED until bootloader is rebooted, then it is LOCKED. If I click start, it becomes UNLOCKED again. Wug's toolkit tries to UNLOCK the phone even while the phone says it is UNLOCKED. I don't think the phone is actually UNLOCKED, however whenever it tells me it is UNLOCKED, I try to proceed with flashing and it gives me a remote failure message on each command.
The next thing I am going try is the drivers and Wug's toolkit has a driver option, so I will try that. Besides the drivers, any other ideas?
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Strephon Alkhalikoi said:
You seem to be inexperienced in rooting Android devices. If you aren't, I apologize for the assumption. However, you should learn how to use adb and fastboot without relying on the toolkit. Toolkits tend to hide diagnostic messages that adb and fastboot generate while running. This missing information makes solving problems much more difficult.
Click to expand...
Click to collapse
I am inexperienced, I stated that earlier. I have check a bunch of different forum posts and a bunch of different guides. Nothing seems to be helping and it seems like such a simple problem, a boot image that can't be validated. I am not trying to do anything special with my phone, I am just trying to get it to work. I woke up and it was stuck in this 'AP Fastboot Flash Mode (Secure)' mode. It is very bare bones, not even similar to the screens within videos I have seen. One moment the phone says it's UNLOCKED, the next it's LOCKED.
You are the expert, I am not. I am merely following your directions and they don't seem to be working. I did some outside research, came to a toolkit. Toolkits are great for beginners, especially since they are UI built, are built by someone who knows the area of interest, which makes researching easier and more efficient, but on top of that, it seems to be getting me much farther than your advice, although nothing is successful at this moment.
Here is a little more context into my situation. My phone seems to be recognized by Fastboot, but not ADB (From what I found, fastboot will find devices in fastboot, and adb will find devices functioning normally, don't know how true that is.). In addition, my phone seems to switch from UNLOCKED TO LOCKED after reboots, but can become UNLOCKED again if I push ANY button. Every command I issue (i.e flash bootloader, flash radio, flash system, flash userdata) result in the message, FAILED:remote failure, which I am not sure how to avoid (I have googled, checked these forums, checked other forums and there doesn't seem to be much, if any documentation on the error), but I think it is related to the fact my developer options are turned OFF. My next course of action is to install new drivers (I checked my drivers which are said to be up to date, I also installed google USB driver through the sdk, but now I am going to look into an adb or universal driver?) and attempt to rerun everything successfully.
If you have any other ideas, or don't think its the drivers, feel free to bring it up.
As a couple of fellows said before, try this:
https://developers.google.com/android/nexus/ota
Flash a FULL OTA from the link above, not a factory image. To flash any OTA you don't need to be unlocked. I think you might be confusing the terms (with the OTA you don't have to flash anything using fastboot)
In the link there are the instructions, it's pretty straight forward and easy if you have the correct drivers installed.
OTA requires that u can startup into recovery, I cannot I can startup fastboot through key combo but when I go to select recovery the green led comes back on and the screen displaying the fastboot options remains static
I think the phone freezes because it does not appear to be able to use the battery. though there is a firm battery connection it will not charge or power on without being plugged in. maybe when I select recovery I can quickly unplug and replug the USB and maybe hold the power button to try to simulate a successful reboot.. idk just thinking aloud and working with what I got..
I also can not start in recovery mode and the OTA requires ADB, which isn't recognizing my device. I have also stated that I have followed those instructions, and nothing resulted from them, except the same messages I have been stating these last few posts.
I will try this first chance I get later tonight..
http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Listen the ota doesn't get installed through fast boot, you have to select recovery through the fast boot then install the update by pushing it as bootloader does not need to be unlocked!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Qwertyismypw said:
Ok, well it seems we are at an impasse. You seem to think I can do something, so I am going to show some pictures of my screen. Its going to be blurry because I had to take it with my computer, so I apologize, but I will elaborate on each picture.
Click to expand...
Click to collapse
The first two pictures are when the phone is 'UNLOCKED'. The second two pictures are when the phone is 'LOCKED'. The moment I press anything in 'LOCKED' mode, the little android man goes away, and it becomes the first two pictures. WHENEVER I push a button in 'UNLOCKED' mode, nothing happens, except in the bootloader logs screen says, 'FAILED TO VALIDATE BOOT IMAGE RET -1'. I have done everything on that OTA page in every way possible. It has done me no good.
Ok, I made a little progress I think. Wugs toolkit allowed me to use TWRP on my phone and ADB is recognizing my phone now. There are a lot of options within TWRP though, so I am going to look through them all for anything relevant. Anything I should keep an extra eye out for?
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
If you can use twrp just download a custom ROM to your phone and move it over to SD card and flash it, then you will be able to boot and unlock the bootloader in developer ootions, that is your best bet, if you keep getting force closes after flashing a custom ROM your going to have to do a factory reset from within twrp
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have an SD card, can I move it to the internal storage? And how exactly do I do this? I can't copy/paste anything into the phone (it says the phone doesn't actually exist, even though adb is recognizing it as in recovery) or do I sideload it? When I try to sideload it though, the device disappears (and device manager sees nexus 6 under other devices, but the driver isn't up to date and no drivers seem to work. I've tried the google usb driver with no luck.) and it won't allow me to sideload it.
I just received my new oneplus 3t
After setting up the basics I updated to Android nougat
It gave an error,
the phone reboots, asks for my code, entered my code started decrypting, got stuck, after 10 mins the phone reboots and the cycle repeated.
Called the help desk, got into recovery mode, wiped everything and now it keeps rebooting into recovery mode.
Is there a way to get out of this?
guusguus said:
I just received my new oneplus 3t
After setting up the basics I updated to Android nougat
It gave an error,
the phone reboots, asks for my code, entered my code started decrypting, got stuck, after 10 mins the phone reboots and the cycle repeated.
Called the help desk, got into recovery mode, wiped everything and now it keeps rebooting into recovery mode.
Is there a way to get out of this?
Click to expand...
Click to collapse
What do you mean by "everything"? If I guess correctly, just get the full 4.0.2 and sideload it from stock recovery.
nvertigo67 said:
What do you mean by "everything"? If I guess correctly, just get the full 4.0.2 and sideload it from stock recovery.
Click to expand...
Click to collapse
I mean the hard reset, kind of a noob here.
I have the option to install from internal storage but the customer service said that might break my phone or something.
guusguus said:
I mean the hard reset, kind of a noob here.
I have the option to install from internal storage but the customer service said that might break my phone or something.
Click to expand...
Click to collapse
I'm pretty sure atock recovery has the option to install via adb sideload - but I had to admit, I've never seen the stock-recovery...
nvertigo67 said:
I'm pretty sure atock recovery has the option to install via adb sideload - but I had to admit, I've never seen the stock-recovery...
Click to expand...
Click to collapse
Well I don't wanna mess around before I **** up my warranty. In that case I would have no phone and no money.
guusguus said:
Well I don't wanna mess around before I **** up my warranty. In that case I would have no phone and no money.
Click to expand...
Click to collapse
Boy, you own a OnePlus device:
https://oneplus.net/nl/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
One of my main reasons to go for oneplus!
BTW: these devices are really hard to brick - and if you have bricked it, there is an unbrick-tool...
BTW2: adb sideload does not unlock boot loader or make 3t explode. sideloading a rom is just an other method to update stock roms.
nvertigo67 said:
Boy, you own a OnePlus device:
https://oneplus.net/nl/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
One of my main reasons to go for oneplus!
BTW: these devices are really hard to brick - and if you have bricked it, there is an unbrick-tool...
BTW2: adb sideload does not unlock boot loader or make 3t explode. sideloading a rom is just an other method to update stock roms.
Click to expand...
Click to collapse
I have exactly the same problem. Do we have any stock ROM we can try to use to install it via recovery? Cos I can't access to internal storage, and there's an option in recovery to that (but i have nothing on it...)
Same issue just today, download adb for your computer, download the file from one plus and sideload it. I had to place the file in the adb folder on my computer to get it to work correctly.
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
One plus 3T stuck in recovery no acces to internal storage PC
Helle everybody,
A couple of weeks ago i unlocked my boot-loader of my one plus 3T.
I was also planning on rooting my phone and flash a custom recovery but i could not acces the internal storage of my phone through my laptop (win 10). So after a couple of hours trying i decided this was to complicated for me and just went on using my phone without a custom recovery/rooting... but with my bootloader still unlocked.
Today i received an OTA update and installed it. Now i have a big problem i am stuck in TWRP recovery mode and still cant acces my internal memory through my pc.... so i cant flash the factory ROM and reboot my device. Does anybody know how i can get acces to my internal memory or how to get my device out of TWRP recovery mode? I am really a beginner so please explain clearly.
Greetings Bas
baswillems123 said:
Helle everybody,
A couple of weeks ago i unlocked my boot-loader of my one plus 3T.
I was also planning on rooting my phone and flash a custom recovery but i could not acces the internal storage of my phone through my laptop (win 10). So after a couple of hours trying i decided this was to complicated for me and just went on using my phone without a custom recovery/rooting... but with my bootloader still unlocked.
Today i received an OTA update and installed it. Now i have a big problem i am stuck in TWRP recovery mode and still cant acces my internal memory through my pc.... so i cant flash the factory ROM and reboot my device. Does anybody know how i can get acces to my internal memory or how to get my device out of TWRP recovery mode? I am really a beginner so please explain clearly.
Greetings Bas
Click to expand...
Click to collapse
Use this...
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Ty
Thanks
Hey guys,
just received this phone from a friend and am trying to fix it.
I can boot into system, which crashes about 1sec after displaying the first welcome animation after the boot screen and just reboots then.
I can also boot into Recovery and Fastboot but the bootloader is LOCKED. To unlock it I would have to first add the account in developer settings, but I cant reach that screen at all.
What are my options here? Flashing official roms via MIFlash is not doing anything (4sec flash, green success message but no reboot, and no change) and I cant flash anything else due to the locked BL?!
Ordinary folk can't flash fastboot ROMs with a locked bootloader. It can only be done by EDL flashing, which requires an authorised account.
You need to open the back and use the test pin method to put the phone in EDL mode. The location of the pins are near the battery, a YouTube video will show you the exact location and which pins to bridge.
Despite numerous guides suggesting it's possible for anyone to EDL flash the phone using Qualcomm tools, I've never yet heard of anyone getting it to work. The only way to EDL flash is via an authorised account. You will need to ask on the K20 Pro telegram group for details of someone who has an authorised account. Depending on who you find, you'll need to pay between $20 - $40 US. They will then arrange a time with you when they can remote onto your PC and flash the phone for you, with their account.
I gave the same advice on here a couple of weeks ago and they found someone to do it for $22 fairly quickly.
[Bricked] TWRP doesn't mount flash drive, PC doesn't recognise in fastboot, TWRP doesn't work with MTP
I've wiped my phone, no realising TWRP doesn't actually work with MTP or a flash drive. I've been using the flash drive when it was booted, before the wipe. So the port is fine. Flashing a recovery via fastboot just leads to an infinite loop of...
forum.xda-developers.com
So I was playing chess and the phone froze, I attempted to restart the phone, but it wont come back on. there is no physical response from the phone, but when plugged into my PC via the side port I get the "Qualcomm HS-USB QDLoader 9008 (COM3)" listed as a device. no button combo / timeing combo I've tried has managed to start the phone. All I want is the photos and videos off the phone. If anyone can help it'd mean the world to me.
are you still trying to find a solution to this problem? a quick google search seems to suggest it may be possible to get your data back, I can dig a little more if you're still trying to work on this.
so far I've found this to seem somewhat promising, but I've not too closely at it.
Recovering data from Mi 4c able to get only to fastboot
my phone has fallen and it cannot boot. The only accessible thing is fastboot, but even there I cannot flash TWRP. When I try to flash TWRP 3.1.1 or 3.1.0 I get: >fastboot.exe flash recovery twr...
android.stackexchange.com
healerdan said:
are you still trying to find a solution to this problem? a quick google search seems to suggest it may be possible to get your data back, I can dig a little more if you're still trying to work on this.
so far I've found this to seem somewhat promising, but I've not too closely at it.
Recovering data from Mi 4c able to get only to fastboot
my phone has fallen and it cannot boot. The only accessible thing is fastboot, but even there I cannot flash TWRP. When I try to flash TWRP 3.1.1 or 3.1.0 I get: >fastboot.exe flash recovery twr...
android.stackexchange.com
Click to expand...
Click to collapse
I will give this a shot and report back, thank you I have not seen this article despite my hours and hours of digging. Saw your reply on reddit too.