Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
it goes in the same folder on your computer as where fastboot is located. then fastboot flash recovery recovery.img
I have fastboot, adb and recovery image in the same folder on my desktop.
mgf8384 said:
I have fastboot, adb and recovery image in the same folder on my desktop.
Click to expand...
Click to collapse
the android laying on its back is the stock recovery btw. did you rename the recovery properly? is it still an img file?
mgf8384 said:
Each time i get failed remote error image is not a boot image....
Click to expand...
Click to collapse
Its not a boot image, Its a recovery image. You sure your typing the correct command?
Esit: Just done some googling and someone had the same problem. Was due to a bad download.
Edit 2: ah just read again and you said you tried 2 types of recovery. Scrap my 1st edit then?
Sent from my Nexus 5 using XDA mobile app
mgf8384 said:
Hoping someone can help. I've unlocked bootloader easily, however, im having a problem flashing recovery. Each time i get failed remote error image is not a boot image....it starts to write and then fails. ive tried with cwm and twrp. i am placing the file in my adb folder, and renaming it to recovery.img so really i dont know whats wrong. never had this issue ever before. i checked to see if it was flashed, and nothing was there, showing a dead robot with an exclamation. cannot figure it out!
Click to expand...
Click to collapse
You'll just be doing wrong and no, nothing needs to be in the same folder of you installed it properly. Click the link in my signature to the sticky thread and read my adb and fastboot thread.
Also ensure "hide known file extensions" is turned off in windows.
If you need more help, you should post screenshots of your cmd window.
Sent from my Nexus 5 using Tapatalk
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
the way it was renamed.
There's no need to rename it....for future flashes.
KJ said:
There's no need to rename it....for future flashes.
Click to expand...
Click to collapse
i rename it to simple 3-4 letter words, for ease of typing
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Just brought it up, cause in this case...he wouldn't have had an issue if he left it.
But yeah, I do that too. Lol
mgf8384 said:
Thank you all. Setting somewhere in my PC I think. When .img.img was typed it worked. ( i tried fastboot flash recovery rec and then hit tab) Checked properties in the recovery zip and it's named just recovery.img so don't understand why it had to be typed twice? If anyone knows please tell me so I can correct it.
Click to expand...
Click to collapse
Because you had "hide file extensions" on in windows like I said.
File was called whatever.img but you can only was whatever because. .img is hidden. So when you rename it, it only let's you rename whatever (leaving .img hidden and unchanged) so you rename what's visible to recovery.img and results are obvious
(whatever).img > (recovery.img).img
So the quick lesson - turn off "hide known file extensions" in windows. Not just for this reason but for your own security. .exe files with word doc icons etc
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:42 AM ---------- Previous post was at 08:41 AM ----------
simms22 said:
i rename it to simple 3-4 letter words, for ease of typing
Click to expand...
Click to collapse
Or type first letter or two then press tab
Sent from my Nexus 5 using Tapatalk
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
siddjazz said:
Hello everyone.
I had to move back to the factory image because of a bad flash. After resetting, i try to install TWRP or CWM using fastboot. The recovery works the first time its installed, but goes away when I reboot my phone. By goes away i mean I see googles recovery (dead robot) once I reboot the phone and then boot into recovery.
I tried to flash a ROM while TWRP works but once I do, I cant see any of my files on the SD card. This means I cannot flash anything even if I booted in TWRP and this brings me back around to flashing the factory image.
Any help is much appreciated.
Click to expand...
Click to collapse
Go to general and read the sticky thread about 5.0 roms and recovery
Related
I know this is not a new subject. but i feel i wont get a response in another thread that is pretty outdated. so im trying to flash cwm recovery thru fastboot but i get an error. I've tried typing the directory path c:\android-sdk\platform-tools\recovery.img. i get "cannot load recovery.img". this is what im typing
fastboot flash recovery c:\android-sdk\platform-tools\recovery.img
and i still get the error. I've even tried moving the recovery.img to c:\recovery.img
but no matter where or how i call it. it wont load. please help guys. I had android sdk install before but i had to wipe my pc clean and i just recieved a replacement nexus s 4g.
Have you tried navigating to the folder where recovery.img is located and typing "fastboot flash recovery recovery.img"
Sent from my Nexus S using XDA App
What do mean navigating? Typing the directory path?
Sent from my Nexus S 4G using Tapatalk
I think he means typing this first:
cd c:\android-sdk\platform-tools\
So how would I type this? I don't I am... please elaborate. Thank
Sent from my Nexus S 4G using Tapatalk
What operating system are you using? Windows?
Sent from my Nexus S using XDA App
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Harbb said:
Place the recovery you need in C:\android-sdk\platform-tools\recovery.img
Open up command prompt and type:
cd \android-sdk\platform-tools
Now, make sure it detects your android:
fastboot devices
You'll see a line with a serial number, you're good to go (remember you need to be in fastboot mode while you do all of this, Vol. Up + Power while off)
Now, just flash the recovery.img (i'd recommend the latest recovery from clockworkmod.com):
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
wow. i did everything mentioned. i even redownloaded the recovery image. and i still get cannot load error. i even did it where i renamed it and left it alone the way it was typed
Is your bootloader unlocked? Also, fastboot devices shows a serial number right?
Harbb said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
yup its unlocked.
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
let me give this a tried
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow this did it for me... i dont understand bc i typed
fastboot flash recovery rec(tab)
fastboot flash recovery recovery.img.img and i hit enter and it flashed. weird. but thanks dude i greatly appreciate it for sticking it out with me.
Wonderful. You probably have "hide file extensions for known file types" checked. So when you downloaded the original, it ACTUALLY had a .img on the end of it already (which windows hid from you). Windows, unlike unix, cannot differentiate files based on their header, but instead relies on a useless extension in the file name of all places (ie, .img, .mp3 and .jpg at the end of the filename).
And noo problem mate, happy to help.
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Techno Droid said:
i flashed super user in cwm and it flashed ok. i reboot, go to the app drawer and its not there.... i did this twice.
Click to expand...
Click to collapse
weird. i downloaded superuser from the their website and flashed. it didnt show. so i downloaded it from the market and tried running an app that requires su permission and it worked. am i missing something here? why did this work that way?
Flash this su.zip file. There was an older su version that automatically accepted any su access because it wasn't compatible with ICS yet.
thanks. it feels good to finally be rooted. i was stock for 2 days.. lol thanks
cannot load recovery.img
Thanks. the TAB autocomplete worked. I had forgotten about the additional file extension. gotta change that setting. Thanks again
Harbb said:
Have you, by any chance, tried pressing the Tab button to autocomplete the recovery filename?
for example:
fastboot flash recovery rec[TAB] --> autocompletes to recovery.img
I'm running out of ideas here
Click to expand...
Click to collapse
wow, thanks man, you made my day, was about to throw the phone from anger. thanks a million man thank you.
I tried installing chainfire3d driver in jellybean( i didnt know then that it is not for JB). Now my nexus wont boot into os. it just stays at the unlocked bootloader logo.
1. I can get into recovery mode
2. I have wiped out the cache and factory reset
3. I dont have a update file in my phone.since nexus dont have an external sd card i cant put any file in it directly.
4. I have tried fastboot -it shows my serial ID and i am able to reboot my phone using it but whenever i try to flash recovery.img or update update.zip it shows "cannot load recovery.img" or "cannot update update.zip"
5. I have tried ADB - on using adb shell it shows "error:device not found"
6. on using Odin (not sure whether it is compatible with Nexus s) it detects my phone. when i tried to flash the stock fireware it fails and my device shows "verify image (radio) fail"
Plz help.Is my phone bricked???????
Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.
What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S
polobunny said:
Ok I don't want to be insulting, but you really REALLY need to read on the whole process of Nexus S rooting and using it.
You don't have to use ODIN at all for something so simple. You simply need to reflash a ROM/your ROM.
Mount your SD from within Clockworkmod recovery and transfer a ROM. Then flash it. Done.
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
kwibis said:
What polo says go to recovery- mount and formay- all the way down "mount sd card". Now your phone will be like a usb drive
Sent from my Nexus S
Click to expand...
Click to collapse
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
amvignesh said:
thank u for the suggestion. I just have the stock recovery right now. I tried installing clockwork recovery through fastboot but as i mentioned in my first post i get "error:cannot load recovery.img" .Is there any other way of installing a clockwork recovery?
Click to expand...
Click to collapse
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Cascabreu said:
is your boot loader unlocked??? (command: fastboot oem unlock)
then in the folder that is your fasboot exe, there is the recovery too?
Click to expand...
Click to collapse
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.
amvignesh said:
yes it is unlocked(using the command in fastboot also shows already unlocked) and yes the recovery image is in the same folder as that of fastboot.
Click to expand...
Click to collapse
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)
Cascabreu said:
Instead of writting fastboo flash recovery (file name)
Do this fastboot flash recovery (drag and drop file)
Click to expand...
Click to collapse
Thanks a lot Cascabreu.it worked . i never knew one could drag and drop files in command prompt(wonder y it didnt work otherwise, I had specified the path correctly).Thanks again..will change the thread topic accordingly....
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
I just lolled xD
Sent from my Nexus S
kwibis said:
I just lolled xD
Sent from my Nexus S
Click to expand...
Click to collapse
helppp..im also facing the same prob...i dun know how to run adb shell and those stufff after that...:crying:
C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Good job.. I wouldn't have thought of that...
Sent from my Nexus S using XDA Premium 4 mobile app
C4SCA said:
Yes!!!!! Finally i helped someone!!!!! Hit the thanks button please.
sent from my Nyan NeXus S
Click to expand...
Click to collapse
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance
tlangey said:
hi there i also need help with almost the same problem, im using alcatel one touch pop c1, i have rooted it a while ago and the decide to install chainfire 3d i didnt know it doesnt work on jelly bean and now my phone cant boot, i tried doing factory reset but nothing happens it just shows the logo and plays that start up sound but can go past that, i have no back up or anything, and please try to explain in a best possible way im not so good when it comes to computers thanks in advance
Click to expand...
Click to collapse
either u can find onlien a way to flash back to stock.
or ur best bet is to go to the store and say u got an update but it failed and that now its not turning on. Warranty will cover that
Hi Guys,
After some cleanup in CMW i accidently format EVERYTHING. (formatted all single option in CMW, afterall a bad idea) So now i'm stuck at the google logo.
Now i have the 4.4.4 KTU.zip on my computer. Can i flash this via ADB sideload (as a renamed ''update.zip''? Or can i just copy the .zip file to my Nexus from a computer?
I'm @ work so i;m stuck guessing what i must do to get this thing work!
Thanks in advance guys
i dont know what it is, but if its a rom, sideload then flash away. your phine is empty right now, no rom or anything. you need to put something into your phone(sideload) then flash it.
Yes, the whole zip file is the stock ROM in a zip file.
Luckely i can't login as administrator here or else i could get my device working here
Thanks!
Why not just start the bootloader (fastboot mode) and execute the flash-all.bat? It'a the 'official' way to completely restore your phone. I've done it several times and it always worked great
experience7 said:
Why not just start the bootloader (fastboot mode) and execute the flash-all.bat? It'a the 'official' way to completely restore your phone. I've done it several times and it always worked great
Click to expand...
Click to collapse
Thanks! Please tell me where to find the flash all bat. Find nothing specific on google...
Alfa Kenny One said:
Thanks! Please tell me where to find the flash all bat. Find nothing specific on google...
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
get the factory image here, unzip it, and run the flas-all.bat. make sure fastboot works correctly. it will flash your phone back to stock.
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Moogagot said:
Any recommendations on removing TWRP and restoring stock recovery so I can move up to 7.1.1?
I don't have a backup of the old recovery.
Click to expand...
Click to collapse
Flash the boot.img from the stock system image. This has been mentioned many times around this forum. Search is your friend.
cntryby429 said:
This has been mentioned many times around this forum. Search is your friend.
Click to expand...
Click to collapse
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Well, it's actually everywhere. However, you have to discern what apply to you and what do not. That's the danger of a public forum such a this. Everyone has an opinion. Sometimes, an inaccurate answer is provided. Most other times, the incorrect question was originally posed.
In your case, you don't need to go back to the original stock image. Assuming your bootloader is still unlocked, just flash 7.1.1 and get on with your life. Download 7.1.1 stock image from the Google developers' web site. Extract it. Edit the flash-all.bat file to remove the -w switch if you don't want to lose userdata. Boot the phone into bootloader. Execute flash-all.bat. Then you have 7.1.1.
If you don't have a recovery backup, then you're taking a risk. I have not only a recovery backup, but more importantly, a complete set of Titanium backup on my laptop.
Moogagot said:
I've spent hours searching everything from "Stock Bootloader" to "Remove TWRP" with no luck. Any advice?
Click to expand...
Click to collapse
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
robocuff said:
Download the factory image for the version of Android that you're currently running. Look inside the zip and you'll find another zipped file. Open that and you'll see a file in there that's named boot.img. Extract the boot.img file the same folder as your fastboot is in, open a command prompt in that folder flash it with fastboot.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
That will get you back to the stock bootloader and stock recovery.
Click to expand...
Click to collapse
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Moogagot said:
I tried flashing some other stuff and it bricked Google is sending out a replacement.
Click to expand...
Click to collapse
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
quangtran1 said:
Well, hope there's not a next time, but power + volume up should take you to the recovery menu. It's next to impossible to brick phones any more. Lord knows I try daily to see how I can brick my phones, just so I can assist others.
Click to expand...
Click to collapse
I broke recovery. I just says "No Command"
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
Come on man, you can do it next time. Please?
http://lmgtfy.com/?q=no+command+stock+recovery+pixel
krelvinaz said:
No you didn't, at that screen with "No Command":
Hold the Power button and press Volume Up once, and a menu will appear.
Click to expand...
Click to collapse
No menu appears. I just get a flash and back to no command.
I can get into the bootloader, but again, any option leads to the No Command screen.
Ok, from the bootloader I was able to manually flash a different image and things are looking a little better.
I now have the dancing dots and ADB see's a device attached. PROGRESS!
The devices throws errors on bootup, but it runs for now.
Please ignore. Posted to wrong thread. Sorry!
Here's the easiest way I've found to update. You'll need TWRP, so go ahead and download it - https://twrp.me/devices/googlepixel.html. Put the img file on your computer and the zip file on your phone. You'll boot into TWRP by using the "Fastboot boot" command. DO NOT "fastboot flash" it or you'll have to re-flash the boot image to get your phone out of a bootloop.
Now that you're in TWRP, you'll need the OTA file. I've only tested going up one increment so I suggest doing it that way. If you're brave, go ahead and download the latest OTA - https://developers.google.com/android/ota. Worst case TWRP won't flash it and you'll have to go back and do them incrementally.
Now that you're in TWRP and have the OTA and TWRP-RC1.zip on your phone, flash the update just like you would a rom. As soon as it successfully flashes (and before you reboot), flash the TWRP zip.
I did this incrementally from NMF260 > NMF26U > NMF26V without any issues. I believe it'll work as long as you're moving up an OTA just as the phone would have normally received them. Just remember to flash TWRP every time after you install the OTA as it gets overwritten with each OTA.
Sent from my Pixel using Tapatalk
Google needs to start voiding warranty for people who want to unlock bootloader
Moogagot said:
I broke recovery. I just says "No Command"
Click to expand...
Click to collapse
I Know this post is old, I am just researching but, sounds to me like you really need to search, read, and actually learn before you attempt anything on your phone. I am not being hateful or rude, just pointing out the obvious....
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.