Related
Hi, I need help. My girlfriend bought a Xiaomi Redmi Note 3 32GB / 3GB RAM Mediatek Helio X10 version.
I want to upgrade the firmware because it needs an upgrade. Since she bought it, February, it didn't updated one single time, and it has some bugs that upset her. So, here is the problem.
I already asked for permission from Xiaomi to unlock the bootloader, and already got it. When I tried to unlock, got the 50% problem (Current account is different from the account info on the device). Since then, tried to flash (from the Updater App) the developer ROM, also with no success (couldn't verify package).
The last option, I believe I have, is to manually flash (using MI FLASH software) the developer ROM and after that, unlock the bootloader to finally install the MIUI 8.0 (that's the goal of all this, with the unlocked bootloader).
So, how can I do this? Suggestions, tips, tutorials, guides or experiences, everything is welcome!
You have to go to latest Beta/developer Version and the Unlock should work...
Else just Update miui, because maybe the Bugs are fixed
MJDdeLacerda said:
Hi, I need help. My girlfriend bought a Xiaomi Redmi Note 3 32GB / 3GB RAM Mediatek Helio X10 version.
I want to upgrade the firmware because it needs an upgrade. Since she bought it, February, it didn't updated one single time, and it has some bugs that upset her. So, here is the problem.
I already asked for permission from Xiaomi to unlock the bootloader, and already got it. When I tried to unlock, got the 50% problem (Current account is different from the account info on the device). Since then, tried to flash (from the Updater App) the developer ROM, also with no success (couldn't verify package).
The last option, I believe I have, is to manually flash (using MI FLASH software) the developer ROM and after that, unlock the bootloader to finally install the MIUI 8.0 (that's the goal of all this, with the unlocked bootloader).
So, how can I do this? Suggestions, tips, tutorials, guides or experiences, everything is welcome!
Click to expand...
Click to collapse
To unlock the bootloader, you must have the MIUI developer installed on the device
4I-I said:
You have to go to latest Beta/developer Version and the Unlock should work...
Else just Update miui, because maybe the Bugs are fixed
Click to expand...
Click to collapse
Mattsantana said:
To unlock the bootloader, you must have the MIUI developer installed on the device
Click to expand...
Click to collapse
I already solved it by 'hard flashing" the miUI 8... because that's the version she wanted. Didn't try to flash the miUI 6 [developer] because I was lazy, but mainly because I didn't see any gains for her from doing it [unlocking the bootloader].
Thank you 2 for the replies!
Hi Guys,
I've been searching for 2 days now for a clear guide on how to unlock the bootloader for the Mediatek version and haven't found anything other than the official way. Can someone point me in the right direction please?
Thanks.
hatski said:
Hi Guys,
I've been searching for 2 days now for a clear guide on how to unlock the bootloader for the Mediatek version and haven't found anything other than the official way. Can someone point me in the right direction please?
Thanks.
Click to expand...
Click to collapse
Hi again,
Another plea for help, I'd really appreciate it. I can't even make a MI account so I'm totally stuck.
Thanks.
... sorry but I'm very confused ...
I'm reading the possible on the network, but the result is I always get confused more despite having a certain familiarity in modding having modded a galaxy nexus, and an LG G2 on which I installed TWRP recovery and various CyanogenMod ROMs.
Unlocking the bootloader in kate/SE, in an official or unofficial way, is still very difficult or almost impossible?
I often read of modified TWRP recovery, which sometimes give problems and sometimes it does not ...is it possible just put the official TWRP for kenzo?
If I can somehow install a TWRP, is possible to easily install the CyanogenMod ROM (after flashing ROM flashing kate modem is needed) and provide CM updates simply by flash new ROM via TWRP recovery?
Thks in adv
Nope! It's easy as 123... Please, check:
http://en.miui.com/thread-345728-1-1.html - for unlocked "emmc_appsboot.mbn".
You can also download ALKA TWRP, rename to "recovery.img", and replace it in fastboot ROM (image folder).
(As well as "emmc_appsboot.mbn emmc_appsboot.mbn", downloaded from the link above.)
ALKA TWRP: http://en.miui.com/thread-282773-1-1.html
rafaelbrunner said:
Nope! It's easy as 123... Please, check:
http://en.miui.com/thread-345728-1-1.html - ...
...
Click to expand...
Click to collapse
Thks for yr reply
I read official unlocking was successful for very very few owners and
such unofficial unlocking gave problems to many others, like bootloop etc...
is that wrong...?
Mrx65 said:
Thks for yr reply
I read official unlocking was successful for very very few owners and
such unofficial unlocking gave problems to many others, like bootloop etc...
is that wrong...?
Click to expand...
Click to collapse
I could not unlock my "kate" officially.
I've tried the method posted above, and works like a charm!
No bootloop, at all...
Thaknk yo so much for yr reply
I remain with the feeling of more complexity and less certainty, than the modding of the galaxy nexus and also the LG G2...
Official unlock works fine.
I have a Kate and unlocked it officially.
Just make sure to flash the global developer ROM, log into your MI account on the phone and press the "bind device to account" button inside the security settings menu before attempting to unlock.
I also got my Kate to unlock officially after using updater on phone to flash global beta rom.then in developer options clicked MI unlock status then linked phone to account. After that unlocked first try after many many failed attempts on global stable.
Nice news and info, thks so much!
But... why so many people can't officially unlock their kate having 50pc error...??
Which version of miui unlock tool and Global Dev. ROM you used when officially unlock yr kate?
I used global beta 6.11.24 and MIflash unlock_1.1.1111.1_en
Thks for reply and info
I recently got tired of using MIUI and since my phone is already out of warranty, I'm looking a totally legit way of unlocking my BL and flashing LOS 14.1. However, there are tons of guides with conflicting information, broken links, non updated methods which is expected of the excellent support for this device but leaves a new comer to this forum confused.
This is alluded to the fact that we have a strong community of developers who are always coming up with ingenious solutions and information which was relevant a month ago is soon deprecated.
Can someone give me a definitive guide to unlock my BL legally, flash TWRP and then flash LOS?
PS: I already got the unlock permission from Xiaomi. So there's that.
amangupta53 said:
I recently got tired of using MIUI and since my phone is already out of warranty, I'm looking a totally legit way of unlocking my BL and flashing LOS 14.1. However, there are tons of guides with conflicting information, broken links, non updated methods which is expected of the excellent support for this device but leaves a new comer to this forum confused.
This is alluded to the fact that we have a strong community of developers who are always coming up with ingenious solutions and information which was relevant a month ago is soon deprecated.
Can someone give me a definitive guide to unlock my BL legally, flash TWRP and then flash LOS?
PS: I already got the unlock permission from Xiaomi. So there's that.
Click to expand...
Click to collapse
If you already got the unlock permission from Xiaomi , why you just try unlocking using Miflash Unlock?
Try this tutorial from XDA:
1. Using Miflash Unlock (legal) http://bit.ly/2tkrvdo
2. [GUIDE][KENZO/KATE] Install LineageOS with locked bootloader http://bit.ly/2ndZhei
3. [GUIDE] [Unofficial BL Unlock] RN3 Pro & Pro SE [Flash the neccessary files only] http://bit.ly/2sPBYua
I am unlocking using Miflash Unlock, but if you got a problem maybe you can try third tutorial first.
iamstrong said:
If you already got the unlock permission from Xiaomi , why you just try unlocking using Miflash Unlock?
Try this tutorial from XDA:
1. Using Miflash Unlock (legal) http://bit.ly/2tkrvdo
2. [GUIDE][KENZO/KATE] Install LineageOS with locked bootloader http://bit.ly/2ndZhei
3. [GUIDE] [Unofficial BL Unlock] RN3 Pro & Pro SE [Flash the neccessary files only] http://bit.ly/2sPBYua
I am unlocking using Miflash Unlock, but if you got a problem maybe you can try third tutorial first.
Click to expand...
Click to collapse
I followed your advise and used the third tutorial for unofficial BL unlock as I couldn't get the Mi unlock working beyond 99% and got stuck with installing LOS 14.1 (latest build) with error 7.
Turns out, this is an expected error if the BL is not unlocked officially.
I created this thread so that I could avoid this exact issue. All so called guides and sticky posts are outdated and need to be updated
amangupta53 said:
I followed your advise and used the third tutorial for unofficial BL unlock as I couldn't get the Mi unlock working beyond 99% and got stuck with installing LOS 14.1 (latest build) with error 7.
Turns out, this is an expected error if the BL is not unlocked officially.
I created this thread so that I could avoid this exact issue. All so called guides and sticky posts are outdated and need to be updated
Click to expand...
Click to collapse
Fourth tutorial : https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778
Oohh.. sadly
So third tutorial is working for you? Because I never try that tutorial, that is new thread from XDA
I can't do anything, I just gave you link. I'm sorry...
Firts time I unlocking my phone using MiFlash Unlock and worked 100%. You can search tutorial how to solve unlocking process stuck 99%.
Or try another ROM not only LOS
I'm using Nitrogen OS right now...
In XDA-Developers every code builders finding solutions for Mate 9 but there is nothing for Mate 9 Pro (LON) versions.
I am opening this thread if someone give a hand to resolve downgrading problem Oreo Beta to Offical Nougat.
In Mate 9 forum @mankindtw build HWOTA 8 solution for MHA versions. Probably people will suggest me to use FunkyHuawei thing. But PayPal and BitCoin payment methods are not working in my country because of acredition at banking system.
So if any developer can support M9 Pro, it's too much appriciated for me.
livevalue said:
In XDA-Developers every code builders finding solutions for Mate 9 but there is nothing for Mate 9 Pro (LON) versions.
I am opening this thread if someone give a hand to resolve downgrading problem Oreo Beta to Offical Nougat.
In Mate 9 forum @mankindtw build HWOTA 8 solution for MHA versions. Probably people will suggest me to use FunkyHuawei thing. But PayPal and BitCoin payment methods are not working in my country because of acredition at banking system.
So if any developer can support M9 Pro, it's too much appriciated for me.
Click to expand...
Click to collapse
It's possible while you are in stock recover via Firmware Finder. Just you need to find which stock ROM works for your device. None of Rollback Roms worked with me.
Yep! I'm also waiting for this! Hope a solution comes soon
polaco95 said:
Yep! I'm also waiting for this! Hope a solution comes soon
Click to expand...
Click to collapse
Probably @mankindtw preparing a solution. He made the old HWOTA system and nowadays keeps silence. It's my guess, waiting for the official ROM release date.
@duraaraa I have a spesific problem. I'm using Huawei Mate 9 Pro. Bootloader unlocked, Oeminfo file belongs to orginal LON-AL00C00B225 but system running under Oreo 8.0.0.323 C636 log. It is sometimes running and sometimes don't.
I tried to downgrade Oreo to Nougat but it wasn't possible by Firmware Finder (special thanks to @gmanrainy for kind interest) or @mankindtw 's solutions. Probably file structure is different on Oreo, that could be reason for not downgrading.
Anyway, I know you are also moderating FunkyHuawei webpage. Is it possible for my situation to rebrand C636 and install LON-L29C636B235 version? Your payment methods not working in my country so I'l figure it out somehow. But I clearly wanted to learn if it is really work for me.
livevalue said:
@duraaraa I have a spesific problem. I'm using Huawei Mate 9 Pro. Bootloader unlocked, Oeminfo file belongs to orginal LON-AL00C00B225 but system running under Oreo 8.0.0.323 C636 log. It is sometimes running and sometimes don't.
I tried to downgrade Oreo to Nougat but it wasn't possible by Firmware Finder (special thanks to @gmanrainy for kind interest) or @mankindtw 's solutions. Probably file structure is different on Oreo, that could be reason for not downgrading.
Anyway, I know you are also moderating FunkyHuawei webpage. Is it possible for my situation to rebrand C636 and install LON-L29C636B235 version? Your payment methods not working in my country so I'l figure it out somehow. But I clearly wanted to learn if it is really work for me.
Click to expand...
Click to collapse
Yes, it's possible. But I would need to look into which package you need to install. You'd probably need to use FHRebrandTool to fix the branding correctly.
duraaraa said:
Yes, it's possible. But I would need to look into which package you need to install. You'd probably need to use FHRebrandTool to fix the branding correctly.
Click to expand...
Click to collapse
It's not problem to use it. I already downloaded tools but looking forward for your answer. Thank you.
I successfully rebranded my phone to LON-L29C636 via your stock OEMINFO file. Now phone is in bootloop.
I am really wondering that is FunkyHuawei able to install B235 Nougat firmware. I'll share all details who are looking solution to downgrade Oreo to Nougat.
livevalue said:
I successfully rebranded my phone to LON-L29C636 via your stock OEMINFO file. Now phone is in bootloop.
I am really wondering that is FunkyHuawei able to install B235 Nougat firmware. I'll share all details who are looking solution to downgrade Oreo to Nougat.
Click to expand...
Click to collapse
You'd need to flash the Oreo firmware with FHUnbrickTool if it's not booting. Or you can re-unlock the bootloader. Probably issue is you used the tool with unlocked bootloader and a modified partition somewhere, I'm guessing.
You might also be able to use eRecovery method with Android O firmware. Downgrading to N will need to be done AFTER you have it booting in Android O.
I can't monitor this thread well, so you should email FH support if you need help.
EDIT: I apologize. I thought you were using FH tools. Apparently not. Yes, FH can fix your phone, to answer your question from before. There is no other solution for M9Pro right now.
duraaraa said:
You'd need to flash the Oreo firmware with FHUnbrickTool if it's not booting. Or you can re-unlock the bootloader. Probably issue is you used the tool with unlocked bootloader and a modified partition somewhere, I'm guessing.
You might also be able to use eRecovery method with Android O firmware. Downgrading to N will need to be done AFTER you have it booting in Android O.
I can't monitor this thread well, so you should email FH support if you need help.
EDIT: I apologize. I thought you were using FH tools. Apparently not. Yes, FH can fix your phone, to answer your question from before. There is no other solution for M9Pro right now.
Click to expand...
Click to collapse
I wrote an email on 23th but there is no answer from FHteam. Anyway my phone now is totally bricked. Opening in error mode. Error no 13 with no image. As you know I tried to downgrade from Oreo to Nougat.
Can we fix it and install the original Chinese edition on my phone? No problem if it would be Oreo or Nougat.
I'm going to try to buy credits from a different way, because PayPal is not working in my area.
livevalue said:
I wrote an email on 23th but there is no answer from FHteam. Anyway my phone now is totally bricked. Opening in error mode. Error no 13 with no image. As you know I tried to downgrade from Oreo to Nougat.
Can we fix it and install the original Chinese edition on my phone? No problem if it would be Oreo or Nougat.
I'm going to try to buy credits from a different way, because PayPal is not working in my area.
Click to expand...
Click to collapse
Please email again and mention that you are livevalue on xda.
duraaraa said:
Please email again and mention that you are livevalue on xda.
Click to expand...
Click to collapse
I sent again and mentioned again that I'm livevalue at xda.
Anyway thank you for your support.
@duraaraa I want to thank FunkyHuawei team for responding very fast this time. We were online together.
I think my device hard bricked and I'll try everything to access fastboot mode. I always have bootloop and error mode continously. Key combinations don't work. Only power key, but it doesn't shuts down the phone, it always restarts. I was really expecting a downgrade solution from @mankindtw like he did for Mate 9 before. But he didn't and now device is hard bricked. Before an Oreo installation they need to warn people about there is no return.
No problem. I believe we will save my M9 Pro together. Thank you in advance and I'll stay in touch.
livevalue said:
@duraaraa I want to thank FunkyHuawei team for responding very fast this time. We were online together.
I think my device hard bricked and I'll try everything to access fastboot mode. I always have bootloop and error mode continously. Key combinations don't work. Only power key, but it doesn't shuts down the phone, it always restarts. I was really expecting a downgrade solution from @mankindtw like he did for Mate 9 before. But he didn't and now device is hard bricked. Before an Oreo installation they need to warn people about there is no return.
No problem. I believe we will save my M9 Pro together. Thank you in advance and I'll stay in touch.
Click to expand...
Click to collapse
if your phone can be detected by pc, it can be recovered don't lose hope
mutahharbashir said:
if your phone can be detected by pc, it can be recovered don't lose hope
Click to expand...
Click to collapse
I had neccesary testpoint and get board firmware. There is no problem anymore but anyway thank you in advance brother.
I used Firmware Finder and it did the job. I downgraded from LON-L29C432B368 to LON-L29C432B229. You need to select FullOTA-MF-PV version.
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.)