Related
Hey Guys,
I have a wild idea and wanted to share the idea.
I was looking through quite a lot of bootloaders and I think we can use the wildfire bootloader and flash it on to our device. The thing is we might be able to intercept SEUS update and swap the wildfire bootloader into our device. I know what you are thinking how could the wildfire bootloader be any good to us? Well the thing it is compiled in ARMv6 as well as there still is the chance the configuration for the bootloader is stored onto flash. most bootloaders on ARM devices are configured via an JTAG board and create a configuration within the flash above bootloader code. usually this is exactly the same jump on all arm bootloaders. Developers later pull the first 1 MB or 2 MB of the nand and make this the bootloader image. which include configuration as well as the bootloader itself.
The trick would be to only flash bootloader from wildfire and leave configuration alone hoping it does the same jump to configuration as the seus does (which in fact is most likely)
So once the wildfire bootloader is ported and SE configuration is in there I think we should be able to flash it. The only thing that still could prevent is that bootloader is also checking if the new bootloader is signed by SE.
What do you guys think of this approach?
Im not a pro on Modding but i think it may work.
flashing only the boot loader will be a dificult thing.
and you may want to try to crack a sign... (yes it seems strange)
but think with me if you could make a clone of the SE sertificates and put it on the wild fire boot loader
you have a crackerd boot loader
BTW
Good luck.
slade87 said:
Hey Guys,
I have a wild idea and wanted to share the idea.
I was looking through quite a lot of bootloaders and I think we can use the wildfire bootloader and flash it on to our device. The thing is we might be able to intercept SEUS update and swap the wildfire bootloader into our device. I know what you are thinking how could the wildfire bootloader be any good to us? Well the thing it is compiled in ARMv6 as well as there still is the chance the configuration for the bootloader is stored onto flash. most bootloaders on ARM devices are configured via an JTAG board and create a configuration within the flash above bootloader code. usually this is exactly the same jump on all arm bootloaders. Developers later pull the first 1 MB or 2 MB of the nand and make this the bootloader image. which include configuration as well as the bootloader itself.
The trick would be to only flash bootloader from wildfire and leave configuration alone hoping it does the same jump to configuration as the seus does (which in fact is most likely)
So once the wildfire bootloader is ported and SE configuration is in there I think we should be able to flash it. The only thing that still could prevent is that bootloader is also checking if the new bootloader is signed by SE.
What do you guys think of this approach?
Click to expand...
Click to collapse
i don't think wildfire got a s1 bootloader right?
can't, I read in the x10 thread that this method will not work because the SE bootloader has its own security code(that's what they want to crack). Basically if you swap the wildfire bootloader, the phone won't boot up because it will reject the code.
Geohot has bought an x10 a few days ago to crack the bootloader (I think)... so maybe it can provide useful information if he manages it.
wow... great... idea!
Let's do that!
Let's flash booloader from MSM7225 chipset without SAKE enabled, to MSM7227 chipset with SAKE enabled chipset. Lets burn our chipsets ... Who is with me? Come on guys!
Chumby_666 said:
Let's do that!
Let's flash booloader from MSM7225 chipset without SAKE enabled, to MSM7227 chipset with SAKE enabled chipset. Lets burn our chipsets ... Who is with me? Come on guys!
Click to expand...
Click to collapse
sorry but will tht really burn the chipset???
newtron_b1 said:
sorry but will tht really burn the chipset???
Click to expand...
Click to collapse
well as the title said different approach.. that would be his approach haha ... lol it wont burn your chipset.
Biodegradable said:
well as the title said different approach.. that would be his approach haha ... lol it wont burn your chipset.
Click to expand...
Click to collapse
huff.. thanx.. i saw read smwhr abt boosting the CPU to 1.9GHz i know that device might be having cracked bootloader! but is that possible!! and really want some speed to this device! atleast 200Mhz more..!
Chumby_666 said:
Let's do that!
Let's flash booloader from MSM7225 chipset without SAKE enabled, to MSM7227 chipset with SAKE enabled chipset. Lets burn our chipsets ... Who is with me? Come on guys!
Click to expand...
Click to collapse
damn i didnt check that you are actually right. I thought both were the same chipset
//Delete if irrelevant
I somehow noticed that ZTE Blade has almost the same configuration with X10 mini pro...
Cpu: Qualcomm msm 7227 with ARM1136EJ-S cpu core on both devices
Adreno 200 graphics on both devices...
and many other similarities between them...
Info found on pdadb. net
Perhaps you could experiment with that...
//Delete if irrelevant
heh... isnt Geohot being sued by Sony?
morning_wood said:
heh... isnt Geohot being sued by Sony?
Click to expand...
Click to collapse
Yup, but he won't get sued because of hacking the phone. It's legal to mod your phone where he lived (United States) And beside with donations of his loyal fan, he had managed to put Sony at bay for now.
You sirs should take a look @ X10 forums, they already cracked Bootloader :O
D4rKn3sSyS said:
You sirs should take a look @ X10 forums, they already cracked Bootloader :O
Click to expand...
Click to collapse
and you sir!
should take a look date the date of the first post of this topic
when this topic was opend they didn't bypass the kernel
not even with bin4ry his files
owain94 said:
and you sir!
should take a look date the date of the first post of this topic
when this topic was opend they didn't bypass the kernel
not even with bin4ry his files
Click to expand...
Click to collapse
yah i know , just saying that they bypassed bootloader ! owain we all trust you !
Divr said:
can't, I read in the x10 thread that this method will not work because the SE bootloader has its own security code(that's what they want to crack). Basically if you swap the wildfire bootloader, the phone won't boot up because it will reject the code.
Click to expand...
Click to collapse
Someone has tried with data interrogation? Some CPU's check security codes a bit at a time. (RFID is notorious for this) You feed the possible code to them changing a bit at a time checking which clock cycle the CPU stops checking at thus which bit is wrong. Toggle the bit and repeat until you have the code.
(or we could read the entire thread before posting, sorry my bad)
I am sorry to resurrect this post, but I would really like to ask one small question. Has the bootloader been cracked?
It's been a while since I came here, and now I see true dual touch, and I wonder, has it been cracked?
From what I understand, we have custom ROMs, OC and undervolting possibility and now dual touch. Is there anything we can't do with this phone?
Thanks all for your help.
Johev said:
I am sorry to resurrect this post, but I would really like to ask one small question. Has the bootloader been cracked?
It's been a while since I came here, and now I see true dual touch, and I wonder, has it been cracked?
From what I understand, we have custom ROMs, OC and undervolting possibility and now dual touch. Is there anything we can't do with this phone?
Thanks all for your help.
Click to expand...
Click to collapse
The bootloader has not been cracked, but it has been bypassed. There is now a method to boot a 2nd kernel over the running one. But as far as I can tell, the devs are having trouble locating the root partition. (correct me if I am wrong)
+1 thank for the information. Well I still hope that someone is able to get the bootloader cracked, but at least this way some cool things came for the phone.
So they are getting root for locked bootloaders over in the Z3 forum. I imagine it would work for our phones, except that to do that someone with an already rooted device would need to provide the info they need
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
BladeRunner said:
So they are getting root for locked bootloaders over in the Z3 forum. I imagine it would work for our phones, except that to do that someone with an already rooted device would need to provide the info they need
http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598
Click to expand...
Click to collapse
You should probably study up a little before posting
thegrants82 said:
You shoot probably study up a little before posting
Click to expand...
Click to collapse
Do you a have a point or anything constructively to add?
BladeRunner said:
Do you a have a point or anything constructively to add?
Click to expand...
Click to collapse
No but obviously neither do you on bootloaders and rooting.
thegrants82 said:
No but obviously neither do you on bootloaders and rooting.
Click to expand...
Click to collapse
Do you understand what I mean by a catch-22?
BladeRunner said:
Do you understand what I mean by a catch-22?
Click to expand...
Click to collapse
I understand your post but you don't know what your talking about.
thegrants82 said:
I understand your post but you don't know what your talking about.
Click to expand...
Click to collapse
I would say that you don't understand my post. They have found a root exploit for the Z3 (or at least certain variants of it at this point) which is exactly what we z3v owners are looking for, however for the devs to make it work for our phones someone with an unlocked boot loader and root would have to supply them with the info they need. Quite obviously we don't have an unlocked boot loader to get root hence the catch-22
BladeRunner said:
I would say that you don't understand my post. They have found a root exploit for the Z3 (or at least certain variants of it at this point) which is exactly what we z3v owners are looking for, however for the devs to make it work for our phones someone with an unlocked boot loader and root would have to supply them with the info they need. Quite obviously we don't have an unlocked boot loader to get root hence the catch-22
Click to expand...
Click to collapse
Good luck.
thegrants82 said:
Good luck.
Click to expand...
Click to collapse
:what:
You know doesn't make sense for someone to give adb output when, if, they already have root.
1linuxfreak said:
You know doesn't make sense for someone to give adb output when, if, they already have root.
Click to expand...
Click to collapse
That's the problem here. He has no idea.
thegrants82 said:
That's the problem here. He has no idea.
Click to expand...
Click to collapse
apparently you haven't been following the thread. Those that are developing the root method need the adb output from someone that already has root. Some of the Z3 variants already had root by unlocking the bootloader.
1linuxfreak said:
You know doesn't make sense for someone to give adb output when, if, they already have root.
Click to expand...
Click to collapse
The root method they are working on is for locked bootloaders, they need the output from someone that previously achieved root by unlocking the bootloader. It is beneficial on Sony devices to have root without unlocking the bootloader so you can save your DRM keys/back up the TA partion. Also rooting without unlocking doesn't disable some on the camera functions.
BladeRunner said:
apparently you haven't been following the thread. Those that are developing the root method need the adb output from someone that already has root. Some of the Z3 variants already had root by unlocking the bootloader.
Click to expand...
Click to collapse
Lol I had two members msg me about how to add you to an ignore list. Didn't know about that so good luck to you and please stop posting about topics that you know nothing about. If you are wanting a high post count then just welcome new members. Judging by your posts I don't think its a secret that other members already know your deal. Later on!
thegrants82 said:
Lol I had two members msg me about how to add you to an ignore list. Didn't know about that so good luck to you and please stop posting about topics that you know nothing about. If you are wanting a high post count then just welcome new members. Judging by your posts I don't think its a secret that other members already know your deal. Later on!
Click to expand...
Click to collapse
It's pretty obvious that you are the one that just doesn't get it.
1linuxfreak said:
You know doesn't make sense for someone to give adb output when, if, they already have root.
Click to expand...
Click to collapse
not everyone would need to provide the adb output, just one person with the device. So, if by a miracle, one person had a z3v with an unlockable boot loader, rooted their phone and provided the adb output then they might be able to make the root tool work on the z3v's that have locked boot loaders, but since no one, afaik, has a z3v with an unlocked boot loader then we can't achieve root via the root tool. Thus the catch-22
BladeRunner said:
not everyone would need to provide the adb output, just one person with the device. So, if by a miracle, one person had a z3v with an unlockable boot loader, rooted their phone and provided the adb output then they might be able to make the root tool work on the z3v's that have locked boot loaders, but since no one, afaik, has a z3v with an unlocked boot loader then we can't achieve root via the root tool. Thus the catch-22
Click to expand...
Click to collapse
Yeah I got the reference, if I had root so would everyone else here cause I would share it with everyone and claim the three thousand dollar bounty offered.
1linuxfreak said:
Yeah I got the reference, if I had root so would everyone else here cause I would share it with everyone and claim the three thousand dollar bounty offered.
Click to expand...
Click to collapse
I suspect we won't have to worry about anyone collecting that bounty in the near future.
So I am npt that experienced when it comes to this stuff but im pretty sure verizon does NOT have an unlocked bootloader. I have the s4 and am looking into the z3v. I know people are still currently trying to break it. But the s4 can use towel root. Obviously its not that simple here since its not done yet. But seeing as this is still fairly new. They will have root sometime soon.
Sent from my SCH-I545 using XDA Free mobile app
If you had read the thread, there's no catch 22. The exploits they're leveraging were patched on the Z3v and TMo Z3 prior to release. It was stated multiple times.
Hello, there is a way to root this phone???
I want to unlock it.
Thanks
luisypica said:
Hello, there is a way to root this phone???
I want to unlock it.
Thanks
Click to expand...
Click to collapse
When you did your search on XDA, did you find your answer?
Ramer said:
When you did your search on XDA, did you find your answer?
Click to expand...
Click to collapse
NO, I didn´t find anything, that´s why I am asking for.
luisypica said:
NO, I didn´t find anything, that´s why I am asking for.
Click to expand...
Click to collapse
Hmm, it's posted ALL OVER XDA. The Sprint S8+ has a locked bootloader. As of now, we don't have root.
Ramer said:
Hmm, it's posted ALL OVER XDA. The Sprint S8+ has a locked bootloader. As of now, we don't have root.
Click to expand...
Click to collapse
Many phone with locked bootloaders has root. I know is hardest than unlocked bootloaders but is not impossible.
I hope will be as soon as possible.
Thanks
luisypica said:
Hello, there is a way to root this phone???
I want to unlock it.
Thanks
Click to expand...
Click to collapse
Here you go.
here it is,
https://www.oneclickroot.com/samsung/samsung-galaxy-s8/
lol
94tbird said:
here it is,
lol
Click to expand...
Click to collapse
I wonder if it's going to brick a Snapdragon S8 or will it just not work. That site doesn't even mention the two types of chipsets, at least not that I found on a quick reading.
94tbird said:
here it is,
https://www.oneclickroot.com/samsung/samsung-galaxy-s8/
Click to expand...
Click to collapse
This is a paid option and not for developer types like us. I am not convinced they support our USA model 955U anyway.
I would think Chainfire might come out with something like happened with S7 Edge. We shall see. Been 3 weeks.
photolarry said:
This is a paid option and not for developer types like us. I am not convinced they support our USA model 955U anyway.
I would think Chainfire might come out with something like happened with S7 Edge. We shall see. Been 3 weeks.
Click to expand...
Click to collapse
Think you missed the "lol" portion if my post
So I have been doing some research and the same kind of issue was occurring with the S7/Edge and there was a modified ODIN and "Engineering" boot.img (kernel) that claims to root the device. So I am curious if using that "modified hack" version of ODIN and a boot.img that has a kernel compatible with snapdragon (the only one I see in main s8+ forum is for Exynos). Not sure if this is really safe to do but I am guessing that once enough devs want root on this device, something will be out there. Has anyone tried KingRoot?
I have trieed Kingroot but always fail!!!
I hope Chainfire can do something for us.
Anyway: eng kernel exist for this device? Snapdragon version ofcourse.
I contacted the support team for oneclickroot and they said that they do not have a root for the US versions of the S8+.
Was wondering if there would be a way to modify and or port the s7 boot.img to an s8+ variant? Maybe even a way to "trick" it as to read it like an exynos vairant processor?
i just bougt sprint s8+ off swappa. any update to the rooting it cause im gonna unlock it.
photolarry said:
So I have been doing some research and the same kind of issue was occurring with the S7/Edge and there was a modified ODIN and "Engineering" boot.img (kernel) that claims to root the device. So I am curious if using that "modified hack" version of ODIN and a boot.img that has a kernel compatible with snapdragon (the only one I see in main s8+ forum is for Exynos). Not sure if this is really safe to do but I am guessing that once enough devs want root on this device, something will be out there. Has anyone tried KingRoot?
Click to expand...
Click to collapse
I've tried KingRoot, but it's hot garbage. Seeing so much in the way of information regarding the S8 Plus having a locked bootloader (Sprint ENG_US version or any other carrier variant for that matter), and I was wondering if there is any new information? Eager to root this bad boy, but no bueno thus far. I'm seeing the information for international ones using the Exynos, but I found this 'CF-Auto-Root-dream2qltesq-dream2qltesq-smg955u.tar' earlier this afternoon. Not even sure if this is compatible and I'm not going to be the guinea pig today. Has anybody else messed with this kit?
Anybody have any relevant information pertaining to effective rooting of the S8 Plus on Sprint by chance? Until I hear of some success with this, I'm not going to attempt. Got a bit of a qualm with a $1K paperweight. Please advise.
Thanks!
I love this phone but am just curious if anyone here is ready to develope for this phone once the bootloader unlock is available?
There's nothing to develop yet, at least on the North America side.
Devs are busy with stuff that is already present. Were they invested in the LG V20 or G6 before bootloader unlock? No. But AFTER LG bootloader unlock (or after Dirty Santa with the LG V20), development took off.
You're not going to get a list of names, if that's what you're looking for... There are people on the sideline, waiting. I bet they're examining files, kicking the tires. But they would look silly to "commit" before open market US998 is added to LG Developer Bootloader Unlock list. They would be pestered beyond belief -- as if they could do something about that bootloader unlock. (Yes, there are devs who specialize in that, like @jcase -- but others do kernel work or ROMs. They wait for the phone to be made available for development.)
Even AFTER bootloader unlock, real devs aren't going to announce stuff until it's ready, at least to be beta tested. All the empty promise threads of "I'm working on root for XXX" are usually not posted by experienced devs.
This is a fantastic spec phone, one of the two best phones of the year -- the other being Samsung Note 8. Better than any OnePlus crap and even better specs than Pixel 2 XL. It would be very strange if no devs didn't come work on this phone once it gets bootloader unlock with full fastboot flash commands.
Sent from my official carrier unlocked LG V30+ US998
Thanks Chazz. So there is not 1 Dev anxious to develope on this device when the bootloader unlock is released?
stu5797 said:
Thanks Chazz. So there is not 1 Dev anxious to develope on this device when the bootloader unlock is released?
Click to expand...
Click to collapse
As I said most experienced devs aren't going to make any public statement until they're ready to release work.
But you can look at V20 and G6 for list of devs who would be interested.
Sent from my official carrier unlocked LG V30+ US998
Im trying to work on LinageOS 14.1.... for the H930 atleast
But Im kinda stuck atm to get this **** to boot
Something with the audio configs is messed up xD
You may take a look and help to find the solution
USB also doesnt work, so i have to use a weird way to get them logs (ramdisk script that executes on boot and writes logs to /data/ramoops)
Might change to GZOSP 8.1 though... have a system.img extracted from the .kdz of the Oreo update of the Korean version, not sure yet lol
Yes they are..i develop a new stock kernel and try to optimize the Stock rom.
But it takes a long time.
OnePlus3 was realy easy.
LG is not realy nice with source code.
Does someone know why lg has a problem to fastboot boot boot.img ?
Stucks ob LG logo and i dont know why?
Cant i only boot signd kernel with fastboot?
But recovery can boot as well.
Why not a boot.img?
Any idea?
djsven said:
Yes they are..i develop a new stock kernel and try to optimize the Stock rom.
But it takes a long time.
OnePlus3 was realy easy.
LG is not realy nice with source code.
Does someone know why lg has a problem to fastboot boot boot.img ?
Stucks ob LG logo and i dont know why?
Cant i only boot signd kernel with fastboot?
But recovery can boot as well.
Why not a boot.img?
Any idea?
Click to expand...
Click to collapse
I had a similar problem (only booted in like 1 out of 20 cases) with a certain Magisk module... was stuck on V30 logo... IDK why though :/
reflashed then everything and checked step by step my modifications if it still works or not ?
djsven said:
Yes they are..i develop a new stock kernel and try to optimize the Stock rom.
But it takes a long time.
OnePlus3 was realy easy.
LG is not realy nice with source code.
Does someone know why lg has a problem to fastboot boot boot.img ?
Stucks ob LG logo and i dont know why?
Cant i only boot signd kernel with fastboot?
But recovery can boot as well.
Why not a boot.img?
Any idea?
Click to expand...
Click to collapse
LG uses aboot.img not boot.img for some weird reason.
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
djsven said:
Yes they are..i develop a new stock kernel and try to optimize the Stock rom.
But it takes a long time.
OnePlus3 was realy easy.
LG is not realy nice with source code.
Does someone know why lg has a problem to fastboot boot boot.img ?
Stucks ob LG logo and i dont know why?
Cant i only boot signd kernel with fastboot?
But recovery can boot as well.
Why not a boot.img?
Any idea?
Click to expand...
Click to collapse
My reply got crazy messed up somehow
LG uses aboot.img not the regular boot.img for some odd reason
So, what we need is ??
Rename from boot to aboot ??
Not realy or?
If you extract the kdz file you will see the same boot_6.img.
Same file as new created boot.img
So how we can test it wihtout flashing it?
Shouldnt aboot be the bootloader ?
Atleast that was the case on my Oneplus 2... So i recommend not to touch it.
And selfcompiled kernels work, didnt do any modifications though, just changed ramdisk (for lineage, USB doesnt work though... and audioserver crashes)
SGCMarkus said:
Shouldnt aboot be the bootloader ?
Atleast that was the case on my Oneplus 2... So i recommend not to touch it.
And selfcompiled kernels work, didnt do any modifications though, just changed ramdisk (for lineage, USB doesnt work though... and audioserver crashes)
Click to expand...
Click to collapse
Yes, you are right. Aboot.img is the bootloader. I remember now after going through it
@ SGCMarkus this is the problem.
If i mod the ramdisk, fastboot boot boot.img didnt work. stuck on logo.
Maymbe be have to flash it.
But iam on holidays. Not interesst to kill my device
I remeber this problem even on my LG G3.
I think the self compiled kernel will work.
Could someone try to do this fastboot command with orginal boot.img?
Does ist work?
djsven said:
@ SGCMarkus this is the problem.
If i mod the ramdisk, fastboot boot boot.img didnt work. stuck on logo.
Maymbe be have to flash it.
But iam on holidays. Not interesst to kill my device
I remeber this problem even on my LG G3.
I think the self compiled kernel will work.
Could someone try to do this fastboot command with orginal boot.img?
Does ist work?
Click to expand...
Click to collapse
Im currently not at home to try this, but i have a few boot images at home which i could try (e.g. fash my broken lineage build and check if i see a bootanimation if i boot just the image it provided via fastboot lol)
Magisk, dm-verity and so on all modify the ramdisk... so atleast the flash should work, but also TWRP has a different than normal ramdisk, so idk why it shouldnt work for others?
ChazzMatt said:
You're not going to get a list of names, if that's what you're looking for... There are people on the sideline, waiting. I bet they're examining files, kicking the tires. But they would look silly to "commit" before open market US998 is added to LG Developer Bootloader Unlock list. They would be pestered beyond belief -- as if they could do something about that bootloader unlock. (Yes, there are devs who specialize in that, like @jcase -- but others do kernel work or ROMs. They wait for the phone to be made available for development.)
8
Click to expand...
Click to collapse
I'm on team #NeverWorkingOnLGStuffPubliclyAgainEverPeriod
jcase said:
I'm on team #NeverWorkingOnLGStuffPubliclyAgainEverPeriod
Click to expand...
Click to collapse
I thank you for your work on the Droid Turbo the last couple of years. You stayed ahead of control freak Verizon for their locked down bootloader, when the other Quarks had easily unlocked bootloader via code from Motorola. Your efforts let a lot of people participate in the available Quark dev work.
I respect you and your work. If you don't want to make LG bootloader unlock/root public, that's your right to do so. Just as I supported your right to charge for Sunshine.
This V30 phone does have amazing specs. I wish someone of your caliber was working on it.
Sent from my official carrier unlocked LG V30+ US998
I take that as encouragement! If JCASE is working on this and in the v30 forums we are in damn great hands for our v30s. You have me excited buddy
ChazzMatt said:
I thank you for your work on the Droid Turbo the last couple of years. You stayed ahead of control freak Verizon for their locked down bootloader, when the other Quarks had easily unlocked bootloader via code from Motorola. Your efforts let a lot of people participate in the available Quark dev work.
I respect you and your work. If you don't want to make LG bootloader unlock/root public, that's your right to do so. Just as I supported your right to charge for Sunshine.
This V30 phone does have amazing specs. I wish someone of your caliber was working on it.
Click to expand...
Click to collapse
I know <3
Lots of reasons for not working on LG.
stu5797 said:
I take that as encouragement! If JCASE is working on this and in the v30 forums we are in damn great hands for our v30s. You have me excited buddy
Click to expand...
Click to collapse
Uhmmmm.... he may work on it in his own time, but he's said he's not going to share results publicly. He's not an admirer of LG. It's up for him to speak for himself, but I've heard in the past others in the LG forums acted badly. He doesn't NEED that kind of grief. Many other stuff he can be working on, where he'll be appreciated -- and that's probably why the carrier variants of the LG G6 (like Verizon) never saw published (public) bootloader unlock and root.
Sent from my official carrier unlocked LG V30+ US998
jcase said:
I'm on team #NeverWorkingOnLGStuffPubliclyAgainEverPeriod
Click to expand...
Click to collapse
We understand but there are some nice people in the world. You are talented people look to you for help. From what I heard part of it was you didn't get all the donations you were supposed to.... Donations are great but don't do it for that, gotta do it because you like to hack. Just saying, it's a challenge, nobody ever wants to take it on. I tried with the V10 until I broke it
abine45 said:
We understand but there are some nice people in the world. You are talented people look to you for help. From what I heard part of it was you didn't get all the donations you were supposed to.... Donations are great but don't do it for that, gotta do it because you like to hack. Just saying, it's a challenge, nobody ever wants to take it on. I tried with the V10 until I broke it
Click to expand...
Click to collapse
Nothing to do with donations, at all. It's because of the way the LG community has treated developers, how some of their fake "developers" steal and sell work of the real ones, and frankly because they won't leave me alone, PM me non stop when I make it clear I am not doing it and then lecture me about how I should do it for {reason}.
If the LG community wants it done so bad, there are plenty of resource to learn from, they can pick up and start working on it on their own.
As someone living in the USA and using T-Mobile as a provider, is there a significant difference between the XQ-CQ54 and XQ-CQ72 models? If so, which one should I go with?
I will not be using the XQ-CQ62 (US version) because the bootloader cannot be unlocked and I would like to use a custom ROM.
You can unlock the bootloader on 62 but it cost about 20 bucks..its a recent hack ... Xda isnt allowing guides with money involved so that's why theres none posted here.
Other then that i think 54 version aka european is way better then chinese 72. Just for esim alone
viper. said:
You can unlock the bootloader on 62 but it cost about 20 bucks..its a recent hack ... Xda isnt allowing guides with money involved so that's why theres none posted here.
Click to expand...
Click to collapse
Would you be able to provide a link to the service or at least a name for the website? I'd like to try that one but I'd also like to not download a virus.
I havent tried it but there are reports of it being a legit thing. I ll send you a pm so you can look into that thread.
Morcleon said:
Would you be able to provide a link to the service or at least a name for the website? I'd like to try that one but I'd also like to not download a virus.
Click to expand...
Click to collapse
would love to hear about your experience with the tool
I have the US version and found out the hard way that its bootloader can't be unlocked. I've always had a rooted phone, BUT I would say this phone has everything that I want and need. And Android 13 now has features that I used root phones to get. On the flip side, I have seen people that have the 1 iv US version and they've used the mentioned tool, and were able to change the no to a yes. As long as Sony keeps pumping out updates, I'm good for now on stock, but I may revisit the tool if updates stop.
jonchance_84 said:
I have the US version and found out the hard way that its bootloader can't be unlocked. I've always had a rooted phone, BUT I would say this phone has everything that I want and need. And Android 13 now has features that I used root phones to get. On the flip side, I have seen people that have the 1 iv US version and they've used the mentioned tool, and were able to change the no to a yes. As long as Sony keeps pumping out updates, I'm good for now on stock, but I may revisit the tool if updates stop.
Click to expand...
Click to collapse
Don't post nonsense. Bootloader unlock is possible.
Kevbodian said:
Don't post nonsense. Bootloader unlock is possible.
Click to expand...
Click to collapse
All that I was saying is that I may be open to trying the "workaround" to enable bootloader unlock on the US version later on. Please explain to me how that is nonsense. Or if you know of a way to change the no to a yes on these locked down versions, I'm all ears.
I have the US version and found out the hard way that its bootloader can't be unlocked
Click to expand...
Click to collapse
That's a pretty direct statement which is made up of nonsense.
No to yes and unlocking the bootloader is possible. See the thread about the so-54c or check my posts.
Kevbodian said:
That's a pretty direct statement which is made up of nonsense.
No to yes and unlocking the bootloader is possible. See the thread about the so-54c or check my posts.
Click to expand...
Click to collapse
That's all you needed to say. I was only verifying that I ran into the same situation. I'll check out your posts, and read up. I haven't had an Xperia in almost 10 years, so I'm getting caught up.