Related
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.
@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.
Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6
simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.
OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.
op got it flashed, and ended up flashing his rom as well. so, he was successful
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything 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 heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck
Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.
mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.