Unlock G900V Bootloader with cid 11? - Galaxy S 5 Q&A, Help & Troubleshooting

For many years now we have tried to unlock the bootloader with devices with CID 11, I want to know if there is already a way to unlock the bootloader and install twrp to install Custom Roms

If your bootloader doesn't come unlocked, with disabled verification, then sorry, you'll never be able to unlock it.
You want custom ROMs, trade your phone with another S5.

Related

Root without unlocking bootloader

Like on the Nexus One, I would like to know if there is a way to root the phone without unlocking the bootloader. I have apps on my phone that I cant currently have wiped, so therefore cant unlock the bootloader. However if i can root, I can backup that specific app, and then unlock the bootloader, install roms etc, and then restore my app. Any help would be great, thanks.
nintendolinky said:
Like on the Nexus One, I would like to know if there is a way to root the phone without unlocking the bootloader. I have apps on my phone that I cant currently have wiped, so therefore cant unlock the bootloader. However if i can root, I can backup that specific app, and then unlock the bootloader, install roms etc, and then restore my app. Any help would be great, thanks.
Click to expand...
Click to collapse
As of now there is no way to root without unlocking the bootloader
unlock bootloader : fastboot oem unlock
lock bootloader : fastboot oem lock
Amon_RA said:
unlock bootloader : fastboot oem unlock
lock bootloader : fastboot oem lock
Click to expand...
Click to collapse
He cant do a full wipe though is what he is saying
Bite the bullet and redo all your apps.
I cant bite the bullet, as the app has data that has to be remotely pushed to my phone and the people who do that are away for Christmas, Is there no way at all to root without unlocking the bootloader.

Flash stock over stock, same version, locked?

I have never really seen this asked, and I am not just asking about the 6p but any Nexus or near stock phone with an unlockable bootloader (Motorola).
I have seen some claim they could not reflash their Nexus at all due to "allow OEM unlock" disabled in GUI. Others say if it is same stock ROM as currently installed, you can reflash the same stock ROM over what is there with bootloader locked.
If true, what if security patches are installed? I know flashing 6.0.1 over 6.0 requires unlocked bootloader. I am not talking about a rooted or modified phone in any way.
Just can the same image 6.0 for example be flashed on phone with 6.0 if bootloader is locked? What if unlocked, but gui has allow OEM unlock disabled?
Thanks.
chromedome00 said:
I have never really seen this asked, and I am not just asking about the 6p but any Nexus or near stock phone with an unlockable bootloader (Motorola).
I have seen some claim they could not reflash their Nexus at all due to "allow OEM unlock" disabled in GUI. Others say if it is same stock ROM as currently installed, you can reflash the same stock ROM over what is there with bootloader locked.
If true, what if security patches are installed? I know flashing 6.0.1 over 6.0 requires unlocked bootloader. I am not talking about a rooted or modified phone in any way.
Just can the same image 6.0 for example be flashed on phone with 6.0 if bootloader is locked? What if unlocked, but gui has allow OEM unlock disabled?
Thanks.
Click to expand...
Click to collapse
On Nexus 5X and 6P, if the bootloader is locked and OEM Unlock is disabled, one can either update via OTA or ADB sideload the update.zip via stock recovery...if using the stock rom.
I cannot speak on any phone aside from 5X and 6P.
Edit: I have not tried it (no reason to) but if bootloader is unlocked, with OEM Unlock setting later turned off, you should still be able to flash stock images via fastboot. The way I see it, the bootloader is still unlocked, which allows for factory images to be flashed in fastboot. You can still OTA or ADB sideload.
Sent from my Nexus 5X using Tapatalk
chromedome00 said:
I have never really seen this asked, and I am not just asking about the 6p but any Nexus or near stock phone with an unlockable bootloader (Motorola).
I have seen some claim they could not reflash their Nexus at all due to "allow OEM unlock" disabled in GUI. Others say if it is same stock ROM as currently installed, you can reflash the same stock ROM over what is there with bootloader locked.
If true, what if security patches are installed? I know flashing 6.0.1 over 6.0 requires unlocked bootloader. I am not talking about a rooted or modified phone in any way.
Just can the same image 6.0 for example be flashed on phone with 6.0 if bootloader is locked? What if unlocked, but gui has allow OEM unlock disabled?
Thanks.
Click to expand...
Click to collapse
If the bootloader is unlocked you can flash with fastboot, the "allow OEM unlocking" toggle has nothing to do with the ability to flash, it only controls whether the bootloader can be unlocked or not. If the bootloader is locked you can't flash anything at all, regardless of whether it's the same build or not, it's undeniably impossible to flash anything with a locked bootloader.
Updating to 6.0.1 from 6.0 doesn't require an unlocked bootloader, you can use the built-in update system to take the OTA update.
To answer your last question (and repeat myself), no you can't flash anything with a locked bootloader. If you''re unlocked but the GUI toggle is set to disallow OEM unlocking you can still flash because the bootloader is unlocked.
Some advice:
Leave the GUI toggle set to allow OEM unlocking. Leave the bootloader unlocked. Sometimes updates fail and the phone ends up in a boot loop, if your bootloader is locked and the toggle set to disallow unlocking you'd essentially have yourself a brick.
To clarify, I am not talking about ota or sideload of ota. I want to know about flashing 6.0 full over 6.0 full if bootloader locked. Let's say something is corrupted and phone isn't booting to GUI.
Is it possible to reflash same full image if bootloader locked. Forget the OEM toggle in GUI.
Surely someone knows for sure, or is curious.
Sorry, I see you answers and confirmed what I thought. Flashing anything but OTA is impossible. Missed that scrolling to fast on mobile.

Unlocking/Locking/Relocking Bootloader

Hi XDA!
I recently unlocked my phone's bootloader to install an update for my p8lite and I want to lock it back. There is an option called relocking the bootloader and I want to know whether it is the same as locking the bootloader. Also will the ability to flash ROMs through fastboot lose after i relock it?
Thanks
Yes, it is the same, and yes, you will lose the fastboot flash ability. However, the fastboot screen won't show "Locked", it will show "Relocked"

unlock after relock

several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
psyvenrix said:
several questions in no particular order:
Does the "OEM Unlocking" toggle do anything on the XT1572?
If I issue the fastboot OEM LOCK command after having sucessfully unlocked the device before, do I need to go through the full data wipe+send oem data+flash unlock code process again?
Lastly, I was able to flash the MM firmware for my Single SIM AISA model XT1572 despite having the bootloader locked (I think).
Is that normal that I can flash the official moto firmware using just fastboot without having to tweak with anything else?
I presume that since the digital signatures are correct the bootloader has no issue accepting the MM files.
Not quite the end of the world if I have to wipe everything and start over (it's only been a day) but I regret not knowing earlier. Nor did I expect to get this far with a relocked boot loader. Was trying to add SuperSU and found that while I can overwrite flash the stock recovery I cannot flash TWRP.
Click to expand...
Click to collapse
As far as I am concerned relocking the bootloader wont wipe your data and yes about the question regarding the stock firmware
PS: Dont relock your bootloader once you unlock it the warranty doesnt come back even if you lock it again

Did I completely brick my T-Mobile 6T?

Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.
GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.

Categories

Resources