Related
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
Hi Everyone,
I have a phone, the Huawei Ascend P7 -L10.
Some weeks earlier I tried to install Spotify in my phone, but I didn't manage to install it. After several attempts I end up crocking my phone.
It happened when I found some app that had apparent solution to solve Spotify installation problem. I don't remember the name of the app. Anyway, I found it effective so I tried to follow the instructions given. I made it, then the changes were effective. What the app does is to change the phone model and respective carrier.
All the dilemmas started when I decided to restart the phone.
Here goes what I've done so far after the incident.
1. I tried by myself to restore/upgrade the system. I've experience doing this.
2. I took the phone to the 1st Repair Agency - they did not fix it
3. I took to the 2nd Repair Agency - the same thing, they fail to fix it
Note: When you try to restore the phone it gives the following information “update failed!"
and when you normally try to switch the phone on it stop on black screen and nothing else, I've also tried wipe cache, wipe data everything but nothing. Please help!!
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
es0tericcha0s said:
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
Click to expand...
Click to collapse
Thanks for your replay. My device is rooted one, but the problem is, I can't login not even connect it via cable (using e.g. HiSuite). So, how can I pick up the file from phone?
Hi guys!
A friend of mine asked me to retrieve a wifi password that was stored on her phone (Glaxy S6 Edge plus). I didn't want to root it, so I installed TWRP and extracted the wpa_supplicant.conf file, the thing is the key shown is very long, so apparently it is encrypted, I can't root/edit build.prop/anything like that on her phone becuse when I installed TWRP a bootloop happened and she got really scared (although I fixed it in 40 minutes, took me so long due to the bad wifi on that place and the fear of not being to fix it without doing wipes). So now I have the encrypted wpa_supplicant.conf file with an "encrypted" psk key and would like to know if there's any way to decrypt it and get the true key. I also have a Galaxy S5 and an S7 edge both rooted TW with custom kernel if that can help by copying the file to them (I doubt it would work). I also can use linux in case anyone has a solution with it.
fanfzero said:
Hi guys!
A friend of mine asked me to retrieve a wifi password that was stored on her phone (Glaxy S6 Edge plus). I didn't want to root it, so I installed TWRP and extracted the wpa_supplicant.conf file, the thing is the key shown is very long, so apparently it is encrypted, I can't root/edit build.prop/anything like that on her phone becuse when I installed TWRP a bootloop happened and she got really scared (although I fixed it in 40 minutes, took me so long due to the bad wifi on that place and the fear of not being to fix it without doing wipes). So now I have the encrypted wpa_supplicant.conf file with an "encrypted" psk key and would like to know if there's any way to decrypt it and get the true key. I also have a Galaxy S5 and an S7 edge both rooted TW with custom kernel if that can help by copying the file to them (I doubt it would work). I also can use linux in case anyone has a solution with it.
Click to expand...
Click to collapse
Without root it won't happen and even then the device is most likely encrypted so you would have to unencrypted it which will wipe the device. You are out of luck.
I just wanted to help you. I had the same problem. I have samsung s5 . So I used "root browser "and In data->misc->wifi : I found this file "raw_conf.conf" And it's actually contains all my WiFi passwords. I used android 6.00 by the way and my device is rooted .
Can someone (who never touched it, obviously) dump his misc partition and upload it?
From H850 international variant.
I wiped mine while I was in a twrp bootloop and need to flash one back.
Open a terminal, and after su run:
dd if=/dev/block/bootdevice/by-name/misc of=/sdcard/misc-dump.img
Thanks
C'mon guys.
Really now, noone?
I case you were wondering at the lack of replies: people won't ever dump their misc partitions unless they're pretty naive: it includes things like bespoke MAC addresses, WiFi passwords and certificate info,so presumably a lot of other security related stuff... I know some of the stuff in there, but I'm not smart enough to scrub it before posting it around... and some of the sanitising (MAC addresses) would make it unusable for you.
What are you aiming to get to (stock ROM / LineageOS / other)??
You can just factory restore using LG Bridge on a Windows PC and then if you want LineageOS, then you can start again (re-flash the unlock.bin, sideload TWRP, etc)....
BTW - I did the same - LineageOS auto-update, bricked (here) and then recovered (back to LG stock), then tried again: unlocked it again, TWRP again... and re-installed LineageOS, only to face problems with WiFi now as my entire data partition (incl. misc) appeared encrypted - if I try to wipe it and start again, then the WiFi MAC address is all 0's and I can't seen to insert the original MAC (either via cat'ing in a replacement config file into data/misc/wifi like THIS) or via various "busybox ifconfig" commands...
Really frustrating... I can get everything, including WiFi working again if I re-apply a factory reset via LG Bridge, but I can't flash LineageOS as it seems that the data partition is unwritable (encrypted?) until I wipe it in TWRP...
BahnStormer said:
I case you were wondering at the lack of replies: people won't ever dump their misc partitions unless they're pretty naive: it includes things like bespoke MAC addresses, WiFi passwords and certificate info,so presumably a lot of other security related stuff... I know some of the stuff in there, but I'm not smart enough to scrub it before posting it around... and some of the sanitising (MAC addresses) would make it unusable for you.
What are you aiming to get to (stock ROM / LineageOS / other)??
You can just factory restore using LG Bridge on a Windows PC and then if you want LineageOS, then you can start again (re-flash the unlock.bin, sideload TWRP, etc)....
BTW - I did the same - LineageOS auto-update, bricked (here) and then recovered (back to LG stock), then tried again: unlocked it again, TWRP again... and re-installed LineageOS, only to face problems with WiFi now as my entire data partition (incl. misc) appeared encrypted - if I try to wipe it and start again, then the WiFi MAC address is all 0's and I can't seen to insert the original MAC (either via cat'ing in a replacement config file into data/misc/wifi like THIS) or via various "busybox ifconfig" commands...
Really frustrating... I can get everything, including WiFi working again if I re-apply a factory reset via LG Bridge, but I can't flash LineageOS as it seems that the data partition is unwritable (encrypted?) until I wipe it in TWRP...
Click to expand...
Click to collapse
I just need it to stop Wi-Fi MAC address from being changed on reboot and restore any other potential loss from the wiped misc.
I'll use a hex editor to search for the address and edit the one uploaded ofc.
As for security, misc is a readonly partition, no personal stuff/data are stored in it. Only the MAC address can be considered "targeted information" which is not sensitive or smth as MAC is not reachable/trackable after first router hop anyway.
If someone uploads it you'll solve your issue too.
DenyDarko said:
I just need it to stop Wi-Fi MAC address from being changed on reboot and restore any other potential loss from the wiped misc.
...
Click to expand...
Click to collapse
The guide at https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841 didn't help?
Under RR now I still had the issue with changing MAC addy despite the guide (all other roms like AOSiP, DU or OwnRom were fine) - but I noticed that it only ever changed it to ONE specific addy. So I used that one and set it with the guide and it's been stable since then :fingers-crossed:
Nimueh said:
The guide at https://forum.xda-developers.com/lg-g5/how-to/guide-fix-wifi-mac-address-changing-t3533841 didn't help?
Under RR now I still had the issue with changing MAC addy despite the guide (all other roms like AOSiP, DU or OwnRom were fine) - but I noticed that it only ever changed it to ONE specific addy. So I used that one and set it with the guide and it's been stable since then :fingers-crossed:
Click to expand...
Click to collapse
This is how I do it ATM but its not a permanent solution.
Well... I guess no one is willing to upload the evil misc.img xD
DenyDarko said:
This is how I do it ATM but its not a permanent solution.
Well... I guess no one is willing to upload the evil misc.img xD
Click to expand...
Click to collapse
Well that was my point - it IS permanent for me.
Under RR it kept changing the MAC back at every reboot, but always to ONE specific MAC. So I edited the config file with that MAC and it hasn't changed it back yet (roughly 12 reboots and a dirty flash later).
Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.