Related
Hi, I apologize up front for the long winded post, but I want to relay as much info as possible in the hope that someone can point out my mistake(s).
This is the 2nd android phone I have managed to brick in the past couple years.. The first was an old dream and I flashed the wrong update file for a different phone by accident, but at least I knew what I did wrong that time.
Fast forward to yesterday. I picked up a brand new LG Optimus 2X (LG-P999 = G2X) From Wind Mobile in Canada running android 2.2.2. I bring it home and load up super one click and it tells me I am rooted, great! After that I loosely followed these instructions: hxxp://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide to get ClockworkMod Recovery installed via the market (free version).
First little hiccup was that when I opened the mod manager and tried to click on 'Flash ClockworkMod Recover' it gave me an error saying, "Error while downloading from Server. Please make sure that you have a stable internet connection, and that your SD card is inserted and has free space!". That's weird.. I have a brand new 2gb sd card and my 3g connection is working great.. I was able to sort that out by connecting to my home wifi connection and then this message disappeared. When flashing clockwork it asks for my model of phone and I choose the LG G2X from the list. Success! Although when I try to click on the option to boot into recovery -- nothing happens. Since I don't want to power off my phone, I download "Quick Boot" by Sirius Applications Ltd. and try to click the reboot option, but again, nothing happens. The recovery option also does nothing, whats going on here? I finally decide to power down my phone the "normal" way from the home screen.
I boot back up normally and realize that I didn't download cyanogenmod yet, so I go do that. I download update-cm-7.1.0.1-G2x-signed.zip for the T-Mobile G2x, even though mine is not T-Mobile, I read on the internet that I definitely have a G2x even though it is marketed as an LG Optimus 2X. I also download the Google apps gapps-gb-20110828-signed.zip.
Once the files are downloaded, I attempt to copy them up to the memory card, but windows explorer (Im using Windows XP) seems to lock up for a bit and I get a weird error: Cannot copy gapps-gb-20110828-signed.zip: The path is too deep. I have never seen this copy error before. I look it up on google and don't get much help, although it tells me what I already assume, that this error appears when your filename + path combo is too long. But its not too long! gapps-gb-20110828-signed.zip is on my desktop, and I'm copying to the root of F:\ !! The other weird thing is that this gapps-gb-20110828-signed.zip is only 6MB large. I have no problem copying the update-cm-7.1.0.1-G2x-signed.zip which is 93MB! I can copy any other file I throw at it.. BUT I CANT COPY THE GAPPS FILE !? I tried so many things at this point. I renamed gapps-gb-20110828-signed.zip to gapps.zip. I redownloaded it from the mirror. I tried copying it from the root of C:\ and another drive. I tried unzipping it and rezipping it. I always got the same error.
Finally I decided to copy the gapps file to the internal memory, and it copied without a problem. I wasn't sure if I could access that drive from recovery, but I decided to try it, even without gapps since I wasn't having much luck getting it onto the card. In hindsight, I should have maybe tried copying it to another sd card and also tried copying to the same sd card plugged into my computer via sd reader to see if the same problems existed. Even rebooting the phone and my computer would have been some good troubleshooting, but I wasn't aware of what would happen next.
I booted to recovery at this point (I can't remember if I booted via the rom manager link or if I rebooted and held the power and volume down button) and it came up as expected. I first made a backup of the existing system even though I didn't think I really needed it. Then I did the Wipe data/factory reset and Wipe cache partition. Finally, I loaded the cyanogenmod update and was surprised at how it loaded in mere seconds-- my old dream always took at least 1 or 2 minutes even for a smaller file. I then noticed an option to load a zip file from my the other storage (I can't remember the exact name of the option - but it was the place where the gapps file was). I loaded gapps without error and rebooted the phone.
It is at this point that I never booted back into anything again. If I remember correctly, it loaded the first LG symbol as usual, and then I saw another 'fancier' LG logo come up, with no animation or progress bar. I waited on this screen for more than 10 minutes, expecting that it would finally change to cyanogenmod, but nothing ever happened. No problem I thought, I can just boot back into recovery and try again without the gapps perhaps. No dice. I removed and replaced the battery, and then booted up with the power and volume down arrow held. I saw a LG symbol with progress bar, I saw a android character coming out of a box with a progress bar. I let go of the buttons. The phone rebooted. I tried again and again. Nothing.
At this time I was getting quite worried, but I had my phone plugged into the computer still and I noticed that everytime I got to the 'fancier' LG logo screen, the computer would recognize the phone via usb. I decided to see what the internet offered for solutions and I read lots and lots of info.
Everything boiled down to pulling out the battery, holding the volume up and down buttons and then plugging the usb to the computer. I installed all the necessary drivers and ran nvflash in an attempt to either install CWM or even the stock recovery. Getting the computer to recognize the phone properly was a chore in itself. Often it would come up saying 'Unrecognized usb device' or it would simply show up in the device manager with an "!". Sometimes when it showed up with the "!" I would right-click and uninstall it, then unplug and replug and install the driver again and that would work for a time or two.
The problem was that when I ran any commands I found for nvflash, it seemed to take forever to do anything. I mean I would be waiting, and waiting, and waiting, and all the command prompt would say is:
"Nvflash started"
One post I read somewhere said to just try a harmless command of "nvflash --sync" to see if the proper output appeared. I tried it a few times, but all I got was the same "Nvflash started", but then one time I noticed after a while it came up with a new line after that of "rcm version 0X20001". I tried nvflash at least 1000 times, no joke. I wasn't about to let this brand new phone beat me without a fight.
On one occassion I tried using the "One Click Recovery Flasher" that I found, and I attempted to load the stock recovery. The response from nvflash seemed to flow a little quicker this time and I got further in the process then ever before. Since it was now 4am I decided to let it do its thing and I would wake up and check it in the morning. I woke up at 10am and it was exactly where I left it. After 6 hours, I would have expected it to do SOMETHING! Here is what it said:
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x037c704243a08357
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
It apparently was unable to send the fastboot file for some reason. I could try 1000 more times but I am defeated at this point. I am planning to return the phone today and see what they say. If by chance I return it successfully, and I get the same model of phone, I will be super wary of trying to root it again. But I also don't want a phone that I can't "have fun with". Any comments or suggestions are most welcome. I would like to know what I did wrong so that I can learn for "next time". Other than the weird sd card error, I really think I did everything correct. At this point I am thinking there was either something wrong with the sd card or even with the phone itself. Regardless, I thank you for reading my story and I look forward to any helpful responses.
Cheers!
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash. Also, try running a vm or dual boot to use Linux. Nvflash worked fine on Linux didn't try on windows. no drivers needed. It recognizes it without doing anything special.
Sdcard problem is because the 2GB card is under /emmc or /sdcard/_Externalsd our something on stock.
tahahawa said:
I'm also on wind. The first thing I did was use nvflash to get a recovery. Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Did the same thing. I am on Linux too, and everything was extremely simple.
BTW, I think Wind's LG doesn't have screen bleeding or rebooting issues. I've never had them.
It sounds like you didn't install the drivers for the APX mode. When you get the explanation mark you need to right click and say update driver, then says I will find myself and browse to the apx directory where you extracted the One Click program for NVFlash. Then when it says the driver is unsigned click yes to continue. Once the apx driver is properly loaded you can flash CWM and reflash any rom you want. Don't worry your phone is not bricked. It is almost impossible to truly brick a G2X.
Did you resolve this issue. I just encountered it myself. Are you in Toronto by any chance. [sigh]. This sucks. I hope you can help shed some light.
Did you see my advice above? Try that. Also try re downloading everything, including all nvflash files.
Sent from my LG-P999 using XDA App
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
tahahawa said:
Never never use ROM manager to flash recovery on the g2x. It's a fake flash.
Click to expand...
Click to collapse
Is this true of ROM Manager in general, or is this something particular to the G2x?
dmj2012 said:
Is this true of ROM Manager in general, or is this something particular to the G2x?
Click to expand...
Click to collapse
Just the g2x/optimus 2x.
theshowmecanuck said:
Awesome. Nvflash unbricked the SOB. I used the youtube video (lookup this one: "How To Install CyanogenMod 7 Nightly on T-Mobile G2x after Nandroid Backup") and the G2x P999 ROM from cyanogen, and got my phone back. The video worked perfectly for me and I would recommend it (but of course don't blame me if anything goes wrong... why should I be different? . The T-mobile stuff bugs me though. I wonder why the cyanogen mod has their branding in it. Ah well.
Now that my phone works again, I can figure out how to get those annoying lines to stop moving all over the frickin' place. Then back up this ROM so I have something to recover to. And maybe try the cynaogen Optimus 2x ROM; although it does say in the file name that it is 990 and not 999. And maybe give the fine xda ROM a go (since I found the answer here).
Thanks to Wind Mobile for messing around with the names and making it confusing. The Optimus 2x by Wind is a P999 and the same as what T-Mobile has, and an Optimus 2x looks to be a 990 everywhere else in the world. I guess Wind never intended to make it easy to upgrade these phones from the start (and aren't offering an official Gingerbread, never mind Ice Cream Sandwich upgrade). Now it looks like they won't even be selling them any more. I guess they would cut into the profit of the new more expensive Galaxy when it comes out.
I know I won't use that ROM manager again. At least not for this phone. Wow!
Thanks again for the quick reply and sticking my nose back into the answer.
Regards,
BillR
Click to expand...
Click to collapse
Never flash anything meant for p990. Period. Unless it states it is for both. cyanogenmod had no Tmobile stuff except wifi calling.
Sent from my LG-P999 using XDA App
tahahawa said:
cyanogenmod had no Tmobile stuff except wifi calling.
Click to expand...
Click to collapse
When I first started the phone a message came up asking me if I wanted to run something, and that I could go to the T-Mobile site later if I didn't want to. Now I have been playing with it for the last hour and haven't seen any other TM related stuff, so maybe it was just that one.
The very first time it runs you get that message from the wifi calling app. You should never see it again unless you do a factory reset.
NOTE: I a m not sure az t where this post goes, I'm new, so please forgive me if this is not the correct destination for this post.
System: LG Lucid VS840 4G
Rooted: Yes
So recently, or like 3 weeks ago, rooted my phone successfully. So then after the root my phone wouldn't connect to the google play services. I unrooted my device successfully hoping that was the issue. It wasn't. So I finally decided to do some research, happily on these forums. Lol. I found out that my hosts file was indeed i ncorrectly written. I'm still confused why that happened but I knew how to fix it, didn't work. I rooted it again and allowed it su. Still not working with e, every time I try to add the pound key to the adress in the hosts file, it says fail. So I have another problem. I am running version 4.0.x and when I try to restart with ROM Manager from clockworkmod it boots up saying secure booting error Cause: boot certification verify. Enter the fast boot. Enter the fast boot. Long time no see...Yah, I'm really confused here, someone online said.it was in a brick phase but I can just restart.it back into normal boot. So that's my story of how.I wound up here. Help would be amazing. Thanks!
Typed out in the length of seven hours on the LG Lucid VS840 G4. This site is extremely buggy to type.on. My curser keeps.flying everywhere. xD
Hello. First of all, let me just say I'm glad I was pointed to this place by a friend, and, while I know asking for help with your first post is simply bad form, I think you guys are my last hope for fixing this phone, so I'll just go ahead an explain.
Alright.
So, yesterday I decided to root my ZenFone 6 (A600CG) for the first time after about 9 months of use. Up until then, I didn't really have any interest in rooting or even unlocking the bootloader, or any knowledge of how to do anything with it at all.
So, I did a quick google search, and found this:
w w w.asus-zenfone.com/2015/05/one-click-root-for-zenfone-series.html
The whole thing felt a bit dodgy, what with the all the bat files and stuff, but I decided to go ahead anyway. And it worked just fine, my phone was rooted. Hooray. Time to go and install stuff I couldn't before, right?
That's when this came in:
w w w.asus-zenfone.com/2015/10/how-to-add-zenmotion-to-your-zenfone.html
So, I did that. What I didn't realize, however, was that my bootloader was still locked. And so I followed the instructions detailed on that tutorial and all, seemed to work. Except when my phone rebooted, all that showed up on the display was a USB symbol. It wouldn't boot. I swear, I nearly shat my pants at that moment. So, I set out to fix that.
I couldn't really find ANY decent tutorial on how to undo the soft-brick for the ZenFone 6 specifically, so what I did first was trying to sideload each and every single rom that ASUS has for the ZenFone 6 on their support page. None of them worked, all of them showed the "failed to verify whole-file signature" error when I tried to have them sideloaded with ADB. So, I followed these:
zenfone-blog.blogspot.com.br/2015/06/guide-how-to-unbrick-asus-zenfone-4-5-6.html
w w w.windroidica.in/2015/07/how-to-revert-back-to-stock.html
First the former, didn't work because the rom wouldn't sideload, then the latter. Now, I'm aware the latter tutorial deals with the ZenFone 5 (for some reason, everything out there regarding these devices is either for the ZenFone 2 or 5, almost nothing can be found regarding the 6), but I figured the two are similar enough that a ZenFone 5 firmware would most likely work on the ZenFone 6, since they're basically the same thing, except for the camera and display size. Well, I was wrong. It kinda worked, though, it was stuck on a bootloop at that point.
So, with my phone stuck on bootloop, instead of coming here for help before, this dumbass here tried to flash the recovery for a custom one (TWRP, in this case). Except the bootloader was locked. So, I tried flashing dnx and ifwi with a bootloader toolkit I found here on XDA-Dev. I don't even know what went wrong, but the bootloader is still apparently locked, fastboot won't flash TWRP on top of the current default recovery, and now the phone is soft-bricked again, with that USB logo appearing whenever it turn the phone on.
Is there any chance at all I can solve this, or should I just throw this in the trash and buy a new one? I'd rather solve it, as I quite like this device, even if ASUS is terrible with their updates.
PS: Sorry about the links, but I feel as though they're necessary to better explain the situation.
EDIT: Seems like the bootloop is back now.
EDIT 2: Finally found a working firmware (2.20.40.11)! Sideloaded it, but I got a message about installing the latest 4.3 version first. I'm assuming it refers to the Android version, and now I'm really not sure whether it worked or not, as the phone still seems to be on a bootloop. Confusing as hell.
EDIT 3: It wasn't even a bootloop, just a longer than normal boot! My phone is running again! Lost all my data, contacts, everything. It's as if I had bought it today. I'm happy, though. Feel free to lock this thread, the issue has been resolved!
Issue resolved, thread closed.
hopefully this will help out some people and the developers to make,fix,restore a not so popular phone. I did a total firmware dump and have uploaded to my 4shared folder. If anyone is interested or can tell me how to upload it here for developing i will be more than happy to share with those in need. I also have a spare phone that i would be willing to test anything made from the firmware dump i created.
PLEASE link?
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
i tried contacting judthro for the same file; no luck
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
Unfortunately, I don't think this file is actually out there. I have REALLY been looking, even contacted the LG Development team. The LG Support Tool, etc. are not going to help you yet as they do not have the firmware on their servers yet. That's why the LG Support Tool will freeze when trying to do an Update Recovery on this phone. -- And I've tried them all: LG Mobile Support Tool, LG PC Suite, Verizon VS425PP Update Tool (from the mounted drive on the phone), LG Flash Tool 2014 to force different KDZ files. All provide nothing. All dead ends. The Optimus won't grab a COM unless it is the right signed firmware for the phone. You'll just sit there in Download Mode or in Debug mode forever with no result. We have to wait for the first update from LG from version VS425PP1 to whatever comes next so they have something to stick on their server. But...if you find something before then, please let me know! The update will eventually be released to the public. It'll probably just take a year or so.
Good thing is Wal-Mart sells these for under $12 (yes, that's right). I picked up seven of these quad-core bad boys at that deal. Just bugs the hell out of me I can't fix the one I over rooted.
this *might* be promising...
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
It works???!!! i have to root this cellphone because i need use with other company...
its not super useful yet
johhnyapplefake said:
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
Click to expand...
Click to collapse
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
I've had no luck, either.
johhnyapplefake said:
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
Click to expand...
Click to collapse
Meanwhile, as my LG cycles endlessly through my really cool "Jolly Roger" boot animation, I stumbled across a Kyocera Hydro Wave at Walmart for $20. I snapped it up to replace the LG Optimus Zone 3. I had big plans to root it, too., but I should've researched it first. The specs are great... but one check on Cyanogen's website probably would've saved me some trouble. Not one Kyocera device is listed there. XDA thread also throws red flags-no one can get root to stick. Well, I at least learned a lesson. Next time, I plan to purposefully buy a phone that can be rooted, has been rooted, has instructions online to do so, AND has at least one custom ROM available! No wonder this thing was $20! Keep us all posted if you stumble across a bootloop fix of some kind, and I'll do the same.
here is stock recovery for this device https://www.dropbox.com/home/Apps/Flashify/VS425PP/recovery
matt4787!
Either I am unable to open that link from an Android device OR the link given is to an unshared folder? It just asks me to log in and then says 'that folder does not exist in your DropBox...' PLEASE check out the SHARE link from within your DropBox and maybe share a new folder (and drop the stock ROM in there, along with what you might've used to flash it maybe?) We'd be very grateful!
Recovery
https://drive.google.com/file/d/0B1Nk8cx3_QgAeGNxZ1JrUmtFS0E/view?usp=drivesdk
Try now
hope my post helped some ppl. now to get twrp recovery ported here.
Thank you matt4787!!
Sent from my C6740 using XDA-Developers mobile app
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Just ordered one. Is there root for this phone? Unlocked bootloader or forgetaboutit?
I rooted this phone and then tried to de-bloat, but I must have deleted too much. Now when I boot all I get is "Security Error - Authentication Fail #9"
I can get to Download mode, but none of the recovery programs recognize the phone. I installed the drivers, but still nothing. Is there anything I can do?
matt4787 said:
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Click to expand...
Click to collapse
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
nikicollazo said:
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
Click to expand...
Click to collapse
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
matt4787 said:
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
Click to expand...
Click to collapse
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
angelgabg said:
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
Click to expand...
Click to collapse
this one is troubling. hmm you got the stock rom from lg? if so then try downloading the drivers from verizon.
Any updates on recoveries? I hate being scared of tweaking due to not having a backup .-. Anyone find something? Plz lemme know, thx! Btw kingo root 4.5 seems to have root for this phone but super sume seems to brick it. Just a heads up eace:
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