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 xda,
Just two days ago out of the blue while transitioning from home to the train with the Tegra on off (I remember turning it off during charging before I left) as I sat down on the train I found it turned on (unusual) I didn't think much of it but since then I later noticed that my Wifi was stuck on the "Turning Wifi on" message and that the app wouldnt allow me to click the cog in the top left to return to the settings page (moreover when I click the open programs buttons it just disappears..strange) the only reason my attention was brought to this was because my Bluetooth gave me an error saying it couldnt share bluetooth anymore.
At the time I thought a simple restart would fix it but nope it didn't. My tegra is rooted but I have had no problems until now!
Since then I have done
Factory data reset
Cleared memory cache
Factory restored using the advent factory 4.3 image http www adventcomputers co uk / product-download-select/296 (sorry first posts and I don't seem to be allowed to post links).
Right now I find myself stuck at the "Welcome" screen as after I select a language and press next the wifi tries to turn on and I cannot skip this.
Any suggestions on what I should/could try please? Is it a hardware problem like it happened with the Samsung Galaxy?
Thank you
Does anyone have a suggestion?
I am trying to compress the latest stock rom (Roms Stock 4.4.2 from rootjunkysdl) into a system.img in ext4 format so as to then place it in the automatic Vega-tegra recovery tool found at: www adventcomputers co uk / product-download-select/296
At the moment I am stuck at the fompressing a folder directory into an ext4 file .img format.
Anyone have any ideas?
The reason I am trying the above is because upon resetting it with the above mentioned recovery tool, the WiFi is still on "turning on" however with it resetting it to version 4.3 means I cannot find a way to bypass the welcome screens as it won't allow me past until I manage to connect it to the internet.
Please, any help at this point would be very much appreciated
Fiztban said:
Does anyone have a suggestion?
I am trying to compress the latest stock rom (Roms Stock 4.4.2 from rootjunkysdl) into a system.img in ext4 format so as to then place it in the automatic Vega-tegra recovery tool found at: www adventcomputers co uk / product-download-select/296
At the moment I am stuck at the fompressing a folder directory into an ext4 file .img format.
Anyone have any ideas?
The reason I am trying the above is because upon resetting it with the above mentioned recovery tool, the WiFi is still on "turning on" however with it resetting it to version 4.3 means I cannot find a way to bypass the welcome screens as it won't allow me past until I manage to connect it to the internet.
Please, any help at this point would be very much appreciated
Click to expand...
Click to collapse
Try some USB 3g/4g Dongle and insert it into micro USB , then you can connect to internet via 3g/4g and see if you can get past welcome screen.
...
I had similar problem "wifi just showing turning on forever" with a phone. But that had happened because I had accidently deleted the "insmod" binary from "/system/bin/" folder ( actually replaced it with the one that came with "precompiled busybox-1.21.1-armv7" from busybox.net.) So at that time my phone was not able to load the "Wifi module some .ko extension file") See if you are also having this problem.
asratxda said:
Try some USB 3g/4g Dongle and insert it into micro USB , then you can connect to internet via 3g/4g and see if you can get past welcome screen.
...
I had similar problem "wifi just showing turning on forever" with a phone. But that had happened because I had accidently deleted the "insmod" binary from "/system/bin/" folder ( actually replaced it with the one that came with "precompiled busybox-1.21.1-armv7" from busybox.net.) So at that time my phone was not able to load the "Wifi module some .ko extension file") See if you are also having this problem.
Click to expand...
Click to collapse
Thank you for your reply, my tegra is not set up for 3/4G as far as I know, wouldnt connecting a dongle require some app installation?
wifi stuck at "turning on" for months
Hi
My tablet turned off and on then would not connect to wifi it gets stuck at turning on amd i cannot press any buttons to turn it on.
I have reset. Put in airplane mode and finally factory reset so now it asks to connect at Welcome page but still shows turning on.
I have not rooted or am not technically savvy i just know the basics but i do not know what to do and cannot use my tablet at all!!
Please help!!
aimeymarie said:
Hi
My tablet turned off and on then would not connect to wifi it gets stuck at turning on amd i cannot press any buttons to turn it on.
I have reset. Put in airplane mode and finally factory reset so now it asks to connect at Welcome page but still shows turning on.
I have not rooted or am not technically savvy i just know the basics but i do not know what to do and cannot use my tablet at all!!
Please help!!
Click to expand...
Click to collapse
You are having one of the symptoms of a bad OTA update/Flash/etc.
I described my problem in detail here: http://forum.xda-developers.com/nvidia-tegra-note-7/help/help-tablet-stuck-fastboot-t2967999
Today I plan to work on it, I'll let you know if I get it going again with Wireless and what I had to do.
Hi, I have a S4 i9505 with a problem, screen broken and no display at all + usb debugging is disabled.
Phone: Not rooted, original software, usb debugging disabled, no display at all
What I want to achieve: restore all my photos / videos on the phone memory, no sd card
What I have attempted:
installed ADB & fastboot based on instructions from http://forum.xda-developers.com/showthread.php?t=2786395
What I need help with:
- When i try to get into recovery mode, i wasn't sure if i am indeed in there since i can't see anything, but in total there's a vibration when i turn on the phone, and another vibration when i release the power up+power+home after pressing them down for about 5 seconds.
- When in command prompt I type adb devices and there was none, and when i type adb shell it says error: device not found
I have ensured all drivers for my phone are installed (even with PdaNetA4180 & UniversalAdbDriverSetup6 from cynanogen) but the error remains. refer to attached image.
I have done extensive search on the forum but still couldn't find any ways to get usb debugging enabled on my crippled phone.
Any step by step guide would really be helpful! Thanks
Ps. Main problem = device not found in adb , usb debugging disabled, screen no display/cracked
What do you want? To recover files? To my knowledge that is not possible.
You would first need to flash a custom recovery for adb to work in recovery.
Then you would need to allow the connection on your device (which you can't do).
Yes I need to recover photos only. Nothing else.
Please kindly guide the steps on how to flash a custom recovery (w/o control of the phone's display or touch)
Thanks.
Your device is shown connected in windows
Why not use the mtp protocol and copy whatever you want
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
If the photos are deleted by the factory reset then i am sorry to day but you cannot recover them even if you get the screen fixed
bomby481 said:
Hi, in the beginning, my phone is locked with a pattern pin.
I read the tutorials and managed to get away with the pattern pin by resetting my phone to factory settings via recovery mode i guess by watching youtube guide.
I didn't knew the photos and all will get deleted off from it, so there's nothing to transfer over when i got MTP working and able to access files inside the phone.
What do you recommend? Would fixing the screen and then using dr fone recovery works? or is there any other way to solve this without getting the phone display fixed? Thanks.
Click to expand...
Click to collapse
Your photos are gone and there is no way to get them back.
When I set up my 6P a few hours ago, it asked me for my SIM pin (white symbol) but never actually connected to a network. Taking a look at my APN settings I get this weird message: "Access point settings are not available for this user." So I'm also not able to add a VPN manually.
I searched a lot and found some methods to try. Here's what I already did:
- Force stopped Phone and Messaging Storage
- Cleared Phone and Messaging Storage data
- Deleted /data/data/com.android.providers.telephony/databases
- Factory Reset
- Rolled back to 7.0.0 from 7.1.1 beta
Is there anything else I could try?
Thanks in advance!
i have the same problem
goog luck
I'm not intimately familiar, but I did see a couple of potential solutions:
Step 1 : WiFi turned on, and be in the range of a known WiFi network.
Step 2 : Reboot the phone (may need to reboot several times, if it doesn't work the first time)
Step 3 : When the phone reboots, it should connect to WiFi network.
Step 4 : Go to APN settings and see that you can, now edit APN settings.
Reason : When phone is turned on, if it's not connected to WiFi, it will try and connect to mobile network thus disabling you from editing APN settings. However if you try the above steps, your phone connects to WiFi instead of Mobile-data.
Click to expand...
Click to collapse
My original solution would be to flash the factory image. I've had some wonky behaviour in the past with the root issue being older radio operating on newer firmware. You can grab the latest image 8.1.0 (OPM7.181205.001, Dec 2018) directly from Google. Flashing instructions are at the top of the page, but boil down to:
Ensure you have necessary tools and drivers installed; reboot into bootloader (power on while holding VolDown key)
Run
Code:
fastboot flashing unlock
Unzip factory images, and execute the flash-all script corresponding to your system (.sh from Linux, .bat from Windows).
This will update the bootloader, radio, and firmware.
[Q] LG G6 H870 | Turning on WiFi does not work, but "/data/misc/wifi/config" is ok
After Reboot from TWRP, it was no longer possible to activate WiFi.
The "/data/misc/wifi/config" contains the correct MAC address, Bluetooth works.
Neither a factory reset nor the installation of another ROM solved the problem.
What can disable WiFi permanently regardless of the ROM and correct configuration file?
How do I reactivate WiFi?
Details:
- was on "Fulmics ROM 4.2" with TWRP from Eliminater74
- flashed Magisk-v18.0.zip, wiped Dalvic and cache
- after Reboot the WiFi switch can no longer be activated
- Factory reset does not help
- flashed "Oreo 8 OPEN EU 20C ROM" with factory reset, which hasn't helped either
- checked "/data/misc/wifi/config" - MAC present
- pulled misc.img, checked at HEX 600 - MAC present
- checked hidden call menu - MAC present
Bud Cord said:
After Reboot from TWRP, it was no longer possible to activate WiFi.
The "/data/misc/wifi/config" contains the correct MAC address, Bluetooth works.
Neither a factory reset nor the installation of another ROM solved the problem.
What can disable WiFi permanently regardless of the ROM and correct configuration file?
How do I reactivate WiFi?
Details:
- was on "Fulmics ROM 4.2" with TWRP from Eliminater74
- flashed Magisk-v18.0.zip, wiped Dalvic and cache
- after Reboot the WiFi switch can no longer be activated
- Factory reset does not help
- flashed "Oreo 8 OPEN EU 20C ROM" with factory reset, which hasn't helped either
- checked "/data/misc/wifi/config" - MAC present
- pulled misc.img, checked at HEX 600 - MAC present
- checked hidden call menu - MAC present
Click to expand...
Click to collapse
I turn on airiplane mode, then 2 seconds later turn airiplane mode off and wifi works.
Matt
Unfortunately this trick (activate WiFi in flight mode) does not work.
But thanks for the idea! :good:
During my long research I had read somewhere that WiFi worked again on a LG with the same symptoms after disconnecting the battery cable.
I don't want to try this during the warranty period.
I know why I don't like fixed batteries!
I probably have no choice but to install a KDZ firmware, lock the bootloader and send the phone in for repair.
Or does anyone else have an idea how I can bring the WiFi back to life?
I have now flashed H87020c_00_OPEN_EU_OP_0817.kdz and locked the bootloaders again.
Even after a final reset to factory defaults, WiFi stays impossible to activate.
Any further suggestions before I send the phone in for repair?
The smartphone has now been repaired under warranty.
Parts of the hardware were defective and had to be replaced.