Guys, Is there any way to get rid of that ugly bootloader unlock warning when phone is reboot?
EDIT September 11, 2020:
Here you go:
LG V30 Unlocked Bootloader Warning Disabler
I would add it to the WTF Instructions but I've run out of room on that LONG post. It's posted in the mods/themes/apps section. People will just have to find it.
Thats the bootloader, telling you its unlocked.... thats before/during the splash screen i think...
I doubt we can get rid of it, except locking your bootloader again probably? (is that even possible on a H930/US998?)
No,like on the G5 it's not possible to remove it.
Unlocked bootloader = warning screen.
There is nothing we can do.
Regards
mkpcxxl
On my old Moto G was the similar bootloader unlock warrning and someone made the flashable zip that this turn, off but that was message instead of the Motorola logo. This was annoying for everyone.
https://forum.xda-developers.com/2015-moto-g/themes-apps/remove-unlocked-bootloader-warning-t3294590
SGCMarkus said:
Thats the bootloader, telling you its unlocked.... thats before/during the splash screen i think...
I doubt we can get rid of it, except locking your bootloader again probably? (is that even possible on a H930/US998?)
Click to expand...
Click to collapse
Bootloader unlock warning has always been able to be replaced on Motorola phones. It's simply a static boot logo graphic.
When you unlock a Motorola bootloader, the "regular" M logo gets replaced by a scary "bootloader unlocked warning". Both are simple static graphic files. I've made lots of them for Motorola phones, which could be flashed via ADB or even TWRP. Surely LG is the same?
What do people do for the bootloader unlocked open market LG G5, V20, LG G6? They don't put up with that annoyance do they?
I suppose if the image the bootloader draws for a short time over the splash screen is stored somewhere else than the bootloader itself (aka not hardcoded), im sure it could be replaced, but someone has to find out where its stored how xD
SGCMarkus said:
I suppose if the image the bootloader draws for a short time over the splash screen is stored somewhere else than the bootloader itself (aka not hardcoded), im sure it could be replaced, but someone has to find out where its stored how xD
Click to expand...
Click to collapse
Yes, on some phones it's called the splash screen. Also, called the boot logo, not to be confused with the boot animation.
Surely people have done it. I've not messed with LG phones since LG G2/G3 and then I never really unlocked the bootloader but used exploits to install TWRP and root. But it's common with Motorola phones.
If you want to figure out the format of the raw_resources partition, that is where all the images are stored. It is possible to change them, but if you mess up, then your phone is a brick since abl will not load -- which is why the risk just wasn't worth it for me.
They are RLE so they have no header. There is an index that gives the name and offset for the location of the image, but not the size (either they are all the same size, or the size is stored somewhere else).
-- Brian
runningnak3d said:
If you want to figure out the format of the raw_resources partition, that is where all the images are stored. It is possible to change them, but if you mess up, then your phone is a brick since abl will not load -- which is why the risk just wasn't worth it for me.
They are RLE so they have no header. There is an index that gives the name and offset for the location of the image, but not the size (either they are all the same size, or the size is stored somewhere else).
-- Brian
Click to expand...
Click to collapse
What if you just want a different boot animation?
Is replacing the Zips in system - media safe?
Or just out right delete them? I hate that T-Mobile logo with a passion.
Sent from my LG-H932 using XDA Labs
Edit, I figured it was safe but to be sure I tested on my V20.
Now I customized my v30 .
Perhaps better yet (though I need some more people to help confirm this)...
I have successfully removed the bootloader warning for my unlocked US998.
The process is simple but try at your own risk for other variants more dissimilar to the US998 etc.. etc..
Steps:
Verizon (in their infinite wisdom) thought "Oh hey, no one will ever ever ever get the LG V30 with our software and have an unlocked bootloader, so why even bother having an unlock warning. "
Lets prove them wrong.
Take a backup (of course)
Go grab yourself the latest VS996_20d kdz file (available here on XDA or "LG-Firmwares")
Get your phone in LGUP mode (/w power off hold Vol-UP while inserting USB to computer)
In LGUP select PARTITION-DL and point it to the shiny VS996-20d kdz you waited so long for the download to complete
Click start then in the partitions list ONLY select raw_resources.
Click Ok.
The phone will do its thing and it will reboot and you will notice a black screen instead of annoying warning... Thanks Verizon. :silly:
Hope this helps!
That warning screen is nothing to even care about.
Sent from my LG-H932 using XDA Labs
SaberShip said:
Perhaps better yet (though I need some more people to help confirm this)...
I have successfully removed the bootloader warning for my unlocked US998.
The process is simple but try at your own risk for other variants more dissimilar to the US998 etc.. etc..
Steps:
Verizon (in their infinite wisdom) thought "Oh hey, no one will ever ever ever get the LG V30 with our software and have an unlocked bootloader, so why even bother having an unlock warning. "
Lets prove them wrong.
Take a backup (of course)
Go grab yourself the latest VS996_20d kdz file (available here on XDA or "LG-Firmwares")
Get your phone in LGUP mode (/w power off hold Vol-UP while inserting USB to computer)
In LGUP select PARTITION-DL and point it to the shiny VS996-20d kdz you waited so long for the download to complete
Click start then in the partitions list ONLY select raw_resources.
Click Ok.
The phone will do its thing and it will reboot and you will notice a black screen instead of annoying warning... Thanks Verizon. :silly:
Hope this helps!
Click to expand...
Click to collapse
It does get rid of the bootloader unlock warning, yes. However it now says you have a V30, even if you have a V30+. Depends on if that matters to you.
If someone has a phone under warranty and wants to be really brave -- null out raw_resources and you should just have a black screen.
Again, that is a risk since the loading routine in abl could have bugs and get wigged out and go into a loop or something. If that happens -- 9008 brick.
If someone wants to try it, boot to TWRP and:
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/raw_resources
reboot and tell us what happened
-- Brian
I thought about this because I liked customizing the boot on my old Motorola phones.
But then I thought, how many times do I actually restart my phone to care about how the boot screen looks?
95% of the time, your phone is on standby.
LOL @runningnak3d ^
Considering you can no longer decompile abl since it is encrypted, the only way to find out is to test it
-- Brian
I'd like to, but this phone as of Saturday, is still worth nearly 500 in-store trade. I'm on the fence.
I can tell you that the only thing in raw_resources are the images that you see for things like the big errors and the charging images, and crap like that.
Someone has to do it. I would, but for some reason eBay doesn't want me to have a V30 .. they just want to tie up my money.
-- Brian
runningnak3d said:
I can tell you that the only thing in raw_resources are the images that you see for things like the big errors and the charging images, and crap like that.
Someone has to do it. I would, but for some reason eBay doesn't want me to have a V30 .. they just want to tie up my money.
-- Brian
Click to expand...
Click to collapse
I think I'd rather take my chances poking around in the binary with a hex editor before zeroing the whole partition. Zeroing would be asking for null pointer exceptions in your bootloader. I don't want to speculate what that might do. Who knows with LG... maybe it will re-lock the bootloader bahhaha....
As others have pointed out i'm not sure the reward is worth the time right now. There are a lot bigger problems yet to be solved with this device in terms of development.
Related
Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.
dbaOCP said:
Hi all,
I've just unlocked my H850 bootloader "successfully" if I may say. why ? Because once it's was done, I get warnings on boot.
The first one says: "Your device software can’t be checked for corruption." with an Orange triangle.
The I got a second one with a red triangle which says "Your device is corrupt. It can’t be trusted and may not work properly"
The first message appears for about 3 seconds then the second for about 8sec then the LG logo and it boots normally...
I still didn't flash the SuperSU zip file to root since I don't have an external storage.
What might be the effects of those warnings ? Should I be worried ? My phone is still working normally however...
How can I erase them ?
Should I keep going with the rooting process ?
Thanks in advance for your answers.
Click to expand...
Click to collapse
This has already been asked many times, just search in the bootloader unlock thread or in TWRP thread...
Back to the "problem", well, it's NORMAL, starting from Android Marshmallow on ALL devices with an unlocked bootloader will boot with those warning, so nope, nothing to worry about, and nope, at the moment is not possibile to remove those warnings
Thanks for your answer. I've seen such threads but no one is talking about the second warning in red. I'm asking specially for that one..
Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour
BahnStormer said:
Isn't this just the same as the warning that you get on Samsung devices where it pops up the alert to say "This device is not SE enforcing."
If you're unlocking the Bootloader, you're opening up something that logically (since you're opening the door to rooting the device), you can more easily compromise the device security - only fair that they warn you and stop the warnings from being suppressed, my devices have always worn that "branding" as a badge of honour
Click to expand...
Click to collapse
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?
After more than 6 months, I'd like to know if there is anything available to remove those message?
dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Afaik no
dsr250p said:
After more than 6 months, I'd like to know if there is anything available to remove those message?
Click to expand...
Click to collapse
Alas, not without a custom kernel for the stock firmware. I also have a bootloader unlocked rooted Nexus 6 running MM that doesn't display the warning. Why not? To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.
dbaOCP said:
Thanks you make me sure of my device again
Did you root it ? Is it mandatory to use an SD card or you could do it without it ?
Click to expand...
Click to collapse
You don't need an SD card to root.
Abort said:
To root the Nexus 6 with MM you had to flash a custom kernel. The developers of the Nexus 6 kernels were somehow able to eliminate the unlocked bootloader warning, but I haven't a clue as to what was needed for them to accomplish its removal.
Click to expand...
Click to collapse
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.
dsr250p said:
But the Nexus 6 is a different device than the LG G5, for some reasons it seems impossible to get rid off the warning message with the LG.
Click to expand...
Click to collapse
You are absolutely correct, and I share your lament that no H850 developer has appeared on the scene with a simple solution for the stock G5. Honestly Annoying has done some very slick work to install a userdebug kernel that permits the disabling of dm-verity, which might therefore eliminate dm-verity warnings. But as you will see at the following link, it is anything but simple. https://forum.xda-developers.com/lg-g5/how-to/guide-adb-root-rw-dm-verity-off-sprint-t3523499
Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.
dsr250p said:
Alright, I see. At this time I will take a distance of using this exploit called "dirtysanta", but hopefully some simple load still coming up.
Click to expand...
Click to collapse
You may want to think twice about DirtySanta. The OP states the following:
Working Devices:
- Verizon (VS995)
- Sprint (LS997)
- ATT (H910)
- Korean(F800L)
You'll note the H850 is not listed. Honestly Annoying's work is the only way I've seen to disable dm-verity on the H850, but there are too many drawbacks associated with it for me to try it simply to eliminate the "Your device software cannot be checked for corruption" warning.
I'll get back to this topic during the next 6 months to see if there is a better solution available. I am not in a hurry.
I have never read the about the red triangle warning
Welcome to DM-VERITY
Still_living714 said:
I have never read the about the red triangle warning
Click to expand...
Click to collapse
Here is an article that will tell you about dm-verity and the warnings it presents, including the very familiar orange triangle due to an unlocked bootloader. The red warning is different, and also discussed in the article.
https://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
As far as i know, someone in a china forum said that he had unlocked the F600S' bootloader successfully.
He first flashed a pre-rooted 5.0 TOT and change the build.prop to h901. Then, he flashed h901 6.0 kdz to his phone and the bootloader became h901 version.
Therefore, he could unlock the bootloader simply by entering "fastboot oem unlock", flashing H901's recovery and rooted the phone.
Some users said this method works but some said didn't and even bricked their phones into "Qualcomm HS-USB QDLoader 9008" mode.
I open this thread for raising attention and investigate whether this method really works or not, but please, DO NOT intend to perform this method unless it was proved to be safe.
If you can read Chinese, here is the source (please remove this link if it violates xda's rules):
http://bbs.gfan.com/android-8325666-1-1.html
i recommend, don't... unless u needed to do that then go
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
DarkestSpawn said:
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
Click to expand...
Click to collapse
Thanks for your reply. According to the source, those people changed their build.prop as below in order to flash h901's kdz:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By the way, as a H961N user, I also wonder that whether it works on dual sim model. Can we flash the modem and related apps separately in order to make dual sim working if bootloader has unlocked?
If memory serves correctly, Yes with an unlocked bootloader you could adb flash modem *BLAHBLAHBLAH* but idk how that works with dual sim phones.
I honestly get aggravated when I see certain users that say they make TOT or KDZ files when really they took it from other sites that aren't English and say they made it. If that was the case they would make a KDZ with stock everything for the device its for but replace the bootloader to the version from H901 and every LG v10 would be bootloader unlockable but somehow they are too busy or working on other TOTs and kdzs... Assinine lies. Sorry had to throw my two cents out there.
I'm so glad I didn't do this attempt yet. Just remembered I gave my backup phone away so I have nothing to fall back on if this fails. If no one tries this before I get it back I will try.
DarkestSpawn said:
I was attempting something like this awhile back. But I wasn't using the normal build.prop. There is one hiding in /cust/open_com_ds/cust_open_hk.prop that I assumed was what the LGUP program used to check vs the one in /system but apparently I was mistaken. Theoretically there isn't anything hardware wise different between the H901 and the H961N besides the dual sim. Those that don't use dual sim might try this. Otherwise I would wait. If there are any people out there that can make kdz's then all it takes is one person to do it right then everyone else can benefit. I might go ahead and try for shizas and googles.
Click to expand...
Click to collapse
Even though many of the pieces are the same, there could well be some fairly significant differences hardware-wise between the H901 and H961N. The two that I know are really close are the H961N (Hong Kong) and H962, if the kernel sources are identical then there isn't much difference between the two.
On the flip side though, there could be enough similarity to flash the H901's bootloader onto another device. The bootloader wouldn't need to worry about how any of the radio bits work, just avoid touching them.
DarkestSpawn said:
I'm so glad I didn't do this attempt yet. Just remembered I gave my backup phone away so I have nothing to fall back on if this fails. If no one tries this before I get it back I will try.
Click to expand...
Click to collapse
Please do report if you do this. Anyone else out there who is reading, we'd love to hear from you if you try this. While I hope you succeed, failure could well occur. Could you report what device you're thinking of trying this on?
There is a tool from Qualcomm which can allow you to write to the flash before the device boots. If your try fails, that tool could be used to write back what is "supposed" to be there and hopefully you won't have a complete brick. A simpler solution might be to use that tool to simply overwrite your device's bootloader with the H901 bootloader. Note there are 2 copies of the bootloader on the H962 and likely other devices and you'd need to get both. I imagine there are several, but here is one tool for extracting the KDZ files (my goal is to be able to construct modified KDZ files, but I haven't analyzed things enough yet, will likely take some time).
EDIT: What look to be the bootloader areas in the H901, H961N and H962 KDZ files appear to be at the same offsets and the same sizes. I cannot be certain, but this might very well be a workable strategy.
EDIT2: If someone does this, it may be helpful to know which H901BK firmware version you use. The known KDZ file is for 20c, so it may be handy to keep links to that. Once you've done the process, it would be helpful for you to dump copies of all the block devices on the phone. Knowing which one(s) have changed could lead us to how LG's bootloader marks a device as unlocked, leading to easier methods of unlocking (hmm, really need a binary diff utility).
emdroidle said:
Even though many of the pieces are the same, there could well be some fairly significant differences hardware-wise between the H901 and H961N. The two that I know are really close are the H961N (Hong Kong) and H962, if the kernel sources are identical then there isn't much difference between the two.
On the flip side though, there could be enough similarity to flash the H901's bootloader onto another device. The bootloader wouldn't need to worry about how any of the radio bits work, just avoid touching them.
Please do report if you do this. Anyone else out there who is reading, we'd love to hear from you if you try this. While I hope you succeed, failure could well occur. Could you report what device you're thinking of trying this on?
There is a tool from Qualcomm which can allow you to write to the flash before the device boots. If your try fails, that tool could be used to write back what is "supposed" to be there and hopefully you won't have a complete brick. A simpler solution might be to use that tool to simply overwrite your device's bootloader with the H901 bootloader. Note there are 2 copies of the bootloader on the H962 and likely other devices and you'd need to get both. I imagine there are several, but here is one tool for extracting the KDZ files (my goal is to be able to construct modified KDZ files, but I haven't analyzed things enough yet, will likely take some time).
EDIT: What look to be the bootloader areas in the H901, H961N and H962 KDZ files appear to be at the same offsets and the same sizes. I cannot be certain, but this might very well be a workable strategy.
EDIT2: If someone does this, it may be helpful to know which H901BK firmware version you use. The known KDZ file is for 20c, so it may be handy to keep links to that. Once you've done the process, it would be helpful for you to dump copies of all the block devices on the phone. Knowing which one(s) have changed could lead us to how LG's bootloader marks a device as unlocked, leading to easier methods of unlocking (hmm, really need a binary diff utility).
Click to expand...
Click to collapse
I think the only worry of trying this method is a complete hard brick. As you have mentioned, any qualcomm phone has a recovery mode and i guess it should be the "Qualcomm HS-USB QDLoader 9008" mode.
I have searched some information and turn out there are two 9008 mode. It depends on whether the phone messed with Qualcomm’s stuffs, if not, then the phone will enter the "new 9008 mode" and it can let you recover the phone easily by a backup emmc image. If it is, then the phone will enter the "old 9008 mode" and it required specific files and "programmer", however, file suitable for msm8992 hasn't been discovered. Therefore, if this method brick the phone into old 9008 mode, no solution at all.
The information i have refered to, don't know if it is correct:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
EDIT: The ro.expect.recovery_id should be "0x9260d50f08bef4a761309001fe20e5ab59508e78000000000000000000000000" (if you try it, double check by yourself)
some people said that they bricked the phone because of typing it incorrectly, but i don't know whether it is true or not
I have asked the people who bricked their phones from trying this method. It seems that they really made a typo on ro.expect.recovery_id and cause brick.
Also, i am pretty sure that those phones have gotten into the "old 9008 mode", therefore, "rawprogram0.xml, patch0.xml and prog_emmc_firehose_8992.mbn" are required for using QPST the fix the hard brick.
However, no suitable prog_emmc_firehose_8992.mbn for V10 has been discovered on the internet (even for the G4).
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Edit: As I can understand Chinese, I'm currently looking into the tutorial.
ivangundampc said:
I think the only worry of trying this method is a complete hard brick. As you have mentioned, any qualcomm phone has a recovery mode and i guess it should be the "Qualcomm HS-USB QDLoader 9008" mode.
I have searched some information and turn out there are two 9008 mode. It depends on whether the phone messed with Qualcomm’s stuffs, if not, then the phone will enter the "new 9008 mode" and it can let you recover the phone easily by a backup emmc image. If it is, then the phone will enter the "old 9008 mode" and it required specific files and "programmer", however, file suitable for msm8992 hasn't been discovered. Therefore, if this method brick the phone into old 9008 mode, no solution at all.
The information i have refered to, don't know if it is correct:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Click to expand...
Click to collapse
Useful, though I cannot speak to the reliability of that information. A different source has a tool they say comes from Qualcomm, which may be more reliable with newer devices. Please note, this is a source of claims, I don't know how reliable they are (they also don't provide much detail on the limits of the tool).
WillyPillow said:
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Edit: As I can understand Chinese, I'm currently looking into the tutorial.
Click to expand...
Click to collapse
I look forward to more detail/reports from that tutorial. Exact details would be invaluable.
I hoped that would work, but I feared the above possibility. The problem is which portions of the flash image sign which other portions of the image, and how many different keys does LG use? Your observation seems to suggest either the key used for signing the H901 aboot was not honored by the rest of the H962 firmware, or the key used for signing the H962 kernel wasn't honored by the non-unlocked H901 aboot (or both).
If the former case, then which are the pieces prior to aboot and can only those pieces be transplanted from a H901 while still preserving the dual-SIM functionality of the H962 (and H961N)? If the latter case, then I suspect you merely need to run a H901 kernel long enough to unlock the bootloader, then you can put back the H962 kernel and run that with the unlocked bootloader.
The other question is, which portions of the data unlock the bootloader? Is it a small change to the aboot portion? Is it changes elsewhere? Can those changes be isolated from the rest of the H901 firmware?
Just in case you didn't notice, I've got lots of questions. I hope I can figure out answers to some, but others I may not be able to answer. I'm currently targeting the kdztools portion.
@emdroidle
TBH I don't see anything not mentioned already. Basically the process is just
Flash 5.1 rooted -> modify build.prop -> flash H901 KDZ
Personally, I'm not going to do more risky experiments since I already RMA'd my last hard brick
Also, you might want to use IDA to take a look at aboot, which is basically an ELF binary. I had been doing that, but stopped after the brick.
WillyPillow said:
@emdroidle
TBH I don't see anything not mentioned already. Basically the process is just
Flash 5.1 rooted -> modify build.prop -> flash H901 KDZ
Personally, I'm not going to do more risky experiments since I already RMA'd my last hard brick
Also, you might want to use IDA to take a look at aboot, which is basically an ELF binary. I had been doing that, but stopped after the brick.
Click to expand...
Click to collapse
I understand. You're in a better position since LG will honor the warranty on your H962. They're a bit tougher if you get one outside Taiwan.
I was fearing we would have to take that approach. Worse, it looks like the firmware updates change aboot, which suggests settling on one version and trying to crack that is best. I wanted to try Plasma, but IDA is likely far enough ahead to beat Plasma. I'm just glad IDA has a Linux version.
WillyPillow said:
Personally, I injected the H901 aboot into an H962 DZ and flashed it onto my device a few months ago.
Long story made short, it was completely bricked, even without 9008 mode. I recommend you guys to be cautious with this method.
Click to expand...
Click to collapse
After some thought, I realized I should ask for some detail about the failed process you used for this. Did you flash both the aboot and abootbak slices? (/dev/mmcblock0p9 and /dev/mmcblock0p15 if I recall correctly)
If you flashed only aboot and ended up bricked, this seems to suggest it did in fact successfully execute the H901BK aboot, but the aboot decided the signature on boot was incorrect and halted. In this scenario if the portion before aboot had decided aboot had a bad signature, then it should have restored abootbak, which likely would have successfully booted the H962 kernel.
If you flashed both aboot and abootbak, this suggests the portion before aboot decided aboot's signature was wrong and it halted there. This doesn't rule out it successfully executing aboot and aboot deciding boot had the wrong signature, but it makes that less likely.
Hate to say it, but flashing only aboot doesn't really give us much information on the likelihood of flashing a full H901BK image onto a H962 being successful or not. The problem is there could be signatures in many places and any one of those could fail yet reproducing the original scenario would work perfectly.
emdroidle said:
After some thought, I realized I should ask for some detail about the failed process you used for this. Did you flash both the aboot and abootbak slices? (/dev/mmcblock0p9 and /dev/mmcblock0p15 if I recall correctly)
If you flashed only aboot and ended up bricked, this seems to suggest it did in fact successfully execute the H901BK aboot, but the aboot decided the signature on boot was incorrect and halted. In this scenario if the portion before aboot had decided aboot had a bad signature, then it should have restored abootbak, which likely would have successfully booted the H962 kernel.
If you flashed both aboot and abootbak, this suggests the portion before aboot decided aboot's signature was wrong and it halted there. This doesn't rule out it successfully executing aboot and aboot deciding boot had the wrong signature, but it makes that less likely.
Hate to say it, but flashing only aboot doesn't really give us much information on the likelihood of flashing a full H901BK image onto a H962 being successful or not. The problem is there could be signatures in many places and any one of those could fail yet reproducing the original scenario would work perfectly.
Click to expand...
Click to collapse
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
I'll do some research and thinking right now
WillyPillow said:
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
I'll do some research and thinking right now
Click to expand...
Click to collapse
Well, i think that you have bricked your phone into the "Qualcomm HS-USB QDLoader 9008" mode
The phone should be able to fix if you can see "Qualcomm MMC Storage USB Device" in "Devices Manager" when the phone is connecting to the computer.
WillyPillow said:
Hmm, I've never thought this deep. I was just like "Sxxt, my phone bricked! Must be a bad signature somwhere..." and stopped messing around with it
Click to expand...
Click to collapse
I was thinking about it, since I would very much like to somehow unlock the bootloader. While this way may or may not be tweaked to work, it does sound plausible. Analyzing failures can be very valuable.
WillyPillow said:
To answer your question, I only flashed aboot, without anything else. And for the details of the brick, you can't even see the "powered by Android" bootloader screen. The device just viberates if you want to turn it on. The only way to make the screen display something is remove the battery and connect it to a computer, for which a "no battery" icon is showed. So my guess then was the aboot signature was invalidated. But now you reminded me the existance of abootbak...
Click to expand...
Click to collapse
So this may suggest aboot successfully executed, but found a mismatched signature and halted. At which point, flashing the H901BK aboot and boot may be enough to make this work. This may though also require the H901BK recovery image. I do not know where the unlock process actually does its magic, so part of it could be in recovery.
I'd love to hear if you can get it to be successful.
Two threads relevant to this topic have shown up.
First, apparently someone somehow managed to accidentally flash a H901 firmware onto a H960A. That person was looking for help with restoring their device, but it leaves me hopeful this method could in fact work on other devices. Most likely you'd end up with a mix of some portions of the flash being copied from a H901 and some from whatever your phone is normally supposed to run, but this does confirm it is possible to run H901 firmware on other devices.
Second, a method has been found to recover devices from Qualcomm 9008 mode. This is big news since it greatly lessens the danger of a bad flash. Problem is it requires root on the phone to generate the initial image, though I suspect the images produced by my kdztools may well work for the job too.
I very much want to unlock the bootloader of my device, so I'm still doing research trying to estimate how plausible this method is. At this point there are enough reports of wrong V10 device images not being fatal to other V10-type devices for me to consider this method "likely".
Examining KDZ files for several devices, there is quite a bit of overlap between device images. There are 9 slices though which seem to warrant special attention based upon them having backup copies. These are named "sbl1", "pmic", "hyp", "tz", "rpm", "aboot", "sdi", and "raw_resources".
My guess is install a H901 image, do `fastboot oem unlock` and then you can copy everything aside these slices from your original device. My concern is these may need to remain the H901 versions in order to remain unlocked (unless all V10 devices share the unlock method, which may or may not be the case).
It may also work to use my KDZ Tools to copy the PrimaryGPT and BackupGPT areas from the target device onto a H901 image, at which point the process could be done without even needing a factory reset!
I'm pretty sure "sbl1"/"sbl1bak" are the first-stage bootloader. All the others aside from "raw_resources" look to be ELF executables.
Open request to Qualcomm here, could you please make your chips either alternate between trying to boot off of "sbl1" and "sbl1bak" (a single MRAM or PCRAM cell should take too much space, should it?), or else make them randomly choose between booting off them upon power-on? Too often one or the other gets corrupted in such a way that booting fails, but either isn't so corrupt to trigger them to try the backup, or else the primary is so badly damaged it is unable to try the backup. Alternating (and passing to the Linux kernel which one it successfully booted off of!) would greatly increase the chances of successful recovery without specialized tools.
Wiki + Likelyhood evaluation
Having examined the situation enough, I'm pretty sure this method should work. Experimentation though is risky.
I'm now working on creating 2 software tools for this project. One is a simple tool to remark the device a KDZ is for. This is pretty simple and the reports are, once this is done LGUP will happily flash a KDZ onto other devices. The second goal is a tool for modifying the GPT afterwords. While the H901 has a GPT similar to other V10s, it isn't quite identical. Of major note, many other devices have a /cust partition which has some extra software.
These two tools may actually be unnecessary. My KDZ Tools expose all of the data in an inconvenient, but workable format. The KDZ Tools can also be used to replace the GPT for the H901 with a GPT from another device, and they also expose the areas which mark which device a KDZ is for. Problem with using the KDZ Tools for this is there is what looks to be an extra checksum, and I've got no idea whether it covers the GPT (I hope not, but...).
I'm now looking to create the above two tools on GitHub, the LGE Tools. Alas, what may be more valuable is the Wiki on GitHub. I've got speculative instructions a little ways from the top. Towards the bottom I've got a list of which areas you'd need to restore from your original device. I guess I'm a bit unsure of "persist", the content is identical for my device, but the differing timestamps might trigger a flag that something has happened.
Hopefully we can get some testers who can risk needing to RMA their devices (I hope they don't need to, but this IS risky).
emdroidle said:
Having examined the situation enough, I'm pretty sure this method should work. Experimentation though is risky.
I'm now working on creating 2 software tools for this project. One is a simple tool to remark the device a KDZ is for. This is pretty simple and the reports are, once this is done LGUP will happily flash a KDZ onto other devices. The second goal is a tool for modifying the GPT afterwords. While the H901 has a GPT similar to other V10s, it isn't quite identical. Of major note, many other devices have a /cust partition which has some extra software.
These two tools may actually be unnecessary. My KDZ Tools expose all of the data in an inconvenient, but workable format. The KDZ Tools can also be used to replace the GPT for the H901 with a GPT from another device, and they also expose the areas which mark which device a KDZ is for. Problem with using the KDZ Tools for this is there is what looks to be an extra checksum, and I've got no idea whether it covers the GPT (I hope not, but...).
I'm now looking to create the above two tools on GitHub, the LGE Tools. Alas, what may be more valuable is the Wiki on GitHub. I've got speculative instructions a little ways from the top. Towards the bottom I've got a list of which areas you'd need to restore from your original device. I guess I'm a bit unsure of "persist", the content is identical for my device, but the differing timestamps might trigger a flag that something has happened.
Hopefully we can get some testers who can risk needing to RMA their devices (I hope they don't need to, but this IS risky).
Click to expand...
Click to collapse
Wow, i am very surprised that you are still working on this method! You have really paid a lot of effort on it!
After taking a look on your works, i really think that this method may really works to help us to unlock the bootloader.
In fact, the T-Mobile variant of both G5 and V20 have bootloader unlocked and so other version of G5 and V20 may also be able to unlock their booloader through a method like this, therefore, I think we should be able to draw more attention (more devs?) on studying this method.
Hello,
As the title says, I'm wanting to root my new CAT S61. Anyone managed to unlock the bootloader yet? I've played around with it but haven't had any luck so far.
+1, Me too. Just started debating them on facebook, to maybe have some pressure on to unlock the bootloader the nice way. Until that I am ready to donate. I really miss htc sense, coming from 10-year htc spree.
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
I really miss the sense freestyle themes, where there is no grid and you pick a theme with background image(can be changed) and stickers (just some themed icons with different sizes). Then you place your stickers and assign apps to them. I myself used an archtecure theme, where there were stickers varying feom minimalistic monopoly houses up to vertically big skyscrapers and horizontally long trains. For my gf I made nature theme with nice summer bliss and clouds, deers, rabbits, butterflies and birds. Its just so customizable. I hate being restricted to grids or standard sizes icons or their 2x, 4x and so on.
k46tank said:
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
Click to expand...
Click to collapse
---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------
I just received a 130MB OTA, I hope it was not a security update, casting me out of the gang, when someone finds the cure for the older build. The build LTE_D0201121.0_S61_0.040.02 gave me Flir Youtube streaming option.
luc1fer said:
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
Click to expand...
Click to collapse
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is ? I'm getting a bit ahead of myself!
Just received another OTA, September 1st patch, LTE_D0201121.0_S61_0.046.02. Radio is LTE_D0201121.1_S61 after the update. This one was larger, but I forgot to screenshot the exact changes and size.
luc1fer said:
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is I'm getting a bit ahead of myself!
Click to expand...
Click to collapse
Is any progress?
I am not a programmer, and can not help anything. Looking forward good news!!
Hi there, also looking forward for root, will hopefully get the phone end of the year...
ogghi said:
Hi there, also looking forward for root, will hopefully get the phone end of the year...
Click to expand...
Click to collapse
I will not buy it until it is rootable.
Nope, no luck as of yet... Nothing I seem to try is giving me any options or progress.
Rather frustrated carrying round 2 devices lol one for root apps and the s61 for everything else!
Still impressed at the phone though, VERY utilitarian!
Hey there, I will get my S61 tomorrow.
Was hoping for any root idea, but will hopefully survive without until we have the privilege to get it
... and there is no option in the programmer options (unlock bootloader)?
Did not stumble upon such a function yet.
The most annoying thing without root is missing a good ad blocking. dns66 seems to work, but there are still plenty of ads in apps that get through...
Also having potentially all power unlocked would be great!
So no news here I guess?
To enter bootloader:
1.switch of your phone
2.press volume down
3.conect the power cable
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
james35888 said:
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
Click to expand...
Click to collapse
This doesn’t work since the boot loader is locked (stock boot loader has not been released on the web to my knowledge)
---------- Post added at 01:55 AM ---------- Previous post was at 01:38 AM ----------
Knuxyl said:
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
Click to expand...
Click to collapse
Are these commands on a computer through ADB?
The only options I had on the phone were:
-Start
-Recovery Mode
-Restart Bootloader
-Power Off
-Boot to QMMI
-Boot to FFBM
Hi,
I looked a bit into the process of rooting on this device. It would be cool to get it rooted. I guess this process is in theory simple. But we should focus on the first problem:
Why is the option "OEM unlock" hidden in the developer Menu? Are there ways to make that option usable? If anyone has an idea how to make this option usable, we could get to the next step. Thanks to anyone who has an contribution.
Edit: some additional info
C:\adb\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
CatS61:/ $ getprop | grep oem
[ro.oem_unlock_supported]: [true]
[sys.oem_unlock_allowed]: [0]
So I have a bit of an unusual question. I bought an AT&T variant of LG V30 (H931). I had to return it to an eBay seller, but before I sent it, I didn't wipe it, and I have forgotten the random password that I used to play with the phone (not logged in to anything). Now the phone is back in my possession. Is there anyway to wipe it without knowing the password? I thought I could oem unlock it, then relock it, then that would wipe (twice). But I can't get into bootloader via the usual "vol down+power" or even "vol down+vol up+power". Some say the AT&T V30 has a crippled bootloarder so you can't do fastboot. And I can't use any of the guides that involve adb because I can't unlock it!
What are my recourse besides selling for parts?
Thanks
??
chochopk said:
So I have a bit of an unusual question. I bought an AT&T variant of LG V30 (H931). I had to return it to an eBay seller, but before I sent it, I didn't wipe it, and I have forgotten the random password that I used to play with the phone (not logged in to anything). Now the phone is back in my possession. Is there anyway to wipe it without knowing the password? I thought I could oem unlock it, then relock it, then that would wipe (twice). But I can't get into bootloader via the usual "vol down+power" or even "vol down+vol up+power". Some say the AT&T V30 has a crippled bootloarder so you can't do fastboot. And I can't use any of the guides that involve adb because I can't unlock it!
What are my recourse besides selling for parts?
Thanks
??
Click to expand...
Click to collapse
Well if you want bootloader, Frankenstein to US998.
I actually want to restore it to its original state. And stable.
chochopk said:
I actually want to restore it to its original state. And stable.
Click to expand...
Click to collapse
AT&T doesn't release KDZ publicly. Here's this if it can help:
david.542569 said:
H931 20F 8.0 Dump
[https://drive.google.com/file/d/108pDh0yFzyAQqQ-F7kXDnOSdb6z2CIdD/view?usp=drivesdk
Compressed with ZArchiver App In 7z format 2.4 GB
Click to expand...
Click to collapse
Somebody bought a phone recently which had been factory reset with with locked password and they googled how to get around it. Maybe that can help? I'm not sure that will help you return to seller if that's what you want...
The only other thing you can do possibly is convert to US998, unlock bootloader, fix it, lock bootloader back and sell it as US998.
It's not google locked, it just has a random password, right? You should be able to master reset and clear it.
-Power off
-Power on holding power button and volume down.
-As soon as LG symbol comes across the screen, release the power button and then press+hold it again
-Follow directions to wipe phone.
Pretty sure that will fix it. If it's google locked, there's a youtube video on how to do it. Generally mods get upset here if you post it, so google is your friend.
ChazzMatt said:
AT&T doesn't release KDZ publicly. Here's this if it can help:
Somebody bought a phone recently which had been factory reset with with locked password and they googled how to get around it. Maybe that can help? I'm not sure that will help you return to seller if that's what you want...
The only other thing you can do possibly is convert to US998, unlock bootloader, fix it, lock bootloader back and sell it as US998.
Click to expand...
Click to collapse
H931 20H Dump
[https://forum.xda-developers.com/lg-v30/development/lg-v30-att-h931-20f-rom-t3872926
Not sure if anyone had seen this or tried it and seen if it did in deed work, if no one tried, i aint scared, ill try it myself...
https://myphoneupdate.com/unlock-bootloader-lg-v60-thinq-5g/
Today I was chatting with LG on Twitter DM an asked about an CARRIER UNLOCKED Version which would be available in the near future with NO DATE.
I also asked about Unlocking the Bootloader in this Beast and hopefully get some custom magic going because i thought LG had a Dev site at one time. I been using Android since July 2010, HTC EVO, Sprints 1st Android. I had a v40 or v40 which i upgraded in the store, and i hated everything about it : Felt Cheap as HELL, hate the LG Version of Android and if i will NEVER be able to change that stock firmware, i dont want it. I'll sit on my Pixel 4XL a little longer when the Moto Edge+ becomes available...
Hot damn. I popped up a thread about this the other day asking if anyone had given it a shot yet. So far no Canadian carriers have the phone, let alone buying it directly, so I'm in no position to try it out but I'll be watching this thread with keen interest.
my oem toggle was able to be switched when i just got, can only boot to fastbootd though...
TeeJay420 said:
Not sure if anyone had seen this or tried it and seen if it did in deed work, if no one tried, i aint scared, ill try it myself...
https://myphoneupdate.com/unlock-bootloader-lg-v60-thinq-5g/
Today I was chatting with LG on Twitter DM an asked about an CARRIER UNLOCKED Version which would be available in the near future with NO DATE.
I also asked about Unlocking the Bootloader in this Beast and hopefully get some custom magic going because i thought LG had a Dev site at one time. I been using Android since July 2010, HTC EVO, Sprints 1st Android. I had a v40 or v40 which i upgraded in the store, and i hated everything about it : Felt Cheap as HELL, hate the LG Version of Android and if i will NEVER be able to change that stock firmware, i dont want it. I'll sit on my Pixel 4XL a little longer when the Moto Edge+ becomes available...
Click to expand...
Click to collapse
Bootloader
How were you able to get into fastboot when I try to ADB fastboot it just returns me back into the phone OS
Just fyi, the phone isn't listed on LG Devs website as being supported by this method (as of this posting): https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0703
Also, I got a bit dubious, because in some sections of the article, he refers to the phone as the LG V40 ThinQ -- and yeah, it looks like a copy-paste of this article: https://myphoneupdate.com/unlock-bootloader-of-lg-v40-thinq/, The LG V40 ThinQ IS a supported device, BUT ONLY THE EU MODEL. In fact, if you live in the US, my hunch is you'll be SOL, and only the EU V60 Tq will be bootloader unlockable.
Edit: Both articles on this site look like just the official LG documentation with some words changed and some links to go get things like ADB: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702
Unlocked bootloader
I'm on T-Mobile
Bootloader
That's the funny thing I'm able to toggle oem unlock on and off
TeeJay420 said:
What carrier are you? And if i find you a way to get into fastboot?I dont have device, basing it on Unlocking Bootloader...
Click to expand...
Click to collapse
I'm on T-Mobile as soon as I walked out of the store I turned on dev options and could toggle the switch, it stayed on with a factory reset too
Rob0225 said:
That's the funny thing I'm able to toggle oem unlock on and off
Click to expand...
Click to collapse
Using an engineering ROM on my S9+, I can toggle OEM lock on and off and it doesn't seem to do anything. Rather, it does let you ADB reboot fastboot, but no actual interface exists once booted to send commands to the phone. Then it throws a weird error message on the phone screen (been too long, can't remember what), does a dump, then reboot back to system.
Maybe this is a similar principle, since you noted earlier that you are unable to get into the bootloader via the reboot command.
Rob0225 said:
How were you able to get into fastboot when I try to ADB fastboot it just returns me back into the phone OS
Click to expand...
Click to collapse
If OEM unlock is exposed in dev options by the current V60 OS build, but rebooting fastboot just sends you back to system, then LG's maybe done some extra work like Sammy to make sure people can't actually send commands to the bootloader.
Rob0225 said:
How were you able to get into fastboot when I try to ADB fastboot it just returns me back into the phone OS
Click to expand...
Click to collapse
adb reboot fastboot brings you to "fastbootd"
---------- Post added at 11:25 PM ---------- Previous post was at 11:24 PM ----------
TeeJay420 said:
So i assume you are carrier LOCKED and owe $ on device? You cant UNLOCK BL until you are carrier UNLOCKED....
Click to expand...
Click to collapse
As long as you can toggle on oem unlock it doesn't matter. Being carrier unlocked allows the switch to be toggled. I'm on eip and as I stated it was able to be turned on out of the box after the sim was put in.
Bootloader
So who makes the decision to lock the bootloader on the phone carrier or LG apparently the source code kernel is out that's a good start
https://www.getdroidpro.com/lg-v60-thinq-5g-root-via-magisk/
Just something I found on the inter webs
---------- Post added at 01:43 PM ---------- Previous post was at 01:39 PM ----------
I just got my v60 so there probably not going to unlock it
So even if OEM unlock is toggled on, do we still need to be carrier unlocked? Also, with OEM unlock enabled I am only able to boot into fastbootd and recovery. Trying to boot to the loader just goes to system
I guess I'll try to call T-Mobile and make up some kind of lie to unlock lol
Great, now can someone find out when us Canadians get this bugger in our paws?! Hahaha
I assume no one has had no luck to this very moment trying to access the bootloader? I have a buddy of mine from Bliss ROMs trying to help me but who knows what will come out of it ??
I really want to get this phone and the OEM unlock doesn't surprise me with lgs but what ya wanna bet that LG still removed almost all adb/fastboot commands even after bootloader unlock.
They've been doing this since the v30 and that's when I left LG. I miss LG.
If you try fastboot boot or fastboot flash etc, it will say command not found or something unless they changed it back which I hope so cause I hate OnePlus' cameras
Josh McGrath said:
I really want to get this phone and the OEM unlock doesn't surprise me with lgs but what ya wanna bet that LG still removed almost all adb/fastboot commands even after bootloader unlock.
They've been doing this since the v30 and that's when I left LG. I miss LG.
If you try fastboot boot or fastboot flash etc, it will say command not found or something unless they changed it back which I hope so cause I hate OnePlus' cameras
Click to expand...
Click to collapse
You can only boot into fastbootd, booting to the bootloader will bring you back to system... I may return this for the 7t pro McLaren tbh even though the battery life on this is so amazing
Some_Ghost said:
You can only boot into fastbootd, booting to the bootloader will bring you back to system... I may return this for the 7t pro McLaren tbh even though the battery life on this is so amazing
Click to expand...
Click to collapse
I would never trade the battery life in this phone for the McLaren battery life. I'd have to cry myself to sleep every night.
Sent from my LM-V600 using Tapatalk