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
Related
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.
Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.
Glad to hear it.
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.
Hey everyone!
So, just upgraded from my Note Edge to a Stylo 3. I'm going through my usual ritual of boot, root, remove useless apps, Xprivacy, migrate data, move SIM card, a process that's getting progressively more annoying but I do want to thank everyone who makes the tools used to make this happen.
Anyway, I got to a point where I must've frozen an app I shouldn't have or something; ironically Jrummy's App Manager wouldn't work thereafter...nor would 'Messages' or a few others. I disabled Xprivacy, used Titanium Backup to defrost every app I'd frozen, disabled AFWall+...and still, things weren't happy. "Okay, let's just factory reset it and start over!", I said to myself. And, I did so. Now, one of the apps I froze was "EULA"...which is a requirement for the initial phone setup, thus preventing me from completing the initial setup wizard. "Okay then, let's just wipe and reload". I found the T-Mobile KDZ file from one of the dozen sites I've been to in my quest, and the LG Flash Tool. It wasn't until I tried using LGFT that I gained a true appreciation for Samsung's Odin, because the 2014 version doesn't seem to want to talk to my phone, giving me the "can't find server" error, and unlike the instructions I was following, the screen didn't indicate that the file was actually moving. The 2015 and 2016 versions of the tool both seem to want a DLL file, which is nowhere to be found.
Now, the saving grace is that I do still have access to TWRP, so if there's some variant of "chmod 777 -R" I can run on a directory somewhere to make sure EULA.apk and its friends are all defrosted, and that's possible from TWRP, then I'd super appreciate a tutorial on how to do that. Alternatively, if someone knows how to get LG Flash Tool to actually shuffle the bits out the USB port, I'm open to that as well.
Thanks for reading. I appreciate your consideration and assistance.
-V5
[SOLVED]
Yep! I managed to poke and prod a bit more, and solved my issue. For the other folks around these parts, the key is this:
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
I used Uppercut, as directed, in 'Upgrade' mode. I used the KDZ file downloaded from here:
https://lg-firmwares.com/lg-tp450tn-firmwares/
I opted for TP45010c_00_0821.kdz, because I didn't want to run the risk of upgrading the bootloader and preventing myself from rooting.
Once I used Uppercut, it wiped everything, and I was able to restart the process again.
I hope it helps someone!
-V5
First thing always when you get a custom recovery is to make a backup right away that way if things get messy you can recover, most phones and even this phone a guy has a flashable zip for TWRP, Uppercut works too but it's very easy to mess things up and you think it's not working because you did something wrong but as the guy above mentioned uppercut is what you will use, if that does not work for what ever reason then you have something else going on, driver's or something. If you can boot into the phone at all, then plug it in and tell it to reboot to bootloader that way you can flash it using uppercut, if you have access to twrp you can try that zip file
I've been getting help in the Newbie thread, but it's time I start a new topic, since it's getting harder and harder to find replies.
All I'm trying to do is upgrade an old LG from Android 5.0 to 6.0. That's it.
I've got the drivers installed. I've downloaded three different versions of Flash Tool. The only one I got to do anything was "Flash Tool 2014".
The first time I ran it (following the directions on the web page where I found it), I picked "CDMA", "DIAG", and "CSE Flash". I was able to pick "Other Country" and "English" and got the phone to start installing. However, it only got as far as 4% and gave me an error. Now, when I run it, I pick "Other Country" and can't even pick a language. They're all blank. If I continue, all the messages consist of Question Marks, however, it still gets as far as 4% before stopping.
The phone is bricked in Download Mode. I have tried two different USB cables, two different computers, one of which has Windows 7 & 8.1 installed. I've tried all different USB ports to make sure I'm on USB 2.0 and not 3.0. I've tried running in Administrator Mode.
I see many posts about the 4% Error. The solution involves downloading a "wx.dll" file and putting it in the C:\system32\LGMOBILEAX\PHONE folder, but that didn't work. I also so one that said when you get the error, take the battery out of the phone, unplug it, put it all back together, and then Continue. That didn't work either.
What else can I possibly do? Thanks.
Hey, I have been trying to find a rom for 6.0 and I can't find anything. The only way to get to 6.0 is through ota. If you have 5.0 then your lucky. Ota can only be used if you still have a sim card that's active in the phone. There isn't roms for stock android 6. I would try and help but I can't.
If anyone finds away to get stock 6.0 please let me know.
Talking about your issue of your phone being bricked, there is many unbrick methods. I personally used https://forum.xda-developers.com/t/...n-qualcomm-hs-usb-qdloader-9008-mode.2933853/ it helped and fixed my issue. I still had my device info wiped off my phone somehow but at least it works. Your at a issue with a flash tool, fresh reflash with that method I sent if you can use it and start over. I can guide you through it if needed.
You might be stuck at a stand still, tell me what your phone says in device manager. You probably flashed a bad firmware. In that case I used the method above.