Made a bit of a boob here. I was upgrading my firmware version 10v to the new January firmware using LGUP. Unfortunately i forgot to click Upgrade, and so by accident ran the refurbish command.
The 'upgrade' ran through OK, and it boots, but I lost root/twrp (im on H930).
When I tried to bung TWRP back on, I cant get the fastboot boot twrp.img command to work (sorry if syntax is wrong while typijg this message) - that command just reboots the phone but it sits of the LG v30 loading screen.
Ive noticed that the fastboot screen tells me to make sure I flip the OEM Unlock switch in Dev options (a blue message). However, that setting is greyed out. Running the getvar command says I am unlocked though, as does re-running the unlock command.
So im confused. Im guessing i cant install TWRP as fastboot mode thinks im locked?
Any ideas??
Sent from my LG-H930 using Tapatalk
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
runningnak3d said:
It may say you are unlocked, but you are not. Once you are rooted, you should never flash a KDZ -- especially if you are unlocked via the unlock.bin method. If you want to upgrade, flash the firmware via TWRP.
But you are in this situation now.... so, have you tried flashing unlock.bin again?
-- Brian
Click to expand...
Click to collapse
Hi Brian
Yeah, if i try flash the unlock.bin file again i get an error telling me im already unlocked (or words to that affect...im away from my PC so can't see the exact message)
Sent from my LG-H930 using Tapatalk
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Awesome Brian, thanks loads for the help. I'll PM you the Zip as soon as ive done it
Sent from my LG-H930 using Tapatalk
runningnak3d said:
When you get a chance, grab a copy of the patched LG UP, dump misc, persist and persistent, zip them up and PM me a link to the zip.
If you have any chance of fixing this, it will be wiping one or all of those partitions -- but I need to take a look at them to figure out which ones.
Once wiped, the phone will no longer report being unlocked and you can flash your unlock.bin again. Once you are unlocked, you will need to make a dump of those partitions again so I can compare them. I will then fix them so you can flash them back.
-- Brian
Click to expand...
Click to collapse
Brian, quick question. Would i need to be rooted to create the dumps....?
Sent from my LG-H930 using Tapatalk
Nope.
-- Brian
thenoble06 said:
Any ideas??
Click to expand...
Click to collapse
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
padmanek said:
Since you flashed a fully stock rom, can you try to do 'fastboot oem lock' and then check developer settings if OEM unlocking became active so you can flip it to ON again?
Click to expand...
Click to collapse
Ahhh cool, that did it. Re-locked, flashed latest KDZ with LG UP and then relocked, installed Recovery and re-rooted.
Jobs a good un!
I'll stay away from KDZ files now and just update/upgrade via TWRP (that's right yeah)?
Thanks both for your help!!
Sent from my LG-H930 using Tapatalk
Related
I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
thchipmunk said:
I have superuser and artas CWM. I am running P769BK. I want to install a new ROM but want to avoid a security error again. Any tips?
I searched here and Google and found nothing. If I need to go to another thread I will.
Sent from my LG-P769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
elpuertorro said:
Same here man i had unlocked the bootloader a while back before the JB upgrade was gonna try a Rom so decide to flash recovery and got the Sec error did all reflashed KDZ back on JB rooted and with artas recovery they say once you unlock the bootlader it stays that way, anyways did all the steps again to unlock, but boot normal and i have no way of checking... How can we know or check that the bootloader is unlocked??
Anyone????
Click to expand...
Click to collapse
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Thanks! This are my unfortunate results.
I did not see the menu. I did the offline flash of V20_00
Nothing about unlocked bootloader
Yeah... I don't feel confident enough to try this again. Not yet.
Oh well. I'll wait longer until I feel better about what I am trying.
I have the P769BKGO GSM unlocked using Net10. So I think I won't be able to do the adb reboot oem-unlock trick. Other thoughts? Is flashing a different KDZ the only other route?
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
kuma82 said:
If you have unlocked your bootloader, you would know
anyways here are a couple of ways to check, because y'all still want to check
1. Dial the number EVIL#*769# (3845#*769#) this will get you into the hidden menu
note: if you have a P760 change number to 3845#*760# change the last number/digit to whatever your device is
Once in that menu look for the bootloader tab, if it doesn't have it, sorry the kdz you are on doesn't show if it's unlocked or not.
2. Put your phone in the s/w upgrade mode, it should show unlocked bootloader
3. Another way to check is to fastboot and flash a custom recovery for your device BUT first extract your current recovery.img in case you receive a security error. However, I would advice y'all don't fastboot and flash anything unless you really know what y'all are doing. You have been warned!!!
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
In your case @elpuertorro you have to flash the u-boot.img from a P760 v20B
I uploaded the u-boot here http://forum.xda-developers.com/showpost.php?p=43386521&postcount=14
Another thing, if you did in deed unlock your bootloader, flashing a new kdz will (should not) not replace the u-boot.img. All P769 or LGMS769 will know right away if their bootloader is unlocked because the "LG" letters will be inverted when your boot up the phone (unless you flashed a u-boot.img from a P769).
Click to expand...
Click to collapse
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
elpuertorro said:
Thanks kuma the thing is i did this when i got the phone back in Jan so as you can see by now what ever i did is a bit of a blur, (short time mem loss you know lol) but i did recall doing it and have my folder set up for my phone, but to try to remember what or how and what tut i followed is the problem...but it's cool because i was looking for
V20b and since i could find one yesterday talking to carloswii for a copy asked if V20c would work as he didn't know figured i will try it and report back for the benefit of all....so that's next today
ps Kuma that's great advice but hey @thchipmunk don't be scared man is scary reading all but once you do it like 2 times it's all smooth plus with th KDZ offline method this cel comes back to life in no time so far as they have said you can't brick this phone even if you tried lol. to the rest stick with kuma's advice lol.
Click to expand...
Click to collapse
thchipmunk said:
I am mostly just scared because it took me forever to get the KDZ to flash again. I kept getting that the USB was not connected to the phone so I wasn't able to ever complete the flash.
I do wonder though, if I would be able to unlock the bootloader. I see the directions say you need to wait 30+ minutes once connected, I assume this is some restriction in place on the actual phone with the SIM. However, I have an ATT SIM that I am using through NET10. Will that matter?
Click to expand...
Click to collapse
Been there , done that lol
By anychance when that happened to you
1 you were connecting the phone on lg software mode? that's what it should be and i'm sure you was
2 if you did, was it giving you errors about installing drivers failed?? that happens to me sometimes so i just restart the pc and then the phone get's recognized.
just remember sometimes we have to hit that skip that pops up when it's searching for drivers on the phone.... worse comes to worse reinstall the drivers for the phone hope this helps you out man.
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands
So, long story short, I recently bought a Nexus 9 from ebay which arrived with factory reset protection.
I have spoken to both Google and HTC about the situation and both were of no real help except for saying a few things outright between them to give me good enough reason to believe one of two things.
That 1 - it is possible to flash factory images over a device with a locked bootloader
or 2 - it is possible to unlock the bootloader without having access to developer settings
Anyone have any experience with either of these possibilities?
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
enriquejones666 said:
https://developers.google.com/android/ota
Full OTA Images can be flashed onto devices with locked boot loaders.
You need to boot into recovery and select sideload update.
Click to expand...
Click to collapse
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Those are full ota images, same as factory image. Meaning full package.
BigDomTheFirst said:
Yeah, I know how to do that, but that only goes for updates, doesn't it? I tried to sideload a previous build onto the tablet but it failed the procedure, so it doesn't really solve the issue and if I flash a more recent update I still get FRP :/ If I wanted to revert back to the 7.0, or even marshmallow, would that be possible? Or does that require an unlocked bootloader?
Click to expand...
Click to collapse
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
enriquejones666 said:
Ah yes, now I see your predicament. Unfortunately, there is no "there" there. You do need an unlocked bootloader to wipe the system clean with a factory image, and as you noted, the Full OTA Image will recover you from a system that won't boot, but it won't get rid of FRP.
Click to expand...
Click to collapse
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
BigDomTheFirst said:
Exactly Hence my questions as to how do the manufacturers wipe everything and flash the new image without unlocking the bootloader? Or will it always be a trade secret?...... Hmmmm
Click to expand...
Click to collapse
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
Never found out how they do this.... are you able to boot in to recovery? if you can do that you may be able to flash a recovery OTA through 'apply update from ADB'. Worth a shot
Uncleheff said:
did we ever fix this? my bootloader is locked and no os installed. Was trying to return to factory and went thru all the flashing steps successfully then at the end locked the bootloader. Now tablet says "for development purposes only not for production use" and boots back to fastboot. It will not reboot at all
Click to expand...
Click to collapse
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Bryanx86 said:
If up dont mind my asking how did it get that way by just locking the bootloader? I was just about to flash stock and lock on my volantis, then read this...?
Click to expand...
Click to collapse
definitely don't lock your bootloader. That is a horrible move and serves no purpose
madbat99 said:
definitely don't lock your bootloader. That is a horrible move and serves no purpose
Click to expand...
Click to collapse
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Bryanx86 said:
I actually reflashed last factory stock image and relocked without issue. It is a horrible move, I agree...I already miss root, but it suits the purpose. Thanks for your reply.
Click to expand...
Click to collapse
it's only a bad move if you make a mistake and can't repair it because your bootloader is now locked. But if it goes well then you're all set.
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.
to get to the point i used the ota updater for a lineage and it wiped twrp and replaced it with lineage recovery. then i decided to perform a factory reset in sed recovery. that led to boot loop that landed me back in recovery. so i started up lgup and went back to stock oreo and bootloader remained unlocked. now that i'm back on stock oem unlock is greyed out. when in fastboot it says to enable oem unlock. so what do you guys think i should do? unable to flash or fastboot boot twrp at all.
heres the pics
https://imgur.com/a/WiDIqfm
For anyone that happens to run into this issue. Run fastboot OEM lock and it'll fail on the command line but reboot your device and it'll relock the bootloader. Then follow the Frankenstein guide to unlock the bootloader again.
Was able to immediately toggle OEM unlock after this
What error do you get when you try to flash?
Sent from my LG-US998 using Tapatalk
kenbo111 said:
What error do you get when you try to flash?
Click to expand...
Click to collapse
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
R800x_user said:
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
Click to expand...
Click to collapse
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
ChazzMatt said:
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
Click to expand...
Click to collapse
I want aware of the wait time. Thanks for the info
R800x_user said:
I want aware of the wait time. Thanks for the info
Click to expand...
Click to collapse
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
ChazzMatt said:
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
Click to expand...
Click to collapse
How long would one have to wait? Still grayed out.
Just an update to this.
R800x_user said:
How long would one have to wait? Still grayed out.
Just an update to this.
Click to expand...
Click to collapse
I never measured, but less than a week I think.
ChazzMatt said:
I never measured, but less than a week I think.
Click to expand...
Click to collapse
[email protected] okay, I'll need to try to OEM lock. I'm unsure if it'll even work. At least I have a functional v30. I was thinking using LGup would've relocked the bootloader if I downgraded.