Related
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
C-4Nati said:
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Solved, mod please delete.
C-4Nati said:
Solved, mod please delete.
Click to expand...
Click to collapse
Please post your solution, so others can see it.
C-4Nati said:
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
stevedebi said:
Please post your solution, so others can see it.
Click to expand...
Click to collapse
I went into fastboot usb mode in the bootloader then connected the phone to the computer then dragged the fast boot file inside the sdk rar you download for the One into the command prompt then entered "fastboot erase cache" and hit enter then it let me boot into recovery and I reflashed the rom.
maigre said:
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
Click to expand...
Click to collapse
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
C-4Nati said:
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
Click to expand...
Click to collapse
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
maigre said:
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
Click to expand...
Click to collapse
Yeah I understand. I know I'm going to terminate the insurance I have with T-Mobile soon because I've violated the terms with them. I just have a slight screen lift like many others described on the top and bottom by the speakers and it's not bad at all just noticeable because I inspected it like a mad man when I heard the rumors. I can deal with it easily in it's current state as it's not a problem but if it were to become worse I'm not sure what to do. I know the chances being taken by unlocking as I've always done on every device I've had, I've just fortunately never had a defected device so it wasn't a problem.
4_SUXEN said:
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope that didn't work, I've owned several android devices and did what you just said and it always worked. This is the first time I've owned a non Samsung device in a while (because I used Odin with those) and I couldn't get into recovery at all and factory reset in the bootloader did nothing. Not much experience with fastboot as I've never had to use it but I'm glad I did so I have that in case I need to do it again in the future.
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
roboshawn said:
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
Click to expand...
Click to collapse
What do you have on your phone that you are worried about deleting? If it's contacts that should be saved with your google account. If it's pictures, you should keep dropbox installed so it always backs up your pictures. Now here's how to save your phone. Factory reset it. That's your only option.
You ask
i7vSa7vi7y said:
What do you have on your phone that you are worried about deleting? ... If it's pictures, you should keep dropbox installed so it always backs up your pictures. ...
Click to expand...
Click to collapse
I originally stated
roboshawn said:
Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose.
Click to expand...
Click to collapse
So yes, I understand the problem and what I could have done, but harping on that doesn't help me recover the photos.
But enough of that - it is done. So what next?
I tried the physical keyboard connected and it had no difference. I even reset the lock with Android Device Manager in the web browser and then disconnected that keyboard from the computer and used it on my phone. No luck.
The fact that this phone does not properly work with Android Device Manager is infuriating because it really should! And what's happened to me really shouldn't be a problem.
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
roboshawn said:
You ask
I originally stated
So yes, I understand the problem and what I could have done, but harping on that doesn't help me recover the photos.
But enough of that - it is done. So what next?
I tried the physical keyboard connected and it had no difference. I even reset the lock with Android Device Manager in the web browser and then disconnected that keyboard from the computer and used it on my phone. No luck.
The fact that this phone does not properly work with Android Device Manager is infuriating because it really should! And what's happened to me really shouldn't be a problem.
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
Click to expand...
Click to collapse
Well looks like the only thing you can do is not repeat the same mistake. Factory reset your phone set it up and get dropbox or google drive also root your phone and have usb debugging.
roboshawn said:
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
Click to expand...
Click to collapse
Ok. This is how it went.
I reset to factory defaults.
I enabled USB Debugging.
I rooted my phone using the guide over here How to root i545vrufnk1.
I tried various recovery photo/file programs such as Myjad, Yodot, Tenorshare, etc. These programs advertise that they can restore photos after a factory reset. None of them found my old photos. I didn't pay for any of these - I was just using their trial versions. If anyone has used one of these or something like it and had it succeed after a factory reset - please let me know.
I set up Google+ backup.
Next step I'll probably take as additional precaution is to setup the Samsung account service.
To reiterate - this is utterly frustrating that the Android Device Manager remote lock solution does not work for these phones - it goes so far as to tease you with the functionality, but essentially permanently lock your phone.
For anyone else looking to solve this problem - you may or may not have success depending on if you have a samsung account or usb debugging already on or a phone that is not exactly an I545, check out these links:
[RESOLVED] HELP please!! Unable to unlock device locked by Google Device Manager
How to Recover Photos and Data From a Keylocked Android Phone
Samsung Account
Good luck and fix your stuff - Samsung and Google!!!
If you reboot to recovery you should be able to use adb to pull files even without debugging turned on is the OS?
I'm having the exact same problem on my nexus 10 did you ever solve it? Seems really stupid that the adm lock function is so broken
I just had the same problem with a Samsung Galaxy S5. I solved the problem and unlocked my phone. Suggest the following if you locked your phone with a lock pattern:
1) Try the wrong pattern 5 times
2) You will see a message asking if you," Forgot Password"
3) Tap that message and you will be presented with a screen requesting your email and password.
4) Use your Google credentials and you will be able to unlock your phone.
Good luck!
change the lock pattern from settings
Go to settings>security and change your home lock screen.This worked for me.
ADM - Blessing and a curse?
Ok so yesterday my wife's phone was stolen out of a car. First we had AT&T shut down the services. According to the history, the attacker actually tried to access Paypal, and tried for a couple of minutes and gave up when he didn't get anywhere. He sent a password reset, that didn't go through. Then I found the ADM and turned on the Lock-screen with a message to call me. According to those who found the phone, the attacker apparently threw the phone underneath a car in a parking lot. The ADM-lock screen allowed them to call me... "Thank you 'Google!'"
Now to the bad news: I cannot get it to 'UNLOCK!'. No password I put in works. And when I attempt to reset the lock I get: "Since Google has verified that a screen lock is already set, the password you entered won't be needed". I guessing this means that it won't alter the password or it can't. Many people all over the internet have come up with all sorts of ideas for this. But I don't see anything 'satisfactory'. Besides just a complete 'reset'. So I really have killed the phone I just recovered? Meaning the ADM is also a 'Curse'? With sarcasm: "Thank you 'Google!'"
This is a Samsung Galaxy S4 Active SGH-I537. I've already attempted to hook up an USB cable, I see nothing. I'm pretty sure that USB debugging is not enabled.
I can enter the password 15-20 times, it never offers me for a 'forget password'. It sometimes says that I need to wait 30 seconds. It keeps tract of how many so-called bad attempts.
PS: I got it... After 30 guesses. The first password apparently stuck. Apparently I wasn't thinking too much, and I put in 'dude'. LOL. And it is now unlocked.
You are living my Exact Story!!
I have a Galaxy S4, and I had a pattern lock on my screen. I also have a 2-year-old, who unfortunately got ahold of my phone and locked it out. It's asking me for the backup Pin- which I've entered over and over, but it keeps saying it's incorrect. Now I have one try left before a factory reset Please help!! I don't want to loose all my memories of the precious (however difficult) daughter
It's also started having a white pop up box that says "Unfortunately, phone has stopped." Then asks me to click ok- it goes away for 5 seconds then pops back up again.
I have already contacted Verizon both over phone and went into the store. Both told me they could not help.. also already went to the Android Device Manager and tried to lock it so I could at least call my husband- I put in the Call Owner thing...
SO FRUSTRATING!!!! Anyway- still don't know what to do..... But just couldn't help but reply when I read your story- It was serious deja vu!!!!!
roboshawn said:
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
Click to expand...
Click to collapse
This might work
KateJuleLynn said:
I have a Galaxy S4, and I had a pattern lock on my screen. I also have a 2-year-old, who unfortunately got ahold of my phone and locked it out. It's asking me for the backup Pin- which I've entered over and over, but it keeps saying it's incorrect. Now I have one try left before a factory reset Please help!! I don't want to loose all my memories of the precious (however difficult) daughter
It's also started having a white pop up box that says "Unfortunately, phone has stopped." Then asks me to click ok- it goes away for 5 seconds then pops back up again.
I have already contacted Verizon both over phone and went into the store. Both told me they could not help.. also already went to the Android Device Manager and tried to lock it so I could at least call my husband- I put in the Call Owner thing...
SO FRUSTRATING!!!! Anyway- still don't know what to do..... But just couldn't help but reply when I read your story- It was serious deja vu!!!!!
Click to expand...
Click to collapse
i too had locked my nubia device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.
NITLOC1 said:
i too had locked my nubia device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.
Click to expand...
Click to collapse
This method WILL delete all data that is on the device! This will only not happen if your using a custom recovery solution!
Please be careful when giving advice.
If you log into the Android device manager website, it will assist you in unlocking your device. You can set up a password to bypass the pin lock, and make sure you don't lose your data
Sent from my SCH-I545 using Tapatalk
Can you just not flash system... I know there is a nc5 emergency no wipe for odin.. should be one for other firmwares, no?
Samsung SM-T531 Google locked
Hi All
Customer came in with a tablet that was stolen, google locked by her, but later recovered.
In short, this is where i'm at. ADM with her login details, unable to remotely unlock.
When blocking she used a password and device is asking for a PIN instead.
Device wont boot into recovery mode to factory reset.
Cant access device to connect to a network..
I cant think of another way around this.. ANYBODY, PLEASE HELP?
Android Device Manager Samsung Resolution
I read this in another forum, can't remember exactly where but if its your Samsung device use the find my Samsung app. Lock you phone then it may take a minute but the Samsung proprietary app will take over and lock your device. This will allow you entry into the device. Set the screen time out for 30 min then backup your device. This worked my Samsung Galaxy Note 3.
My phone did not originally have a lock screen until i used the Android Device Manager. Each time I entered the password it was incorrect. I wasn't presented with an option to enter my email after 5 attempts either. After completing this procedure the option to remove the lock screen was still unavailable as I didn't know the password that was set. I was able to backup my device and reset.
Hope this helps
how can you able to unlock when it is locked by ADM??
Same thing with my Galaxy S5. Many, many times of password & pin incorrect over 5 days, 8 hours of phone & online with AT&T and Samsung and in-store visits. Finally, I did Findmymobile again. The unlock feature never did show up on the left side, but I right (I think) clicked on the location when it found my phone and unlocked it. I was so surprised that I didn't even realize my home screen was visible for at least a half minute. It's worth a try, 'cause I did the same stuff as all of you have said without any good results.
This worked!
microi said:
I just had the same problem with a Samsung Galaxy S5. I solved the problem and unlocked my phone. Suggest the following if you locked your phone with a lock pattern:
1) Try the wrong pattern 5 times
2) You will see a message asking if you," Forgot Password"
3) Tap that message and you will be presented with a screen requesting your email and password.
4) Use your Google credentials and you will be able to unlock your phone.
Good luck!
Click to expand...
Click to collapse
I left my device at a Starbucks and didn't realize until I got home. I went into my Google account to change password and found I could locate my locate and lock it so I did. It located the device exactly where I left it - at Stuckbucks. So, I went back in the morning to recover it...with a locked home screen with my message on it. Unable to unlock directly on the device. I went back home to research this on my desktop. Google Account doesn't have unlock device feature so I used the search engine and found this forum. I followed the instructions and bingo, my device is now unlocked! I was about ready to get a new device!
Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
OnePlus will not do anything due to the warranty being void...
DM me. I can work this out with you. I ran into a similar problem.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
Tried sending it for repair but had the op guy look up my imei and ITS A DAMN DEMO PHONE I GUESS!? Cant return it, bought off amazon refurbrished and due to my anger problems i shattered the screen but other than that i shouldnt of been sold a damn demo phone from the start.
T3CHN0T33N said:
OnePlus will not do anything due to the warranty being void...
Click to expand...
Click to collapse
they would repair it, they even repair tmobiles version and metro and all but it really ticked me that amazon refurbrished sold me a demo phone or the phone is now thinking its a demo phone somehow..
Springles2 said:
DM me. I can work this out with you. I ran into a similar problem.
Click to expand...
Click to collapse
Never discuss in DMs! This person has illegitimate intentions.
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
it's not against the rules it's just not a good idea to do
T3CHN0T33N said:
it's not against the rules it's just not a good idea to do
Click to expand...
Click to collapse
Thank you for the advice! Just wanted to see if I could legitimately help!
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
illegitimate intentions, lol what are you trying to say? didnt know my intentions had any type of rules to be followed.
if oneplus sends people on the daily unlock codes in order to unlock their bootloaders on their phones, shouldnt people be able to explore some other OS's and things of that sort? My intentions were to TEST out GSI's that developers worked hard on to work with certain devices and provide some feedback and hopefully come along one that i can use on the device as a daily.
This is Forums, know your place. I think we are all a lil illegitimately intentional at times dont ya think?
no offense.
Springles2 said:
Thank you for the advice! Just wanted to see if I could legitimately help!
Click to expand...
Click to collapse
Thanks for your gratitude.
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
jerryhou85 said:
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
Click to expand...
Click to collapse
Thank you for explaining it to others who might need it
Also, will never ask for anyone’s personal info or financial info or anything to do with their identity. That is their information and have no interest in knowing more than their username on here
Maatt_OG said:
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
Click to expand...
Click to collapse
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Maatt_OG said:
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Click to expand...
Click to collapse
Please write something up on how you did it! It could save someone!
Springles2 said:
Please write something up on how you did it! It could save someone!
Click to expand...
Click to collapse
Well at times it would just bootloop nonstop after using the msmtool, but then tried entering safe mode and that was a success but remembered each time it went to turn on the wifi to set up the phone it would freeze and bootloop no matter what,
So from emergency call find your way into permission manager , from there you can open settings app, disable location and anything that would trigger wifi to turn on , airplane mode is on remember this, you need to turn it off withput having the wifi kick on. Disabling some modem/network apps or that has anything to do with wifi, location, carrier, modem that you can disable, do it. Once you're able to turn airplane mode off successfully you can get passed the wifi part of the phone setup and use your mobile data instead, or what I did is use gnirehtet , you can find it on GitHub. Install on PC, make sure you enable USB debugging and have the default USB config set to USB tether, not hotspot .extract zip to platform tools, Move the apk file from gnirehtet zip to your phone, run the provided command from the zip and you'll get a request to allow debugging on your phone from PC, once you do that. You'll finally be able to update your n200 T-Mobile phone to Android 12 which is the only way I found to do this. Make sure you update to Android 12 and not another android 11 before turning wifi on or anything else or you will have to start ALL OVER. Done it twice it's a pain in the arse
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
I was going to say keep discussion in the open in case any future people come across the same issue. If there's one thing I hate is coming across the same issue as my issue on stack overflow or elsewhere and OP from 7 years ago saying, "Never mind, I figured it out."
Hello all...hoping to get some assistance with this thing. Long story short, debloated it due to horrid battery life and high heat. Everything was great until about a week ago when my settings app go renamed somehow. Tried fixing it but couldn't find the com.android.settings file with the correct signature for my phone (AT&T, US Model, unlocked, not rooted).
It's been working fine except no settings...so I backed up the usual stuff and had plans to do a factory reset this weekend. A few hours ago I picked it up and it went all wonky on me. Upon boot, it comes up to the lock screen and then the screen just starts turning on/off. I'm unable to bring up the passcode screen...but, am able to bring up the power menu by holding the power button. But, can't power down or get into safe mode that way. After about 5 seconds of doing this, it reboots. Rinse and repeat. Safe mode via buttons starts, but, does the same thing.
I am able to get into both recovery mode and download mode though. I can view logs/etc.
Normally, I'd just ***** and moan, then do the factory reset, However, I made one huge oversight when I backed up my data earlier this week and forgot to backup my notes. There's about a dozen of them, pages and pages long with all the medical details regarding my sons illness that I've been tracking for years. It's a nightmare dealing with different Dr's all the time so I've logged it all on the phone. Unfortunately, the best app I've found for it doesn't do cloud storage and keeps them saved as local txt files on the device.
Is there any hope I can somehow pull the files using recovery/download mode or utilize the logs to determine the errors and fix it enough to be able to get them? I'm fairly tech savvy and have ADB installed. I'm super ADD though and my head is just spinning trying to sort through all the possible posts regarding trying to do this...many being for older phones.
Absolute worst case, is there a legitimate service that would be able to do it?
Any help recovering my son's medical notes would be really really appreciated.
RiBBiTeDD said:
Hello all...hoping to get some assistance with this thing. Long story short, debloated it due to horrid battery life and high heat. Everything was great until about a week ago when my settings app go renamed somehow. Tried fixing it but couldn't find the com.android.settings file with the correct signature for my phone (AT&T, US Model, unlocked, not rooted).
It's been working fine except no settings...so I backed up the usual stuff and had plans to do a factory reset this weekend. A few hours ago I picked it up and it went all wonky on me. Upon boot, it comes up to the lock screen and then the screen just starts turning on/off. I'm unable to bring up the passcode screen...but, am able to bring up the power menu by holding the power button. But, can't power down or get into safe mode that way. After about 5 seconds of doing this, it reboots. Rinse and repeat. Safe mode via buttons starts, but, does the same thing.
I am able to get into both recovery mode and download mode though. I can view logs/etc.
Normally, I'd just ***** and moan, then do the factory reset, However, I made one huge oversight when I backed up my data earlier this week and forgot to backup my notes. There's about a dozen of them, pages and pages long with all the medical details regarding my sons illness that I've been tracking for years. It's a nightmare dealing with different Dr's all the time so I've logged it all on the phone. Unfortunately, the best app I've found for it doesn't do cloud storage and keeps them saved as local txt files on the device.
Is there any hope I can somehow pull the files using recovery/download mode or utilize the logs to determine the errors and fix it enough to be able to get them? I'm fairly tech savvy and have ADB installed. I'm super ADD though and my head is just spinning trying to sort through all the possible posts regarding trying to do this...many being for older phones.
Absolute worst case, is there a legitimate service that would be able to do it?
Any help recovering my son's medical notes would be really really appreciated.
Click to expand...
Click to collapse
Man, i'm so sorry to hear that :/
Sience you have access to recovery, did you try to wipe only cache partition and hit repair apps(also in recovery)?
I'm also using debloated device and i dont have any problems with it
nocio said:
Man, i'm so sorry to hear that :/
Sience you have access to recovery, did you try to wipe only cache partition and hit repair apps(also in recovery)?
I'm also using debloated device and i dont have any problems with it
Click to expand...
Click to collapse
Yeah...that's the first thing I tried after safe mode failed. :\
There's quite a few folks reporting similar issues since the last OTA update a couple weeks ago.
Usually I delay until I get a chance to restore then allow it...this one didn't even give me a chance. I was using my phone when it popped up. No option to remind me later. When I tried to exit it counted down from 10, rebooted and installed.
RiBBiTeDD said:
Yeah...that's the first thing I tried after safe mode failed. :\
There's quite a few folks reporting similar issues since the last OTA update a couple weeks ago.
Usually I delay until I get a chance to restore then allow it...this one didn't even give me a chance. I was using my phone when it popped up. No option to remind me later. When I tried to exit it counted down from 10, rebooted and installed.
Click to expand...
Click to collapse
I have one idea, it may seem unusual but it may work.
Try to remove sim card and than boot device
nocio said:
I have one idea, it may seem unusual but it may work.
Try to remove sim card and than boot device
Click to expand...
Click to collapse
Thanks for the idea. But, yeah, tried that to already...cleared cache and repaired apps afterwards too. Tried it with cable, tried a 2.0 cable too.
No dice.
The app repair works just fine and then it does the same thing when lock screen tries to appear.
RiBBiTeDD said:
Thanks for the idea. But, yeah, tried that to already...cleared cache and repaired apps afterwards too. Tried it with cable, tried a 2.0 cable too.
No dice.
The app repair works just fine and then it does the same thing when lock screen tries to appear.
Click to expand...
Click to collapse
Only thing that came to my mind is to download latest firmware for your device than flash it via odin
EDIT: but be carefull with that. Odin have box to untick factory reset but i didnt do that a loooooooooong time so i dont know if something is changed
nocio said:
Only thing that came to my mind is to download latest firmware for your device than flash it via odin
EDIT: but be carefull with that. Odin have box to untick factory reset but i didnt do that a loooooooooong time so i dont know if something is changed
Click to expand...
Click to collapse
Yeah, I figured that'd be my last shot at it... I've read the horror stories of tripping Knox even with factory firmware.
Was just really hoping there was some way to yank the stuff using recovery or download modes.
RiBBiTeDD said:
Yeah, I figured that'd be my last shot at it... I've read the horror stories of tripping Knox even with factory firmware.
Was just really hoping there was some way to yank the stuff using recovery or download modes.
Click to expand...
Click to collapse
I think that you can't trip Knox only when you flash official firmware over unlocked bootloader and custom ROM, but I'm not so sure.
Last time I did that is when I had Samsung Galaxy S2 and flashing official firmware over official firmware and that didn't trip the Knox counter
Does flashing genuine firmware trip knox?
Hi It's been a while since I bothered flashing firmware so I am not upto date with how things work now. My questions are I am currently on 02s version of firmware and would like to go samsungs version so I can take part in things like the one...
forum.xda-developers.com
Here you can see that flashing official firmware over official firmware(i'm guessing that you are not rooted) won't trip knox counter
nocio said:
Does flashing genuine firmware trip knox?
Hi It's been a while since I bothered flashing firmware so I am not upto date with how things work now. My questions are I am currently on 02s version of firmware and would like to go samsungs version so I can take part in things like the one...
forum.xda-developers.com
Here you can see that flashing official firmware over official firmware(i'm guessing that you are not rooted) won't trip knox counter
Click to expand...
Click to collapse
Awesome! Thank you!
I was able to get the files...for others in the same boat, here's a link to what worked for me:
Help finding correct firmware and installing for AT&T SM-G991U.
Hello all...I'm a fellow victim of the OTA updates screwing us debloaters currently stuck in a boot-loop. I'm trying to recover my the past several years text notes containing all the medical details for my son's illness. Details on that can be...
forum.xda-developers.com