Related
I'm curious to know whether Heimdall will work with Nexus S devices. As the device is developed by Samsung and reasonably similar to members of the Galaxy S range it's fairly likely that it will. The main requirement is that the device is running a particular type of Samsung secondary bootloader, referred to by Samsung as Loke.
Without an actual dump of the secondary bootloader the simplest way to check is whether or not Nexus S phones have "download mode". If a Nexus S owner could confirm whether or not they have download mode that would be great. If so could they please share the product ID and vendor ID of the Nexus S? These can be retrieved in Windows by doing the following:
Instructions for Windows Vista / Server 2008 (Should be similar for XP & 7)
1. Open up Device Manager on your PC (Control Panel -> System -> Device Manager).
2. Under Universal Serial Bus Controllers, find the Samsung composite driver (if in download mode) or your whatever Nexus S driver you're currently using (if not in download mode), the latter of which may depend on phone settings.
3. Right click on the driver you found in the previous step and chose Properties.
4. Go to the Details tab and select "Hardware Ids" from the "Property" drop down list.
5. Copy and paste your hardware IDs and fill out the rest of the form below.
With the existing Galaxy S variants there are already a few different ways to access download mode, so the way to access it on the Nexus S may be different again, but hopefully similar. As a reference, the way to access it on a GT-I9000 is to turn the device off. Hold the home and volume down buttons, then turn on the device. Don't release the the buttons until the device has boot into download mode. If the phone boots up normally then you know that a particular key sequence didn't work and you should turn off the device and try another key sequence.
Any information would be much appreciated.
I thought that google device use fastboot for flashing (that's the official tool in the sdk)
omrij said:
I thought that google device use fastboot for flashing (that's the official tool in the sdk)
Click to expand...
Click to collapse
fastboot is a tool used to interact with HTC's proprietary bootloader. It is certainly possible that Google co-developed or licensed this technology from HTC. However as the bootloaders of all Android phones are developed by the manufacturer and not Google it's quite likely Samsung chose to go with what they already have i.e. the Loke flashing protocol.
Benjamin Dobell said:
fastboot is a tool used to interact with HTC's proprietary bootloader. It is certainly possible that Google co-developed or licensed this technology from HTC. However as the bootloaders of all Android phones are developed by the manufacturer and not Google it's quite likely Samsung chose to go with what they already have i.e. the Loke flashing protocol.
Click to expand...
Click to collapse
No. Fastboot was integrated into HTC's bootloader. But it is open source, fastboot I mean.
Acer is using it, too, just as an example.
And the Nexus S features fastboot aswell.
maxisma said:
No. Fastboot was integrated into HTC's bootloader. But it is open source, fastboot I mean.
Acer is using it, too, just as an example.
And the Nexus S features fastboot aswell.
Click to expand...
Click to collapse
Only the fastboot tool itself is open-source. A manufacturer would still need to come up with their own implementation to be included in the bootloaders of the device. I guess I'll just wait and see what some Nexus S owners have to say.
EDIT: I missed your last sentence, can you confirm your source please.
Benjamin Dobell said:
Only the fastboot tool itself is open-source. A manufacturer would still need to come up with their own implementation to be included in the bootloaders of the device. I guess I'll just wait and see what some Nexus S owners have to say.
EDIT: I missed your last sentence, can you confirm your source please.
Click to expand...
Click to collapse
Swetland himself said so. Also u can fastboot oem unlock.
Daneshm90 said:
Swetland himself said so. Also u can fastboot oem unlock.
Click to expand...
Click to collapse
Thanks, this thread I assume.
Ah well, would have been nice to say that Heimdall supports one more device. Not a problem though, fastboot works flawlessly, is cross-platform and open-source, no complaints there
Not that it's particularly relevant any-more. However this thread shouldn't have been moved as it is development related. Could this thread please be moved back to the development section so that in odd event that the issue does come up, the necessary information is available in the correct location.
Why is this development related?
It's actually about as development related as you can get. I was looking for information about the Nexus S so that I could develop extra functionality for Heimdall, in order to support the Nexus S. Heimdall is also a development tool used to flash firmware to Android devices. So the development nature is actually two-fold.
Benjamin Dobell said:
Not that it's particularly relevant any-more. However this thread shouldn't have been moved as it is development related. Could this thread please be moved back to the development section so that in odd event that the issue does come up, the necessary information is available in the correct location.
Why is this development related?
It's actually about as development related as you can get. I was looking for information about the Nexus S so that I could develop extra functionality for Heimdall, in order to support the Nexus S. Heimdall is also a development tool used to flash firmware to Android devices. So the development nature is actually two-fold.
Click to expand...
Click to collapse
Hello, I have a Nexus S (I9020a), I put it in download mode (volume up+down)+plugin-usb, I downloaded Heimdall, I followed the instructions to install Winusb, it detected the device, it listed the PITS? (Partitions).
You may be wondering WHY is this guy fooling around with NVRAM, well it just so happens I flashed a badly written rom and my /efs partition got corrupted and I have no back-up.
I asked myself, If I know what my IMEI is (just looking behind the battery) why can't I reload an EFS partition. Sounds reasonable to me.
Does anyone have any experience flashing a new EFS? Please help if you do. Thanks.
Introduction
Since I'm not a ROM developer or Java coder, I thought I could help by donating this little tool, that was origionally written for my personal use, for all to utilize in an attempt to give back to this community.
WinFastboot - Flash Recovery has been renamed to Android Flash Recovery
Requirements
- A PC running Microsoft Windows. 32 or 64 bit.
- Correct Android USB drivers installed for your device
- An Android powered device with debugging enabled
Description
Android Flash Recovery is a Windows GUI front-end for the Windows version of fastboot. This particular tool is designed to simplify flashing an Android device's recovery partition. Android Flash Recovery WILL NOT repair a bricked device. The device must be able to be put in to fastboot mode for Android Flash Recovery to be able to work. Since Android Flash Recovery is just a GUI for fastboot, the same applies for fastboot.
Beware. Android Flash Recovery unfortunately will not work with every single Android device. I am however, attempting to make strides in that direction
Installation
Installing Android Flash Recovery is simple too. Just unzip to a folder of your choice and then execute androidflashrecovery.exe, assuming your device drivers are already installed.
If you haven't installed your drivers yet, then they will need to be installed before using Android Flash Recovery as your device won't be detected.
If you are an LG user, the latest LG United Mobile USB drivers are are in a sub-folder of Android Flash Recovery, titled "USB". If you have attempted to install your USB drivers in the past with no success or with errors, go to Control Panel and uninstall any LG driver setup program you may find. Reboot your computer. Run the driver installation program. Make sure your device is NOT connected to the PC. Reboot your PC once more. Enable USB debugging on your device the power it off, trust me. After your PC has fully booted, plug your device into a USB port. Do not plug in to a USB hub. Windows may detect your device at this point and begin searching for or installing drivers. Power on your phone. Wait for all devices to be installed. For Froyo and GingerBread phones this is normally 5 or 6 devices. For ICS and JB this is 4 devices I believe. The important one is 'Android Single Sooner Interface'. This won't be installed if USB debugging isn't enabled on the device. Now your drivers should be installed and you can use Android Flash Recovery at your leisure.
Using
Using Android Flash Recovery is even easier than installing it. Browse for the recovery you wish to flash and press the 'Flash Recovery' button. NOTE: In order for Android Flash Recovery to flash, your device MUST BE in fastboot mode.
Included with Android Flash Recovery are the adb binaries with support libraries as well as fastboot. Android Flash Recovery is written to use the binaries included in it's package. Also included is the driver setup application for LGE Android Mobile devices ( United Mobile USB Drivers ).
Post questions here. I will try to answer them as I can. I have a regular full-time job so I am not a full-time developer. You may also email me at [email protected]. Set your subject line to "Android Flash Recovery". If the subject line isn't correct your email will be ignored.
Download
Latest version here -> Android Flash Recovery
Reserved...
Removed
Since I have had zero feedback about my previous post, I've decided to rename "WinFastboot - Flash Recovery" to "Android Flash Recovery". I'd also like to mention that it will be updated later this evening. I have a few more minor things to wrap up and then I'll upload and post a new link.
I've had quite a few downloads, so I know my app is being tried. I really need some feedback folks. If you have issues with, a feature request, or even a simpe UI improvement/suggestion. I'm also curious as to the types of devices that my app is being used in conjunction with. What works and what doesn't.
Thanks.
if a device is able to go into recovery mode, does it mean this app is applicable?
oldsap said:
if a device is able to go into recovery mode, does it mean this app is applicable?
Click to expand...
Click to collapse
Unfortunately no. The device must be in fastboot/bootloader mode.
bill.weckel said:
Unfortunately no. The device must be in fastboot/bootloader mode.
Click to expand...
Click to collapse
well there goes every samsung device that isnt a nexus
jamcar said:
well there goes every samsung device that isnt a nexus
Click to expand...
Click to collapse
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app
bill.weckel said:
There is a way to install a ROM with adb so I'd say it may be possible to do a recovery too. I'll do some investigating. Might be able to do something.
Sent from my LG-P506 using xda app-developers app
Click to expand...
Click to collapse
could you keep us posted on you research?
jamcar said:
could you keep us posted on you research?
Click to expand...
Click to collapse
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
for samsung phones you would look into using the dd if=[recoveryimg] of=[recovery partition] to copy the recovery image to the recovery partition. this is how you manually do a samsung phone's recovery flash. so a way to implement this into the app for, let's say the GS3 would be
adb push [user selected recovery img] \sdcard\recovery.img ( or some other way of copying the user selected recovery img to the root of the sdcard )
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
and that will flash the recovery to the gs3.
of course the main issue is that the recovery partition is not always the same name of the block so /dev/block/mmcblk0p18 will not always be the name of the recovery block. The way to overcome this ( i think ) would be to program in a part of the app that reads in Build.MODEL which will give you the model device the user has plugged in and then you can determine from there what the block title is by programming in the blocks for each samsung phone model. To make it simpler befoer you do that, filter out stuff that can just be fastbooted...something like...
if(Build.Manufacturer == 'HTC' || Build.Manufacturer == 'Motorola' ||... etc)
// just do fastboot
else
{
switch(Build.MODEL) { // if switching strings is supported in Android ( it was introduced in java se 7 ) otherwise use enums
case GS3:
block = 'mmcblk0p18';
break;
}
//move the file to the SD card if the model is supported
//do the su and dd command here
}
anyways...im bored at work so just figured ide give my 2 cents, not sure how much support you wanna give this haha...hope this helps
For me it's not working i am in Fastboot mode but winfastboot tells me i am not ... it recognized that the device is connected but not in fastboot mode even tough on my phone it says "fastboot usb" :\
Phone : HTC Wildfire
s-off
radio 3.35.15.31
ROM : CM9
Yeah i just saw "ICS( 4.0.* ) and JB( 4.1.1 ) devices are not detected correctly by the driver software. Some devices may not get installed." in the readme ...
Cant you do anything about this to fix it ?
That's strange. I figured there would be some devices that this wouldn't work for. Are your USB drivers installed correctly? All other fastboot screens say "Fastboot mode started\nudc_start()". I will look into it tho.
Sent from my LG-P506 using xda app-developers app
Updated. Check first post for downloads
Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...
Commandox said:
Yep , USB drivers installed correctly , other things worked everytime i tried to do something ...
Click to expand...
Click to collapse
I'm looking into a workaround for your HTC device and from what I've heard I may need one for some Samsung devices as well. I'm sorry the update I posted doesn't contain this workaround. It is something that I will look into. I do have a regular full-time job tho, so it may take a few days for me to figure out what I need to do, how to do it, then writing the code for it.
As for the fixing how device drivers are installed, that's not something that I can fix. I believe it is actually an issue with the ICS and JB ROMs themselves.
For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.
bill.weckel said:
More than happy to. I've have a little more to do as far as completing this piece of software then I'll look into using adb as an alternative for the purpose of this thread and possibly for devices such as yours that do not have access to the bootloader/fastboot mode for whatever reasons.
Click to expand...
Click to collapse
we have download mode instead of fastboot/bootloader we can use ODIN, samsungs recovery tool (tool not mode, meaning the program ODIN is on a computer)
EDIT: sprint galaxy s III is /dev/block/mmcblk0p18
I believe I've stumbled upon a universal method to check a device for mount points. I'm going to throw together a little test app and then upload here for y'all to test out if you would. If my suspicions are correct, I will then be most able to write the
universal recovery tool for windows.
@jamcar
Thanks for your response. I've actually heard of ODIN.
bill.weckel said:
For those of you who are having issues with Android Flash Recovery, I really need the names of your recovery mount points. HTC owners and Samsung GS3 owners for sure.
I can't fix these issues without your input folks. I'd really like to be the guy that has the one universal recovery tool that no one can live without. Scratch my back and I'll scratch yours.
Click to expand...
Click to collapse
For Galaxy Note International (GT-N7000) it should be - /dev/block/mmcblk0p6
i just need to confirm that
Hi guys,
I decided to root my Nexus S with Nexus root toolkit, and then I tried to install CyanogendMod 10.
Then, it rebooted, and now when booting it stuck at a moving circle with the CyanogendMod text in it. after 30 minutes I had to remove the battery to shut it down.
Now I can access to the Fastboot mode (bootloader version I9020XXLC2)
it says Lock State : unlocked. But a recovery shows a robot on it's back with an exclamation mark on top of it during some minutes and then it try to but normally again and get stuck at the circle.
Update :
thanks to http://forum.xda-developers.com/showthread.php?t=1069032
I can now access to download mode, and I'll try to do something with ODIN, I'm on my way to tutorials.
And it's still recognize in windows as : Android ADB Interface in the computer management window (but no USB hard drive in the computer menu).
Any suggestion to help me out ?
ps : as you can guess, I'm quite a beginner, and may not get the meaning of all technical word in flashing phones.
Thanks for reading.
DO NOT use Odin for things like that. Think of Odin as a last resort thing rather than a tool you can use daily.
The Nexus line of phones is super easy to deal with.
Flash your recovery using fastboot.exe while in bootloader mode.
http://wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img
Download for recovery (rightmost column):
http://www.clockworkmod.com/rommanager
Once that is done, boot to recovery, and wipe data + flash your prefered ROM.
Edit: Apple pie is awesome.
polobunny said:
DO NOT use Odin for things like that.
Edit: Apple pie is awesome.
Click to expand...
Click to collapse
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Tartopom said:
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Click to expand...
Click to collapse
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
polobunny said:
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
Click to expand...
Click to collapse
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Tartopom said:
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Click to expand...
Click to collapse
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
polobunny said:
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
Click to expand...
Click to collapse
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Tartopom said:
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Click to expand...
Click to collapse
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
polobunny said:
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
Click to expand...
Click to collapse
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Tartopom said:
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Click to expand...
Click to collapse
Bravo, you're getting there. You'll be an adb master in no time.
At least you are now a user that knows how to use fastboot and fix issues that arise from flashing ROMs and relying on automated stuff.
Besides actual hardware issues most issues people have on their device are by some automated form of something. Tool kits/ROM manager and so on. All of which can be fixed up right away with fastboot and a basic understanding of what you're doing.
So now you're better off. All nexus devices work the same way as well.
Hi all. I'm at my wit's end.
I'm new to Android and am attempting to rid my phone of Verizon bloat apps and want a clean Sense free environment. But my issue is that when I type "adb device" in command prompt, it doesn't show my device.
I have already spent the $25 for Sunshine and s-off'd my M8, and when I type "adb reboot bootloader" it reboots my phone into bootloader. So it's seeing something. In "Device Manager" it comes up as "Android Phone." I think it did that because I tried to do the troubleshooting of manually installing the Google ADB USB driver, but I'm not totally sure.
I have the Android SDK installed.
Ugh... this is headache inducing, and I just want a clean phone
If anyone can give some help, it would be TOTALLY appreciated.
Thanks!
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
pogswarts said:
fixed the issue. Instead of using the SDK, I used the website theunlockr and their guide worked perfectly.
Sorry for taking up forum space with my stupidity
Click to expand...
Click to collapse
You really should be using HTC drivers as well as the HTC version of fastboot. It's better tailored for the use of RUU etc on HTC phones whereas the sdk fastboot will fail.
http://forum.xda-developers.com/showpost.php?p=56890497&postcount=3
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
There's a cool tool kit called wugs nexus toolkit that will help some http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Also, here's mostly all the roms stock & custom here: http://forum.xda-developers.com/goo...dex-google-nexus-5-roms-kernels-mods-t2475401
Did you say you can still get into recovery? Because there's an unroot rom thats flashable somewhere... Itd take you to stock everything.....
Sent from my Nexus 5 using Tapatalk
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
In fastboot, but can't flash operating system
dahawthorne said:
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
Click to expand...
Click to collapse
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
" I've followed every rabbit trail"
Have you followed this one?
"Wugfresh's Nexus Root Toolkit"
kakid56 said:
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
Click to expand...
Click to collapse
Yup use wugfresh toolkit ... download the factory image https://developers.google.com/android/nexus/images#hammerhead
and boot into bootloader.. then u knw what to do
kakid56 said:
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
Click to expand...
Click to collapse
I don't disagree with the NRT suggestion but am confused. Sorry if I'm missing something obvious. When you are in the bootloader, do you get a cmd response from "fastboot devices" (no quotes in the command)? ADB doesn't work from the bootloader as you probably know, but since you identify as a noob, thought I'd throw it out there. You can flash the system using fastboot commands if your PC recognizes (part of the confusion) the device in fastboot. If not, then you do need to get the drivers set up. If you just need adb/fastboot drivers, I recommend this which I used recently when NRT didn't seem to have the SDK version I needed for my N9 to sideload the latest OTA. Since it installs at the system level, you can place flashable files at the root of C rather than in a specific platform-tools folder. I'm on Windows 10; don't know if that makes any difference for this minimal install. As far as the flash-all. bat not working, that's not uncommon; the files can be extracted and flashed separately.
Sent from my Nexus 9 using Tapatalk