Starts at $100. BOUNTY requires successful flash of Global firmware.
Pretty sure there is no 5G 7t pro global phone?
A bounty for the T-Mobile MSM is more important. We need that before we start messing around with the global firmware files for the non-5G variants.
LLStarks said:
A bounty for the T-Mobile MSM is more important. We need that before we start messing around with the global firmware files for the non-5G variants.
Click to expand...
Click to collapse
Agree! Got to have a fallback msm to flash once we brick it lol
Has there been any oneplus devices in recent history that didn't have a msm download tool become available?
headcreepz said:
Has there been any oneplus devices in recent history that didn't have a msm download tool become available?
Click to expand...
Click to collapse
Yes, 7Pro 5G EU (only sold via EE in UK and Elisa in Finland), most likely because it wasn't sold a lot and that no one either required the tool or leaked it.
In for $100 USD. Without a way to restore the OnePlus 7T Pro McLaren 5G, I don't expect many developers to pick up the device. My $100 will be paid out to either a way to restore the STOCK T-Mobile firmware, OR a global image. As long as it is done via the MSM download tool.
Apparently, there are Windows tools to decrypt an .ops file, but I haven't seen any via brief Google search to encrypt/create; maybe there's something on XDA related to creation. T-Mobile and/or OnePlus should release a restore to stock T-Mobile MSM image on XDA for the OnePlus 7T Pro 5G McLaren. It seems like it could only benefit both companies to release it here. Not on their website because it's not for your average user, but on XDA only makes life easier for everyone.
ddggttff3 said:
In for $100 USD. Without a way to restore the OnePlus 7T Pro McLaren 5G, I don't expect many developers to pick up the device. My $100 will be paid out to either a way to restore the STOCK T-Mobile firmware, OR a global image. As long as it is done via the MSM download tool.
Click to expand...
Click to collapse
I know you've asked OnePlus already, but maybe you'd have more luck asking T-Mobile because OnePlus is probably seeing it as the ball is more in T-Mobile's court, so-to-speak?
T-Mobile would only have OTAs at best on their servers.
Does anyone have even the fastboot rom for this phone?
I have very bad news for you T-Mobile customers that have a OnePlus Device.. and yes I am one too..
OnePlus Rather youbuy direct from them, then from Carrier, OnePlus has Crippled the carrier edition of all their OnePlus Devices starting with the 7 Series.....
They have a MSMDownload Tool, that is now coded to each and every device it has.. meaning, if you have a T-mo edition, you will not be able to use the
msmdownload tool that has global edition, and you cant bypass that with a hex edit of the ops file anymore..
and you cant edit the msmdownload tool, because its VMP Protected, meaning unless you can unpack that VMP and restore all the imports
you will not be able to hex edit that..........
the newer MSMDownload tools check project code, which is located in a few places on your device.. but the place it checks against is
in eprom, No way to get around that.. and fastbootD which is the current way to convert. Will no longer be available to use anymore soon as well
,as OP has patched that too....... also, News is that Qualcomm is now implanting a new security method that will write protect your device.. and the only
way to bypass that is with a susyq cable and or taking apart your device and turning a switch. then flashing a developers edition OS.. So good luck with that too..
that prob wont be out for another 5 years total.... but soon all android devices will be Fully locked Down do to that.............................. This is already been implanted into chromebooks (newer)..
also, if you happen to get the ops file. well thats encrypted as well.. and because of the vmp protected msmdownload tool, the old public way to get your hands
on the loader from the ops file is no longer possible............
pretty much the only way to convert to global is by extracting OPS, then flashing partitions manually using loader......
But there is a catch there too, Oneplus is the only idiot to protect its FireHose Loader, you can read but you cant write with it.. So no matter if you had their loader extracted. you will still run into the next issue
of flashing each partition because it will fail.. Why will it fail, because OP write Protected it, you need a Demecia token and then you need another Project token... so in all you need
about 520 chars total of tokens.. good luck on that too................ Just to flash a partition to the device...........
some might ask how do I know all this, Lets just just say, I know people..............
But remember, OP has managed to encrypt everything to try and keep you carrier peepz from converting to global............
I personally think OnePlus is a jacka** company that will sell the global and carrier edition of their device for the same crazy price, but well know that the carrier editions are crippled
and nowhere near the global standard way........ Its unfair that OP took the time to lock us carrier peepz from converting.. just because they want us to buy direct and not from carrier.............
This 7 Pro that I have.. will most likely be the last OnePlus device I buy. and I know about 20 other people that refuse to buy another OnePlus device on the account they are locking people
out from a so called Developer friendly device.. OnePlus lies............................................ I have 200% Proof on everything I have said above.. if you need me to do a screen record to prove it further I will.
as for ways around said issues above, It can be done.. but the way it can be done is not public use.. and I have no permission or right to release said way............
I dont care how much money is offered, Its not in my place to release such info... But again, I dont even care about Oneplus devices anymore.. OP has shown their true colors now..
and again, Most likely will never buy another OnePlus Device again.........................
OnePlus, I know you read this, Hope you prove that you can be just as fair to carrier editions as you are with global editions.. cause I have a feeling all carrier editions will soon fail you..
because nobody is going to pay that kinda money for a crippled device that they cant convert.. you can pay nearly the same amount for the pixel 4 XL, and its not crippled in any way..
its pure vanilla Android OS....................... Guess you can figure out where I might go next........................... (waiting for Pixel 5) ...................
Please Dont message me with crazy questions and so on.. I will ignore all.. I barely use XDA.. someone posted this in my channel and I just wanted to check it out.................
only true way to reach me is on Telegram.. same nick as here...................
Good luck all...
That's a nice write-up but one question: How did the regular T-Mobile OnePlus 7T conversion work? Was that the v4 tool? Did the v5 tool stop this?
These measures are absolutely devastating to anyone who wants to test open betas and developer previews. What's the point of an unlocked bootloader for the McLaren 5G if you can do next to nothing with it and there's no rescue method.
With a Pixel, you just need to convince T-Mobile to sim unlock and then you're set for years.
For what it's worth, OnePlus got back to my support ticket and confirmed 2 things for me:
1. An unlocked bootloader OnePlus 7T Pro McLaren 5G will still get OTAs on an unlocked bootloader, but they come from OnePlus
2. If you unlock your bootloader and brick your device, I was informed they can do a "remote session" to restore the software. If that's the case, someone may want to take this approach with a keylogger so we can get the support ZIP.
I know there are at least few with bricked devices that should take advantage of this and be the hero.
ddggttff3 said:
For what it's worth, OnePlus got back to my support ticket and confirmed 2 things for me:
1. An unlocked bootloader OnePlus 7T Pro McLaren 5G will still get OTAs on an unlocked bootloader, but they come from OnePlus
2. If you unlock your bootloader and brick your device, I was informed they can do a "remote session" to restore the software. If that's the case, someone may want to take this approach with a keylogger so we can get the support ZIP.
Click to expand...
Click to collapse
How would we get ota updates straight from oneplus if we are still on T-Mobile firmware/software Would we have to download their software?
Anyone have the ota for the hd1925
Need to restore it bad update
Thanks I'm advance
ddggttff3 said:
For what it's worth, OnePlus got back to my support ticket and confirmed 2 things for me:
1. An unlocked bootloader OnePlus 7T Pro McLaren 5G will still get OTAs on an unlocked bootloader, but they come from OnePlus
2. If you unlock your bootloader and brick your device, I was informed they can do a "remote session" to restore the software. If that's the case, someone may want to take this approach with a keylogger so we can get the support ZIP.
Click to expand...
Click to collapse
Remote session hmm? Something tells me they'd have to put files on your computer right? I know it's not the most ethical thing in the world to suggest but what if you wait till said files get transferred over then maybe oh nooo my computer powered off whoops
ddggttff3 said:
For what it's worth, OnePlus got back to my support ticket and confirmed 2 things for me:
1. An unlocked bootloader OnePlus 7T Pro McLaren 5G will still get OTAs on an unlocked bootloader, but they come from OnePlus
2. If you unlock your bootloader and brick your device, I was informed they can do a "remote session" to restore the software. If that's the case, someone may want to take this approach with a keylogger so we can get the support ZIP.
Click to expand...
Click to collapse
I just attempted to get onto a chat and request a repair for my bricked device. The OnePlus guy told me they did not have a MSM tool for the TMobile version, unless they were lying. It was worth a shot.
thepotatoman1 said:
I just attempted to get onto a chat and request a repair for my bricked device. The OnePlus guy told me they did not have a MSM tool for the TMobile version, unless they were lying. It was worth a shot.
Click to expand...
Click to collapse
So if our T-Mobile variants get bricked we're SOL?
Related
What are the chances that this device will get TWRP and Root?
Not that I know... But this seems to be the best android tablet around now considering the price. Furthermore, its born with Android 8, which means it will be treple enabled thus the adaption of vanilla Android or others should be easier. Likewise, this should also improve security patches. I hope that someone will bring it.
Any progress of Rooting the HUAWEI MediaPad M5?
I want to buy it cuz my old Pixel C is sadly broken, but I wanna wait till it gots Root and Custom ROM:
@Marcopoloy13 I am in a similar situation as I would like to retire my old Nexus 7 (2012) and I am quite optimistic that TWRP will be available quite soon, as there is a device tree for the Honor 9 available and the Mediapad M5 sports the same SoC ...
As I am receiving my Huawei Mediapad M5 PRO next week, I wanted to look for root ... Is Huawei known to make a fuzz about root in case of sending it in for repairs etc. (I have a Samsung-past, friends of mine had issues with their support due to root ... ) ?
I am very new to Rooting, i just want to get linux deploy on this tab to install Debian. I have unlocked the bootloader the rooting is very hard.... i have no clue to what i am doing and was following the guide on this awesome forum but the imaging and so forth is not somthing i understand.
i have the CMR-w09 (non pro)
Unlock the bootloader?
How did you unlock the bootloader? I tried the “Huawei unlocking page" mentioned at Kingoapps website, but it didn't find anything about unlocking or bootloaders.
m5mediapad said:
I am very new to Rooting, i just want to get linux deploy on this tab to install Debian. I have unlocked the bootloader the rooting is very hard.... i have no clue to what i am doing and was following the guide on this awesome forum but the imaging and so forth is not somthing i understand.
i have the CMR-w09 (non pro)
Click to expand...
Click to collapse
jkaltes said:
How did you unlock the bootloader? I tried the “Huawei unlocking page" mentioned
Click to expand...
Click to collapse
For any WIFI only device, contact Huwaei via Phone (they rarely answer mails, so dont write one), explain the problem using their site (WIFI only device, therefore no IMEI etc), provide them your tablets serial number and let them send the unlock code via mail to you. Takes usually two business days until you have the unlock code.
I am new to rooting phone from what it seems this phone has not been successfully rooted. I would love to chat with someone who is working at this or has achieved this task.
Still waiting to find a way to bootloader unlock.
Any news about Firehose leak ?
I've been pretty busy working on patching LGUP for the sake of the Stylo 6 root and carrier unlocking, but, after that's done, I planned on moving on to the V60.
Patched LGUP should allow for quite a few things. It's a big assignment and is thus taking some time, but should get done, and will unlock a lot. Menu options (possibly including a mysterious "TOT Build" function I haven't looked into yet), OPID mismatch error voidance to flash over new carriers/unlock the carrier, the possibility of disabling the ARB check (obviously this poses concerns for accidental bricking i.e "possibility of") and some other more subtle changes. I might also redo the UI for fun...that's not a priority though. If anyone by chance wants to help with that so that I could get moving forward on the V60 much faster than is projected at the moment, then here's a link to my discord server where development is focused and a link to the thread that spawned it. I can't balance both projects at once, as I also have work and life happening around me.
I haven't looked everywhere for the V60 engineering boot or firehose or whatever just yet (I haven't familiarized myself with that much yet either) but I did poke around for a bit when I got curious and nothing turned up. I'll do more in depth stuff when the time comes, but for now I'm occupied.
Either way, I'll get around to taking a look at the V60 at some point. In the mean time, if I come across something that might help people out here, I'll go ahead and post it here, or make a new forum post depending on its relevancy.
Good luck, everyone!
haise.zero said:
I've been pretty busy working on patching LGUP for the sake of the Stylo 6 root and carrier unlocking, but, after that's done, I planned on moving on to the V60.
Patched LGUP should allow for quite a few things. It's a big assignment and is thus taking some time, but should get done, and will unlock a lot. Menu options (possibly including a mysterious "TOT Build" function I haven't looked into yet), OPID mismatch error voidance to flash over new carriers/unlock the carrier, the possibility of disabling the ARB check (obviously this poses concerns for accidental bricking i.e "possibility of") and some other more subtle changes. I might also redo the UI for fun...that's not a priority though. If anyone by chance wants to help with that so that I could get moving forward on the V60 much faster than is projected at the moment, then here's a link to my discord server where development is focused and a link to the thread that spawned it. I can't balance both projects at once, as I also have work and life happening around me.
I haven't looked everywhere for the V60 engineering boot or firehose or whatever just yet (I haven't familiarized myself with that much yet either) but I did poke around for a bit when I got curious and nothing turned up. I'll do more in depth stuff when the time comes, but for now I'm occupied.
Either way, I'll get around to taking a look at the V60 at some point. In the mean time, if I come across something that might help people out here, I'll go ahead and post it here, or make a new forum post depending on its relevancy.
Good luck, everyone!
Click to expand...
Click to collapse
Bricking will not be a risk if you have a firehose programmer
TheLoonyRebel said:
Still waiting to find a way to bootloader unlock.
Click to expand...
Click to collapse
I'm so confused, people keep saying that there is no root for a V60 and bootloader can't be unlocked. I'm looking at a bootloader option on my phone as I type here and here is a link to the rooting v60 article.
How to Root LG V60 ThinQ and Unlock Bootloader (Guide) (ytechb.com)
I guess I should try it to see if it works but statements like above are confusing to me.
Gaper1337 said:
I'm so confused, people keep saying that there is no root for a V60 and bootloader can't be unlocked. I'm looking at a bootloader option on my phone as I type here and here is a link to the rooting v60 article.
How to Root LG V60 ThinQ and Unlock Bootloader (Guide) (ytechb.com)
I guess I should try it to see if it works but statements like above are confusing to me.
Click to expand...
Click to collapse
That would work if you had a European version of the v60. Beside that, there are no custom roms/kernel/radio for the v60...
waiting for the prog_ufs_firehose_sm8250_lge.elf to show up and a modded abl_a.bin
Can't wait for this to be available for US. I have been really wanting this beast of a phone to use for pen testing etc
allb6ack said:
I am new to rooting phone from what it seems this phone has not been successfully rooted. I would love to chat with someone who is working at this or has achieved this task.
Click to expand...
Click to collapse
Hello
I have a LMV600EA with V600EA10o_00_1118 firmware. Today I managed to extract the boot.img and patch it with Magisk. I now have a working rooted LG V60. Attached is the Magisk patched boot file for the firmware V600EA10o_00_1118.
Regards,
Olavbson
allb6ack said:
I am new to rooting phone from what it seems this phone has not been successfully rooted. I would love to chat with someone who is working at this or has achieved this task.
Click to expand...
Click to collapse
olavbson said:
Hello
I have a LMV600EA with V600EA10o_00_1118 firmware. Today I managed to extract the boot.img and patch it with Magisk. I now have a working rooted LG V60. Attached is the Magisk patched boot file for the firmware V600EA10o_00_1118.
Regards,
Olavbson
Click to expand...
Click to collapse
The attach did not work, here is a link for downloading: https://drive.google.com/file/d/15K1DRQCnLg-5YQbOv0uQuipg1yypYWIJ/view?usp=sharing
olavbson said:
The attach did not work, here is a link for downloading: https://drive.google.com/file/d/15K1DRQCnLg-5YQbOv0uQuipg1yypYWIJ/view?usp=sharing
Click to expand...
Click to collapse
you have the link for the firehose for lg v60?
tmobile pushed an OTA and now my phone has android 11 and i hate it, i need to go back to android 10. i have .kdz 10p and LGUP 1.14 keeps crashing
olavbson said:
Hello
I have a LMV600EA with V600EA10o_00_1118 firmware. Today I managed to extract the boot.img and patch it with Magisk. I now have a working rooted LG V60. Attached is the Magisk patched boot file for the firmware V600EA10o_00_1118.
Regards,
Olavbson
Click to expand...
Click to collapse
Could you by chance upload a dump of your device partitions? Specifically, the boot img and perhaps your laf images? Everything in total would be really great, but I want to see if flashing the European bootloader over the USA variant is at all a good idea... perhaps we can shove the European bootloader into the USA variant and unlock that way?
Also, are you able to find your unlock.bin that LG sent you? Could you post that, too, for analysis?
I'm very curious.
V60 TMobile Feb 2021 Android 11 Magisk patched boot image:
magisk_patched_tmo_v60_a11.img | by AngryManMLS for Generic Device/Other
LG V60 T-Mobile February 2021 Android 11 Magisk patched boot image.
androidfilehost.com
Sadly no way to use given Magisk won't let me do anything right now beyond just patching the image that I pulled from the KDZ. Hopefully soon-ish we'll be able to root (and maybe bootloader unlock) this beast then really push the V60 to it's real potential.
TheLoonyRebel said:
V60 TMobile Feb 2021 Android 11 Magisk patched boot image:
magisk_patched_tmo_v60_a11.img | by AngryManMLS for Generic Device/Other
LG V60 T-Mobile February 2021 Android 11 Magisk patched boot image.
androidfilehost.com
Sadly no way to use given Magisk won't let me do anything right now beyond just patching the image that I pulled from the KDZ. Hopefully soon-ish we'll be able to root (and maybe bootloader unlock) this beast then really push the V60 to it's real potential.
Click to expand...
Click to collapse
so for now is only Boot.img patched and can it be used to root permissions the T-mobile variant and we must to wait for unlock bootloader?
JigsawMobile said:
so for now is only Boot.img patched and can it be used to root permissions the T-mobile variant and we must to wait for unlock bootloader?
Click to expand...
Click to collapse
Sadly we can't even get root permissions until we get the bootloader unlocked on the T-Mobile V60 unless if some other method is found.
TheLoonyRebel said:
V60 TMobile Feb 2021 Android 11 Magisk patched boot image:
magisk_patched_tmo_v60_a11.img | by AngryManMLS for Generic Device/Other
LG V60 T-Mobile February 2021 Android 11 Magisk patched boot image.
androidfilehost.com
Sadly no way to use given Magisk won't let me do anything right now beyond just patching the image that I pulled from the KDZ. Hopefully soon-ish we'll be able to root (and maybe bootloader unlock) this beast then really push the V60 to it's real potential.
Click to expand...
Click to collapse
I'm so sorry, I probably should have clarified, do you by chance have the unpatched version you could upload as well? I'd love to take a look at it and see what we can do with it, if anything, since LG likes to make their files very, very obscure and difficult to work with.
I can also, to an extent, dump some of the rootfs of the Stylo 6 but I'm yet to try it with the V60. My time here is limited until I can get the Stylo 6 done with, but assuming we finish everything we're working on, we'll have a patched LGUP 2.x dll (I can never remember the actual full version) with a patched LGUP 1.16 exe that should allow for crossflashing and dumping devices, and hopefully some other goodies among that and it should totally help jumpstart a lot of development for the V60 as well as most if not all other LG modern devices.
Hopefully!
haise.zero said:
I'm so sorry, I probably should have clarified, do you by chance have the unpatched version you could upload as well?
Click to expand...
Click to collapse
Ask and I shall provide....
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
I have a verizon v60 so not sure if i cam be much help since i know verizon isnt very root friendly but if i can do much to assist let me know
Hi, everyone! Big news for the LG community. Team and I have been working on something truly beautiful
Please see my post in the thread here.
It's coming soon! We're not completely ready yet, but we're so, so close.
From doing some searching it looks like other OnePlus phones can run the stock firmware on cell provided phones. Can I run the OnePlus version of Oxygen OS on my metro OnePlus Nord N10 or do I have to always wait on the slow carrier updates to be rolled out? This is my primary phone so I don't want to brick it by trying to do it. Was just wondering if anyone else had tried it and what their experience was?
avengerpro said:
From doing some searching it looks like other OnePlus phones can run the stock firmware on cell provided phones. Can I run the OnePlus version of Oxygen OS on my metro OnePlus Nord N10 or do I have to always wait on the slow carrier updates to be rolled out? This is my primary phone so I don't want to brick it by trying to do it. Was just wondering if anyone else had tried it and what their experience was?
Click to expand...
Click to collapse
I doubt it: Porting ROMs is not an easy process, it could mess with your hardware: Wi-Fi/BT/Camera/Data not working.
But I actually wanted to read some more opinions on this.
Now about bricking your phone: After you unlock the bootloader, you can always flash back the original ROM (I think it's available on the OP website). OP's default bootloader should do the trick but for extra precautions, you can always try flashing TWRP.
I've been seeing the MSMDownloadTool for flashing stock images to the phone with MetroPCS by T-Mobile and T-Mobile build numbers and people saying that the OnePlus is almost impossible to brick and not be able to fix it. I saw where someone said it can be flashed in the EDL mode and bypasses the greyed out Enable OEM Unlocking too.
Won't work. Modern OnePlus devices are locked by model number and device build.
Honestly, you won't even get the transfer started before it quits on you.
I been trying to root my Samsung Galaxy A52 5G but in order to do that i need to unlock the bootloader. So i follow the instructions and tells me to toggle the OEM option but i don't see it in my phone. Can someone please help.
Included screenshots
lolhelloeddie said:
I been trying to root my Samsung Galaxy A52 5G but in order to do that i need to unlock the bootloader. So i follow the instructions and tells me to toggle the OEM option but i don't see it in my phone. Can someone please help.
Included screenshots
Click to expand...
Click to collapse
assuming u have a usa model u cant unlock the bootloader
elliwigy said:
assuming u have a usa model u cant unlock the bootloader
Click to expand...
Click to collapse
Yes i bought it directly from Samsung
again, assuming you have a usa model (buying from samsung doesnt answer that question unless you say you bought a usa model from samsung meaning its a U1 model) then your bl cant be unlocked without paid service and you will not have oem unlock toggle at all
I said yes, can you recommend someone? Or where I can find them?
Arobase40 said:
Maybe you can try something like this ?
How to Fix Missing OEM Unlock in Samsung Devices
In this tutorial, we have shared four methods that will help you to fix the missing OEM Unlock option in various Samsung devices and tablets.
www.droidwin.com
Click to expand...
Click to collapse
most of those are for international devices that are unlockable where there is a 7 day wait period and doesnt apply to usa models at all.. usa models are NOT unlockable.. that site even thinks you can create a factory/combination firmware by using stock firmware which is also bs lol
just saying...
try
try
Arobase40 said:
Have you fully red the whole thread you're linking ???
I Participated myself to this long discussion in this thread and the conclusion is that : IT DOES NOT WORK for the Galaxy A52S 5G !!!
Most people are confusing between the A52 5G (SM-A526B) and the A52S 5G (SM-528B) !!!
The first one IS most probably rootable but not the second one !
Click to expand...
Click to collapse
I am verry sorry just try to help you i am out of this thread now
Arobase40 said:
At present time we are all on the same boat for the A52S 5G USA or International models as this phone is not really unlockable even when the system pretends it is unlocked !
My OEM toggle is ON and when I turn my phone on I got a message telling me exactly this :
"This Phone's bootloader is unlocked and the software integrity can't be verified. Any data on this phone may be vulnerable to attackers. Don't store any important or sensitive information on this phone.".
But whenever I try to flash a patched AP file with Magisk my phone goes into a bootloop !!!
I tried different methods including creating a "custom ROM" with modified AP and BL files and the result is just the same : bootloop !
For what I know there is something related with the Samsung Vault Keeper mechanism and I'm trying to find out a workaround for this, with no result ATM...
So the purpose of my previous link was to fix the missing OEM toggle button, nothing else... But I guess this option may also be not available anymore with this phone... At least you can try...
On my side, whether I unlock or re-lock the bootloader (in Download mode) the OEM toggle button is always on... ^^
So I guess the unique solution should be to create a petition address to Samsung to put the pressure on this dam*** company ! ^^
I used to love Samsung products but this company's policy is driving me nuts and it makes me more angry as time goes by...
Click to expand...
Click to collapse
I am not sure what that has anything to do with the OP or this thread. Your bootloader is clearly unlocked. Because you dont know how to root it doesnt mean your bootloader is locked as well as doesnt help the OP at all since his model is a usa model and cant unlock the BL like you can.
You will likely confuse people by trying to hijack the thread to solve your own issues that are unrelated to this thread. Just saying.
Arobase40 said:
Have you fully red the whole thread you're linking ???
I Participated myself to this long discussion in this thread and the conclusion is that : IT DOES NOT WORK for the Galaxy A52S 5G !!!
Most people are confusing between the A52 5G (SM-A526B) and the A52S 5G (SM-528B) !!!
The first one IS most probably rootable but not the second one !
Click to expand...
Click to collapse
both of those are unlockable and rootable but the op in this thread has a A526U or A526U1 so you both are in the wrong thread lol none of that will work on his device and sibce hes not unlocked and cant unlock in the first place he cant flash any custom firmware at all.
What is the KG or RMM state after you unlocked it? So to be clear, you unlocked the phone, booted into download mode, flashed the pached boot file, rebooted phone, it does not work?
So I'm coming to a conclusion that this phone is unlockable. Right? Right! Oh well thanks everyone for your help and support. Much appreciated.
Arobase40 said:
You're right on one point is that my post has nothing to do with OP but it was just a response to your own post... ^^
I'm here on XDA over 10 years and I always rooted my devices and I also saw different US Samsung devices being unlocked after a certain time...
So it's not a matter of hijacking the thread to solve my own issues but just a conversation to explain the situation of both A52 5G and A52S 5G whether from USA or International model...
Click to expand...
Click to collapse
a response to my own post saying the links provided likely only applied to international variants and NOT to the usa models and therefore are irrelevant doesnt mean its ok to confuse ppl and hijack a thread to try and solve your own problem lol..
It is hijacking because the international models and the usa models are very different when it comes to unlocking the bootloader.. USA models cannot unlock the BL whereas Intl' models can.. you can unlock your bl but dont know how to root it which is completely dif. than the ops issue who cant even unlock the BL.. the "situations" you are trying to explain are completely different.
Arobase40 said:
Well I'm not really wrong as I simply tried to solve the OP missing OEM Toggle !
Click to expand...
Click to collapse
you are wrong bcuz u are going based off all the intl models being same as usa models which they are not so any solutions you have based on intl models will not work as they dont apply to usa models.
Arobase40 said:
I don't understand why you are globally locked down with the US models and what you are saying is false and you know it as you are also the same moderator in the Galaxy Note 9 thread !
It took more time to unlock and to root the US Note 9 than the International one but at least it is now possible to unlock the US bootloader and to root the US Galaxy Note 9, including installing TWRP (since 2018) and some custom roms. You also proposed a way to root the US Note 9 without the need to unlock the bootloader and to touch the Knox flag. Partially useful but the problem is that you cannot do TWRP backup and restore when something is wrong... This was the same problem with my Galaxy Note 3 and with every firmware updates I had to redo the whole process from start to root it as there was no TWRP available at that time...
There may be also some other US Samsung devices in the same position such as Galaxy S10e (SM-G970U) but I don't own them and I don't have time to check all their situations...
I saw also TWRP for the US S21 Ultra and the US Galaxy Tab S7 Plus... based on your signature...
BTW, the OP issue is that he can't even try to unlock the bootloader simply because he can't see and can't access the OEM Toogle !
Click to expand...
Click to collapse
- USA Models have almost always been locked down. A few variants were unlockable for a bit like tmo or sprint but for the most part for years and years us models havent been unlockable without exploits and even then a majority of said exploits were just for root (bootloader was still locked and not able to use TWRP.)
- Not sure what you mean about Note 9 because I dont moderate in Samsung forums, I mostly am mod for Xiaomi. If you mean my root exploit for N9, that is using exploits and only for root, not for unlocking the BL.
- There was no way to unlock the bootloader of the US Note 9 in 2018. I posted the worlds first and only Note 9 root exploit which BL was still locked at that time and no option to unlock and use TWRP so I am not sure what you are referring to there.
- As I stated earlier I believe, devices released in 2019 to current (S9 to S21 and even some flip/fold devices) up to a certain update (each device is dif. but newer security isnt possible) via paid service which I also provide (and one other person) that relies on a device specific "token" that unlocks the bootloader. Even then, the oem toggle is never visible even after unlocking via paif service if it can even be unlocked (meaning its not updated to the point it cant unlock anymore.)
- My S21U did have an unlocked BL until I was robbed at gunppint and thethief broke my screen and upon getting it repaired theyhad to update it to latest firmware therefore losing my unlock. And the Tab S7+ that I have isnt a us carrier model (which are not unlockable without paid service) and is a SM-T970 (wifi only model) which is BL unlockable out of the box unlike us carrier models.
- Lastly, that is exactly what I am saying. He has a USA model that is not unlockable without paid service (if hes not updated to a firmware it no longer would work on.) The oem toggle will never appear. Theres no 7 day trick or anything he can do to get it unlocked. He'd have to find some sort of exploit that no one in the world has found yet or that they havent released (if someone did find some exploits.)
This is coming from someone who knows many devs around the world and as of last few years seems to be the only one still actively searching for exploits (and even found some root exploits and other things) and that only buys US models that are locked down tight and currently working with s21u a50 a32 5g s20u with no luck even at a root exploit. I was simply just trying to put it out there so ppl dont waste their time and stated the links and such ppl posted are irrelevant in this case as they dont apply to us models but hey, you can think I am wrong if you like and I hope op finds a miracle somehow to unlock his BL as itd help me unlock my other devices and others in the same boat but I'll take that with a grain of salt lol.
Hopefully this cleats things up for you.
Arobase40 said:
Nope you are still wrong because the International models don't have this issue about hidden OEM Toggle !!!
Click to expand...
Click to collapse
huh? I literally said the intl models are not the same as the usa models so any solutions for intl models will not work in this case which I cant tell if you agree or not as u indicate/acknowledge that they are not the same..
Arobase40 said:
Why are you talking as my "own problem" and why are you mocking me as if I was the sole person who is concerned with this issue ???
"My problem" is everyone's problem whether we own a US or an International model !!!
Click to expand...
Click to collapse
Because this isnt your thread and the ops issue is completely different than your issue and US or intl model DOES matter because you are unlocked.. US model cant even get that far.. your issue is with not knowing how to root after your bl is unlocked.. ops issue ishe has a US model and cant unlock the bootloader at all.. talking about your issue confuses people with US models into thinking they can unlock their bl but they cant so two different issues...
Arobase40 said:
First of all I have to say English is not my native language so I can say things that can be misunderstood, but since now I don't think this is the case...
I never said or meant that US and International Samsung phone are the same or could be treated the same way nor did I said that ALL US phones could be unlocked, but as you said yourself : "A few variants were unlockable for a bit like tmo or sprint but for the most part for years and years us models havent been unlockable without exploits and even then a majority of said exploits were just for root (bootloader was still locked and not able to use TWRP.)"... ^^
Then it's hard to know when you participate into a discussion as moderator or not as you always use the same pseudo with the same status "elliwigy : Forum moderator /Recognized Dev / Dev Relations"... ^^
But when we go in the Snapdragon dev section for the Galaxy Note 9 your name appears seven times in seven threads... Excluding the open thread where you explained how to root the Note 9 with an exploit.
Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels,
Samsung Galaxy Note 9 (Snapdragon) ROMs, Kernels, Recoveries, & Other Development
forum.xda-developers.com
About unlocking the bootloader of the US Note 9 in 2018 I was indeed confusing with the SD 9600 which is a Snapdragon but not for the US model... ^^
But if you go to this following thread OP, did say the US Note 9 could be unlocked with possibility to install TWRP and it was by May 6, 2020 even if the title mentioned N9600 !!!
[ROM] [Q] [N9600] Note 9 All Carriers [5FTK1] V8
This ROM is based on Samsung Note 9 TGY firmware and modded to allow full US carrier functions (volte, wifi-calling, etc.), but can be installed on any N9600 that meets the requirements below. Flash at your own risk! I am not responsible for any...
forum.xda-developers.com
Requirements:
Must be on Android 10 firmware. I recommend that you be on 5FTK1 bootloader
Must have klabit's official TWRP 3.4.0-0 installed
Instructions:
Make a full TWRP backup!!
Download ROM to phone from link below
Download ODM to phone from link below ONLY if you're on a USA carrier
Reboot to TWRP, select wipe and swipe to factory reset
Install ODM if you're on a USA carrier
Install ROM
Reboot
After setup, open rom control, open each tab in rom control and reboot SystemUI
*For SafetyNet to pass, you need to enable Magisk hide in Magisk manager settings
Downloads:
ROM Krog_N9600_NoteRom_5FTK1_V8.zip or Gdrive link
ODM Krog_N960U_USA_ODM_Q (For U.S. carriers only!!)
Magisk seems to work fine...
Then there is another and newer thread from afaneh92 (Nov 30, 2021) describing how to install TWRP on US Note 9 (using a paid service to unlock the bootloader is another subject and it doesn't matter)
[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 9 (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Finally, you admitted you owned a "My S21U did have an unlocked BL"... So what should we think about your own words ???
In regard with my own International A528B phone I did the unlocked process and tried many times to install a custom AP file with Magisk but it didn't work as my phone enter into a bootloop process after flashing it via PC Odin. At last resort I relocked my phone and I was surprised to receive an OTA update which should be impossible if my phone was really unlocked !!! ^^
How can you explain this ??? lol
Click to expand...
Click to collapse
- My "pseudo" as you call it is a tag/status. I was a "recognized developer" before I became a forum moderator and before jpining the dev commitee. It is tags that every forum moderator receives so ppl can see who the mods are. I am still a developer. The way it is broken down is each device has its own set of moderators which you can usually find a list in each section usually its stickied forwhichever moderators can moderate that section i.e. I can moderate xiaomi forums but since I am not a mod for Samsung I cant moderate in Samsung forums. Rule of thumb though, if you see I have created a thread in say Samsung forum then that is me posting something I have developed or am developing i.e. N9 root method and obviously posting as a developer. You would know if I was posting as a moderator as it'd be saying something in regards to moderation i.e. cleaning a thread for bad language or off topic banter of which I would have deleted/removed comments or some sort of action or if responding to a reported post etc. etc. So it would be clear if I was posting as a moderator as I would make it clear.
- The snapdragon dev section in N9 forum is for all snapdragon models of the note 9. The N9600 is the Korean variant if I am not mistaken and is unlockable by default. The OP in this thread has a USA variant, I did not say all "snapdragon" models were the same. ai simply stated "US/Carrier Models" were not unlockable without a paid service. Since N9600 is not a US/Carrier model it is unlockable and is in that section because it has a Snapdragon chip in it therefore falls in the category of an international model that is unlockable by default and therefore unrelated to the discussion here. The korean variants typically end with a 0. Models that are not unlockable are typically ending with U, U1, or W i.e. N960U, N960U1 or N960W. Anything else is likely not a US/Can model and are typically unlockable by default.
- Afaneh is the other person that can unlock bl's using a paid service which I already stated. USA models can use twrp once they get paid service (given they arent updated to a firmware not able to be unlocked) to unlock the bootloader first. This is the ONLY way to unlock the bootloader. He also makes twrp builds for devices and clearly (as you also included in your link) he is clear that you need to use a paid service. As for that other twrp post I have no idea. Because someone posts in a Snapdragon section and isn't specific on which variants it is for is not against any specific rules. I can bet however without even looking at it you can likely read the comments and see people with US models saying it didnt work or asking how to unlock the BL because it wasnt possible. Typically in those threads the dev will indicate you need to unlock the bootloader first and US variants cannot unlock the BL therefore that TWRP wouldnt apply to them at all.
- As far as your issue, the fact that you could successfully flash custom firmware using ODIN tells me you were unlocked. On locked devices (i.e. US variants) ODIN would fail and device will say an error so they wouldnt even be able to get that far. Samsung always likes to be different in how android and root and stuff work. Sometimes magisk needs to be modified or tweaked to work and sometimes the install instructions vary by device. I cant help you there because I sold my N9 before was able to unlock the bootloader but can guarantee you are able to root your device since bl is unlocked you just have to find the right instructions and follow them to the T. I do not know the steps for your intl model so I cannot say why its bootlooping but I assume you are missing a step somewhere.
As for relocking and getting an OTA, it is possible even if you were still unlocked. OTA will not work however if anything is modified i.e. if you are rooted the ota will fail. Simply having an unlocked BL you can still get an OTA if you havent modified anything i.e. no twrp and no root and no modified rom etc.
Arobase40 said:
First of all, when I posted a thread with a link on how to unhide the OEM toggle I said "Maybe you can try something like this ?" and nothing in the link mentions it was an International model !
And at present time nobody can certify my A528B phone is really unlocked as I was able to relocked it and I also received an OTA update which would be impossible if my phone was really unlocked !!!
That's why I said we are on the same boat... at present time... ^^
In regard with US bootloaders I gave demonstration it was possible to unlock some of them with different Samsung phones and I never said it was possible with all of them but sooner or later it is possible to unlock some of them whatever the process with or without paid services...
Ok, I'm now done with this discussion.
Click to expand...
Click to collapse
I said it was irrelevant because it will not work as usa models cannot unlock the BL. A lot of those sites will not list specific models and assume every model is the same andsometimes even use old pictures/instructions for super old devices and just create new pages. I bet most samsung sites like that all have same instructions word for word and only difference is the name of the device lol. I dont know why they do this but they obviously dont know what they are talking about,dont care or the page creation is somewhat automated but rule of thumb is us models cant unlock so you can assume those pages do not apply to us models.
Again, you can get an ota if unlocked and on complete stock firmware hence doesnt mean anything really. To add, just the fact alone you can toggle oem unlock and unlock your bootloader and were able to successfully flash a modified firmware in odin says you were unlocked as it would have failed in odin and not flashed anything. The fact that you bootlooped aftereards doesnt mean you werent unlocked, just means theres some steps you are missing or the files you used were no good. This also means you are NOT having the same issues. I dont know why its hard for you to understand that op cannot unlock his bl at all, doesnt even see the oem toggle (and never will) is the same as you who can see the oem toggle and can unlock bl and can flash modified firmware but bootloops afterwards as being the same issues.. OP can only hope his device isnt updated and can pay for paid service to unlock whereas you need to find proper instructions on rooting your device and to avoid a bootloop.. two completely separate issues.. You might have initially thought they were the same issue but that is why i clarified multiple times they are not the same issue at all and you even have a completely dif. variant than op does.. If you still think they are the same issue then i dont know what to tell you at that point and hopefully op realizes that he can only unlock with paid service and isnt confused as you are.
And yes, some us models were unlockable years ago.. In fact, I believe the S4 verizon models could unlock using an exploit on a certain firmware and verizon note 4 could unlock using an exploit turning it into a dev device but outside of that it has not been possible so if you are saying some could be unlocked going based off devices that came out years and years ago then sure. Recent years/devices though it has not been possible.
The paid service technically uses an exploit that creates a "token" that sets device to allow custom firmware to be flashed (essentially acts like an unlocked bootloader) but isnt unlocking the bootloader in a traditional sense at all so one could argue it isnt exactly the same (although result is the same.)
I just wanted to ask if there is any development effort going to bring TWRP and AOSP Custom ROMs to this device.
Under the hood, this device is very powerful. And well built. After using it for a few days, I feel like the just software experience is holding it back.
If there is, I'd like to join and help as much as I can.
Reserved
Tbh, the stock rom (global) is sufficient, and with root you can modify it however you like...
Custom development may start after Realme stops supporting the phone with OTA updates, which isn't anytime soon since GT 2 Pro is their flagship...
There is also Android 13 coming out...
And until there is an open-source bypass of MSM tool to recover bricks without paying $$, I think that not many people will waste time and money to build custom ROM and then maintain it to integrate Realme OTA's.
Quake94 said:
Tbh, the stock rom (global) is sufficient, and with root you can modify it however you like...
Custom development may start after Realme stops supporting the phone with OTA updates, which isn't anytime soon since GT 2 Pro is their flagship...
There is also Android 13 coming out...
And until there is an open-source bypass of MSM tool to recover bricks without paying $$, I think that not many people will waste time and money to build custom ROM and then maintain it to integrate Realme OTA's.
Click to expand...
Click to collapse
What about Xiaomi? They also have auth for EDL flash. But if you see the forum for xiaomi devices. It got lots of Custom ROM.
There's no need for a free MSM. To install any custom ROM you would have to unlock the bootloader first, and with an unlocked bootloader you can recovery every brick, unless you destroy the bootloader itself.
Rapper_skull said:
There's no need for a free MSM. To install any custom ROM you would have to unlock the bootloader first, and with an unlocked bootloader you can recovery every brick, unless you destroy the bootloader itself.
Click to expand...
Click to collapse
Yeah tell me about it.....I still feel violated for having a random stranger connect to my computer just to type a damn password, and paid for it....never had this issue with xiaomi, mi flash tool works great.....we need to pressure realme to stop this insanity.....there is no reason for having MSM locked.
dick_vigarista said:
Yeah tell me about it.....I still feel violated for having a random stranger connect to my computer just to type a damn password, and paid for it....never had this issue with xiaomi, mi flash tool works great.....we need to pressure realme to stop this insanity.....there is no reason for having MSM locked.
Click to expand...
Click to collapse
I also agree with this. And the unlock process itself is crappy. We need to install a dedicated app to be able to boot into fastboot mode! Why? Why not just allow bootloader to be unlocked like OnePlus devices, both phones are from the same parent.