The Free Google Drive space promotion was recently increased from 65GB to 100GB. So, there is more reason than ever to get this great offer.
If however, like me, you rooted your phone and found out you couldn't redeem it... and also read some people claiming that HTC wouldn't provide a code to redeem the offer because you had unlocked the bootloader... Follow the steps below to get this offer without dealing at all with HTC.
There are two primary obstacles to redeeming this offer. Since you rooted your phone, you have unlocked the bootloader. Even if you have relocked it using fastboot oem lock, this will still prevent the Drive App from displaying the offer screeen. The problem is that when you use fastboot oem lock, you are changing the status of the bootloader to ***RELOCKED*** . What you need is a factory default bootloader lock, which displays as ***LOCKED*** on the hBoot screen.
Plus, if you attain S-Off after unlocking your bootloader following HTCDev, it is very possible you will have a
*** TAMPERED ***
banner on your hboot screen. This must be removed as well.
HUGE thanks to Scotty1223 who first shared the methods for removing the TAMPERED banner and locking the bootloader to factory default several months ago. I am just consolidating those steps plus some other minor info into a sequential series of steps in one place for convenience.
These steps presume you have ADB installed, and have not changed your CID.
STEPS to GET TO STOCK FOR PURPOSES OF THE GOOGLE DRIVE PROMO.
1. Make a Nandroid backup using TWRP or CWM.
2. Get S-Off.
Use Sunshine or some other method to get S-Off. Link to Sunshine S-Off apk
3. Remove ***TAMPERED*** Banner.
If you have a ***TAMPERED*** banner on your hboot screen, follow the steps below (thanks to Scotty1223 for sharing this method). ADB must be installed!!! You can go to the first step of this thread to install a compact version
Connect your phone to your PC. Open up a terminal (as administrator in Windows...or as root in Linux) and cd to the adb directory (which contains fastboot, etc.).
Enter the following:
adb devices
You should see your device's serial number appear on the screen... If so, you are all good. If not, please check your ADB install..... there are many many guides to getting this set up.
Now we are going into the ADB Shell, which is like a terminal emulator from the OS on your phone. Enter the following:
adb shell
to enter the shell. You will be presented with a prompt... most likely it will be
[email protected]_m8: / $
Enter the following command to get root in ADB
su
[Very important note: You need this for superuser privileges on your phone... Make sure to wait for a prompt that looks like the following:
[email protected]_m8:/ #.
(if you are getting something different, don't worry... Just make sure there is a '#' at the end of the prompt)
If it hangs and only shows the first prompt like this:
[email protected]_m8: / $ <== note the '$' at the end
Then hit return in your terminal window on your PC (whether in windows or linux). It may exit automatically from the shell.
If this happens, it is because you have not used adb shell yet and have SuperSU (or Superuser) on default settings, which is to prompt the first time an app asks for root privileges. You should see a toast/dialog box on your phone that requests superuser permissions for "ADB Shell". Grant them, and then enter adb shell again from the terminal window on your PC. Now the root prompt (in red above) should show up in the terminal window.]
Now copy the line below and paste it into the terminal window on your PC at the root prompt:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
You should get something like this in response:
ock/mmcblk0p6 bs=1 seek=5314564 <
1+0 records in
1+0 records out
1 bytes transferred in 0.007 secs (142 bytes/sec)
If not, double check that you copied the above line correctly, that there are no spaces before the 'echo', and enter it again.
Then enter:
adb reboot bootloader
This will boot into hboot. Confirm that the ***TAMPERED*** is in fact not showing on the hboot screen.
Back in your terminal on your PC, enter:
fastboot reboot
to reboot the phone.
4. Lock the bootloader.
To lock the bootloader the correct way, you must follow the steps below. As far as I have determined, it is the same for all carriers of the HTC One M8. Again, a big thanks to Scotty1223 for this very cool route to locking the bootloader.
Like step 3, above, we are going into the ADB Shell, which is like a terminal emulator from the OS on your phone. If you do not have ADB installed on your PC, there are ample resources all over the internet for getting this installed...
Enter the following:
adb shell
to enter the shell. You will be presented with a prompt... most likely it will be
[email protected]_m8: / $
Enter the following command to get root in ADB
su
[IMPORTANT NOTE: See warning under Step 3 about getting a root prompt]
Then copy and paste this into your terminal on your PC:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
And lastly:
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
Confirm that your bootloader shows a ***LOCKED*** banner (and not ***RELOCKED***).
Back in your terminal on your PC, enter:
fastboot reboot
to reboot the phone
5. Getting to Stock.
****If you have NOT touched the stock Rom at all, nor deleted any system apps (essentially you have merely rooted and flashed a stock recovery) you can skip this step (no need to perform either step 5a or 5b). Just Reboot and finish with step 7.
To get the Google Drive storage you need to be running near to stock.. This means you need the stock firmware, and the stock Sense Rom (including all system applications). Many people will not have to worry about firmware or system applications. However, if you switched to an AOSP/AOKP Rom or a different kernel, then you do. Depending on your situation, follow step 5a OR step 5b.
5a. If you have switched to an AOSP/AOKP Rom, and are unsure about your firmware being correct and/or stock, an easy way to get all of the components which make up full stock (stock rom, stock firmware, stock hboot) is to flash an RUU from your carrier (see M8 forum for your carrier...there should be a roll-up thread with links and instructions to flash an RUU. NOTE: For anyone reading this thread that somehow managed to lock the bootloader without S-off, It is highly recommended NOT TO FLASH AN RUU WITH BOOTLOADER LOCKED AND S-ON. You must have S-OFF to flash an RUU with a locked bootloader).
5b. If you don't have to worry about firmware, but have deleted several system apps or otherwise altered the stock Rom, then you should restore a stock nandroid or find and flash a stock Rom. You should again go to the HTC One M8 forum for your carrier to get these items. If restoring a stock nandroid backup, make sure you have made a backup (as instructed in Step 1) so you have the right folder structure (whether you are using TWRP stock nandroid or a CWM stock nandroid) on the SD in which to place the stock nandroid.
6. Reboot.
7. REDEEM OFFER!
Go to the Play Store and uninstall any and all Google Drive updates (I did not have any, but in some cases Drive may have updated while you were rooted). After uninstalling any Drive updates, you should be able to go into the Drive app, and see the promo screen immediately and redeem the promo. If you do not see any screen with the offer, select "Product Tour" from the dropdown menu and go through the various "tour" screens. At the end it will show you the offer—it will probably be for 65GB. After you accept the offer however, it will say "an extra 50GB has been added to your Google Drive storage (so 65GB + 50GB = 115GB)
Again a big thank you to Scott1223 for the methods which allow us to go back and get this offer!!!
....and also thank you to jshamlet, kabuts, rcharliesam, phil.culler for helping me in some other threads!!!!
And exocetdj for his awesome help!!!!!!!
Please comment!
extremely well put out guide mate :good:
Maybe worth merging this with other thread so people have it all in one place?
One post for original method and then the next for this one? both brilliantly relevant
exocetdj said:
extremely well put out guide mate :good:
Maybe worth merging this with other thread so people have it all in one place?
One post for original method and then the next for this one? both brilliantly relevant
Click to expand...
Click to collapse
Is there a guide to get the Google Drive offer? I only saw various threads discussing it and threads explaining how to get back to stock...or Scotty1223's method to lock the bootloader.
I wouldn't have compiled a complete guide if there was one already. I hope I didn't miss it.
I started one in the other thread...but it was just a post in the third page of a thread discussing the Drive offer and discussing ways to get it (like contacting HTC, etc. (But thank you for reminding me-- I really should link that post to this thread since the guide in that post is old).
Let me know where the other guide is and I will try to get them merged or linked or something.
syntropic said:
Is there a guide to get the Google Drive offer? I only saw various threads discussing it and threads explaining how to get back to stock...or Scotty1223's method to lock the bootloader.
I wouldn't have compiled a complete guide if there was one already. I hope I didn't miss it.
I started one in the other thread...but it was just a post in the third page of a thread discussing the Drive offer and discussing ways to get it (like contacting HTC, etc. (But thank you for reminding me-- I really should link that post to this thread since the guide in that post is old).
Let me know where the other guide is and I will try to get them merged or linked or something.
Click to expand...
Click to collapse
HERE is is
They are about the same thing, may be better if everything is in the same place. have a word with the OP and see what he thinks then ask a mod, they should be able to help out
I got the 'not applicable due to tampering' error, but not going to bother with the hassle of relocking the bootloader. I probably would be interested in this offer if my BT Broadband wasn't so utterly dreadful that uploading anything takes a lifetime.
The offer's two years would be up by the time I'd finished uploading this year's holiday snaps
exocetdj said:
HERE is is
They are about the same thing, may be better if everything is in the same place. have a word with the OP and see what he thinks then ask a mod, they should be able to help out
Click to expand...
Click to collapse
That's just a thread debating ways some people were able to get it... Posts point to threads to lock the bootloader, and other posts state the tampered banner needs to be removed but no links.... It's a mess for anyone that doesn't understand what all needs to be done, nor how to do it.
That's why I compiled the thread here...it takes all the endless discussions, and just condenses it into a straightforward sequence of steps to get it.
syntropic said:
That's just a thread debating ways some people were able to get it... Posts point to threads to lock the bootloader, and other posts state the tampered banner needs to be removed but no links.... It's a mess for anyone that doesn't understand what all needs to be done, nor how to do it.
That's why I compiled the thread here...it takes all the endless discussions, and just condenses it into a straightforward sequence of steps to get it.
Click to expand...
Click to collapse
Fair point, as u were soldier!!!! :good:
Save yourself all this time/effort. Just chat with HTC support on their website. Takes less than 5 minutes and they email you a link to activate the extra space. I did this for both my phone and my wife's phone, when they had been unlocked for months already.
I was able to redeem the offer rather quickly, followed your directions, installed a stock rom, redeemed the promotion and nandroid back to Venom within 30 minutes. Mostly because I was reading like an idiot (totally exhausted from work.)
Thanks.
nomisunrider said:
Save yourself all this time/effort. Just chat with HTC support on their website. Takes less than 5 minutes and they email you a link to activate the extra space. I did this for both my phone and my wife's phone, when they had been unlocked for months already.
Click to expand...
Click to collapse
I think its luck of the draw... when this happened to me... I read everywhere, and out of everyone I spoke to who had to go to HTC because they couldn't redeem it through the Drive app, about 15% of them chatted with an HTC rep who either: (a) never asked them a single question and just sent them an email with a promo code link; (b) asked them to confirm that the caller "has not unlocked the bootloader or rooted their phone" (in which case the caller would need to lie and say "no sir! I would never do something foolish like that" and then get the email with the promo code), or (c) the rep asked them their IMEI, then said in a wry voice "I see you requested a bootloader unlock token...." (almost as if the rep was leading the caller to admit he unlocked the bootloader—and if he did...no promo).
The other 85% (who for the most part unlocked their bootloader using HTCDev) could not get the Drive deal because HTC had it on file they requested an unlock token... and in most of these cases, HTC was resolute on the offer being ineligible for those who unlocked their BL.
Given those odds—and the fear of choking if I called/chatted with HTC and had to lie—I opted to take the above steps and create a guide for anyone who needed it. Trust me... I would not have bothered to make it if it sounded like it was simple matter of contacting HTC.
I was debating going through all of this to get the offer since I'm cheap and don't want to pay for dropbox right now.
I did the online chat, and they didn't ask me any questions. I just said I tried to do it over crappy wifi connection early and it failed and now it won't redeem.
I have a Verizon edition however, so I can't unlock with HTC dev which is likely why I didn't get asked questions. My backup was to say something stupid like "unlock....? Like with my SIM code? Or the lockscreen code? Yea, I did that."
Fortunately they didn't ask and were really nice. But thanks for this guide; i was about to switch ROMs so I had just made a nandroid and was about to try and get it to redeem the hard way.
If you have Verizon or used Sunshine (or similar) I would try their support first.
Thanks very much for taking the time to write this guide.
In my case I was also just able to get in touch with HTC via chat and give them my IMEI, no need to relock, revert to stock etc.
I lost my 65gb free storage. Is there anyway to recover it?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
syntropic said:
I think its luck of the draw... when this happened to me... I read everywhere, and out of everyone I spoke to who had to go to HTC because they couldn't redeem it through the Drive app, about 15% of them chatted with an HTC rep who either: (a) never asked them a single question and just sent them an email with a promo code link; (b) asked them to confirm that the caller "has not unlocked the bootloader or rooted their phone" (in which case the caller would need to lie and say "no sir! I would never do something foolish like that" and then get the email with the promo code), or (c) the rep asked them their IMEI, then said in a wry voice "I see you requested a bootloader unlock token...." (almost as if the rep was leading the caller to admit he unlocked the bootloader—and if he did...no promo).
The other 85% (who for the most part unlocked their bootloader using HTCDev) could not get the Drive deal because HTC had it on file they requested an unlock token... and in most of these cases, HTC was resolute on the offer being ineligible for those who unlocked their BL.
Given those odds—and the fear of choking if I called/chatted with HTC and had to lie—I opted to take the above steps and create a guide for anyone who needed it. Trust me... I would not have bothered to make it if it sounded like it was simple matter of contacting HTC.
Click to expand...
Click to collapse
Interesting. I was one of those who unlocked the bootloader through HTCDev. I called HTC, the rep asked for my IMEI number, and I got the activation email within 5 minutes. No mention of unlocked bootloaders. I guess it really depends on how laid back the rep is.
adotkdotjh said:
Interesting. I was one of those who unlocked the bootloader through HTCDev. I called HTC, the rep asked for my IMEI number, and I got the activation email within 5 minutes. No mention of unlocked bootloaders. I guess it really depends on how laid back the rep is.
Click to expand...
Click to collapse
Who knows too if there has been an internal policy change? HTC's website (I can't remember where) states that you are not eligible for the storage if you unlocked your bootloader. About a month ago, the threads I saw on this topic were more of a warning to get it first and then root or else you can't get it.
But since this phone has been out for 6 months and a lot of upfront costs are reduced (for me, I paid $0 to get it under TMO), a lot more people are getting this phone.
Plus Google changed the promo from 65GB to 100GB about a month ago...so it's possible that HTC has encountered higher-than-expected number of purchasers who unlocked the bootloader and also want the Google Drive storage. And maybe recently they have decided relax their restrictions... I am sure that those who were told no were angry. I know that had I ended up calling/chatting with HTC and they said "sorry, you unlocked your bootloader", I would have been very upset.
syntropic said:
Who knows too if there has been an internal policy change? HTC's website (I can't remember where) states that you are not eligible for the storage if you unlocked your bootloader. About a month ago, the threads I saw on this topic were more of a warning to get it first and then root or else you can't get it.
But since this phone has been out for 6 months and a lot of upfront costs are reduced (for me, I paid $0 to get it under TMO), a lot more people are getting this phone.
Plus Google changed the promo from 65GB to 100GB about a month ago...so it's possible that HTC has encountered higher-than-expected number of purchasers who unlocked the bootloader and also want the Google Drive storage. And maybe recently they have decided relax their restrictions... I am sure that those who were told no were angry. I know that had I ended up calling/chatting with HTC and they said "sorry, you unlocked your bootloader", I would have been very upset.
Click to expand...
Click to collapse
Yeah policy change could definitely happened. Then again, I was dealing with HTC Canada, so that may have been the difference. I didn't even know the offer was changed to 100GB. Htc advantage website still said 65gb when I called htc to redeem the offer several weeks ago, and when I saw they gave me 100gb, I thought the extra space was their way of saying "sorry for trouble".
Just got my 100gb free through HTC chat. Very easy just needed my name phone number and email address :good:
Congratulations!
+100GB
added for 2 years
Go to Google Drive
But this guide is very much appreciated i was just hoping I wouldn't have to go this route. Thank you very much for taking the time to share
Less work necessary for me
i followed your great guide to redeem the Drive's extra space successfully however i only had to do the:
TEMPERED OUT Removed
UNLOCKED BOOTLOADER Removed
Running Viper without many stock apps
So i avoided all the returning to stock rom and nandroid backup.
Thanks again man
Hello,
thanks for this write-up! All you need to do is remove TAMPERED flag and LOCK bootloader. There is no need to go back to stock
Thanks one more time!
I was also able to get the offer after contacting the htc support via the live chat.
I didn't bothered with getting back to stock or anything - I just pinged them, was asked for my serial etc. and got an offer email with my 100GB.
No word about the htc dev token I have requested etc. - after about 3 minutes I received email stating that:
Based on your ticket ##TicketNumber## we have increased the storage space for your Google Drive account. In order to access the additional space, please visit the website via the link listed below.
and with the activation link...
---------- Post added at 09:21 PM ---------- Previous post was at 09:21 PM ----------
pastynko said:
Hello,
thanks for this write-up! All you need to do is remove TAMPERED flag and LOCK bootloader. There is no need to go back to stock
Thanks one more time!
Click to expand...
Click to collapse
True - on my M7, it was all about the locked bootloader....
Related
Has any one so far managed to unlock the bootloader and root the retail version of the tab. I'm asking cuz a friend is looking to get the retail version but won't get it unless its unlockable and root -able. Does pressing the vol down and power take you to recovery?
I know the io version has been rooted.
Sent from my GT-P7100 using XDA App
I am able to get into Recovery fine. Unfortunately there is no mounted sdcard, so although I can push with ADB, I cannot actually load the zip.
Just mount the file create the directory and place files there
Mount the ZIP?
Could someone please post exact instructions how to apply these zip files? As previously noted, we do not have access to the sdcard when booting into recovery. Thanks!
Yes please tell us how to mount /sdcard/
I have the retail version from Best Buy and /sdcard is not mounted. I tried to mount it but I don't seem to be able to. Also when I try to run fastboot devices it comes up blank but adb devices returns:
D:\android-sdk-windows\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
37C7046403FF217 device
I also tried in Ubuntu and same result... adb communication working, but fastboot executable can't see the device and I don't know how to get the /sdcard mounted using adb.
*** Please help ***
Please check the development forum. I bought mine from BestBuy on Friday, 16G metallic one. It is rooted.
The basic steps are to use nvflash to replace the stock bootloader with one that was from Googles IO tabs, then installing CWM, then rooting. Took me about 20 minutes.
xavierdylan said:
Has any one so far managed to unlock the bootloader and root the retail version of the tab. I'm asking cuz a friend is looking to get the retail version but won't get it unless its unlockable and root -able. Does pressing the vol down and power take you to recovery?
I know the io version has been rooted.
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
The threads you need are:
Retail 3.1 CWM - http://forum.xda-developers.com/showthread.php?t=1130574
If you use the above thread, then refer to this thread when you get to the "root like you have an i/o tab now" part of the instructions - http://forum.xda-developers.com/showthread.php?t=1074802
If your bootloader is locked (No padlock icon appears when you boot) http://forum.xda-developers.com/showthread.php?t=1131448
Sandelb said:
The threads you need are:
Retail 3.1 CWM - http://forum.xda-developers.com/showthread.php?t=1130574
If you use the above thread, then refer to this thread when you get to the "root like you have an i/o tab now" part of the instructions - http://forum.xda-developers.com/showthread.php?t=1074802
If your bootloader is locked (No padlock icon appears when you boot) http://forum.xda-developers.com/showthread.php?t=1131448
Click to expand...
Click to collapse
The above links worked for me. I have a 16GB Tab purchased from Best Buy.
On initial bootup I had the unlocked icon on the boot screen so I don't know if the same method works for tabs without the unlocked icon.
But here is something very important. The Samsung USB drivers for PCs are a mess. There are so many versions for different devices (I have had 7 other Samsung devices that all connect to my PC via USB) After having constant connection problems I realized that the simple solution was to go to a "clean" PC (one that had never had Samsung USB drivers installed) and install nvflash per the instructions. Without the legacy Samsung USB drivers the nvflash method worked flawlessly.
Hello
Is there any chance of unlocking the locked bootloader for the SGT ??
guys I dont think I have seen any recent posts by anyone claiming theirs is locked. I have a locked white 16gb that I had got at the launch on the 8th but I am pretty sure most if not all of the tabs are unlocked at stores.
If someone can show a post indicating the user got it sometime between the 17th and now and it being locked, please indicate so
Some still locked...
Had a launch unit that was locked. Returned it for the metallic one on the 20th and wound up with another locked one.
Rooted using the above linked instructions though, worked like a charm.
NyPlaya513 said:
guys I dont think I have seen any recent posts by anyone claiming theirs is locked. I have a locked white 16gb that I had got at the launch on the 8th but I am pretty sure most if not all of the tabs are unlocked at stores.
If someone can show a post indicating the user got it sometime between the 17th and now and it being locked, please indicate so
Click to expand...
Click to collapse
I got mine on the launch from Best Buy and it was locked. 16GB metallic WiFi model.
So basically whether you get a locked or unlocked bootloader is a free for all?
What gives Samsung...
Could they potentially release an update unlocking the bootloader for everyone?
meeekael said:
So basically whether you get a locked or unlocked bootloader is a free for all?
What gives Samsung...
Could they potentially release an update unlocking the bootloader for everyone?
Click to expand...
Click to collapse
From what I've been hearing you're just lucky. There are some that are unlocked but the majority are locked. I doubt Samsung will be releasing anything to help but, I'd keep up in the forums, someone smarter than us will fix the issue for them!
Retail Roulette?
So, I've been kind of interested in this and, since I work at Best Buy's Geek Squad I've got a chance to check out the SGT's that get returned. It really does seem kind of random. I've seen 3 so far, 2 16GB's and 1 32GB returned since launch. The 32GB was unlocked as was one of the 16's. So, I don't know what the deal is... perhaps poor QC at Samsung manufacturing? Got me, LoL!
I have just recently started my journey into rooting, I've been in research mode for about a week trying to learn as much as I can but it's SO overwhelming trying to keep up with all the old and new techniques - trying to find out what is the best method to use.
Before discovering this place I asked a few questions on reddit and was able to get a cheat sheet on all the terms one needs for rooting:
https://www.reddit.com/r/androidroo...ingroot_considered_true_rooting_where_is_the/
and while browsing Xda I found this short guide:
http://forum.xda-developers.com/htc-one-m8/help/how-to-root-htc-one-m8-android-6-0-t3420748
However both of theses sets of instructions miss out a few starting points.
I've watched a few videos on how to root a htc but they've all been made around the time of the phones release, and as we all know each year things get bigger and better in computing, so new techniques might have arrived. So I wanted to ask here what are the full sets of instructions to root a htc one m8 in 2016, starting from watch software to use to back up your phone, how to unlock the bootloader, etc... and using whatever new rooms and kernels people have been using and would recommend.
My aim is, with your help, to make this post a place beginners can go to learn how to do their first root. thankyou in advance.
My phone:
service provider: Orange/EE (UK)
Android: 6.0 (Marshmallow I think)
HTC sense version: 7.0
Sofware number: 6.12.61.4
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
ieatabiscuit said:
How are you getting S-off that isn't free? I had S-off within a week of owning my phone back when it was new, and I'm on Verizon, they are the devil when it comes to modding anything. Have you looked into Sunshine?
Click to expand...
Click to collapse
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
3mel said:
the "not free" S-off I'm referring to is sunshine, unless things have changed (if they have I'll be delighted).
Click to expand...
Click to collapse
Just rechecked into it to refresh my memory, as I've been S-off so long I forgot the method I had used. It was in the pre-Sunshine days. I used Firewater to get S-off (thought Sunshine sounded odd to me for some reason). Didn't cost me anything but a couple minutes of my time. Hope that helps. I wouldn't want to pay for S-off either, it's not really something that I think many people would want to do...
---------- Post added at 06:53 AM ---------- Previous post was at 06:47 AM ----------
GreiverX said:
hello guys,im looking forward rooting my m8,is there any method to root my phone without void my warranty?(i mean if i unroot my phone will still be on warranty?)
Click to expand...
Click to collapse
If you have a way to revert it and become S-on again (assuming you're S-off also) I would say you could hide the fact it's been rooted by unrooting and removing any root apps, but don't quote me on that. I rooted back when mine was new, and never looked back at the warranty. Now my phone would have had the warranty expire anyway, so it still doesn't matter. When in doubt, assume the warranty to be void upon rooting, but research a way to revert if it's possible. Not like we have to bother with KNOX at least.
only way is USD $25 for sunshine....can't S-OFF it without other ways.
WingZer0n said:
only way is USD $25 for sunshine....can't S-OFF it without other ways.
Click to expand...
Click to collapse
then why does firewater say different?
grrmisfit said:
then why does firewater say different?
Click to expand...
Click to collapse
firewater doesn't work anymore unfortunately. Only way to get S-Off now is sunshine @ USD 25.
3mel said:
I've just rooted my phone unlocking the bootloader yesterday. I haven't gone S-off yet.
I'm coming from Samsung phones so things are a little different for me too. I followed this guide which covers everything you can and will need to gain full root on an m8
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
to get root apps to have all the ability they have elsewhere you need to cover 3 steps
1) unlock the bootloader, which will make some partitions accessible, but writing to the system partition is still blocked apart from via custom recovery (the phone reboots when you try to write into the system partition without "full root").
2) root. fairly obvious what that is.
3) gain S-off, which makes system partition accessible outside of the custom recovery. the phone can be enjoyed the same as any other rooted device at this stage. **this can only be done one way, and that one single way isn't free.**
you want to have all the stages mentioned in that link covered apart from the last firmware guide which is more optional.
Click to expand...
Click to collapse
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Nebster7 said:
Hi I can't root mine . Every time I try to get token it says that it's a incorrect file batch path or something like that? Do you know what the problem is?
Click to expand...
Click to collapse
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
redpoint73 said:
Please stop making new posts in different threads. It won't get your issue fixed any faster. It just confuses those trying to help you, leaving incomplete bits of info here and there. Just stick to one thread, specifically the one where I am already trying to help you.
Click to expand...
Click to collapse
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
---------- Post added at 02:56 AM ---------- Previous post was at 02:38 AM ----------
Nebster7 said:
Sorry. I have my issue fixed now as I just needed to type cmd on the top of the window to get token to unlock bootloader token. Flashed aicp 14.0 working excellent. Much faster, better battery oh only arm 9.0 pico seemed like the best gapps as I tried other ones didn't work. Man it took a lot of searching to do this as things are posted all over the place
Click to expand...
Click to collapse
Just one thing my PC doesn't see my phone now.???
Nebster7 said:
Just one thing my PC doesn't see my phone now.???
Click to expand...
Click to collapse
Meaning what exactly? Doesn't see storage (did you select the option on the phone to allow data transfer?) or adb or fastboot? Booted to the custom ROM, or something else (bootloader, recovery)?
When asking for help, please give as much information as possible. One sentence is really never enough info to go on.
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
back to official rom, before that
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
r_w said:
I bought a used Essential (love it!). It came with the bootloader unlocked, so every reboot I get the "your device software can't be checked for corruption. Please lock the bootloader."
I am not really concerned about that (should I be?), but when I try to set up Google Pay I get this:
"Couldn't finish setup to pay in stores. This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
I'm not sure that the Pay issue is because of the unlocked bootloader, but I don't need it rooted/unlocked, so I might as well re-lock to eliminate it as an issue.
There's a lot of info on the forums about *not* relocking when you have a custom rom, but I'm pure Pie.
So - is there a straightforward way to relock? I have things backed up/etc.
Click to expand...
Click to collapse
Look at the other threads about rooting.
You can do a couple of things to solve the issue:
Install ElementalX kernel
Install Magisk
VoidWalkerAlpha said:
First of all make sure you are pure stock
Then boot into fastboot by holding vol- and power button together.
Download android platform tools https:REMOVEME//developer.android.com/studio/releases/platform-tools?hl=th, unzip it, go into the folder, open cmd there, and type
Code:
fastboot flashing lock
And it's finished!
Click to expand...
Click to collapse
Perfect! Flashed the latest original from Essential per HapRow's comment, pulling from Essentials current build website.
Had to wait a long time to restore everything. Then the "fastboot flashing lock" erases everything, so I had to restore again.
Took a while, but was thankfully uneventful.
And now Google Pay works!
Thank!
As most of you know if you try to enroll your 3A device into the Preview Program, it will not show up and will see that Google is preventing them until June. However you can still install the official build directly from Google now which includes the May 5th, 2019 Security Patch.
Don't use the Factory image, as a lot of people are taking advantage of carrier specific promotions, most of these devices cannot yet be OEM Unlocked until they are SIM unlocked. So you will not be able to install the Factory Image unless that condition is met.
You can Sideload the OTA.
Keep in mind you will be installing Beta software on your device and doing so at your own risk.
I will be writing this guide in the perspective for someone who has never installed a custom rom or used ADB before on a PC.
Ensure your device is setup and you can access the home screen.
Swipe down from the top to access the settings menu.
Scroll down to and click "About Phone."
Scroll to "Build Number", tap on it 6 times in a row until it says developer options enabled.
Click back in the setting menu.
Click on "System"
Click the "Advanced" Dropdown.
Click "Developer Options"
Scroll down to "USB Debugging" and enable it, accept the warning.
Download the "SDK Platform Tools" from here: https://developer.android.com/studio/releases/platform-tools.html
Unzip them to a folder on your desktop.
Download the latest "Full OTA Image" from here: https://developer.android.com/preview/download-ota (3A Files were removed, I have mirrored the non-XL OTA, but I don't have the XL)
Pixel 3A: sargo-ota-qpp3.190404.015-dde326a4.zip (https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc)
Pixel 3A XL: bonito-ota-qpp3.190404.015-d4e9922f.zip (No current mirror)
Move that ZIP file into the Platform Tools folder on your desktop, do not unzip it.
Connect your Pixel to your PC via the USB A to C cable, the driver should automatically install.
A popup will appear on your pixel to grant debugging access to the connected computer, allow it.
Open the "Platform Tools" folder on your desktop, click the file explorer bar where it says "This PC>..." and type "CMD" and click enter, it will open the command prompt with access to that folder.
Enter the following command
Code:
adb reboot recovery
The phone will reboot, when it goes to a screen with the android mascot and exclamation mark hold the power button and click volume up this will access the recovery menu.
Select "Apply update from ADB." and hit the power button to choose it.
Enter this command into command prompt on the PC
Pixel 3A:
Code:
adb sideload sargo-ota-qpp3.190404.015-dde326a4.zip
Pixel 3A XL:
Code:
adb sideload bonito-ota-qpp3.190404.015-d4e9922f.zip
It will take a couple minutes, once done hit "Reboot System Now"
Congratulations, you are now on the official Android Q Beta 3 software for Pixel 3A!
Thanks for the mirror
I've been around this place for a while, but the Pixels have been a bit tricky. Just to clarify, the only prerequisite to flash is to be OEM unlocked?
I've never sideloaded like this, especially with the default bootloader/recovery.
Lastly, can we revert back if need be?
stevew84 said:
I've been around this place for a while, but the Pixels have been a bit tricky. Just to clarify, the only prerequisite to flash is to be OEM unlocked?
I've never sideloaded like this, especially with the default bootloader/recovery.
Lastly, can we revert back if need be?
Click to expand...
Click to collapse
If you want to flash the Factory Image than you need to be OEM Unlocked.
If you're not you can Sideload the OTA via the method in the main post.
I've updated the main post with a mirror for the 3A OTA: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Bulls729 said:
If you want to flash the Factory Image than you need to be OEM Unlocked.
If you're not you can Sideload the OTA via the method in the main post.
I've updated the main post with a mirror for the 3A OTA: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Click to expand...
Click to collapse
Thanks. Reverting back via same method?
crackedvenom2 said:
Latest version I see is sargo-qpp3.190404.015-factory-29c0085a.zip and I'm getting
E: footer is wrong
Update package verification took 0.1 s (result 1).
E:Signature verification failed
E:error:21
Installation aborted.
Do I have to factory reset or anything? It's been a little bit since I flashed anything but I know I followed the instructions except the version you show isn't on there. Can you make a mirror? Could it possibly be that? The version I'm finding is sargo-qpp3.190404.015-factory-29c0085a.zip
Click to expand...
Click to collapse
The file you mentioned is the factory image, which you can't use unless OEM unlocked, you need to sideload the OTA image using those steps, they were removed but heres a mirror: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Thank you! I thought I was out of luck, but couldn't complain because by turning in an S8 it's a free pixel.
Now it's a free pixel with Android Q
So confirmed working using the Mega linked OTA and sideload method?
stevew84 said:
So confirmed working using the Mega linked OTA and sideload method?
Click to expand...
Click to collapse
I'm sure you'd like another source, but the MEGA mirror is the exact file I downloaded from the Google Dev Page prior to it being removed. I'm just bummed I didn't grab the XL OTA zip.
Bulls729 said:
I'm sure you'd like another source, but the MEGA mirror is the exact file I downloaded from the Google Dev Page prior to it being removed. I'm just bummed I didn't grab the XL OTA zip.
Click to expand...
Click to collapse
Oh no I don't care about the source. Just curious if the file itself and the method you provided is working for everyone.
EDIT: Confirmed working.
Bulls729 said:
The file you mentioned is the factory image, which you can't use unless OEM unlocked, you need to sideload the OTA image using those steps, they were removed but heres a mirror: https://mega.nz/#!iWhFXaIL!O0fIHTWivEZR8My9q2C9AtEVO7uxJIPQIf51sKUFrTc
Click to expand...
Click to collapse
Yes thank you. I had edited the post once I saw you provided mirrors
Just out of curiosity, is anyone keeping track of 'known' bugs? I think it should be an edit attached to these kinds of posts if there are any major ones only one I know of so far is listed below:
-Samsung Wearable (does not open at all or communicate with watch)
Vonsk said:
Just out of curiosity, is anyone keeping track of 'known' bugs? I think it should be an edit attached to these kinds of posts if there are any major ones only one I know of so far is listed below:
-Samsung Wearable (does not open at all or communicate with watch)
Click to expand...
Click to collapse
The Top Issues are listed here: https://developer.android.com/preview/release-notes
you can also file bug reports there as well.
Sent from my iPhone using Tapatalk
Bulls729 said:
The Top Issues are listed here: https://developer.android.com/preview/release-notes
you can also file bug reports there as well.
Click to expand...
Click to collapse
I followed that link and did not see mention of the bug I just listed, which I did indeed file. I followed up on it and it was actually reported as a duplicate since others have already reported it (which leads me to call it a known issue). The only thing I found was some vague "financial apps might not work as expected" and that's about it.
I know it's hard to ask for here, but things that are lay-user or layperson friendly are SUPER NICE. Just calling out that Samsung Wearable literally doesn't work at all right now I think is nice for people to know going into it. *shrug*
It is still possible to find the original images for both 3a devices on the "Downloads for Pixel" page on the android developer website, the forum won't let me post the link.
ClawMacaw said:
It is still possible to find the original images for both 3a devices on the "Downloads for Pixel" page on the android developer website, the forum won't let me post the link.
Click to expand...
Click to collapse
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Sent from my iPhone using Tapatalk
Bulls729 said:
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see. How embarrassing, I didn't realize there was a difference between the OTA and the factory images.
CAExempt said:
How would I go about reverting back to Pie? I've downloaded the correct image file for Pie on the Pixel 3a (non XL)
Click to expand...
Click to collapse
If you have a device that is able to be OEM Unlocked you can restore using the Factory Image. If not you can go to this reddit link which shows information to context Pixel Support to revert your device.
https://reddit.com/r/android_beta/comments/bpjxhb/pixel_3axl_and_android_beta/
Bulls729 said:
Yes the Factory images are and have still been up, but these are only useful to those who have a device that is OEM Unlocked. A good amount of people took advantage of the T-Mobile $400 credit trade in. And those devices are not able to be OEM Unlocked until they get a SIM unlock, while silly they tied the SIM Unlock status to the OEM Unlock ability. So for those with OEM Locked phones they can only use the side-load procedure wit an OTA zip which have been removed.
Click to expand...
Click to collapse
The other problem is that when you unlock bootloader, you don't pass safetynet (so apps like Google pay, boxer, many banking apps, etc won't work at all). You could unlock bootloader, flash Q beta 3 image, then relock bootloader, but unlocking it wipes your phone so you'd need to set up from scratch. Wait for the beta ota and you won't have to wipe to use Q
OTA sideload won't erase data, correct?
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