Related
Ok i know a thread of this kind has probably been made a couple of times, and i apologize for this, but i have been searching every where to find a way to make my nexus one back to stock. I know once the bootloader is locked i cant reverse that but i just want to have the original stock recovery image. I currently have amonRA 1.7.0 recovery image. I have tried everything possible that i know, and as I must mention im not a really a good adb user. I mostly know how to use custom recovery images, load roms, themes, mods, etc. I have read a couple of threads where it would help me revert back original state but i just cant figure it out. I would very much appreciate it if someone would help me out and give me a step by step procedure i can use to flash a recovery image.
I currently have my nexus on ERD79 stock rom, no mods no nothing.
Firmware is 2.1(not 2.1update1)
thanks for the help!
http://forum.xda-developers.com/showthread.php?t=614850
this puts everything back to original even recovery img.. this is full instructions
and once its "unlocked" it cant be Relocked.. it stays unlocked
http://forum.xda-developers.com/showthread.php?t=614057
the PASSIMG
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not
fastboot flash recovery recovery.img
Step 13. fastboot reboot
Thanks for this but i came across this thread and to be honest i got lost after it asked to put the unziped file where i can find it.
Can you give me an idea where i could put it?
Oh and i downloaded the passimg.zip and i couldnt extract it, my comp said file is invalid.
thanks again.
Ok ill see if i can unzip it for you sir
or you can try it this way too
http://www.mediafire.com/file/e5t4504thl2ry42/recovery.rar
there you go man recovery image from the thread posted before
1. Plug the phone into the computer
2. Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
3. On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
4. With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
5.
Code:
adb devices
A device name and 'recovery' should be returned
6.
Code:
adb push recovery.img /sdcard/recovery.img
recovery.img is located on android-sdk/tools dir
7.
Code:
adb shell flash_image recovery /sdcard/recovery.img
This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
8. Reboot
Click to expand...
Click to collapse
i apologise if this seems like a noob question, but i searched everywhere, and couldn't find the answer.
I followed the steps to flash the stock recovery to my nexus, and when i boot into the recovery mode to test it, it's just a blank screen with an error triangle and a little android standing next to it.
Is this what the stock recovery is meant to be? or did something go wrong in the process?
Yeah that should be the stock recovery, you should be able to press the power button and volume up and get a blue text list saying reboot system now, apply sdcard:update.zip.... etc.
yes, thank you very much for clearing that up for me
see my guide: [UNROOT] Unroot al android devices which was also posted on the front page. this step allows you to get a stock recover image specifically for YOUR GOOGLE NEXUS PHONE, not just generic google nexus phones
hate to revive a thread thread but im having the same delima.
i just bought a nexus one from CL and it was loaded up with a 2.3 rom. Im guessing its not using stock kernals, baseband, etc etc.
Im trying to get it back to stock EVERYTHING. i know i cant relock the bootloader but other than that, i want to revert it back to what you get right when you open the box. im not even sure what a recovery image is... but if its different when u flash different roms, i would like that stock too lol.
i know about the passingimg method but i wasn't sure if thats compatible with all roms (kind of like how unlocking iphones only works with certain basebands). i also wasn't sure if that'll return everything to stock, kernal, OS, modem, radio, recovery (?), etc.
im not very familiar with adb either. can anyone PLEASE help me out?
this is the method im talking about http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
would the passingimg get EVERYTHING back to stock? or would it leave the custom recovery, kernal, or something else etc.
Hi there, I am trying to figure out what the difference between fastboot and recovery images are? It seems to me that you can flash images and radios when you are in fastboot, so what is the point of running recovery images?
Also, is the recovery image something that runs ontop of fastboot?
Read the wiki.
Know-Fear said:
Read the wiki.
Click to expand...
Click to collapse
Neither the android 101 section nor the Nexus one/ Recovery images section of the wiki contain any information as to the differences between the 2 or how the recovery image loads, perhapes you can add that into the wiki?
Basically, I would say the biggest difference is functionality...
Fastboot has very limited "on board" options, but you can do a bit more when connected to a computer, and even more with an unlocked bootloader. You're pretty much limited to flashing images normally, and the unlocked bootloader allows you to also flash unofficial images. If your phone won't boot into the system or recovery, then fastboot might be your only option.
Recovery has more "on board" options, especially with the custom recoveries, where you can flash images, make and restore backups,and also create and format partitions (among other things), directly from the phone. Connected to a computer gives you a bit more flexibility, but not much (using adb to push apks direct to the phone, whereas from recovery on the phone, you need a flashable zip).
I do pretty much everything from my phone, since I'm not always near a computer. That means I rely on recovery and the terminal emulator for the most part. Once, I needed to hook up to the computer and use fastboot to flash a new recovery, because every other optiod failed...
For me, having a custom recovery is much more useful than unlocking the bootloader. Unlocking the bootloader just makes it a lot easier to install a custom recovery. I would even venture to say that most people go direct to installing a custom recovery after rooting, or after unlocking the bootloader. Even though you can install ROMs through fastboot, it's much easier to use recovery.
The other big difference is that unlocking the bootloader will wipe the memory, whereas rooting and installing a custom recovery won't erase your memory...
I see, thanks for explaining to me the differences, but does anyone know where the difference comes from??? Does the recovery image run ontop of fastboot and call functions from fastboot to achieve its backup options or what??? If not, could you simply remove fastboot to save memory and be left with just the recovery image which persumably has more functions anyways?
There's a bit of mis-information in this thread.
Fastboot is a binary that you execute on your computer. To be able to use it, your device needs to be booted into the bootloader. There is no "fastboot image". Most fastboot commands require an unlocked bootloader. The most used fastboot command is "flash" which lets you flash images to any of the partitions on your device.
A recovery image in the recovery partition is like a mini ROM which allows you to perform some tasks directly from that partition without booting into your ROM, like applying updates to your ROM and performing backups. Custom recoveries have more functionality than the stock recovery. To enter the recovery partition, you need to boot it through bootloader (generally).
adb is another binary that you execute on your computer. It is unrelated to fastboot. It allows, among other things, transfering of files to/from your device and running a shell.
flash_image is binary that you execute on your device, or on your computer using a shell (via adb). It allows you to flash images to most of the partitions on your device. This binary requires root access.
I see, thank you very much for clearing up this misunderstanding. I take it both fastboot and recovery images manipulate the bootloader to achieve flashing and backup capabilities? Since on default the USB support is disabled on the bootloader, which is why you need to unlock the bootloader first so that the fastboot can send its signals to the bootloader via USB. Since recovery images can directly manipulate the bootloader without the need of a USB, therefore you can do not need to unlock the bootloader to use recovery images.
xcmir said:
I see, thank you very much for clearing up this misunderstanding. I take it both fastboot and recovery images manipulate the bootloader to achieve flashing and backup capabilities? Since on default the USB support is disabled on the bootloader, which is why you need to unlock the bootloader first so that the fastboot can send its signals to the bootloader via USB. Since recovery images can directly manipulate the bootloader without the need of a USB, therefore you can do not need to unlock the bootloader to use recovery images.
Click to expand...
Click to collapse
I think you need to re-read my post.
1. There is no "fastboot image", so I don't know what you are talking about there.
2. A recovery image does not "manipulate" the bootloader.
3. USB support is not disabled on the bootloader.
Sent from my Nexus One using XDA App
efrant
Can you explain the bootloader a bit more?
The bootloader has two very similar screens. The only differences between the two screens are the four menu options, and one screen is labeled HBOOT, and the other FASTBOOT. I assumed these to be be two operating modes of the bootloader, since the fastboot binary will only work when the phone is at the FASTBOOT screen, and not the HBOOT?
How do you refer to, or distinguish between, these two "modes"?
Also, the screen labeled HBOOT has four menu options, the first one being FASTBOOT, which merely takes you to the second screen with the FASTBOOT label.
So, just for giggles, let's call the first screen/mode/thingy HBOOT, and the second FASTBOOT...
It's my understanding that the fastboot binary communicates with the FASTBOOT 'thingy' on the phone (both parts are known as fastboot). This is similar to the adb binary communicating with adbd on the phone...
Now, with that in mind, the OPs original question seems to be related to interfaces on the phone. Wouldn't it then be fair to assume that these two interfaces we're the recovery and the FASTBOOT 'thingy' (although I actually believe he was referring to the bootloader as a whole)?
Sent from my Nexus One using XDA App
danger-rat said:
efrant
Can you explain the bootloader a bit more?
The bootloader has two very similar screens. The only differences between the two screens are the four menu options, and one screen is labeled HBOOT, and the other FASTBOOT. I assumed these to be be two operating modes of the bootloader, since the fastboot binary will only work when the phone is at the FASTBOOT screen, and not the HBOOT?
How do you refer to, or distinguish between, these two "modes"?
Also, the screen labeled HBOOT has four menu options, the first one being FASTBOOT, which merely takes you to the second screen with the FASTBOOT label.
So, just for giggles, let's call the first screen/mode/thingy HBOOT, and the second FASTBOOT...
It's my understanding that the fastboot binary communicates with the FASTBOOT 'thingy' on the phone (both parts are known as fastboot). This is similar to the adb binary communicating with adbd on the phone...
Now, with that in mind, the OPs original question seems to be related to interfaces on the phone. Wouldn't it then be fair to assume that these two interfaces we're the recovery and the FASTBOOT 'thingy' (although I actually believe he was referring to the bootloader as a whole)?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
As far as terminology goes, this is what I have read (and which makes sense to me): 1) the bootloader is the white screen with the three androids at the bottom. Yes, there are two screens, but so? It is just a menu in the bootloader, just like a menu in a ROM. It's the bootloader. 2) Fastboot is used to refer to the executable, not to the fastboot menu on the device.
Yes, I supposed you could consider a recovery an "interface", just like a ROM is an interface. Would I compare it to fastboot? Not really. Fastboot and adb are two interfaces to interact with your device from your computer. The ROM and recovery are two "interfaces" on your device itself...
Fastboot, or actually bootloader, is the part of the phone that loads when it's powered on. It also happens to have PC interface through USB and "fastboot" executable.
When it loads, it either allows user control or loads one of the bootable partitions. One such partition is ROM. The other is recovery. In fact, recovery is a small ROM with features for controlling the phone - flashing images etc. You might as well write a custom recovery that will allow you play Tetris. It's just another (but very small) ROM.
Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
************
First, I am not responsible if you damage your phone in any way.
Also you might back up your phone's data completely because after unlocking bootloader you can lose all your installed data.
*************
So, first step is unlock the bootloader. First go into
Setiing> About Phone > Press Build Number A couple of time until it shows you are a developer now > go back > Developer Options > Turn on USB debugging.
After that, go to your bootloader, by powering off your phone and once it is powered off press the Volume down key + Power button until something appears with a vibration.
Now download adb and fastboot from this link:
http://*******/1Zsyme
After downloading it, install it. And you can install it easily with no problem. Just make a folder in your windows drive of :
C:\Android-adb\
And you are good to go.
Now goto that folder (C:\Android-adb\) and press SHIFT+CTRL+RIGHT-CLICK together or just SHIFT+CTRL first and then RIGHT-CLICK and then click "open command window here".
Now connect your nexus 5 and check if your PC makes a sound like when you connect a external device.
If yes, then you are good to go. Else try connecting it several times to automatically make the PC install any drivers.
After this, go to that DOS type window and write:
fastboot devices
(press enter to activate any command)
If you it shows a serial number then you are doing fine.
After this, write this command in that CMD.exe window:
fastboot oem unlock
and wait until something pop-ups in your phone. It might be a warning, read it carefully and using your volume up or down key cycle through the options and using power button select yes. And it might reboot on it's own else restart manually by pressing the power button for 10 or 15 sec until you see your screen with a unlocked lock which means you have successfully unlocked the device.
Now after that, it's finally time to FLASH recovery file.
For this to happen you need to download CWM latest version from here:
http://*******/1Zt1Fs
It's latest for HAMMERHEAD or NEXUS 5!!!!
Now, again go to the bootloader as described in the beginning.
Now you can also copy the recovery zip file by your data cable of your phone by turning in on normally and also from bootloader.
How to do it from bootloader? Here's how too.
Now you have to be on the bootloader screen. Now goto the same CMD.exe and write:
adb push filename.zip /storage/emulated/0/
adb push filename.img /storage/emulated/0/
If you get any error ask me.
Now it might get some time to be moved to that.
(Data Cable should be attached to do so, also the RECOVERY img file should be in C:\Android-adb\ this folder to be moved to PHONE)
Now, you might have successfully moved the zip file to your phone. So now write this command to flash Recovery.img file:
fastboot flash recovery your_recovery_image_name.img
After this, it will FLASH the recovery file. Until it's installed successfully wait till then.
Once it is FLASHED, now cycle to recovery mode using volume buttons from the BOOTLOADER and wait till it gets there:
Now you will see some options, but you need to flash a zip file so cycle again using volume buttons and select anyone using power button. So select:
install zip
Now select choose zip from /sdcard
Now you are in your internal storage's directory where you moved your zip files from CMD.exe. Just select it and you are done. go back and reboot system now. And you are done.
Don't forget to say thanks if you find it helpful in any way.
Also report to me if you get any errors between in it. By the way, I didn't have any errors in my journey to do this in first time.
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
wangdaning said:
You do not need USB debugging for fastboot, you do not need to open fastboot or adb within the directory they are install in, you...
There are already guides, which are more accurate and up to date, to direct people through the process. Who uses CWM?
Click to expand...
Click to collapse
TWRP not worked for me. I use and recommend CWM. TWRP is full of bugs and does not show errors and hangs. But CWM is the best.
ddimple4 said:
You should point out and highlight that unlocking the bootloader will wipe all data.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I did mentioned but didn't highlight.
Except for the fact that CWM is out of date and not maintained for our device.
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Except CWM is out of date and not maintained for our device. TWRP is not full of bugs.
What is the point of this thread? Isn't this all common knowledge?
Google says you need to hold VOL UP, VOL DOWN, and POWER to boot into fastboot, but I've used just VOL DOWN and POWER on my N5.
fastboot oem unlock has been superseded by fastboot flashing unlock, though it still works for the N5.
You can download the Android ADK CLI tools from https://developer.android.com/sdk/index.html . Always point to the authoritative source.
You'll need to be in the \platform-tools directory UNLESS you add it to the PATH.
So far's I know, ADB will not push a file while you're in fastboot. You can just flash the recovery file from the directory you have it, e.g. fastboot flash recovery .\your_recovery_image.img.
Very nice of you to post, OP, but you've got a few things wrong in your guide. Read some others to find your errors, and keep writing, Android needs informed enthusiasts and writers.
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
GldRush98 said:
Yeah, it's 2016. Why was this thread even made? It's either common knowledge, or there are a hundred other guides about doing this.
Plus, who the hell uses cwm these days? Twrp or don't waste your time.
This whole post feels like something from 4 years ago.
Click to expand...
Click to collapse
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
Outdated for years.
ChromeJob said:
I'm still using CWM. What's wrong with that?
// Tapatalk on Nexus 4/5 //
Click to expand...
Click to collapse
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
RoyJ said:
It's outdated, no updates. Last I heard some of the CWM team are now contributing to TWRP. It's pretty much the official unofficial Android custom recovery at this point. You will also have a lot of issues trying to flash or update on older versions of TWRP or other recoveries that aren't updated due to file structure changes in newer Android versions.
Click to expand...
Click to collapse
I see the light. CWM team seem to have abandoned Helium, too; no longer works on systemless root. That's second or third app they've simply gotten bored with and not continued development.
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.