[Q] Verizon Moto X Pattern Lock Predicament - Moto X Q&A

Thanks for trying to help guys but he lost the data and worked on re-installing his apps last night. I reported this thread to be removed.

chris23445 said:
So I have a pretty big problem here, and I'm having a ton of trouble finding a proper solution.
My college roommate has a Verizon Moto X, and long story short, he wasn't doing homework and was doing stupid stuff on his phone, so I took it and made a pattern lock for him. I didn't know he was going to try to figure it out, and he wound up trying to unlock it 10 times. After the tenth time, with no prior warning, the phone rebooted. It then proceeded to try to erase his phone. I turned it off and it keeps trying to erase it. I got into the bootloader by holding power and volume down, but is there any way to fix this? I don't think the phone has erased yet, but we're trying to get it to actually boot up. Please help me out if you know a solution. We may have to just let it erase but I really hope we don't have to do that.
Thanks a ton!!!!
EDIT So it just rebooted and it's all gone. Any way to fix it?!?!
Click to expand...
Click to collapse
Its gone.....

Try these solutions,
http://laptapos.com/android/how-to-unlock-android-device-after-too-many-pattern-attempts/
Good chance all your data will be gone tho. That's just how its made to work. I'd never use these unlock things. My kids would definitely mess my phone up. I just don't keep anything sensitive on my phone.

I had no clue that if you entered incorrect info 10 times it would factory reset your phone. Is that automatic or is that just an option?

SymbioticGenius said:
I had no clue that if you entered incorrect info 10 times it would factory reset your phone. Is that automatic or is that just an option?
Click to expand...
Click to collapse
Automatic. Doesn't do that on my Galaxy S4 though.

Related

Returning a bricked phone

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".

[Q] a quick bypass of pattern lock

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
ಠ_ಠ

[Q] What happened to my HTC One?

Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.

Eight days in, and a replacement phone.

8 days ago, I decided my s5 had had enough abuse, and got the z force. It's been an amazing phone, other than the heat, which has always seemed a little warm, but didn't do anything to slow the phone down. Up until today, it's been glitch free, and I loved it.
Until about six hours ago. I wasn't paying attention to the battery, it died in the middle of watching YouTube videos with my kids, so I let it finish powering down, plugged it in, and let it charge. Upon turning the phone back on, I got an error message saying the device failed validation and may not work properly. Five second delay and it powered on, and everything seemed to function normally. Rebooted the device, same screen. Factory reset the device, same screen. I took the phone back to Best Buy and got a replacement, and I'm hoping it doesn't happen again, I really happen to like this phone...but I'm curious. Moto's customer support's first question was if I'd unlocked the bootloader or rooted the device, but being verizon-locked, I'm well aware that isn't possible and haven't attempted it. Anyone have any ideas why my phone just randomly decided to fail the bootloader verification so I can try to avoid replicating this mess?
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Mace68 said:
I'd like to know as well. I have the same message every time it boots but it doesn't seem to affect anything I've noticed so far.
Click to expand...
Click to collapse
If you boot into the bootloader does it say if your device is locked or unlocked?
BladeRunner said:
If you boot into the bootloader does it say if your device is locked or unlocked?
Click to expand...
Click to collapse
No such luck lol. It says "oem_locked" and software status is "Official".
Sent from my XT1650 using XDA-Developers mobile app
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Mace68 said:
I wanted to add that a factory reset didn't clear the message.
I also wonder if it has to do with turning on allow bootloader unlock in dev options. It seemed to have happened at about the same time I turned it on.
Click to expand...
Click to collapse
Factory reset didn't fix mine, either. And as far as turning on the bootloader unlock option...I hadn't even enabled dev options on mine, so I'd assume that's just a coincidence on yours.

Tab a (2017) force oem unlock

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?

Categories

Resources