I have an LG G pad x 8.0 TMO V521 build number NRD90U updated to Nougat fully updated as of jan 1st 2018 with no modification, no root, no open bootloader basically got it from store kept up to date via lg bridge.
The problem in a failed attempt to downgrade I believe I flashed my recovery with it having some password I didn't realize was there it made it to 10% has password error and stops most of my recovery images are not recognized when looking for them from recover device menu the 1 that is wont go past 10% device only reads at 1%. After realizing it was at a point I could not do anything from I disconnected the battery to preserve what battery i had left hoping I didn't totally mess everything up. Hard reset sends to update screen and boot sends to upgrade screen but device wont accept any update That I've tried.I have searched what to me seems like all the current threads with no luck finding what I thought was useful info since most refer to devices with open boot loaders or twrp or other things installed on the device that I don't have. Willing to except that I may have missed the thread I actually needed though by it being for similar process that sounded wrong so if I did even a push in the right direction would be a world of help.
My question is can this be recovered and how or am I SOL and should just go smash it with a big hammer for the frustration its been.
This problem fixed itself the next time I attempted to fix it with lg bridge and the update recovery kept saying i wasnt connected to iternetand making me click retry every 2 percent for about 45 minutes but i eventually got there and it wouldnt even do that last time so yay thanks all who may have attemped to understand my problem even if you never got to a solution for me if any admin wish to delete this thread your welcome to or if anyone knows a better solution for future occurences still not a fan of the method I had work.
Related
If anyone can advise me here I will be very grateful. I have spent several days looking online and reading countless threads here but am still not having any joy. Am a bit of a noob so go easy on me please!
I have a rooted LG D618 running Lollipop (recently upgraded itself from Kitkat). Long story short, I was fiddling around with the bootloader trying to install a custom recovery (ahem... ) and I ended up bricking the phone. I have been trying since then to install the original firmware using LG Flash Tool 2014 and it always stops on the 4% mark whilst extracting the kdz. I have tried this about a hundred times and the same thing happens every time. The phone is completely dead, I can not switch it on and I am unable to boot it into Factory Reset mode using the keys either. But it is still being recognized by the PC (win7 x64) and can enter (what I assume is) download mode. However in Windows the phone is recognized as removable disk containing 2 folders - 'image' and 'verinfo'. Not sure if that is normal or not? I am able to start the kdz flashing process and it goes through the first couple of steps verifying connectivity etc and then stops at the aforementioned 4% during the file extraction process, sticks for a while, and then gives me an error message.
I tried a solution which I found on the forum here, which I think was for the same issue, involving the wx.dll file in C/ProgramData/LGMOBILEAX/phone but this has no effect. I thought it might be related to me installing the KitKat kdx (v10c) onto the phone but I have since tried flashing the stock Lollipop variant (v20b) also and the exact same thing happens so am guessing it is not because of the KitKat wx.dll file causing issues. I am pretty clueless here, all of this is unchartered territory for me and I am out of my depth so if any kind soul here can advise me on any possible solution I am willing to try anything before admitting defeat, and taking the phone to LG to fix under warranty and hoping they don't realize that I broke it. :laugh:
I got my LG G3 yesterday night and I tried rooting it for hours, I was on Andrioid 5.0.1 and couldn't get it to work after 6 hours of trying so this morning I tried to downgrade back to stock firmware and now everytime I try I get the Factory Reset Status 2 screen and I am told to just remove the battery and it'll boot but nope it just goes back to the same screen. This is becoming a nightmare I have tried multiple PC's Operating Systems, drivers, firmware files, and multiple tutorials and I cannot fix this.
I think the issue is when the phone reboots instead of being a COM port it becomes a MTP device so LG Flash Tool can't find the device.
I really need help, I didn't plan on spending the whole day trying to fix this but it seems I am going to have to.
Adamgm10 said:
I got my LG G3 yesterday night and I tried rooting it for hours, I was on Andrioid 5.0.1 and couldn't get it to work after 6 hours of trying so this morning I tried to downgrade back to stock firmware and now everytime I try I get the Factory Reset Status 2 screen and I am told to just remove the battery and it'll boot but nope it just goes back to the same screen. This is becoming a nightmare I have tried multiple PC's Operating Systems, drivers, firmware files, and multiple tutorials and I cannot fix this.
I think the issue is when the phone reboots instead of being a COM port it becomes a MTP device so LG Flash Tool can't find the device.
I really need help, I didn't plan on spending the whole day trying to fix this but it seems I am going to have to.
Click to expand...
Click to collapse
Select "board dl".
In the general section, stickied, is a thread on how to do it.
Hello
I need some advice and help if someone can.
My LG V10 was rooted and on latest Eliminators room. It was working perfectly and few days ago while ending the phone call it just switched off.
Since then i have been trying to bring it back to life but without any success .
I can boot it to fastboot but no commands are accepted in fastboot mode, no download mode . It only goes to logo and the information that software can not be checked , further from there it goes nowhere . Since i am mac user , i installed VM of Win 7 and only thing it detects is Qualcom 9008......
Please some advice and help what is possible to do.
In fastboot mode i can not do anything.......
Sent from my iPhone using Tapatalk
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
I will play with it from tomorrow again. From yesterday i have gave it to one service center but they have not succeeded to do anything. I have succeeded in one moment to get to download mode which laster only about 2 seconds, not enough even to connect it to lg up, suspecting tht it is maybe something because of VM that doesn't' discover phone complerely. Tomorrow morning i shall pick it up and during next few days i shall try again, if i succeed to find a solution it would be good. I was also planing to do complete factory back up to stock last version. But...
Sent from my iPhone using Tapatalk
bildo said:
This is the exact thing that happened to me last night too. I was wondering if my phone pushed the latest update on accident or something to cause it.
Another thread in the Q & A Section has reports of this happening and maybe being a hardware issue.
I plan on trying to do a full restore back to stock tonight when I get home from work to see if I can bring it back to life. I also read somewhere that you need to have the latest binary for fastboot to work.
The few minutes I messed around with it last night, my fastboot was sending but not writing. I'll keep you posted it I have any success tonight after work.
Side note the thread I mentioned above the S/N for the phones having issues started with 510...
Also, I can get mine to boot into recovery but once I try to erase or install it freezes and boot loops again.
Click to expand...
Click to collapse
I have the same problem with my v10 do you found a solution ?
No. I bought a new phone and my v10 is now a paperweight. I have not really tried too fix either. Jumped on project fi and got a got a 5x on the cheap. Couldn't be happier.
I've had luck flashing my LG from within a virtual machine, running on top of Linux Mint. I tried both VMware Workstation and VirtualBox. Just make sure to install the guest additions within VMware, or the extension pack within VirtualBox. Also download the LG driver and install that inside the VM too. Each VM software may have settings relating to sharing a real USB port with the VM, make sure you look into that and enable the relevant options. Otherwise the VM may not detect the device.
On the other hand, my v10 isn't hardbricked, I'm just going to hold onto it as long as possible until it goes belly-up. Which it will probably do sooner rather than later, if the issues I've had are any indication. If you're only seeing Qualcomm 9008, fastboot not responding to any commands, and no download mode, this def sounds like a hardbrick. If you're still under warranty I would recommend getting it replaced by LG. If you have insurance then cash it in.
This is the 3rd v10 I've had, so far I've done 2 exchanges if I remember correctly. These phones are definitely susceptible to big issues. Like the now famous LG bootloop scenario.
Hope you get this figured out!
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.
I waited to write here, if the March 2020 patches solved the problem, but unfortunately it is not...
several nokia comunity users have the same problem and nokia is not responding about It.
having Nokia 8.1, I gave Nokia 7.1 to my girlfriend last year ... great smartphone, the Android 10 update work very well, but the February 2020 patch was a disaster!
Probably it didn't install well, and then the phone asked for a factory restart.
the problem is that the Factory reset did not come back to a pre-February patch state, but always brings it to the point of "restarting the phone to finish installing the February patch".
and immediately the restart is requested, which can be postponed, but not indefinitely, so after fifteen days the smartphone restarts by itself, and freezes again asking for a factory reset!
in an endless loop!
I think I have to do a system flash to bring the phone back to a previous stable state, right?
Can you help me on the procedure to follow?
I have never unlocked the bootloader and all the rest
thank you guys
My friend has the same issue.
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
thanks for the answer!
the guarantee is still active,
I think I will send it to nokia assistance, as soon as next week I will be able to see my girlfriend (for the emergency covid19 I haven't seen her for 60 days, but next week there is the unlock down).
meanwhile I took for her a Nokia 4.2 to be used as a replacement.
I hope Nokia's lab assistance will flash the system quickly and better than what I could do
PCIHD said:
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
Click to expand...
Click to collapse
Can you show me to a thread or video for option 2)?