Related
Hi guys!
I received my Nexus yesterday en immediately rooted and unlocked the device. No problems so far.
I want to install a the cyanogen custom rom on my nexus but get stuck in the recovery step.
I have used the tutorial from Theunlockr . com (unfortunately I cant insert a link here because Im a new member)
Because I already rooted and unlocked my Nexus I started with ''III. Flash the Custom ROM''. I managed to start up the bootloader and click on 'Recovery'. Here the problems start, after clicking on 'recovery' a screen with a yellow exclamation shows up. (see attachment for screenshot)
Can somebody help me with flashing my Nexus with a custom rom? Thanks in advance!
Try to run "fastboot boot recovery.img" and see if that works. (Something like that anyway)
This was what I did for all my time using Amon's 1.5.3 recovery. Now that I'm on 1.6.0, I can use the normal recovery. That worked perfectly for me anyway. I also would always boot to that screen when attempting the normal recovery via the phone.
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
So am I
To run fastboot, you should simply go find the Android SDK download. Once you've downloaded that, make your way to the tools folder. Place the recovery image in that folder and then Shift+Right Click in the window. You click the option to bring up a command prompt.
In that Command prompt, type flashboot devices and verify the PC sees your phone. If so, then you can do the Flashboot command. Though you may need USB drivers. If you do need them, they're somewhere in this forum, but I've completely lost track of them.
P.S. if my initial command doesn't work... You might need to try "fastboot boot recovery recovery.img"
(Note... Don't try "Flashboot".. That was a typo )
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' ?
I am quite an android-noob.
Click to expand...
Click to collapse
got this info from the same site you posted, you just skipped the step before you started to flash the rom altogether.
II. Flash a Custom Recovery Image
1. Download the Nexus One Amon Ra Recovery Image below:
Nexus One Recovery Image (Link under Download in the first Post)
2. Save the recovery image file inside the superboot folder you used to root the phone.
3. Turn the phone off and then plug it in via USB cable.
4. Turn it on by holding down Power and the Trackball to get into fastboot mode.
5. Open a command prompt and type the following with hitting enter at the end of each line:
cd\
cd c:\superboot
fastboot-windows devices
*this is to check that the computer can see the phone (a serial should pop up if it can)
6. Then type:
fastboot-windows flash recovery recovery-RA-nexus-v1.5.3.img
7. This should flash the recovery image onto the phone.
Click to expand...
Click to collapse
The recovery img is in this thread
http://forum.xda-developers.com/showthread.php?t=611829
Click to expand...
Click to collapse
Also, you don't really need the android sdk for flashing the recovery img, but it's a good idea to download it for future use.
Can ANYONE just stop answering threads that are in wrong sections?
lazinase said:
Can ANYONE just stop answering threads that are in wrong sections?
Click to expand...
Click to collapse
Why? So that it gets moved and answered anyway? The sooner the guy gets helped out... The sooner the post gets buried.
A mod will be by to do their duty later. As the community, we may as well help in the mean time.
Man, oh man. Niceness has really lost some popularity in the virtual world, hasn't it...
Stinosss_31 said:
Do you have small tutorial or how-to how I can run 'flashboot boot recovery.img'' on my Mac?
I am quite an android-noob.
Click to expand...
Click to collapse
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
grainysand said:
If you use a Mac, you don't deserve help. Bootcamp Windows and we'll talk.
Click to expand...
Click to collapse
great help!
for a mac just use ./fastboot-mac in the terminal
Like they said, sounds like you are missing recovery. Just do the step two, you skipped it. Why flame people? He is new, might as well help, instead of making this thread longer by telling him to post in right section.
Besides, he did find tutorials and followed them, he didn't come here completely unprepared and expecting people to walk him through. We all make mistakes sometimes, specially when dealing with something we are new to, he simply skipped a step.
MOD EDIT - Thread moved to Q&A
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.
I have been searching all afternoon, here is my problem. I had issues with some radio and SPL files last night (won't verify), and someone pointed me to a newer version but they are *.img files...I've never loaded anything but the recovery partition as an image file.
I looked this up and it says it needs "fastboot"
90% of the searches tell you how to install the SDK (even though fastboot is in the title, it's never mentioned in the body of the post), thanks, I have the SDK since I got my phone, but I don't have or see fastboot anywhere in it.
So my newbie question is how do I fastboot the *.img files onto my G1, since I don't see fastboot on SDK or on my phone?
Second newbie question, when I see the directions for installing they list the fastboot commands serially...so do I have to reboot after each img load or can I just load one then the next without rebooting/power cycle?
Thanks.
GolfnWrx said:
I have been searching all afternoon, here is my problem. I had issues with some radio and SPL files last night (won't verify), and someone pointed me to a newer version but they are *.img files...I've never loaded anything but the recovery partition as an image file.
I looked this up and it says it needs "fastboot"
90% of the searches tell you how to install the SDK (even though fastboot is in the title, it's never mentioned in the body of the post), thanks, I have the SDK since I got my phone, but I don't have or see fastboot anywhere in it.
So my newbie question is how do I fastboot the *.img files onto my G1, since I don't see fastboot on SDK or on my phone?
Second newbie question, when I see the directions for installing they list the fastboot commands serially...so do I have to reboot after each img load or can I just load one then the next without rebooting/power cycle?
Thanks.
Click to expand...
Click to collapse
1.turn off the phone . open fastboot on the phone by holding back and power.
2.open up command prompt with admin priveliges. use the command "cd" for main android sdk directory, wherever you have it.
3. once found the directory, for me its X:/AndroidSDK/ , refer to the tools by adding the /tools like so: X:/AndroidSDK/tools
.
4. enable fastboot devices by typing the command fastboot devices
5. use the command fastboot flash *****.img.
if you are flahing new radio and hboot's. PLEASE flash the radio first!!!! and with the second question, you can flash the next img right after, just make sure you do the correct ones first.
I'm still missing something here
Back+power = rainbow screen, now I'm stuck because my ADB command fails here, no device detected (it works on normal power up, or even in recovery mode).
So my issue is with item #2, how can I "open up a command prompt" from the rainbow screen? gonna search on that though.
Is this a hack that I missed?
I DO see fastboot in my tools directory.
ooops androids on skateboards are gone
Think I found it....
"...you need to replace your bootloader with an unlocked G1 bootloader that has fastboot enabled..."
So my old build had it, and my new one (1.6 rooted) does not....so need a known good ROM with fastboot enabled.
haha, that only took me all day.
Help please, need a ROM that supports Fastboot
Yes, I'm an idiot...while there is tons of information here, even tutorials and walkthroughs, the amount of time I had to spend searching and reading to find what I wanted is phenomenal. I have been out of it for a while, and it's gotten much worse in many ways and better in some ways too.
What I don't understand is why so many ROM's fail to load still. The tools and processes are much better understood now but many ROM's fail at loading, at least that I tried.
There are also tons of dead links to ROM's, frustrating for someone not familiar with the site.
I want a simple fast ROM, FAST = 3.0 MFLOPS+ on LINPACK, that is reasonably stable...not having much luck so far.
THANKS! for all the help.
Alright so last night i was able to unlock my phone and root it no problem on my mac computer (which I regret and wish i did it on windows) but the phone worked great after. But after debating if I should unroot I went ahead and tried unrooting the phone but the phone would not activate, it became stuck in bootloader. Ive tried everything that I could look up online and even called google for help but they said to search online and ask the developers. Ive tried flashing the stock image back on but it wouldnt work, it kept saying ivalid boot image header fastboot reason fall-through from normal boot mode. I dont even think my computer is recognizing the phone anymore so I dont know how I would get back into terminal to flash anything. If anyone can help me I would appreciate it. I have no idea what to do now after trying for a whole day. Thanks all, hope someone can be a savior.
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
zephiK said:
Firstly, if you want help... please please please use paragraphs and lines and not 1 blob of text. It makes it extremely difficult to know your problem.
Secondly, do not ever call Google or Motorola (or any manufacturer) or any carrier for help. What you do on XDA is not their problem, that is why there is a warning when you unlock the bootloader.
Third, if you're able to get into bootloader mode then you can fix your phone by flashing the stock images. You most likely had the wrong environment or it is not set up properly to flash the stock images.
If you don't feel comfortable doing this kind of stuff, stick to using the phone out of the box rather than tinkering with it.
Click to expand...
Click to collapse
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Is the device recognized by the fastboot command when connected to either the mac or pc?
zylstrajs said:
Is the device recognized by the fastboot command when connected to either the mac or pc?
Click to expand...
Click to collapse
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
Adb is for android. You want to use the command: fastboot devices
dnasr87 said:
Yea, my bad. I typed it in a hurry on my phone.
Bootloader is the only screen I am able to get into. Whatever option I choose and hit power, all it does is flash the screen and go back to bootloader.
The stock image I download was from the google developers page but it did not work.
Will anything even work if my computer doesn't recognize the phone? If so how would I go about doing it?
I used to this this years ago and never ran into problems, just for some reason when I tried to unroot it messed up.
Is there anyway to possibly delete the terminal so I could start over and re-root it??
Anyways thanks for your response.
Click to expand...
Click to collapse
If you want to start over you'd want to be flashing the stock images https://developers.google.com/android/nexus/images
Have your phone in bootloader mode (vol down + power)
Go into the directory with fastboot and type fastboot devices.
If your environment is set up properly then it should display your device as the output. From there you can flash back to stock.
dnasr87 said:
Not sure to be exact, if I just go into terminal and enter "adb devices" nothing will pop up but if I enter cd then space and drag the android file into it, it wont say my device number anymore it'll say device. I'm wondering if I could somehow delete my terminal and possibly start over?
Click to expand...
Click to collapse
what does it say why you type
>fastboot devices
zylstrajs said:
what does it say why you type
>fastboot devices
Click to expand...
Click to collapse
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
dnasr87 said:
command not found, but all I did was open terminal and entered fastboot devices. Not sure if I should enter anything before it.
Click to expand...
Click to collapse
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
zephiK said:
You have to change directory to the folder that contains fastboot. Do you even have fastboot environment set up? You need that.
Google search on how to set it up before posting back. There are many guides on XDA on how to accomplish this.
Click to expand...
Click to collapse
I did when I rooted it then once it crashed I tried to start over but wiped my computer.. I'll re download and try again
zylstrajs said:
Okay, your environment isn't set up ideally. Follow these instructions to install fastboot and adb on your PC.
http://forum.xda-developers.com/showthread.php?t=2317790
---
Once you've done and you get a reply to the following command, you can move on.
>fastboot devices
---
open the google factory image file (using something like 7zip) : shamu-lrx21o-factory-e028f5ea.tgz
There is a folder in the .tgz file. Extract the contents of that folder to the directory listed for your command prompt (where you successfully ran fastboot just before).
> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
>fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
>fastboot reboot-bootloader
---
The device will reboot. Don't close the terminal window. Now, extract the contents of image-shamu-lrx21o.zip to the same folder that you've been working in. The folder that contains the bootloader and radio files you just flashed.
---
>fastboot flash recovery recovery.img
>fastboot flash boot boot.img
>fastboot flash system system.img
Some time will pass, this img may be sent in parts.
>fastboot flash cache cache.img
>fastboot flash userdata userdata.img
>fastboot reboot
Click to expand...
Click to collapse
I did it on my mac, if i try to connect my phone to a pc it wont recognize it because its stuck in bootloader. I have already tried connecting it
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
PaisanNYC said:
Why does this thread make me LoL so much?
This thread is all over the place. Are you using your PC or Mac right now to do this? If it is a PC, what does Device Manager say when you plug your phone in while its in Bootloader mode?
Click to expand...
Click to collapse
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
dnasr87 said:
Im using mac right now. I want to start from scratch, not sure if possible. but nothing really shows when I connect the device. I think I wipe the software off my computer. Would I be able to start doing it all over on a pc even if its stuck on bootloader and computer wont recognize?
Click to expand...
Click to collapse
Are you in the NYC area? I'd just come over with my laptop and do it for you.
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
PaisanNYC said:
Are you in the NYC area? I'd just come over with my laptop and do it for you.
Click to expand...
Click to collapse
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
not necessary some one can just use hangouts remote desktop to help you i thinks that's what they use on xda assist
Acer ADB
Your PC might not be recognizing because you got the Acer ADB of doom...
Just roll back your driver.
dnasr87 said:
Dude im in NH but at this point I will ship the phone to anyone who can fix it and I will pay you guys $100
Click to expand...
Click to collapse
Don't send it to a stranger on the internet. You never know who is who behind a screen lol
Honestly bro, if i were close to you, I'd just do it for you. I have the stock image, drivers, and adb/fastboot all set up. i'm good at fixing things, horrible at explaining things.
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.