Related
Has anyway found a way to Root the OnePlus One without having to flash a custom recovery with the new 33R OTA?
(yes I didn't check the CM recovery)
*But after I updated to the 33R update I still had root access intact, despite gaining root by boot and not having unlocked the bootloader under 33R. The problem was I did a factory reset and obviously it reflashed the newer bootloader and I lost root access (yes stupid)
This can no longer be done 'fastboot boot twrpimgname.img' with the 33R update ;
Aren't One Plus all about give you the power so why did they go ahead and block boot custom recovery that worked before ??
This is the under 33R OTA =
C:\adb>adb reboot bootloader
C:\adb>fastboot boot openrecovery-twrp-2.7.1.1-bacon.img
downloading 'openrecovery-twrp-2.7.1.1-bacon.img'...
OKAY [ 0.402s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.404s
Seems the have patched being able to boot a custom recovery without unlocking the boot loader
Yes I realized the the 'Update CM recovery' option but not after I updated to 33R (my oneplus was rooted without having to unlock the boot loader)
I did do a Nandriod backup of course before the 33R OTA.
The nandriod backup is rooted without having to unlock the bootloader via this ' fastboot boot twrpimgname.img '
Is their no way yet to boot a custom recovery without unlocking the boot loader ? Does one have to wait for a update twrp recovery to boot not flash ?
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
mcbyte_it said:
The question is: WHY?
the locked bootloader is locked because it allows only booting a signed recovery, if you use a custom-unsigned-by-manufacturer recovery there is no sense in keeping the bootloader locked.....
OnePlus knows that 90% of the users are rooting and unlocking, so there is no sense to keep it unlocked.... in case of necessity, you can relock the bootloader !!!
Anyway, you wrote in the wrong section !!!
Click to expand...
Click to collapse
What area is the right one, my bad.
Also asking if their is a way around the 33R to boot custom recovery
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
timmaaa said:
Why though?? You don't need to boot to a custom recovery. Just unlock the bootloader, it doesn't void your warranty. You have absolutely nothing to lose by doing it, and absolutely nothing to gain by leaving it locked.
Transmitted via Bacon
Click to expand...
Click to collapse
Just an innocent wipe... and he only wants root.
Yeah and the right way to get root is to unlock your bootloader, install TWRP, and flash SuperSU.
Back stuff up, unlock bootloader, restore stuff. It's stupid to try to 'hack' into the world's easiest phone to root.
Transmitted via Bacon
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Have you tried towelroot? https://towelroot.com/
-fluffy- said:
go back to 25R an root it
then untick the update recovery in develop settings
install recovery twrp
now remember to have the update recovery
install the 33R
with twrp an in the end choose fix permissions
now u can download from phone it will come up to fully root
just hit fully root an install with twrp
it will download root
an restart in recovery wait fore it to finnish an u are now rooted on 33R
Click to expand...
Click to collapse
How's he meant to go back without an unlocked bootloader??
Transmitted via Bacon
Whilst upgrading to Oxygen OS, I ran into an issue (wiped all partitions however ADB Sideload did not work so I got stuck with no OS). In an attempt to completely wipe the phone, I tried to lock and relock the bootloader, forgetting that the phone required to be booted up in order to unlock the bootloader. So now, I am stuck with no OS and with a locked bootloader (so I am unable to flash the factory image). I am also unable to unlock the bootloader as I cannot boot the phone. I still have access to TWRP, however upon pushing a rom onto the memory, it failed to flash. I am assuming this is due to the locked bootloader, however I am not sure.
If anyone has any ideas on how I can fix the phone, I would greatly appreciate it.
Thanks!
This is what you need:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
You flash that from TWRP and it'll unlock your bootloader again.
Transmitted via Bacon
I've android PumpKinx 10.1 tablet with 5.1 Lollipop android os.
I did take backup of its stock recovery image.
Since there is no custom recovery image for this device I tried to flash it with twrp recovery image. But after running below command, device goes into bootloop. I've tried many methods but no success.
fastboot flash:raw boot twrp.img
Any help would be highly appreciated. Thanks in advance.
maybe u have locked bootloader. First turn on oem unlock in developer options, then reboot in bootloader and type
Code:
fastboot oem unlock
Then confirm acion in the tablet whit volume up, then the bootloader now is unlocked.
Note: The tablet get soft reset. Make backup first.
Then try flash the recovery
xdedeone said:
maybe u have locked bootloader. First turn on oem unlock in developer options, then reboot in bootloader and type
Code:
fastboot oem unlock
Then confirm acion in the tablet whit volume up, then the bootloader now is unlocked.
Note: The tablet get soft reset. Make backup first.
Then try flash the recovery
Click to expand...
Click to collapse
Do you understand boot loop or not? First of all fastboot is already unlocked otherwise how I will be able to run above command and since my device is in boot loop then how can I go to developer option?
chitrang200889 said:
I've android PumpKinx 10.1 tablet with 5.1 Lollipop android os.
I did take backup of its stock recovery image.
Since there is no custom recovery image for this device I tried to flash it with twrp recovery image. But after running below command, device goes into bootloop. I've tried many methods but no success.
fastboot flash:raw boot twrp.img
Click to expand...
Click to collapse
Just send them an email asking for stock firmware with flash tool, along with the purchase bill..
Or if it still has warranty, just go to the service center and say something like you over-charged the phone a complete night & since then it's not working and claim warranty..
Have you tried to wipe the cache partition or even factory reset???
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
I unlock the bootloader to install twrp and magisk, it's possible to lock the bootloader again without problems or the phone don't boot?
Toni Moon said:
I unlock the bootloader to install twrp and magisk, it's possible to lock the bootloader again without problems or the phone don't boot?
Click to expand...
Click to collapse
Locking you bootloader while TWRP and Magisk are installed will give you a guaranteed brick. Use a Fastboot Rom to return to stock, then you can lock it
If you want to keep TWRP and root, do not lock the bootloader. As the user mentioned above, you'll brick your device.
if i flash stock rom, than is that ok to lock the bootloader ? and how to lock it ?
majidshahab091 said:
if i flash stock rom, than is that ok to lock the bootloader ? and how to lock it ?
Click to expand...
Click to collapse
If you flash a full stock rom then yes. All you do is use the fastboot rom we talked about earlier, let the phone boot up (don't bother completing the setup process, just let the phone boot up), restart to bootloader, and use the following command from the command prompt on your pc:
Fastboot oem lock
It will give you a menu on your pone asking if you want to lock the bootloader. Tell it yes. It will then lock the bootloader, factory reset the phone, and then boot up normally with the bootloader locked. It's that easy.
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
majidshahab091 said:
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
Click to expand...
Click to collapse
I did it through twrp, worked just fine. Make sure to wipe beforehand though, don't want to risk bricking your phone
majidshahab091 said:
ok thanks.one question. is that important to flash the stock rom using fastboot only ? or can i flash it using twrp ?
Click to expand...
Click to collapse
Doing it with a Fastboot Rom will guarantee that things needing wiped will get wiped. When returning to full stock I will always recommend the Fastboot Rom just because of how it completely handles everything it does flawlessly. I imagine flashing a full rom in TWRP will work but I have never tried to return to stock this way
i did try stock using twrp and it was perfect
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
TaranQ said:
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
Click to expand...
Click to collapse
Use msm download tool to be sure. It will however wipe all.
TaranQ said:
I have unlocked bootloader but in the end NOT installed TWRP or root (just wanted to test if i can live without it and still be able to install without wiping everything)
Now I just want to lock bootloader again for selling device.
Can I do so with simple fastboot command "fastboot oem lock" without bricking phone?
Click to expand...
Click to collapse
You can, but if you are selling the phone I would still use a fastboot rom just to be sure everything is wiped and no data sensitive to you is being sold along with the phone.
Thanks a lot for the shared info here. This is just what I need and had been asking myself for quite some time now.??
So never lock bootloader with twrp and magisk installed.