I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.
Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again
Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.
This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.
I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?
Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.
Related
Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James
I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful
Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James
Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!
What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?
wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!
yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.
Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App
Hi,
I bought a faulty Nexus one from ebay, thought I can fix it, as I did buy a faulty desire from ebay and was able to fix it. This time im not so lucky I guess.
So here it is:
The phone is stuck at X when booting normally.
I can access HBoot (But not Hboot USB Plug, because USB debugging is not enabled) and Fastboot USB. I unlocked Hboot. Fastboot in PC recognizes the phone but ADB does not as usb debugging is not enabled.
The phone is not Rooted
Here are my ideas so far:
Get somehow debugging on with some commands (No luck from reshearching in google)
Reflash stock rom with PASSIMG.ZIP in sdcard, but my phone does not recognize the file from my sdcard (I'm pretty certain im doing something wrong or my idea is somehow wrong)
Flash new images through FASTBOOT, but every time Signature check fails (Shipped-roms.com).
Root with superboot, but signature check failed here too.
Flash a recovery, signature check fails.
I will reguraly update my tries
Please suggest correction to my ideas or suggest new ones!
Help will be much appreciated!
I admit it, the phone might be briked, but I want to make sure that I have tried everything before I abandon this project.
And ofcourse I have no Warranty.
What file are you using for passimg.zip? Make sure it's not a zip inside a zip.
What images are you using via the fastboot flash command?
Sent from my Nexus One
You didn't unlock the bootloader, it seems - because if you did, it wouldn't be checking signatures, and you'd be able to flash anything.
First of thanks to both of you for helping.
I'm pretty sure that i do not have zip inside zip and I downloaded them from shipped roms.com -> android -> Passion-> PASSIMG_Google .... .ZIP, (Then renamed it ofcourse) Is there a difference what version of android i use?
The issue with this is, it checks the SD CARD and does not find anything. I have seen from google that the most common issue is that it starts to check the .zip file but then aborts. Does the SDCARD have to be a goldcard (I do have a goldcard but it might be faulty, right?)
I tried fastboot flash PASSIMG_Google.... .ZIP; Fastboot Flashall ( With having boot, recovery, system in my fastboot folder)
Maybe I should try to flash everything the .zip has in it seperately because that succeded for boot, system and recovery but I was too afraid to flash every partitation (Like Radio which seems to be the scariest and the most easiest way to brick phone)
For the third answer, I have ***UNLOCKED*** in bootloader in purple and top on the screen.
Once again thanks and keep suggesting!
Unpack the ZIP and flash each image separately.
Leave the radio as is, if it's updated enough (5.08 or 5.12). In any case, fastboot won't allow you to flash bad radio - and the risk of bricking the phone using fastboot is near 0.
For passimg.zip, you need to download the FRG33 shipped ROM from shipped-roms.com then EXTRACT the zip file that is inside the zip that you downloaded. Rename that file to passimg.zip
For fastboot, flash boot and system seperately.
When you boot the device normally, do you see the lock icon below the four colored x?
Sent from my Nexus One
Okay,
Did it one by one (PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip):
Succeeded:
Boot, Recovery, System and Userdata (that was only 3Kb)
Failed with signature check (Remote:Signature check failed):
Splash1, spcustom,
Did not do:
Radio
I'm going to post more details:
When booting up, it displays the X normally with the unlocking badge on the bottom of the screen and vibrates once. Then it goes black for a second or even less, the same images comes on and then it vibrates 6-7 times.
now that you successfully flashed the stock recovery, cam you boot into it?
Sent from my Nexus One
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
http://forum.xda-developers.com/showthread.php?t=710937
Thanks, Well thats it then for now, just have to figure out what to do now
Sounds like you need to get the PASSIMG.zip method to work, or unlock and flash a new recovery like amon ra, and flash a full rom with sig checks off.
siimplangi said:
Nope, it does that what I described on the previous post
Oh and what's more it randomly during no activity being in fastboot vibrates as well for 5 times or so. It does this rarely but it's there
Click to expand...
Click to collapse
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
any solution?
efrant said:
Ok, but can you boot into recovery? In other words, boot into the bootloader and select recovery.
Click to expand...
Click to collapse
hi guys.i have exactly same situation.
does anyone have a solution fir this?
kobi_eidelman said:
hi guys.i have exactly same situation.
does anyone have a solution fir this?
Click to expand...
Click to collapse
Did you try all the solutions suggested above (passimg, fastboot flash, etc)? If yes then no I don't think so.
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
EDIT: What I did from beginning was followed this video "How to Root the HTC One-FlamingArio"to the point where you try and flash the recovery fastboot. That didnt work so after trying to fix that I tried How To Root HTC One & Unlock Bootloader - Easiest & User Friendly- The smoking Android ( super boot a 1 click install) that made my bootloader screen turn to tampered. after that I tried One_M7_All-In-One_Kit_v1.
Note in all in one kit I did erase cache and standard recovery works fine, I've re-installed it may times.
Cant post links yet but I gave video names.
EDIT: when I do the cmd fastboot devices my device shows up when I do adb devices nothing shows up could this be part of the problem?
Thank you all for your help, I re-installed all the programs on my laptop and redid all the steps and it worked. Bye!
Try this in ABD fastboot erase cache then flash the recovery again i hope this helps:fingers-crossed:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Tonberry23 said:
Hello today I attempted something that I thought was going to be a quick video tutorial fix. I tried Rooting my HTC one. I followed several guides and read many posts I easily managed to unlock my phone. The problem started when trying to flash the recovery onto my phone, first I tried through commands: fastboot flash recovery and I received the error (FAILED data transfer failure unknown error) I've searched for 7 hours looking for a fix. Since I cant root reverting back to a fresh install is impossible, I cant find a RUU for telus, (I live in canada). I just don't know what to do, when I try to flash anything my bootloader freeze, drivers are up to date, tried restarting computer. Used One_M7_All-In-One_Kit_v1.0 doesn't work. This is a nightmare come save me before I jump off a cliff.
Click to expand...
Click to collapse
Keep an eye on this thread http://forum.xda-developers.com/showthread.php?t=2302870
Many people are looking for the Telus RUU.
Can you still access standard recovery? If so try reverting to factory settings (all data will be lost) and try to boot.
If you can get it to boot you should have more luck in trying to root your device.
I know that I had some issue's trying to get root on my device. But once I got S-off with revone, I was able to install root no problem.
ArmedandDangerous said:
What did you do from the beginning? Could you post a step by step traceback of what got you to this point? Let's see if you missed any steps
Click to expand...
Click to collapse
But I would agree, if you can post the steps you have taken so we know where the bottleneck is.
Hope this helps you out bud
Still need help
Tonberry23 said:
Still need help
Click to expand...
Click to collapse
Nice to see you sorted it
Assuming you have actually flashed a recovery image to your device, you will then need to push a ROM to your sd card so that you can flash it in recovery.
Just do the following:
1. I am guessing you have the HTC drivers installed on your PC.
2. Download the attached adb.zip and unzip it to a folder on your C drive and call the folder whatever you like.
3. Boot your device into recovery and plug it in to a powered USB port on your PC.
4. Navigate to the folder that you just created on your PC and copy your ROM zip into it. rename the ROM zip to 'rom.zip' to make life easy.
5. Inside the folder, press and hold the shift key and right click in a blank part of the window and select 'Open command window here' (screenshot attached).
6. Type 'adb push rom.zip /sdcard' (don't use the quote marks)
7. Press 'enter'
8. Once the zip has finished being pushed to your sdcard, you can reboot into recovery and then flash it as normal.
EDIT: That will teach me not to read to the very end of a post. I'll leave this here for someone else.
I recently formatted everything on my nexus 6 and I mean everything, the OS too. And I can't fix it, there was nothing on the forums or threads about this and how to fix it. Could you please help me?
Boot into the boatloader and flash the fastboot image.
Sent from my DROID Turbo 2
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Big-Blunt said:
I have Ben an apple guy for 5 years just bought the nexus, I know how to get in to the boot loader but how do I flash the image? I tried downloading the image from the Google developers website but it said it failed ins
talling it!
Click to expand...
Click to collapse
you cant use the flash-all, you need to flash each part separately. ynzip the file, then flash each .img file sepately. btw, ive deleted the whole os before. if you already have twrp installed, it wouls be a much easier fix using twrp instead.
How do I unzip the file in the boot loader?
Big-Blunt said:
How do I unzip the file in the boot loader?
Click to expand...
Click to collapse
i dont remember the program i used on my laptop, maybe 7zip.
The file downloaded from Google has a second zip inside. Unzip twice with 7 zip. The system image is inside the embedded zip file.
I assume you have the SDK from Google... Place all image files in the platform tools folder. I rename the images boot, radio, system, etc. to simplify typing the commands when actually flashing the images. DO NOT add the, " .IMG" when renaming.
Then:
Fastboot flash bootloader bootloader.IMG
Fastboot reboot-boitloader
Then same for system, radio, data and cache with out the reboot line.
When all files are flashed then fastboot reboot and enjoy
My brains are exploding rn, idk what or how to do anything, maybe u will think I'm dumb but I don't know what u guys are saying, could anyone post full instructions on how I would do it
The ONLY thing that you need to revive your device is alive bootloader. Every OS has its bootloader, and it determines what to load before system loaded.
I guess you did that foolish things on recovery. Then it won't kill itself of bootloader for sure.
Then there's always a chance. Try to boot into bootloader and switch it to fastboot mode.
Just flash stock rom image provided by google as described above.
You need to do some googling about fastboot and/or look for the beginners guide posted in the forums. You could use wugsfresh toolkit as well. I'm not being a douche not linking them,I'm to stoned
Google anything you don't understand
Sent from my Nexus 6 using Tapatalk
Do you know if your bootloader is unlocked?
You say you're an Apple guy - are you using a Mac? If you have access to a Windows machine I suggest you install Wugfresh's Nexus Root Toolkit and use the "Install & test drivers" button to set up the required drivers to connect your Nexus 6 to the computer. The walkthrough is comprehensive and extraordinarily simple - brilliant piece of programming. There is no Mac version.
Download the factory image (https://developers.google.com/android/nexus/images?hl=en#shamu image MMB29K).
Find the Fastboot/ADB programs on the web (I may have used the Minimal ADB & Fastboot tool, I can't remember exactly) and create a directory containing both programs plus their associated bits and pieces. I recommend making the path as simple as possible - e.g. C:\ADB for ease of navigation ( see below).
(While reading up on this, I came across this, which you may find useful - http://www.android.gs/install-set-up-adb-mac-os-x-linux/).
Unzip everything in the factory image, including the zip inside the zip as Larzzzz82 said, then copy the unzipped *.img files into the ADB Fastboot directory.
Boot your N6 into bootloader.
Open a CMD window and navigate to the ADB directory.
To check that you're connected, type (you don't need caps, this is just to make it clearer) FASTBOOT DEVICES. You should see something like "djdgkdjhgkdfj device" in response; if it's blank you're not connected - go through the driver setup again to see what you've missed.
Once you're successfully connected, you can install your new image following the instructions in this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
I did ask for an expert to run a more experienced eye over them to correct any errors or to remove any pointless reboot commands, but nobody did either, so I guess they're ok. It's what I did and it worked for me. I've just noticed that it includes a line "fastboot flash recovery twrp.img" which you can ignore for the moment - though you may want to do this later when you have a working device.
Come back if you want any clarifications.
Happy new year (and, I hope, device...)
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Big-Blunt said:
I tried I guess flashing the image through the recovery mode in the mount section but it said it failed,
Click to expand...
Click to collapse
No no no you do not flash images through the recovery
Use Wugfresh's Nexus root and toolkit to restore it. Pretty easy.
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
dahawthorne said:
@wolfen69 - duck and take cover...
I was going to suggest exactly that, since I'm a big fan of Wugfresh's NRT, but recommending it doesn't half bring down the flak... that's why I recommended using it initially at least to get the PC set up properly to connect and then get on with learning how to do it manually.
Personally in this situation using the NRT is exactly what I'd do myself. But now I'm retiring to my bunker for a while.
Click to expand...
Click to collapse
That's OK if people disagree with my recommendation. People are entitled to their opinions.
I tried for hours to do it the manual way and could never get it to work. And I'm a person who is VERY tech savvy. I had a computer repair business and have written advanced linux tutorials. I gave up and started using wugfresh. Has worked great for me. Others are free to do what works for them.
If you dont flash the images through the recovery mode then how do you flash it? I cant flash through command because the phone dosent have usb debugging enabled and its not in developer mode. I tried the nexus root toolkit as well and that didnt work either. Plz i need help!
So how much of my instruction did you follow? What exactly have you tried? Step by step. If you're vague then we can't help you. Error messages?
How did you delete the OS if your phone isn't unlocked?
Sent from my DROID Turbo 2
So i put it in recovery mode and when i tried resetting to factory i accidentally clicked advanced wipe and deleted everything so now its stuck in the boot loop. What i have tried was i downloaded the img file 6.0 shamu from googles site and drag and dropped on internal memory with my pc. Then in recovery mode i went mount and selected the img and it said error.
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.