Custon Rom after Oxygen has loaded
All,
I have a OnePlusOne and I love the phone. I have had custom roms on the phone in the past and now running Oxygen and not a big fan of it. .I have now tried to Root and unlock boot loader . and it doesn't appear to be working
I have followed the directions from here:
forums.oneplus.net/threads/guide-oneplus-one-how-to-unlock-bootloader-install-custom-recovery-and-root.64487/[/url]
when I unlock the boot loader I don't think it is unlocking. I think this because it does not wipe the device
if I go thru the rest of the steps it does load the TRWP and it is rooted
I am just trying to load the Cyanogen rom or something that is clean and smooth
AM I missing something?
I can boot into TRWP
and root checker sais that I am rooted
thanks in advance
E
If you've had custom ROMs on the device in the past then the bootloader must have been unlocked at some point already. Did you relock it? Check the status with this fastboot command:
Code:
fastboot oem device-info
Hi,
I recently got a brand new s6 G920A AT&T version from an authorized reseller. To my surprise the firmware on it is very old - 5.0.2 with sw version G920AUCU1AOCE
I have heard that this firmware was a pre-release/developer/engineering version of s6 and has unlocked bootloader. Is that true?
How do I find if the bootloader is locked or unlocked in my samsung s6 or for that matter in *any Samsung* phone? Is it possible to check using Odin or some other tool on whether the bootloader is unlocked?
Please let me know your thoughts or ideas! If the above is true, I could perhaps extract the unlocked bootloader and share it with everybody else!!
Thanks!
Alright Interesting...
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Thanks @ROOT67! Let me try both options out and get back on this thread.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
I hope i was helpful to you, if not then i'm sorry to have wasted your time.
Click to expand...
Click to collapse
Both the methods did not work! Please see for details below.
ROOT67 said:
Use ADB:
=========================================
1. Make to go to about device and tap build number 7 times.
2. Go to developer options (Above About Device)
3. Check usb debugging and oem (Just in case)
4. Connect your phone to your computer via usb cable (Of Course)
5. Download ADB Fastboot if you haven't already =====> https://forum.xda-developers.com/showthread.php?t=2317790
6. Install it and after that it should be set-up
6. Type the command fastboot devices
7. Then type fastboot oem device-info (BTW I am sorry for letting you know now but i think you might need to be in downloading mode or something to use the commands)
8. It should tell you if it is unlocked or not
==============================================
Click to expand...
Click to collapse
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
Method 2:
1. Boot up the phone normally then open the phone application and go to the dialer
2. *#*#7378423#*#*
3. Then service info --> configuration
4. Then it should say one of the following:
---------------------------------------------------------------------------------------------------------------------------------
1. Bootloader unlock allowed --Yes >> This means that your Bootloader is Locked
2. Bootloader Unlocked - Yes >> This means that your Bootloader is unlocked
Click to expand...
Click to collapse
When I dial this number, nothing happened. Is there a different number for Samsung s6?
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
jilebi said:
Both the methods did not work! Please see for details below.
I could not put it in fastboot mode. Do we know if the Samsung s6 supports fastboot mode? If so, how to put it in fastboot mode?
Also as a side note, in developer mode under settings, I could find check box for USB debugging but not for OEM. There was another post which said that OEM checkbox was added under developer options only after bootloader lock was introduced in 5.1.1 firmware. Not sure if this is true.
When I dial this number, nothing happened. Is there a different number for Samsung s6?
Click to expand...
Click to collapse
No other number is available that i know of, like the person above stated it is a old firmware version and with that said i would highly try to prevent any updates from installing. I would love to help you out, but since i have no idea as to what would be needed to tell if the bootloader is unlocked, but i do know since Samsung is against us rooting and using our devices the way we want, it is safe to assume the bootloader is locked and because you have at&t variant. Your best bet to get your device bootloader information is to look around on the XDA forums.
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
forumber2 said:
It's not a pre-release/developer/engineering firmware. It's just a really old firmware which released for public officially.
Click to expand...
Click to collapse
jilebi said:
Do you have any details on whether the bootloader was locked or unlocked for this old version? How can one test or check if bootloader is locked?
Click to expand...
Click to collapse
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
forumber2 said:
All AT&T branded nearly-new (including S6) Samsung devices has a non-unlockable locked bootloader.
There's no way to test that.
Click to expand...
Click to collapse
jilebi said:
here are a couple of test scenario that i can think of. let me know your thoughts on them
- if the device is rooted, load a custom recovery like TWRP. next, try to boot into custom recovery. if it boots into custom recovery, bootloader is unlocked. if not, try to restore factory recovery using odin.
- if the device is rooted, load a custom ROM. next, try to boot into custom ROM. if it boots into custom ROM, bootloader is unlocked. if not, try to restore factory ROM using odin.
Will these test scenarios work? If not, what are the potential issues you see?
Click to expand...
Click to collapse
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
forumber2 said:
- There's no custom recovery or custom kernel for SM-G920A, because of the reason I've wrote above.
- Installing a custom ROM doesn't require an unlocked bootloader unless the ROM doesn't require custom kernel. (Custom ROMs for SM-G920A don't require custom kernel (except leaked engineering/debugging kernel from Samsung for disabling dm-verity))
Click to expand...
Click to collapse
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
jilebi said:
Got it. Thanks. That makes sense.
Here is another option. For making custom recovery, my understanding is that partition info is needed. If the device is rooted e.g. using Pingpong (which works for this Android version), then one can get a partition info and compile TWRP for G920A. If so, can one try to install custom recovery like TWRP and verify if bootloader is locked? It feels to me that this may work. Do you see any flaws?
One possible flaw is that if bootloader is locked, it will prevent recovery from loading. So the phone will be without a working recovery. In that case, can factory recovery be re-installed using Odin?
Also, will any of the above steps trigger the KNOX flag?
Click to expand...
Click to collapse
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
forumber2 said:
You don't have to get partition info, and compile TWRP. All S6 variants are using same partition name scheme and there are no difference on TWRP builds between S6 variants (except kernel and DTB).
The bootloader won't allow you to flash any custom recovery image (via Odin or in Android OS). If you could flash it, It won't boot it up anyway.
I don't have any idea about the KNOX trigger on AT&T variant devices, but I think it won't increase anyway.
Click to expand...
Click to collapse
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
jilebi said:
Sorry, I perhaps misunderstood from your last post that since custom recovery is not available for G920A it implied its partition info was different from other variants. If it is the same partition structure for all variants, then I guess we can use the TWRP for the G920F international version for which bootloader is unlocked.
Now that we agree that TWRP is available for use on G920A, the next question is how to load it. My thought is that if the device is rooted that means one can use dd at root shell prompt to write TWRP to the recovery partition, without using Odin or the current bootloader. Do you agree?
Not sure I understand why you say that if one could flash TWRP it would not boot anyways. If bootloader is unlocked (which is what we are testing here), then it should boot, right?
Click to expand...
Click to collapse
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Sorry to ressurect this old thread, but can you (or anybody else who is knowledgeable) answer the following?
1. Since custom recovery is not available for G920A, which of the Tmobile/Sprint/International versions of TWRP custom recovery would you recommend to use for testing if bootloader is unlocked, using either ODIN or dd method?
2. If bootloader is unlocked, you are suggesting below that it should boot up. However, if it is locked, then will the phone still boot up? i.e. if one does not go into recovery mode, will it still boot up or does the bootloader check if both recovery and kernel are signed and if it finds that the recovery is unsigned, will it also prevent the signed kernel from booting up?
Thanks!
forumber2 said:
A custom recovery is not available for G920A, because no one could try any custom recovery on G920A due to locked bootloader.
Yes you can write the recovery image via dd at root shell prompt.
And yes, If bootloader is unlocked, it will boot it up.
Click to expand...
Click to collapse
Bricked Pixel 2 - locked bootloader & no access to developer options - please help
Hello guys, I just bought myself a Pixel 2 device today and decided to have a go at some changes: I've unlocked my bootloader of my Pixel 2 to perform TWRP flashing & Magisk installation and afterwards I decided to revert to stock.
The first step that I did when trying to revert to stock was to relock the bootloader via adb because I thought (big mistake) this will also revert everything to the factory image. Problem is right now the device isn't booting anymore (so I cannot change anything in developer settings and the bootloader is locked).
Fastboot does work now (I get an "FA8271A02780 fastboot" message when typing fastboot devices) but I cannot flash anything (it always says FAILED: remote Flashing unlock is not allowed.
I tried the Deuces script and UAF but they don't work (because my bootloader is locked). Given that I cannot unlock it, is there any way of flashing the stock image on my device? Any help is appreciated. Thanks a lot.
Sadly I don't believe so. Google doesn't allow us to flash anything without bootloader being unlocked. Other OEMs either have a program or allow you flash signed roms with a locked bootloader. For the trouble iTunes is at least you flash firmware through in the event of a Brick
We flashing v35 engineering bootloaders
1. enable USB-Debugging
2. Enable OEM unlock
3. enter into 9008 mod
4. do step by step instructions. Video youtube: p8Z0KOUNw7Q
5. And then "fastboot oem unlock" will work.
LG_LG+G7+Unlock+Bootloader.zip on mega nz
#!P2wDBa4R!NLS6k9QAK0-I2PWdACqEOiKdUpGzisrxnh1876cRTKU
copy of instructions from youtube on mega nz
#!XuhDDCRJ!8kUG3MWgQCeDhKIJqRcKJc0TTvAeNeP7RodkbZ-mGrs
Because when you 'fastboot oem unlock' successful.
you phone just unlocked bootloader, so you can flash root booted to root you phone.
Flashing back to Stock KDZ: we can flash the stock KDZ for the G7 and keep booloader unlocked but -- depending on version -- we loose access to fastboot commands. To avoid this he mentions using patched LGUP to flash the KDZ, making sure to uncheck the bootloader partitions
Please be aware that the v35 bootloader will hard brick your phone, if you flash stock pie kdz without bootloader partitions. I was in that situation and only recovery option was octoplus again.
The owner of that video is @motogvasyag
https://forum.xda-developers.com/lg-v40/how-to/remote-unlocking-bootloader-models-t-t3946648
cheeze.keyk said:
The owner of that video is @motogvasyag
https://forum.xda-developers.com/lg-v40/how-to/remote-unlocking-bootloader-models-t-t3946648
Click to expand...
Click to collapse
yes. and i link his youtube channel
It works using Pie?
If I flash KDZ and lost Fastboot I can install another KDZ to recover fastboot access?
Why not t-mobile?
There appears to be a post (from two days back) on one of the famous Russian forums showing a way to do this without Octoplus by temporarily booting using a rooted boot and then replacing the bootloader using a root terminal and finally doing the unlock using "fastboot oem unlock". Has anyone here tried it / have any thoughts on it?
can keep Fastboot on Slot a when update to Android Pie
LG G6 ThinkQ Unlocking Product
ruvhell said:
We flashing v35 engineering bootloaders
1. enable USB-Debugging
2. Enable OEM unlock
3. enter into 9008 mod
4. do step by step instructions. Video youtube: p8Z0KOUNw7Q
5. And then "fastboot oem unlock" will work.
LG_LG+G7+Unlock+Bootloader.zip on mega nz
#!P2wDBa4R!NLS6k9QAK0-I2PWdACqEOiKdUpGzisrxnh1876cRTKU
copy of instructions from youtube on mega nz
#!XuhDDCRJ!8kUG3MWgQCeDhKIJqRcKJc0TTvAeNeP7RodkbZ-mGrs
Because when you 'fastboot oem unlock' successful.
you phone just unlocked bootloader, so you can flash root booted to root you phone.
Flashing back to Stock KDZ: we can flash the stock KDZ for the G7 and keep booloader unlocked but -- depending on version -- we loose access to fastboot commands. To avoid this he mentions using patched LGUP to flash the KDZ, making sure to uncheck the bootloader partitions
Click to expand...
Click to collapse
I have a question about the Octoplus Pro Box. Is this product better than the Infinite Box Chinese Miracle II? We have some ex demo phones without an IMEI where we need the boot sector unlocked. We want to flush the OS to install a new OS, e.g lineage or ubuntu., preferably an open source linux version. Do you recommend the Octoplus Pro Box or the Chinese Infinite Box Miracle II and why would you prefer one over the other? Thanks for your feedback.
How can I root my Nokia 1.4 Android 11(Go edition)
Unlock bootloader and flash magisk. Since the device is new, I recon that you will need to wait a couple of months for a guide to pop up. Or you could try your hand with generic guides on web and risk it. Either you unlock and root your device or you hard brick it. Nothing a trip to the service won't fix.
I unlocked bootloader
Bootloader
MD.sajjad said:
I unlocked bootloader
Click to expand...
Click to collapse
Can you please share with me how you unlock the bootloader. Because I want to instal Android 12. Please reply bro
Fytdyh said:
Unlock bootloader and flash magisk. Since the device is new, I recon that you will need to wait a couple of months for a guide to pop up. Or you could try your hand with generic guides on web and risk it. Either you unlock and root your device or you hard brick it. Nothing a trip to the service won't fix.
Click to expand...
Click to collapse
Can you tell me how to unlock bootloader please on Nokia 1.4 and root the device so that I can install twrp on it. I'm not a pro in these stuff
Just… go to dev options and enabwl oem unlocking then download platform tools on pc, boot into bootloader, and do an unlock command. Just find a generic, no-Samsung guide.
Arealhooman said:
Just… go to dev options and enabwl oem unlocking then download platform tools on pc, boot into bootloader, and do an unlock command. Just find a generic, no-Samsung guide.
Click to expand...
Click to collapse
What's the unlock command
How do I boot into bootloader mode
adb reboot-bootloader
command can be found in fastboot . just type fastboot hit enter and it will give a list of commands