[Q] Recovery - Samsung Galaxy Nexus

My Verizon nexus is stuck in boot loop. My volume up button does not work so i cant get into fast boot. Is there any other way that i can get into recovery to nandroid? Or any odin methods i can use to get it back without erasing internal storage preferably? If there is no way possible then i assume i will have to flash stock images.
-Thanks much

Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app

wisefreakz said:
Take a look at this... It may give you some guidance.
http://forum.xda-developers.com/showthread.php?t=1827685
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895

bk201doesntexist said:
why would you suggest an unsupported tool to reflash/update a fw, of a Nexus? just because it's made by samsung, doesnt mean that samsung supports it, and the flashing through odin.
OP, use FASTBOOT, it's the tool Google INSTRUCTS you to use to recover a Nexus device to factory status.
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Really?? Can you read well??
1) his vol up is not working... So no ADB for fastboot commands.
2) i used the word GUIDANCE... Way different from YOU HAVE TO or MANDATORY.
Giz...
Sent from my Galaxy Nexus using xda app-developers app

Weel, in order to reach the recovery is quite simple. If i'm not wrong, you just have to install correctly adb driver in your pc and, once installed the driver and plugged in the device, you just have to open cmd or terminal or whatelse depending on your os and write "adb reboot bootloader" without "
Or even easier (but you need root), install rom toolbox (both free or pay, your choice) and inside there's an option to choose where to reboot, bootloader, recovery or simple reboot.
EDIT: @wisefreakz: fastboot it's necessary only for fastboot command, for adb command the device could be running (ie when you get a bootloop you're not in fastboot but, instead of pulling off the battery it's better to prompt a good adb reboot), isn't it?

Thanks much. I used the link provided. Since I'm back on cna I can boot from the power menus. Appreciate your time
Sent from my Galaxy Nexus using xda app-developers app

Related

No operating system on phone

I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
I did a factory reset on my galaxy nexus. I also by mistake erased my internal SD card. So now my phone only boots as far as the google screen because there is not ROM to boot into and when you connect to a computer it doesn't recognize the phone. How do I get a rom on my phone so it works again.
Thanks
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Can you boot into fastboot? (Hold the power button and both volume buttons). I would boot into fastboot and reflash the Stock images. Also want to specify which variant you have.. GSM or CDMA if CDMA, verizon or Sprint?
Factory reset from stock or a custom recovery will not wipe the system partition. If you formatted the system partition from a custom recovery you can boot back into the custom recovery and adb push a ROM to your sdcard
Install the drivers on the computer. Then put the phone in fastboot mode like uber mentioned. Then push the rom to the phone and flash it in recovery. If you didnt install a recovery either, youll need one of those too.
Yeah hard to tell by her post if her bootloader is unlocked or not. I didnt think it was possible to wipe system without unlocking the boot loader and flashing a new recovery. Which means she needs knowledge of fastboot to even set that up.
The more i read the OP the more it sounds like unless she bought a used rooted phone off ebay. This thing is stock and just needs to boot to stock recovery and perform a factory reset from there. And that her system is fine.
With then phone off, hold down both volume buttons. Then hold down the power button, once it boots , use the volume keys to cycle and the power button to select. Navigate to recovery and perform a factory reset.
Sent from my Galaxy Nexus using Tapatalk 2
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Fire n mage said:
Lol i just fixed this on my brothers phone, Odin a stock tar, then reroot/install and CWM
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No.
Thanks for all the replies. My bootloader is unlocked. I'll give it a try and let you know how it turns out, thank you
Sent from my HTC-X710a using XDA Premium App
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
AshleyPem28 said:
Also my phone was rooted and GSM
Sent from my HTC-X710a using XDA Premium App
Click to expand...
Click to collapse
Doesn't matter if its GSM or rooted. Fastboot is independent.
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Plug in your phone via USB, in Fastboot mode.
Does it show in the device manager? It might not be called 'Galaxy Nexus', might be called something Fastboot related. It might be in the USB section.
XP:To open Device Manager, click Start, and then click Control Panel. Click Performance and Maintenance, and then click System. On the Hardware tab, click Device Manager.
7: Hit windows key, type in "Device Manager"
If there's a yellow triangle next to the device, the drivers on your PC may be not working correctly.
If it is working correctly, the easiest option is to load the Galaxy Nexus Toolkit, and flash stock ROM.
You installed the drivers as mentioned I take it?
AshleyPem28 said:
I can boot into fastboot and clockworkmod recovery, but the SD storage is blank. The computer won't recognize the phone. I can't seem to fix it and it's driving me crazy not having a phone. Please help!!
Sent from my HTC-X710a using xda premium
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Convert to latest yakju/takju/mysid (incl JB) / Return to stock
Take a look at step A. Install the drivers. Note you should also be able to set up the adb drivers while your phone is booted into a custom recovery.
follow the instructions here: https://developers.google.com/android/nexus/images
Install the drivers, then flash the stock image in fastboot, nothing to it.
Whoa there are females on this forum!!!!????? <Sound of a hundred myths shattering>
But anyway, why dont u just flash fastboot stock images?
Whoops, ninja'ed.
psycho2097 said:
females
Click to expand...
Click to collapse
Pluralizing the word is likely over-optimism on your part :laugh:
CMNein said:
Pluralizing the word is likely over-optimism on your part :laugh:
Click to expand...
Click to collapse
Damn, it's getting sexist!
Mach3.2 said:
Damn, it's getting sexist!
Click to expand...
Click to collapse
Well its bound to when there's 40k males n 40 females(i m taking 1-2 per current device)
THIS. IS. NEXUS.
Ash just install the drivers for the galaxy nexus, download a rom like aokp (the "maguro" version is the gsm version. Dont flash "toro" versions those are for cdma ) and then push it to the sd card using fastboot. All those steps are listed in a lot of posts in great detail by the author mskip and are stickied in the dev section here. Just read his posts for questions or drivers . Its all pretty straight forward once you read the right posts. Id avoid using any toolkits though, its all fairly simple stuff. And dont worry about the geeks here being surprised about seeing females. Some of them have never left the basement before. ( no offence guys , i got no problem with the homosexuals )
Sent from my Galaxy Nexus using Tapatalk 2

Fastboot

Hello, I have 2 questions regarding Fastboot for the Galaxy Note II:
1) Is fastboot supported in the Galaxy Note II?
2) If not, is there an adb equivalent of the command: fastboot boot recovery.img?
I ask because I know that adb is supported by the Galaxy Note II, and it seems that Fastboot isn't. I appreciate all help.
Regards,
Alan
Why do you believe fastboot is not supported? Fastboot only works in a special bootloader mode, you can get into with 'adb reboot bootloader'.You shoulb be able to use fastboot then. Generally there are no adb equivalents of fastboot, as they just do different things.
Sent from my HTC One X using xda app-developers app
dobbi10k said:
Why do you believe fastboot is not supported? Fastboot only works in a special bootloader mode, you can get into with 'adb reboot bootloader'.You shoulb be able to use fastboot then. Generally there are no adb equivalents of fastboot, as they just do different things.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Hi dobbi,
Thank you for your reply. Unfortunately, the command 'adb reboot bootloader' does not boot the Galaxy Note II into bootloader/fastboot mode. It just boots the device into normal mode, just like a regular restart. That is why I think this mode is not supported by the Galaxy Note II. Could it be that I am doing something wrong? I doubt it, because the 'adb devices' command works normally, so it must be that even though the adb reboot command is being sent correctly, the device somehow blocks it. Any ideas?
Regards,
Alan
Try to boot into download mode with either a jig or by pressing special buttons, I don't know them by heart, but they should be easy to find. Then issue the fastboot devices command. If you see your note, you can use fastboot.
Sent from my HTC One X using xda app-developers app
dobbi10k said:
Try to boot into download mode with either a jig or by pressing special buttons, I don't know them by heart, but they should be easy to find. Then issue the fastboot devices command. If you see your note, you can use fastboot.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Booting into download mode is easy (Vol. Down+Power+Home). But once in download mode, neither fastboot devices nor adb devices show my device. In normal mode, adb commands do work though. I have read somewhere that fastboot mode is not supported by the Galaxy Note II because it supports Odin. I am not that experienced, so I do not understand why supporting Odin means that fastboot must not be supported (why cannot both be supported?). Does this make any sense to you?
Regards,
Alan
It is possible to support both. I cannot find any real evidence that the Note II does not support fastboot, however it isn't mentioned in any tutorial or similar. Not every device supports fastboot, unfortunately, as it's a developer tool, really. And let's face it, the Note II isn't exactly what you'd call a developer device... I do not own this device, so I can't check, but it seems there's no fastboot for you
Sent from my HTC One X using xda app-developers app
dobbi10k said:
It is possible to support both. I cannot find any real evidence that the Note II does not support fastboot, however it isn't mentioned in any tutorial or similar. Not every device supports fastboot, unfortunately, as it's a developer tool, really. And let's face it, the Note II isn't exactly what you'd call a developer device... I do not own this device, so I can't check, but it seems there's no fastboot for you
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what I thought. Anyway, I really appreciate your effort in this issue. Many thanks for trying to help me out.
Regards,
Alan
Did anyone get a solution? I tried for 5 hours now to root this device using that crap ODIN **** but it just gets halway and freezes...
Puffin617 said:
Did anyone get a solution? I tried for 5 hours now to root this device using that crap ODIN **** but it just gets halway and freezes...
Click to expand...
Click to collapse
just use CF root
put it in PDA put ur device on download mode and hit start
yahyoh said:
just use CF root
put it in PDA put ur device on download mode and hit start
Click to expand...
Click to collapse
Tried it but it just gets to "recovery.img" and sits there for 15 minutes...
The Note 2 uses ODIN/Heimdal to flash recovery. It's insanely simple.
VolDown+Home+Power, then choose VolUp to get into ODIN mode.
From there, use ODIN (Windows) or Heimdal (Linux) to flash a proper recovery (ClockworkMod, TeamWin OpenRecovery...) and use the new recovery to flash your new ROM.
I use Linux so I haven't tried ODIN. Heimdal went like this:
Download TeamWin Openrecovery. Extract the recovery.img
heimdal flash --recovery recovery.img
Done.
Puffin617 said:
Tried it but it just gets to "recovery.img" and sits there for 15 minutes...
Click to expand...
Click to collapse
Close kies from task manager or remove it entirely. Just leave the drivers.
Sent from my GT-N7100 using xda premium
Something of note that no one has mentioned: ODIN requires .TAR files in order to flash correctly. .IMG files will not work. The Galaxy Note 2 Toolkit includes all tools you will need to root, add a custom recovery, flash an insecure bootloader, and convert .IMG files to .TAR files.
Maybe try Heimdall, or a different version of Odin.
Just realized how old this thread is. I'm sure you have this figured out by now. lol
Same here...!!!
Hey Bro,
I use Samsung Galaxy Note II (SGH-T889). I am facing the same trouble regarding fastboot. Very depressed to find my phone does not support fastboot..!!
Thank God and thanks to you all for this thread!
I've done everything humanly possible to fastboot
N7100 but no way! Adb works fine, I've used Odin to flash stock firmware from sammobile with pit file and everything worked well but fastboot? No way!
I've downloaded the Lastest drivers from Samsung and Google, disabled firewall and Anti-virus, run as Administrator, uninstall and reinstall drivers but yet fastboot ain't working on N7100....
Anybody who has ever used fastboot on N7100 should please tell us how, it's really annoying that I can't use fastboot on this phone.....
Bolumstar said:
Thank God and thanks to you all for this thread!
I've done everything humanly possible to fastboot
N7100 but no way! Adb works fine, I've used Odin to flash stock firmware from sammobile with pit file and everything worked well but fastboot? No way!
I've downloaded the Lastest drivers from Samsung and Google, disabled firewall and Anti-virus, run as Administrator, uninstall and reinstall drivers but yet fastboot ain't working on N7100....
Anybody who has ever used fastboot on N7100 should please tell us how, it's really annoying that I can't use fastboot on this phone.....
Click to expand...
Click to collapse
You can't use Fastboot on Note 2 cause.........it doesn't have it
Samsung uses Download mode and ODIN (which is much better with GUI than CLI Fastboot) for same purposes.
Search and read more and you'll like it
If you need more help from me, mention me in query.
Good luck !

Waiting for device no matter what

I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Do u have USB debugging on?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah usb debugging is enabled. :crying:
Unplug your phone from computer install the drivers from Samsung's website. (Google USB drivers for galaxy nexus i515) reboot computer and try again. Maybe u should install android SDK with adb and do it manually instead of using a toolkit. Those cause problems.
Sent from my Galaxy Nexus using xda premium
Its a driver problem, for sure. OP, stop being lazy please, learn from this here, and after that, like Zepius says, put your big boys pants on and do it like this
Sent from my Nexus 10 using xda app-developers app
Ohhh the universal naked drivers. I never even thought of that. Actually i did. I have installed them same issue. I have fallowed the instructions in your first link prior to starting this thread. I appreciate the help but your attempt to call me lazy is wrong. Still unable to flash cwm or anything from the computer however i was able to flash cwrm touch today after buying the rom manager premium. Still doesnt explain why i cannot do it from my computer. Mind you i attempted this on my laptop (slackerware) and i did still have issues.
I think it is somthing with the port on my phone ror maybe somthing else. Regardless, im not lazy for i do know where google is and how to abuse all of her abilities. I know where the forum search button is also.
Drivers i have tried.
Naked nexus drivers
Windows native drivers
Slackerware mobile drivers
Samsung drivers
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Sent from my GT-N8013 using xda app-developers app
5imp7y said:
I have installed and reinstalled the usb drivers like 4 times with reboots in between. I was about to root, but after root i cant do anything. The main thing i want to do is flash a custom rom. I have the gnex tool kit, it says waiting for device (option 6), and the most recent drivers are from that toolkit. I tried command pront, Fastboot reboot-bootloader, it says waiting for device. I tried adb flash recovery recovery.img it says waiting for device. I tried 2 different cables and all my usb ports on my computer.
Im at a loss. I can still transfer files from my computer to my device. My computer detects it just none of these commands... god i wish i had an sd card slot... lol
Edit:
I also tried putting it inot fastboot mode by pressing the power and wolume up / down keys. It goes to the screen and says start. All commands still say waiting for device.
I feel like this is a driver issue but idk why.... i have tried all drivers...........
i have a samsung galaxy nexus l515 verizon cdma.
Thanks!
Click to expand...
Click to collapse
Are you confusing adb with fastboot, or was "adb flash recovery recovery.img" a typo? Anyway, forget the toolkit. Get adb/fastboot binaries from the 101 & FAQ, and try:
1) booted into Android: adb devices
This should list your device with a number. If the list is empty, adb cannot interface with your gnex.
2) booted into the bootloader: fastboot devices
This should also list your device with a number. If the list is empty, fastboot cannot interface with your gnex.
Note that the adb and the fastboot interface are different. If you installed drivers and got adb running, this does not automatically make fastboot working. Boot into fastboot, connect and use device manager to scout for unknown devices. Update using naked driver if necessary.
5imp7y said:
im not lazy
And what ever the gnex tool kit installs. No matter what i get waiting for device...
Click to expand...
Click to collapse
you are lazy. you're relying on a toolkit.
please root your phone the manual way, or at least try fastboot alone so we actually know what the problem is.
Thanks yeah that was a typo. I have the adroid bianarys. Adb and fastboot. I was typing. Fastboot reboot bootloader to try and get gnex tools to see the device. No luck.
Sent from my GT-N8013 using XDA Premium HD app
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
I did root without the tool kit...? I was trying all possabilities to flash cwrm touch before i created a thread. I realize there was a typo in the op. I AM rooted but i had no recovery. Sorry for the confusion.
I rooted manually no problems. Problems arose post root. This can be marked as solved for buying the app fixed my issue. With recovery i can flash roms on the device. No need for a computer anymore. Thanks to those who didnt attack me and make me cry. To those who did well... thanks anyways....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
If you know how to root manually, then surely you must know how to boot or flash a custom recovery like twrp or cwm with fastboot.
Sent from my Nexus
Fastboot flash recovery "your recovery img here". Still said waiting for device....
Edit:
so many typos my bad it is hard to type on my phone or tablet with fat fingers.
Seriously though, to the 2 people taking time out of their day to be jerks, grow up im done with this thread.
Sent from my GT-N8013 using XDA Premium HD app
5imp7y said:
Fastboot flash recover your recovery img here. Still said waiting for device....
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host (PC/Mac) and client (device) see and recognise each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Nexus
bk201doesntexist said:
Again, driver issue. 'fastboot devices' should return your devices serial number. that command is the tell-tell sign that communication between fastboot host and client see each other.
And please try to be flawless on the transcription of the exact commands used, to exclude the possibility of typos.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
BUT! in the gnex tool kit my serial number is displayed...?
5imp7y said:
BUT! in the gnex tool kit my serial number is displayed...?
Click to expand...
Click to collapse
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Let's try and be as friendly as possible when trying to help someone.
Thanks bk201doesntexist for trying to help.
bk201doesntexist said:
Then it maybe not be a driver problem: you need to update platform-tools through android-sdk, which has fastboot/adb binaries. 4.2.2 requires it.
Sent from my Nexus
Click to expand...
Click to collapse
if not a driver issue, it must be this.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
driver: http://www.samsung.com/us/support/owners/product/GT-I9250TSGGEN#

[Q] HElP !!!!!

Help Help Help !!! I accidentally factory reset my phone and there are no OS installed. Now i can on my phone and get my phone into the recovery mode. Anyone can help me reinstall my OS ? By the way, im using TWRP. THanks :crying:
How to get into Recovery Mode
https://www.youtube.com/watch?v=1vXCyI-BpZw
Once in recovery you will need to flash the ROM you want to install.
There are nothing left in the phone. Thats why i cant flash the rom. Anymore solutions ? Thanks
Try to use nexus root tool kit, you can flash zip file from you pc to your Nexus, I've tried it many times and it work perfectly.
Toolkits are easy but not preferred. It is very easy to learn adb and fastboot. There is a site called google where you can search for information. You need to 'adb push' the rom that was installed or the rom you want to install. Some recoverys can also 'adb sideload' thats even easier.
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Toolkits are easy but not preferred. It is very easy to learn adb and fastboot. There is a site called google where you can search for information. You need to 'adb push' the rom that was installed or the rom you want to install. Some recoverys can also 'adb sideload' thats even easier.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
while I agree that learning the basics are preferred, toolkits can actually be a good way to introduce someone to learning the basics and getting past that initial "overwhelming" feeling when it comes to figuring out which commands do what. especially since I believe the toolkits like wug has an option to open a command prompt that will show you which commands are being run when you choose an option. this way a user can familiarize themselves with their most used commands, eventually letting them "builds up the courage" to give the manually entered commands a shot on their own
either way, lmgtfy.com is still one of my fav sites to use sometimes lol

Confused with rooting and TWRP

I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I am getting mixed messages with how to root. I figured I have to flash TWRP before rooting, but how do I do that with having MDA89E version? The tutorial for flashing new OTA says I have to have TWRP first??? Can someone put me in the right direction??? Thanks a lot.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Get this one: MDB08I - 6.0.0: https://dl.google.com/dl/android/aosp/bullhead-mdb08i-factory-64536fcf.tgz , unpack it fully down to the folder that has the image files in it and that can be anywhere (let's say \temp for now).
Notice that there is a batch file that can do a full flash of the OS that you'll have unpacked from the .tgz file. You'll use that once in Fastboot to flash it. Don't worry about having TWRP or a special bootloader before you do any of this. Just get into fastboot (like "adb reboot bootloader" or hold down up&down&power buttons for awhile until in fastboot). Once in flashboot:
Flash MDB08I, boot things up, set things up, make sure it seems "normal" and check the "about phone" settings, and then you should be set to do what you want with the modified image & TWRP, etc.
I don't know what I'm doing wrong but when I try to flash I get an error "fastboot is not recognized...blah."
Sent from my Nexus 5X using XDA Free mobile app
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
You need to put the extracted files from the download "flash-all.sh, flash-all.bat, flash-base.sh bootloader-bullhead-bhz10i.img, image-bullhead-mdb08i.zip, radio-bullhead-m8994f-2.6.28.0.065.img" in the same folder as platfrom-tools. From there you run the flash-all.bat in the command prompt. just did it today.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
If you are getting confused you can always use the Unified Android Toolkit to download/flash the MDB08I image automatically. It will guide you through decrypting and rooting it too.
If you want to learn and do it all manually then good luck
Mark.
dave2775 said:
I confirmed fastboot and adb are working correctly so not sure what I'm doing wrong. Just opening the batch file opens command window correct? I don't have to do anything else?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
You say that you "confirmed fastboot and adb are working correctly", but that doesn't sound right since your prior post said that "fastboot not recognized". Everyone else that's posted is on the right track and you need to be certain that fastboot (and adb for that matter) are in the correct path or they won't run or be recognized. It's not automatic. You need to either modify %PATH% var in windows, but that's semi-complex, or take the easy road, and move a copy of fastboot & adb to the same folder your image files (.img) are in. Also be certain to move the 'flash-all.bat' file(s) to the same place.
Change your directory to be where all those files are. Be certain the device is in fastboot mode and then make sure it's all working by doing this (or these) commands:
Code:
c:\{place-where-it's-all-at}: fastboot devices
That command should list some number which is the device number which verifies that fastboot is recognized and that the device is recognized.
you can do the same thing with adb (adb devices, look at the number).
---------------------- If that works.... -----------------
Stay in that folder and do the flash-all.bat (OK, I don't recall the exact name of their everything flash file, but I think it's that). It takes some time, but I've used these instructions to help a couple people through this.
Of course, mskip's way is also fine. Whatever works is good. -- Good luck. You're no where near being bricked and in good shape to get this done.
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I thought I wasn't able to do that without flashing the image first. Anyway ibwas able to figure it out. I did try to flash TWRP and root with your tootkit but got a nessage " recovery not recognized" or something to that effect. Any idea?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
The way I've talked about flashing the image, you don't need TWRP, or anything before you do it, other than what I said. If someone has now put up a zip version of the image, then yeah, you'd need custom recovery, but you don't need to use a zip image. It's less confusing just to use the native stuff and fastboot.
Is fastboot working or not. Are you sure you are getting the phone into fastboot? Can you get output from a "fastboot devices" command? Also, please give us the exact error messages. Write them down when you see them. It'll help whichever of us is trying to help.
I helped someone with this type of problem over here http://forum.xda-developers.com/showpost.php?p=63439400&postcount=17 , so maybe reading that will help.
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
I was able to flash the image over with fastboot so I'm now on the OTA. My question now is with flashing twrp. When it prompts within twrp to allow modifications or keep as read only? That's where I'm stuck now. Thanks for your help.
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Good. There's no point in installing TWRP at all unless you allow modifications. Allow them and tell that screen to go away forever. Good luck.
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
dave2775 said:
Yeh I figured that but never came across if before with other phones. Would you know if its an excessively long boot time after first flashing it?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Once you get to this point (installing TWRP), it's best to find & follow the best guide (by that I mean that people had the least problems with) verbatim. Then ask questions in that thread:
I took a quick look and this one looks fine: http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Another way to to use mskips ways, but ask questions afterward in his thread.
I don't have a 5x (or anything like it) and I only really want to comment on things I've done a number of times before. My only comment about boot "quickly" vs. "booting normally", is that the first time you've done something "traumatic" like unencrypting, or wiping something, then of course it takes longer to do a regular boot. Booting into recovery should always be nearly instant.

Categories

Resources