Related
Hello,
is it possible to relock bootloader after ulocking it? I need it due to the warranty.
in short, No. please search the forum for details, as this is discussed.
i suggest you just try the luck sending the phone in and not mention anythong about the bootloader. of course should flash to stock rom if that still can be done
Sent from my LG-P769 using xda premium
@stanislavdavid
Why you want the warranty? Want to sell it later? Or did it already got any fault?
mrmathematica said:
in short, No. please search the forum for details, as this is discussed.
i suggest you just try the luck sending the phone in and not mention anythong about the bootloader. of course should flash to stock rom if that still can be done
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
I think, he did not say he is sending to service center. He just said he needs it for warranty (in future).
See how smart these new pals are. May be we are all idiots to unlock it without giving a second thought. lolz
I do not have yet any fault, I just want to try alternative rom and I want to have way back to stock rom
My last phone had after 3 month of use some problem and I must return it. So I just want to know if it is possible
I thought that flashing the stock u-boot & x-boot will re-lock the bootloader.
http://forum.xda-developers.com/showpost.php?p=37250265&postcount=10
http://forum.xda-developers.com/showpost.php?p=39761686&postcount=30
Maybe this should be in a sticky post somewhere. I have seen a few people ask about re-locking the bootloader.
If this works, we should start collecting u-boot & x-boot images.
There is no way to relock bootloader. Here is good post about bootloader and omap4430, it applies to L9s. In our case ics xloader ,uboot or both simply don't recognize that bootloader had been unlocked and it just appears locked.
I see. Thanks you.
So, you guys with unlocked bootloader, have no problem with fact that your devices have no warranty?
If you don't mention the unlocked bootloader to the customer service and your device has an unrooted stock ROM, there is only a few chance that they check the bootloader if it is for an hardware issue.
It only requires a little bit luck .
If i will make root by this:
http://forum.xda-developers.com/showthread.php?t=2173465
With locked bootloader, then install cwm. May I then install cyanogenmod and if something goes wrong may i return to original stock rom together with warranty?
Sent from my LG-P760 using xda app-developers app
stanislavdavid said:
If i will make root by this:
http://forum.xda-developers.com/showthread.php?t=2173465
With locked bootloader, then install cwm. May I then install cyanogenmod and if something goes wrong may i return to original stock rom together with warranty?
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
cwm requires unlocked bootloader
I think you need to install the "CWM Recovery" bootloader to flash a custom ROM. And with a locked bootloader, you can only have a bootloader signed by LG (not a "CWM Recovery" one).
However, you can try this : http://forum.xda-developers.com/showthread.php?t=2095825
It is a "CWM Recovery" which is not directly placed inside the bootloader (instead, it adds a step on Android start). When I tried it on my P760 (when it still had a locked bootloader), it failed (but you can still try).
OperationNT said:
I think you need to install the "CWM Recovery" bootloader to flash a custom ROM. And with a locked bootloader, you can only have a bootloader signed by LG (not a "CWM Recovery" one).
However, you can try this : http://forum.xda-developers.com/showthread.php?t=2095825
It is a "CWM Recovery" which is not directly placed on in the bootloader. When I tried it on my phone, it failed (but you can still try).
Click to expand...
Click to collapse
Actually that recovery will not work on jb,
Ok, that's why it failed for me.
Now, you have your answer, you must stay on ICS if you wish to keep your bootloader locked with CWM Recovery.
However, I would be curious to know what happens if a JB ROM (custom or stock) is installed through using this "locked bootloader CWM Recovery".
OperationNT said:
Ok, that's why it failed for me.
Now, you have your answer, you must stay on ICS if you wish to keep your bootloader locked with CWM Recovery.
However, I would be curious to know what happens if a JB ROM (custom or stock) is installed through using this "locked bootloader CWM Recovery".
Click to expand...
Click to collapse
I received "Security Error" when attempting to boot when I tried this a while back. It just won't work because the kernel needs to be signed by LG.
So may I at least root phone or even root is not possible without unlocked bootloader?
Sent from my LG-P760 using xda app-developers app
Root is possible with boolloader, try this method (it worked fine for me while I wasn't on an unlocked bootloader) :
http://forum.xda-developers.com/showthread.php?t=2173465
relocked
stanislavdavid said:
Hello,
is it possible to relock bootloader after ulocking it? I need it due to the warranty.
Click to expand...
Click to collapse
You do not know resealed on, it is true that and forth they have forgotten to write never to can be relocked
sometihing new
Hello, does anybody know something new about bootloader relock?
stanislavdavid said:
Hello, does anybody know something new about bootloader relock?
Click to expand...
Click to collapse
Not possible yet.
¿How to know if my bootloader is locked? I searched on the hidden menu and found nothing but the bootloader version. I'm looking forward to unlock it so i can root and do stuff.
I own a P768G v10a
http://forum.xda-developers.com/showthread.php?t=2173465
Follow instructions here
Sent from my LG-P769
I read the whole thing and found no answers to my question dude.
LuisDe said:
I read the whole thing and found no answers to my question dude.
Click to expand...
Click to collapse
I'm not sure it's the easiest way but you can go to fastboot with method wrote here http://forum.xda-developers.com/showthread.php?t=2221102. But first you will have to flash jb V20* ROM. If you have first screen where you are asked if you want to unlock bootloader = locked. If second screen with quick guidance = unlocked.
WARNING! Be careful if you don't want to unlock bootloader watch which button you press.
You still didn't answer his question. I would like to know as well. Is there a way to tell if my bootloader is unlocked or locked?
jollyjones said:
You still didn't answer his question. I would like to know as well. Is there a way to tell if my bootloader is unlocked or locked?
Click to expand...
Click to collapse
Of course it's locked, every phone you get will have bootloader locked. Unless you have an S4 or S3 as far as I know.
Sent from my LG-P769
geeshiet said:
Of course it's locked, every phone you get will have bootloader locked. Unless you have an S4 or S3 as far as I know.
Sent from my LG-P769
Click to expand...
Click to collapse
As far as I know, not every phone comes with a bootloader closed unless some phones are able to change roms and stuff without needing to open this.
If your on JB, just go to the dialer and type 3845#*760# then scroll to the bottom to bootloader unlock check. (if you have differernt L9 - 3845#*7xx# - your numbers)
Another way to check is to go to software update mode by switching off the phone then holding volume up while inserting the USB cable. If your bootloader is unlocked, it will say so in the top corner of the S/W update screen.
If you havnt unlocked it, it will be locked by default.
Sent from my LG-P760 using xda app-developers app
Okay, so I restored animusFL's deodexed stock backup, and then I flashed the CWM recovery V20F update, but now my phone is stuck at the T-Mobile logo, and even if I try to flash a KDZ with S/W upgrade mode it doesn't work because I was previously on JB. I'm unable to access my homescreen to activate LG Software Mode. Can somebody please provide me with a simple hotfix? Please I need this fixed before night lol.
EDIT: I'm unable to access my Locked Bootloader CWM as well, before the flash I selected to preserve root and recovery but it didn't work... So now I have a phone that says T-Mobile constantly. /:
http://forum.xda-developers.com/showthread.php?p=43703749
Flash ice cream u & x (for p769) partitions in fastboot, and do the offline flash method.
Sent from my LG-P769 using xda app-developers app
kuma82 said:
http://forum.xda-developers.com/showthread.php?p=43703749
Flash ice cream u & x (for p769) partitions in fastboot, and do the offline flash method.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Hey llxaot, I'd be interested to know if you tried Kuma82's suggestion & if it worked. I'm in a similar boat ... working phone, but locked bootloader and not rooted on P769 with v20f OTA.
Kuma82, my phone is fully functional now. I'm "simply" trying to unlock bootloader & root the device. The methods in the links look to restore function of a device that's been soft-bricked, etc.
Is this the only currently known method for unlocking bootloader on P769 v20f?
Basically get fastboot working via Lelus script, flash the uboot and xloader from the 3rd link in that post & I'll be unlocked & have ICS recovery on device?
Then, I just need to flash back JB, flash CWM recovery (if I want) and root?
SO DAMN CONFUSING...this is by far the most difficult phone I've ever worked with.
tbonezx11 said:
Hey llxaot, I'd be interested to know if you tried Kuma82's suggestion & if it worked. I'm in a similar boat ... working phone, but locked bootloader and not rooted on P769 with v20f OTA.
Kuma82, my phone is fully functional now. I'm "simply" trying to unlock bootloader & root the device. The methods in the links look to restore function of a device that's been soft-bricked, etc.
Is this the only currently known method for unlocking bootloader on P769 v20f?
Basically get fastboot working via Lelus script, flash the uboot and xloader from the 3rd link in that post & I'll be unlocked & have ICS recovery on device?
Then, I just need to flash back JB, flash CWM recovery (if I want) and root?
SO DAMN CONFUSING...this is by far the most difficult phone I've ever worked with.
Click to expand...
Click to collapse
I fixed it with Lelus' help. Kuma's would definitely work but I can't seem to get fastboot to work. Anyways, what I did was went into LG PC Suite and clicked on Device -> Emergency Recovery or something like that. Make sure you don't have the local server setup from cmahendra's offline KDZ flash method. Then you just find where you put in your device's IMEI code or whatever and click OK, it'll flash the stock v20F firmware straight from LG's server to your phone! Then you have to re-root (I recommend LG Pwn method) and install busybox and then flash Artas locked CWM recovery. About the whole bootloader thing, just wait. @carloswii5 is making a video to upload soon on how to do it, that's when noobs like you and I can do this.
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Sent from my SM-G892U using Tapatalk
reukiodo said:
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Click to expand...
Click to collapse
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Gizmoe said:
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Click to expand...
Click to collapse
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
reukiodo said:
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Team DevDigitel said:
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?usp=drivesdk
This might only work on the T-Mobile version.
reukiodo said:
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?uk
This might only work on the T-Mobile version.
Click to expand...
Click to collapse
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Team DevDigitel said:
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Click to expand...
Click to collapse
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
reukiodo said:
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
Click to expand...
Click to collapse
No one has compiled twrp for snapdragon because we dont have a unlocked bl. Removing link is primarily to avoid people flashing this or reposting it with incorrect info and causing confusion.
If I can get the boot.img as well that is compiled for this bootloader I can get a running system and see if it can be unlocked. Otherwise without it there's no way to determine some of the important factors here. Just flashing against device to test is quite risky.
The bl is compatible with all snapdragon and does install correctly but it won't boot with the combo imgs we use for samfail or a stock img.
Link is still active fyi and I've sent you a pm with telegram info. It's a group for us and a few other devs that can work with us to get things sorted.
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Click to expand...
Click to collapse
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
DroidisLINUX said:
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
Click to expand...
Click to collapse
Has anyone tried the same procedure/comands used to unlock the Pixel XL? Would they even work I this phone if it had this eng bootloader? I wish I knew enough about this stuff to try it out or even know if it would work.
Sent from my [device_name] using XDA-Developers Legacy app
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
you could test,
but if you look under the info on the boot up screen, secure boot is still set to : enabled
IE: each and every boot it checks for a modified boot.img and if found it fails secure check.
I never tested the oem unlock options etc, or waiting any time frame, just mostly seeing what we could use with it.
The phone wont boot a modified system as well. has to be unrooted stock system + stock boot.img to boot with the eng bootloader.
Unfortunately i havent heard anything back, was hoping we could get the boot.img that is ENG so we can boot the entire setup and go.