Database Develop

Help, anyone?

Guys, just got my phone last week. I read a lot about rooting. Should I root my phone? What are the advantages of it? Havent been able to back my phone yet. When I do root, would it wipe out my phone? Should I wait for the release of the ICS or should I just root now? Also, which link should i follow?
Heres my phones spec:
Model Number: GT-N7000
Android Version: 2.3.6
Baseband Version: N7000DXKL2
Kernel version: 2.6.35.7-N7000DXLA1-CL886914
[email protected]#2
Build Number: GINGERBREAD.DXLA1
Please help. I am new to android. thanks!

Its really up to you. If you already satisfy with stock, then just wait for ics. But if you a type of person who could not wait and could not stand with bug on existing stock rom, then go for custom rom. Which ever suit and good for you..my 2 cent.. B-)
Sent from my GT-N7000 using XDA App

Hey, I was in the same boat as you. Dabble with Android, some time back, but left the fold as I thought it hadn't matured enough for me back then. Now I a back - couldn't resist the Note and I find that Android has come along leaps and bounds, more functionality than I could of hoped for. I am glad Im back, and I will be staying
To answer some of your questions,
* Yes root the device (at your own risk of course)
*The advantages are numerous, but to name a few: many apps that can take advantage of your root status, eg Titanuim backup. Once rooted, you can explore different roms (firmwares developed/enhanced by others), kernels etc which can increase the speed, functionality etc of your phone. You make full backup of your phone prior to changing or trying different roms, that way if something goes wrong, you can load your last working copy etc. For example, Im just trying a new/different kernel or a ROM developed by a totally different person. Pretty cool really.
At the end of the day it is entirely up to you, but there is a whole different world out there waiting for you if you go the 'root' path.
Good luck and enjoy..

Vatoe said:
Hey, I was in the same boat as you. Dabble with Android, some time back, but left the fold as I thought it hadn't matured enough for me back then. Now I a back - couldn't resist the Note and I find that Android has come along leaps and bounds, more functionality than I could of hoped for. I am glad Im back, and I will be staying
To answer some of your questions,
* Yes root the device (at your own risk of course)
*The advantages are numerous, but to name a few: many apps that can take advantage of your root status, eg Titanuim backup. Once rooted, you can explore different roms (firmwares developed/enhanced by others), kernels etc which can increase the speed, functionality etc of your phone. You make full backup of your phone prior to changing or trying different roms, that way if something goes wrong, you can load your last working copy etc. For example, Im just trying a new/different kernel or a ROM developed by a totally different person. Pretty cool really.
At the end of the day it is entirely up to you, but there is a whole different world out there waiting for you if you go the 'root' path.
Good luck and enjoy..
Click to expand...
Click to collapse
Thanks for the reply. Can you provide me the links that i need to be able to do the rooting?

No problems. Unfortunately you have one of the newer firmwares which are not directly rootable. All is not lost though, you can still root your phone, it just involves al little more effort on your part. Read the linked post very carefully, following the instructions regarding not directly rootable firmwares:
http://forum.xda-developers.com/showthread.php?t=1424997
Good luck..

ok, thank you very much!

gokenong said:
ok, thank you very much!
Click to expand...
Click to collapse
No problem at all.

Moved to Q&A​
All question in the Q&A section please!​

Root, root, root!
I must say I tried to avoid it and wait for ICS, but the battery drain was giving me grief. Here's why I rooted, and will root evermore:
There are dozens of 'stock' apps that pop up and start chewing through your battery any time they feel like it. The are all small apps, but there are a lot of them, and it really eats into your battery life and RAM.
Even if you kill them off, either with a task killer or manually, they pop right back up again, sometimes within seconds. This is because they have 'listeners' registered with the OS, and they respond to any of these events they have registered to listen for.
I use Autorun Manager to both stop them starting at boot, and to turn off all 'listeners' these apps have in place. My device then only runs what I want it to run!
The other extremely nice thing to have, and one that I find I just cannot do without, is a firewall. I use DroidWall, and it allows me to specify exactly which apps can get access to the internet, and how (by WiFi, Mobile, or both). This gives you battery savings and mobile data savings, and it also provides a certain level of security because malicious apps just cannot send personal information back to base (like they certainly can without a firewall).
I immediately increased battery life by 50%. I have added another 50% by sleeping the WiFi, because I can now specify only WiFi for apps (so they don't jump on mobile data when WiFi is asleep, like they used to, I think).
One happy Rooter!

Hello to OP and the above warm-hearted members
I had similar question and a bit over it. I thought I could add it to this thread instead of making a whole new thread.
During my short days with GNexus, I learned quite a lot of things (my 1st Android Device), for example, the elementary intro to fastboot and adb.
However, after switching to Note, I found there is no fastboot mode? Or at least, pressing volume rockers+power button didn't do the trick. Am I missing something here? Because everytime I search "fastboot mode (or bootloader) and Galaxy Note", all the results turn out to be about Galaxy Nexus...
Really confused..

I don't know if this helps you but since noone has responded I can tell you this.
Holding Volume Up + Home Button + Power Button boots you in Recovery mode where you can install ROMs, kernels and updates, wipe data, cache, dalvik cache, battery stats do factory reset, make nandroid backup and restore and some other stuff.
Holding Volume Down + Home Button + Power Button boots you in download mode where you can connect to Odin and do stuff.

Thanks! So it's quite different when there's an extra physical button
I just tried and it works.
Is the recovery mode the equivalent to fastboot mode?

[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] adb not recognizing device

Hello all, wanting to use ADB to do a backup of my device. Running OSX 10.9, Moto X 4.4.2 VZW, unrooted, stock. I've downloaded the Android SDK, ran it, and updated it; downloaded and installed the Motorola drivers; enabled USB debugging; navigated to adb and can run commands, but when I run adb devices, it does not list my device. Any thoughts?
Thanks!

Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.

KJ said:
Its your drivers. They aren't letting your PC see the phone.
Now, I know nothing of Mac....so not sure what you can do. Except uninstall them completely. Download again and be sure they're the right ones. Also, try another cable perhaps.
Click to expand...
Click to collapse
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.

patheimata said:
The phone is being recognized by the computer. I can transfer data and connect to Android File Transfer, etc. Just isn't being recognized by ADB. I'll try reinstalling the drivers, though.
Click to expand...
Click to collapse
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck

samwathegreat said:
Sometimes adb has issues while booted into android. Try this: Unplug the phone from the usb cable. Power it off.
Now, hold down the VOL DOWN button, and power it back on. You should boot into the bootloader. The screen will say something about "AP Fastboot Mode".
Now, plug the usb cord back in. adb devices should now respond with your connected phone, and your adb commands should work.
May I ask why you are backing up your phone via adb? Or more aptly, what do you plan to do with the backup? With a locked bootloader, there should be no way you will be able to restore whatever backup you plan to make. What am I missing?
Good Luck
Click to expand...
Click to collapse
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...

patheimata said:
Thanks, I had intended to try the bootloader and quite frankly forgot as I got caught up troubleshooting other methods. I'll try that shortly and post results.
Meanwhile, you may be right. I've found lots of conflicting information. At least one person in the Motorola forums claims to have been able to do an adb backup and then restore it on his locked device after a FDR. I need to do one to try to deal with some battery issues. I was trying to find the path of least resistance for backup and restore, although I'm two days into researching this, so I can pretty well say this is no longer the path of least resistance, but I haven't wanted to give up, either, if it's possible...
Click to expand...
Click to collapse
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.

samwathegreat said:
My best advice would be to make a list of all the apps you need, save any pictures or files you need, do FDR, then use the list to re-install your apps, and copy your pictures / files back, and set everything back up the way you want it.
Even if you are able to 'backup via adb', and do a FDR, once you subsequently do your 'restore', you will have the exact same issues you are having now. Battery issues are usually caused by misbehaving apps, but even if you assume the issue is caused by something else, the method you are pursuing is ill-advised.
Ok, so when you do a FDR, it clears the data and cache partitions, essentially returning the device to factory assuming you haven't tried to do root exploits or similar.
If you do a restore, it writes to....(you guessed it!) the data and possibly cache partitions. You'll essentially be right back at square 1 so to speak because -whatever- the problem is, you'll RESTORE it...
EDIT: What kind of battery life are you getting on your X? Can you give us an idea how long it is lasting, and tell us a little about your usage patterns. How much time do you spend on calls, and how much of the time is the screen on?
With what I would consider 'average' usage, I normally get 14~18 hours between charges. This includes very little talk time, but regular internet usage, and usually 1-3 hours of internet radio streaming.
I'm just curious how long yours is lasting between charges.
Click to expand...
Click to collapse
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb backup and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
EDIT (A thought I started and never completed in the original post): I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs, which solved their battery life. In a 31 page thread, I had only seen one user have a FDR actually fix their battery problems, so I haven't exactly been hopeful that it would help mine. In addition to that, since I remember my Dev Edition getting better battery life all things being equal, it does make me wonder if mine is more hardware related than app or software/firmware.

patheimata said:
Absolutely.
First, agreed on the app and cache situation. I was going to exclude apps on the adb and just use it for pictures, settings, text messages, etc., and leave out of the backup would be potentially corrupting it after the FDR. I've used other apps in the past to back those things up, but the promise of adb seemed easier (and more fun), thus going that route. I think I've thrown in the towel on that plan at this point, but it has been a good learning experience as I learned a lot commands and troubleshooting methods in that department.
As far as battery life goes, I've had two devices. Started with a dev edition, and while I had that, I was really impressed that it would make it all day long and still have some battery leftover at the end of the day. I exchanged it for a MotoMaker edition, though. I'm not sure I ever remember this one getting as good as battery life as the other, although it's been 5 months, so it's hard to tell. Nevertheless, 18 hours would be fantastic for me.
GSAM says my average fully charged battery lasts 14 hours, with 7 hours and 4 minutes active time. That sounds pretty on par with you, but looking at the charts, I believe they're projecting from 100%–0% as I wouldn't say I typically make it from 100%–20%, which is when I always try to recharge by. The 7 hours active is where I assume my problem lies, and thus the desire to try an FDR. I use my phone a lot, but I'm not active on it for over 7 hours a day. GSAM says my average screen on time is 2h 8min, max of 2h 33min. (These averages are over a 2 month period.) In light of that, I'm regularly charging midday to make sure I can make it through the end of the night.
Regular usage patterns include very little by way of voice calling. I felt like I was on the phone a lot today, that was probably no more than 10–15 minutes. Most of the rest of the SOT time split between texting and internet/light app usage.
Android OS is of course the far and away process consuming battery, which I realize tells us nothing and isn't that uncommon, especially when the phone isn't in use.
Over the past few months, I've tried isolating the typical likely suspects (Facebook and Facebook Messenger, Google+, location services, etc.), uninstalling them, and looking for battery improvements to no avail. The only time I ever really saw a direct correlation with a particular app that I could trace has been with Google Camera. I haven't reinstalled it since they're most recent update, but while it was installed, after it's first update I dropped to about 6–8 hours of battery life.
I've also participated a good amount in this forum on the issue: https://forums.motorola.com/posts/6675cef7e3?page=31 which also happens to be where I read of user jason.motox's experience backing and and restoring with adb.
Alright, I think that's a good start from there. Would love anyone's thoughts on best practices, etc. As much as I hate the thought of adding a few apps at a time every few days, I know that's the best way to go to ensure it's not an app. But anything else that anyone else is aware of to watch out for would be useful. Also happy to post a list of currently installed apps if that would be useful.
I have read in the Motorola forums of at least one user eventually having the cellular radio replaced in theirs
Click to expand...
Click to collapse
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course

samwathegreat said:
Who is your carrier? Are you rooted, or are you able to unlock your BL? There is a root app called "Greenify" that many people swear by. It helps identify potential 'problem apps', and actually allows you to 'hibernate' them.
This basically 'hides' the app from the system completely, but you don't notice. When you explicitly launch the app it functions 100% normally, but a short time after you exit it, it gets hibernated again so it can't suck any power.
If you are rooted, or if you may consider unlocking, I would suggest giving Greenify a try. It always sucks to have to charge mid-day.
Also remember that even if moto won't unlock your BL, the gentleman from China will...for a small fee of course
Click to expand...
Click to collapse
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...

patheimata said:
Sadly I'm a Verizon user, and since I didn't keep my Dev Edition, my bootloader is locked down hard core. I'd love to use Greenify. Had it on my GNex (speaking of atrocious battery life!), but no such luck here. I've contemplated unlocking and rooting, but I have read a lot of horror stories of OTA updates with the X for those who are unlocked and/or rooted and just didn't want to deal with all that. In moments like these, though, it makes me want to send a few bucks to that Chinese gentleman...
Click to expand...
Click to collapse
There are just a few caveats to being unlocked:
If a new OTA comes out, it is recommended to return to stock before accepting the OTA. This is because OTAs include a "manifest" of the files that SHOULD be present on the device, along with their checksums. A modified device often won't match the manifest.
Don't let this scare you though. We may not be updated past 4.4.2 heck, 4.4.3 hasn't been released on anything yet. And if we do get another OTA, you can SBF back to stock, take the update, and then re-install everything.
In my humble opinion, the ability to use root apps (especially TETHER) is much more important to me that the minor inconvenience of possibly having to set everything back up again in the future.
If you're considering it, I recommend you take the plunge. You will get your money back if he doesn't have your code. I was able to unlock my device using the China method this 2nd time around and my device is from Nov 2013 - he still had my code. So there ARE some 2013 models in his database for sure....or I wouldn't have gotten one.
If you suspect this is a hardware problem, unlocking is ill-advised as your warranty will be void. Even if you re-lock the bootloader, it will never show "LOCKED" - it will say "RE-LOCKED" instead......and they will know you had unlocked it.
Good Luck

HELP : Phone asking for PIN instead of Fingerprints after MarshMallow update.

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.

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?