Related
Hi.
Im sorry for the lackluster thread, im kinda in a hurry having my sister in law over who lost 1k photos by pressing something she doesnt remember.
I think its been resetting the phone.
Its running kitkat so its mtp which makes accessing the memory hard.
Is there a way to recover the phones, maybe rooting it (which i think that i can manage to do but i fear to overwrite the data doing it) it?
thx!
If she reset the phone and wiped the memory, then you are out of luck...
But maybe, you can take a look at EASEUS: http://www.easeus.com/mac/mac-data-recovery-resource/photo-recovery-freeware/free-recover-photo-from-android-phone.htm
Thank you so far!
After unlocking and rooting it seems to work, it found some icons and its working and working...i know how long it can take.
Now she has to go home and ill try another day but it made me optimistic to get the icons, so maybe the factory reset didnt delete the pictures.
it's possible, however, a long and complex process. I would only recommend to do it if the info you lose is really important.
cuyo11 said:
it's possible, however, a long and complex process. I would only recommend to do it if the info you lose is really important.
Click to expand...
Click to collapse
It is about 1000 (she said, i think its about 500^^) children photos so yes, it is worth all the work i guess.
Im going to try again later this evening, so far i rooted the phone and the software had first results but we didnt have time to finish.
If anybody comes up with another great idea im totally open, whilling and skilled enough to do about anything but i think that the worst part will be the hours its gonna take to find and then rescure all the data, this time i can say goodbye and they let it work over night
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.
Something really strange happened to my father's Turbo. He got it brand new from Verizon about a month ago and I sat down and updated up to .44. I told him that if another update comes in, do not touch it because I was going to unlock it with Sunshine and root it. I don't allow him to do updates on anything, I do it for him when I know the bugs won't screw anything up and flash it myself.
I was ready to unlock the phone and when I looked About Phone, I saw it was on .49. So I checked a little more and found the exact date and time it updated (July 23rd, 7:23PM). The date and time coincided with his being in the hospital and I had possession of the phone. The phone was sitting in my room (there's no one else around to mess with things), undisturbed for a week. I never saw the .49 update show up before I left it alone--and I checked it to make sure he didn't accidentally update it, just in case. I know on my Turbo, it was annoying as all get out and I dealt with the nag screens for a week or so until I could buy the Sunshine app.
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
pearlheartgtr said:
Is it possible Verizon is now forcing the .49 update? I know there's no way possible that either, I or my father, allowed this update to happen.
Click to expand...
Click to collapse
Others have claimed that with some people being very skeptical. I would not put it past Verizon. Is it possible if you totally ignored the nag screens Verizon takes that as a yes?
Thing is, the update and nags never showed up in the first place for it to be accepted or ignored. It just happened.
My phone auto-updated while I was sleeping one night. I was thinking of unlocking the bootloader. Oh well.
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconeted a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
mt021322 said:
lastnight that's update come to my turbo,.luckily that's happen when the phone on my hand,so i'm disconnected a mobile data ..
but now i'm stuck on no mobile data or wifi cause i'm afraid when i'm turn it on,the updates get installed
Click to expand...
Click to collapse
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.
(Wow, that's quite a cracked screen!)
Can you boot into recovery and clear cache? Would that clear the downloaded update files from the phone?
Of course, first chance -- after you stop the SUTL-49 update -- you get go ahead and unlock the bootloader already! Then you don't have to worry about it anymore.[/QUOTE]
yups,,for a first time the progress still there,,but after I'm trying to root a phone using vroot (via pc) and kingroot,specially by vroot cause this process makes turbo reboot a couple time (with a failed result :silly,.now on the second time on wipe cache,the progress is gone ( it's a temporary right?it's will coming again on a mysterius time :silly i'm use Gsm/Edge for a connectivity to make a slow downloading update progress when is coming back
.
a money problems for this time to buy that license
I, too, would probably resist unlocking that particular device, since the screen is so cracked up... if you replace the phone, you'd have to get another Sunshine license for the new device.
Anyway, back to the original point, I recall on my old GalaxyS3, VZ was pushing an update that only allowed you to postpone it for some specific amount of time and/or it had a timer for the "we're going to start installing" popup, after which it would force-install. Based on that, I wouldn't be surprised to hear VZ is forcing updates, especially on an unattended phone...
There may be hope...
http://forum.xda-developers.com/droid-turbo/general/sunshine-bootloader-unlock-su4tl-49-t3445523
while collecting a money,i'm try freezing updater using adguard.apk (non root) and the result for a last two days,the update progress is gone (I don't know if that's a result from a adguard method)..
The old user of my phone said that. The .49 update was made automatically, with no Yes/No options, just updated.
I think it might be that if you don't interact with the prompt it will update your phone after a certain amount of time. When the update first rolled out I would always postpone it, telling it to remind me at 12AM cause that's when I usually go to bed. However one day, after setting it to remind me at 12, I fell asleep earlier and didn't see the prompt. The next morning, surprise, surprise, it was updated to .49.
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
jcase said:
We just released it, 3.4.6 will unlock SunShine
Sometimes stars align and a bug becomes apparent, one that we can use.
Click to expand...
Click to collapse
ChazzMatt said:
Good news!
Sunshine will now unlock bootloader on Verizon SUTL-49 on the Droid Turbo XT1254:
http://forum.xda-developers.com/showpost.php?p=68384014&postcount=21
Click to expand...
Click to collapse
It is a great news for a lot of people.
Good work by Sunshine team.
In the future with any phone. If you see a update is about to happen, plug your phone to your computer, go to root of storage, and delete the download.. Hell I do this all the time... You can't miss it, it will be the only white looking item there..
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?
Hi there community,
revolted because of battery life on my pixel (pixel 4 xl) I did few moments ago hard reset, to give it a try. Battery level droped ca. 45% in few hours doing nothing ( I don't have any new apps or somethig new on phone) During this initial setup, I was wondering should we restore our backups 1-1, will this just give us our problem back, or somehow this will be avoided? (to be clear, I am not thinking that HardReset will 100% resolve the problem, just want to give it a try)
I hope you understood my dilemma and my english
¯\_(ツ)_/¯
100kaa said:
Hi there community,
revolted because of battery life on my pixel (pixel 4 xl) I did few moments ago hard reset, to give it a try. Battery level droped ca. 45% in few hours doing nothing ( I don't have any new apps or somethig new on phone) During this initial setup, I was wondering should we restore our backups 1-1, will this just give us our problem back, or somehow this will be avoided? (to be clear, I am not thinking that HardReset will 100% resolve the problem, just want to give it a try)...
Click to expand...
Click to collapse
If you mean allow Google backup to restore your apps then YES, it is perfectly safe (and a big time saver). You may have to reset again to get that option. In my experience, once you use the phone and start setting it up, the restore option is not offered again. If you are talking about another type of backup like Titanium Backup, then you would allow Google to restore first and then run TiBu afterwards to restore your remaining user apps. As far as battery performance there are many ways to track down the culprit(s), BUT a fresh start is always a good thing for phone performance and stability. Best of luck! :good:
@v12xke
Thank You for Your clear response. I did restored the apps from the google one, but I thought it would be possible to restore settings also (e.g. app folders and their position, ringtone, widgets and similar).
Maybe now is not such a big deal, I have started from beginning, but is this possible for the future and if it is, should it be done?
and I will check TiBa, thanks once again.
100kaa said:
@v12xke
Thank You for Your clear response. I did restored the apps from the google one, but I thought it would be possible to restore settings also (e.g. app folders and their position, ringtone, widgets and similar).
Maybe now is not such a big deal, I have started from beginning, but is this possible for the future and if it is, should it be done?and I will check TiBa, thanks once again.
Click to expand...
Click to collapse
You're welcome. I use a combination of Google backup, Titanium Backup (requires root) and Nova Launcher. Nova allows you to backup all your home screen(s) icon locations and widgets. Google restore first, TiBu all the remaining apps, and then restore a recent Nova backup will get me back to 95% of where I was. App settings (and notifications) require a bit more time. As for how long between resets? I usually only reset on a major release 9->10->11, but sometimes things just happen and you either live with it, or reset. Hopefully this reset will allow you to find the app(s) causing the battery drain. Next time boot into safe mode first and try to duplicate the battery drain. If the battery is performing normally in safe mode, one of your apps is causing the problem and you have a smaller problem to deal with. in finding it. Best of luck. :good:
@v12xke
Hey thanks once again. I am sooo unfamiliar with Root and benefits from rooting the phone, it's a nuclear since for me. I bought Nova Launcher but I could not find how to enable "at glance" so I will wait for a bit, just to get bored with this launcher, I think it won't take a lot of time. And just to share, battery is much better today. I have 62% and its almost 12 hours as I disconnected it from the charger.
If you could share with me few links with benefits of rooting or some useful links, I would appreciate it so much.
100kaa said:
@v12xke
Hey thanks once again. I am sooo unfamiliar with Root and benefits from rooting the phone, it's a nuclear since for me. I bought Nova Launcher but I could not find how to enable "at glance" so I will wait for a bit, just to get bored with this launcher, I think it won't take a lot of time. And just to share, battery is much better today. I have 62% and its almost 12 hours as I disconnected it from the charger.
If you could share with me few links with benefits of rooting or some useful links, I would appreciate it so much.
Click to expand...
Click to collapse
The ability to root is the primary reason I have stayed with Google phones over the past 10+ years. There are many advantages, but the ability to flash firmware (stock or custom) strong ad blocking and the ability to backup offline are a few. I also refuse to be locked out of something I paid for. First you should verify your variant is one that CAN be unlocked. Not all Google phones are unlocked. Where did you buy your phone? If you did not purchase an unlocked phone directly from Google, your phone may be bootloader locked and you will not be able to root even if you wanted to. First, enable developer settings and verify whether the toggle to allow OEM unlocking is NOT grayed out or locked. If you are able to toggle this setting, your bootloader can be unlocked and the phone can be rooted. Note: it is perfectly safe to toggle this setting even if you never intend to root your phone, so feel free to enable if you can. If for some reason you cannot change this setting, your phone has been bootloader locked. Step 2: Determine if the phone is carrier locked which is different from bootloader locked. Do you know if you are tied to using one carrier, or do you know for a fact you can use a SIM from another carrier? Have you tested this already? If not, borrow a SIM from a different carrier and try it. Knowing whether your phone is carrier locked is important, because if your phone is carrier locked, you may still be able to get it unlocked.
@v12xke
Thank you very much for your time and patience. I am able to unlock OEM (and i did it ) regarding the carrier lock, it's unlocked, I am using e-sim from T-Mobile and when visit other countries, I use sim card from other carrier/country and its working.
You have started my curiosity, I would like to give it a try, can you please point me at some good tutorial and will it be ok that I send you some questions if something pops out
thank you very much
100kaa said:
@v12xke
Thank you very much for your time and patience. I am able to unlock OEM (and i did it ) regarding the carrier lock, it's unlocked, I am using e-sim from T-Mobile and when visit other countries, I use sim card from other carrier/country and its working.
You have started my curiosity, I would like to give it a try, can you please point me at some good tutorial and will it be ok that I send you some questions if something pops out
thank you very much
Click to expand...
Click to collapse
You're welcome, and you're lucky to have an unlocked version. My son does not root, but his bootloader is unlocked anyway just in case something happens we can always get it back to stock. The next step I would suggest is to download, install and test the fastboot/adb tools. It is the command line interface that enables you to push/pull files to and from your phone (and unlock the phone). Very simply you d/l the zipfile and extract into a dedicated folder (eg. adb). It makes it easier if you add that folder to your path statement, but this is not a requirement. There are many tutorials on how to install these basic binaries (as opposed to the entire SDK which you don't need). Once you can use the fastboot command "fastboot devices" and get a response from the phone you are ready for unlocking. You can find one of the exhaustive, step-by-step, and well written guide HERE. Lots of time and effort went into that guide by @Homeboy76. :good: Best of luck, and remember even if you decide not to root that's ok, but at least your bootloader will be unlocked and you will have learned some basic fastboot/adb commands. The best time to install and learn the basics is BEFORE you have a problem.