Related
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says
Hi there
I've in the past, rooted some of my android phones. Just got the HTC one M8 and it updated to 5.0.
I would like to get root access (not planning on flashing a new rom). I'd like to get OTA still.
I followed step by step instructions on how to root, but when I go to SU, I get an error message:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root - consult the relevant forums for your device!"
Also, my touchscreen / keyboard seems messed up. It starts typing random stuff on it's own I think I might have damaged my phone by keep trying to do it.
I'm a noob and try to usually follow step by step instructions.
Please help - and in basic terms, please
Thanks!
Update
I reset my phone, and now it is rooted and works. Problem is that the screen is still messed up It doesn't type what I want and closes typing screen, opens other windows etc What should I do?
Does the glitchy behavior only happens when you're charging the phone?
My phone has now updated all its apps and the screen is working fine again, but I get the same message again as previously. SuperSU message: There is no SU binary installed, ......".
Seems it worked only until it updated.
Would love to get it rooted. Help would be appreciated please.
TheMabaet said:
Does the glitchy behavior only happens when you're charging the phone?
Click to expand...
Click to collapse
You're right. It was happening while charging. My phone was still linked to the laptop. So that could be it.
This is my first post, so please forgive any mistakes I make with a post.
My wife's Galaxy Note 8.0 tablet was being stupid, it would refuse to properly use the internet from our Asus router, would connect but apps would insist there was no connection. Was getting tired of that crap so I decided to install a custom ROM, since samsung can be kind of jackasses abandoning most their devices after one major update, was only running Kitkat for crying out loud. I had done so before, but issues arouse. For one, I had great difficulty finding a proper TWRP for some stupid reason, NO ONE seamed to know where to get a well working version. I found one, but it messed everything up, it seems to work just fine but any ROM I install has massive issues with the Google apps, they crash eternally and continuously so I can do literally nothing, can't even get past first setup. I came across talk that it was old TWRP to blame, that it has issues with newer OS's like the lollipop I was trying to install, and FINALLY managed to find a newer version of TWRP, but freaking Odin keeps hanging on it's install, gets to "Nand write start" then stops doing anything. I have tried different cables as well as different computers, does jack crap so far to help. My backup I made in TWRP doesn't even work, when I restore the result is nothing but a boot loop. I am trying to find a stock os to restore it to (mostly) original condition, but it is absurdly difficult for some stupid reason to find, found one all in one exe that didn't work for a damn. I was hoping there might even be a way to install the newer TWRP from with TWRP itself. Can anyone help me with any part of this?
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
kge420 said:
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
Click to expand...
Click to collapse
Sorry, but you are going to have to be a little more specific. I installed Switch, but connecting an off device obviously does nothing, should I install and let it boot into a broken ROM again, where gapps crashes, and connect it then?
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Thanks, pretty much.
kge420 said:
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Click to expand...
Click to collapse
None of what you said really made sense, I could not get to ANYTHING AT ALL that was not Odin or TWRP. But that link you had gave me the name for the stock os, I searched that and flashed it and now everything is great. So thanks, sort of. You even mentioned that method not working for you I think in that thread, but it did for me, so yeah.
All good then.
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
mdphoenix said:
Long story short - Bought an LG D851 off Swappe. It came with CM13. I've been sticking nightlies on it. Currently on 2/14. I tried to put 2/18 and found that TWRP wasn't working - it hangs on TWRP Splace. Then I noticed SuperSU wasn't on the phone. So I installed it. Can't update the binaries. Looks like I don't have root.
Used LG Flash tool and flashed D85120E_00.kdz. Part way through, I get an error that the software cannot communicate with the server and it asks if I want to abort. I let it continue.
The phone reboots, I get the "Android is updating 1/196", etc. After which, it reboots, I get the boot jingle, and then it holds on the T-Mobile screen. I've tried flashing the KDZ a few times with the same result.
So now, I humbly, yet again, ask for help.
The endgoal here, is to have a working ROM with BT and WiFi working. I really don't care what it is at this point. Marshmallow is nice. Lollipop is okay. Whatever. I just need a working phone.
Thanks in advance, as always.
Click to expand...
Click to collapse
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
debianmain1 said:
Ouch!!! Read my CM13 post...you don't need SuperSU anymore (CM13 has root built in)--I had the same problem a while back--fixed it by flashing the old factory version on the phone & then used Purple Drake to root it & then installed CM13...Was a HARD lesson for me.
Upshot---No SuperSU needed--No BusyBox needed on CM13. If you are used to the old way of doing things--you'll get B0rked big time.
Luck to you!!!!
Click to expand...
Click to collapse
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
mdphoenix said:
I guess trying to push the SuperSU binaries is what effed up TWRP?
I'll check out your CM13 post. But the issue I have is that I can't flash a factory version with LG Flash Utility. I mean, it does, but now it just sits on the Tmobile splash.
Hopefully your post will show me something I missing.
@debianmain1 is this the post you're talking about? http://forum.xda-developers.com/showpost.php?p=65432245&postcount=158
I tried that DD command to no avail last night. I tried everything I could find before reaching out to everyone for help.
Click to expand...
Click to collapse
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
debianmain1 said:
Yes--the SuperSU binaries B0rked my install real good ( as I understand it--2 different types of SU installed B0rks everything )..... And with CM13, you have to allow ADB & apps to have root. I've been modding phones for years now & CM13 threw me under the bus until I learned what to do... I use to ALWAYS root, install BusyBox & SuperSU---not with CM13
Ya--that won't help you I'd look up fastboot commands & try to flash it that way--sounds like you are stuck in a startup bootloop. I did see some info online about starting the G3 in fastboot--I had a very hard time getting my G3 fixed. Do you have a Linux computer to use? It's easier to work with some of the diag stuff with Linux.
Click to expand...
Click to collapse
I can always fire up an Ubuntu flash drive if necessary. I'll get working on Fastboot.
Thanks again!
@debianmain1 Hmmm, Fastboot doesn't seem to be functional. I've got download mode. Can I push something to it that way?
I managed to get somewhere yesterday. I tried flashing D85120e_00.kdz and it failed again. I got the "cannot communicate with server" error, then it rebooted and tried running initial setup and failed.
So I tried flashing D85110C_00.kdz. Much to my surprise, it worked! So I ran through initial setup and got the phone working to make sure all was well. I rebooted and got the Red 2. So now here I am. Guides show that I should be able to put it in download mode and reload factory firmware again. But all I get is the "Download Mode" graphic. It never switches over to the updating mode with the circular arrows. I fear the worst at this point, but I really don't know enough about the LGs to diagnose my own doom just yet.
Someone on Reddit pointed me in the direction of Board Diag. Unfortunately it doesn't appear to work on D851. Running out of options. Looks like it'll end up being an expensive learning experience.
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
golfnut22 said:
My sw3 has been stuck on the 4 dots/symbols for some time now. I have tried XC (even though it ran with success, it did not fix the watch), by way of fastboot, adb and twrp I have run, installed, pushed various files such as recovery, roms, .simg, etc to no avail. I had a thread going on the 4 dots that describes each of these functions with the 4 dot thread title if you care to see what has been done and the results.
The last entry of that thread suggested there may be an issue with my partitions. So, I wondering if anyone knows either how to check/compare and better yet, repair if needed?
Edit: Edit: I found this post http://forum.xda-developers.com/smar...rsion-t2988087 and I was able to get the watch working again. I still cannot use XC to repair or update, but at least it is working with LP.
Click to expand...
Click to collapse
Same issue here
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
baronimus said:
Hi,
I have the exact same issue with my sw3, stuck on the four symbols. Like you I managed to flash TWRP and mount the SWR50-LWX48P-repacked ROM. This doesn't do the trick unfortunately because firstly I cannot update the ROM and worst of all the watch will not connect to my smartphone. Like you I suspect there to be an issue with the partitions but I haven't got a clue really. Hope for some help on this.
Click to expand...
Click to collapse
Yes, I still have not been able to update to MM. Mine does connect to my smartphone with no issues. Although, the last time I did have an issue where it kept cycling and trying to connect to the internet via the phone. So, I went thru the steps again to basically get it back to the ROM you noted above and it is working. One thing I have noticed once I get it going with the steps I used, I cannot boot to twrp via fastboot. I have to go to XC and let it try and repair, which it says it does, but doesn't. I get the 4 dots again, and from there when I fastboot, I can fastboot twrp.img and adb push stuff to install. However, I have noticed that I need to use the flash commands and flash the .simg file noted in my thread in order for the above ROM to actually work. I also noticed when that ROM is installing, it does mention working on partitions...so, it must be doing something to some of them.
I would love to be able to get MM working on this, but I think I have run out of ROMs to try. I'm probably not sequencing something right, but have not clue as to what is wrong. I am an newbie at this.
If you get MM to finally update on your watch, it would be much appreciated if you would share your detailed process in achieving that success.