A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
Hello all,
usually i deal with my problems by searching the forum, though this time i am really worried as i cant find anything to my help.
You see something went bad with the screen and because the phone is rooted, i cant get it fixed (it is still in warranty), nor can i use it (the touch sucks).
So i am trying to get it unrooted.
So i have downloaded LG mobile support tool and the drivers, i enter the phone to download mode and nothing happens. i get all the time errors. Also, in the lg mobile support tool, i see a software update. Should i do it? I cant though because the start upgrade button is greyed out, and the "LGD802" sign on the left pane is flushing like its trying to verify my g2. Also, should i wait for like 10 minutes or so when i enter download mode for the bar seen at the phone to be completed before the whole process? Lastly, the most of times the lg mobile support tool crashes on the pc.
Please help me folks... :/
the problem is when i hook my phone up the pc and it recognizes it, it starts the download drivers part but it freezes and force closes...
Hello,
I want upgrade my LG G2 with a new rom 5.xX
This phone have only the operator update. No custom, no trwp, nothing...
I installed drivers and when i want access to download mode. I can't. I use the good proccess with vol up then plug usb cable always with vol up presses.
follow this procces after a little moment my phone show me battery logo charging.
So i can't access to download mode.
I would use this process
t was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
but it's impossible for me to install B2appsetup on my pc the installation begin then stop after 5s then nothing.
I have Win 10.
Do you have a solution for me , please??
poupinej said:
Hello,
I want upgrade my LG G2 with a new rom 5.xX
This phone have only the operator update. No custom, no trwp, nothing...
I installed drivers and when i want access to download mode. I can't. I use the good proccess with vol up then plug usb cable always with vol up presses.
follow this procces after a little moment my phone show me battery logo charging.
So i can't access to download mode.
I would use this process
t was NOT bricked. I finally tried playing around with the LG Mobile Support Tool (B2CAppSetup.exe). Of course it detected that my phone already had the latest firmware from T-Mobile, but then I clicked Options>Upgrade Recovery.
It downloaded for a while then I noticed it had put my phone into download mode (it said "Rooted" in red letters at the bottom). Then it flashed the same firmware over and I immediately tested, it entered download mode right away. But I didn't end up needing that as Stumproot was able to brute force it now after the recovery flash.
Anyway, I couldn't find an answer anywhere else. Most results also have a bricked phone, but that wasn't my issue. This solved my problem and maybe it could work for others.
but it's impossible for me to install B2appsetup on my pc the installation begin then stop after 5s then nothing.
I have Win 10.
Do you have a solution for me , please??
Click to expand...
Click to collapse
so you have tmobile. right?
and only 5.0.2 lillipop is availabe stock.. if you go asop or cm the theres 5.1.1- 6.0
then do what the guide says to do here.
http://forum.xda-developers.com/showthread.php?t=2432476
I can't do that because I don't have the download mode
poupinej said:
I can't do that because I don't have the download mode
Click to expand...
Click to collapse
try the skr tools , with the nuke download . read as i havent used it but i read that might bring download. the other way is to short circuit the motherboard.. but ill go read skr tools if i was you.
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
growiel said:
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
Click to expand...
Click to collapse
It does sound like a hard brick... you said fastboot is hosed, do you have access to adb in any way?
Sent from my moto g(6) play using Tapatalk
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
growiel said:
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
Click to expand...
Click to collapse
On my lg tribute HD (ls676) fastboot was removed by lg themselves on Android 6.0.1 quietly with a security update and download mode never worked right for me. Without access to fastboot, adb or even diag mode it really sounds like you have a hard brick. if i can find a solution of some kind, I'll definitely let you know.
Sent from my moto g(6) play using Tapatalk
What would "diag mode" be and how can I check if I can access it ?
Small update for people who stumble upon this thread, I managed to save my phone by using the Qualcomm Test Point, see here: https://forum.xda-developers.com/showpost.php?p=81697447&postcount=128
Hi.
To start off, I'd like to say im no expert with phones, I had phones mostly to call, watch videos and listen to music, and this is my first attempt at doing all the stuff I will be describing now.
From the beginning:
I bought a seller refurbished LG G2, which worked fine when I received it, I had to do some updates which my phone found automatically, and it ended at OS version 4.4.2.
I wanted to finally have a decent but cheap phone, however it couldn't play some games I wanted to play and thought "Maybe if I update OS to something new, it will work, and it looks better"
Here my journey to update the phone to Android 11 started.
I was looking at many different videos and guide and everything, how to root, first time I rooted was by accident, only later a better video instructed me how to do it properly, then I installed the trww or whatever its called. then it didnt work properly after using that recovery to install android 11, so I had to flash it to some old version I found for my device (My version is LG D802 btw). For some reason it now had only 11gb of space, instead of 32gb. Anyway, I tried installing root and twrw thing again. After getting root and the recovery program I clicked reboot in its options and now my phone is having an issue.
First off, I left it to charge over 9 hours. If its NOT connected via usb it does nothing, power button, volume buttons do nothing.
I tried connecting it to my phone to flash it, but nope, after few seconds it says my phone disconnected from the usb and try again, even tho it is connected and I can see in device manager that it's seen by my PC. Now, I tried to enter the download mode manually, and it worked.
It says that it's rooted and B0 above it (this number was going down over different roots, twrw installs and flashes and such, no idea what it is.
I tried to flash it again since Im in download mod, however now the main issue appeared. It goes well for 40% of the flash using the LG flash tool 2014, I can see the progress in the download mode on the phone's screen, however once it reaches that certain point it just resets and the program treats it as disconnected.
Now when I have the phone connected via usb it just flashes red between 1 and 3 times, LG logo shows up for several seconds, then it turns off, and repeats the whole process.
During the flashing, software instructed me to remove the batter and try again, so I looked up how to remove it, did it, put everything back together, and its still the same.
Please tell me what to do, I've already spent over 10 hours trying to fix it and I just bought this phone...
hi... if your phone flashes LG logo - i'd recommend a full TOT flash of the original Lollipop image as a starting point...
just make sure you download a proper TOT file for your d802 device (32gb model)...
you'll end up with a working stock Lollipop rom which you can later root and flash a custom rom (i.e. Lineage 18)
Stock TOT file is usually about 2.6-2.7GB in size (at least for my 16gb model)
this youtube video shows how to do it and what is required for the process...
i think there is also an older thread here on XDA on how to TOT flash a G2 device (try to search it)