Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.
dthslce42 said:
Hello.
Recently i flashed this: ROM in my Redmi 10C, and now I can't unlock the bootloader to flash it back to the stock ROM. Its not exactly bricked, but I can't root it. Why do I need to root it? Because you can do all the fun things only if you have root of course!
My question is:
Is the Redmi 10C going to let me flash it through EDL mode with QPST/QFIL (Qualcomm emergency tools for dumdums like me)
Or am I forced to go to someone with an authorized MI account (and that person can flash it). Alternatively, can I get my MI account authorized, or at least borrow one only for this.
Thank you for reading, and good day to you.
Click to expand...
Click to collapse
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?
TThThank you f
SubwayChamp said:
First, be absolutely sure, which model, exactly is your device, check the code name of your device, and which ROM suits for it.
Still, not clear, how did you get to flash a custom ROM, with the bootloader locked?
Click to expand...
Click to collapse
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!
dthslce42 said:
TThThank you f
Thank you for answering. I apologize, the bootloader isn't locked. It's just that I cannot check the OEM unlock option (it's greyed out, on the system i installed).
First. I rooted my redmi 10c (still had the stock/default ROM)
Then. I proceeded to flash it (with twrp) with the ROM I quoted before. Although I suspect it didn't completed installation, because it doesn't have some features that all ROMs have (thank god it still has networking & basic telephony functions). And now i cannot root it, because i can't check 'OEM unlock' option.
I researched thoroughly and the only way I see fit (at the moment) is to use the EDL mode and the official 'MI Flash Pro tool'.
BUT according to various sources, the Redmi 10c falls in the category of models that need an Authorized MI Account (log into the official tool) to properly flash a system through EDL mode.
I want to restore it to the stock/default ROM. But to do that through EDL i need an authorized account.
My doubt is simple: do I really need the 'MI Flash Tool Pro' ? Or can I just enter EDL mode, use QPST/QFIL (also an official tool) and do it without the need to log in? (authorized).
Thank you for keeping up!
Click to expand...
Click to collapse
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.
SubwayChamp said:
There are some confusing concepts here.
Firstly, a locked device doesn´t admit custom images, OK, I must assume you know that, next, if you didn´t expressly re-locked it, then it remains unlocked, the toggle unlock OEM grayed out, is not a problem, always that it is checked, it means your device is still unlocked.
Anyway, if the doubt persists, can you provide some screenshots.
Click to expand...
Click to collapse
Mmm, i assumed the the device was still unlocked because it should persist (after you flash it any number of times you want). That, and when I restart it it shows an 'unlocked' padlock icon.
I'm going to post some screenshots.
Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)
dthslce42 said:
Pic 2: the 'OEM unlock' should appear with the other debugging (Depuración) options, it doesn't.
Pic 1: it only appears when I search for it, when i tap on it it doesn't do anything.
(Sorry for the Spanish)
Click to expand...
Click to collapse
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info
SubwayChamp said:
I guess you want to referring to OEM unlock toggle, that it´s not present. Again, that the toggle is not present, doesn´t mean, your bootloader is locked, most probably, the ROM you´re actually on is not showing, and nothing more, strange, but as it is.
So, you can do what you want, as the bootloader is unlocked.
You can be absolutely sure, by sending device to fastboot mode and doing fastboot oem device-info
Click to expand...
Click to collapse
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).
dthslce42 said:
Mmmmm. I forgot to clarify... It doesn't even let me transfer files trough USB. So fastboot mode is locked(?). You could say that the phone is kinda bricked. Since I have 0 clues on how to change the ROM.
But back to the core of this thread.
Is it advisable to use any of the tools: QPST/QFIL(Qualcomm), in EDL mode to change the ROM.
I ask here because i hope someone knows if using the Qualcomm tools is gonna work.
Since xiaomi tools ABSOLUTELY require an authorized account to complete the process (and not hardbrick the phone pls).
Click to expand...
Click to collapse
Man, please, put all the attention, to both, to me, and to your words. I don´t understand at all, why you say you´re bricked or something, or you say, you don´t know how to put another ROM onto your device when you already flashed in the past a custom ROM, Why you should use Qfil/QPST or other of those unbricking tool, if...
Your device has the bootloader UNLOCKED and you DON´T need to put the Xiaomi ROM into your device, an authorized account is needed when you need to flash the OFFICIAL ROM, not for any other custom ROM, in your case, you can flash any other custom ROM as you already did it in the past.
Better tell me:
1-Can your device be power on?
2-Can your device enter to TWRP, and/or fastboot mode?
3-What exactly do you want to achieve right now?
"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.
dthslce42 said:
"1-Can your device be power on?"
Yes.
"2-Can your device enter to TWRP, and/or fastboot mode?"
It can enter fastboot mode. But not TWRP, it was erased. I didn't realize until it was too late.
"3-What exactly do you want to achieve right now?"
Either change to other ROM. Or reinstall the current one. But I don't know how.
Click to expand...
Click to collapse
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.
SubwayChamp said:
Ok, if you have a fastboot mode working fine, then you just have to reinstall the recovery available for your device, as you did it once, then, rebooting to it, just flash the ROM available for your device. Jut repeat that process.
Click to expand...
Click to collapse
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)
dthslce42 said:
I'm really grateful mate. What you told me about the EDL mode (that i can install any ROM with the Qualcomm tool, as long as it's not the official from Xiaomi) was really helpful. Thank you!
The phone can enter fastboot mode, but it's not recognized by any PC. (That's why I say the 'OEM unlock' option it's the most likely culprit) so -i think- it cannot be done that way.
All drivers were installed (automatically, the unlock tool has an option to scan and install the correct drivers, and manually)
Click to expand...
Click to collapse
OK, from what I understood, you want to follow the guidelines provided, I mean, flash the TWRP again using fastboot, then boot to it, and from there can flash any custom ROM...
If I´m right, and this is correct, you are feeling that you´re stuck in fastboot mode but the device is not recognized as of now...
Unlock tool and also the Xiaomi Unlock tool or even the Xiaomi (Pro) tool, has the correct fastboot drivers for any Xiaomi device, BUT, the issue is "simply" that you have to "call" that specific drivers and "match" it to your device, the right drivers are already there, from within a long list of all of the device (compatible or not) drivers...
I mean, you just have to connect your device in fastboot mode, you have to see, either the Xiaomi bunny (in older devices) or the fastboot legend into your screen, then just update the drivers...
Keep the device manager windows opened in a part of your PC, and check the changes when you connect your device, then you have to see, some driver that appeared, and update it from the list following something like the images I´ll upload, the guide I made is to update EDL drivers, but apply the part you need, in order to get Android Bootloader Interface, note that your device has not to be listed under Port COM like in EDL.
When you uncheck this option, then you can find it from the list.
Related
Solved!
Firstly, I apologize for basic English, but it is not my first language.
I am desperate and urgently needing help.
I made the mistake of flash the Global rom 10.1.1 in a Chinese ver. and locking the bootloader through MI flash tools.
The result was a Bootloop to recovery.
Already tried:
Re-unlock the bootloader
- I get the message "Wait 30 days to unlock another device".
Install through recovery using Mi Pc suite 3.0 beta.
-With stable version 10.2.2 I receive the message "error install the latest version"
- With version Dev 9.1.14 "error to install the dev version download on the official website"
Finally in EDL mode with Miflash tools ver. 2018
- I get the message that I am not have permissions to flash any of the Roms above.
Can someone please help me, through some unknown process or through authentication my ID 1683581889.
Many thanks in advance.
Short tutorial
1- Start your device in EDL mode "test point" by : https://en.miui.com/thread-5293017-1-1.html .
2- Download TeamViewer 14.x.x, MIFlash tools 2018 and last version of the fastboot Rom "Dev or Stable".
3- get in touch with this guy " https://forum.xda-developers.com/member.php?u=5189577 " .
the man is a legend in 3min your device will be restored.
All credits are to NikSalsa, gonyla and nickgrserifos89.
hugocorreia said:
Firstly, I apologize for basic English, but it is not my first language.
I am desperate and urgently needing help.
I made the mistake of flash the Global rom 10.1.1 in a Chinese ver. and locking the bootloader through MI flash tools.
The result was a Bootloop to recovery.
Already tried:
Re-unlock the bootloader
- I get the message "Wait 30 days to unlock another device".
Install through recovery using Mi Pc suite 3.0 beta.
-With stable version 10.2.2 I receive the message "error install the latest version"
- With version Dev 9.1.14 "error to install the dev version download on the official website"
Finally in EDL mode with Miflash tools ver. 2018
- I get the message that I am not have permissions to flash any of the Roms above.
Can someone please help me, through some unknown process or through authentication my ID 1683581889.
Many thanks in advance.
Click to expand...
Click to collapse
If you flashed the Global rom on the Chinese model phone and locked the bootloader you'll have yourself a nice paper weight
I hope not,
When I did the flash, had the pc connected to a smarttv, due to high resolution the option "clean all and lock" was hidden. which led to screw up.
You need to reflash the stock Chinese firmware with Xiaomi's firmware flashing tool. If you unlocked your device through the official app, it will be able to re-unlock the bootloader to flash it.
It was my first choice. Tried with:
Miflash 3.0/3.x, Miflash pro 3.x, XiaoMiflash, XiaomoABD and always end up with same results " error install the latest version". Maybe i losing something.
With official unlock tool i get message "Wait 30 days to unlock another device".
Maybe because i unlink my account before,
the idea was return to full stock to resell the device.
hugocorreia said:
It was my first choice. Tried with:
Miflash 3.0/3.x, Miflash pro 3.x, XiaoMiflash, XiaomoABD and always end up with same results " error install the latest version". Maybe i losing something.
Click to expand...
Click to collapse
You can try EDL mode but not sure how that's done on the Mix 3
Mackay53 said:
You can try EDL mode but not sure how that's done on the Mix 3
Click to expand...
Click to collapse
At this moment, the device is disassembled in the EDL mode.
But when I try to flash a Rom I'm getting the message, that my ID does not have permissions to flash.
hugocorreia said:
With official unlock tool i get message "Wait 30 days to unlock another device".
Maybe because i unlink my account before,
the idea was return to full stock to resell the device.
Click to expand...
Click to collapse
Unlinking your account removes your ability to re-unlock your bootloader necause that devices bootloader unlock was tied to your account.
hugocorreia said:
With official unlock tool i get message "Wait 30 days to unlock another device".
Maybe because i unlink my account before,
the idea was return to full stock to resell the device.
Click to expand...
Click to collapse
jcsww said:
Unlinking your account removes your ability to re-unlock your bootloader necause that devices bootloader unlock was tied to your account.
Click to expand...
Click to collapse
And now because you can't boot phone to connect account to phone it's a paper weight. Not sure what else you can do.
You could try using the standard fastboot from google and running through the scripts provided by Xiaomi to try to flash, even though the BL is locked. You might be able to fix it that way. What I would do is connect the phone, hold down VOL Down + Power til you get Fastboot mode, and then try running through the fastboot lines one at a time in the Xiaomi script.
As others have mentioned, you have created a brick. Whatever you choose to do at this point is up to you, and you certainly could make your situation worse. If you live in a country that Xiaomi supports, you could get the device to a service center and they can almost certainly fix it. I am looking into Qualcomm EDL stuff on this device, and am hopeful that I can find a way to change the hardware origin flags at a hardware level. Nothing concrete yet though.
Edit: for clarity: I'm saying flash a CN STABLE version from fastboot, over the global version.
jcsww said:
Unlinking your account removes your ability to re-unlock your bootloader necause that devices bootloader unlock was tied to your account.
Click to expand...
Click to collapse
Now realise that, i done a mistake after another.
My hope is to find a solution , maybe S-unlock.
PWn3R said:
You could try using the standard fastboot from google and running through the scripts provided by Xiaomi to try to flash, even though the BL is locked. You might be able to fix it that way. What I would do is connect the phone, hold down VOL Down + Power til you get Fastboot mode, and then try running through the fastboot lines one at a time in the Xiaomi script.
As others have mentioned, you have created a brick. Whatever you choose to do at this point is up to you, and you certainly could make your situation worse. If you live in a country that Xiaomi supports, you could get the device to a service center and they can almost certainly fix it. I am looking into Qualcomm EDL stuff on this device, and am hopeful that I can find a way to change the hardware origin flags at a hardware level. Nothing concrete yet though.
Edit: for clarity: I'm saying flash a CN STABLE version from fastboot, over the global version.
Click to expand...
Click to collapse
I Will try.
Status:
Didn't work , lost recovery " system destroyed".
Now i only have fastboot and EDL mode.
I've been talking to the S-unlocked team, and they say they support Mi MIX 3 through EDL mode. The service costs $ 25. Does anyone know someone who provides the same service cheaper?
hugocorreia said:
I've been talking to the S-unlocked team, and they say they support Mi MIX 3 through EDL mode. The service costs $ 25. Does anyone know someone who provides the same service cheaper?
Click to expand...
Click to collapse
Cheaper??? That sounds like a bargain!
invisiblewave said:
Cheaper??? That sounds like a bargain!
Click to expand...
Click to collapse
I have to agree! You can't expect them to do it for nothing. It is a service and it will restore the device that isn't working to working condition. Definitely a bargain!
jcsww said:
I have to agree! You can't expect them to do it for nothing. It is a service and it will restore the device that isn't working to working condition. Definitely a bargain!
Click to expand...
Click to collapse
Sorry, but it's not my point of view, please understand.
So far U-Unlocker was unknown company I'm afraid to spend another 25 $ for nothing.
So far I'm losing $ 500 "device cost" I do not want to waste more money on a device that is device that is destined for resale.
hugocorreia said:
Sorry, but it's not my point of view, please understand.
So far U-Unlocker was unknown company I'm afraid to spend another 25 $ for nothing.
So far I'm losing $ 500 "device cost" I do not want to spend more money on a device that is device that is destined for resale.
Click to expand...
Click to collapse
That doesn't make much sense.
If you do nothing you lose $500, phone in current state has no resale value.
If you spend $25 you could potentially get your phone back to a working state with a few hundred value
hugocorreia said:
I've been talking to the S-unlocked team, and they say they support Mi MIX 3 through EDL mode. The service costs $ 25. Does anyone know someone who provides the same service cheaper?
Click to expand...
Click to collapse
Maybe the right question was.
Anyone know if they are reliable? It will work? Or someone used the service before for this device.
So, I ****ed up.
TL;DR: My device is locked with no way to unlock it.
Got it today, wanted to flash a ROM. So I install TWRP, all fine. I reset everything, also format, then of course my zip on internal storage is gone too. So I put it on a SD card and reboot the phone to recovery again. But I can't, because after wiping it just shows "system destroyed" or something. So I panic. Then I realize I can flash stock ROM via MI flash tool, do that, install TWRP again. But I still can't flash because the version is too low. So I decide to flash stock again, do an update and try again. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed. So I try to use the MI unlock flash tool, add phone to account, but no, because I didn't sign it at first it won't let me unlock because "your account isn't associated with this device". And now I can't do anything.
Is there anything I can do now apart from this testpoint method? I don't really wanna take the back off, I'm afraid of breaking it. Also the next Xiami store is like 800km from me and I don't wanna send it back cause it already took 2 months here and I paid 60 euros to customs.
I would really appreciate any help you could offer me. Thanks in advance!
remotefan said:
So, I ****ed up.
TL;DR: My device is locked with no way to unlock it.
Got it today, wanted to flash a ROM. So I install TWRP, all fine. I reset everything, also format, then of course my zip on internal storage is gone too. So I put it on a SD card and reboot the phone to recovery again. But I can't, because after wiping it just shows "system destroyed" or something. So I panic. Then I realize I can flash stock ROM via MI flash tool, do that, install TWRP again. But I still can't flash because the version is too low. So I decide to flash stock again, do an update and try again. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed. So I try to use the MI unlock flash tool, add phone to account, but no, because I didn't sign it at first it won't let me unlock because "your account isn't associated with this device". And now I can't do anything.
Is there anything I can do now apart from this testpoint method? I don't really wanna take the back off, I'm afraid of breaking it. Also the next Xiami store is like 800km from me and I don't wanna send it back cause it already took 2 months here and I paid 60 euros to customs.
I would really appreciate any help you could offer me. Thanks in advance!
Click to expand...
Click to collapse
1. did u officially unlock bootloader?
2. can u access fastboot?
3. did u remove mi account after unlocking bootloader?
4. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed
did you complete the flash process in MiFlash-Tool? or while flashing u plugged out usb?
If you have selected clean all & lock then your phone have booted to os, i think you locked the bootloader before flashing because bootloader lock command runs after firmware installation is complete
Simoom Sadik said:
1. did u officially unlock bootloader?
2. can u access fastboot?
3. did u remove mi account after unlocking bootloader?
4. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed
did you complete the flash process in MiFlash-Tool? or while flashing u plugged out usb?
Click to expand...
Click to collapse
1. The bootloader was already unlocked as I got it.
2. I can boot into fastboot mode
3. I skipped adding it in the first place cause I never really wanted to use the stock software, it's too china for me
4. I flashed after wiping in TWRP, it "completed", as it didn't show completion but the phone rebooted to stock recovery and stayed there, displaying "this MIUI version can't be installed" or something like that.
navi_58861170 said:
If you have selected clean all & lock then your phone have booted to os, i think you locked the bootloader before flashing because bootloader lock command runs after firmware installation is complete
Click to expand...
Click to collapse
That may be true, but maybe that's cause it didn't succeed in installing MIUI this time, see other comment to where it is now
remotefan said:
1. The bootloader was already unlocked as I got it.
2. I can boot into fastboot mode
3. I skipped adding it in the first place cause I never really wanted to use the stock software, it's too china for me
4. I flashed after wiping in TWRP, it "completed", as it didn't show completion but the phone rebooted to stock recovery and stayed there, displaying "this MIUI version can't be installed" or something like that.
Click to expand...
Click to collapse
since your phone is not associated with a mi account, u might need customer care support.
u said bootloader was already unlocked.
if u bought a used phone ask the original user for mi id+pass to unlock bootloader again
remotefan said:
So, I ****ed up.
TL;DR: My device is locked with no way to unlock it.
Got it today, wanted to flash a ROM. So I install TWRP, all fine. I reset everything, also format, then of course my zip on internal storage is gone too. So I put it on a SD card and reboot the phone to recovery again. But I can't, because after wiping it just shows "system destroyed" or something. So I panic. Then I realize I can flash stock ROM via MI flash tool, do that, install TWRP again. But I still can't flash because the version is too low. So I decide to flash stock again, do an update and try again. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed. So I try to use the MI unlock flash tool, add phone to account, but no, because I didn't sign it at first it won't let me unlock because "your account isn't associated with this device". And now I can't do anything.
Is there anything I can do now apart from this testpoint method? I don't really wanna take the back off, I'm afraid of breaking it. Also the next Xiami store is like 800km from me and I don't wanna send it back cause it already took 2 months here and I paid 60 euros to customs.
I would really appreciate any help you could offer me. Thanks in advance!
Click to expand...
Click to collapse
Ok since you have reached point where only a service centre visit can unlock it, I suggest you use an authorised account! I believe there are people online who accept payment in return for unlocking the bootloader (I have no idea how to find them tho, sorry)
These accounts are rare and are used by service centres to unlock bootloaders and stuff..and which TWRP did you even use? Use Peter's, the official one is **** and doesn't support decryption.
remotefan said:
So, I ****ed up.
TL;DR: My device is locked with no way to unlock it.
Got it today, wanted to flash a ROM. So I install TWRP, all fine. I reset everything, also format, then of course my zip on internal storage is gone too. So I put it on a SD card and reboot the phone to recovery again. But I can't, because after wiping it just shows "system destroyed" or something. So I panic. Then I realize I can flash stock ROM via MI flash tool, do that, install TWRP again. But I still can't flash because the version is too low. So I decide to flash stock again, do an update and try again. But this time I forgot to turn off "clean and lock" in the MI flash tool. So now the bootloader is locked and no stock ROM is installed. So I try to use the MI unlock flash tool, add phone to account, but no, because I didn't sign it at first it won't let me unlock because "your account isn't associated with this device". And now I can't do anything.
Is there anything I can do now apart from this testpoint method? I don't really wanna take the back off, I'm afraid of breaking it. Also the next Xiami store is like 800km from me and I don't wanna send it back cause it already took 2 months here and I paid 60 euros to customs.
I would really appreciate any help you could offer me. Thanks in advance!
Click to expand...
Click to collapse
U should buy a deep flash cable or u may make it at home.(search on youtube). Clean flash stock fastboot rom from mi flash in edl (emergency download mode). It will flash successfully. Then set up a mi account ( may be cratate a new one to unlock the bl). Then give try to mi unlock tool.
Note - suggest to buy a deep flash cabel instead for home made.
U may done flashing in edl mode only because bl is locked now.
A year ago i also forget to deselect clean and lock option and locked my bl accidently but i used above method and get success.
Sent from my Redmi Note 7 Pro using XDA Labs
remotefan said:
That may be true, but maybe that's cause it didn't succeed in installing MIUI this time, see other comment to where it is now
Click to expand...
Click to collapse
Actually while flashing it locks the bootloader after complete installation is done, so might be you first locked the bootloader you can check the script in fastboot rom
hackermssharma said:
U should buy a deep flash cable or u may make it at home.(search on youtube). Clean flash stock fastboot rom from mi flash in edl (emergency download mode). It will flash successfully. Then set up a mi account ( may be cratate a new one to unlock the bl). Then give try to mi unlock tool.
Note - suggest to buy a deep flash cabel instead for home made.
U may done flashing in edl mode only because bl is locked now.
A year ago i also forget to deselect clean and lock option and locked my bl accidently but i used above method and get success.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
So I tried this, and it did not work either with edl mode, it is still asking me for my account, which isn't affiliated with that device.
remotefan said:
So I tried this, and it did not work either with edl mode, it is still asking me for my account, which isn't affiliated with that device.
Click to expand...
Click to collapse
hey buddy Im on the same boat! My customer have an "indian version"miui on his note7 pro (China version) with unlock bootloader, after a while he flash twrp and flash "HAVOC" OS to it, it's work fine...but few days ago he want to change back to indian stock, he forget to switch the "flash and lock" to flash_all unlock...of cos, it fail and get to recovery show "This miui version can't be installed on this device", I really dunno WTF he is doing this! I try to flash it buy theree method already, EDL is unsuccessful it need an authorize account; Miflash Tool Pro, flash recovery rom it shows " Couldn't verify, looks like current ROM's network carrier type is different from that in the Recovery package..."
V10.3.8.0 and 10.3.10.0 got the same result; the third try is actually the XiaoMi adb method, someone is success to save their redmi note 5 by that...but as i try it on N7 pro it fail...!
Just wonder this N7 pro is brick by ARB already? any suggestion at all guys?
sky104hk said:
hey buddy Im on the same boat! My customer have an "indian version"miui on his note7 pro (China version) with unlock bootloader, after a while he flash twrp and flash "HAVOC" OS to it, it's work fine...but few days ago he want to change back to indian stock, he forget to switch the "flash and lock" to flash_all unlock...of cos, it fail and get to recovery show "This miui version can't be installed on this device", I really dunno WTF he is doing this! I try to flash it buy theree method already, EDL is unsuccessful it need an authorize account; Miflash Tool Pro, flash recovery rom it shows " Couldn't verify, looks like current ROM's network carrier type is different from that in the Recovery package..."
V10.3.8.0 and 10.3.10.0 got the same result; the third try is actually the XiaoMi adb method, someone is success to save their redmi note 5 by that...but as i try it on N7 pro it fail...!
Just wonder this N7 pro is brick by ARB already? any suggestion at all guys?
Click to expand...
Click to collapse
Have you tried to unlock using mi unlock?
If the devices was unlocked officially, you should be able to unlock again immediately without asking for the permission.
ne0t said:
Have you tried to unlock using mi unlock?
If the devices was unlocked officially, you should be able to unlock again immediately without asking for the permission.
Click to expand...
Click to collapse
Try already but no success; my fd's Redmi N7 pro is unlocked by someone outside...Im sure the account is already bounded, but u think It possible to flash the China developer ROM to it?
---------- Post added at 10:20 AM ---------- Previous post was at 10:18 AM ----------
The way Of xiaomi doing this is protective but stupid...and make us stupid too haha, so that's why I always tell my FD not to relock it after changing ROM...!
sky104hk said:
hey buddy Im on the same boat! My customer have an "indian version"miui on his note7 pro (China version) with unlock bootloader, after a while he flash twrp and flash "HAVOC" OS to it, it's work fine...but few days ago he want to change back to indian stock, he forget to switch the "flash and lock" to flash_all unlock...of cos, it fail and get to recovery show "This miui version can't be installed on this device", I really dunno WTF he is doing this! I try to flash it buy theree method already, EDL is unsuccessful it need an authorize account; Miflash Tool Pro, flash recovery rom it shows " Couldn't verify, looks like current ROM's network carrier type is different from that in the Recovery package..."
V10.3.8.0 and 10.3.10.0 got the same result; the third try is actually the XiaoMi adb method, someone is success to save their redmi note 5 by that...but as i try it on N7 pro it fail...!
Just wonder this N7 pro is brick by ARB already? any suggestion at all guys?
Click to expand...
Click to collapse
me too...
how we can unlock phone without test point?
Does anyone know how to solve this problem?
Hello. first of all you have to remove the back to be able to put the phone in edl mode. then you need to find someone with an account authorized to install a rom stock china for which you will have to pay. I paid $ 15. then you will need to associate the phone with your me account and unlock the bootloader. nothing else works. for a month I lost my nights trying dozens. until I paid everything was in vain. or you have the option of an authorized service, but I am convinced that it will cost you more. success.
delete
It's sd, no mtk
https://youtu.be/XzknDcBovWw
remotefan said:
So I tried this, and it did not work either with edl mode, it is still asking me for my account, which isn't affiliated with that device.
Click to expand...
Click to collapse
If you're able to access to EDL mode, you should be able to flash using QFIL tools instead of MiFlash. Something like this
I can't find anything definitive about whether it's rootable or not
Same here i tried every root app possible and failed.
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?
sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.
I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.
Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.
mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?
Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop
jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.
Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true
Hello,
I am trying to convert Tmobile OP9 to Global version and I am stuck at a basic step of getting the oem unlock code when trying to unlock the bootloader.
Details:
1. got my network unlocked from mobbdeep couple of weeks back.
2. Under Settings > "Network Unlock" status shows as unlocked
3. Installed the latest SDK as I am following the guide here to get the bootloader unlocked. When I boot in fastmode and run the oem command it stays at "waiting for device" and returns nothing.
Code:
fastboot oem get_unlock_code
When I run this, device list shows empty
Code:
adb devices
- Enabled USB debugging and stay awake options is checked from what I read on few posts
- When I restart the phone normally and then run "adb devices" it shows my phone listed
- Working on windows machine
What am I doing wrong here ?
TIA !!
PS: attached image shows the device state as Locked
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Superguy said:
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
Click to expand...
Click to collapse
Thanks for your response.
I tried that earlier assuming the same but it asked me to first flash the unlock token for which I am following the steps
I was however able to get the device listed after manually uninstalling/installing adb drivers
avid_droid said:
Check in device manager. If you have the yellow triangle on your phone in device manager just download android composite driver and update it through device manager/browse computer/ select unzipped folder and click OK.
Might be the issue
Click to expand...
Click to collapse
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
This thread was helpful as well. Thanks !
cass89 said:
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Click to expand...
Click to collapse
This thread was helpful as well. Thanks !
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
FRNK8 said:
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
Click to expand...
Click to collapse
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Hey thanks for the heads up. I will
Would infact first go through the conversion steps to go back to Tmo just incase things go south.
avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Following the guide here, I just performed the bootloader unlock successfully. Per your suggestion, I want to backup the modem files before I proceed any further.
I cant seem to recollect how do I backup the modem files when I did the same conversion for OP6T. Can you please guide me here before I proceed with the next steps.
I tried installing the partitions backup but it wont allow me without root. I vaguely remember that I hadn't rooted my device the last time while backing up these files or is root needed ?
TIA !
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
craznazn said:
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
Click to expand...
Click to collapse
Can you help me with the steps to root ? Just want to be careful while doing so.
I saw some posts but that was related to the Tmobile OP9Pro(in my case its its Tmo Op9). The boot images were different so I didnt try to play around.
Thanks !
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
craznazn said:
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
Okay did this step.
Downloaded an copied stock image and the boot_patched image provided on the link and copied to my phones internal storage
Also as next step said, rebooted the phone
- went to Magisk app > install > selected boot_patched.img from internal storage
- phone restarted
- When I open the partitions backup app it still shows "device is not rooted" warning
What step did I miss ?
FRNK8 said:
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
Click to expand...
Click to collapse
do you have a link for the driver I'm having the same problem
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.