I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..
Three days ago?
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.
capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.
so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?
Related
So, I have successfully bricked my phone (not by choice). I am a long time WinMo user and I have never even come close to bricking a phone. Today was exactly one week from when I bought my first android phone and I bricked it.(not blaming android, I love android)
I have tried EVERYTHING, to no avail.
My phone is on the phone++!++computer screen.
So, first thing tomorrow morning, I am headed to the AT&T store for replacement (I will act dumb and get the phone).
My questions are -
1.Will my information (contacts,emails,etc.) on the phone be checked or in any way violated?
2.If they do find out that I had rooted the phone, after I have already walked out of the store, can they do anything about it?
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
TehDave said:
1: Yes, the contacts and all other data on the phone itself is still there, and will all still be there when Samsung / AT&T *un-bricks* the phone.
2: They "could", but I am not knowledgable enough to know if they "will".
Or, save yourself the hassle, and the negative moral karma, and read here:
forum.xda-developers.com/showthread.php?t=731989
I've intentionally (with much failure), tried to "break" the phone so that I'd know how to fix it.
The above linked post will not only recover you from your "phone++!++computer" issue, but actually works so far as the dreaded "orange hex dump".
Click to expand...
Click to collapse
I have tried everything. I don't want to return this phone, but there is no option left.
None of the methods work and I am pretty experienced in this stuff. So, its not that I am messing up on the methods, its just that there was a batch of phones that had the key combos disabled.
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
I can tell you that by flashing ONLY the pit file in odin another user and myself were able to succesfully make the phone unresponsive to all buttons, all methods and all pulls of the battery. it literally turned into a brick...then again i would call this an illegitimate method after realized how simple it is now. as long as i can get power to the phone thou i have to agree ive been able to save it every time now
ukulele_ninja said:
Once you get the new phone there is nothing they can do because they have already agreed to replace it. All they do with it is send it off to be refurbished and it is completely wiped clean. I agree with the others that you have not tried *everything* because I have yet to read a post on any forum about a legitimate bricking of this phone.
Click to expand...
Click to collapse
Seriously?
I was up for six hours last night trying to fix the damn thing. I don't want to replace the phone just because I want to beat the system. I have never ran into problems when I am modding. I always figure it out, but when the phone is absolutely unresponsive to all keys, what am I going to do?
Anyways, this thread can be closed now.
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
seems pretty complicated to flash this phone. My last one-Nokia N900- is very easy to work with. It never get bricked.
alec5216 said:
That same screen (http://img228.imageshack.us/img228/8420/hum1e0.jpg) happened to me yesterday. I thought I had tried all of the key combos but I missed one.
Try the following: (I know you said you tried all of the methods, but I thought it was worth mentioning just in case)
http://forum.xda-developers.com/showthread.php?t=731989 (Method 3)
I hope if you have not tried that yet, that it will work for you and save you the hassle of going to ATT.
Alec5216
Click to expand...
Click to collapse
I tried that too, nothing. I got it exchanged. No hassle.
AT&T store rep just said the phone will be factory reset and there is nothing to it.
Anyway thanks for the help folks, really appreciate it.
Lets hope, I don't bust this one because the phone I just got is also impervious to key combos. I tried getting into recovery (just for the heck of it), it didnt work with the keys, had to do it with "adb reboot recovery".
Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.
blazerphoenix said:
Recently my BFF thinks that her boyfriend is starting to lose feeling for her and start finding other girls. She wants to break up but her boyfriend won't let her go unless she provides evidence that he is losing feeling/cheating on her. She asked me to help but I'm at a loss except for one idea.
It was recently reported in the newspapers that you could bypass all security by freezing an android phone for an hour, then quickly removing the battery and putting it back on and turning it on while it was still below -10 degrees celcius. Is this really possible?
Secondly, his phone is a Galaxy Mini with whatever is the newest firmware (I'm a galaxy Mini II user so I'm not too sure), stock kernel, stock ROM, non-rooted but bootloader i think by default it's unlocked in SG. (mine came unlocked). It's been in use for quite some time only.
If the freezing is not possible, could we do it by any other method? note: before i can get pass the damn password i can't turn adb, unknown sources or debugging on.
Yeah that's all. Also, we can't wipe the /data since that's what we're gunning for. The method must be accomplish-able within 2 hours.
I might sound like I'm asking for a lot and might be unreasonable but please help.
Thanks in advance.
P.S. Please don't talk about the "just break up" or "politely ask him". If that had worked I wouldn't be asking here. He refuses to break up and he refuses to give his phone to me, even to "play". so called ethical hacking through the human link doesn't work anymore. We plan to take his phone for a while, bypass the pattern lock, then sieve through information.
Click to expand...
Click to collapse
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.
F4uzan said:
ADB isn't on, well i think somehow exploit might work. Search around XDA there are some tutorials here.
Click to expand...
Click to collapse
Erm sorry i'm not sure what do you mean by exploits. I'm sorry I'm kinda new to all these stuff.
How do u know that the phone is not "Debugging On"
Most android users are turning on that feature.
Well if the Debugging is ON ... I got the way to unlock the pattern within 1 minute.
Fastest way to bypass: Wipe data. If you can't, there are only harder ways.
Factory reset
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.
Generalil said:
You can always do a factory reset to remove the lock but it will wipe /data. You can still do that tho. It's explained here : http://www.hard-reset.com/samsung-gt-s5570-galaxy-mini-hard-reset.html . Also the fastboot mode works with adb swell as download mode.
Click to expand...
Click to collapse
Mini doesn't have fastboot. It only have Recovery, and Download Mode (don't tell me about normal boot).
My mistake ;P A habit from LG-GT540
ಠ_ಠ
Hi!
Yesterday my phone beeped telling me there was and Android update available, around 198MB
it came from this
dropbox.. com/s/kek0lyolyzdrjhj/2014-10-17%2020.16.39.png?dl=0
To this
dropbox.. com/s/zh92wxumigfe00e/2014-10-17%2020.38.32.png?dl=0
Everything was ok for some hours until hell broke loose
The screen will have a bad time turning on. I press the button several times with no response.
The phone is lagged as my grandpa in his grave. Apps close and even transition from one screen to the other is everything but impossible.
But, when I reboot it, it's ok for as long as I'm using it. If I lock the screen and let it aside for a while, the problems come back
No app updates in the meantime. It went from smooth to horrendous in the period of 4 or 5 hours. I didn't use it much in there, but I doubt it was malfunctioning like this
Special apps I have are Greenify pro, MinGuard (I think that's the name), SuperUser and I rooted it with Towelroot long ago
Any help will be appreciated
marioho said:
Hi!
Yesterday my phone beeped telling me there was and Android update available, around 198MB
it came from this
dropbox.. com/s/kek0lyolyzdrjhj/2014-10-17%2020.16.39.png?dl=0
To this
dropbox.. com/s/zh92wxumigfe00e/2014-10-17%2020.38.32.png?dl=0
Everything was ok for some hours until hell broke loose
The screen will have a bad time turning on. I press the button several times with no response.
The phone is lagged as my grandpa in his grave. Apps close and even transition from one screen to the other is everything but impossible.
But, when I reboot it, it's ok for as long as I'm using it. If I lock the screen and let it aside for a while, the problems come back
No app updates in the meantime. It went from smooth to horrendous in the period of 4 or 5 hours. I didn't use it much in there, but I doubt it was malfunctioning like this
Special apps I have are Greenify pro, MinGuard (I think that's the name), SuperUser and I rooted it with Towelroot long ago
Any help will be appreciated
Click to expand...
Click to collapse
If it was a factory update I'm willing to bet you lost root along with busybox. If so, TowelRoot will probably not work this time. There's another root exploit available called PurpleDrake.
shinobisoft said:
If it was a factory update I'm willing to bet you lost root along with busybox. If so, TowelRoot will probably not work this time. There's another root exploit available called PurpleDrake.
Click to expand...
Click to collapse
Thank you! I did it, re-rooted it following the instructions (indeed it looked like I'd lost my root) but the problem is not solved.
It's just a hunch, but seems to me that changing the Launcher smoothes things up. I was using Google Now Launcher and switched to both LG stock one and Solo Launcher and it seems to be ok.
I'll update the post in a few minutes to clarify it further. It could be that just those few minutes of usage after a reboot are smooth, as I stated in OP. Nevertheless, as soon as I change the launcher, the phone behaves better
Any hints? Google launcher version in Play Store is from August 1st here
Edit: bah, no luck. Same ****, regardless of the chosen launcher.
What do I do now? Try to downgrade it?
marioho said:
Thank you! I did it, re-rooted it following the instructions (indeed it looked like I'd lost my root) but the problem is not solved.
It's just a hunch, but seems to me that changing the Launcher smoothes things up. I was using Google Now Launcher and switched to both LG stock one and Solo Launcher and it seems to be ok.
I'll update the post in a few minutes to clarify it further. It could be that just those few minutes of usage after a reboot are smooth, as I stated in OP. Nevertheless, as soon as I change the launcher, the phone behaves better
Any hints? Google launcher version in Play Store is from August 1st here
Edit: bah, no luck. Same ****, regardless of the chosen launcher.
What do I do now? Try to downgrade it?
Click to expand...
Click to collapse
Wait a minute. I remember some issues changing from Quarx ROM back to stock. I walked someone else thru this once before. Lemme see if I can find that post. Otherwise I'll have to go back to stock, which isn't a problem but I'd rather not if I can avoid it. LOL.
shinobisoft said:
Wait a minute. I remember some issues changing from Quarx ROM back to stock. I walked someone else thru this once before. Lemme see if I can find that post. Otherwise I'll have to go back to stock, which isn't a problem but I'd rather not if I can avoid it. LOL.
Click to expand...
Click to collapse
There's a special place in Heaven for people like you.
It's probably clear by now, but I'm using stock rom here. I grabbed the phone in its early days, when this sub was crawling its way to glory, and we didn't even have a Recovery by that time. Since I was mostly ok with Stock, never minded doing anything special other than rooting it.
marioho said:
There's a special place in Heaven for people like you.
It's probably clear by now, but I'm using stock rom here. I grabbed the phone in its early days, when this sub was crawling its way to glory, and we didn't even have a Recovery by that time. Since I was mostly ok with Stock, never minded doing anything special other than rooting it.
Click to expand...
Click to collapse
LOL. Thanks
Here's the post.
Let me know if that does the trick.
---------- Post added at 03:42 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention, the code listed to activate LG's hidden menu is for the D415 variant.
Code:
3845#*XXX#
Change the XXX to your device model number, ie, 400, 405, 410, 415
shinobisoft said:
LOL. Thanks
Here's the post.
Let me know if that does the trick.
---------- Post added at 03:42 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention, the code listed to activate LG's hidden menu is for the D415 variant.
Code:
3845#*XXX#
Change the XXX to your device model number, ie, 400, 405, 410, 415
Click to expand...
Click to collapse
Haha I noticed that. Mine is 410 (LGD410HN, to be more precise, according to lg-firmware-rom.com).
I followed the instructions. This is what I saw: dropbox. com/s/6h721axufevchjw/2014-10-18%2019.42.10.png?dl=0
I'll update the post in a few minutes with the outcome. As far as I can see, though, things seem to be the same.
Just rebooted the phone, so it takes a few minutes for it to get sluggish.
Edit: Yeah, same thing.
It's another hunch, but every now and then pops up a message saying that a certain google process or app stopped working. Yesterday's update did have a pack of Google updates, IIRC.
Check greenified apps. Maybe it's trying greenify any system or normal app and Android it's trying wake it. Same problem here time ago
Kowalzki said:
Check greenified apps. Maybe it's trying greenify any system or normal app and Android it's trying wake it. Same problem here time ago
Click to expand...
Click to collapse
It makes sense if you take in account that the problem starts a few minutes after the phone sits idle.
I opened Greenify and there was this orange popup
dropbox. com/s/qkxeb850esfkxuo/2014-10-18%2020.40.57.png?dl=0
I disabled the auto-hibernate featuer now and unchecked the google apps that were on the list (Play Music; Play Books, Play Games, Remote Access - i think). But I didn't add any app since the update yesterday and the phone was running smooth since the last time I checked a few more, wich happened weeks ago.
I've got no clue about what may be causing the auto-hibernation problem that Greenify notes (the picture above).
I'll only be able to state for sure in a few minutes, but seems to me that the problem persists.
marioho said:
It makes sense if you take in account that the problem starts a few minutes after the phone sits idle.
I opened Greenify and there was this orange popup
dropbox. com/s/qkxeb850esfkxuo/2014-10-18%2020.40.57.png?dl=0
I disabled the auto-hibernate featuer now and unchecked the google apps that were on the list (Play Music; Play Books, Play Games, Remote Access - i think). But I didn't add any app since the update yesterday and the phone was running smooth since the last time I checked a few more, wich happened weeks ago.
I've got no clue about what may be causing the auto-hibernation problem that Greenify notes (the picture above).
I'll only be able to state for sure in a few minutes, but seems to me that the problem persists.
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, the only other suggestion I have, mainly because of the app updates, is to wipe cache and Dalvik cache and then reboot the device.
shinobisoft said:
Do you have a custom recovery installed? If so, the only other suggestion I have, mainly because of the app updates, is to wipe cache and Dalvik cache and then reboot the device.
Click to expand...
Click to collapse
No, I don't, but I'll try to install one right now.
If it doesn't work, will downgrade be the only option?
marioho said:
No, I don't, but I'll try to install one right now.
If it doesn't work, will downgrade be the only option?
Click to expand...
Click to collapse
That's what it's sounding like. I hate to say that because the only way to downgrade is to flash a KDZ. Unless someone has made a flashable zip of your stock ROM.
shinobisoft said:
That's what it's sounding like. I hate to say that because the only way to downgrade is to flash a KDZ. Unless someone has made a flashable zip of your stock ROM.
Click to expand...
Click to collapse
It's been ages since I last meddled with KDZ-ish things... I guess the "hate to say" part is because it will wipe all data from my phone, right?
I installed CWM and wiped cache and Dalvik. It asked to fix my root, I chose 'yes' and rebooted. After the phone took its sweet time to update apps, I was gifted with this popup message after normally unlocking the screen:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
It's the same error message I've been receiving constantly for a while now, as I stated before.
And, yes, things seem to be the same broken s**t as before.
Gosh, what a headache!
marioho said:
It's been ages since I last meddled with KDZ-ish things... I guess the "hate to say" part is because it will wipe all data from my phone, right?
I installed CWM and wiped cache and Dalvik. It asked to fix my root, I chose 'yes' and rebooted. After the phone took its sweet time to update apps, I was gifted with this popup message after normally unlocking the screen:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
It's the same error message I've been receiving constantly for a while now, as I stated before.
And, yes, things seem to be the same broken s**t as before.
Gosh, what a headache!
Click to expand...
Click to collapse
Unfortunately, you cannot just reflash GApps on stock like we can on custom ROMs. As for CWM asking to fix root, this generally isn't needed. So selecting "No" wouldn't hurt.
Well my friend, I'm fresh outta ideas. This may be the first issue that I've not had a fix for. LOL. Sorry. I really hate it when I can't help someone resolve an issue. It's the perfectionist in me, LOL.
Your help and almost instantaneous replies made it. I appreciate, trust me.
I'll search for that old post with LG tool and kdz files and do the deed in a few minutes. I'll update the topic and deem it Solved when I'm finished
Thank you, again
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Login into this website using your Samsung account
findmymobile.samsung.com/mindex.jsp
Find "Unlock my device" section
And make sure your device is connected to the internet then unlock you device
GreenXSI said:
Hi,
I'm in need of help urgently!
Last week I had updated my Note 5 to MarshMallow and it was working fine. I remember the phone had never been off or restarted after the update until today when the battery ran out. Connected to charger and when I turned on the mobile it showed this message :
"Enter PIN instead of using fingerprint recognition after restarting device to protect fingerprints"
Now I've been unlocking screen using fingerprints from the time I got this phone. Unfortunately, I forgot the PIN and now I can't use fingerprints to unlock the screen. After a few failed attempts the wait time keeps increasing and now it has reached 30 minutes.
Is there anyway I can unlock my phone?
Please help ASAP!
Click to expand...
Click to collapse
On the MM build, after a reboot you have to use the pin but subsequent times will be fingerprint, I have no idea why they did this. Sorry that happened to you, I have no idea how to get around that other than to keep searching, someone else had had that happen I'm sure.
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Douglas333 said:
Yep, I'm screwed, too...
I even kept a list of every iteration of PIN numbers I would ever use (they are generated by an algorithm). I have tried every one - and I am still locked out - with 60 minutes in between tries!
I have very, very important legal documents, notes, and recordings on my phone that I didn't get to backup yet. Unfortunately, most backups do not "dig" well enough under App directories to get all files generated by all Apps. So sad...
And "No", I can't access any sdcard or SIM bc it's an S6 edge+, and they are all locked into the case! The supposed Samsung "unlock" feature does not work, though it says it does.
Dying here! HELP...
Click to expand...
Click to collapse
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Rats! Catch 22...
MrMike2182 said:
You're screwed really and this is why a lot of devs on here say to make backups! Your only option at this point is a firmware reinstall..
Click to expand...
Click to collapse
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Douglas333 said:
But without root, I can't find a backup that will catch all the files well nested under App directories. With root, there are too many "gotchas" nowadays.
Besides, I know I have tried every PIN I would have ever set - so this MM "PIN" is a joke! There should have been a warning, as this is a serious disruption of service.
Wiping is just not an option - I have files created Friday, before the Upgrade, which would not have gotten backed up anyway. Besides, No update should block data access. One of you Gurus can't think of a workaround or push Samsung or Google for a fix? I'm thinking more like "Class Action Lawsuit" for disrupting normal access to my data and my lawsuit...
Anyone else that pissed?
Click to expand...
Click to collapse
You need to learn to "manually" back your stuff up yourself and don't rely on any programs/apps to do it...
There's seriously nothing the dev community could do because for 1 it's not the right way to go about this because if someone's phone is stolen or whatever basically they'd be able to come to XDA-Developers and find a way around the phone being locked for 2 that's definitely not what devs do, we don't look for ways to break into a phone or circumvent the security. You should have backed up anything you knew was important, simple as that .. You need to factory reset at this point. Sorry.
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)
aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.
So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.