The Development thread has been opened. Please refer HERE
This is THE best root method I have ever used. Y'all are gonna love this.
Very sweet- cannot wait! If you guys need a tester, let me know.. I'm still stock.
Totally excited about this new development. Thanks for sharing and caring.
Sent from my EVO using XDA
You guys are the best!!!
Now that is how I like it, rooting for dummies, no offense. Looking forward to it to root and open up this Beauty and the Beast phone.
Thanks,
Ian B
Very Cool. If we are rooted but still have bootloader locked will we be able to use the automated bootloader unlock option? Or does the phone have to be completely stock?
What about those of us already rooted via the method available?
Will your method also unlock the bootloader for those already rooted OR is this method only workable from an Unrooted and Locked beginning point?
Does my question make sense?
Mr Ian B said:
Now that is how I like it, rooting for dummies, no offense. Looking forward to it to root and open up this Beauty and the Beast phone.
Thanks,
Ian B
Click to expand...
Click to collapse
That is what I've always been striving for in everything I release. Easy to use and understand.
purock said:
Very Cool. If we are rooted but still have bootloader locked will we be able to use the automated bootloader unlock option? Or does the phone have to be completely stock?
Click to expand...
Click to collapse
typhoonikan said:
What about those of us already rooted via the method available?
Will your method also unlock the bootloader for those already rooted OR is this method only workable from an Unrooted and Locked beginning point?
Does my question make sense?
Click to expand...
Click to collapse
I have had the exact same thought process while developing this, and my answer right now is, most likely. I haven't tested what happens if you try to unlock the bootloader when it's already unlocked. If you are already rooted and have a locked bootloader still, this will work. Just remember that unlocking the bootloader resets your ROM to stock (deletes all user data). All this will be tested before release and answered clearly though
Regaw,
Would it be possible to have an alternate version or option that solely does the recovery image? Let's say someone already were able to get SU on their device with the other method but struggled with fastboot, for example. They wouldn't necessarily want to start over with a new, unrooted/stock ROM.
Is this possible or perhaps too remote of a request to be relevant? I'm in that small minority now I guess, lol.. Got tampered screen, got root on phone, but cannot get recovery pushed to it.
logie said:
Regaw,
Would it be possible to have an alternate version or option that solely does the recovery image? Let's say someone already were able to get SU on their device with the other method but struggled with fastboot, for example. They wouldn't necessarily want to start over with a new, unrooted/stock ROM.
Is this possible or perhaps too remote of a request to be relevant? I'm in that small minority now I guess, lol.. Got tampered screen, got root on phone, but cannot get recovery pushed to it.
Click to expand...
Click to collapse
Unfortunately, you have to unlock the bootloader before you can flash a recovery, and unlocking erases all user data on the phone anyways. So, you really do have to start over. But this application takes care of everything.
Just tested the process on my OG EVO (I left out the actual rooting/flashing so I didn't ruin my phone ) but the process looks nice and works well
{
"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"
}
Wait am I understanding this correctly that this will unlock the bootloader and HTC will be none the wiser? Because that would be awesome!
Sent from my EVO 4G LTE
Well, it uses your phone's unlock token (obviously has to in order to unlock your own device), but not your login information to htcdev. Every time you call
Code:
fastboot oem get_identifier_token
the token is randomly seeded (different), so I don't know exactly how "traceable" the token is back to your device.
I didn't want to use htcdev to unlock my bootloader, so I've been waiting for something like this.
very impressive! but you're taking all the fun away, lol
O.M.J said:
very impressive! but you're taking all the fun away, lol
Click to expand...
Click to collapse
Trust me.. I know what you mean But that's why I made it look similar to a terminal on the phone haha, had to make it seem cool to us somehow
EDIT: grrrrrrrrrrrrrrrrrrrrrrrrrrrr
clownfart said:
I didn't want to use htcdev to unlock my bootloader, so I've been waiting for something like this.
Click to expand...
Click to collapse
well ur still using HTC Dev with this in a sense...so dont think your avoiding that one...like he said you just dont have to log into it with your account...though if that was your only worry of HTC Dev Unlock then you could just create a fake acocunt on there to unlock the device...
outstanding work though regaw!!
makes it nice for those users that dont wanna mess with fastboot and all...to unlock...
So this will give me S-off?
just kidding - saw you removed the video link when I got back to my comp, something wrong with the vid?
Related
Q&A for Team Infernal FakeCid AUTOMATIC bootloader unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Team Infernal FakeCid AUTOMATIC bootloader unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
FakeCID Automatic Unlock Failed
Here's a screenshot. I don't know if the failure to write the files to the SD card caused the failure. Did I miss anything on setting this up? I exited the script rather than do a factory reset. I saw the note about doing a factory reset and then trying again, but if this is related to the file write failure, I'd rather not reset the phone and have to set it all back up again.
{
"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"
}
I assume you're working on getting s-off. Working from that I expect you have the most recent update from almost a year ago. If you do then this thread should get you to where you want to go.
crokett said:
Here's a screenshot. I don't know if the failure to write the files to the SD card caused the failure. Did I miss anything on setting this up? I exited the script rather than do a factory reset.
Click to expand...
Click to collapse
No. I am working on unlocking the bootloader so I can install a custom recovery. Hence the thread title. Is S-Off a requirement to unlocking the boot loader? I didn't see anything that says it is.
S-off makes installing ROMs easier because you don't need to extract the boot.IMG each time. S-off gives you more options but opens you up to a little more risk of you mess up. Read a bit more on the differences between an unlocked bootloader and s-off. If I can find a few links I'll as then tomorrow to help you out.
Sent from my Nexus 7 using XDA Free mobile app
Thanks. I have done some reading and I am reasonably familiar with S-OFF. I think my problem is that I need to factory reset the phone before I try the bootloader unlock. The HTCDev site doesn't support this phone for a bootloader unlock. I'm not quite ready to do a factory reset yet so I will wait a bit longer.
Installing a custom ROM will require a factory reset, so when you're ready for that go for it. An app like this https://play.google.com/store/apps/details?id=com.koushikdutta.backup makes the transition much easier.
Ok I believe I know why the unlock is failing. My sdcard for some reason is getting mounted as read only, or at least the script thinks it is.
This is from the script:
Code:
db shell "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4"
and line that tries to dump the mcblk0p4 file to the sdcard to pull it to the PC fails. I thought that the error I was getting was related to backups. this page:
http://forum.xda-developers.com/showthread.php?t=1986346
says that you need to remove mmcblk0p4 from the directory if you run the script multiple times.
So it appears that after the 'adb restore fakebackup.ab' command is run, at least on this phone the sdcard is mounted as read-only. Is there a way around this? can adb push/pull the file from phone storage directly to and from my PC if I want to edit the file manually?
Or, does anybody have a backed up modified file for this phone that they can send me? I am stuck at dumping the file to the sdcard so that I can modify it, but I think I can push a modified file to the phone so that I can then go to HTCDev to get it unlocked
An update. I followed the manual steps and was able to get the file with the CID in it off the phone. I edited it as per the directions, then pushed it back to the phone and used dd to push it back to /dev/block however after I rebooted the phone and did the readcid command, it still has the stock Verizon CID. Any help?
One last update, I tried both the manual method and the automatied script after factory resetting the phone. That did not work either. Any suggestions? I'd really like to get this phone rooted if I can. If it helps or matters, my phone device type starts with an FA, not the HT that the script calls out.
The script works up to the point that I run the dd command to write the modified file back to /block. The dd command works, but checking the OEMCID it is still the Verizon CID. Do I need to S_OFF the phone first? I didn't think that was related to this.
crokett said:
One last update, I tried both the manual method and the automatied script after factory resetting the phone. That did not work either. Any suggestions? I'd really like to get this phone rooted if I can. If it helps or matters, my phone device type starts with an FA, not the HT that the script calls out.
The script works up to the point that I run the dd command to write the modified file back to /block. The dd command works, but checking the OEMCID it is still the Verizon CID. Do I need to S_OFF the phone first? I didn't think that was related to this.
Click to expand...
Click to collapse
After reading the thread, I am not sure why you wouldn't just go with s-off instead of only unlocking the bootloader. Yes, there's more risk in having an s-off phone, but it does make life much easier overall. However, If you are able to s-off the phone, you're done - no need to further work on unlocking the bootloader because the phone is fully unlocked (and it will stay that way unless you explicitly lock it). It also seems as though the s-off methods are now more tried and true for this phone versus just unlocking the bootloader.
Instead of continuing to struggle to just unlock the bootloader, you may try just going full out s-off. Just back up what you can - contacts to Google Contacts, USB cable to pull off your files/music/whatever to your PC, etc. then go for it. Make sure you are using the s-off method that matches your phone's current version.
Good luck!
junkmail9 said:
After reading the thread, I am not sure why you wouldn't just go with s-off instead of only unlocking the bootloader. Yes, there's more risk in having an s-off phone, but it does make life much easier overall. However, If you are able to s-off the phone, you're done - no need to further work on unlocking the bootloader because the phone is fully unlocked (and it will stay that way unless you explicitly lock it). It also seems as though the s-off methods are now more tried and true for this phone versus just unlocking the bootloader.
Instead of continuing to struggle to just unlock the bootloader, you may try just going full out s-off. Just back up what you can - contacts to Google Contacts, USB cable to pull off your files/music/whatever to your PC, etc. then go for it. Make sure you are using the s-off method that matches your phone's current version.
Good luck!
Click to expand...
Click to collapse
thanks for confirming that. I misunderstood what S_OFF did, else I might have done it sooner. I did not realize that it also unlocks the phone as a whole. I thought it gave access to the radios, etc which I wasn't necessarily interested in.
crokett said:
thanks for confirming that. I misunderstood what S_OFF did, else I might have done it sooner. I did not realize that it also unlocks the phone as a whole. I thought it gave access to the radios, etc which I wasn't necessarily interested in.
Click to expand...
Click to collapse
Yep. S-Off is the full unlock. Once achieved, you can do whatever you want to the phone, including updating the radio (be very careful!), install a custom recovery, install a new kernel (from the SD card), install full ROMs without needing to push anything separately, mess with partitions, etc. IMHO it is the best way to go, but just be careful after achieving s-off, one wrong keystroke or click while connected to your PC, you can very easily make yourself an expensive paper weight.
Also, if you are installing custom ROMs, on this phone it does make a difference which recovery is installed. ViperLTE will not install properly with a CWM variant, but installs just fine with TWRP.
Success!!! many thanks to wmuflyer for pointing me to rumrunner for S_OFF. the phone is now S_OFF and the bootloader is unlocked. thanks for all the suggestions.
Congratulations. Now the fun begins. And remember you can always use the thanks button.
Sent from my Nexus 7 using XDA Free mobile app
Hi everyone, my phone is s-off but locked bootloader how can I unlock it?
Hello,
I purchased an LG V30 on Swappa but noticed the launcher has a userdebug water mark on the launcher. Does anyone know what it is exactly? Is it a pre-production unit? Can't really find much information on it. Here are some pictures of the phone and the userdebug: https://imgur.com/a/FfPUd
Can I flash a stock KDZ to remove the weird firmware it currently has? Where can I find it?
Let me know what you guys think? Should I just return the phone and get another one?
Thanks!
woundman said:
Hello,
I purchased an LG V30 on Swappa but noticed the launcher has a userdebug water mark on the launcher. Does anyone know what it is exactly? Is it a pre-production unit? Can't really find much information on it. Here are some pictures of the phone and the userdebug: https://imgur.com/a/FfPUd
Can I flash a stock KDZ to remove the weird firmware it currently has? Where can I find it?
Let me know what you guys think? Should I just return the phone and get another one?
Thanks!
Click to expand...
Click to collapse
or possibly you can unlock your bootloader and root your phone.
{
"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"
}
And maybe you could help others that way with rooting/unlocking their H931, which normally wouldnt be possible (atleast no way known currently).
ChazzMatt said:
or possibly you can unlock your bootloader and root your phone.
Click to expand...
Click to collapse
What do you think I should do?
woundman said:
What do you think I should do?
Click to expand...
Click to collapse
See if OEM bootloader unlock works...
If so, then run some fastboot commands. Someone else lucked into another phone like that. I'll see If I can find the posts...
Sent from my carrier unlocked LG V30+ US998
ChazzMatt said:
See if OEM bootloader unlock works...
If so, then run some fastboot commands. Someone else lucked into another phone like that. I'll see If I can find the posts...
Sent from my carrier unlocked LG V30+ US998
Click to expand...
Click to collapse
Okay, thank you. So you don't think there is any issue with the phone? It's in flawless condition and from what I can tell runs fine. I haven't tested it throughly though. Going to run benchmarks tonight.
Will there be any issues relocking the phone?
Thank you OP for taking the advise from us on Reddit and posting your question here on XDA I am hoping your phone is the key to rooting us with AT&T versions of this phone
See this post and the other posts before and after. Curious if your phone is like that one...
https://forum.xda-developers.com/showthread.php?p=74790875
jcradio said:
I have a interesting situation. Recently I got a LG V30 Plus from T-Mobile. Unpacked the phone and set it up. Everything appeared to work as expected. However trying to get the fingerprint scanner to work seems impossible because there is nothing in settings to set it up. In settings under the General Tab, there should be a fingerprints and security tab. My phone only shows security and is missing the fingerprint settings. I spoke with T-Mobile tech support who put me in touch with LG tech support. It turns out I was given a DEMO version of the phone, even though LG says it is a international version. The reason I say it is a DEMO version is because it makes sense to remove the fingerprint feature so on one can come along and lock the phone. My point is, or shall I say my question is, is it possible that my phone does not have all the security as the standard phones, therefore making it possible to gain root? Is there a way I can test my phone to see if I can gain root. I have rooted phones in the past, just curious if my phone can be a way to gain root for the DEV. Looking forward to some responses.
Click to expand...
Click to collapse
jcradio said:
Model - LG-H932
Click to expand...
Click to collapse
20degrees said:
Are the adb commands stripped?
Click to expand...
Click to collapse
20degrees said:
Don't return it yet. Are the adb commands missing/stripped?
Click to expand...
Click to collapse
jcradio said:
I tried a few commands and they seem to work.
I tried the following:
adb shell
pm uninstall -k --user
Just let me know what commands to try to see if any have been stripped.
Click to expand...
Click to collapse
NotATreoFan said:
ADB commands aren't missing from our V30 retail models. What's missing is the Fastboot commands.
So after enabling Developer Options, and ticking Enable OEM Unlocking, type "ADB reboot bootloader" and then try "fastboot oem unlock".
If that works, you will truly have struck gold.
Sent from my LG-H932 using Tapatalk
Click to expand...
Click to collapse
jcradio said:
I did as you mentioned and it worked.
Click to expand...
Click to collapse
Sent from my carrier unlocked LG V30+ US998
Ooh we're getting so close to unlocking this phone's potential. So exciting. If an experienced dev can get their hands on either version of these two dev phones, amazing work can be done
I've got a phone with the same exact issue. I can use adb commands to get to bootloader, but when trying fastboot oem unlock command I get FAILED error. Any ideas of what to try to get it unlocked and eventually rooted?
texas83 said:
I've got a phone with the same exact issue. I can use adb commands to get to bootloader, but when trying fastboot oem unlock command I get FAILED error. Any ideas of what to try to get it unlocked and eventually rooted?
Click to expand...
Click to collapse
That means it's got a locked bootloader, therefore the oem unlock is failing.
You may want to check out this thread, it might help you.
https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
Hi,
A couple of days ago I tried to root my xperia m4 because I want to remove those annoying paid apps you can't remove without rooting. But I genuinely tried EVERYTHING! But nothing would work. The first problem I ran into was unlocking my bootloader, wich I could not do. I followed a lot of different guides but none of them worked. Below are a few links of the guides I followed:
https://forum.xda-developers.com/m4-aqua/general/guide-rooting-xperia-m4-aqua-t3407215
https://forum.xda-developers.com/m4-aqua/general/guide-unlock-bootloader-twrp-touch-t3247939
https://www.youtube.com/watch?v=OEF7ZAAVW00
https://www.youtube.com/watch?v=xAnBziMMr8g
https://www.youtube.com/watch?v=yHAcze1T4sQ
I found a lot more "guides" but they were too sketchy if you ask me.
If someone is willing to help me, I would really appreciate it!
ian_99 said:
Hi,
A couple of days ago I tried to root my xperia m4 because I want to remove those annoying paid apps you can't remove without rooting. But I genuinely tried EVERYTHING! But nothing would work. The first problem I ran into was unlocking my bootloader, wich I could not do. I followed a lot of different guides but none of them worked. Below are a few links of the guides I followed:
https://forum.xda-developers.com/m4-aqua/general/guide-rooting-xperia-m4-aqua-t3407215
https://forum.xda-developers.com/m4-aqua/general/guide-unlock-bootloader-twrp-touch-t3247939
https://www.youtube.com/watch?v=OEF7ZAAVW00
https://www.youtube.com/watch?v=xAnBziMMr8g
https://www.youtube.com/watch?v=yHAcze1T4sQ
I found a lot more "guides" but they were too sketchy if you ask me.
If someone is willing to help me, I would really appreciate it!
Click to expand...
Click to collapse
Go to the dialer and type in *#*#7378423#*#* until it pops ups the Service Info,then press Configuration and check for Rooting Status: Bootloader Unlocked,it should say Yes,if it says No then this is the reason any of the bootloader unlocking methods did not work and unfortunately you cannot unlock the bootloader.
And what error does it exactly say when you try unlocking? Make sure you have OEM unlocking and USB debugging on in the Developer Options.
Dinkec27 said:
Go to the dialer and type in *#*#7378423#*#* until it pops ups the Service Info,then press Configuration and check for Rooting Status: Bootloader Unlocked,it should say Yes,if it says No then this is the reason any of the bootloader unlocking methods did not work and unfortunately you cannot unlock the bootloader.
And what error does it exactly say when you try unlocking? Make sure you have OEM unlocking and USB debugging on in the Developer Options.
Click to expand...
Click to collapse
It says my bootloader is not unlocked crying, to be sure I made a screenshot of the service menu.
{
"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"
}
I guess there's no way to unlock it, otherwise it would have worked I guess.
Theoretically you can use dirty cow exploit (stock kernel must be affected) to get temp root, after that you can get permanent root.
Regards, Pavel.
Cubbins said:
Theoretically you can use dirty cow exploit (stock kernel must be affected) to get temp root, after that you can get permanent root.
Regards, Pavel.
Click to expand...
Click to collapse
"Dirty cow exploit"? Never heard of that before, quite a funny name for an exploit if you ask me. I'll ask my good friend Google if he knows anything about this exploit. Thanks for letting me know!
And how exactly could I get a permanent root when I have a temp root? Can't find any information about it.
ian_99 said:
"Dirty cow exploit"? Never heard of that before, quite a funny name for an exploit if you ask me. I'll ask my good friend Google if he knows anything about this exploit. Thanks for letting me know!
And how exactly could I get a permanent root when I have a temp root? Can't find any information about it.
Click to expand...
Click to collapse
Once you unlock your bootloader ---to get everything you'll need for root CLICK HERE
Hi7m3up said:
Once you unlock your bootloader ---to get everything you'll need for root CLICK HERE
Click to expand...
Click to collapse
He can't unlock his bootloader
For a guide to unlock your bootloader using flashtool CLICK HERE.
Do that before attempting to root your phone as you wont be able to root as this is the first step and is compulsory
Hi7m3up said:
For a guide to unlock your bootloader using flashtool CLICK HERE.
Do that before attempting to root your phone as you wont be able to root as this is the first step and is compulsory
Click to expand...
Click to collapse
it's impossible to unlock the bootloader on his device
Cubbins said:
it's impossible to unlock the bootloader on his device
Click to expand...
Click to collapse
Yeah just looked at screenshot ,didn't look before "my bad"
Quick question in command prompt could he still flash a modified supersu boot.img for m4 with the locked bootloader (i've not had a device with unlock-able bootloader) is that possible ?
Hi7m3up said:
Yeah just looked at screenshot ,didn't look before "my bad"
Quick question could he still flash a modified supersu boot.img for m4 (i've not had a device with unlock-able bootloader) is that possible ?
Click to expand...
Click to collapse
Unfortunately it's not possible. It's only possible to use some exploits
Cubbins said:
Unfortunately it's not possible. It's only possible to use some exploits
Click to expand...
Click to collapse
That's a problem i've not came across before so no experience to help out.
Good luck.
Cubbins said:
Unfortunately it's not possible. It's only possible to use some exploits
Click to expand...
Click to collapse
Since I'm not really experienced with this stuff, using an advanced exploit like the dirty cow exploit is probably not going to happen. But I am going to buy a new smartphone in the near future, this time I will buy one that can be rooted.
Thanks everyone for your help!
anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Ehacksa said:
anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Click to expand...
Click to collapse
No we realy want root for this phone
Ditto for root on lg tribute dynasty
Mag xx said:
No we realy want root for this phone
Click to expand...
Click to collapse
Ditto for root on lg tribute dynasty, would like to have it. Just putting it out there as a request, thanks.
if we get a custom recovery first get root will be easier
Are there any updates on this?
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
jasonmerc said:
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
Click to expand...
Click to collapse
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Kevin4762 said:
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Click to expand...
Click to collapse
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be
And as far as your other question, yes it is possible to use twrp for a similar phone. However it doesn't look like there is a similar phone with a similar chipset like this that has twrp already but I could be wrong. Note that cross compatibility like this is only for custom firmware like twrp, stock firmware IS NOT CROSS COMPATIBLE.
jasonmerc said:
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be.
Click to expand...
Click to collapse
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
{
"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"
}
Kevin4762 said:
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
Click to expand...
Click to collapse
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
jasonmerc said:
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
Click to expand...
Click to collapse
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Kevin4762 said:
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Click to expand...
Click to collapse
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
jasonmerc said:
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
Click to expand...
Click to collapse
First off, I appreciate you taking the time to help me out. I found what you're talking about, but it's specific to only a few devices and LG SP200 isn't one of the models listed. Also, in order to get the device ID, you first need to enter fastboot mode, which I can't get to work.
[email protected] every cool phone i get i cant root ... :/
Alldayismokebomb said:
[email protected] every cool phone i get i cant root ... :/
Click to expand...
Click to collapse
I think they skipped over the "Unlock OEM" in the developer settings. The device is a mcv150 close to the cv1. Search up LG Aristo 2 TWRP and see if the TWRP flashes to your device. If it works then I can fix the device specific bugs.
It appears that no one has replied to this thread in almost 3 years (as of this post). To resurrect this thread, I have quite a couple of things about this device to say:
I don't think accessing the bootloader is possible for whatever reason. I've tried rebooting into the bootloader (with "Enable OEM Unlock" enabled) through adb reboot bootloader but to no avail.
Root is possible.The Tribute Dynasty (SP200) contains a MediaTek MT6750 SoC. Combined with the last security patch being November 1, 2019 (an interesting coincidence), this makes this device vulnerable to the mtk-su temporary root exploit.
I remember following a guide somewhere else on XDA, but I can't recall which guide (nor can I find it right now). I remember using mtk-easy-su for this purpose, but then that's all I can remember.
There might be some other developments with this phone that I might know about, but all of this I find from experience.
{
"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"
}
Bootloader is already unlocked via IV's unlock code page. But the device is not allowing init_boot partition. Unlike older models, I've heard native Android 13 devices should root these partitions(init_boot_a, b). Are there alternative way to root, or open Qualcomm diag ports to VoLTE patch?
Solved: we should boot into fastbootd mode to flash the init_boot.
I bought the Chinese mainland version of Xperia 1 V, flashed the Hong Kong version ROM and unlocked the Bootloader, but after rebooting I found that I could not set the Pin password, it would repeat this step infinitely, I don’t know if your phone has this situation.
MattBoBo said:
我买了中国大陆版的Xperia 1 V，刷了港版ROM，解锁了Bootloader，重启后发现无法设置Pin密码，会无限重复这一步，不知道你的是不是手机有这种情况。
Click to expand...
Click to collapse
me too
HK Market version & unlocked BL by code generated by 1iv on sony developer
Everytjing's fine except the TEE. I dumped TA file by newflasher but no way to restore it.
it seems there is no way to fix the issue of a broken keyguard when bootloader is unlocked. It remains broken on a custom gsi as well. It returns to a working state once the bootloader is relocked.
uuidd said:
HK Market version & unlocked BL by code generated by 1iv on sony developer
Everytjing's fine except the TEE. I dumped TA file by newflasher but no way to restore it.
View attachment 5925909View attachment 5925911View attachment 5925913
Click to expand...
Click to collapse
have you been able to figure out a way to allow the keyguard to have a pin, passcode, or pattern set after bootloader unlock? I was able to log it, so we see what i happening, keystore breaks, but I had to relock due to this issue. Also, I have XQ-DQ-72 and running the HK firmware on Tmobile in the US. How in the world did you get 5G to work? I cannot get it.
Hurt Copain said:
have you been able to figure out a way to allow the keyguard to have a pin, passcode, or pattern set after bootloader unlock? I was able to log it, so we see what i happening, keystore breaks, but I had to relock due to this issue. Also, I have XQ-DQ-72 and running the HK firmware on Tmobile in the US. How in the world did you get 5G to work? I cannot get it.
Click to expand...
Click to collapse
You are right, the keystore refuses to distribute any key. But my pin and other safe tools are still working well after unlocking the bootloader. Have you added any pin before unlocking the bootloader? I guess the keymaster still have your old pin stored which causes a mismatch to refuse accepting a new one?
The 5G works in default settings without touching any thing. I dont quite know the band things across different contries.
uuidd said:
You are right, the keystore refuses to distribute any key. But my pin and other safe tools are still working well after unlocking the bootloader. Have you added any pin before unlocking the bootloader? I guess the keymaster still have your old pin stored which causes a mismatch to refuse accepting a new one?
The 5G works in default settings without touching any thing. I dont quite know the band things across different contries.
Click to expand...
Click to collapse
ok I think I had a pin added before. Although, I may have tried it without as well. Did you unlock your bootloader on HK firmware or another? I didn't unlock till the ota update that came first boot. I am thinking I need to lock, then unlock on another firmware. I will try what you suggested. thank you!
uuidd said:
You are right, the keystore refuses to distribute any key. But my pin and other safe tools are still working well after unlocking the bootloader. Have you added any pin before unlocking the bootloader? I guess the keymaster still have your old pin stored which causes a mismatch to refuse accepting a new one?
The 5G works in default settings without touching any thing. I dont quite know the band things across different contries.
Click to expand...
Click to collapse
So, is it able to unlock the decive, flash kernelSu kernel, then lock the device and make the TEE works?
MCredbear said:
So, is it able to unlock the decive, flash kernelSu kernel, then lock the device and make the TEE works?
Click to expand...
Click to collapse
You cannot lock a bootloader with a rooted or otherwise modified kernel.
Hurt Copain said:
You cannot lock a bootloader with a rooted or otherwise modified kernel.
Click to expand...
Click to collapse
Sad ... Except Pin, is there any thing else effected by the not working TEE?
You cannot use any type of security including fingerprint, pin, passcode/password. This is something Sony will fix. Some claim if you unlock without having a previously setup security method, it would work. It doesn't. I believe I was firmware related and depending on that point what happens after unlocking.
Hurt Copain said:
You cannot use any type of security including fingerprint, pin, passcode/password. This is something Sony will fix. Some claim if you unlock without having a previously setup security method, it would work. It doesn't. I believe I was firmware related and depending on that point what happens after unlocking.
Click to expand...
Click to collapse
Ok that's fine, I don't need any security. But what meanings Sony will fix? Will Sony updates a firmware that makes TEE works after unlocked?
Sony will likely fix the issue as described above.
uuidd said:
HK Market version & unlocked BL by code generated by 1iv on sony developer
Everytjing's fine except the TEE. I dumped TA file by newflasher but no way to restore it.
View attachment 5925909View attachment 5925911View attachment 5925913
Click to expand...
Click to collapse
How did you get KernelSu works? I tried all the 5.15.74 kernels from Github CI but failed to boot.
MCredbear said:
How did you get KernelSu works? I tried all the 5.15.74 kernels from Github CI but failed to boot.
Click to expand...
Click to collapse
Sorry, I know how to do this now.
Hurt Copain said:
Sony will likely fix the issue as described above.
Click to expand...
Click to collapse
Good to see u hurt i followed ur roms on pixel 6 series, Planning to development on this device?
Vman006 said:
Good to see u hurt i followed ur roms on pixel 6 series, Planning to development on this device?
Click to expand...
Click to collapse
Yes, happy to be here. Best phone purchase for sure. Just wating for sony to figure out this keystore bug. So, I can stay unlocked and build something... Gsi's have the same issue after flashing as well as on stock..
uuidd said:
You are right, the keystore refuses to distribute any key. But my pin and other safe tools are still working well after unlocking the bootloader. Have you added any pin before unlocking the bootloader? I guess the keymaster still have your old pin stored which causes a mismatch to refuse accepting a new one?
The 5G works in default settings without touching any thing. I dont quite know the band things across different contries.
Click to expand...
Click to collapse
Did you unlock on Chinese firmware or hong kong? Not setting a pin and unlocking yields the same results..