Obviously I'm a noob, so sorry if this is stupid or there is an obvious answer (I've spent a lot of time looking and couldn't find it though). I was having problems with my phone so decided to flash back to stock and relock it to 'start again'.
Maybe that wasn't a great idea because I've had lots of problems since then. When I try to flash back to stock using nexus root toolkit I get "failed (remote: invalid bootloader)" and the phone finishes still in bootloader. There was a suggestion to force flash, but given the warnings around that I'm pretty nervous about doing that. If I then start my phone up it stays on the google screen for quite a while and then gets stuck on the X screen (it isn't frozen because the animation keeps running, but nothing else happens, even if I leave it for an hour).
I did a bit more reading and tried wiping the dalvik cache and cache. It then said it was upgrading android, optimising apps etc, but then got stuck again. I tried resetting again and the phone now restarts when I push the off button and slowly goes through both the google screen and X screen.
This might be a stupid problem, but I'm stuck so any help would be great.
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
Follow this carefully step by step using method 2. Be extremely careful flashing the boot loader, in fact you can probably skip that part. As long as your boot loader is always in tact it's virtually impossible to brick. As of right now you're stuck in what's called a boot loop. Most likely, either your boot.img (not the same as boot loader) or system.img (aka ROM/firmware) is messed up and is causing it.
Welcome to modding, have fun, but be smart
Sent from my Nexus 5 using xda app-developers app
Chromium_ said:
Flash the stock images manually rather than with a toolkit. You can find a guide stickied under the nexus 5 general section.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
beshakey said:
Thanks. Either a new problem or a related one - following the guide for setting up adb and fastboot, when i type adb devices into the command prompt nothing is listed (says "list of devices attached", but there isn't anything listed).
Click to expand...
Click to collapse
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Chromium_ said:
Go into fastboot mode and run "fastboot devices". If the device shows up there, that's good enough.
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks, that worked. But having done it when I reboot the phone it does the same thing (hangs of the Google screen for a long time then moves to the X screen and stays there). My phone is rooted and I have clockworkmod installed, so I selected fix root when asked, not sure if that is relevant?
Did you continue to follow the guide and flash the stock images in fastboot
Sent from my Nexus 5 using xda app-developers app
Yeah I did. I got the message "FAILED (remote:invalid bootloader image) and archive does not contain 'boot.sig' 'recovery.sig' and 'system.sig'. Everything else was OKAY. Put into recovery mode fine (with clockworkmod), wiped data and rebooted (fixing root when asked) but the problem described above remains.
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
And you are following the factory image flashing guide that has been provided above?
Can you try going through the guide again, and tell us the specific errors that you are encountering.
And use method two, not the first one that talks about running the flash all script. You should be doing command's like "fastboot flash boot boot.img"
Sent from my Nexus 5 using xda app-developers app
beshakey said:
More problems - tried doing it again, now it won't even boot up to the google/Android X screens. When I restart the screen lights up but nothing else. I can still reboot into the bootloader though. Arggh
Click to expand...
Click to collapse
Don't worry, you'll get it, eventually. When you first start doing this kind of thing, it takes some getting used to because you have to read VERY carefully, and perform each step EXACTLY as stated. Computers are absolutely unforgiving of even the tiniest mistake, so you have to take your time, and be patient when you have to start all over. But, it's a challenge, and a learning process, and a lot of fun, once you get the hang of it.
Sent from my Nexus 5
OK, step by step. If you need more detail yell out.
1) I've downloaded ADB and Fastboot
2) If I put ADB devices into the command prompt I don't get any devices listed. But if I put in Fastboot devices I get the serial number of my phone
3) Previously I'd been using method one. So I now extract the image for hammerhead krt16m to my f:\ drive. I've also extracted radio-hammerhead-M8974A-1.0.25.0.17 and bootloader-hammerhead-HHZ11d to the same location and renamed them to radio.img and bootloader.img respectively
4) Phone is connected to computer and in fastboot (and detected by fastboot devices)
5) In command prompt when I type in fastboot flash bootloader f:/bootloader.img I get the error message FAILED (remoteL invalid bootloader image).
6) Flashed radio.img and rebooted bootloader and system.img (no reboot) without any errors (although they took a while)
7) Flashing userdata.img got the error 'FAILED (remote: flash write failure)
8) Performed all the remaining commands without any errors (when erasing the cache I got the message 'Did you mean to fastboot format this partition? erasing 'cache'... OKAY
9) Entered recovery mode. Earlier when I did this it was fine, but now (like when I try to start the phone) the screen lights up but no text etc appears
10) At this point I'm stuck, as I can't see the cwm text so can't select wipe data/factory data reset (although I did do this as part of earlier attempts)
From the 'on but no text' state, I can using the on button to restart into the same state or can enter fastboot (where text etc appears fine)
One at the boot loader you said you put f:/bootlaoder.img that was wrong, no drive letter. You do not need to flash your boot loader though anyways. Avoid doing that unless you have to, it is the only thing that will brick your phone.
You said system.img flashed fine, did not see any Menton of a boot.img or recovery.img. you need all three of these.
So, start over again. Make sure you flash a boot.img system.img and recovery.img separately. DO NOT flash the bootloader.img unless you have to (to update). Again, the boot loader is the one thing that will brick your phone if done wrong.
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------
Sorry I just read through that tutorial and it does tell you to use drive letters. Im used to flashing with my files in the location of fastboot so I don't need to do that.
Sent from my Nexus 5 using xda app-developers app
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Good catch.
Sent from my Nexus 5 using xda app-developers app
samersh72 said:
@op why you are flashing 4.4 images?? it has a different bootloader then 4.4.2.
i guess your primary bootloader now is 11k and not 11d or 11a .....(since you took the ota out of the box)
bootloader version must match with the rest of images.
so download 4.4.2 images and flash them using 11k bootloader. (note that you have the old and new bootloaders on your device, volume down + power will take to the new bootloader 11k, and Volume down + volume up + power will take you to the old bootloader).
regarding adb command, it will not work in fastboot mode, it works when booting in os with usb debugging enabled, or in custom recovery mode
Click to expand...
Click to collapse
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
beshakey said:
Thanks I'll try that. Is there any way for me to confirm on my phone what my primary bootloader is?
Click to expand...
Click to collapse
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
travisjustin said:
Boot into it using power volume down and it will list the version
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
beshakey said:
Will try that, thanks.
I'm pretty sure I've done something stupid to cause this and I had a thought about what it might be - my phone was still at 4.3 for some reason. It would receive the update and install it, but the version wouldn't change to the new one. So should I try to track down the old 4.3.? bootloader?
Click to expand...
Click to collapse
4.3? The nexus 5 ships with kitkat 4.4 ...there is no 4.3 for it.
Sent using xda-developers app
Related
Hi
I have bricked my nexus s when I loaded a ROM that I downloaded.
I have used several different ROMs and had no problems.
I asume this ROM was dodgey.. Anyway I get no screen at all, the menu control at the botom of the screen lights up but that is it.
I can get to it using fastboot but it won't load any ROMS. There is no action on the Nexus screen itself.
Is there a guide using fastboot to recover this also what file/files will I need to download?
Thanks in advance any help would be much appreciated.....
If you are here looking for help you need to give us more information.
What model Nexus S do you have?
What rom did you flash?
What have you done sense flashing the rom?
My guess is you flashed a rom that isn't for your model phone. So you either have SAMOLED or SLCD. I'm guessing the rom you installed was for the screen type you don't have.
So let us have some more details so we can help.
Sent from my Nexus S 4G using xda premium
Sounds like a call for the mighty Odin...
Sent from my Nexus S 4G using xda premium
And u can't get into recovery using the button method?
Sent from my Nexus S using XDA App
If you can get fastboot to work, you can flash all partitions including system. Don't worry, this is an easy fix.
Hi Again guys
Firstly thanks a lot for the replys I really appreciate it.
Its a 3g the model no: is GT-19023.
Its SAMOLED that much I know.
I cannot get into recovery I can get fastboot to recognise the phone but nothing on the screen.
I have downloaded a stock rom and extracted the boot, recovery & system.img files.
I have followed the instructions below and all seems to work till I get to the system. it fails with the following message. The other steps seem to work OK.
"FAILED (remote write failed)"
I have also tried this with several other ROMs I know work on wifes Nexus s and still no luck. Some allow the system to be flashed but the phone still won't boot.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
Any help would be great
I also downloaded ODIN but cant get it to work; It does not recognise that it is connected to the USB, but fastboot does!. (Is there a step by step guide to using it?)
Sorry for sounding like noob, but I have read everything and looked up these forums and tried a lot before asking for help.
GL
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
k_myk said:
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
Click to expand...
Click to collapse
ROMs are compatible between those variants! But, if you're flashing some stock ROM bundles you can flash wrong one. Because bundles contain rom, kernels and radios for specific device with specific drivers. In that case you can flash wrong driver for your display, or even something worse...
Follow what it says, unlock your bootloader first.
Sent from my GT-P1000 using xda premium
glockman63 said:
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
Click to expand...
Click to collapse
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Rem3Dy said:
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I've got a phone in the same state I am trying to revive for a guy. With the bootloader locked download mode gives you a locked bootloader screen. Odin sends the flash images to the phone, the phone verifies them but then refuses to flash them (presumably due to the bootloader being locked). The bootloader won't unlock so there is no way to flash a rom to fix the phone.
glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
jboxer said:
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
Click to expand...
Click to collapse
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it does! Or at least on the phone I am trying to repair it has. On the phone I am trying to repair when you go into download mode you get a screen that says to unlock the bootloader. Odin connects and sends the file but then the phone refuses to flash it. If that is not the bootloader being locked affecting Odin then I don't know what is. I have flashed with Odin hundreds of times with Galaxy S phones so I know what I am doing. I have never seen Odin send a file, have the phone say it is verified and then refuse to flash it, but that is what is happening with this Nexus S with an unlockable bootloader. The files are the correct files and Odin is the correct version. If you are so smart, then you tell me what to do to get Odin to accept the flash and you will be my hero.
I have attached a shot of the phone in "download mode." Notice it is a warning about the bootloader being locked, not the normal screen with the Android bot and a shovel. Odin sees the phone (connected to computer as Samsung device) but once the phone verifies the file nothing else happens. The file is never flashed. Notice in the photo there is no YES and NO selections to unlock the bootloader like you get when you issue the "fastboot oem unlock" command. In Fastboot when that command is issued you get the normal unlock the bootloader screen but when you select YES and press Power nothing else happens. It just hangs no matter how long you leave it. A battery pull is the only thing you can do and when you turn the phone back on the bootloader is still locked.
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cannot flash in fastboot. Sends over image then says fail due to bootloader being locked. If you have a signed update.zip with android-info and android-product files that can be flaahed in fastboot mode let me know where it can be downloaded from.
Sent from my LG-P999 using Tapatalk
I have a one xl that will reboot after being on for 2 minutes
evita pvt ship s-on rl
hboot-1.14.0002
it is unlocked, but i cant relock it. Every time i try it says fails then reboots. I have also tried flashing twrp and cwm recovery via fastboot, but everytime i try to enter one it hangs on the teamwin screen. I have tried the ruu it reads my phone at first then when it says rebooting to bootloader the phone reboots normaly and get error 107.
Any help would be greatly appreciated.
What method are you using to try to relock the phone? What method are you using to install the mentioned recoveries? Please give as much detailed information as possible.
Sent from my Evita.
To relock i have used fastboot in cmd and typed fastboot oem lock. I have done that 10 times with the same result phone reboots normally and when i reboot back into bootloader it still says unlocked.
To flash recoveries i have used fastboot flash recovery ********.img
fastboot erase cache
fastboot reboot-bootloader
but instead of rebooting to the bootloader it boots normally
What did you do to the phone before all this started happening? Phones don't usually just start doing things like this of their own accord.
Sent from my Evita.
I bought it like this. The last owner said it happend after he installed a rom. I was hopping i could unbrick it with out jtagging it becuase i am still able to fastboot to it.
If you can't get an RUU to work I think jtag might be your only option.
Sent from my Evita.
I've only tried 2.20. I even extracted the system IMG from it but fast boot says it is too large. The only reason ruu won't work is because I can't get my phone to reboot into boot loader. Is there any way I can flash a different boot loader through fast boot.
Just curious, but when you type fastboot devices from the Bootloader, what is the output?
Are you running fastboot oem lock from the bootloader?
Sent from my One X using XDA Premium 4 mobile app
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
keithman2567 said:
Nothing happens. And if I type fast boot OEM lock from the boot I get waiting for devices
Click to expand...
Click to collapse
If when you type fastboot devices (while in the boot loader) in your computers command prompt, and it doesn't show your HTC device being attached, that means that your computer is not recognizing your phone. Have you installed the HTC drivers? Do you have the newest versions of fastboot and adb installed?
What OS are you running on your computer?
Sent from my One X using XDA Premium 4 mobile app
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
keithman2567 said:
I have the HTC drivers installed. My computer only recognizes my phone when I put it into fast boot mode then it tend me my device name ht253w309354. Fastboot. As for three adb and fast boot versions I do not know.
Click to expand...
Click to collapse
Does your device boot into the ROM at all?
Sent from my One X using XDA Premium 4 mobile app
Yes. But only for 2 mins before it reboots.
keithman2567 said:
Yes. But only for 2 mins before it reboots.
Click to expand...
Click to collapse
If you can connect to Google Play store, download recovery tools, if you have time. From there you could try to install a new recovery for your device. With only 2 minutes you will have to be quick though.
Do you have access to your sdcard from your computer?
Sent from my One X using XDA Premium 4 mobile app
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
keithman2567 said:
I don't have time. Every time I reboot I have to renter my WiFi password. Yes I think I do but by the time any thing loads it reboots.
Click to expand...
Click to collapse
Here is the app. Not sure if you'll have time, but you can try
https://www.dropbox.com/s/wa4u565woyrrrlw/de.mkrtchyan.recoverytools-2.apk
Sent from my One X using XDA Premium 4 mobile app
Thank you, but there isn't enough time to even transfer it over
keithman2567 said:
Thank you, but there isn't enough time to even transfer it over
Click to expand...
Click to collapse
Do you have USB debugging enabled in the phone?
Sent from my One X using XDA Premium 4 mobile app
---------- Post added at 10:22 PM ---------- Previous post was at 10:15 PM ----------
Have you tried to flash a new ROM from fastboot? It sounds like your recovery partition might have been corrupted.
Sent from my One X using XDA Premium 4 mobile app
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
keithman2567 said:
I can if I turn it on fast enough, but when it reboots I have to turn it back on.
I have only tried flashing a system.IMG I pulled from an ruu. But fast boot said it was too large.
Click to expand...
Click to collapse
Alright, so I have a few ideas.
1. Try flashing a new rom via fastboot. (the following is based on the assumption that you have adb and fastboot in your path)
Flashing a ROM through Fastboot
So Why Do I Need To Do This?
You don't, normally you would flash a ROM through recovery, but why not have another way? Maybe your recovery partition on your phone is corrupt?
Maybe you just want to say "I learned something new!" whatever your reason here are the simple steps:
To start:
Quote:
Quote:
We need to download the ROM of choice to your computer. Once complete find the folder that rom is in and open terminal/cmd to that directory
(quickest way for windows; just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
In the command line type:
Code:
fastboot devices
Seeing your serial number means we know all is good
Now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
Of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
2. Boot into Recovery via fastboot.
Plug phone into PC, connect with USB cable and have phone in fastboot mode, now open CMD/Terminal in the same directory as your recovery image
Code:
fastboot boot recovery.img
Of course name image correctly to fit command or vise versa
Now you are in recovery of choice within your device without it being flashed to your recovery partition. There is a time and a place for everything, can you think of ways this may help you? Sure you can!
This doesn't actually flash the recovery.img... it will just allow you to boot into it. Make sure that you have a good TWRP version.
The previous quotes were taken from this guide on XDA-University:
http://forum.xda-developers.com/showthread.php?t=2277112
Android 6.0.1, build number MOB30H
I have a brand new nexus 5 that I want to root. Using ota, I accepted the system updates to 6.0.1 with the Android security patch of May 1, 2016. (not sure if that was a good idea or not but it's done now....). Now I want to root it with a twrp recovery.
Like most run of the mill users I've only rooted a device 2-3 times in my life, so my memory is rusty on how exactly to do it. I searched this forum and found many threads about this or that rooting problem which just confused me further. I know I need to unlock the bootloader and then flash a twrp recovery but I am not sure of the exact sequence of steps.
1. When I connect the nexus 5 to my windows pc using adb, it appears in Windows but the nexus 5 folder is empty. I have developer options available and usb debugging is on but I can't find where the mtp switch is.
2. Adb.
I have adb installed in Windows. The command "adb devices" returns the nexus 5 number unauthorized.
Don't know what "unauthorized" means or what to do about it.
I've done nothing further because I don't want to mess things up. Please help me resolve questions 1 and 2. Then, I presume I need to
A. unlock the bootloader
Fastboot command?
B. What's next?
Thanks for any help.
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Two things, have you enabled developer options. Go to settings, about phone and tap build number 7 times. In developer options you can change USB configuration and you'll also need to enable OEM unlock. Then unlock and root your device per the guide in the general section.
Click to expand...
Click to collapse
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Yes I already had developer options working and also usb debug on.
Discovered that mtp is a problem in marshmallow. I finally got file transfer working.
audit13 said:
You need to connect the phone in fastboot mode, run the command "fastboot oem unlock:, accept the agreement using the volume and power buttons, reboot into fastboot mode, flash twrp, copy the latest version of supersu.zip to the phone's internal memory, and flash supersu.zip from twrp.
You can install TWRP and root without using ADB commands.
Click to expand...
Click to collapse
Thank you very much. That is very helpful.
I didn't know you could "install TWRP and root without using ADB commands". How do you do that?
BTW, I updated the new nexus 5 to marshmallow inadvertently. When I root I'll probably use a 5.1.1 image. Good idea?
Stevica Smederevac said:
Just to add,not to confuse him even more, there is no Oem unlock option for Nexus 5
Sent from my Alps Q10101 using XDA Labs
Click to expand...
Click to collapse
Yep, my bad. Sorry about that. My 5 crapped out and have the 5x now. Amazing how fast you forget things, lol.
Sent from my Nexus 9 using XDA Free mobile app
Download and flash twrp in fastboot mode: https://dl.twrp.me/hammerhead/twrp-3.0.2-0-hammerhead.img.html
Download supersu.zip and save it to the phone's internal memory: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Boot the phone into fasboot mode, open a command prompt, type fastboot devices and press enter. If the device is recognized, you'll see the device's serial number. Unlock the bootloader by typing "fastboot oem unlock" and use the volume/power button to accept the agreement and unlock the bootloader. Unlocking the bootloader will wipe the phone's data and cache.
To install TWRP, boot the phone into fastboot mode, connect it to the computer, open a command prompt, and type "fastboot flash recovery name-of-TWRP-file,img" and press enter. After flashing, immediately boot into recovery using the power and volume buttons, and then flash supersu.zip.
Thank you so much audit13. I really appreciate your help.
One question if I may. Reading on the web about rooting the nexus 5 running marshmallow I came across a couple of sites that said I should download and flash "ElementalX kernel and SuperSU 2.52" in addition to supersu.
I've never had to install a separate kernel when I rooted in the past. I notice you don't add flashing a kernel either. Can I ignore flashing a special kernel?
Thank you so very much for your clear instructions.
Some root methods require a rootable kernel. The latest supersu should root mm.
Thank you. Ran into a problem. That's why people like me are afraid of rooting.
Bootloader is now unlocked. Thanks.
With the N5 in fastboot mode, I connected it again with the laptop.
From the laptop command prompt I ussued "fastboot devices" and it found the phone.
Problem:
1. Fastboot flash recovery.img
(I had renamed the twrp 3.0.2 img file to recovery. Img)
Result:
unknown partition 'recovery.img'
error: cannot determine image filename for' recovery.img'
Tried by downloading a fresh copy and using its original filename.
Same result.
What am I doing wrong?
Thank you.
Found my error. I forgot the word recovery.
I now flashed twrp successfully!
When I went to flash supersu I discovered that the supersu I had downloaded was no longer in download folder. Guess it got wiped. So I rebooted into system and will download it again. Hope that does not mess up things.
Edit:
All went well. Re-downloaded SuperSU, installed fine and I'm home free.
Thank you all, especially audit13. This is a nerve-wracking process for people who only do it rarely. Glad it is over. The rest is easy!
I spoke too soon. I believe I now have a boot loop? What I have is that the horizontal turning balls of marshmallow go around forever and never finish booting.
How do I exit from this?
So close, but not there!
Edit
I rebooted into twrp, deleted cache, davlik. Still in bootloop.
Deleted data. Still in bootloop.
Help.
Reflash the entire stock rom and start over.
Try the latest beta of supersu: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Great you are still here.
Need more details.
You say reflash stock rom. Where do I get it? How do I get it into the phone? Do I flash it through twrp?
How to flash factory image: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Factory images are here: https://developers.google.com/android/nexus/ota#hammerhead
Thank you again. Will do.
I think I know what went wrong. After I flashed twrp the phone rebooted into system before I could stop it and I think I interrupted it somewhere to return to twrp to flash Supersu. Anyway, glad I didn't brick it. Thanks again for being there.
It's morning now and after a good night's sleep I'm less rattled. Will get breakfast and start again.
I'm going out with my wife for breakfast.
I haven't followed the marshmallow threads but I recall reading about lingering problems with marshmallow. I also like to use xprivacy and gravitybox. So I'm thinking of flashing the latest 5.1.1 instead of 6. Any thoughts?
I like both ROMs but my battery life seems a bit better on MM. I'm sticking with unrooted stock ROMs on all of my phones for now.
Being a "flashaholic" is tiring!
audit13, I know you know this but it was so simple to do (once you know how.....!). It took me the whole of 20 minutes, if that, to download the files, flash 5.1.1, flash twrp and install SuperSU. Makes you wonder why I had so much trouble before!
Well when you don't know the command syntax (forget to write which partition to flash to) and are frozen with fear that you will brick the phone, it is a scary process. Once I knew how, I breezed through it. Problem is that by the next time I need to do this, I will have forgotten how or will worry that the process has changed.
I just want to thank you more than I can say for helping and hanging in while I made my mistakes. I wish there was a way I could thank you with more than words. You were great!
P.S. This time I used the beta SuperSU. Don't know if it made any difference.
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
maybeme2 said:
My wife's Rooted Nexus 5, stock 6.0.1 phone has become unusable. After deleting some contacts she gets a popup that "Android.process.acore has stopped" every couple of seconds.
Searching for solutions on the web I've
Deleted her contacts data and cache
Deleted her contacts storage data and cache
Reset app preferences
Disabled contacts
And nothing stops it.
Is there a solution to this problem?
Thanks.
Is it possible to restore a working nandroid made on a different nexus 5 to the messed up nexus 5?
Click to expand...
Click to collapse
you need to flash again the stock rom. try using nexus toolkit.
https://forum.xda-developers.com/google-nexus-5/development/toolkit-wugs-nexus-root-toolkit-v1-8-3-t2517778
you can get the stock roms here.
https://forum.xda-developers.com/google-nexus-5/development/rom-android-m-preview-2-flashable-zip-t3157299
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
maybeme2 said:
Thank you. I thought I might need to reflash the rom. I was trying to avoid it because flashing roms always makes me nervous. But I'll just have to do it.
Xposed is also installed on the phone. I assume I will need to uninstall that first too. Ugh!
Click to expand...
Click to collapse
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing just the system image and not the whole rom. You'll be able to save all your apps and data that way.
Click to expand...
Click to collapse
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
maybeme2 said:
That would be great!
Never done that. I'll search the web for just the 6.0.1 system image. I assume that's different from the "factory image" from https://developers.google.com/android/images
Could you point me in the right direction?
Click to expand...
Click to collapse
Download the factory image, it's a zip file. Extract it and inside is another zip file. Extract that too. Inside that are a number of .img files, one of which is the system.img. You'll use that one. Use fastboot to flash it, fastboot flash system system.img. If you've never used fastboot Google "15 second adb xda" The first thing that should pop up is a tool by Snoop05. That'll install fastboot and adb on your PC.
Sent from my [device_name] using XDA-Developers Legacy app
You are wonderful jd1639. Thank you very much.
What you suggested worked like a charm. I flashed the system.img successfully. Took no time.
Unfortunately, it did not solve the Android.process.acore bug.
So I decided to just flash the entire rom and go that route. That's where I ran into problems.
1. I did adb reboot bootloader
and then flash-all
which resulted in something about system img not found (even though I had moved everything into the same folder).
Now, the phone is now no longer rooted and I can no longer get into recovery. And adb reboot bootloader no longer works. I get "error device offline".
I'm not that knowledgeable in android and flashing and am stuck. What should I do?
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially,
Ok, solved the offline problem. Disconnected and reconnected the USB cable.
But still no go. Here's what I get with flash-all
For some reason my paste of the results won't show when I save.....
Essentially, it says archive does not contain 'boot.sig', archive does not contain 'recovery.sig'.
Sorry, error.
maybeme2 said:
Sorry, error.
Click to expand...
Click to collapse
The no .sig stuff is normal and you don't need to worry about it. Just ignore it and let the flash continue and do its thing.
Let me know if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
maybeme2 said:
Unfortunately, I can't ignore it because it stops with "press any key to exit". So I exit.
Wish you lived next door. I would be glad to pay you to do it.....
Click to expand...
Click to collapse
Does it flash anything before it gets to the press and key? It should flash the bootloader and modem before it gets to the .sig stuff. Or does it immediately go to the press any key? If it goes immediately to the press any key then it sound like the PC isn't recognizing the N5. If that's the case boot into the bootloader, press power and vol up and down keys at the same time. Once it boots into the bootloader then connect it to your PC. Then using fastboot issue the command, fastboot devices If your PC recognizes the N5 it'll spit out a long alpha/numeric number on your pc. About 16 characters long.
If you get the alpha/numeric then go to the folder of the second zip file you extracted. There should be boot, cache, etc image files. Then open a command window /power shell there and we'll flash all the partitions manually. Issue the following commands, one after the other once the previous one ends.
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
If any of those don't work let me know which one.
Sent from my [device_name] using XDA-Developers Legacy app
Thank you again.
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
maybeme2 said:
Thank you jd1639.
All the flashing worked when I did it sequentially as you suggested. Don't know why the batch file got stuck but no matter, you saved the day.
So it is now factory fresh. Please remind me how to root it.
Thank you so much for hanging in there to help a total stranger.
Click to expand...
Click to collapse
No problem. To root download twrp for the N5. I Google teamwin nexus 5. It'll be a .img file. Also download supersu. Google supersu 2.82 sr5. To flash twrp boot into the bootloader and with fastboot flash it, fastboot flash recovery twrp.img. Twrp.img is the full file name of the download. Then boot into recovery (it'll be twrp). From recovery your PC will see the N5 and you'll be able to copy supersu to the download folder of the N5. Then flash it in twrp (install) supersu will be a zip file.
Sent from my [device_name] using XDA-Developers Legacy app
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
maybeme2 said:
Problems never end.
1. I successfully flashed twrp.img using fastboot. But when I go to recovery I get the empty robot with the red exclamation mark. (No twrp recovery)
2. Other problem: the 32Gb nexus 5 now shows only 16Gb.
Click to expand...
Click to collapse
Yep, you're having fun. The problem is twrp is not sticking. But first let's solve the memory issue, which is fairly common. The red ! Is the stock recovery. It's been awhile since I've messed with it so you might have to play around with it a little. When you get the ! Press and release the power and vol up keys. Timing is important so that's where the playing around comes in. It might be vol down or both vol. If you get it right it'll go into the stock recovery, don't ask why you need to mess with the keys and it won't just go into recovery and not go through the ! crap.
Anyway, once you get into recovery go to factory reset and reset the device. That will solve the memory issue.
Now to twrp, instead of flashing twrp you'll want to boot into it. Use fastboot and the command fastboot boot twrp.img. Once in twrp get supersu on your device and then flash it. Then go to reboot in twrp and boot into the bootloader. Then use fastboot to flash twrp, fastboot flash recovery twrp.img. Twrp should stick now.
Edit: to get into stock recovery it's power and both vol keys. Press, hold about 1/2 second, and release.
Sent from my [device_name] using XDA-Developers Legacy app
Yes I'm having fun...... (that's why non-experts are scared to do things which the experts say "not to it - which is true when everything works)
The 32Gb becoming 16 is a problem I encountered previously on another nexus 5. So I noted its solution : the fix is to wipe cache and data. Catch 22: how to do that when you can't get into recovery? I was going to search for a way to wipe cache and data using fastboot when I read your message.
I'll try to do what you advise. Fingers crossed.
Tried rooting my pixel 3 with XDA instructions. Phone bootlooped and went into recovery. Tried restarting, same issue. Tried factory reset, same issue.
I can still boot to fastboot, recovery, barcodes etc.
When the pixel 3 is in bootloader the device is not recognized by adb on mac or pc. Can someone help? Prefer to solve the issue through mac if possible but if PC is the only option I'll greatly appreciate your help too.
Solved
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
I'm love you??????
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Thank you thank you thank you. The last part still got me confused, because I actually pulled from the zipped image file I had. I had an image file on hand, but it just wouldn't work. And I had no idea about the radio, so I just skipped since it didn't seem all that pertinent. This is the second time I've had to get it back to stock, but I couldn't remember for the LIFE of me how I did it. Even though it was literally two hours before this time. Hey! I just don't know when to quit!
suhaybh said:
Figured it out. If anyone is in a similar situation here is how i got my phone working again on a mac.
1) ./adb kill-server
2) ./adb start-server
3) ./fastboot devices (to make sure your device is seen)
4) ./fastboot flash radio <radio.img> (probably didn't have to do this but made me feel safer for whatever reason)
5) ./fastboot reboot bootloader
6) ./fastboot -w update <image.img>
My phone then booted to my recovery which said that my OS was corrupt. After having a panic attack, I simply selected retry and BOOM my phone is back to working condition.
Click to expand...
Click to collapse
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
robertoancini51 said:
Hello, I cannot unlock fastboot in a Pixel 3 XL and If I press the Button Recovery in Fastboot, the phone ia turning off. Any ideas? Thank you
Click to expand...
Click to collapse
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Click to expand...
Click to collapse
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
robertoancini51 said:
If i cannot unlock the bootloader, is there any posibility to flash factory image? I didn't do anything to it, that's how I bought it.
Click to expand...
Click to collapse
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Try flashing the factory image. The official firmware should flash. But make sure you have the latest sdk tools platform, r28.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
bobby janow said:
I'm not sure what the rules are on cross posting but here's his OP https://forum.xda-developers.com/pixel-3-xl/help/google-pixel-3xl-fastboot-locked-t3885967
Can you flash a factory image with a locked bl? I thought not. Either a factory reset, perhaps sideload the OTA but that's about it IIRC. I'm also wondering where he got it from since it's not really clear.
Click to expand...
Click to collapse
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if it will flash with the locked bootloader, but it's worth a try. He can't get into recovery so the ota, which would be my first suggestion, isn't an option. But if the device is new and came that way RMA of the best choice.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
bobby janow said:
I don't think he knows how to get into recovery and I also don't think this is a new device. He needs to read up on some things first. From entering recovery to platform tools to adb and fastboot commands. It's all out there he just needs to search a little.
Click to expand...
Click to collapse
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
You're probably right on recovery. It seems a lot of people don't know what to do once you get the "no command".
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I was included in that first time I saw it. lol. Slight panic but the Google helped me out of it. Even knowing what to do it can be a little finicky.
jd1639 said:
Have you tried to flash the factory image? Also, did you do anything to the device, flash something, to get it to the point where it will only boot to the bootloader and won't boot into recovery?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Is your bootloader unlocked? Have you tried flashing the factory image?
abhinavkonagala said:
This is me right now. I can only boot into bootloader. I can't power off, start, or enter recovery mode. It just takes me back to bootloader. I have a mac. Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
What happened exactly? If your bootloader unlocked, and have fastboot access, then you should be able to fastboot the factory image.
LGFr.... said:
For me the same here (bootloader is unlocked)
Device was rooted, and I only wanted to flash the march factory image...
Any help would be great! Thanks
Click to expand...
Click to collapse
You using sudo for fastboot and adb commands?
How'd you install platform tools? I know for me the only thing that worked on Mac was using Homebrew . All other methods were finicky at best