Hi friends,
this is my first post here and thanks a lot to whom paying time to answer my questions.
I am having trouble with Samsung A7 2017. My wife always uses fingerprint for unlocking her phone. 2 or 3 days ago (~20.01.2018) she has started an official regular update and it finished normally. But after a restart, the phone gave a message that at least once the phone should be opened with the unlock pattern. Both i and my wife does not know or at least could not enter the correct pattern. So, i talked to a samsung call center person, and she asked me if we have any samsung account working on that phone but unfortunately we do not have one. She told me that more probably the data on the phone would have to be erased in samsung authorized technical service.
Until then, i did not have any experience about android technically, but i am now trying to understand what booting, TWRP, CWM, odin is meaning in terms of android running phone. Actually i am an electronics engineer, i even develop some basic applications on android but this kind of informations are completely different and new to me.
The only important point is that I REALLY DO NOT WANT ANY DATA LOSS, since i have many memories, pictures, videos on that phone. Please do not get angry with me for not backing up earlier, because i am already very sorry on that and angry with myself.
Anyway, i tried following but could not have success.
1. The phone's "developer options" menu is not activated, thus "USB debug" option is also unchecked. We do not have any chance for changing this because we are unable to bypass the pattern lock screen. So as i guess ADB commands are of no use. If this information is not true please explain me how i can proceed since i do not have much information.
2. I restarted the phone, by pressing "VolumeDown + Home + Power" buttons and Downloading mode appeared on the screen. I ran the Odin (latest versions - do not know exactly since i tried many) software on my PC and tried to download TWRP on the phone but failed each time. Phone gave the massage telling about "... FRP lock". I guess this is due to a lock under developer options (something like ... OEM lock). So i could not install TWRP.
Again if my knowledge is false please tell me the true way or right information.
3. I had an idea on creating a bootable SD card so that it will boot from it and thus giving me the opportunity for installing TWRP. But i could not find much information on that.
Please help me find a suitable solution. I am actually not interested in rooting the device or installing TWRP and in fact i do not want my device warranty voided. But my first priority is extracting safely my data from the phone. So if i need to root the phone to get them it is not a problem even if the varranty vanishes. Being able to bypass the lock screen is a sufficient solution for me now but i do not know how. So please direct me in a best and simplest way and i, as a newbie, will try to understand and search what you advice with my greatest effort.
Thank you all in advance & best wishes
Tankut (Elect. Eng.)
Unfortunately I don't think that there is any way to hack your phone with these conditions... The only think I can tell you is that you can factory reset your phone without paying anyone just from the downloading mode
Didn't Google photos automatically backup your pics and videos?
Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.
In addition to my previous post, i searched for possible backup of photos and videos on google account and found some, it is a nice news. But my wife was usully using CandyCam application on the phone and unfortunately i could not find any photos or videos bakup taken by CandyCam. I could not find a way for adding the CandyCam photo or video folders in the google backup task via google account remotely(that is outside the phone)(If only i had done it before on the phone itself while everything is fine). Do you think it is possible? Thanks.
hayat_bilgisi said:
Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.
Click to expand...
Click to collapse
Stock recovery is of no use unless you are prepared to wipe/reset the device.
Are you sure you can't use Google's find my mobile?
As far as I'm aware you can reset the lock to a password which you then use on the device. You may have to wait a while for this to happen and reboot.
Also if there is a Samsung account on the device you can unlock with that.
Have you tried entering the wrong pin around 15 times (I think)?
This used to allow you to use Forgot password and enter your Google log in details instead.
Lastly there is a possible way with ADB.
When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.
hayat_bilgisi said:
When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.
Click to expand...
Click to collapse
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?
ashyx said:
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?
Click to expand...
Click to collapse
Dear ashyx,
Thanks for your reply,
Yes, unfortunately there is no samsung account on the device.
At this moment i think the device has the latest official firmware(by saying firmware, i think you mean what we install or upgrade as the operating system) which samsung published, because my wife accepted the install just a few days ago(about 20.01.2018). I do not know what this upgrade consists of or what version it is. But is it possible to revert back to previous or former releases of firmware in my situation? Can you explain me shortly how i can do this briefly? And of course, if this works - e.i. if i reverted back to a previous firmware, do you think is it going to be useful in my situation?
How should i proceed? Thanks
By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.
hayat_bilgisi said:
By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.
Click to expand...
Click to collapse
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?
ashyx said:
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?
Click to expand...
Click to collapse
Here is the recovery screen of my A7 2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
hi everyone, i received today my phone, it seems to be a korean import unlocked for sims but not rooted.
i had a galsaxy s2 for a few years and know how to root and flash a rom, but problem is, on my htc one m8 there is no option to disable fast boot in the battery menu
i looked everywhere on the phone, it's just not there. i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore, links are dead, any suggestion?
thanks
anybody can help with this? I'm bloody stuck without a rooted phone!!!! thank you
satello said:
i looked on the net and somebody suggested CleanFLASH 1.0 just to start the phone in hboot, but can't manage to find the file anymore
Click to expand...
Click to collapse
Is your main problem not being able to get into bootloader (I don't see how else the fast boot power option would prevent you from rooting)? Just hold the power button until the options come up, select Restart, then when the screen goes black, immediately (before the white HTC boot screen) hold the power down rocker, and don't let go until hboot appears.
Alternately, hold power and vol up to force a reboot of the phone, then when the screen goes dark, switch to holding the vol down rocker.
Why are you worry so much on "fast boot" ?
You don't necessarily need to press power + volume down to go to hboot/bootloader.
I never disable "fast boot". Just simply restart, wait for the downanimation complete (it turn black screen) then press volume down (no holding power button) ... it will go to hboot.
Or you can plug in your device to PC with USB debugging enabled. Open a command prompt from your adb folder, type command adb reboot bootloader
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
I bet you do have a clone, does the phone has a playstore ? Install some phone specs app and see what it comes up with.
satello said:
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
Question is... Have I got a clone here??
Click to expand...
Click to collapse
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
ckpv5 said:
Is your about phone (there is no about phone on real HTC One M8, only "about") looks like these screenshots here : http://forum.xda-developers.com/showpost.php?p=54102512&postcount=7 and here : http://forum.xda-developers.com/showpost.php?p=54102633&postcount=8
Then it is a clone
Click to expand...
Click to collapse
it looks like that, checking the specs i can see a ARM v7 Processor, rev3 and a screen resolution of 1280 x 720...
Unfortunately, I think your device is a "Clone".
thanks guys, i've haven't been rooting for a couple of years, but really thougt something was wrong, terribly wrong. ok, will check back here when i get a real one, if needed.
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here. Nevermind. And yes, that phone is/was a clone
CNK80Q3MX said:
I think he was talking about "Fast boot" option in battery settings and not the "Fastboot" everybody is talking about here.
Click to expand...
Click to collapse
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
redpoint73 said:
The subsequent responses by clpv5 and myself understood that he was talking about "Fast boot" in Settings.
The only reason the "old" root guides instructed to turn off "Fast boot" in power settings, is that this mode enabled would prevent you from entering bootloader from a "powered down" conditon (since with the "Fast boot" option enabled, the phone was never actually powered down, just a deep sleep mode).
But as we pointed out, you could always enter bootloader from a reboot, since a reboot is always a true reboot. This would work regardless of whether "Fast boot" was enabled or not in power settings.
Although it should be noted this thread is from July 2014, and the "Fast boot" option was removed some time ago.
Click to expand...
Click to collapse
Thanks. I was looking for an explanation like that; in fact, somehow that's why I ended up in this thread. Though, it's useful yet, since there must be lots of devices still running the 'Fast boot' option due to certain manufacturer's lack of firmware updates and because not every device in need for support out there is actually a new device
Sent from my LG-D693n using XDA Free mobile app
same problem
satello said:
thank you. i've tried all the above all afternoon, including all the tools available but phone will only either reboot, sometimes in safe mode, or reboot regularly.
I think I know what I'm doing. I need to unlock bootloader to root, but this is not possible. When connecting to pc by usb, and using tools, from comand line, computer screen just hangs and nothing else happens. with another program I can only see a tiny "fast boot...." on the bottom left corner of the screen. I cannot basically unlock the bootloader hence root the device.
another few things i notice you may be able to double check.
trying to reboot in standard recovery, the android buddy comes up on the screen, like dead, with "no command" message. then pressing volume up will take to recovery screens, never seen this before.
And last, but not least, checking the serial number from the menu > about phone > status the serial number comes as
0123456789ABCDEF
I checked with HTC support on chat and they basically gave me the registered serial number for this IMEI and told me of course that it is impossible that it has another number as this cannot be changed.
Question is... Have I got a clone here??
edit: sorry about the data, it was not set the apn, now it works. normally used to have automatically apn from sim card, but it's not the case for this phone/sim
Click to expand...
Click to collapse
oh man, i thought i was the only one !
i have the same exact phone !
my serial number is exactly 123456789ABCDEF !!!
mine is a chinese mtk htc one m8. after hours of search i figured my phone name is alps_htc one m8 and yes my friend, is a fu..... clone !!!
i tried everything ! and search whole bunch of websites and forums like xda and xda itself, nothing happened !
i also get the => fastboot....... every time i try to go to bootloader !
this is something that you guys who trying to help here had to understand, these clone phones settings is completely different from other phones and even the original one ! hold power button then hold volume up or down, doesn't work !
every time it stock in => fastboot..... none of the buttons of the damn phone works and i have to wait until the battery drain ! real pain in the ass !!! because you know, htc one m8 does not have battery removing option, another pain in the ass !!!!!!!!!
i had a another problem too, when i wipe this clone phone, amazingly, the IMEI was gone !!! the phone said "invalid IMEI" !!! witch after hours of search i flashed it with an app from mobileuncle tools, thank to them amazing app allowed me to flash a custom IMEI from a unused phone.
now i use another htc device from the original manufacturer.
a little piece of advice, do not buy a clone phone ! cause it's going to piss you off !!!
and if you don't know how to recognize a clone from a original phone, its simple, just check the serial number, if it's feel weird, just give back the phone to seller, smile, and run out of the store !
thanks to XDA btw.
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
jac10000 said:
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
Click to expand...
Click to collapse
It does not show up ever, unplugged or plugged in.
Jacobsen Chief said:
It does not show up ever, unplugged or plugged in.
Click to expand...
Click to collapse
Ok try this :
Solution 1 : Have you switche the activate button ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
jac10000 said:
Ok try this :
Solution 1 : Have you switche the activate button ?
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
Click to expand...
Click to collapse
None of those things worked... Ive never seen this before. Here is a screenshot
I think it's a bug with lollipop and it seem that the solution is the factory reset
jac10000 said:
I think it's a bug with lollipop and it seem that the solution is the factory reset
Click to expand...
Click to collapse
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
jac10000 said:
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
Click to expand...
Click to collapse
I tried installing the KDZ though TWRP, but when it failed I decided to go ahead and just update it with the LG Software. I had read other articles on rooting the G3 with Lollipop, so I didn't really worry about re-rooting it until I ran into this problem.
For installing with the KDZ, I extracted Modem, Boot, and System.imgs, but the System.img failed. And yes with KitKat, I could use debugging.
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Dragontype191 said:
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Click to expand...
Click to collapse
Update, I made a post over on the US Cellular forums and if anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Dragontype191 said:
If anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Click to expand...
Click to collapse
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
To Enable USB Debugging mode that is blocked by Server you have to dissable McAfee Mobile SECURITY
Jacobsen Chief said:
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
Click to expand...
Click to collapse
Click on revoke USB debugging authorization. Click ok. Turn off developers option on the verg top. Turn it on again and voila you now have an option to put a check on usb debugging. Hope it works for you...
LG G3 Android 5.0 user
Jacobsen Chief said:
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
PLEASE PLEASE PLEASE READ! This is probably the fix to this problem all because of a stupid built in app that the g3 includes now and it has to do with McAfee Security.
If it worked mark this up for those future people who have issues!!
Okay so i found out what the problem was. I used to own and lg g2 but recently got the g3. Im with sprint fyi...but anyways i was tinkering around with it being 17 and stupid i bricked the phone, so i eventually got it fixed again. Previously my phone was rooted but now it wasnt so then i went back to get developer options activated and usb debugging active as well, however i ran into this problem. This stumped me because i had it rooted before. So then i was thinking what did i give accsess to that i hadnt before that isnt allowing usb debbugging...well it had to be an app since this didnt happen to me before and it had to be an app that i hadnt used before i bricked my phone and then i thought it has to be a built in app since no third party app would have that permission to say something like "disabled by server policy" then i realised okay what does the g3 have that the g2 doesnt have and is built in.....Mcafee security and Lookout! And it made sence because when you check the box for usb debugging you are making your android less secure! So i entered the McAfee app tapped settings ---> and the first option should be "lock down device" TURN THAT OFF! That right there is your culprit now go back to dev options and you can now enable usb debugging again please rate this up so people can see what was going on and how to fix it. No need to reset your phone. Also let me know if this worked. I have got nothing but positive feed back so far.
I am having the same problem and i have an LG Lucky and usb debugging is disabled by server policy and i really dont know what to do but it worked at first then later it got blocked.
help please
PokrTom said:
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
Click to expand...
Click to collapse
My debugging option is not available. Do I need to have my old sim card in place? It was from at&t. I took it out a while back. Is that why I cannot chose the Debug option? Ive tried everything on this forum.
I had the same issue. It was blocked by mcafee. I had to change it from " locked down mode" to unlocked mode, then turn developer options off and right baxk on. Then i was allowed to turn on usb debugging
Solution
Okay, so I was having the same issue. I contacted LG, Google, and finally AT&T after I tried a lot of the suggested solutions on this post. The AT&T tech support rep helped me research this issue. The issue is that an app on your phone is not allowing you to be able to debug, most likely a security app. I suppose that it thinks by allowing your phone to debug could cause harm to the device. The app that was keeping me from debugging was McAfee, which came pre-installed. When you disable this app, or whichever app is keeping you from debugging, you will then notice that the message 'USB debugging is disabled by server policy' goes away. I hope this helps you all, and happy developing!
God is good!!!
sir can you all help me for this problem? i can't update and fix my g3! ugrrrr !!!1
I have forgot my pin which was set just an hour ago. Fingerprint won't work as I restarted my device. I can't loose data. Please help me. USB won't work as device is locked.
Right now, I'm using guest mode. Where I can't even make a call. Just can access net and can't and other basic apps. Can't install any app due to insufficient storage.
????Sorry guyz. Please Lemme know asap.
you have 2 options :
1- Access your google account , and reset your pin "as if your phone was stolen"
2- "if your device is rooted" ,,
access /daata/system/
and delete "gatekeeper.password.key" file , "after making a backup" , this should make your device work with swipe only "you will not be able to have a pin"
Need help to root
no2ba said:
you have 2 options :
1- Access your google account , and reset your pin "as if your phone was stolen"
2- "if your device is rooted" ,,
access /daata/system/
and delete "gatekeeper.password.key" file , "after making a backup" , this should make your device work with swipe only "you will not be able to have a pin"
Click to expand...
Click to collapse
Can you please quickly redirect me to a post which can help me root.
Whats problems to nougat update?
My father in law died last weekend and we don't know the pincode of his stock Nexus 5X. We can access his Google account and we know the pincode of his sim card. I hope someone can help us out to get access to his phone. Things we've tried:
- The vingerprint reader was setup but we've tried a lot of possible pins. We've tried his vinger yesterday but because of the attempts the pin is also required now.
- With a pattern lock you'll get a possibility to unlock through the Google account password after some attempts but his phone was secured with a vingerprint and/or pincode. Only the delay between attempts get increased, currently 16 minutes between them.
- The lock option from https://www.google.com/android/devicemanager, but because there is already a pin lock it doesn't work. The pin doesn't change.
- I've tried to access the phone through ADB, booted into the recovery but "adb devices" doesn't see the phone. When I choose to "install update through adb" I see the devices with "adb devices" but I can't use "adb shell", only sideloading works.
- Installing a custom recovery could work but the bootloader is locked, when I unlock it a full wipe will be performed so we still can't access the data.
- From the Play store in the browser on my Mac I've installed the androidlost.com app on the phone, but the app needs to be opened once before it can be used.
- A rubber ducky could help us out, but I don't have one and the time between attempts get increased and increased... it would take weeks, months or years to unlock.
What other possibilities do I have?
First sorry for your lost!
Second, i don´t know for sure, but maybe get the phone to the store where you bought it and explain the situation, maybe they will give a correct advice or like you said the phone is registed in google ( device manager) maybe if you contact them they will help you with that ( the problem is they probably will take a long time to reply or don´t reply at all) or wait for a more expert user than me here in xda,
again, sorry for your lost and hope you solve this problem,
cheers
If the phone was rooted with a recovery installed, YES, you could delete the passcode files and get into it, without root/recovery, you cannot get into it without the password, that is the point of encryption and passwords and all that jazz.... Yes there is probably a way for some high level hacker to do it but good luck finding that.... If you just want to be able to USE the phone, do a factory reset from recovery....
TL.DR; Trying to root new Verizon Android flip-phone with Marshmallow 6.0.1, ARMv7. Firmware version: VN22010B. Seems to to be locked down.
Click to expand...
Click to collapse
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Why?
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
jfn0802 said:
First of all thank you, I've been looking for that service code to enable developer settings / adb since I discovered the phone secretly runs Android. But I don't see why we would need root, I've been using adb to side load apps since I can't get to a menu that allows it
Click to expand...
Click to collapse
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Same problem
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
i get the same error. did you find a solution? i would really appreciate it
InfectedPackets said:
1. Why? To install a custom ROM.
2. Did you get any issue with certificates when side-loading apps? I keep getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES. Can't seem to find the "Install from Unknown Sources" option.
Click to expand...
Click to collapse
MendilR said:
i get the same error. did you find a solution? i would really appreciate it
Click to expand...
Click to collapse
re: the certificate error for side loading apps...
Code:
adb shell settings put secure install_non_market_apps 1
turns off the unknown source block, but I'm still getting INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
Could the apk itself I'm trying to use have a bad certificate? Or is there another solution?
InfectedPackets said:
I'm trying to root the LG Exalt LTE, or LG VN220, from Verizon. Initially, I've attempted the common rooting kits, such as KingoRoot as well as the tools described around XDA. However all failed. I suspect the cause to be the restrictive permissions of /data/local/tmp, which prevents execution of binaries. I believe any kit using this location will likely fail to achieve anything.
As such, I've been looking to achieve the same using manual techniques. The first step, as in most rooting activity is to put the device into USB debugging mode. To do this on the VN220, first compose ##7764726220. When asked for a service code, use 000000 to access a special menu. Select the Developer Options > USB Debugging and select On. There is an additional menu below named Select USB configuration, from which you can select Media Transfer Protocol or RNDIS among other options.
With that done, you can verify that you can now communicate with the device via ADB. To do so, download the Minimal ADB and Fastboot bundle. While I was successful in querying the device with ADB with
Code:
adb devices
Trying to use fastboot simply outputs "< waiting for device >" indefinitively. It is also possible to open a shell using ADB, however attempting ADB with root will fail. I don't think this is caused by having wrong drivers, as all the other tools could detect the phone (see below), but rather a permission issue.
From there, I've try to boot in different modes, which are accessible by turning off the phone, and then powering up the device while holding the Volume Down button. This will boot into a white screen with some options, including the "Safe Mode" option which I attempted. The second mode is the "Firmware Upgrade" mode which is accessible by again, powering down the phone and powering it up again, but this time holding the Volume Up for 3 seconds.
Attempting to run the following fails:
Code:
fastboot oem unlock
That being said, I later found out that LG does provides a legitimate way to unlock the bootloader via their LG developer portal. Unfortunately the VN220 is not in the list of supported devices, nor does the procedure given applies to this phone. Additionally, it requires the device ID which fails also since it requires fastboot:
Code:
fastboot oem device-id
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Trying to run apps from the internal storage such as su or even using the chmod command only results in "Operation not permitted" messages. So even temporary root seems rather difficult.
At this point, I'd like to know if anyone has any advice on additional things I could try to root the phone, or even have temporary root.
Thanks in advance
@cyberrecce
Click to expand...
Click to collapse
Just curious - any success or updates. I can't seem to get past " INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from here.
Click to expand...
Click to collapse
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
PAULC91316 said:
Any ideas on how to get past - "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES"?
Click to expand...
Click to collapse
I'm still at the same place I was the other day when I posted this.
effulgent.unicorn said:
For installing apps I'm still not getting past INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES
I even tried pulling an apk from my LG G4 that successfully installed on that device and tried installing it on the Exalt, but same error.
The biggest reason I've seen for the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES is apks that are signed poorly. When I check the apks I'm using for their signatures with the JDK it says one or more of their signatures lack a timestamp which can cause problems.
Also, downloading the apk from the Exalt's browser and trying to install from either
settings > phone settings > storage > phone > explore > downloads > open > install
or
tools > file manager > internal storage > downloads > open > install
has been coming up with "app not installed" after it tries to install the apk.
I'm not really giving up though, I just don't really know where to go from
here.
Click to expand...
Click to collapse
InfectedPackets said:
The other attempt I've tried is using the LG Mobile Support Too l and while it was useful to obtain the KDZ file from their website, it also failed to apply the update. LGUP didn't recognise the model. (Note that both requires the USB mode to be RNDIS to detect the phone)
Click to expand...
Click to collapse
Can you please share with us the KDZ file?
Thanks!
anyone?
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Thanks for taking your time, to help me.
I will check if I can unlock the bootloader.
Thanks alot
r3w1NNNd said:
You will need to:
- unlock it’s Bootloader. If the “fastboot oem unlock” command will not work (and I’m quite sure it will not, since we’re talking about a USA LG device), you can stop here and throw the phone out the window.
- if by some any miracle you will be able to unlock the bootloader, you have two ways of rooting it:
1. Using TWRP and a superuser zip file (magisk or the now Chinese owned supersu). The main problem with this is that you will need to compile TWRP yourself, since I doubt anyone will bother for such an obscure device.
2. Using a prerooted boot image. You will need the stock boot image, install the latest magisk manager, let it root it and then flash it via fastboot. This is particularly difficult because you will need to decrypt the kdz file (if any available) in order to get the boot.img
Even if by a greater miracle you will be able to get 1 or 2 working, there still is a huge chance that the fastboot flash command will be disabled.
Forget about solutions like king/kingoroot. Best case scenario they will fail. Worst case scenario they will softbrick the phone by gaining temporary root and then modifying /system. That will in turn trigger dm-verity which will cause the soft brick.
Forget about the scams like oneclickroot. Their so called techs will try the aforementioned and fail and you will waste your $40.
Sorry To deliver the bad news, but there’s no way out of it.
Click to expand...
Click to collapse
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
effulgent.unicorn said:
Any sage advice on the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] issue when sideloading apps?
@jfn0802 said they had success with sideloading, but haven't been online in ages, and none of the rest of us seem to have had the same success. Minimum, that's what I would like to accomplish.
[side note, has anyone switched from Verizon with this phone? I'm looking to, but I'm wondering a couple of things like, does verizon have the mobile hotspot function restricted from use on other carriers? & etc & just wondering how it's doing off-verizon for anyone.]
Click to expand...
Click to collapse
my freinds are using it in Canada with videotron and everything works, without unlocking
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
GenTech Solution said:
Just to add a clue what to look at, I think these devices are from Verizon and they are blocking anonymous apps from being installed
Click to expand...
Click to collapse
Isn't that what turning on the "install from unknown sources" option should do? I still get the Install Parse Failed after switching it on with ADB.
@98jbsz I've tried to uninstall without success. What way did you do it? And does it just leave a blank space in the menu screen?
[Less on topic, sorry again, but has anyone seen the LG Wine LTE? http://www.lg.com/us/cell-phones/lg-UN220-lg-wine
It's strikingly similar to our friend the Exalt LTE here, but it seems less carrier branded/available at US Cellular, so I'm wondering if that would make a difference?
Major differences Wine LTE has more 4G bands (2/4/5/12/25) versus Exalt (4/5/13), which kind of has me kicking myself, because travel and 4G was one of the reasons I bought the Exalt. Both have quadband GSM and WCDMA, but interestingly the Wine also has CDMA.
Beyond that, there are some more smaller differences I scavenged from their LG pages, Exalt has more bluetooth profiles, supports more music formats, has more GPS capabilities, wifi calling, and 1 more ringtone. Wine has more supported video formats, and an FM radio.
I'm curious about what/if the Wine would have for sms messaging (I doubt it'd have Verizon's message+) and instead of my Verizon app...]
98jbsz said:
Yes right, but how can I go around it?
Ps. I was able to uninstall apps (I removed my Verizon)
With adb shell, as the user 0, but with adb normal uninstall didn't work, but when I try to install with adb shell, it gave the same certificate erorr
Click to expand...
Click to collapse
Alright, I also managed to uninstall my verizon and verizon's cloud app using
Code:
adb shell and the pm uninstall -k --user 0
But the Verizon apps folder on the menu screen remains, although it's empty. Any ideas on how to remove it?
Then I tried to install an apk using
Code:
pm install
and it came back with [INSTALL_FAILED_INVALID_URI] which...is a different than [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES], but not better.
right, but when you first copy the APK to the phone, and then you install it, you will see the [INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES] error. still not a solution