[Q] Rooting Question - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Does anyone know if there is a more updated way or (cant think of the word for it) rooting a Samsung Galaxy SIII SGH I747? I've wanted to do it for months and months, but I was terrified of screwing something up, and when I finally over came my fear and heavily prepared, researching and everything ( different technique and all) none of them of them worked. I tried toolkits, XDA troubleshooting tips, all kinds of links and etc. I only get so far in the process where there is a quick flash of some sort in the Odin portion where you input the path from the C: drive part and stuff. I've just had so many issues. I feel like giving up so bad. But I'm not that type of person. I'M GOING tO GET THIS IF IT KILLS ME! Yesterday, I stayed on this thing from 9:00 am till 10:00 pm. Trying over and over, recapping my steps, making sure I read and reread the directions, jumping from site to site to see what other folks have tried.

I think I used quickroot method. I tried the toolkit before and it didn't work either. I finally found a correct root method in the i747 Android Development forum. Ill try to find the forum for you.
Sent from my SAMSUNG-SGH-I747 using xda premium

13 hours "trying" to root your phone with no success??? You're way over thinking it! Flash recovery to your phone through odin, then flash superuser through your newly installed recovery. Should take all of 10 minutes...

CF AUTO ROOT! It should take no more than a minute to root but it won't install a custom recovery so you'll need to use Rom Manager for CWM or GooManager to install TWRP after you root.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Related

No ODIN after ROOT attempt!

I'm on stock and I decided I wanted to try CM10. I've been flashing for almost 2 years now with my captivate and S2.
I went here: http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Flashed the first file and noticed no recovery...
I then noticed I had no more internet, so I decided to try and go back to stock.
Now ODIN will recognize, but hangs before any actual flashing. I am at a loss here. The phone works, but I can't flash anything! Help please?
I would suspect the reason Odin isn't working properly is because the one mention on that site is not the proper (or atleast recommended) version to use with i747. Also their logic to flash custom recovery before achieving root, although possible (maybe??), seems flawed to me. Also, flashing anything other than an officially signed .tar through Odin trips the flash counter, which from a so called 'Noob Friendly' guide seems counter intuitive. Try using the guide posted HERE over on in the development forum here on XDA and see if you get better results.
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Good to hear you got it working , glad to help.
offtopicjack said:
Ok I figured it out. I was using my old Captivate USB cable and not the one that came with the new phone. CM10 is up and running. Thanks for the link btw, that helped.
Click to expand...
Click to collapse
I have flashed via Odin with my cappy cable! Maybe it varies in effectiveness? One thing I did notice however is adb can't see my captivate when I use my gs3 cable(odd eh?)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is definitely an intermittent problem that I can recall happening since I started with android back on the Samsung Moment. Some devices like certain cables, and doesn't like others.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator

[Q] What am I doing wrong. ..........

So im usually pretty tech savy and have always learned things by just doing it. Last night I attempted to root my phone for the first time ever. I began at 11 pm and at 4:15am I through in the towel. I downloaded the tool kit and followed every step to a "T"!!! But everytime I got to Odin and clicked start it began and 1 of 3 things happened everytime. Either it stopped at "_______connection" forgot what it said.. Stopped at Get Pit Meeting for 10 minutes than switched to fail. Or nothing at all.I googled alot researching and tried everything. New USB cable, battery pull, SIM pull, SD pull, different versions of Odin, different USB port, etc. Please help as I dont want to give up but man when I get to trying something I do n9t take failure well which is why I kept at it till 4am.
BTW Im on Sprint
Chainfire's cf-auto root was the easiest method for me. Then I used goo-manager to install twrp.
I tried that one first since after reading it it sounded so easy.
YouTube should have some videos on how to. Maybe this will help http://forum.xda-developers.com/showthread.php?t=2447712
Bump
I know no idea. I used the other method. Here's the link to the thread: linky. There's a video to walk you through the process. The Tool will install the drivers needed. So, I would suggest removing any drivers you have installed regarding the phone. If everything goes well, it shouldn't take longer than fifteen minutes. I had to do it twice. And the tool that you only need once be used free. There's a pay option, but I would recommend donating to, but if funds are tight, it can still be used. If you need it more often, I would definitely say to pay for it.
I've never tried CF autoroot, so I can't say which is easier to use. I just know the link has worked for me, twice.
Try a different pc. I had a hell of a time once getting my kick ass laptop to root a phone. Put it on my wife's little netbook and it worked like a charm.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Also Make sure you are flashing the correct version for your phone. I also have Sprint and used the same toolkit and had no issues.

[Q] help! rooting i747m not working

Hello! This is my first time posting to a forum like this, hopefully I'm doing it right!
I have just gotten an S3 i747m to play with and cant seem to get it to root successfully
I have tried several times with the guides online, the actual root process works great, but when I use root checker it hangs up. Also there is no root access for apps.
I have read the forums and have seen most people root the S3 very easy. Has anyone come across this problem or have a fix for it?
I had no issues running Odin 3.07, everything says that the root was a success, but when I check the phone I have no root access. My phone was at full charge, my sd card was removed, and followed everything to the letter. It's also not the first phone I've rooted.
Any help in this regard would be appreciated thanks!!
What method did you use to roo?
Sent from my SAMSUNG-SGH-I747 using xda premium
I used chainfires method I believe. Readily available, step by step diy . I plugged my phone into odin, everything connected well. I loaded the PDA and the install passed. Everything passed, but there is no root access. I've tried the process several times, also the timer isnt resetting..... I check off F. Reset Time but its not resetting lol I'm stumped.
Did cf auto root install the supersu app? If yes, you should go to the playstore and update the supersu app.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed!! Thank you very much. Was out of date for sure. Thank!

[UPDATE 12/24/13 ] SOLVED! Hard-bricked? Un-hard brick using sd card SM-N900T/N9005

UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaĐ–)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...
msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app
Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.
msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?
i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.
Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol
In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4
Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.

Why TRWP is removed after every flash or reboot?

I am working on my own ROM for my Nexus 5X, but i noticed when i install TRWP Recovery and i reboot my phone again that TRWP has been removed. Is this because my phone is not rooted?
Also i want to know how i can unroot my phone if i root it to do my stuff on it.
@Yzord: using the search function you would have found this thread with the same question. And your 2nd question is also answered yet many times.
You need to flash a modified boot.img or else it will restore the stock recovery every time you reboot. If you flash SuperSU, it will modify your boot.img for you.
Sent from my Nexus 5X using Tapatalk
rp158 said:
@Yzord: using the search function you would have found this thread with the same question. And your 2nd question is also answered yet many times.
Click to expand...
Click to collapse
Believe me, i am trying hard to read the forum through the (very) bad search function. But i can't seem to figure out how i do all of this. Apparently i get old topics above through the search function, because i needed to find out through Google that there is a Nexus Root Toolkit.
I am working with the Nexus Root Toolkit and did the Root option. The result was "Automated Rooting Procedure Complete" and it told me to push the SuperSu app to finish it. But i dont have a SuperSu app installed ( i do have a custom rom installed already) , and if i push busybox it tells me it has issues with opening a shell with root access.
So, i am a little bit confused. Like in the old days people are always the first to shout to use the search function of the forum, but the search function isn't really helpful. I have the phone already a week now and i really tried it to search through the forum before opening a topic. But no matter what i try, i keep unrooted (Android 7.1.1) and so i can't cook my own ROM like how easy it was in the old days.
@Yzord: reset and, as in the good old days, do it with basics, as described here. Worked flawless for me.
Happened with me too when the phone is encrypted, what i done is reset the phone or unencrypted.
Sent from my Nexus 5X using Tapatalk

Categories

Resources