Hello:
I'm having a frustrating experience attempting my first root of my G2X.
I've had a previous thread from yesterday, attempting to do things from the Mac side:
http://forum.xda-developers.com/showthread.php?t=1172487&highlight=velanche
As of now, I've decided to revert to Windows 7 on my Mac to try and rectify things. I'm able to use One-Click Recovery Flasher, following the instructions, to flash the phone. I then downloaded an earlier nightly version of CM7, installed it on my flash drive, and did the install via ClockworkMod.
I had no errors from CWM, from the wipe to the install. I then choose the reboot open, and it powers off my phone.
Upon attempting to turn on my phone, I would get the LG screen, followed by a quick flash, followed by another LG screen with some horizontal blue background behind it. I'm taking it that it means that it's stuck, because I've waited 10 minutes before having to do a battery pull.
I did at one time attempted to flash back to the stock T-Mobile, but when the LG screen came it, it would just remain there without any progress.
At this stage, I don't know where else to go. I'm not sure if there's something amiss, because my phone, as far as I know, as been erased. If there's a way to progress to CM7, I'm game. But one thing I really need to do is to get my phone back.
I didn't backup my phone's contents initially because I was going to recreate everything anyway. Now I'm in a not-so-good place, save having to get a phone exchange.
Any assistance would be appreciated; thanks so much.
V.
Download one of the "Stock Rooted Nandroid Backups" from the development section, stick it on your SD card and do a Nandroid restore from CWM. That should get your phone working again...
On the CM7 installation problem, I have no idea what that could be. I've been flashing ROMs on Android devices since the G1 first came out a few years ago and the only reasons I had bootloops were from me trying to flash without wiping or flashing an unstable build.
Sorry to digress for a second here, but you DO have the T-Mobile branded G2x and NOT the Optimus2x, right?
Working on It
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
Sent from my Nexus 5g using XDA Ultimate App
velanche said:
Hey thanks for the help.
I have a T-Mobile G2X, so I should have done everything the way I expected. Then again, things should have worked if I did.
So I installed the Nandroid recovery for my phone, and attempted recovery via CWM, but ended up with a MD5 mismatch error (whatever that means).
I even went so far as move select files from my SD card. I formatted it, then put in those select files i wanted to keep.
I tried again, and no change.
Any suggestions on how I should proceed? Thanks!
V.
Click to expand...
Click to collapse
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
Sent from my LG-P999 using XDA Premium App
LordButtersI said:
I get the same kind of "just not going to happen" errors when I try to install EaglesBlood. I've found no solution, though CM7 works just fine. I don't know what to tell you, really...
I don't know if this might have anything to do with why I've had problems getting CM7 to work, but I've noticed that when I plug the phone either into Windows or OS X, I've somehow lost the internal drive. I know that it's there because I've found a whole bunch of files on it while in CWN, but I'm suspecting that there's some link between neither computer seeing the internal drive and the issue with getting the phone to boot.
Yes, I can mount the external drive, either from CWM's mount on both platforms or when I press both volumes on my phone and plug in to Windows 7 via USB.
Do you have any insight on this? I was watching a few of The Unlockr vids, and I noticed that even though the guy's phone was rooted and flashed, he still could boot into his phone until he was ready to put on the new ROM (CM7, in this case).
Thanks!
Click to expand...
Click to collapse
scooter247 said:
The md5 mismatch will happen if you try to copy and past the files. Try it again but this time unzip it directly to the fold where it should be. Do not copy and past the unzipped folder. This is also someones backup so you must go through the restore option in cm
I tried on the OS X side to do this, having to download an RAR app. I found the LG file, and told the app to extract it to the backup directory on my phone. I tried the restore again in CWM, but still a mismatch.
I will try it in Windows 7 tomorrow, and will let you know the outcome.
I'm beat; spent the whole weekend on this phone modding biz. I suspect I'll be really good by the time I finally am able to get things working.
V.
Click to expand...
Click to collapse
Is this an old SD card? Perhaps some bad sectors on it? Without holding the phone in my hands I can't think of anything else. Other than double check your steps, re-copy the files and try, try again.
The SD card is not old; about 2 months old. I tried formatting the card via Windows 7, but did it in FAT32. I take it that it's supposed to be formatted differently? The card is 16GB, but when I looked into CWM it's limit is 4GB.
I tried the steps again, and still get the same md5 mismatch. Is my guess correct that the card is supposed to be formatted a certain way? Unfortunately, I can access the previous OS via my phone, nor will the internal memory appear when the phone is plugged into the computer. However, I am able to mount the SD card within the computer's OS.
I almost feel like walking away from it for a week, but that means I'll be stuck without phone access for awhile. Tips or suggestions are most welcome.
BTW, there's apparently alternate instructions to deal with the md5 mismatch error. Though in Windows the NDIVIA driver is loaded for the phone, I tried the adb shell command but my device isn't detected by the software.
Thanks again,
V.
Related
All,
Noob here as far as Android goes. I picked up a Galaxy S Captivate a few months ago from AT&T and I got a notification saying Froyo was available. Of course, Samsung made it near impossible to do, so I figured "I'm a computer programmer, I can do these kinds of things".
Using Odin, I put on a version of Froyo. It was... not a good ROM by far (I didn't know all the great ones were here) and after the 4th or 5th random crash, I decided to try something different. However, at one point the phone bricked. I was finally able to get Odin to push back 2.1 Eclair (the stock AT&T version), but since then, I get a "SIM Network Unlock Pin" prompt. I followed the instructions to grab the unlock code from the bml3.back file, but it doesn't work. I've tried upgrading to various Froyo's, but they don't work either. AT&T tried a new SIM card, but that didn't work.
At this point, my Android abilities are done. I have no idea how to fix my phone. AT&T can't help and of course, Samsung will charge me for a repair (I have no idea how much that is).
Can anyone think of a way to get rid of the SIM Network Unlock PIN thing? This is a legitimate phone on a legit plan. The Continuum 3.5 Froyo runs great, it just can't see my SIM Network card and a phone without that is...well, bunk
Thanks for the help, I wish I could retrace all my steps but I was an idiot and didnt write it all down.
R
I have never heard of anyone overcoming a lost PIN issue without completely reformatting the phone and reinstalling a ROM.
Try flashing a new 2.2 rom and using the froyo unlock method in the dev section (http://forum.xda-developers.com/showthread.php?t=831569).
Since you mentioned you're a programmer, I'm going to assume you're comfortable with adb. Make sure you back up /efs/ to your sd card, then again to your computer before you try it as rom flashes will typically not overwrite this partition. I suspect your nv_data.bin or some other part of your /efs partition is messed up, which is why flashing most roms won't fix it. I'm not sure if the one click stock odin will do anything, but it's also worth a shot if you haven't tried it yet.
There's also a backup of nv_data.bin in /efs, you can try copying that over your existing nv_data.bin and rebooting to see if it helps.
modest_mandroid said:
Try flashing a new 2.2 rom and using the froyo unlock method in the dev section (http://forum.xda-developers.com/showthread.php?t=831569).
Since you mentioned you're a programmer, I'm going to assume you're comfortable with adb. Make sure you back up /efs/ to your sd card, then again to your computer before you try it as rom flashes will typically not overwrite this partition. I suspect your nv_data.bin or some other part of your /efs partition is messed up, which is why flashing most roms won't fix it. I'm not sure if the one click stock odin will do anything, but it's also worth a shot if you haven't tried it yet.
There's also a backup of nv_data.bin in /efs, you can try copying that over your existing nv_data.bin and rebooting to see if it helps.
Click to expand...
Click to collapse
Thank you thank you thank you thank you. That was exactly it. I now have a phone again!
This place is great, but it's a bit overwhelming when you first join. Couldn't find that article on my own, but it was there!
Cool, glad to hear you got it running again.
Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
I was wondering if there are any ROMs or Apks for the P500 that work for the P506 also. I believe I have a 2.2.1 gingerbread rom, I put a rom on here months ago and my memory is horrible so I'm not entirely sure that's what I have and honestly I've been seeing all these new things on here for modded music players and other things and I don't wanna download it and have it mess my phone up cause I'm using a different type of phone. So would these things work on a P506 even though it says P500?
Sent from my LG-P506 using Tapatalk 2
Any apk that runs on the p500 will run on the p506. As for roms, you should be able to flash a p500 rom, but you have to flash the p506 version of this kernel: http://forum.xda-developers.com/showthread.php?t=1587209 in order for everything to work properly. Make sure to make a backup in recovery before flashing anything so that if anything goes wrong you can just restore it back to the way it was.
Well I have backed everything up using ROM toolbox, titanium backup, android assistant and a couple other things. I'll do a couple more backups though to make sure. Also what would you suggest for gaming and music?
Sent from my LG-P506 using Tapatalk 2
For music I would recommend installing cyanogenmod 7 and tweaking the dsp manager app, I never noticed a difference with beats audio or team acid's audio thing, but the dsp manager you can tweak while musics playing. For gaming, cyanogenmod 7 along with the kernel I linked up above are probably your best bet. Make sure that you make a nandroid backup in recovery, that's the most important type to have when testing out roms.
I'll check it out, thanks man.
Edit: Did a nandroid backup and now my phone won't work. It says Fastboot mode started and below that it says uac_start() when I try turning it on. I've taken out the battery in hopes of making it work but it hasn't. Is there anything I can do to make it work? I have no internet, I'm using another phone to write this.
Sent from my LG-P506 using Tapatalk 2
Does it say uac_start() or udc_start()? I've heard of udc_start() but never uac_start().
Also, can you get into recovery? Pull the battery, wait a few seconds, put it back in then hold the power button, the down arrow and the home button.
EDIT: How did you install clockworkmod? Did you use rom manager?
AfflictedMortal said:
I'll check it out, thanks man.
Edit: Did a nandroid backup and now my phone won't work. It says Fastboot mode started and below that it says uac_start() when I try turning it on. I've taken out the battery in hopes of making it work but it hasn't. Is there anything I can do to make it work? I have no internet, I'm using another phone to write this.
Sent from my LG-P506 using Tapatalk 2
Click to expand...
Click to collapse
You could try using this http://forum.xda-developers.com/showthread.php?t=1827723 to flash the recovery again
I tried that and it doesn't work, and yeah it's udc my bad. It was cutoff. As for the program there's nothing I can do with that cause my phone isn't working. I need a quickfix cause I cant keep using this phone since it's not mine. Is there a file I can delete from the SD card to make it work again?
You bricked it by attempting a backup through ROM Manager. ROM Manager is dangerous for our phones. Search for "Android Flash Recovery". It works through fastboot.
-- Sent from my TouchPad using Communities
The only way to fix this would be by using a computer, if you don't have that your only option would be to take it to a service centre.
Alright for the computer how would I go about fixing my phone? I might be able to hook up a computer at my brothers place. Right now I'm using my sister in laws iPhone. As for the service center there are none in my town unless you count Walmart but they barely know anything about phones, I only use them for familymobile. Plus a service center would cost money that I don't have.
AfflictedMortal said:
Alright for the computer how would I go about fixing my phone? I might be able to hook up a computer at my brothers place. Right now I'm using my sister in laws iPhone. As for the service center there are none in my town unless you count Walmart but they barely know anything about phones, I only use them for familymobile. Plus a service center would cost money that I don't have.
Click to expand...
Click to collapse
There are actually instructions here: http://forums.androidcentral.com/t-...-how-fix-fastboot-mode-started-udc_start.html as to what you should do. Whatever you do, once the kdz updater has started installing the firmware do not pull the battery. If you do, you will damage the phone permanently.
Once you're done doing this, if you're still interested in custom roms, flash the p506 version of clockworkmod. This problem is very common for p506 phones using a p500 recovery.
bluespoon4 said:
There are actually instructions here: http://forums.androidcentral.com/t-...-how-fix-fastboot-mode-started-udc_start.html as to what you should do. Whatever you do, once the kdz updater has started installing the firmware do not pull the battery. If you do, you will damage the phone permanently.
Once you're done doing this, if you're still interested in custom roms, flash the p506 version of clockworkmod. This problem is very common for p506 phones using a p500 recovery.
Click to expand...
Click to collapse
As i understood, the problem wasn't caused by the incompatibility of the recovery, because it only affects the screen driver (weird colors) not the functionality of the recovery; it was caused because he made a backup using rom manager, not the recovery....
And other thing,,,, flashing the p506 recovery will only let him flash p506 roms, and i don't see a lot of variety to choose from...
Okay so I'm still trying to find someone with a computer and internet so I can fix my phone. And is that program the only way to fix my phone? If so then is that all there is to it? Cause I can't get it to go to any menus, it just does that screen and I have to take my battery out.
Once you fix the recovery, you'll be able to flash ROMs, again. Or, you can restore a previous nandroid backup.
So is it possible to download that program on another phone and then put it on the computer and then the sd card? My sd card is the only way to put something on my phone cause when I hook it up to the computer it says a bunch of stuff but then says it's been interrupted or something.
To use fastboot or adb, you need to connect to a computer through USB. Since your recovery is not working properly, you can use Android Flash Recovery to fix it. Unfortunately, it works through fastboot, so you will need to connect your phone to a Windows computer. (If you know the commands to execute, and you have the appropriate files, you can do it through another computer, but you will still need a computer.)
If your recovery was working, you could do it without a computer.
Well the thing is since I have no internet I have to try finding a person with a working computer and internet so that I can do this. Basically is it possible to put the program on another phone but transfer it via usb to the computer then transfer it to my sd card? Cause when I hook my phone up to the computer it just does nothing.
You can download the program from your phone, save it to SD card, then put the SD card in the computer & run it with the phone connected by USB. That way, you can do it without internet access. But unless you can boot to recovery, I seriously doubt you can fix this without using a computer.
Edit: To clarify, the Android Flash Recovery program I linked to is a Windows program which is designed to run on a computer. You can download it on any device, but it will only run on a Windows computer.
The computer thing isn't the problem, it's the fact that I have no internet and only have someone else's phone.
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
sliceroo said:
I am relatively new at ROMs and I installed CyanogenMod 10 on my AT&T HTC One X (US) a couple of months ago. Recently, I tried upgrading to the M2 release of CM10.1 using the evita package which I understand is the US version of the ROM. I followed the same instructions I used to install 10.0 for 10.1. However, the installation froze and did nothing for a few minutes and gave me the message "no MD5 file found". I shut the phone down and restarted, but the phone would no longer start. I did a "system wipe" to get ride of the OS so I could re-install it, but now, my computer won't recognize my phone when I connect them and I can't move the CM10.1 zip file from my desktop to my phone. I have nothing already on the phone I can flash besides Team Win Recovery Project which is what I use for Recovery. I have no recovery files.
Did I just paperweight my phone, or is there a way to salvage this situation.
Click to expand...
Click to collapse
Are you able to get into recovery?
joelrwise said:
Are you able to get into recovery?
Click to expand...
Click to collapse
Yes. I can get into recovery and the screen that tells you the root status of the phone.
sliceroo said:
Yes. I can get into recovery and the screen that tells you the root status of the phone.
Click to expand...
Click to collapse
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
joelrwise said:
If you can get into recovery then you aren't bricked just yet! If you have an sd card reader on your computer or know somebody who does thats one way you could get a new rom on your phone to flash. Most recoveries have a way to let you connect your phone to your computer for file transfer while in recovery. I believe in TWRP the option is in the Mount are. I could be wrong though. You just need to figure out how to get a new Rom on your phone. If none of the above work, one trick that has always worked for me, would be to put your sd card into someone elses phone, and download a known working rom onto your sd card via theyre phone, and just put it back into your phone. Hope i helped. Let me know how it goes man. I've been here before haha
Click to expand...
Click to collapse
I went into TWRP Mount and it allowed me to mount the phone. I went ahead and did that, but Windows told me that I had to format the disk. I agreed and Windows formatted it. Afterwards, I successfully copied over the CM10.1 Evita M2 zip file and the lates Gapps zip file. I then went to TWRP's install section and flashed both zips. TWRP told me both happened succesfully. However, while flashing over the CM10.1 file, it told me that no MD5 file was found and that it was just going to skip that. Then, it formatted some mke5 partition and then went ahead and finished. I wiped the Dalvik cache and the system Cache and restarted the phone. It is currently stuck at the "HTC Quietly Beautiful" intro screen and won't boot past that. Is there something I missed?
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Pennycake said:
If that 10.1 already failed because of an MD5 problem, I wouldn't have tried to flash it again - the file probably has some problems in itself and either needs to be re-downloaded or just won't work.
Just flash the stock firmware or something - and use an MD5 checking program.
Click to expand...
Click to collapse
The thing is TWRP returned the status as successful despite missing the MD5 file. I'll try flashing over another package and if that doesn't work, I'll try flashing over CM10. If that still doesn't work, I'll just do stock firmware if I can find it somewhere, I guess.
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Pennycake said:
In the future, making a backup is really awesome. Not saying that like "I told ya so" - but I've used them so many times myself, it's really great to say, "oops, I overlooked something" and then be able to just go back to a perfect snapshot of how things were before.
Also, how long did you let the phone sit at the boot screen ? It can hang for quite a while on the first boot.
Click to expand...
Click to collapse
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
joelrwise said:
Yeah I would just reflash a ROM that you've used before and that you know works. Chances are if the cm10.1 didn't work the first time its probably not going to the second time. And he has a point. First boot always takes forever. I've flashed a couple ROMs and thought I was bootlooped but I let it sit for a good 5-10 minutes and the setup screen finally came up.
Click to expand...
Click to collapse
I had no idea that it could take that long. I guess I'll just turn my phone on and see if it wants to start. I'll leave it going for a good five to ten minutes this time. Shutting the phone down while its still in the intro screen doesn't damage the OS, does it? Thanks for the advice so far guys, I really appreciate it.
So following the instructions here I rooted my LG Tribute 5 when I got it with Kingroot. And everything was fine for months. Until System Updates started to pop up regularly but I could never get them to install(they would error out). After a quick search I learned the updates won't install cuz the device was rooted. And a quick unroot would get the install to work.
I just unrooted through the kingroot app and started the updated. Before, when I tried the update it would error out about a quarter of the way through. This time the bar made it all the way to the end and then error'd out. I didn't think much of it. So since the device was stuck I took my battery out and back in. The device went through the boot process, then a No Command error popped up. Never saw that before.
So I tinkered with it a bit and kept getting the error. So I got into the Recovery Menu to do a full wipe and factory reset. I did that, but the No Command still popped up.
I know I can put a custom rom file on my external sd card and install that through recovery, right? The thing is I would like to install Slimrom, but there are a ton of downloads on the sites download page. So I'm asking for a little help on directions on a slimrom that will work on the LG Tribute 5.
And if there isn't a custom rom that works with a tribute 5,can I get a recommendation of one a custom rom that does? I'm into lightweight and minimalistic. By the way, I didn't have a custom rom on my phone, just had it rooted.
Thank you so much in advance for any and all help
No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.
No-one has any advice for me?
A little more info, the phone was on Android 5.1.1 before it started erroring out.
Do you have a custom recovery as well? If it is only the stock recovery, which blocks most zips, your very option may be to use LG UP and the stock dz file and return the device to stock. The process to update can be done from that point.
I'm pretty sure I only have the stock recovery. I knew i should have installed TWRP...
So just search for LG UP and the stock firmware and they should be easily accessible?
Thanks for the reply xanscorp.
https://drive.google.com/folderview?id=0B0KV4b0_G1PQZW95ZmloejU5dFk
The LG UP program and .dz file are in there.
That's awesome! Thank you very much for linking the files for me.
I'm gonna do this in a couple hours when I get home and I'll let you know how it went.
Much appreciated xanscorp
One last stupid question... Just the LG Up and.dz files are the only two I need right?
I'm guessing so, but just wanna be sure.
Yes. It'll put you back to stock.
Unfortunately I haven't yet found how to get the ZV5 firmware fully rooted (i.e. a custom recovery) but it can be partially rooted with KingRoot. (http://www.kingroot.net/wap)
I just finally got around to giving this a shot. Sheesh....
Anyways I downloaded the files, put them on my external SD card, popped my SD card into my phone, then booted my phone to recovery. I went to install update from SD, and the phone didn't find any files. Hmmm....
I'm definitely doing something wrong. The .msi file looks like an executable. So I hopped onto Windows to install it. It installed, but when I run the program it can't find my phone when I plug it in.
I'm about to just give up, trash this thing, switch to a different provider and get another new phone. This time I won't mess with Kingroot. I'm pretty positive that's the app that screwed things up. I've had three different phones, rooted all three through different methods, and never had a problem.
Things files are to restore from a pc using LG Up for Windows... that's why it's a Microsoft Installer (.msi) file.
Yeah I figured that. But when I plug my phone into the computer my phone isn't recognized. I'm assuming because it boots straight to a No Command screen.
So since the computer doesn't recognize it neither does LG Up. Any trick to get around this?
Still haven't gotten this phone back to working. This is the first time I've really been stumped after a brick.
Please...anymore help?
Sent from my KFFOWI using Tapatalk
You find annything cause my same phone did the same thing
Sure haven't bud.
I've tried the help in the thread with no success