What started with non-functional BT (other thread in this forum) is now a seemingly (soft?) bricked device. Here's my situation:
- dd'd a ZV9 rootedsystem.img (I was already running a ZV9 rooted system) hoping would fix my BT problems
- Instead boot now stuck at LG logo
- Can boot recovery
- Can start DL mode
- Have a backup of system.img but Send_Command.exe does nothing regardless cmd sent except LEAVE which reboots
- Factory reset, wiped cache, etc etc.
Why doesn't send command in dl mode work anymore?!?! Going insane. Please help!
Do you have the stock system.img or rootedsystem.img in internal storage?
Enviado desde mi LG-H955 mediante Tapatalk
pelelademadera said:
Do you have the stock system.img or rootedsystem.img in internal storage?
Enviado desde mi LG-H955 mediante Tapatalk
Click to expand...
Click to collapse
Yes, rootedsystem.img and backup system.img in internal storage. But I can't seem to access it.
hallucinate said:
Yes, rootedsystem.img and backup system.img in internal storage. But I can't seem to access it.
Click to expand...
Click to collapse
Poibt absolutly to the directory... But if you wipe data, or factory reset... You erase the img...
Enviado desde mi LG-H955 mediante Tapatalk
pelelademadera said:
Poibt absolutly to the directory... But if you wipe data, or factory reset... You erase the img...
Enviado desde mi LG-H955 mediante Tapatalk
Click to expand...
Click to collapse
Yep... factory reset / wiped data. Sounds like I'm screwed then.
In the same boat. if anyone finds a fix please help. I feel like my system partition is corrupted
Unfortunately, I ended up shipping to LG service. If LG would realize how much money they're losing out on by keeping their bootloader locked, it seems a likely enough incentive.
Anyway, if I had been able to use Send_Command, I'd have attempted what these guys are doing over in this thread. http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105 Have yet to see why in the world Send_Command stopped working though. Corrupt system partition as you @x4gvnferdy suggested seems as likely as any idea, but how dd failed so silently yet catastrophically I can't fathom.
Anyway, if I had been able to use Send_Command, I'd have attempted what these guys are doing over in this thread. http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105 Have yet to see why in the world Send_Command stopped working though. Corrupt system partition as you @x4gvnferdy suggested seems as likely as any idea, but how dd failed so silently yet catastrophically I can't fathom.[/QUOTE]
If you did the factory reset, you lost your rooted system.img and on this occasion the dd command wasn't working. It couldn't have executed something being removed off.
If you gonna do something kinda tricky, make sure to have system.img on your internal as there have been lot of us being forced to send the devive back to LG as none have seemed to figure this out. I've heard that in US guys get the device back in a week, I was without that 30 days. I gave upon any mod on my H955. Just rooted it again, put xposed on and finito. This snazzy phone is doomed because of no bootloader unlocked nor we get Android M as I fear. Globally it didn't bring money LG expected so they really don't care what we think.
I have the same issue. After flashing with dd, my phone now boots up to a No Command screen. I can enter recovery and download mode, but Send_Command.exe no longer works.
If u could boot into DL why don't you just try LG Mobile Support Tool or LGUP?
Related
Hi, I have had this issue for a while now where my custom recovery looses the ability to mount data, this is the message I get,
E: could not mount /data to set up /data/media path. When the problem occurs which can be going into to recovery from any custom rom I just reboot the phone again which has always rebooted ok, but I am worried that it may not reboot ok some time in the future breaking my phone.
I have tried all 3 custom recovery's so I don't think it's a recovery problem, anyone have any ideas what the problem may be.
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, can I fastboot flash stock cache.img on any rom ?
maxal said:
Thanks, can I fastboot flash stock cache.img on any rom ?
Click to expand...
Click to collapse
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
maxal said:
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
Click to expand...
Click to collapse
fastboot flash cache cache.img
Tapatalk-kal küldve az én Nexus 5-el
maxal said:
fastboot flash stock cache.img
Click to expand...
Click to collapse
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
rootSU said:
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks fastboot command worked that time. I normally use adb and fastboot commands but I have never had to use cache.img command before, Thanks again :good:
Update: I tried what rootSU said but it didn't resolve my problem so I tried one last thing which was to flash a factory image using the LG Flashtool and so far every thing seems fine. So should anyone else have the same problem that I had with their recovery give the LG Flashtool ago. Should my original fault reoccur I will post an update.
For what it's worth, I had the same issue as the OP. I didn't want to flash the .tot, because my computer was being weird(it said COM41 was in use, because I already used the LGFT for my G2, didn't want to risk it). Basically I just RMAed it, because all fixes were failing. Using e2fsck, flashing stock cache, etc. I could temporarily fix it by flashing a factory image, but when I flashed a new ROM, it would happen again. So if it keeps happening, just send it back. :good:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
maxal said:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
Click to expand...
Click to collapse
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Koopa777 said:
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Click to expand...
Click to collapse
No problem I will test PA 4.2 beta tomorrow for you.
I had the same problem on an installation of a kernel that didn't boot atop a CM rom. When it bootlooped, I went into recovery and found the infamous could not mount /data. I tried rootSU's recommendation about wiping cache several times and flashing a cache.img but it didn't work for me. I was about to do the whole factory stock image thing (and thus wipe my sdcard) when out of desperation to avoid that, I tried something that surprisingly succeeded. The following steps are for a newbie but presupposes a working knowledge of how to use adb and fastboot commands.
1. Download and copy a known stable ROM's zip file into your SDK's platform-tools, renaming it ROM.zip
2. Boot you phone into (TWRP 2.7.0.0) recovery
2. Choose ADB sideload in Advanced
3. From your computer's DOS prompt in the SDK platform-tools directory, type adb sideload ROM.zip
When it's done sideloading, it will flash
4. Choose reboot system
It will boot and get a series of FC's of android process and dialer
5. Hard reset into bootloader (hold down the power button until screen goes off (in like 7 secs) immediately hit vol-down) and choose recovery
Voila! Rebooted into recovery for me with data mounted as normal. No need to flash factory images!
Hope this helps and good luck!
I know that this thread is nearly a year old, but just wanted to report that my phone soft bricked when I flashed a kernel (without flashing the rom). TWRP (2.8.5) was unable to mount data, storage, /data/media. When I went into TWRP/Advanced/File Manager there was nothing in the sd card. After an ADB flash cache cache.img it was still the same. I decided to follow the @reeper000 post and it booted into the ROM i flashed (Slim Lollipop version) and it came up with only a couple errors. I was then able to go into TWRP and restore a nandroid backup and all is fine. I was sooooooo close to erasing data/restoring to a factory image!!!!!! THANKS, @reaper000!
Glad all well. I had 2 nasty surprises yesterday. First I flashed a nandroid
, only one I had. It kept going past 100 %on loading the data. Went to 300%! I'd one rom with Gapps I'd not tried so I thought saved.. Aghhhhhh Noo when it came on said playstore support missing. Had to tap like mad to get it off the screen in between putting my acc in. 2 hours later it linked and downloaded the missing file. Thank god. Then my baseband went! I was at my wits end. Decided I'd nothing to loose with a factory reset which fixed it. Good job as the new battery came today! Now I test backups and have two different ones
What Happens?
My phone weather rebooted from adb, bootmenu, powered off and then on, rebooted from recovery, always boots in bootloader.
It says UTAG "bootmode" configured as fastboot
From bootloader I can go to recovery or regular power up! it all works.
Just I have to face the bootloader every time my phone turns on!
When did this occur?
I don't know, I flashed 3 firmwares back-to-back and then got back to GPe. I booted to bootloader in all ways. I remember me going to bootloader from my XT1033 stock ROM's boot menu, then once using adb reboot bootloader, and once going by pressing VolDown+Power. So I kind of messed up. And then after setting down to a ROM. I rebooted and realised!
What did I try to recover
1. Flashed bootloaders from different firmware
2. Went back to Stock
3. Tried all adb reboot commands
4. Tried all reboot methods from bootmenu
Help Please!
Everything else is working fine, its not a panic attack, but i need a solution
Do "fastboot oem fb_mode_clear"
Enviado desde mi Moto G mediante Tapatalk
Take a backup. And make a full & clean install of stock ROM. Your problem should be solved
I would suggest not to mess with BL , you will get in to trouble
Sent from my XT1032 using Tapatalk
reversegear said:
Take a backup. And make a full & clean install of stock ROM. Your problem should be solved
I would suggest not to mess with BL , you will get in to trouble
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
I have done that more than once!
That doesnt solve the problem! and the prooblem didn't start becaues of BL.
Going to stock doesnt change anything!
Boss442 said:
Do "fastboot oem fb_mode_clear"
Enviado desde mi Moto G mediante Tapatalk
Click to expand...
Click to collapse
That solves the problem!
What is the purpose of fb_mode_set/fb_mode_clear
I would liked to know more!
I asked this question at http://forum.xda-developers.com/showthread.php?t=2738055
But i didnt get a reply there as well!
reversegear said:
Take a backup. And make a full & clean install of stock ROM. Your problem should be solved
I would suggest not to mess with BL , you will get in to trouble
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Too lazy to not try this:
fastboot oem fb_mode_clear
solved the issue in 1 sec.
help
Hi i already try that fastboot oem fb_mode_clear but still nothing if i turn the phone off as soon as i turn it un it goes back straight to bootloader i have to press normal powerup in order for the phone to boot what else can i do
Bricked MOTO 2 G XT1063 stuck at Bootloader - utag flash fail configured as fastboot
hi mine is XT1063 Bricked, after doing fastboot oem fb mode clear, still i am not able to boot normal.
it says:
boot up failed
failed to validate ftm image
that means its not fih ftm mode
load and validate boot image
failed to validate boot image
Hi guys, i just made a mess with my wife Moto G, i had Tesla ROM installed in it, everything was working fine but i just decided to make her a Backup using TWRP, the backup process went fine and i rebooted the phone, now i was stuck at Motorola Logo and can enter to Recovery anymore, tried fastboot erasing userdata and now i am stuck at ROM logo but nothing more.
I appreaciate your help. Thanks in advance.
Erasing userdata allows you to boot back into TWRP, but ROM is corrupt and needs to be reflashed. Best do a factory reset in TWRP and flash.
lost101 said:
Erasing userdata allows you to boot back into TWRP, but ROM is corrupt and needs to be reflashed. Best do a factory reset in TWRP and flash.
Click to expand...
Click to collapse
Thanks, i did that and now I dont have any rom to flash in sdcard. Tried transfering a zip using fastboot and the pc recognizes the phone but when i try it says it cant or phone is disconnnected
I was using 5.1.1, can i downgrade to stock 5.0.2 without problem?
eldoggor said:
Thanks, i did that and now I dont have any rom to flash in sdcard. Tried transfering a zip using fastboot and the pc recognizes the phone but when i try it says it cant or phone is disconnnected
I was using 5.1.1, can i downgrade to stock 5.0.2 without problem?
Click to expand...
Click to collapse
ADB push or sideload will work in TWRP. ADB push Rom.zip /sdcard
You don't state want Model Moto G you have.
Tried Adb push and didn´t work, say device not found but i could flash twrp recovery in fastboot and in fastboot command it recognizes the phone. Is a 1032.
I appreciate your help, i have recovery, just need to transfer the rom file but at the moment can´t. Any other way?
Flash stock firmware.
motofirmware.center
Sent from my XT1031™
Similar thing happened with my xt1033. It got stuck at bootloader after taking a backup with twrp. Advice you to flash the latest version of twrp(forgot the version name, but it has material design), that has resolved the issue for me, I could take a backup and reboot. And you should use mfastboot to flash the stock firmware into your phone. Even for me, the phone was not getting detected, but the files were flashed anyways. Check other forums for the steps to flash stock firmware. Make sure to extract all the files from the zip of the stock firmware in the same folder where mfastboot is.
Sent from my Moto G using Tapatalk
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
Debanka said:
Similar thing happened with my xt1033. It got stuck at bootloader after taking a backup with twrp. Advice you to flash the latest version of twrp(forgot the version name, but it has material design), that has resolved the issue for me, I could take a backup and reboot. And you should use mfastboot to flash the stock firmware into your phone. Even for me, the phone was not getting detected, but the files were flashed anyways. Check other forums for the steps to flash stock firmware. Make sure to extract all the files from the zip of the stock firmware in the same folder where mfastboot is.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Its version 2.8.7 for me
Sent from my Moto G using Tapatalk
Thanks guys, well, after trying a lot i could put a zip ROM in TWRP using ADB push, tried to flash it and when try to moun cache data etc it says it failed. Can´t mount nothing by itself. Will try TWRP 2.8.7 now and try to flash stock, if i make a downgrade to stock kitkat will damage the phone or is fine? i had lollipop 5.1.1.
EDIT: Thank you very much guys, i installed TWRP 2.8.7 and Stock firmware using mfastboot (That was a great solution Debanka) Now i am in kit kat but i dont care as soon is working and i now lollipop will appear soon in the phone. Thanks again!!!
Hi everyone. First of all, excuse me for my not well English. Today I've tried to reset my Motorola Moto G XT1032: it's a GPE converted by me some months ago. I've not succeded to reset it using Android settings. So, I've tried using the flashboot menu (Volume down + power, Recovery, Volume up + power, delete all), but all data has remained on the phone.
So I tried to re-flash GPE firmware, as I did some months ago, but after the process the phone does not boot and stucks on Google boot logo with an the opened lock. I've tried many guides but I've not succeded to repair. Please, help me! Thanks.
P.S. I'm using Linux for fastboot and other tools.
I'm trying again by re-flashing. Now I'm seeing that there is an error on flashing partition.gpt. Why?
u can change a rom
Hi !
I have the same problem, beside all that my phone is in bootloop i cannot install any custom recovery, what ever custom recovery i flash i get hab check failed or partition mismatch and then i end up with the stuck recovery (i know i should not reboot right after the flash and i go to recovery mode but the moment i boot up i see the old recovery)
I am not sure what is wrong but i guess there should be something wrong with my partitions. the only rom that gets flashed with no errors (but still gets stuck in the bootloop) is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC
I managed to see my files via the command fastboot boot recovery recovery.img but then i only have read access, If only i had write access i could upload some files to my phone and get it working with updating from SD card .
any help is appreciated
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
alexandrino said:
Have you guys tried flashing stock firmware image (not flashable zip)? Take a look at http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795 and at the guide in the OP on how to flash it.
Enviado de meu SM-G900M usando Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. Is nt that exactly what i did ? i mean i looked at the files . there ate generally two types of files. some are XML which i need to use fast boot. the other one is a zip file with several folders in it which i dont know how to flash. do you mean there is my answer?
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
alexandrino said:
Inside the factory firmware file you should find several files (.img,. bin, etc.) inside the zip which you should flash following this guide: http://forum.xda-developers.com/showthread.php?t=2542219. Just remember to not downgrade (or just flash a Lollipop image)
Click to expand...
Click to collapse
I have followed the guide but maybe here is actually my problem
there are two kinds of ROMS to my knowledge. one has several files in it boot.img recovery.img chucnks etc... and there are no folders in the ROM file it is usually called XML
second type is a zip file like this one http://forum.xda-developers.com/devdb/project/dl/?id=14940 if you exract it there is a file named boot.img and two folders META-INF and System.
in the system there are numerous files but there is nothing to flash. the only way i know is flashing via fastboot. i dont know how flash these zip files.
one more point is that i dont have a custom recovery ( and i cannot install one since it does not show up after each reboot for an unknown reason)
from what i read people upload these second type zip files to their phone and then install it with their custom recovery software, but i dont have that luxury!
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
alexandrino said:
I have just noticed that we have been discussing your problem in two different threads (I thought they were from different people).
So you have already tried using fastboot to flash all those bin and img files and it still does not work? What error are you getting while trying to perform those commands?
Click to expand...
Click to collapse
yes i guess. we can continue here, and thanks.
For anyfirmware i get hab check failed and partition mismatched errors
for recoveries i get mismatched partition error
they said you should ignore them but i am not sure if i should!
the only firmware which flashes flawlessly is XT1032_FALCON_RETFR_5.1_LPB23.13-56_cid7_CFC.xml by works i mean it just does not come up with any errors and it flashes but still the bootloader loops.
by the way, is there anyway i could upload some images to the device ? i cannot side load adb cause it comes with verification error in the middle of upload for anything i tried.
Thank you everyone for the replies. Some months ago I converted my Moto G to GPE as reported in this guide. When I tried to do it again (with the purpose of resetting the device) I got the issue descripted in my first post. But I was doing the all procedure using Ubuntu: I opened the batch file, written in Windows Batch Language, and I executed all the commands through the bash. Maybe, that's the thing that has made the phone not starting anymore. In my last try I've followed the procedure using Windows and now everything is ok.
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.