Related
I have the S3 Mini for Verizon (SM-G730V)
I rooted my phone a while back but my phone updated this month and it automatically unrooted. I tried using Kingo to root it because it had worked previously but I got an error saying "NEEDROOT"
I've been searching for a program ever since, but every one I've tried doesn't work. One even hard reset my phone
Does anyone know a root method that works for my phone??
PoisonBullet9 said:
I have the S3 Mini for Verizon (SM-G730V)
I rooted my phone a while back but my phone updated this month and it automatically unrooted. I tried using Kingo to root it because it had worked previously but I got an error saying "NEEDROOT"
I've been searching for a program ever since, but every one I've tried doesn't work. One even hard reset my phone
Does anyone know a root method that works for my phone??
Click to expand...
Click to collapse
Try to use vroot
Ahmed.ragab said:
Try to use vroot
Click to expand...
Click to collapse
I did, with no luck. I also tried various other programs, like one click, odin, and phone apps like poot. None seem to work with my phone.
PoisonBullet9 said:
I did, with no luck. I also tried various other programs, like one click, odin, and phone apps like poot. None seem to work with my phone.
Click to expand...
Click to collapse
why not just flash a custom rom with odin? you could try cyanogenmod though the 11 version maybe has hard battery drain. carbon should be fine though! then you also have kitkat 4,4,2
good luck... click the thanks button if you think this is useful
PoisonBullet9 said:
I did, with no luck. I also tried various other programs, like one click, odin, and phone apps like poot. None seem to work with my phone.
Click to expand...
Click to collapse
if you have custom recovery try to flash this file and see if it will work
http://www.mediafire.com/download/r229vw3lt10n45e/Superuser-3.1.3-Recovery.zip
Aronuser said:
why not just flash a custom rom with odin? you could try cyanogenmod though the 11 version maybe has hard battery drain. carbon should be fine though! then you also have kitkat 4,4,2
good luck... click the thanks button if you think this is useful
Click to expand...
Click to collapse
Flashing ROMs thought Odin is inconvenient, I'd prefer to just root the phone for ease of use.
I think I found the source of the problem:
When I was using vRoot, it said that I didn't have 'root permission' and gave me a how-to in order to solve that problem. However it was in Chinese so I couldn't figure it out. Is it possible that I just need to find a way to get root permission for my phone? How do I get permission?
Ahmed.ragab said:
if you have custom recovery try to flash this file and see if it will work
Click to expand...
Click to collapse
Nope, doesn't have the correct files for Odin (PDA, Phone, CSC...)
PoisonBullet9 said:
Flashing ROMs thought Odin is inconvenient, I'd prefer to just root the phone for ease of use.
I think I found the source of the problem:
When I was using vRoot, it said that I didn't have 'root permission' and gave me a how-to in order to solve that problem. However it was in Chinese so I couldn't figure it out. Is it possible that I just need to find a way to get root permission for my phone? How do I get permission?
Click to expand...
Click to collapse
there is an english version of vroot too now check it here http://www.mgyun.com/en/getvroot
if you consider this useful please click thanks button under my post thanks
Aronuser said:
there is an english version of vroot too now check it here
if you consider this useful please click thanks button under my post thanks
Click to expand...
Click to collapse
The English version is a little broken, not all of it is in English. I'm talking about the app they have for the phone. I downloaded it and it said it couldn't root my phone (at least that's what I think it said it was all Chinese) and it gave me a list of instructions I couldn't understand. I already tried the English vRoot and it didn't work.
IMHO best way how to root your phone is by flashing custom recovery (TWRP or CWM) via Odin and then by flashing root binaries from recovery.
Gw|n said:
IMHO best way of root is flash custom recovery (TWRP, CWM) and then flash zip file with root via recovery.
Click to expand...
Click to collapse
Can you explain how to do that? Or provide a link that does?
I've updated my previous post. Download some custom recovery and flash it as pda, then reboot into it by pressing vol. up + home + power and finally flash zip with root from recovery.
and after you have custom recovery it's also super easy to flash .zip files with recovery only (not odin) so then you can flash custom roms .zip's
Gw|n said:
I've updated my previous post. Download some custom recovery and flash it as pda, then reboot into it by pressing vol. up + home + power and finally flash zip with root from recovery.
Click to expand...
Click to collapse
Can I get a link for any custom recovery that is compatible with the Verizon S3 mini? (SM-G730V)
PoisonBullet9 said:
I have the S3 Mini for Verizon (SM-G730V)
I rooted my phone a while back but my phone updated this month and it automatically unrooted. I tried using Kingo to root it because it had worked previously but I got an error saying "NEEDROOT"
I've been searching for a program ever since, but every one I've tried doesn't work. One even hard reset my phone
Does anyone know a root method that works for my phone??
Click to expand...
Click to collapse
Try using Unified Android Toolkit and simply following the on screen instructions.
I am having the same issue with my wife's phone. Rooted once with Kingo but she accidentally accepted an OTA update and we lost root. Now Kingo just says "Root failed."
Verizon has locked the bootloader on these phones so that it is, AFAIK, not possible at all to flash a custom recovery. I have plenty of experience with CWM and TWRP from my own two previous sammys (Epic 4G and Galaxy S4, both on Sprint). If someone here (with a VZW model) has experience otherwise, I'd love to hear about it and how you got around the lock.
Downloading Unified Android Toolkit now and we'll see how it goes, but it is not looking good.
-Sean
---------- Post added at 07:45 AM ---------- Previous post was at 07:26 AM ----------
slwelsh said:
...
Downloading Unified Android Toolkit now and we'll see how it goes, but it is not looking good.
Click to expand...
Click to collapse
Well, that lead me nowhere. It comes up with a list of S3 Mini model numbers that does not include Verizon's. On top of that, AVG said one of the executables was infected with a virus (a warning which I bypassed in order to test).
Any other suggestions?
-Sean
slwelsh said:
I am having the same issue with my wife's phone. Rooted once with Kingo but she accidentally accepted an OTA update and we lost root. Now Kingo just says "Root failed."
Verizon has locked the bootloader on these phones so that it is, AFAIK, not possible at all to flash a custom recovery. I have plenty of experience with CWM and TWRP from my own two previous sammys (Epic 4G and Galaxy S4, both on Sprint). If someone here (with a VZW model) has experience otherwise, I'd love to hear about it and how you got around the lock.
Downloading Unified Android Toolkit now and we'll see how it goes, but it is not looking good.
-Sean
---------- Post added at 07:45 AM ---------- Previous post was at 07:26 AM ----------
Well, that lead me nowhere. It comes up with a list of S3 Mini model numbers that does not include Verizon's. On top of that, AVG said one of the executables was infected with a virus (a warning which I bypassed in order to test).
Any other suggestions?
-Sean
Click to expand...
Click to collapse
Tried saferoot?
ImproAptoVictum said:
Tried saferoot?
Click to expand...
Click to collapse
Trying now, but it doesn't look good. It's been stuck on "Testing adb usability" for ten minutes or so.
So I am now noticing that any time I plug this phone in, during the "Found new hardware" for the ADB interface it is telling me that my new hardware "might not work." This does not happen when I plug in my S4. I'm wondering if VZW has done something to block ADB access...
I've backed the phone up with Kies and now I am thinking about a factory reset before trying again. I just don't want to make things any worse, knowing I can't simply Odin the stock image on this phone.
Any other recommendations?
-Sean
---------- Post added at 01:54 PM ---------- Previous post was at 01:24 PM ----------
slwelsh said:
Trying now, but it doesn't look good. It's been stuck on "Testing adb usability" for ten minutes or so.
Click to expand...
Click to collapse
Update: on retry, I got past this spot, but ultimately the root failed and it told me the model was not supported.
Kingo gets further than anything else I've tried, but eventually fails with the error "NeedRoot." Ironically.
I'm going to try a factory reset. I am wondering if the fact that SuperSu is still in ROM is what's tripping Kingo up. I can force stop it and "turn it off" but, of course, without root I can't actually remove it from the ROM.
-Sean
slwelsh said:
Trying now, but it doesn't look good. It's been stuck on "Testing adb usability" for ten minutes or so.
So I am now noticing that any time I plug this phone in, during the "Found new hardware" for the ADB interface it is telling me that my new hardware "might not work." This does not happen when I plug in my S4. I'm wondering if VZW has done something to block ADB access...
I've backed the phone up with Kies and now I am thinking about a factory reset before trying again. I just don't want to make things any worse, knowing I can't simply Odin the stock image on this phone.
Any other recommendations?
-Sean
---------- Post added at 01:54 PM ---------- Previous post was at 01:24 PM ----------
Update: on retry, I got past this spot, but ultimately the root failed and it told me the model was not supported.
Kingo gets further than anything else I've tried, but eventually fails with the error "NeedRoot." Ironically.
I'm going to try a factory reset. I am wondering if the fact that SuperSu is still in ROM is what's tripping Kingo up. I can force stop it and "turn it off" but, of course, without root I can't actually remove it from the ROM.
-Sean
Click to expand...
Click to collapse
That sounds plausible, factory reset might help avoid the issue, but if SuperSu is installed as system app (normally the case), it might in some cases still be there after a factory reset.
I'm having the same issues. I have tried with three different cables, using three different programs. Do you think it's because I don't have three original cable I only have moto ones? I can reset using kries so it's not like the computer doesn't see it
Sent from my XT875 using Tapatalk 2
Just wondering how long we may have to wait for a Root. Just some small tweaks I'm dying to make.
Until someone gets a phone. Deliveries begin tomorrow.
Sent from my Nexus 5 using XDA Free mobile app
knitler said:
Just wondering how long we may have to wait for a Root. Just some small tweaks I'm dying to make.
Click to expand...
Click to collapse
I don't think we will have to wait very long... The bootloader is so easily unlockable that I'm sure we will see the Pure Edition getting a root within the next few days. Hopefully.. mine came in today and I'm dying to get some xposed modules on it.
markwebb said:
Until someone gets a phone. Deliveries begin tomorrow.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Me and others have them in hand. Mine came today.
knitler said:
Me and others have them in hand. Mine came today.
Click to expand...
Click to collapse
Indeed! If you pre-ordered on day one, you should have it. Unless FedEx didn't do their job (which is likely.)
Vultorus said:
Indeed! If you pre-ordered on day one, you should have it. Unless FedEx didn't do their job (which is likely.)
Click to expand...
Click to collapse
Well Day 1 orders were supposed to arrive on the 26th. they just came early.
knitler said:
Well Day 1 orders were supposed to arrive on the 26th. they just came early.
Click to expand...
Click to collapse
I suppose not EVERYONE would have it yet then.. I have mine though!! (Just excited, been waiting since this thing leaked..)
Some seemed to have root, if you are willing to unlock the bootloader, install the experimental CWM, and flash the latest SuperSU beta.
http://forum.xda-developers.com/moto-x-2014/help/moto-x-2014-dump-t2868250/post55628034
Not a real issue if you have the pure edition (as far as I know unlocking the bootloader on the pure edition does not void your warranty). But currently I can't find the working CWM.
If people are looking for root w/o unlocking the bootloader then I think we will need more time.
My Pure Edition arrived around noon today (the 24th).
Unlocked the bootloader, then I installed the test version of CWM, then I installed SuperSU
Launched SuperSU app and it seemed to work so I went ahead and went crazy...
Currently rocking a device with all my apps & data (thanks Titanium Backup!) and with a few UI tweaks (thanks Xposed and GravityBox!)
I can vouch it is all working 100% and is safe if you can follow instructions. Everything I needed was in this thread:http://forum.xda-developers.com/moto-x-2014/help/moto-x-2014-dump-t2868250 Test version #8 of CWM is the one you want; page 9 I believe. Post #99 is the instructions I followed, worked like a charm.
wynterend said:
My Pure Edition arrived around noon today (the 24th).
Unlocked the bootloader, then I installed the test version of CWM, then I installed SuperSU
Launched SuperSU app and it seemed to work so I went ahead and went crazy...
Currently rocking a device with all my apps & data (thanks Titanium Backup!) and with a few UI tweaks (thanks Xposed and GravityBox!)
I can vouch it is all working 100% and is safe if you can follow instructions. Everything I needed was in this thread:http://forum.xda-developers.com/moto-x-2014/help/moto-x-2014-dump-t2868250 Test version #8 of CWM is the one you want; page 9 I believe. Post #99 is the instructions I followed, worked like a charm.
Click to expand...
Click to collapse
could you upload the CWM file? us users cannot get it since it reached a download quota. please and thank you!
edit: do I need to flash CWM or can I just "fastboot boot recovery.img" and flash SuperSU?
0.0 said:
could you upload the CWM file? us users cannot get it since it reached a download quota. please and thank you!
edit: do I need to flash CWM or can I just "fastboot boot recovery.img" and flash SuperSU?
Click to expand...
Click to collapse
Oh, sure. Where do people like stuff uploaded to? Dropbox? Drive? Somewhere else?
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
0.0 said:
could you upload the CWM file? us users cannot get it since it reached a download quota. please and thank you!
edit: do I need to flash CWM or can I just "fastboot boot recovery.img" and flash SuperSU?
Click to expand...
Click to collapse
Just saw your edit. Not sure, I went ahead and just flashed it. I'm just going to leave it there until somebody ports TWRP to the new X (probably only a matter of days). Never tried just booting it - should maybe work; but again, can't say for sure.
wynterend said:
Oh, sure. Where do people like stuff uploaded to? Dropbox? Drive? Somewhere else?
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Just saw your edit. Not sure, I went ahead and just flashed it. I'm just going to leave it there until somebody ports TWRP to the new X (probably only a matter of days). Never tried just booting it - should maybe work; but again, can't say for sure.
Click to expand...
Click to collapse
drive for now. i just need the file and I'll upload it to my AFH account. gdrive had a download quota from the other user\
i'll test just booting CWM and flashing SU when i get my phone. also, to unlock bootloader, is it
Code:
fastboot oem unlock
0.0 said:
drive for now. i just need the file and I'll upload it to my AFH account. gdrive had a download quota from the other user\
i'll test just booting CWM and flashing SU when i get my phone. also, to unlock bootloader, is it
Code:
fastboot oem unlock
Click to expand...
Click to collapse
No that is not how you unlock. You need a code.
I followed these instructions: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
Here is the Test 8 of CWM:
http://d-h.st/XJr
wynterend said:
No that is not how you unlock. You need a code.
I followed these instructions: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
Here is the Test 8 of CWM:
http://d-h.st/XJr
Click to expand...
Click to collapse
even if I have the Pure Edition, I need a code? that sucks...oh well, shouldn't be too difficult
0.0 said:
even if I have the Pure Edition, I need a code? that sucks...oh well, shouldn't be too difficult
Click to expand...
Click to collapse
Yeah, still needs a code. Took 45 seconds though. Email with code came to my gmail in seconds. No real hassle
wynterend said:
Oh, sure. Where do people like stuff uploaded to? Dropbox? Drive? Somewhere else?
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Just saw your edit. Not sure, I went ahead and just flashed it. I'm just going to leave it there until somebody ports TWRP to the new X (probably only a matter of days). Never tried just booting it - should maybe work; but again, can't say for sure.
Click to expand...
Click to collapse
If you can get it to me somehow, I will post it somewhere that bandwidth quotas will not be an issue. Please do share it, I think there's alot of us (me included) that got their X's early, and have them ready to go with an unlocked bootloader, just waiting to root. Thanks!
You can send me a direct message, or make the link public. Thanks again.
ccie7599 said:
If you can get it to me somehow, I will post it somewhere that bandwidth quotas will not be an issue. Please do share it, I think there's alot of us (me included) that got their X's early, and have them ready to go with an unlocked bootloader, just waiting to root. Thanks!
You can send me a direct message, or make the link public. Thanks again.
Click to expand...
Click to collapse
I did, file is at the link just a few posts up. Enjoy!
I just rooted without flashing CWM using
Code:
fastboot boot recovery.img
where recovery.img is the CWM Test-8 file, and sideloading the 2.02 version of SuperSU. Rebooted from CWM and chose to fix root, now I have root. Took all of 30 seconds to do.
gakio12 said:
I just rooted without flashing CWM using
Code:
fastboot boot recovery.img
where recovery.img is the CWM Test-8 file, and sideloading the 2.02 version of SuperSU. Rebooted from CWM and chose to fix root, now I have root. Took all of 30 seconds to do.
Click to expand...
Click to collapse
i am glad many are saying you don't need to flash CWM. good news for me!
p.s. you should get your SuperSU up to date. may i suggest 2.09 beta?
0.0 said:
i am glad many are saying you don't need to flash CWM. good news for me!
p.s. you should get your SuperSU up to date. may i suggest 2.09 beta?
Click to expand...
Click to collapse
Yeah, I probably should, but I might install Superuser instead, I don't know
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
Oh god are you on the US version (SGH-I537)? If you're on the international version (I9295) ignore this post but otherwise, you need to read and take in my short rant. Trust me I wish this weren't the case, but it is, and it's important:
The Galaxy S4 Active i537 has a locked bootloader. There is no way around this, no ifs ands or buts. You simply cannot flash custom ROMs or recoveries. That's it, end of story as far as CM, CWM, AOSP and such things are concerned. That being said there is a sort of recovery called SafeStrap which you can use to make nandroid backups, flash mods and STOCK-BASED roms, but it's not a true custom recovery in the sense that we had been used to, because of this locked bootloader nightmare.
OK so I think you're gonna want to check out this thread. It's all about how to install any firmware from download mode, I think you're gonna have to go with NE3 or NH3.
Let me reiterate. NO CUSTOM ROMS. NO CWM. No Paranoid, no cyanogenmod, no AOSP, no crossing go before going directly to jail. Sorry for the stupid joke but seriously, you have got to keep your phone on stock-based roms (of which there are unfortunately few).
Firmware download links
timmytron said:
Okay, so I finally decided to ditch AT&T and go full Paranoid (This is not my first flashing attempt with Android devices). Got the latest version, etc. Load into BootStrap and wipe everything. Go to install PA and for some reason I had neglected to tell my build.prop (ro.product.device/name) is supposed to be "jactivelteatt"/"jactivelteuc" and not "SN-M9009". So when I started the flash process, immediate error and now I'm stuck with a phone with no OS or bootloader and can not, for the life of me, find a ROM to flash with .MD5 or .TAR that will work with ODIN. I did find "Oneclick_I537UCUAMF1" that gets all the way to the end and fails. Tried multiple times with multiple cables.
Please if anyone has any idea's, please help.
Click to expand...
Click to collapse
What phone do you have (i537 or i9295) and what version of firmware were you on?
Devo7v said:
What phone do you have (i537 or i9295) and what version of firmware were you on?
Click to expand...
Click to collapse
i537 and second to last, I537UCUCNE3
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Web browser login, edit, advanced.
Add "solved" to title?
same problem with my i537, need help
timmytron said:
Okay, :laugh: I'm back. FINALLY found some MD5 files that loaded. In the process of updating and putting things back they way they were. Thank you to all who viewed/helped!
Is there a way to mark this as "Resolved"?
Click to expand...
Click to collapse
Need help, having the same problem
baddhabbitz88 said:
Need help, having the same problem
Click to expand...
Click to collapse
Have you used ODIN before?
i537 Stuck in download mode
timmytron said:
Have you used ODIN before?
Click to expand...
Click to collapse
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
baddhabbitz88 said:
yes I have use odin but I think I have the same issue you did, need to know where to get the files .
Click to expand...
Click to collapse
Did you get my PM?
timmytron said:
Okay. Well I'm not sure where I got the files either. What I'm going to do is upload them (please do keep in mind that it's a huge file) to my Drive account and I will link it here when complete. You are on the AT&T i537 version?
Click to expand...
Click to collapse
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
Well AT&T decided to completely lock us out on this particular version on this particular phone. At least we have *ROOT*.
baddhabbitz88 said:
Yes, the at&t version i537 is the one I'm. Found some files this morning and run them in Odin but now back at bootloop. I'll check your files and see whats up on that end. It sucks because have not done anything to this phone unlike my other ones and this crap starts with this one on its own.
Click to expand...
Click to collapse
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Devo7v said:
You need to make sure you are flashing a version that is the same or more recent than the version you are currently on. You cannot downgrade your firmware or else you'll end up with a bootloop.
Click to expand...
Click to collapse
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
timmytron said:
Did you get my PM?
Click to expand...
Click to collapse
yeah I got it thanks but it didn't work still digging
baddhabbitz88 said:
k will try to find a more updated version but that is part of the problem is locating the firmware I need + this started doing it on its own and really never dug into it to no which firmware was on it other than rooted months ago with towelroot
---------- Post added at 09:36 PM ---------- Previous post was at 09:04 PM ----------
yeah I got it thanks but it didn't work still digging
Click to expand...
Click to collapse
Always check the stickies.
http://forum.xda-developers.com/showthread.php?t=2892445
So i purchased a Note 4 SM-N910T about a year ago. It worked fine but last month shortly after the 5.1.1 update I did it started randomly restarting for no reason. First i taught it was Snapchat because I red somewhere that there are camera problems, so I stopped using it. But it kept restarting even after that. From then I have made a factory and a master reset, rooted the phone and even installed CM 12. No mater what i do it keeps on restarting. The only way to get it out of the boot loop is to connect it to a charger that is not a fast charger. Then it starts charging and works normally and you can do everything normally. After you remove it from the charger it works as long as you do not use it. When you start using it and want to do something with it it starts restarting again. I hope somebody can help me fix this issue. I have noticed that connecting it to WIFI makes it 100% sure that it will restart any moment. If you leave it without WIFI as long as you do not do anything big it will not restart. For example I watched series on my phone I downloaded beforehand. I was able to go to the CM 12 file manager and change series for the duration of my bus drive and it has not reset yet and it has not been connected to a charger for around 12 hours already.
My last resort is to wait 3 hours for the stupid free 5.0.1 official firmware and flash it using the TWRP Recovery or Odin. If that does not work I would have t give it to a service. Any help will be greatly appreciated! Also a link to where I can download the 5.0.1 official firmware for free in normal speed will be of greatly appreciated as well!
Merry Christmas!
That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile
MisterCoolBeans said:
That's odd, I recommend odin flashing the stock ROM and everything. (Modem + bootloader) the latest one is DOK2 for T-Mobile
Click to expand...
Click to collapse
Do you have a link to where I could download that because all I found were sites where the free user speeds took 3 hours to download 1.5 GB?:crying:
Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!
MisterCoolBeans said:
Let me see if I can find one
---------- Post added at 04:41 PM ---------- Previous post was at 04:40 PM ----------
Here is the full untouched ROM that you can download from Sammobile but it was uploaded to mega instead.
http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858
Make sure you click the first link!
Click to expand...
Click to collapse
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!
Lazarov987 said:
Thank you very much! I put it for download and it has a reasonable speed. After its done I will try and flash it! I hope the problem does not occur anymore!
Click to expand...
Click to collapse
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?
Lazarov987 said:
So since the phone restarts when I connect it to the WIFI should i also flash the stock modem or just try first without it?
Click to expand...
Click to collapse
If you flash the stock firmware it includes the baseband and modem
ShrekOpher said:
If you flash the stock firmware it includes the baseband and modem
Click to expand...
Click to collapse
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!
I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.
Lazarov987 said:
To revive the thread I tried flashing the N910TUVU2DOK2_N910TTMB2DOK2_N910TUVU2DOK2_HOME.tar via Odin. It all went fine and after starting the phone it went on to the step where its optimizing apps. It got stuck there and it went back to the boot loop. I had reflash the CM 12 and TWRP Recovery and now I am back at 0. So my question is how should I flash the stock rom. Go to TWRP do a factory reset than turn the phone off and flash the stock rom via Odin? Should I also flash TWRP ans SuperSu after flashing the stock rom?
Thank you for your help!
Click to expand...
Click to collapse
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
jazzmachine said:
I've been having the same problem for about a week and a half; it's super annoying. I was running Dynamic Pop on COG2 then yesterday I updated to DOK2 and flashed Maximum Overdrive... no improvement. It rarely even fully boots before freezing or rebooting.
My best guess as to what the problem is that it may be overheating because it tends to actually boot if I put it in the freezer while booting, but then it freezes soon after taking it out. I suppose it could also be internal memory corruption.
Either way, I'm getting ready to do a warranty exchange.
Click to expand...
Click to collapse
You may have messed up the partitions. There is a thread about the pit file you should check out.
ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
What thread is that and how do I find it? I mean I always checked that in Odin i never had Re-partition on.
ShrekOpher said:
First focus on getting a clean stock firmware booted. Do what you mentioned above but don't flash TWRP or superSu until the stock ROM is stable. We need to narrow down the issues so do as few modifications as possible.
---------- Post added at 06:02 AM ---------- Previous post was at 06:01 AM ----------
You may have messed up the partitions. There is a thread about the pit file you should check out.
Click to expand...
Click to collapse
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..
Lazarov987 said:
I actually downloaded 2 stock roms for my Note 4. One was the COG2 and the other one was the completely stock firmware. I tried flashing them but Odin failed (Auth) whatever that means. The only stock rom I was able to flash was 5.1.1 but it wouldn't boot up so I had to install CM 12 again! I have no idea how to fix the phone. All I want is to return to 5.0.1 and delete any changes. The phone has no apps on it so i have nothing to loose but I do not know how to do it..
Click to expand...
Click to collapse
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.
ShrekOpher said:
You cannot use 5.0.1 ROMs on DOK2 they will never boot and no down grading. You have to use 5.1.1 ROMs for now on.
Click to expand...
Click to collapse
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
Ashwin Prabhunerurkar said:
check this out
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
Click to expand...
Click to collapse
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!
Lazarov987 said:
This is exactly what is happening to my T-Mobile Note 4 (SM-N910T) and the thing that you did to your Canadian Note 4 is exactly what I want to do. But can I use the firmware you provided at: http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452
or must I use the T-Mobile ones and if I have to use the N910T firmware where can I get it so I can do what you did? A link or a thread would be amazing cause I really miss using my phone as normal!
Click to expand...
Click to collapse
Don't flash Canadian tar files
We are searching for the answer
Hope to come back to you with a solution
Try Odin flash back to stock.
@dannygoround
dannygoround said:
Try Odin flash back to stock.
@dannygoround
Click to expand...
Click to collapse
Doesnt work. Wont flash the stock rom. It says Fail(Auth)
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave
Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave
dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3
Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1
dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave