I'm totally NOOB for unlocking RN3Pro, currently i am on MIUI 8.2 / 8.2.9.99 LHOMIDG & applied for official unlock but we all know how it will go down
Please help me unlocking the bootloader i will so much appreciate it, i am trying to study it from last night but i don't know what procedure to follow, THERE'RE SO MANY
P.S @falcon4wars if you have any advice, you're also a RN3Pro owner right?
Thank You All...
Why don't you just wait to get permissions? It only took me 3 days after I applied. Unlocking it unofficially is more complicated than the official way anyways.
I got permissions,still its waste !
jimakos98 said:
Why don't you just wait to get permissions? It only took me 3 days after I applied. Unlocking it unofficially is more complicated than the official way anyways.
Click to expand...
Click to collapse
As you said I got my permissions within 3 days and then I tried unlocking my device and it gets stuck at 50% saying couldn't verify device I also tried again after the next 4 days and its the same problem if you can help me fix this I would be really happy or give me another way to unlock bootloader officially or unofficially!
Are you logged into the phone with the same miui account that you are unlocking with?
Have you used the miui (find my device)? Doing this is supposed to help with the verify.
if you cant wait, like most of us here (thats something good) i found that getting a custom twrp recovery can make you forget about unlocking the bootloader (because you can flash roms, supersu, xposed, sound mods and other zip files by using twrp).
i will give you a link to that forum
https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
just pay attetion to know if you have a kenzo or kate device.
their hardware is exactly the same except kate (also know as special edition) has more network bands .
i had 2 days flashing all kenzo roms and getting bootloops then someone told me i was kate and i almost exploted of happiness.
Hey guys, thank you all so much for replying i much appreciate RN3SD community, it turns out my RN3SD bootloader is already officially unlocked HOW ABOUT THAT? I just bought it 2 days ago and its Built-in unlocked... Amazing
C:\adb>fastboot devices
******** fastboot
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.008s]
finished. total time: 0.009s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.001s
I had the same thing happen to me, spent a week trying all the things to unlock it, because it kept getting stuck at 50% and then checked and it was already unlocked, got mine from gearbest so maybe they dont relock them when they put on the vendor rom...
eu4ria said:
I had the same thing happen to me, spent a week trying all the things to unlock it, because it kept getting stuck at 50% and then checked and it was already unlocked, got mine from gearbest so maybe they dont relock them when they put on the vendor rom...
Click to expand...
Click to collapse
Yeah i think so bro, anyway what ROM are you using currently? today i am gonna go for Android N 7.1 but MIUI have this Touchwiz feeling which i am not ready to leave right away since i gifted my Galaxy Note 4 couple of days ago, that phone was surely a beast.
P.S Redmi Note 3 Front camera is not so good though
I have tried CM 13 and I tried the latest global development rom, I have the "lazy modem" issue on mine, basically after use and the screen locks the phone will no longer receive calls/texts, but data is fine. Im trying out different things as it doesnt seem to be a totally widespread issue so not sure what causes it.
Related
Hey guys! Im having trouble unlocking my HTC One M9 (Sprint) with htc Dev.
I downloaded Android sdk, installed platform tools, i open command prompt window inside the platform tools folder
and I type adb devices, and it shows my device number and that it is connected. I reboot my phone into download mode, and I
type fastboot oem get_identifier_token and instead of showing me the token number i get
C:\Users\Rudy Molina\Desktop\platform-tools>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Rudy Molina\Desktop\platform-tools>
I have no clue what to do.
I have tried it many times moved the folder around. uninstalled htc sync manager sdk manager and reinstalled. i get the same thing every time.
I recently did the ota update, not sure if that has something to do with it. So im now running
Android 5.1 sense 7
Please help me out. Im thinking about installing an RUU to have Android 5.0 and then trying the htc dev unlock.
I'm not sure but might have something to do with Android's Anti-Theft protection. Try disabling all security on the phone including and pin codes or lock screens, reboot and try again. Doesn't look like a driver issue
rmolina06 said:
Hey guys! Im having trouble unlocking my HTC One M9 (Sprint) with htc Dev.
I downloaded Android sdk, installed platform tools, i open command prompt window inside the platform tools folder
and I type adb devices, and it shows my device number and that it is connected. I reboot my phone into download mode, and I
type fastboot oem get_identifier_token and instead of showing me the token number i get
C:\Users\Rudy Molina\Desktop\platform-tools>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Users\Rudy Molina\Desktop\platform-tools>
I have no clue what to do.
I have tried it many times moved the folder around. uninstalled htc sync manager sdk manager and reinstalled. i get the same thing every time.
I recently did the ota update, not sure if that has something to do with it. So im now running
Android 5.1 sense 7
Please help me out. Im thinking about installing an RUU to have Android 5.0 and then trying the htc dev unlock.
Click to expand...
Click to collapse
Go to Settings - developer options and check box next to Allow OEM unlock first.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Go to Settings - developer options and check box next to Allow OEM unlock first.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
.......IT WORKED!!!!!!! lol I cant believe i didnt see that. Thank you soo much!!
rmolina06 said:
.......IT WORKED!!!!!!! lol I cant believe i didnt see that. Thank you soo much!!
Click to expand...
Click to collapse
Glad to hear you got it sorted. Welcome to XDA by the way.
Sent from my A0001 using XDA Free mobile app
Guys, I have the same problem rmolina06.
However, the phone does not start.
Is there a way to disable this thing, from fastboot?
: Pianto:
Unlock bootloader problem Sprint HTC One m9
Hi,
I also have a brand new Sprint HTC One M9 and am trying to unlock the bootloader.
I seem to have the exact problem which you had and also learned to enable the OEM unlock setting. However i still have a problem with the next step which is to submit the token ID on the htcdev.com site. Everything in the process works until I submit the token to htcdev. I get an error regarding an invalid token or wrong token length message each time i try it.
Can you let me know if you have succeeded and if so did you have to perform any additional steps.
Thanks
Tiernan
littlebam said:
Hi,
I also have a brand new Sprint HTC One M9 and am trying to unlock the bootloader.
I seem to have the exact problem which you had and also learned to enable the OEM unlock setting. However i still have a problem with the next step which is to submit the token ID on the htcdev.com site. Everything in the process works until I submit the token to htcdev. I get an error regarding an invalid token or wrong token length message each time i try it.
Can you let me know if you have succeeded and if so did you have to perform any additional steps.
Thanks
Tiernan
Click to expand...
Click to collapse
I have seen before where when I copy my token from the cmd prompt, it will put spaces on every line screwing up the token hence kicking out an error. Try pasting it into notepad first and delete any extra spaces before submitting.
I had trouble "marking" my token as well, highlighted way too much. I looked into the properties of edit and unchecked something about word wrap and it was all good. Sorry I can't remember the particulars or the terminology.
I am trying to buy a Sprint phone today (possibly the Htc one M9). Is it still possible to unlock bootloader through the HTC website? And if so, must the phone be completely paid off?? I really do not want to deal with any Samsung phones since I have had my At&t GS4 with locked bootloader for 2 years. Is there any roms or good mods for this phone yet?
There is no good roms for either the Note 5, s6, or Edge plus so if HTC allows unlocking bootloader to allow for a custom recovery than I would think the development will be good over time unlike any locked down samsung phone. Any advice on a good phone?
cyrusalmighty said:
I am trying to buy a Sprint phone today (possibly the Htc one M9). Is it still possible to unlock bootloader through the HTC website? And if so, must the phone be completely paid off?? I really do not want to deal with any Samsung phones since I have had my At&t GS4 with locked bootloader for 2 years. Is there any roms or good mods for this phone yet?
There is no good roms for either the Note 5, s6, or Edge plus so if HTC allows unlocking bootloader to allow for a custom recovery than I would think the development will be good over time unlike any locked down samsung phone. Any advice on a good phone?
Click to expand...
Click to collapse
yes, u can unlock via htcdev.com anytime...I do know of one good ROM
Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).
Samsung A02s(SM-A025F)
I do these steps any body help
1.I unlock oem through developer option
2.I unlock bootloader successfully
3.I downloaded firmware and patch AP with magisk to root
4.I flash Patched AP
5.After getting my phone rooted successfully I want to install TWRP Recovery
6.I downloaded unofficial version of TWRP from xdaforums....
7.I followed the steps guided here
The steps are as follows
1.reboot to boot loader and flash vbmeta_disable.tar
2.Put TWRP tar in AP and flash
3.Reboot to recovery
4.Disable encryption
Go to Advanced >Terminal : type "multidisabler"
5.Go back to wipe>Format Data>type "yes"
6.Reboot system
This is my first experience to root and flash TWRP.... but after that when I reboot my phone got lock .... only official binaries allowed to be installed....and stuck there
I got frightened so I locked my bootloader
But nothing happens...
I downloaded stock firmware and flash.....now my phone works perfectly But I want to root my phone I searched and found a correct way to root but now oem unlock option is not found in developer options....
I watched hundreds of videos on yt and searched a lot on Google but
found no proper solution.....someone tell me to wait 7 days....
In about phone> phone status>uptime
Uptime should be equal to 7days... then oem unlock option will appear but ...... I want another solution date change and WiFi connect is not solution ... If any body knows any other solution please guide me ... I'll be very thankful.....
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
bmwdroid said:
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
Click to expand...
Click to collapse
Thanks for reply...
This bypass method doesn't work in my device
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Mahmoudm.kamal said:
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Click to expand...
Click to collapse
Keep us updated.. I'd like to get my OEM unlock to come out of hiding.. this is frustrsting.. i see all these tutorials for the A02s root, twrp and ROMs and whatnot and I'm itching to get flashing!
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Noobiu said:
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Click to expand...
Click to collapse
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Mahmoudm.kamal said:
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Click to expand...
Click to collapse
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Swyen said:
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Click to expand...
Click to collapse
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Mahmoudm.kamal said:
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Click to expand...
Click to collapse
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
ewrecc said:
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Click to expand...
Click to collapse
STOP TRYING TO UNLOCK A US DEVICE ITS NOT POSSIBLE
Swyen said:
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
Click to expand...
Click to collapse
Which tool did you use?
I got a locked tracfone moto g play from a relatives. I try to flash twrp to use other roms. But when I try to unlock bootloader it said:
(bootloader) usage: fastboot oem unlock < unlock code >
FAILED (remote failure)
finished. total time: 0.080s
Does that mean I have to contact the carrier to unlock my phone so I can unlock booloader? And if it is, are there any ways to install twrp without unlock it? Pls help me?
Thank for reading!
Not the carrier but Motorola is who you have to contact. In fact the only thing you need to do is register your phone with Motorola. Follow the instructions as stated officially by Motorola in order to get your device ID and check if your device qualifies for an unlock code. Keep in mind this is not a network/carrier lock. This is for unlocking the phone's bootloader which is essential for rooting and flashing.
In regards to TWRP it may be a hit or miss with how you follow what you got to do based on the posts spread throughout this forum and whether you'll have a flawless experience with a fully functional TWRP, or you may have one of the phones manufactured with some slightly different hardware which winds up TWRP flashing OK but no touchscreen capabilities. Or you may not even get or need to flash it and get by just sideloading the image.
Honestly, reading thru all relevant threads will be your best interest. Check out the other like-design Moto G 2021 device forums as well for additional insight on how these devices behave, quirks and common issues, etc. Good luck and try to have fun doing this.