As title suggests, didn't know if this is possible or not.
Nitemare3219 said:
As title suggests, didn't know if this is possible or not.
Click to expand...
Click to collapse
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
jollywhitefoot said:
I recommend against it. What's your reason for wanting to do this? There's really not much benefit to doing it.
But it's certainly possible and simple to do.
Click to expand...
Click to collapse
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Nitemare3219 said:
I may be wanting to return my 10 - was a purchase directly from HTC. Just not sure if it fits my wants as a device. Their return policy doesn't say anything about reusing unlocked devices, but I felt that may be bad if I returned it unlocked.
Click to expand...
Click to collapse
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
If you want to relock your bootloader for warrenty, you'll have to S-OFF first and use some device-specific procedure(which hasn't released yet) to make it completely stock-like again.
Stephen said:
Moderator Information,
I have removed the above two posts. The commands given are device specific commands. If used on another device, it could brick the phone.
Click to expand...
Click to collapse
thank you I apologize for the mishap
Mark112887 said:
thank you I apologize for the mishap
Click to expand...
Click to collapse
As an aside if you do run that specific command on this device you will end up with some serious problems.. the adb echo command of the past devices is more.
Sent from my HTC6545LVW using Tapatalk
jollywhitefoot said:
Well if you received an unlocked code from htcdev, they will be able to tell you unlocked it, so I'm not sure how much it matters. Also, even if they didn't check the htcdev database, when you relock, your bootloader will show "relocked" instead of "locked".
I'm not sure what their return policy is on unlocked devices. Good luck.
Oh, and if you want to relock it, just go to download mode and enter "fastboot oem lock" in a command window.
Click to expand...
Click to collapse
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Rijul30 said:
I tried "fastboot oem lock" but it bounced back with a failure saying it's an unknown command. I tried a few other commands as well.
Fastboot flashing lock
Fastboot lock_bootloader (which was in the command list )
Fastboot OEM relock
But none worked. Need help.
Click to expand...
Click to collapse
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
adriano25028 said:
You can use All in one toolkit to relock bootloader
https://forum.xda-developers.com/htc-10/development/tool-htc-10-m10-one-toolkit-v1-0-t3538317
Click to expand...
Click to collapse
Will it wipe the device ?
Rijul30 said:
Will it wipe the device ?
Click to expand...
Click to collapse
Yes.
adriano25028 said:
Yes.
Click to expand...
Click to collapse
Thanks !
Related
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
Fastboot flashing lock.
toknitup420 said:
Fastboot flashing lock.
Click to expand...
Click to collapse
does this work? anyone tried?
mgear356 said:
does this work? anyone tried?
Click to expand...
Click to collapse
LOL of course it works, the command is directly from Google.
That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
That easy! Here are the instructions from Google:
https://developers.google.com/android/images
Tells you the commands to unlock, flash stock rom and re-lock the bootloader...
This ain't no iPhone, son! Lol
You are allowed to do this stuff. All of the software to lock and unlock are provided by Google...
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Cheers mate.. Was worried as my last phone was 6p.
My first pixel lol..
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
Why you returning the phone in the first place?
Jiggs82 said:
Why you returning the phone in the first place?
Click to expand...
Click to collapse
Returning it to Google and re buying elsewhere for at least $200 less.
vibrantliker said:
If I'm rooted can I just relock the bootloader and it will wipe the system or do I need to flash stock from google's website then relock if I want to return it?
Click to expand...
Click to collapse
when you lock or unlock, it wipes the phone.
uicnren said:
when you lock or unlock, it wipes the phone.
Click to expand...
Click to collapse
Just that I read in a couple of places when re locking some have had a "no os installed" result.
enginuity2 said:
I bought my Pixel 2 XL from Google and I know they have a 15 day return policy but I don't know if unlocking the bootloader voids that. Can I re-lock the bootloader? Has anybody else returned their phone to Google?
Click to expand...
Click to collapse
You don't need to lock bootloader to return..I returned multiple devices without locking
vibrantliker said:
Just that I read in a couple of places when re locking some have had a "no os installed" result.
Click to expand...
Click to collapse
simply flash both partitions first then.
Just wipe it and ship it. Google will only inspect it for physical abuse and water damage. The don't care if it's unlocked. It Google, the sell us unlocked phones. I too have sent them back unlocked as have many others.
I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.
vibrantliker said:
I just flashed the latest factory image then did a factory reset before I was going to re lock the bootloader. Now the oem unlock option on my phone is greyed out and adb/fastboot fives me errors trying to fastboot oem lock or fastboot flashing lock.
Click to expand...
Click to collapse
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.
TonikJDK said:
The slider will stay gray until the fastboot commands relock it. What are the errors you are getting. Exact wording please.
Really, just ship it as is.
Click to expand...
Click to collapse
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?
vibrantliker said:
I'll try again tomorrow and get back.
You said earlier they just check for physical damage. Don't they turn on the phone?
They shouldn't care when the locked boot loader screen shows at boot?
Click to expand...
Click to collapse
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.
mac796 said:
I sent one back with the bootloader unlocked they don't care. I'd make damn sure it's completely stock before you relock it maybe Flash the factory image to both slots just to be sure.
Click to expand...
Click to collapse
It is completely stock, but what does that mean
"Flash the image to both slots"?
vibrantliker said:
It is completely stock, but what does that mean
"Flash the image to both slots"?
Click to expand...
Click to collapse
Go to Google's factory image page download January's image and do the flash all to slot a. Then change to slot B.
Fastboot --set-active=b then flash all to slot B. Probably Overkill but you'll for sure be stock. Then issue you're relock command to both critical and the regular bootloader one. For one you need to make sure your fastboot is current if it's not up to date you're probably going to have problems.
Edit. I would just send it back the way it is
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Az Biker said:
When I first got my device, everyone was talking about unlocking it with fastboot unlock.... Now I'm seeing several comments that fastboot unlock critical is needed.
Would someone be so kind as to share the difference, and the purpose for each of these?
I ran fastboot unlock back in October, and my device shows "OEM Unlocking" greyed out (bootloader is already unlocked)..
So now I'm wondering if I need to run fastboot unlock critical?
Thanks in advance...
Click to expand...
Click to collapse
Only if you want to update the bootloader. That's the only thing I can see that critical does.
Sent from my Pixel 2 XL using Tapatalk
I believe unlock_critical is necessary if you want to be able to flash updates manually..
"For Pixel 2 XL only: the critical partitions may also need to be unlocked before flashing. The unlock can be performed with this command, and should NOT be done on other devices:
fastboot flashing unlock_critical
If you are updating an older device, run this command:
fastboot oem unlock "
Above quote is from Google Factory Image page.
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Badger50 said:
You can just run it again. However, it WILL wipe your phone. Which is why I did mine back to back when I got the device. :good:
Click to expand...
Click to collapse
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Az Biker said:
What all have you done to your phone so far?
Once I get home tonight, I plan to:
-start fresh with unlock_critical
Then follow nathanchamce's guide to
-sideload nov update
-root,
-install Nathan's kernel
Click to expand...
Click to collapse
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Wickidmasshole said:
I ran the basic fastboot unlock when i first got the phone before i knew about the unlock_critical, so I went back recently to run the fastboot unlock critical and it would fail each time telling me the boot loader was already unlocked, even after i went and re-locked it just to run this command. Very interested to know if you can get it to work if you've already previously unlocked your bootloader because i had no luck
Click to expand...
Click to collapse
This is why I asked the question. I wasn't sure if doing the basic unlock prior to the critical unlock would be an issue.
I'm running the critical unlock when I get home tonight (I want to be able to update the bootlader in the future), I'll let you know what I run into, if anything.
Az Biker said:
Did you use a guide? A tool (wugs or skips)?
Did you run into any issues?
Click to expand...
Click to collapse
Didn't use any toolkits, just these 2 guides....
https://forum.xda-developers.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176 https://forum.xda-developers.com/pixel-2-xl/how-to/guide-magisk-root-snoke-kernel-t3701930
....and didn't run into any problems at all. My P2XL is just humming right along. The battery on this thing is phenomenal! Takes me a good 2 days to knock it down to 10% :good:
Now we just need some TWRP to get Beans up and running :good::good:
Badger50 said:
Just flashed the November update with fastboot, rooted with magisk using Snoke kernel, got V4A, AdAway, and TiBu up and running. Going to give Nathan's kernel a try in the next couple of days :good:
Click to expand...
Click to collapse
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
iamjimmy said:
Could you please tell me where you got Adaway and Viper4Android from? If I go to the OPs of these, the versions don't work on Pixel 2 XL. Thanks in advance.
Click to expand...
Click to collapse
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Badger50 said:
I'm using the AdAway from here.....https://androidfilehost.com/?fid=817550096634744719
Using the V4A module that I downloaded from the Magisk Manager app. To use V4A, you'll need to disable Music FX app that comes from the factory images :good:
Click to expand...
Click to collapse
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Sent from my [device_name] using XDA-Developers Legacy app
slaydog said:
Which V4A module did you download, if you don't mind? There are 3 in Magisk...
Click to expand...
Click to collapse
This one :good:
Az Biker said:
thanks for the responses.
Since I already ran fastboot unlock, can I just run fastboot unlock_critical? Or do I need to do anything additional prior to running critical?
I've read @nathanchance 's guide where it says run one or the other, but haven't seen anything about running unlock prior to critical.
Thanks again!
Click to expand...
Click to collapse
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
marbertshere said:
Hey, I have this exact same question. I originally unlocked it with the regular unlock command. Can I just run the critical command or do i have to relock the bootloader? How did you do it? Thanks!
Click to expand...
Click to collapse
I've unlocked the ordinary bootloader first, then the bootloader_critical without any problems :good:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
jaybird779 said:
I got a replacement Pixel 2 XL and wanted to do unlock_critical from the outset. So, I enabled oem unlock, booted to bootloader, ran the command, the phone prompted me to unlock, which I did. I rebooted and it wiped my data. I thought I was all set. So, I setup my phone. I then went to root with Magisk and it told me I wasn't unlocked. I booted back into OS and it also showed that the bootloader wasn't unlocked. It's definitely a Google version (not Verizon). I rebooted into bootloader and ran the regular fastboot flashing unlock command and it wiped and rebooted to an unlocked bootloader. SO... what happened the first time? Has anyone seen this? Confused, I searched around online and found this link:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-2-pixel-2-xl-0180707/
It says that when you send the fastboot flashing unlock_critical, you *also* need to send the fastboot flashing unlock command when you are prompted to confirm the unlock on the phone. Did anyone else have to do this? The instructions on XDA do not indicate this step and I don't see comments that others' phones still showed as locked when only using the unlock_critical command.
I tried booting into bootloader to run the unlock_critical command again and it says my bootloader is already unlocked, but there's no indication whether I have critical unlock or regular. I know I could lock it again and try to enter the instructions as provided on that site. However, I'd prefer not to reset my phone again.
Thoughts?
Click to expand...
Click to collapse
The bootloader_critical unlock has to be performed only if you want to flash the bootloader (e.g. when you flash a factory image), but, if you want to perform all the other operations, such as rooting, kernel flashing, etc., you have to unlock the ordinary bootloader, too.
So, these are the two Fastboot commands:
fastboot flashing unlock_critical (for bootloader flashing, you've already performed this)
fastboot flashing unlock (for all the other operations)
The request which appears on your phone, when you enter these two commands, is the same, and you have to allow the bootloader unlock in both cases :good:
Hey everyone is this possible to do if so how?
xcha0tic said:
Hey everyone is this possible to do if so how?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...ol-tool-one-driversunlocktwrpfactory-t3730226
Haven't used this tool but I would look at this as a possible solution for locking bootloader.
xcha0tic said:
Hey everyone is this possible to do if so how?
Click to expand...
Click to collapse
If you are planning to return or sell the device.
1. Do a factory reset.
2. Make sure OEM unlocking and USB debugging are set to ON in the developer options.
3. Reboot into bootloader mode.
4. Run "fastboot flashing lock"
5. Then run "fastboot flashing lock_critical
The last two commands will wipe your phone again. Your bootloader should then be locked.
If your not planning on returning or selling your device. Then just leave it unlocked. That is all ?
Badger50 said:
If you are planning to return or sell the device.
1. Do a factory reset.
2. Make sure OEM unlocking and USB debugging are set to ON in the developer options.
3. Reboot into bootloader mode.
4. Run "fastboot flashing lock"
5. Then run "fastboot flashing lock_critical
The last two commands will wipe your phone again. Your bootloader should then be locked.
If your not planning on returning or selling your device. Then just leave it unlocked. That is all
Click to expand...
Click to collapse
I flashed elemntal kernel would flashing back to stock or the reset take it back to stock kernel?
xcha0tic said:
I flashed elemntal kernel would flashing back to stock or the reset take it back to stock kernel?
Click to expand...
Click to collapse
Flashing back to stock will install the stock kernel :good:
Badger50 said:
If you are planning to return or sell the device.
1. Do a factory reset.
2. Make sure OEM unlocking and USB debugging are set to ON in the developer options.
3. Reboot into bootloader mode.
4. Run "fastboot flashing lock"
5. Then run "fastboot flashing lock_critical
The last two commands will wipe your phone again. Your bootloader should then be locked.
If your not planning on returning or selling your device. Then just leave it unlocked. That is all
Click to expand...
Click to collapse
Hey Badger50, When I did this, I was able to perform the fastboot flashing lock and then rebooted into the bootloader (after phone loaded up again) and attempted to do "fastboot flashing lock_critical" but nothing happens, it just says "waiting for any device'" Should I be concerned? Thanks for your help!
kryptonite_2448 said:
Hey Badger50, When I did this, I was able to perform the fastboot flashing lock and then rebooted into the bootloader (after phone loaded up again) and attempted to do "fastboot flashing lock_critical" but nothing happens, it just says "waiting for any device'" Should I be concerned? Thanks for your help!
Click to expand...
Click to collapse
Nothing to be worried about. I've seen a few folks have that issue. Just outa curiosity, what do you get when you run....fastboot oem device-info.......?
Badger50 said:
Nothing to be worried about. I've seen a few folks have that issue. Just outa curiosity, what do you get when you run....fastboot oem device-info.......?
Click to expand...
Click to collapse
Well it did say:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
So I tried it again and it seems to have gone through the motions of locking it again. Now it says:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
Honestly have no idea what I did to make it work haha. I factory reset just because and was signing in to Google whenever I got the notification that you responded. Either way, I'm all locked up now. Thanks!!!
kryptonite_2448 said:
Well it did say:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
So I tried it again and it seems to have gone through the motions of locking it again. Now it says:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
Honestly have no idea what I did to make it work haha. I factory reset just because and was signing in to Google whenever I got the notification that you responded. Either way, I'm all locked up now. Thanks!!!
Click to expand...
Click to collapse
There ya go bruh! :good::good:
I want left a custom rom on my phone and unroot it, is this possible? I need to put apps on which check for root access
prv8droid said:
I want left a custom rom on my phone and unroot it, is this possible? I need to put apps on which check for root access
Click to expand...
Click to collapse
Sure. Just dirty flash the rom again, but don't flash root :good:
Badger50 said:
If you are planning to return or sell the device.
1. Do a factory reset.
2. Make sure OEM unlocking and USB debugging are set to ON in the developer options.
3. Reboot into bootloader mode.
4. Run "fastboot flashing lock"
5. Then run "fastboot flashing lock_critical
The last two commands will wipe your phone again. Your bootloader should then be locked.
If your not planning on returning or selling your device. Then just leave it unlocked. That is all
Click to expand...
Click to collapse
Is this still correct procedure after 18 months? I guess no more critical unlock. Anything else different?
srqrob said:
Is this still correct procedure after 18 months? I guess no more critical unlock. Anything else different?
Click to expand...
Click to collapse
Nothing has changed except the critical unlock part :good:
Thanks for the help. Gosh, middle of the night post. I follow enough to know you're pulling back a bit. Hope all is good with you.
srqrob said:
Thanks for the help. Gosh, middle of the night post. I follow enough to know you're pulling back a bit. Hope all is good with you.
Click to expand...
Click to collapse
All is well my friend, but thanks for asking. Real life with the family has changed things a bit, in a good way that is! Not to mention that I'm just waiting for the P4XL, and many to most of the things about the P2XL have been answered many times over. But no worries, I'm still lurking around from time to time
Badger50 said:
If you are planning to return or sell the device.
1. Do a factory reset.
2. Make sure OEM unlocking and USB debugging are set to ON in the developer options.
3. Reboot into bootloader mode.
4. Run "fastboot flashing lock"
5. Then run "fastboot flashing lock_critical
The last two commands will wipe your phone again. Your bootloader should then be locked.
If your not planning on returning or selling your device. Then just leave it unlocked. That is all
Click to expand...
Click to collapse
Will this command unroot the phone as well? Thanks
billgufran said:
Will this command unroot the phone as well? Thanks
Click to expand...
Click to collapse
Most definitely :good:
This is my first OnePlus device so I'm a little confused. I've followed a bootloader unlock guide found here; however, it says my device will be wiped once it is unlocked. Problem is, the device isn't wiping so I can only assume it hasn't unlocked. Can someone point me to a guide that works?
I've already got my unlock_code.bin file from OnePlus and I flashed it before trying the unlock commands. Every command claimed to be successful; yet, there seem to be no changes whatsoever.
Try "fastboot oem device-info" without quotes, to get bootloader info. Should tell you if it's unlocked or not
Allen77777 said:
Try "fastboot oem device-info" without quotes, to get bootloader info. Should tell you if it's unlocked or not
Click to expand...
Click to collapse
I'll give this a go tomorrow when I get back to my computer. Thanks
noxarcana said:
This is my first OnePlus device so I'm a little confused. I've followed a bootloader unlock guide found here; however, it says my device will be wiped once it is unlocked. Problem is, the device isn't wiping so I can only assume it hasn't unlocked. Can someone point me to a guide that works?
I've already got my unlock_code.bin file from OnePlus and I flashed it before trying the unlock commands. Every command claimed to be successful; yet, there seem to be no changes whatsoever.
Click to expand...
Click to collapse
unlock_code.bin
I remember my old HTC´s have unlock_code.bin but not OnePlus!
You are sure you flash unlock_code.bin???
Read here:
https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2
Matija Gubec said:
unlock_code.bin
I remember my old HTC´s have unlock_code.bin but not OnePlus!
You are sure you flash unlock_code.bin???
Read here:
https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2
Click to expand...
Click to collapse
I'll have a look at it after I get off work; but, yea, many of the guides I looked at previously said I had to get an unlock token file from OnePlus to unlock the bootloader. I used as to get the code and then used the site down below to get the unlock_code.bin file from OnePlus.
https://www.oneplus.com/unlock_token
Regardless, flashing that file not the "fastboot OEM unlock," or whatever the command is, worked and I'm certain my device is still locked.
First thing I did after work was to try and unlock it again. I'm not sure what happened or what I did differently, but it worked. Bootloader is unlocked and now I'm trying to figure out my next step.
ROOT RED MAGIC 8 PRO V3.18Your device must be bootloader unlocked
To unlock bootloader enable oem unlock in developer options and usb debugging
Then type the command: adb reboot bootloader
Or access fastboot with hardware key: Power + volume down
Once in fastboot type the following command to unlock:
fastboot flashing unlock
fastboot flashing unlock_critical"
Access fastboot then type the command:
fastboot flash init_boot_a magisk_patched-25200_3.18UN.img
fastboot reboot
Done
You check if the correct active slot is a, if it is b just change the command a with b
Only use for V3.18 version I have not tested other versions
Note: Absolutely do not patch the boot file, you will have a continuous boot error
Root Done
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
mcfizzlestag said:
The backups with just ommiting the B slots is 12.7 gb so i cant personally help you with that. Have you tried flashing the OTA's boot.img (might even try boot_a.img) and init_boot.img while slot A is selected? Not the magisk modded files either.
Click to expand...
Click to collapse
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
I Pm'd you the backups now that i am at home, hopefully they help
Im at a stand still with this. I have already fastboot flashing unlock_critical as you can see in which it states Device already unlocked but whether I am in bootloader and fastboot I get Flashing is not allowed in a lock state. Any help from some else that ran into this or has knowledge on it?
Thanks
Update. Fixed the issue. Add the step of "fastboot flashing unlock" before "fastboot flashing unlock_critical"
If You can flash a GSI, It'd be a decisive factor in getting people to buy this phone. The company should be paying you to do this, but they're probably too greedy to make a bigger profit
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
yes, you can return warranty
Muriyata said:
I know that this next question were asked before, but i keep not understanding much about it: if i revert back the root completely (unroot the phone, lock the oem and delete "third party apps" like magisk, etc.) will my warranty be back? i am talking about the redmagic 8 pro void specifically. Can someone help me understanding this? i have searched on internet about this and they all say that simply it depends on manufacturers to "detect" if the warranty was void (even if you unroot and lock oem and all).... Thank you in advance
Click to expand...
Click to collapse
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
edzchen said:
Well once you unlock bootloader it clearly says warranty: void in fastboot so it probably is very easy to detect
Click to expand...
Click to collapse
In that case, why op said that the warranty can still be returned after relocking the bootloader?
As you see, it is very connfusing... Some guys say yes, some others not. :s
edzchen said:
I've successfully flashed a few A13 GSIs but screen lock is a still a problem and so far calls and messaging doesn't work normally.
Click to expand...
Click to collapse
Could you please tell me the steps to flash A13 GSI roms. Thanks.
[email protected] said:
Could you please tell me the steps to flash A13 GSI roms. Thanks.
Click to expand...
Click to collapse
Unlock bootloader
Reboot into fastboot
Flash system with the GSI.img
Mr.PvT said:
i flashed those 2 files but still can't boot the phone, go to logo then turn off the screen, can only go to fastboot and recovery, i sideload 47% it gives error
If you are rooted, please help me, I will send you coffee donate, please help me, full backup
Click to expand...
Click to collapse
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
[email protected] said:
I have the same problem with my phone. Could you please tell me if you know find the solution to this. Thanks.
Click to expand...
Click to collapse
inbox me
Mr.PvT said:
inbox me
Click to expand...
Click to collapse
How can I inbox you?
Oh no... Can this be fixed?
Stusick said:
View attachment 5862143View attachment 5862145View attachment 5862147
Click to expand...
Click to collapse
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Mr.PvT said:
Did you follow the instructions correctly, this error may have you flashed the wrong boot file, right?
Click to expand...
Click to collapse
Yes, I unlocked the bootloader first.
Then I flash boot and an error occurred.
Did I get a brick or is there hope?)