K first off Yes I did do my research here looking to see if my problem was solved but just wanted to make sure by posting and explaining my situation. So pretty much, my nexus was having some issues and so I decided to flash the factory image. Everything all stock by the way. So I unlocked the boot loader flash everything manually and come to find that it kept spinning at the dots. It was probably at least 20 mins so I got pretty impatient. Went into stock recovery, wiped data and cache then proceeded to reboot. And here's probably where I screwed up. Got worried again to I went to fastboot, locked the damn boot loader, and wiped again and restarted into the endless swirl of the google dots.
Now, is there anything constructive, rather than bashing me, someone could provide me with? Thanks so much guys. Never thought this would happen with a nexus device.
http://forum.xda-developers.com/showthread.php?t=3059518
via fastboot(while in the bootloader), try this..
fastboot format userdata
fastboot format cache
fastboot reboot
jiv101 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Has this been successful to you? I remember reading that earlier today but seems a bit confusing. Not too sure how it works. Would you be able to explain a little more?
jiv101 said:
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
simms22 said:
via fastboot(while in the bootloader), try this..
fastboot format userdata
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I can try this. About how long should I wait afterwards? That way I don't get impatient again
Sorry I never tried it
BraddahBoi808 said:
I can try this. About how long should I wait afterwards? That way I don't get impatient again
Click to expand...
Click to collapse
that other way, i have no idea. the way i posted, maybe 10-12 minites. well, if it boots.
Alright, I'll try out both. Thanks guys
Alright so nothing has worked so far. Anyone else know what I should do, or am I now forced to send it in for service?
BraddahBoi808 said:
Alright so nothing has worked so far. Anyone else know what I should do, or am I now forced to send it in for service?
Click to expand...
Click to collapse
There is nothing else you can do.
Can you unlock again or are you stuck locked.
toknitup420 said:
Can you unlock again or are you stuck locked.
Click to expand...
Click to collapse
Its not possible to unlock unless you boot into android and set "enable OEM unlock" but he cannot boot into android.
There is nothing at the moment he can do.
rootSU said:
Its not possible to unlock unless you boot into android and set "enable OEM unlock" but he cannot boot into android.
There is nothing at the moment he can do.
Click to expand...
Click to collapse
I wasn't sure if OEM unlock would untick itself since he never actually booted the os. I thought that only became unchecked when you boot the os. I do agree with you though. He's most likely SOL. I haven't seen anyone on XDA yet that's had any real success after being stuck in bootloader with locked bootloader.
toknitup420 said:
I wasn't sure if OEM unlock would untick itself since he never actually booted the os. I thought that only became unchecked when you boot the os. I do agree with you though. He's most likely SOL. I haven't seen anyone on XDA yet that's had any real success after being stuck in bootloader with locked bootloader.
Click to expand...
Click to collapse
I think you're right. If its ticked and you boot, I think it unticks it at boot. Whether a loop is enough to do that I don't know.
But another thing is that the default setting is unticked anyway. Until 5.1 at least to me, "allow OEM unlock" seems to be window dressing. I never needed to use this to unlock so I imaging for most people this setting remains untucked
rootSU said:
I think you're right. If its ticked and you boot, I think it unticks it at boot. Whether a loop is enough to do that I don't know.
But another thing is that the default setting is unticked anyway. Until 5.1 at least to me, "allow OEM unlock" seems to be window dressing. I never needed to use this to unlock so I imaging for most people this setting remains untucked
Click to expand...
Click to collapse
Yeah is normal to be unticked in 5.1. It won't affect anything though. But. If you relock without ticking it first and you can't boot to os then you're screwed. From what I've seen.
toknitup420 said:
Yeah is normal to be unticked in 5.1. It won't affect anything though. But. If you relock without ticking it first and you can't boot to os then you're screwed. From what I've seen.
Click to expand...
Click to collapse
Yes absolutely.
But what I meant is I never ticked mine in 5.0 and was still able to unlock. So since we could unlock without ticking it before 5.1, I imagine most people never ticked it before updating.. Then things changed.
Damn, I had a bad feeling about it as soon as it didn't start after 20 mins. So best bet would be to RMA it then and hope they fix it or should I try and go further than that by asking for a replacement since it still is under warranty and to bootloader is "locked"? lol
Sending it in for RMA. Getting a replacement device
Related
Hi!
I was installing TWRP on my Nexus 6 just to try it out. Wasn't planning on rooting, just getting my "tap to wake" active. I followed the instructions for unlocking my Nexus 6 through the Dev Options. Then i continued to install a factory image and TWRP. It was all going good until I decided to lock the bootloader again. Now it's on a loop, where however I start the phone, it just goes to the TWRP startscreen and starts blinking at a slow pace.
Is there a way to enable the "allow OEM unlock" option in the Dev Options from a command line? Please can someone help? I really need to fix this, I got this phone yesterday and I feel so bad right now.
Thanks for any answers you might have.
/Diego
Sound like you have a bricked phone... There's a forum about it already started
jiv101 said:
Sound like you have a bricked phone... There's a forum about it already started
Click to expand...
Click to collapse
Can u link it please?
Format cache and userdata via fastboot. If that doesn't work, nothing you can do. Send for warranty
DiegoValdes said:
. It was all going good until I decided to lock the bootloader again.
Click to expand...
Click to collapse
Words to live by
Sent from my Google N6 on VZ
I never found a solution but luckily the place where I bought it felt sorry for me and gave me a new one with at new receipt. I don't feel like I deserve it though. Never again will I mess with the phone, stock for life.
Thanks for replying people! I appreciate it, truly.
Take care!
/Diego
Just don't relock the bootloader and we can get you out of any other issue [emoji6]
Sent from my Google N6 on VZ
Read, read, succeed.
http://forum.xda-developers.com/showthread.php?t=3067302
DiegoValdes said:
I never found a solution but luckily the place where I bought it felt sorry for me and gave me a new one with at new receipt. I don't feel like I deserve it though. Never again will I mess with the phone, stock for life.
Thanks for replying people! I appreciate it, truly.
Take care!
/Diego
Click to expand...
Click to collapse
Don't do that. This is part of learning. Sure its stinks that you messed you're phone up. But now you know what you did wrong so just don't do it again. Lol. We've all bricked one or two devices, it comes with the territory. I'm glad the store helped you out though. That's really cool of them.
I soft bricked a phone once and it took me a few days to figure it out. I think the worst part was my wife asking me things like; how much did that phone cost? Aren't computers kind of your job? What number should I call you on?
Sent from my Google N6 on VZ
Is there any solution for bootloop and locked bootloader ?
Thanks !
usernome said:
Is there any solution for bootloop and locked bootloader ?
Thanks !
Click to expand...
Click to collapse
If you have stock recovery, first try clearing the cache via recovery. If that doesn't work, factory data reset from stock recovery.
If TWRP is installed, reflash your ROM. Or factory reset option.
Otherwise,
fastboot format userdata
fastboot format cache
usernome said:
Is there any solution for bootloop and locked bootloader ?
Thanks !
Click to expand...
Click to collapse
All else fails. Grab this and go back to stock. Then use it to upload your bootloader and root.
http://forum.xda-developers.com/showthread.php?t=2947452
Use the Tool Kit
Sent from my HTC6535LVW using Tapatalk
DiegoValdes said:
Hi!
I was installing TWRP on my Nexus 6 just to try it out. Wasn't planning on rooting, just getting my "tap to wake" active. I followed the instructions for unlocking my Nexus 6 through the Dev Options. Then i continued to install a factory image and TWRP. It was all going good until I decided to lock the bootloader again. Now it's on a loop, where however I start the phone, it just goes to the TWRP startscreen and starts blinking at a slow pace.
Is there a way to enable the "allow OEM unlock" option in the Dev Options from a command line? Please can someone help? I really need to fix this, I got this phone yesterday and I feel so bad right now.
Thanks for any answers you might have.
/Diego
Click to expand...
Click to collapse
What demon possessed you to relock your bootloader??!?!?
Also, even if twrp doesn't start "fully", it should still give you access through ADB, which is all you need to wipe your data partition. I'm not sure why people recommend wiping your cache partition, it won't do you any good.
My nexus 6 is in a mess.
Ive briefly read everywhere about fixing it so far no luck. Is there any way any fix /solution possible
It started when i Wiped data and formated data thus wiping out the whole os inside twrp when it was working "by mistake".
So i remained oem unlocked . I used wug fresh toolkit to reflash 5.0, I suspected the process had finished but it didnt work the first time it just sat on google splash sreen and idiot me clicked on oem lock right after.
Now i cant oem unlock to run any commands or even the toolkit. I read about a hardbrick fix solution using rsd lite and qhsusb drivers basically lg version of qualcomm flashing. Would this work for my instance? What are my choices? WHAT I Dont understand is if there is no O.S why would it even ask for oem unlock knowing there isnt even a operating system on board since it was wiped after twrp reboot
androidddaaron said:
My nexus 6 is in a mess.
Ive briefly read everywhere about fixing it so far no luck. Is there any way any fix /solution possible
It started when i Wiped data and formated data thus wiping out the whole os inside twrp when it was working "by mistake".
So i remained oem unlocked . I used wug fresh toolkit to reflash 5.0, I suspected the process had finished but it didnt work the first time it just sat on google splash sreen and idiot me clicked on oem lock right after.
Now i cant oem unlock to run any commands or even the toolkit. I read about a hardbrick fix solution using rsd lite and qhsusb drivers basically lg version of qualcomm flashing. Would this work for my instance? What are my choices? WHAT I Dont understand is if there is no O.S why would it even ask for oem unlock knowing there isnt even a operating system on board since it was wiped after twrp reboot
Click to expand...
Click to collapse
No, you cannot use that fix, as it is specifically for a hard brick, non bootable device. When you relocked your bootloader, you sealed your fate. Your only option is to RMA at this point. Sorry.
Evolution_Tech said:
No, you cannot use that fix, as it is specifically for a hard brick, non bootable device. When you relocked your bootloader, you sealed your fate. Your only option is to RMA at this point. Sorry.
Click to expand...
Click to collapse
Hi! Sorry for my English. I use Google Translate. I have noticed a hundred you know well the device Nexus 6. My problem - OEM locked, stock recovery, Status code 2.
Do you think it possible to hope for a solution to this problem in software?I mean, is it possible that it will release software to solve this problem?
ArmanioKZ said:
Hi! Sorry for my English. I use Google Translate. I have noticed a hundred you know well the device Nexus 6. My problem - OEM locked, stock recovery, Status code 2.
Do you think it possible to hope for a solution to this problem in software?I mean, is it possible that it will release software to solve this problem?
Click to expand...
Click to collapse
No. You need to make a request to Motorola for repair (RMA).
cam30era said:
No. You need to make a request to Motorola for repair (RMA).
Click to expand...
Click to collapse
Thanks for the answer. Unfortunately I have no such possibility(( I'll wait, can think of something.
ArmanioKZ said:
Thanks for the answer. Unfortunately I have no such possibility(( I'll wait, can think of something.
Click to expand...
Click to collapse
your only option is to fastboot format userdata and cache.
simms22 said:
your only option is to fastboot format userdata and cache.
Click to expand...
Click to collapse
it does not help, because the established stock recovery
ArmanioKZ said:
it does not help, because the established stock recovery
Click to expand...
Click to collapse
some people it does help, but they usually have twrp recovery, so youre right.
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
kickenwing13 said:
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
Click to expand...
Click to collapse
There is honestly no way to tell. We would be guessing. You cannot unlock the bootloader now either, so we can't even get you to manually flash stock to test.
You can try a "fastboot format userdata" and "fastboot format cache" to see if that helps you boot, otherwise, nothing you can do.
We do recommend that you only use toolkits if you know what they are doing in the background. It really isn't difficult. In fact, I wrote a very simple thread to explain in in General > Sticky roll-up. None of this has anything to do with omniscience. Though, that particular skill would be helpful to us to answer your actual question.
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
kickenwing13 said:
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
Click to expand...
Click to collapse
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
danarama said:
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
Click to expand...
Click to collapse
tried and the process failed... I have it back to status 2 and not rooted and it died after flashing stock so I assume sending it back is okay.. my replacement is here today. I'm unlocking and rooting as we speak
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
openbook said:
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
Click to expand...
Click to collapse
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Evolution_Tech said:
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Click to expand...
Click to collapse
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
openbook said:
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
Click to expand...
Click to collapse
It's a security feature since 5.1. You cannot.unlock the bootloader without first setting "enable oem unlock". If you unlocked before 5.1, then you most likely didn't do this as it wasn't needed. So now you're locked and there is no way to unlock it.
Some devs may be looking into it, but if they are, they have been looking into it for a long time. It's extremely unlikely there will be a solution for this that doesn't come from Motorola. It could be an easy fix if Moto Wanted. They could provide a stock recovery flash able fully signed, rom.zip. This wouldn't bypass security either because you would still need your unlock code / google password to boot the device. But so far, we've heard nothing
Send it in to them. If you haven't got TWRP installed, there is nothing you can do. There's no reason for them to void warranty
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?
boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.
I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.
Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk
I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.
Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.
I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/
Mage42384 said:
I've been digging around all day for an answer, but I can only find what to do for an FRP error if you're locked out of your phone, nothing about installing custom recoveries and roms.
Downloaded all the latest, and some older in case, recoveries, auto roots, and unlockers + roms even though I never got that far, lol. Tried Odin 3.11 and 3.10, nothing older yet because I'm just annoyed now.
So, I reboot into bootloader with adb or pressing buttons, Odin detects the phone fine, thow the recovery into the AP section, hit start, it starts the flash, I see a touch of a progress bar, and I get the "Custom binary blocked by frp...." error at the bottom of the info lines at the top. Phone locks up, I'll reboot with vol-/pwr or just pull the battery, and it reboots fine.
So, what do I have to do to get around this FRP so I can install a new recovery/rom? I'm really sick of 6.0.1 just not working right or doing anything it promised =/
Click to expand...
Click to collapse
Have you turned off Factory Reset Protection (reactivation lock)? :silly:
nine5raptor said:
Have you turned off Factory Reset Protection (reactivation lock)? :silly:
Click to expand...
Click to collapse
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that
Mage42384 said:
Well that does seem like it would fix the problem doesn't it? Of course, can't find how to do that
Click to expand...
Click to collapse
Settings - security - reactivation lock. Untick the box
nine5raptor said:
Settings - security - reactivation lock. Untick the box
Click to expand...
Click to collapse
Not there
Mage42384 said:
Not there
Click to expand...
Click to collapse
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on
nine5raptor said:
I'm trying to upload a screenshot....stupid app failing. What OS version?
Edit: nevermind, I see 6.0.1 which is what I'm on
Click to expand...
Click to collapse
Was hoping it was that when I first saw it earlier, but not showing in security, developers, or searches
Should be attached now.
My current security screen
Mage42384 said:
My current security screen
Click to expand...
Click to collapse
Do you have OEM unlock at the bottom of developer options?
And my builds and versions since that's probably a question coming up soon
nine5raptor said:
Do you have OEM unlock at the bottom of developer options?
Click to expand...
Click to collapse
That I do have have (^_^)
Mage42384 said:
That I do have have (^_^)
Click to expand...
Click to collapse
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.
nine5raptor said:
So they dropped their reactivation lock on the T3 variant...interesting. OEM unlock should allow you to proceed.
Samsung and all their silly variants....just to confuse us.
Reactivation Lock is Samsung's proprietary variant of the OEM unlock Google already provides.
Click to expand...
Click to collapse
Not sure if it's all T3s, seen a bunch of posts today about the T3 using the Samsung security version, but this is a very late model, lol. Think I bought this a little over 6 months ago
I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)
Mage42384 said:
I'll see if I have time tomorrow to try it out, but def let you know by Thursday. Thanks for the help =)
Click to expand...
Click to collapse
Hope it works out for you. Sorry for all the confusion searching menus.
nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
No worries, it got done lol. Spent 6 hours at work today finding all the wrong answers xD
nine5raptor said:
Hope it works out for you. Sorry for all the confusion searching menus.
Click to expand...
Click to collapse
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol
Mage42384 said:
Ok, installation works...but when I try to go to recovery, I just get the dead droid pic saying no command now =( Back to digging through forums, unless you have any advice for that, lol
Click to expand...
Click to collapse
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.
nine5raptor said:
After flashing twrp, don't let it boot system. As soon as it reboots, pull the battery. Then boot into twrp. For some reason, MM changed the process and now you cannot boot into system before booting twrp for the first time.
Click to expand...
Click to collapse
Ah, it does that first boot restore recovery thing that my HTC's used to do...but with those, you'd get one shot into recovery at any time if I remember right (could be 3 weeks later, but only once, lol)