Database Users

flash recovery error “out of memory”

my magic is TIM's G2
the rom is myhero 2.0.5 but the recovery is too old, so i want to flash the recovery to Amon's recovery 1.5.2.
but when i flash_image recovery /sdcard/recovery.img
some error type. all is "out of memory". then i open the phone, i can't into the recovery.
it's so bay. now i can flash 1.2.3H into my Magic, i want flash 1.5.2, help please.

It won't work if you only type that. I assume you're using a terminal emulator. I'm pretty sure you only forgot the mount command, but I'll go trough everything to be sure.
All you need to to is to flash the recovery image again. As you're having MyHero, I assume you're having a 32A. Therefore, make sure you have the recovery-RA-sapphire-v1.5.2H.img, not the recovery-RA-sapphire-v1.5.2G.img.
Copy the file to the root of your SD, no need to rename it.
Open up your terminal emulator, and type:
Code:
su
You should get a root request, accept it. Then type in:
Code:
mount -a
Don't worry if you're getting errors here, that's normal. Lastly, type in the following.
Code:
flash_image recovery /sdcard/recovery-RA-sapphire-v1.5.2H.img
It's just normal to get errors here too. Or, at least I do.
Start your phone in recovery, and it should work.

tks
i will try later

[Q] problems with CW [SOLVED]

EDIT:
In my humble opinion, there's a new blade around, since all the sources for recoveries on english websites don't work with my 256mb "new" blade (jan 2012), while many people using older chinese blades from china unicom can use all the software found online.
flashing re regular cw with rom manager, adb won't work and give errors later shown in this post.
the only recovery i found that will actually work and let me install another rom is a recovery i found on a chinese forum.
downolad this recovery: http://dl.dbank.com/c0sw12amzu
chinese forum: http://bbs.anzhi.com/forum.php?mod=v...fromuid=423904
in that forum u can't see the download link because you have to log in and write a message in that topic in order to see the link.
to flash this recovery go to this thread, page 3 first post and follow the instructions from matt4321.
I am waiting for someone to try with "new blades" with the same problem as mine.
ORIGINAL POST:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.

Flash cwm using rom manager again

i tried but nothing... :/
thanks by the way.

Does anyone knows how to install CW via adb? i found how to do it here http://forum.xda-developers.com/showthread.php?t=852905 but i have no idea how to download the latest cw for my china uni blade.
thanks if anyone has some hints!

Are you sure you installed the right version of CWM according to your phone's GEN?
Sent from my Blade using XDA app

well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/

Do not use CWM's latest verson
tetora said:
well, i guess so, my phone is gen2. i installed cw from rom manager, i just selected zte blade. i tried to reinstall cw, to reinstall rom manager, tried to dowload cw with wifi or data internet connection, same result as 1st post, or either like phone stuck on start screen when booting into cw (but the phone was working).
btw, i am using the latest cw.
i wonder what's wrong with my zte :/
Click to expand...
Click to collapse
I guess that there's nothing wrong with your device. My Blade is similar to yours (256MB RAM) and the last version of CWM does not work: I even can't enter recovery mod with it. The solution is to use CWM version before the last one (5.0.1.0 I think).
You can easily install it via ROM Manager: Just go to the last option (CWM all versions and select the desired one).
[]'s
Ah, the Best rom so far to our stripped Blade in my opinion is Squadzone's CM7.2.0 RC 5.6

5.0.1.0 isn't working... could you please check which one you have on your blade?
btw thanks, i didn't see that option in ROM Manager!
i am trying with the 5.0.0.8, just in case... i hope it will work...
edit: no, it doesn't work... :/ i'll try with the previous one. with 5.0.0.8 i can't even boot in cw.

Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.

tetora said:
Anyone has a tip? it really doesn't work. i really have no idea how to do it via adb, if this could fix the problem.
Click to expand...
Click to collapse
I guess the only option for you is to try Amon RA recovery. I don't even know if it still exists. Check out the CM wiki regarding flashing. It might be there.
Sent from my Blade using XDA app
---------- Post added at 06:30 PM ---------- Previous post was at 06:18 PM ----------
You can follow this if you want but the versions of recoveries are old.
http://forum.xda-developers.com/showthread.php?t=915143
Sent from my Blade using XDA app

the problem is that i can't enter recovery mode (i can, but i can't use it) and i can't get the "green android" screen.
to my extent, i have no way to write anything via usb onto the phone. am i right?
i tried all of the cw versions, but all of them give me the same error i posted in the 1st post...

I think CWM can't find your root. Very weird issue. Will check and get back.
Sent from my ZTE Blade using XDA app

Try rooting the phone again! I had problems with my sisters blade when Z4root wouldn't perm root, only temp root (even if i pressed the perm root button).
Use zergRush to root again (or something similar) then flash CWM again through fastboot or adb

z4root actually works, apps that need SU enabled work also when i restart the phone.
zergrush doesn't work. everything seems fine but in the end the phone is not rooted.
plus, i can't use fastboot or adb since the recovery mode does not work, so i have to reinstall it from rom manager.
and yes, i tried to root it again, but with z4root, but nothing.

You should be able use adb with the phone on. Make sure USB debugging is enabled. Install drivers, use adb to reboot into bootloader, then flash cwm through there. Maybe there is a problem with the way rom manager is trying to flash cwm.
Sent from my ZTE-BLADE using Tapatalk 2

tetora said:
hi everybody, i tried to look also in the forum with the search and i didn't find anything relevant...
i have the blade from china unicom, i rooted it and installed cw. everything was almost smooth (i downloaded the wrong z4root, but then i got it right).
when i tried to make a backup or anything else vis CW it shows me this:
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/command
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
E: can't find misc
E: failed to find "cache" partition to mount at "/cache"
basically i can't do anything. i can't even make a factory reset.
what went wrong?
thanks to anybody that can help me.
Click to expand...
Click to collapse
it could come from root access or you have made a bad manipulation, I have got a similar problem, my recovery has been deleted after have tried to flash one .

thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.

i found some drivers here: http://android.modaco.com/topic/319156-winxp7-zte-blade-drivers-and-adb/ and now it's recognised from the pc as "android bootloader interface", but fastboot is not working, it doesn't see the device. :/

tetora said:
thanks matt, but I still can't do anything. adb command works from command line, but fastboot is not working.
the device is recognised when i type "adb devices" when rebooting in recovery, but any commands starting with fastboot give back an error "fastboot is not recognised as a command ..."
maybe it's the way i added fastboot. i found the fastboot.exe and put in the android-sdk\tools folder. even if i restart the pc it's still not recognised.
but if i go in the folder where fastboot.exe is it works, well, kinda, because "fastboot devices" gives me nothing. "fastboot \?" gives me the list of every option i can use, but i can't use them.
i guess it is like this because when i reboot the pc says there are no drivers for the phone. i actually tried to give him the drivers that come with the android sdk and the ones from zte, but both of them do not work. I guess that with the right drivers it will work, but i have no idea where to get them. am i right?
thanks for the patience.
i almost forgot, usb debug is enabled.
Click to expand...
Click to collapse
Okay so it seems the issue is that fastboot won't work and there's some drivers issue!? I remember a while back when i had issues with getting fastboot to work with my ZTE blade, I can't remember where i got the drivers from but recently got my Xoom and the drivers installed from the device wouldn't work, so used koushs drivers for his tether app which worked, give those drivers a go but for ZTE of course, http://www.clockworkmod.com/tether/drivers
you could also try flashing CWM via adb which is what I used to do when I had issues with fastboot, i've got the instructions and commands saved on my computer if you want me to upload them? but then again a google search would probably produce the same results but i've used these before and know they work.
EDIT: also after rereading what you said and saying fastboot isn't recognized as a command (sorry if this is a dumb point) put when in the command prompt you are changing the directory to where the fastboot file is located right?!

as I understand, adb can't flash the recovery, only fastboot.
the drivers are working, windows xp recognise the phone both in recovery and in bootloader mode.
yes, i am running fastboot from the path fastboot.exe is located.
with google the only thing i get is rebooting via adb into bootloader and use fastboot...
so far no luck...

Someone just .. help :(

Ok so i was normally using my phone and it randomly just said UI system crashed and the homescreen and everything wouldnt show so i restarted the phone and then it was just stuck on the intro screen..
after waiting for 20 min of it doing that i went in recovery and formated system cache and all that and now it wont go past google..
i tried to go in MOUNT and mount system and data it works but it wont let me Mount the sdCard why is that? how do i fix this
-
Any help would be appreciated .

ronnyg12 said:
Ok so i was normally using my phone and it randomly just said UI system crashed and the homescreen and everything wouldnt show so i restarted the phone and then it was just stuck on the intro screen..
after waiting for 20 min of it doing that i went in recovery and formated system cache and all that and now it wont go past google..
i tried to go in MOUNT and mount system and data it works but it wont let me Mount the sdCard why is that? how do i fix this
-
Any help would be appreciated .
Click to expand...
Click to collapse
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.

gee2012 said:
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.
Click to expand...
Click to collapse
Yes my phone is rooted. and i do have a custom recovery (CWM) . and so i open CMD in my SDK file and say this line " adb push namerom.zip /sdcard/"?

ronnyg12 said:
Yes my phone is rooted. and i do have a custom recovery (CWM) . and so i open CMD in my SDK file and say this line " adb push namerom.zip /sdcard/"?
Click to expand...
Click to collapse
Yes, that`a all. Place the rom you want to push in the platform-tools folder though or adb will not find it. It`s best to open CMD with a right click and open as administrator.

gee2012 said:
Do you have a custom recovery? If yes use adb to push a custom rom to the sdcard: adb push namerom.zip /sdcard/. If you have stock recovery try to get in fastbootmode and push a custom recovery (TWRP pr CWM) and do the above.
I assume you have root, if you don`t you have to reflash a factory image in fastbootmode from here https://developers.google.com/android/nexus/images#occam.
Click to expand...
Click to collapse
Ok it worked. Really great help man thanks

ronnyg12 said:
Ok it worked. Really great help man thanks
Click to expand...
Click to collapse
Happy you fixed it mate :good:

[Q] Won't boot after ROM install

Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.

juckeyy said:
Hello! My first post here on the forum
So I've got this problem that my Samsung Galaxy S4 won't boot properly after the rom install.
The recovery I've been using is CWM and after the install when I press reboot the phone vibrates and the "Samsung Galaxy S4 GT-I9505" screen shows up and then the phone immediately shuts down again. Now I can't get the phone to start... :/
Thanks, Joakim.
Click to expand...
Click to collapse
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?

gee2012 said:
Do a data factory reset reflash the rom again and clear the caches and reboot. Which rom did you flash?
Click to expand...
Click to collapse
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?

juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.

juckeyy said:
Hmm alright, I tried to flash 4.2.2 google edition. But the problem is now when I go into recovery my phone can't find any ROM to install.
It feels like it's broken. And I've got no adapter for the micro-SD card so I manually can put in a rom to the SD :/
I can get in to the CWM recovery but in "install zip update package -> choose ZIP from sdcard" there is nothing. So all I can do is try to get a rom into the external SD and flash from there?
Click to expand...
Click to collapse
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom

samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)

gee2012 said:
I`am out of thanks and will thank you tomorrow, wasn`t sure adb sideload worked on Samsung devices (i now it works on HTC, Sony and Nexus devices)
Click to expand...
Click to collapse
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx

gee2012 said:
Yes, do that. Power down the phone, take the sdcard out and place a rom on it, boot into recovery and flash it in CWM. If that gives problems flash a stock rom in downloadmode with Odin.
Click to expand...
Click to collapse
Hmm, couldnt find my adapter. Is there no way to flash in the stock rom with odin?
samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Hmm wow seems like a long process but i'll try it.
Thanks!

samersh72 said:
NVM my friend
adb commands work in custom recovery mode even if "usb debugging" is disabled.
it is just a simple push to sd :good:
EDIT: @gee2012 can you do me a favor, since i dont have my s4 with me right now, can you try if adb recognized your phone in custom recovery mode?? i just want to be sure
Code:
adb devices
thx
Click to expand...
Click to collapse
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).

gee2012 said:
No bro, the device is OFFLINE. You would have checked the box first when the device was on in usb mode. Like you have to with a nexus (fingerprint).
Click to expand...
Click to collapse
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend

samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
thank you my friend
Click to expand...
Click to collapse
Wait one minute bro.

samersh72 said:
are you sure you are in custom recovery??
no, you need usb debugging enabled only when the OS is booted.
in custom recovery, you will see the serial number with "recovery" at the right in cmd
adb in custom recovery works fine with my SII plus
Code:
C:\Users\Samer\Desktop>adb devices
List of devices attached
014E1E761000700C recovery
C:\Users\Samer\Desktop>
thank you my friend
Click to expand...
Click to collapse
Hey when I type in adb devies it says mine is unauthorized :/

samersh72 said:
push rom with adb. (you must have adb file on your pc)
boot into custom recovery, connect your phone, put the rom in with adb folder, open cmd prompt in the adb folder and type:
Code:
adb devices
you must see serial number
Code:
adb push name_of_rom.zip /data/media/
or
Code:
adb push name_of_rom.zip /sdcard/
Code:
adb reboot recovery
then install the rom
Click to expand...
Click to collapse
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
-Edit- also with usb debugging disabled the serialnumber is shown.in recovery.

juckeyy said:
Hey when I type in adb devies it says mine is unauthorized :/
Click to expand...
Click to collapse
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
gee2012 said:
Yes, you`re right. The serialnumber is shown in recovery mode after typing adb devices in cmd. Was on stock ( + stock recovery) and not rooted.
Sorry it took so long. I have usb debugging enabled btw.
Click to expand...
Click to collapse
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os

samersh72 said:
make sure you have the right driver for samsung
you must have custom recovery and not stock recovery to be recognized by adb command
use the latest adb file version (attached)
make sure that your phone in custom recovery mode
put the rom into adb folder and open cmd in that folder
push the rom
+1
it will not recognize your phone in stock recovery :good:
EDIT: yes, enabling usb debugging is used only when your phone is booted in os
Click to expand...
Click to collapse
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?

juckeyy said:
I've got the right driver, my phone is in CWM recovery and rom is in the adb folder.
What do you mean with "open cmd in that folder"?
Click to expand...
Click to collapse
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it

samersh72 said:
open adb folder where the rom included.
"shift" + mouse right click, choose "open command window here"
download adb.zip 1.0.31 attached in my previous post, if you dont have it
Click to expand...
Click to collapse
I did still didnt work. Now I managed to get a ROM into my SD-card so now i'll boot custom recovery and try to install.
lets hope for the best!

Hey again!
Just wanna thank everybody for the help. I solved everything with flashing in stock ROM with odin.
I'll try again tomorrow with other ROM:s
Thanks, Joakim.

had same problem
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.

fezz64 said:
hi there my s4 done the same after trying to install cy 10.1
I made a back up first with cwm
then went to install cy 10.1 rom after it said it was done I reboot and got the same problem
I took out my battery waited couple of mins and booted up in cwm mode then went to restore and installed my back up
alls working again but still have not found a fix to install custom roms.
Click to expand...
Click to collapse
Is it the same with other roms?
Make sure the download is not corrupted.
Wipe data, cache and dalvic after flashing the rom, reboot
sent from my Galaxy

download mode

I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?

May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler

What's up now ?
Sorted it out or still issues there ?

I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going

bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #

Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.

bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"

I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"

I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...