Related
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app
ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.
:thumbup:
I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...
daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota
doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.
y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.
rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT
It seems that Google has turned it's back on devs a bit more. Tons of people are having this issue, as I was finally tweaking around and could never get safetynet working. Turns out I got an early taste of Google's rollout yesterday.
Happening to me as well. Both on my 5x and N6 that used to work. Locking the bootloader (I'm not rooted) will now wipe the phone, right?
I have a completely stock 5X. The only modification is an unlocked bootloader. When I installed the 7.1.1 DP update yesterday, Android Pay quit working. I tried to pay for an Uber ride using Android Pay and it failed. I assume the same is true for trying to use Android Pay via NFC in stores.
---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------
Minker17 said:
Happening to me as well. Both on my 5x and N6 that used to work. Locking the bootloader (I'm not rooted) will now wipe the phone, right?
Click to expand...
Click to collapse
Unlocking the bootloader wipes the device. Locking does not.
http://www.androidcentral.com/how-unlock-nexus-5x-bootloader
I've seen reports that it started wiping a few versions ago. This is for a 6p, but have seen others. Does it just not apply to the 5x?
https://plus.google.com/+ArtemRussakovskii/posts/49VyN48ixDp
I relocked my bootloader yesterday, it does now cause a factory reset. It will also cause bricking to happen if you have a modified system, recovery or boot partition, recommend practice would be to flash a factory image before relocking if you have rooted or used twrp etc.
If you do go ahead also remember to back up anything you have on your storage first.
It was only a matter of time before they started doing stuff like this... I didn't know they were really that worried about nfc payments yet.
Minker17 said:
I've seen reports that it started wiping a few versions ago. This is for a 6p, but have seen others. Does it just not apply to the 5x?
https://plus.google.com/+ArtemRussakovskii/posts/49VyN48ixDp
Click to expand...
Click to collapse
I think the previous guy is confused. On 5x, t has been forcing a factory reset during lock since at least MHC19J if not since the beginning.
On older phones it didn't force factory reset during lock, only unlock, so I think many people are just going by memory and probably never relocked on 5x.
sfhub said:
I think the previous guy is confused. On 5x, t has been forcing a factory reset during lock since at least MHC19J if not since the beginning.
On older phones it didn't force factory reset during lock, only unlock, so I think many people are just going by memory and probably never relocked on 5x.
Click to expand...
Click to collapse
That's correct. I just relocked mine last night and I had to do a factory reset.
So, I installed the 7.1 preview a few days back without rooting or anything else, can I safely just relock bootloader to get android pay working again?
I was on the 7.0 factory image before hand, again, unrooted and stock recovery
Mikey F said:
So, I installed the 7.1 preview a few days back without rooting or anything else, can I safely just relock bootloader to get android pay working again?
I was on the 7.0 factory image before hand, again, unrooted and stock recovery
Click to expand...
Click to collapse
Yes, but be aware locking or unlocking your bootloader will wipe your device.
yochananmarqos said:
Yes, but be aware locking or unlocking your bootloader will wipe your device.
Click to expand...
Click to collapse
OK cool, yes I'm aware it will wipe the phone, I'm prepared for that.
The Flash's kernel now had a fix for that bootloader check.
Try it and see if it works for you before locking the bootloader. It is easier to flash a boot.img than it is to format.
odunke01 said:
The Flash's kernel now had a fix for that bootloader check.
Try it and see if it works for you before locking the bootloader. It is easier to flash a boot.img than it is to format.
Click to expand...
Click to collapse
So flashing the flash's kernel means android pay should work with unlocked bootloader?
With flash or Franco kernel I pass safetynet helper. So I am assuming it will work with pay, I don't have any cards at up atm to try.
Edit. Just enrolled a card and all good.
https://www.engadget.com/2016/10/24/android-pay-is-coming-to-hundreds-of-thousands-more-websites/
It's a losing battle imo. Either root or use banking and ap. No reason to try both. It's just frustrating.
Sent from my Nexus 5X using XDA-Developers mobile app
Wait. Just so I'm clear, unlocking the bootloader alone will break Android Pay? I typically unlock my bootloader as soon as I get a new phone, mainly so I can manually flash images, but I don't root or flash custom recovery. It's be really annoying to lose that option.
Sent from my Nexus 5X using Tapatalk
Yeah I think I'm going to just back up and relock my bootloader, android pay, once I'd started using it, became really handy
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Bright.Light said:
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Click to expand...
Click to collapse
That's fine and your decision, but AP is Google's service and they can operate how they want with what security features they want. And with lots of banks & lots of money on the line, you better believe it Google needs to ensure as much security as they can with it.
Bright.Light said:
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Click to expand...
Click to collapse
Entirely your call, but working in the computer repair business, I deal with a lot of end users that have been done over by malware and ransomware, so any efforts to stop that are welcome. I'm happy to be able to use android pay at the cost of a more secure phone, so I'll be relocking my boot loader when I'm home from holiday
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!
LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.
Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.
V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.
Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT="]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse
lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk
Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT="]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.
Can someone run this:
Code:
fastboot getvar all
Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.
Quick and simple bc after sifting through this website I accidently figured it out. First use the script from this post - https://forum.xda-developers.com/t/oneplus-pure-debloat.4157691/ then check dev options and OEM unlocking should be ungreyed out. Grab your oneplus unlock by running this command - "fastboot oem get_unlock_code" Then go to - https://www.oneplus.com/unlock_token submit your token and serial number and wait exactly one week to the day. Download this tool https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ and you can unlock the bootload with your unlock.bin file. After that whats next is up too you!
I don't know about SIM unlocking, however I did figure out which package specifically enables the toggle for OEM unlocking in the Developer Options.
So I took a look at the debloat thread linked above and I went through the list of packages and I was uninstalling them on my phone one by one until I found the one that enabled the toggle for OEM unlocking in the Developer Options.
When I uninstalled the package com.qualcomm.qti.uim, the toggle for OEM unlocking was no longer greyed out.
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
LLStarks said:
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
Click to expand...
Click to collapse
I didn't see if force stopping it worked or not so I wouldn't be able to answer that. I just uninstalled it with adb.
Title of tread said sim-unlocking, after reading through, it only mentions bootloader unlocking via the OnePlus website and all in one flashing tool. Yes it may bypassed the carrier restriction for bootloader unlocking, but is the phone actually sim unlocked? As you can use it with another carrier?
But I agree, finding out com.qualcomm.qti.uim being the toggle for bootloader unlock is great find.
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
kevinco1 said:
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
Click to expand...
Click to collapse
gotta complete the whole process homie.. AFTER doing the uninstall or disable of com.qualcomm.qti.uim, then you gotta flip the toggle and then reboot to bootloader. after that you need to run the fastboot command, "fastboot oem get_unlock_code"... copy that code to your clipboard, then go to the Oneplus website, fill out the form and paste that code in the proper field.
After that it does take exactly one week... (to the minute) and you will need to go back to this site and you will see it change to download. Download that file and flash it via fastboot, then confirm you want to unlock and its done!
Now after that you have to remember to NEVER flash a stock firmware via fastboot again, otherwise you will re-lock your bootloader. I cannot confirm whether or not you will be able to, or even need to flash the unlock token again, but in the case of Samsung phones, when you flash the bootloader unlock token, you DO NOT get a second chance. If you unlock it once, and then accidently re-lock via flashing stock, you will be stuck with a locked bl. (EDIT: you CAN flash stock with samsung, as long as the bootloader version isnt changed. If you upgrade the BL then you are stuck!)
(Now theres a simpler way around all this but you must do your research, and look into converting your TMO-US fw to TMO-EU ... this can be done without unlocking the bootloader. And after the conversion, if you disable the OP mentioned file, you can simply toggle, and run the "fastboot oem unlock" command and thats it... no token file needed! And i am in Texas, so i can confirm 100% that ALL of the bands are active and available, and i get 5g with absolutely no problem... In fact my phone runs quicker and gets better battery life on the EU fw. )
Then when your phone is fully paid off, simply flash back to the US fw and you can have them Sim unlock you and you can either go thru the normal unlocking process, or you can go back to the EU... but either way no foul, no harm!
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
kyanox said:
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
Click to expand...
Click to collapse
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
i am shop in istanbul come to me oneplus 8t 5g t-mobile i ask whole world for simlock no one can and one of customer tell me i can unlock he take device for 3 hour he come back and device unlocked and he tell me i can do anything in oneplus phones i got crazy how he did this ? anyone know how ?
jabe78 said:
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
Click to expand...
Click to collapse
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
jabe78 said:
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Click to expand...
Click to collapse
I should've done more research myself. Galaxy was about to quit on me so I grabbed this one specifically because it was rated as one of the very top phones for development. If it wasn't such a rush I would've spent more time.
jtford said:
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
Click to expand...
Click to collapse
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Xryphon said:
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Click to expand...
Click to collapse
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
jtford said:
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
Holy ****.... finally! I just needed the OnePlus_usb_driver_setup.exe in order to install the right driver from said directory. Big thanks man. Really!
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
So it was actually 40 days, I don't know why I said 45. Anyway, even after (48 days), it took me calling TMOBILE and having someone talk to their (OEM team) and start a conversation with them. 3 days later I was able to SIM unlock the phone. I was able to toggle OEM unlocking. Did the Fastboot command to get the Unlock Code, and sent it to OnePlus for "7 days". What the crap is all of this hassle? I left Android and went to Apple for 7 years. When I left, you could unlock a bootloader in minutes. For being so keen on allowing us to unlock our phones, it seems they give you a Circus of Hoops to jump thru "on Their timeline". Anyway, I actually think I may have screwed up the code because it was displayed on two lines from Fastboot. I sent it as one line. Hoping they sort it out and I don't have to reapply and wait another 7 days. What a mess!
jabe78 said:
So it was actually 40 days, I don't know why I said 45...
Click to expand...
Click to collapse
Thanks for the update