Cannot adb correctly--connection is made, then lost - G4 Q&A, Help & Troubleshooting

Hi all. I have a newbie question that is more newbie than I am. I am in the bizarre situation of having installed the SDK toolkit, tried various tweaks, but am utterly unable to run adb commands to my LG G4, after the first one, "adb reboot bootloader". After that, the device seems to reboot--but I can no longer connect to it. Any other adb command results in either hanging (adb oem device-id) or "error: device not found". I have created a new virtual machine so that the installation of Windows 7 x64 is clean.
Of course, I have the "international" H815. To unlock its bootloader, I need to get its device id. The problem with LG is that far fewer people use it, and various approaches to unlocking/rooting it have just not been developed yet. And of course, LG has become as malign as Samsung ever was. I've learned this recently.
Anyway, could I be the only one who is having such problems?

srk05 said:
Hi all. I have a newbie question that is more newbie than I am. I am in the bizarre situation of having installed the SDK toolkit, tried various tweaks, but am utterly unable to run adb commands to my LG G4, after the first one, "adb reboot bootloader". After that, the device seems to reboot--but I can no longer connect to it. Any other adb command results in either hanging (adb oem device-id) or "error: device not found". I have created a new virtual machine so that the installation of Windows 7 x64 is clean.
Of course, I have the "international" H815. To unlock its bootloader, I need to get its device id. The problem with LG is that far fewer people use it, and various approaches to unlocking/rooting it have just not been developed yet. And of course, LG has become as malign as Samsung ever was. I've learned this recently.
Anyway, could I be the only one who is having such problems?
Click to expand...
Click to collapse
I have seen a few people in this same boat (with the actual unlockable variant), though I do not recall every seeing anyone get an answer out of anyone on what to do in order to fix it.....Though since this is supported by LG, you could always try to email them directly or call their customer support group.....I assume since they offer the service they should also offer support for it.

Z3ldaFan88 said:
I have seen a few people in this same boat (with the actual unlockable variant), though I do not recall every seeing anyone get an answer out of anyone on what to do in order to fix it.....Though since this is supported by LG, you could always try to email them directly or call their customer support group.....I assume since they offer the service they should also offer support for it.
Click to expand...
Click to collapse
Thanks for your reply. When I call LG support I get no help whatsoever, with the people there not even being allowed to go to the Developer web site to see what I'm talking about regarding unlocking the bootloader. I have asked for a phone number in the Developer email, but responses are sloooow, and this request has been ignored so far.
It looks like LG is just not my kind of manufacturer. Other Americans in my situation should be forwarned: LG will not help you.

jkamel123 said:
Thanks for your reply. When I call LG support I get no help whatsoever, with the people there not even being allowed to go to the Developer web site to see what I'm talking about regarding unlocking the bootloader. I have asked for a phone number in the Developer email, but responses are sloooow, and this request has been ignored so far.
It looks like LG is just not my kind of manufacturer. Other Americans in my situation should be forwarned: LG will not help you.
Click to expand...
Click to collapse
Well damn, I am sorry to hear that man. Had I known I would not have made you waste your time (now I feel like a ****). I will search around online and message a few people and see if I can get an answer or a solution (hopefully a resolution) for you.
Again I am sorry that LG was of no help.....gotta love how THEY offer these things but then refuse to give support for them.
---------- Post added at 12:53 PM ---------- Previous post was at 12:47 PM ----------
*Quick afterthought* - Maybe you can try grabbing the Minimalist ADB & Fastboot, this worked for a couple of my HTC devices when I was having troubles getting them to link up with my PC -- http://forum.xda-developers.com/showthread.php?t=2317790
Also (I am sure you do/did) did you make sure to go into your developer options and turn on the "Unlock OEM Bootloader" and also activate the USB Debugging optionn.

Z3ldaFan88 said:
Well damn, I am sorry to hear that man. Had I known I would not have made you waste your time (now I feel like a ****). I will search around online and message a few people and see if I can get an answer or a solution (hopefully a resolution) for you.
Again I am sorry that LG was of no help.....gotta love how THEY offer these things but then refuse to give support for them.
---------- Post added at 12:53 PM ---------- Previous post was at 12:47 PM ----------
*Quick afterthought* - Maybe you can try grabbing the Minimalist ADB & Fastboot, this worked for a couple of my HTC devices when I was having troubles getting them to link up with my PC -- http://forum.xda-developers.com/showthread.php?t=2317790
Also (I am sure you do/did) did you make sure to go into your developer options and turn on the "Unlock OEM Bootloader" and also activate the USB Debugging optionn.
Click to expand...
Click to collapse
No need for you to feel bad. I had already contacted LG *twice* and listened in ever greater amazement at what I was hearing. And yes, I did turn on the Unlock OEM Bootloader and USB Debugging! (But hey, it's important to verify.)
I'll check the Minimalist ADB. I think the real issue might be some DOS path setting to certain LG drivers. What else could it be?

I did try the "Quick afterthought" just before I completely recreated a virtual machine and tried one last time. But that didn't help.
I somehow managed to get the drivers for the LG working, at least somewhat. Note that the downloadable drivers from the LG Mobility site were apparently worthless. The phone will push out to the PC some drivers, but you must click on them from a popup (something I never ordinarily even think to do). For some reason I had to do this twice. This allowed me to issue the fastboot oem device-id command with good results. However, after that happened ... I noticed that adb was hanging again. The LG G4 was, as usual, totally frozen and required a--get this--battery pull. Otherwise, it would just sit frozen with some fastboot info at the top and an LG icon.
So, now the question is whether I want even to use this unlock code. I'm not sure I can get adb to cooperate further, and the whole setup looks extremely dangerous to me. I mean, a battery pull?
Yes, that's LG!

srk05 said:
I did try the "Quick afterthought" just before I completely recreated a virtual machine and tried one last time. But that didn't help.
I somehow managed to get the drivers for the LG working, at least somewhat. Note that the downloadable drivers from the LG Mobility site were apparently worthless. The phone will push out to the PC some drivers, but you must click on them from a popup (something I never ordinarily even think to do). For some reason I had to do this twice. This allowed me to issue the fastboot oem device-id command with good results. However, after that happened ... I noticed that adb was hanging again. The LG G4 was, as usual, totally frozen and required a--get this--battery pull. Otherwise, it would just sit frozen with some fastboot info at the top and an LG icon.
So, now the question is whether I want even to use this unlock code. I'm not sure I can get adb to cooperate further, and the whole setup looks extremely dangerous to me. I mean, a battery pull?
Yes, that's LG!
Click to expand...
Click to collapse
If it makes you feel any better, back when I rooted my HTC Hero I had to take apart an S-Video cable so I could make the phone short out (had to connect from MicroSD slot to the motherboard) basically this made it boot from the SD card as opposed to from the phone.....Talk about being sketchy, eh.

Related

HELP! Can't sync with Vista anymore.

I recently installed a different ROM onto my device, and now when it syncs with my PC to install the device driver, it installs "Micro$oft Windows Mobile Remote Adapter #3." What the hell is this? Removing it from the Device Manager only reinstalls the same one and I can't sync with WMDC. How do I get Vista to install the correct driver, and why did it never have a problem before?
This happened to me as well after I installed Schap's 3.54c ROM would like to know if there is a fix.
Oh come on, guys. I really wish just once someone would successfully answer one of my questions. This is kind of a big deal here. I can't flash another ROM if I can't sync, and I'm a little skeptical that NO ONE HERE has ever encountered a solution for this. Help me out!
You've been very lucky my friend.
Blowfish64 said:
Oh come on, guys. I really wish just once someone would successfully answer one of my questions. This is kind of a big deal here. I can't flash another ROM if I can't sync, and I'm a little skeptical that NO ONE HERE has ever encountered a solution for this. Help me out!
Click to expand...
Click to collapse
You’re damn lucky no one has flamed you for all of your noob posts. You need to post less and search and read more.
However, because I'm somewhat of "noob" as it relates to posting but, I'm a bit of veteran when it comes to flashing, etc. I’ll bail you out on this one.
1) First, in order to flash from Vista you should visit the Incredible MrVanx’s site. That should allow you to flash from Vista (I haven’t tried it as I have an XP machine right behind me from which to upgrade my 8525 without the risk of heartburn).
2) If it’s syncing you want then you may need to disregard the above and follow the advice posted here.
And, as advice I gave to another smarta** poster (free advice being worth exactly what you paid for it). Drop the attitude and improve your searching/reading skills. If you don’t want to do that, then stop f’ing around with ROM upgrades.
Timtown said:
You’re damn lucky no one has flamed you for all of your noob posts. You need to post less and search and read more.
However, because I'm somewhat of "noob" as it relates to posting but, I'm a bit of veteran when it comes to flashing, etc. I’ll bail you out on this one.
1) First, in order to flash from Vista you should visit the Incredible MrVanx’s site. That should allow you to flash from Vista (I haven’t tried it as I have an XP machine right behind me from which to upgrade my 8525 without the risk of heartburn).
2) If it’s syncing you want then you may need to disregard the above and follow the advice posted here.
And, as advice I gave to another smarta** poster (free advice being worth exactly what you paid for it). Drop the attitude and improve your searching/reading skills. If you don’t want to do that, then stop f’ing around with ROM upgrades.
Click to expand...
Click to collapse
Meanwhile, you need to post less and learn to read more carefully to the posts of those you're responding to. I have flashed ROMs a number of times. Where did I say that I did not know how to flash a ROM? I said that I can't now because since my last flash Vista will not recognize my PPC. It installs the wrong driver and I cannot figure out how to change that. The only thread I found that seemed to answer this question (http://forum.xda-developers.com/showthread.php?t=303634) did so in italian.
I also found another thread dealing with this same problem (http://forum.xda-developers.com/showthread.php?t=301876&page=3) but aside from re-installing Vista which I am loath to do, none of those solutions worked either.
And as for your second thread you directed me to, I'd already read that and tried downgrading WMDC before. I suppose I should have clarified myself by saying that it's not simply that I can't sync, I cannot connect my PPC to my computer through WMDC at all. I should have been more specific, but I figured since I mentioned that it kept installing the wrong driver, you would have been able to figure that out on your own.
And let me get this straight, you call yourself a veteran flasher, but don't even HAVE the computer operating system I'm having trouble with? Perhaps we both have things to improve about our postings, Timmy.
As for all my "noob" posts, I searched all of them before posting. Not to mention I've only had to post three previous questions which I could not find an answer to on here or elsewhere, those being
A) Is it possible to copy the gwes.exe.0409.mui without having to do a ROM dump? (Never got resolved, though Sleuth at least tried the basics).
B) Is there anyway to redate SMS's since Jeyo screwed them all up when using the program to back them up. (Never got resolved).
C) Can anyone help with the device lock asking for a password I never set up? (Yep, never got resolved).
If you would like to direct me to RELEVANT threads that answer these questions, I'll be more than happy to thank you for it, but until then at least you did get one thing right about your post, that being what it was worth.
Don't know if you've tried this, but.
I had the same issue. After installing one of JJ's ROMs, I couldn't get WMDC to recognize the new build. Broke all partnerships, nothing helped.
I then completely uninstalled WMDC and rebooted. I then went back to MS and grabbed WMDC again. It installed, I plugged in the TyTN and crossed my fingers.
The drivers re-installed and everything is good in the world now.
Also, Mr. Vanx's guide for downgrading drivers is not necessary for the HTC official or at least the last three builds of Black. I can't speak for any other RUU's, but the latest completely work with Vista (Ultimate & Enterprise, at least).
Hope this helps you out.
Thanks for the effort, silverfox, and the tone. Unfortunately I've tried that a couple of times, and it still goes along merrily installing the wrong driver. Does anyone how I could manually select the "HTC USB SYNC" driver? Not even sure where it's located. Checked under system32/drivers but it's not in there.
Nevermind...
Blowfish64 said:
...can't sync, I cannot connect my PPC to my computer through WMDC at all. I should have been more specific, but I figured since I mentioned that it kept installing the wrong driver, you would have been able to figure that out on your own.
Click to expand...
Click to collapse
You are quite right, I should have been able to read you mind. My bad.
Blowfish64 said:
And let me get this straight, you call yourself a veteran flasher, but don't even HAVE the computer operating system I'm having trouble with? Perhaps we both have things to improve about our postings, Timmy.
Click to expand...
Click to collapse
Wrong again blowhard, read the post again, especially the part about where I say I have "...an XP machine right behind me..., I'm posting from a Vista machine.
Blowfish64 said:
As for all my "noob" posts, I searched all of them before posting. Not to mention I've only had to post three previous questions which I could not find an answer to on here or elsewhere, those being
A) Is it possible to copy the gwes.exe.0409.mui without having to do a ROM dump? (Never got resolved, though Sleuth at least tried the basics).
B) Is there anyway to redate SMS's since Jeyo screwed them all up when using the program to back them up. (Never got resolved).
C) Can anyone help with the device lock asking for a password I never set up? (Yep, never got resolved).
If you would like to direct me to RELEVANT threads that answer these questions, I'll be more than happy to thank you for it, but until then at least you did get one thing right about your post, that being what it was worth.
Click to expand...
Click to collapse
Really? Someone else might help you but, you are apparently so smart, I doubt it. Good luck Richard-head.
This worked for me
Settings > Connections > USB to PC
Uncheck "Enable advanced network functionality"
tinpusher said:
This worked for me
Settings > Connections > USB to PC
Uncheck "Enable advanced network functionality"
Click to expand...
Click to collapse
Unfortunately, I've had that disabled for a long time now.

How to access diag mode on Sprint Arrive, and maybe all HTC

You can access the Diag mode switch on HTC Arrive by typing ##MFG# (##634#) in the phone app and hit Diag, then enable it. I can connect via CDMA workshop and dump the memory, ESN, MSL, etc. It will turn off Zune syncing while enabled, but otherwise operate as normal.
You can also go to FieldTrial and see things like supported bluetooth profiles, battery voltage, GPS coordinates, Signal levels, and other bits of info I cannot find in the OS.
Not sure what else we can do with this diag mode, let me know if anyone finds anything fun to do with it. Maybe tethering?
-Paul
Doesn't work on HD7. The dial pad just refreshes (no numbers entered).
On my arrive it bring up a menu with sliders.
drkfngthdragnlrd said:
Doesn't work on HD7. The dial pad just refreshes (no numbers entered).
Click to expand...
Click to collapse
Doesn't work on HTC Surround too, same behavior.
htc trophy
On htc trophy doesn't have afunktion
I added in pictures of some of the sliders and output. Maybe it is only a Sprint thing? I still think we can do tethering with this, I am just having a few win7x64 driver difficulties to straighten out. It creates a "HTC Diagnostic Interface" in device manager but it has been flaky in creating an "HTC Modem" port. Get that figured out and tethering should work, on Sprint at least.
-Paul
Confirmed works on Verizon HTC Trophy. Its probably a CDMA thing
Paul_Hammons said:
I added in pictures of some of the sliders and output. Maybe it is only a Sprint thing? I still think we can do tethering with this, I am just having a few win7x64 driver difficulties to straighten out. It creates a "HTC Diagnostic Interface" in device manager but it has been flaky in creating an "HTC Modem" port. Get that figured out and tethering should work, on Sprint at least.
-Paul
Click to expand...
Click to collapse
Something I just noticed that may be of use. I couldnt get my computer to see it all at first. I had to download HTC Sync (got the one for the incredible) and it now shows like it does for you with a "HTC Diagnostic Interface" in my ports section.
So then I found this http://forum.xda-developers.com/showthread.php?t=929868
which will work if your phone is unlocked (mine is not due to not wanting to pay 100 just for tethering). It seems this diagnostic window is where other phones can access tether and we are using HtcVComV64.sys already. Now we just need it to call HtcUsbMdmV64 and create the HTC Modem as you said before. I think we still would need probably a custom XAP to get it to call which means we would still need the unlock but this menu may make it easier for those unlocked with CDMA to get access or someone may figure how to use this menu for tethering after all.
good luck
ca2l3vin said:
Something I just noticed that may be of use. I couldnt get my computer to see it all at first. I had to download HTC Sync (got the one for the incredible) and it now shows like it does for you with a "HTC Diagnostic Interface" in my ports section.
So then I found this http://forum.xda-developers.com/showthread.php?t=929868
which will work if your phone is unlocked (mine is not due to not wanting to pay 100 just for tethering). It seems this diagnostic window is where other phones can access tether and we are using HtcVComV64.sys already. Now we just need it to call HtcUsbMdmV64 and create the HTC Modem as you said before. I think we still would need probably a custom XAP to get it to call which means we would still need the unlock but this menu may make it easier for those unlocked with CDMA to get access or someone may figure how to use this menu for tethering after all.
good luck
Click to expand...
Click to collapse
Any update on this? Can we make this work with the Chevron Unlock?
Paul_Hammons said:
I added in pictures of some of the sliders and output. Maybe it is only a Sprint thing? I still think we can do tethering with this, I am just having a few win7x64 driver difficulties to straighten out. It creates a "HTC Diagnostic Interface" in device manager but it has been flaky in creating an "HTC Modem" port. Get that figured out and tethering should work, on Sprint at least.
-Paul
Click to expand...
Click to collapse
All pc drivers can be found here
Already did the leg work pimpin
win7 pc drivers were a pain to install but can be done
http://forum.xda-developers.com/showthread.php?t=1014234&page=2
Also ansar already made a custom xap thats what the usb mode switch app is
Yes I do realize that any talk of this is a little archived but I thought I would give it a shot. On my Htc Arrive as probably many other Htc, you cannot access nor input anything related to sound boosting or increasing, as easily as samsungs and a few others. Has anyone ever figured out how to get to the sound/volume control panel thru the diagnostics. I work construction and the ringers and alarms are a little bit low for me. Actually a lot. I've tried all the reg hacks available and keep coming back to the answer being in the diagnostic mode area. Thank you for your time and any response would be greatly appreciated. thank you
CDMA only i think
on my gsm it also refreshes (7 mozart)
this looks like locked
maybe full unlock should make it accessible with some registry tweaks ?

[Q] Smartphone newbie: Unlocking?

Greetings!
I just got a HTC Desire from a friend. This is my first smartphone and besides normal uses of the phone like calling, texting taking photos, I don't know anything.
Now, I can't use my simcard on the phone, but I know my friend could use his, so I suppose it's sim-locked and it's obviously possible to unlock phones without going to a store and paying them a stupid price to get it done.
That's where this thread comes in; For starters I want to learn how to unlock my phone. I've searched the forums and looked here and there for ways to do it and I might've found the solution. The problem is that I don't really understand the solution, because of words like "rooting/unrooting" S-OFF/S-ON" "Goldcard" and even "HTC Desire (HTC Bravo)" doesn't make sense to me.
Here's a thread that keeps poppin up in combination with Desire and Unlocking:
http://forum.xda-developers.com/showthread.php?t=943726
But I'm afraid of following the steps on that thread because of my lack of information and knowledge about my phone.
Do I even have the phone they speak of? (HTC Desire(HTC Bravo)), Do I have the right androidversion or doesn't that even matter? Are there previous steps that has to be done before proceeding to use the "HTC Desire SIM-Unlock Utillity"? (if that is what I'm supposed to use)
Any help is appreciated even if the help simply is a redirection to another thread.
If you cannot provide me with help because my thread lacks some information, then please tell me that so I can try to provide the information necessary.
Thanks,
Jerry.
I used it twice for my DESIRE's worked well but I used iso version as it was ages ago
Any doubts ask in thread
Okey, so I should just do it?
And there's nothing I have to do before, and my android version etc doesn't matter?
I really don't remember what state my phones were... have a good reading throughout the thread then decide, that is your call
read the thread thoroughly and if you dont understand a term then just google it like "What is S-OFF?". And the HTC Desire is the HTC Bravo also.
Yep, read, read and read some more until you are confident you know what each term or reference means and what it is you are actually going to do with your phone.
Don't rush into it, take your time. It's actually a lot easier and less painful than you might first think, as long as you do the research first.
After reading ALOT, I decided to try the sim-unlocking utility since it seemed harmless, and harmless it was. It was executed without any errors but I can still not use my simcard for it. It doesn't appear in the list of "Network operators".
After some more reading I used Revolutionary to S-off my phone (even though it was s-off'ed before) since that had hepled for some people, but not for me.
If the phone was bought in say, UK, is it possble that it will never work with my swedish operator, or should an unlock fix that, regardless of where the phone was bought?
Also, any ideas on what I should try next?
Is it possible that rooting the phone and doing the unlock thingy again will help?
It sounds like the phone hasn't got your particular networks settings in it. You'll need to look on your providers website and search for 'APN' settings. In 'settings', 'wireless & networks', 'mobile networks' and finally 'access point names' you can enter these settings then set them as default and hopefully, job done.
I checked the providers info and entered it, but it seems that that info is mainly for internet and mms. It still didn't solve my problem, since it doesn't recognize or acknowledge my simcard.
Right now I just wanna throw the phone at the wall, then go stomp on it a few times...

[Q] pattern lock reset help ~ I've not forgotten it, simply want to change it

Please help me? I am by no means a developer, just a wanna be nerd with a new phone. I'm looking for pattern lock reset help ~ I've not forgotten it, simply want to change it, and while it seems like something that would be simple and obvious, it is currently not presenting itself that way and I'm more than a little frustrated with myself (and it).
Meanwhile, the first two weeks the phone seemed just fine (apart from not playing with Planet anymore, though that seems worked out now, though I'm not at all certain). Now, I'm getting a lot of security issues cropping up that seem disturbing. Verizon tech support tells me that Kitkat 4.3 has known issues in this arena that they hope will be corrected in the next update. There is a constant message about my network traffic, email, etc may be monitored by an unknown third party and to check my security certificates. Did that ~ cleared them all, but that only helped for about 10 minutes. The phone insists that it cannot get a secure connection to Facebook, so I am too wary to do much of anything online with it. Seems to defeat the purpose of even having the phone. I'm seriously considering switching back to my last smartphone and turning this one off (I do not believe that I can return it).
I'm so sorry to ramble on so, but is it insane to ask if the M8 can be pushed back to an older version of Android?!?!?
Thank you so very much for ANY help at all.
Change pattern: settings, security, click on Screen lock and enter your current pattern. Click Screen Lock again to enter a new one, then repeat to confirm, and you're done.
For the second part I have no solution I'm afraid.
vosg said:
Change pattern: settings, security, click on Screen lock and enter your current pattern. Click Screen Lock again to enter a new one, then repeat to confirm, and you're done.
For the second part I have no solution I'm afraid.
Click to expand...
Click to collapse
He is asking for how to reset it not how to change it.And @hnvr911 you should google it.You shouldn't ask for hacks in xda.
Jyotirdeb said:
He is asking for how to reset it not how to change it.And @hnvr911 you should google it.You shouldn't ask for hacks in xda.
Click to expand...
Click to collapse
"He" is a she... and I am not looking to hack anything at all. I am simply too daft to change my own security pattern. As I stated clearly, I have not forgotten how to unlock my phone, I would simply like to change it, and while this should be a simple and obvious task, it appears to be eluding me at present... (though I am, somehow, adept enough to have already tried the obvious tactic of "googling" the question before annoying those I presumed more clever than myself.
To the first response, I thank you for your kindness and patience, I will attempt your suggestion straight away.
Kind regards,
~donna:cyclops:
hnvr911 said:
"He" is a she... and I am not looking to hack anything at all. I am simply too daft to change my own security pattern. As I stated clearly, I have not forgotten how to unlock my phone, I would simply like to change it, and while this should be a simple and obvious task, it appears to be eluding me at present... (though I am, somehow, adept enough to have already tried the obvious tactic of "googling" the question before annoying those I presumed more clever than myself.
To the first response, I thank you for your kindness and patience, I will attempt your suggestion straight away.
Kind regards,
~donna:cyclops:
Click to expand...
Click to collapse
Sorry my bad didnot see "I've not forgotten it" it.
thank you!!!
vosg said:
Change pattern: settings, security, click on Screen lock and enter your current pattern. Click Screen Lock again to enter a new one, then repeat to confirm, and you're done.
For the second part I have no solution I'm afraid.
Click to expand...
Click to collapse
Thank you so very much for the help. Your instructions worked perfectly, and I very much appreciate your kindness and patience.
Kind regards,
~donna
hnvr911 said:
Thank you so very much for the help. Your instructions worked perfectly, and I very much appreciate your kindness and patience.
Kind regards,
~donna
Click to expand...
Click to collapse
You're most welcome.
hnvr911 said:
Please help me? I am by no means a developer, just a wanna be nerd with a new phone. I'm looking for pattern lock reset help ~ I've not forgotten it, simply want to change it, and while it seems like something that would be simple and obvious, it is currently not presenting itself that way and I'm more than a little frustrated with myself (and it).
Meanwhile, the first two weeks the phone seemed just fine (apart from not playing with Planet anymore, though that seems worked out now, though I'm not at all certain). Now, I'm getting a lot of security issues cropping up that seem disturbing. Verizon tech support tells me that Kitkat 4.3 has known issues in this arena that they hope will be corrected in the next update. There is a constant message about my network traffic, email, etc may be monitored by an unknown third party and to check my security certificates. Did that ~ cleared them all, but that only helped for about 10 minutes. The phone insists that it cannot get a secure connection to Facebook, so I am too wary to do much of anything online with it. Seems to defeat the purpose of even having the phone. I'm seriously considering switching back to my last smartphone and turning this one off (I do not believe that I can return it).
I'm so sorry to ramble on so, but is it insane to ask if the M8 can be pushed back to an older version of Android?!?!?
Thank you so very much for ANY help at all.
Click to expand...
Click to collapse
Have you tried following these "suggestions" ?
HOWTO Install a custom cert without "Your network could be monitored" message
How can I trust CAcert's root certificate?
Remove "Network May Be Monitored by an Unknown Third Party" in Android 4.4 KitKat
Maybe/Hopefully it'll sort out your second problem in regards to the Trusted Credentials.
Anyone htat ever needs to reset their lock if they have forgotten it or get locked out somehow, Here is my backdoor mod I created specifically for this type of situation You may not need it now but download it & save it so you will always have it with you when that time comes if it ever oes and chances are, it will!
http://forum.xda-developers.com/showthread.php?t=2789684

replacement motherboard for G4 came with 'hacked' ROM

Hi,
Just something that worries me a lot atm and wanted to ask/alert people about. Probably 'a thing' that everybody knows about (?) in which case .. .well.. carry on, nothing to see here
I ordered a replacement motherboard for my LG G4 (H815) on ebay and the board I got does not seem to have come with the Stock ROM on it although it does appear at first to be stock.
When going through the pre-installed Apps I noticed that there was something odd though : it comes pre-installed with SuperSU (which starts automatically at boot). Even worse : I can't remove that SuperSU either, only Disable it.
When I tried to Unlock the bootloader at LG's website and replace the ROM (something I had done before so I know the procedure) I was told that the IMEI and DeviceID do not match. Replacing the ROM seems to not be an option even though it probably was rooted before to install the current ROM. I haven't tried to flash it with LG Flash yet ... so maybe that'll be the way out.
The more I started thinking about it the more nefarious this seems to me : a replacement motherboard with a locked bootloader that can't be unlocked (the ROM on it is Android 5.1 btw, not 6) which starts a SuperSU service at boot that most people probably wouldn't even notice and which has access to :
- Google Play billing service
- Retrieve running apps
- Run at Startup
- Prevent Phone from sleeping
That service could turn that phone into a zombi and considering that more smartphones than this one are probably in the same state things could get ugly.
What's worse, although I did disable it, there really is no way of really knowing that the smartphone is indeed 'safe'. I'm surely not going to use it for Home Banking atm! But even email or adding a Google account , or using facebook, etc already are things you probably shouldnt do when somebody else may have root on your smartphone..
kind regards,
Benny
kleykenb said:
Hi,
Just something that worries me a lot atm and wanted to ask/alert people about. Probably 'a thing' that everybody knows about (?) in which case .. .well.. carry on, nothing to see here
I ordered a replacement motherboard for my LG G4 (H815) on ebay and the board I got does not seem to have come with the Stock ROM on it although it does appear at first to be stock.
When going through the pre-installed Apps I noticed that there was something odd though : it comes pre-installed with SuperSU (which starts automatically at boot). Even worse : I can't remove that SuperSU either, only Disable it.
When I tried to Unlock the bootloader at LG's website and replace the ROM (something I had done before so I know the procedure) I was told that the IMEI and DeviceID do not match. Replacing the ROM seems to not be an option even though it probably was rooted before to install the current ROM. I haven't tried to flash it with LG Flash yet ... so maybe that'll be the way out.
The more I started thinking about it the more nefarious this seems to me : a replacement motherboard with a locked bootloader that can't be unlocked (the ROM on it is Android 5.1 btw, not 6) which starts a SuperSU service at boot that most people probably wouldn't even notice and which has access to :
- Google Play billing service
- Retrieve running apps
- Run at Startup
- Prevent Phone from sleeping
That service could turn that phone into a zombi and considering that more smartphones than this one are probably in the same state things could get ugly.
What's worse, although I did disable it, there really is no way of really knowing that the smartphone is indeed 'safe'. I'm surely not going to use it for Home Banking atm! But even email or adding a Google account , or using facebook, etc already are things you probably shouldnt do when somebody else may have root on your smartphone..
kind regards,
Benny
Click to expand...
Click to collapse
Wow that's unfortunate
Maybe try @steadfasterX's SALT utility and see what info it gives you. Also, I assume the IMEI is from the software and not the back of your phone (e.g. the one from your previous motherboard)
ThePiGuy said:
Wow that's unfortunate
Maybe try @steadfasterX's SALT utility and see what info it gives you. Also, I assume the IMEI is from the software and not the back of your phone (e.g. the one from your previous motherboard)
Click to expand...
Click to collapse
hi, Thanks, I'll have a look at Salt Utility. Got the IMEI from the OS, not the sticker. It's actually not just the mobo that I replaced. This G4 is 'lego-ed" togheter from parts sourced all over the place so do not have the original housing I have a second, unlocked G4. This one was supposed to be my backup. Maybe the unlock simply fails because somebody else already unlocked it before - not sure if they could relock it afterwards , maybe they used Salt and didn't unlock...
Thanks for the response.
Edit : Come think of it, maybe the Device ID is not only dependant on the Motherboard but calculated from information gathered from other parts in the system as well like the screen , cameras, sim card reader ... who knows :-/ Might not be able to unlock any LG when any of those unknown parts is replaced.
kleykenb said:
Edit : Come think of it, maybe the Device ID is not only dependant on the Motherboard but calculated from information gathered from other parts in the system as well like the screen , cameras, sim card reader ... who knows :-/ Might not be able to unlock any LG when any of those unknown parts is replaced.
Click to expand...
Click to collapse
. As long as you talk about the device ID displayed in fastboot it is coming from your mainboard and can't be changed. if you talk about the Android device ID it's generated by the ROM and that one can be changed easily
Sent from my LG-H815 using XDA Labs
steadfasterX said:
. As long as you talk about the device ID displayed in fastboot it is coming from your mainboard and can't be changed. if you talk about the Android device ID it's generated by the ROM and that one can be changed easily
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Good to know.
The Device ID came from fastboot in this case.
(and thanks for Salt Utility
kleykenb said:
Good to know.
The Device ID came from fastboot in this case.
(and thanks or Salt Utility
Click to expand...
Click to collapse
I'd be interested to know whether the IMEI and device model from SALT match the values displayed in the OS

Categories

Resources