SM-320FN FRP lock, custom OS installed, how to recover? - Samsung Galaxy J3 (2016) Questions & Answers

Hello,
Me, naab - accidentally turned off OEM boot options (didn't noticed), and restarted the phone (SM-320FN).
Now I have "custom binary blocked by FRP lock" message on boot. I've been using LineageOS 13, so I can't boot it right now.
How to recover this phone? Is is possible to reflash it via Samsung Kies (to the stock FW), then I unlock OEM Boot option and reflash it again to LOS? Or can I type some magic in console via ADB?

Fisz said:
Hello,
Me, naab - accidentally turned off OEM boot options (didn't noticed), and restarted the phone (SM-320FN).
Now I have "custom binary blocked by FRP lock" message on boot. I've been using LineageOS 13, so I can't boot it right now.
How to recover this phone? Is is possible to reflash it via Samsung Kies (to the stock FW), then I unlock OEM Boot option and reflash it again to LOS? Or can I type some magic in console via ADB?
Click to expand...
Click to collapse
Read this
https://forum.xda-developers.com/showthread.php?t=2154890
https://www.ayudaroot.com/root/root-galaxy-j3-sm-j320fn/

Related

[Q] Forgot Patter {USB debugging disabled}{Locked Bootloader}{4.4.2}

hello,
my nephew forgot pattern and when i enter recovery mode says (no command).
device has official kitkat firmware and locked bootloader and usb debugging disabled.
any ideas ??
You should be able to use the gmail account to unlock it after a few attempts. It would be fairly easy to unlock the bootloader and flash cwm if the stock recovery isn't working for a factory reset. In fact now I think about it unlocking the bootloader wipes the device anyway so if you are stuck boot into fastboot mode power and vol down then use adb ( you will have to set this up first) to input the command "fastboot OEM unlock" hit OK on the tablet and when the tablet reboots the bootloader will be unlocked it will also be reset which is the point of the exercise
Sent from my C5303 using xda app-developers app

OEM Unlocked

After unlocking the bootloader a month ago or so and installing tpxmm , I noticed oem unlock under developer options was disabled.
Well I had to enable oem unlock to disable device protection to reinstall tpxmm.
Should this be set to disabled now after install?
Sent from my XT1575 using Tapatalk
Doesn't matter. That setting only affects whether you can use the "fastboot oem unlock" command. Since your bootloader is currently unlocked, that setting will have no affect.
divinemyth99 said:
Doesn't matter. That setting only affects whether you can use the "fastboot oem unlock" command. Since your bootloader is currently unlocked, that setting will have no affect.
Click to expand...
Click to collapse
Old thread, but still relevant.
Are we sure about this? If "OEM unlocking" is disabled, does Moto's bootloader not block flashing certain images? I have read about other devices not allowing modification with this setting disabled, including flashing back to stock. The solution was restoring a full backup of stock in TWRP, then booting stock and enabling OEM unlocking.
Can anybody confirm if this is the case with the MXPE?
quakeaz said:
Can anybody confirm if this is the case with the MXPE?
Click to expand...
Click to collapse
That's the phone I have.
In Android OS, Developer Settings -> Allow OEM Unlocking is Off, but boot loader was previously unlocked and I have TWRP 3.0.0 installed. Rebooting to bootloader shows
Code:
Device is UNLOCKED. Status code: 3
Software status: Modified
I was able to upgrade to TWRP 3.0.2 using fastboot despite the Developer Settings- > Allow OEM Unlocking setting.
Re-locking the bootloader and restoring to stock as a bit of a process for another thread and if your bootloader shows "Device is LOCKED" then you will need to change the setting in Android before fastboot oem unlock will work. I've never had to change the setting since then, though, and every factory reset in android set it back to Off.
divinemyth99 said:
That's the phone I have.
In Android OS, Developer Settings -> Allow OEM Unlocking is Off, but boot loader was previously unlocked and I have TWRP 3.0.0 installed. Rebooting to bootloader shows
I was able to upgrade to TWRP 3.0.2 using fastboot despite the Developer Settings- > Allow OEM Unlocking setting.
Re-locking the bootloader and restoring to stock as a bit of a process for another thread and if your bootloader shows "Device is LOCKED" then you will need to change the setting in Android before fastboot oem unlock will work. I've never had to change the setting since then, though, and every factory reset in android set it back to Off.
Click to expand...
Click to collapse
Thank you for the info. Have you tried flashing stock recovery with the setting off? If so, no issues?
quakeaz said:
Thank you for the info. Have you tried flashing stock recovery with the setting off? If so, no issues?
Click to expand...
Click to collapse
Not in a log time, so I just tried just now and did the following.
Installed factory recovery
booted into factory recovery
wiped cache (I couldn't remember how to get the menu in the factory recovery, so that took a while =D)
booted into android
rebooted back to boot loader
flashed twrp
booted into recovery to verify twrp installed and is functional
Everything seems to be working.
divinemyth99 said:
Not in a log time, so I just tried just now and did the following.
Installed factory recovery
booted into factory recovery
wiped cache (I couldn't remember how to get the menu in the factory recovery, so that took a while =D)
booted into android
rebooted back to boot loader
flashed twrp
booted into recovery to verify twrp installed and is functional
Everything seems to be working.
Click to expand...
Click to collapse
You flashed stock recovery with the OEM unlocking option turned off, correct? That's what I was reading on a Hauwei device was the problem. With the setting turned off in stock, it wouldn't let him flash stock recovery image. He had to restore via twrp backup.
quakeaz said:
You flashed stock recovery with the OEM unlocking option turned off, correct? .
Click to expand...
Click to collapse
Yes, I left the OEM unlocking option in Developer Settings turned off through the whole process. I haven't turned that setting on since I originally unlocked my bootloader back in January.

How to Stock FW and Relock Bootloader? OP5

Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.
r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?
here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU
HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command
Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.

How to restore original imei & s/n {g935f}

Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.
kalirobot said:
Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.
Click to expand...
Click to collapse
It seems they changed imei may be because it was blacklisted. Imei wont get corrected without a box repair. And that dm verity issue will occur when you root using modification on system partition and it wont go away even after a reflash. You should have used systemless root. But you can bypass dm verity by flashing no verity opt encrypt from this link
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Flash it using twrp, and your phone should work on stock rooted rom with twrp recovery.
Sent from my S7 Edge using XDA Labs
I have got FRP : ON, will FRP block me? When i flash a twrp, FRP blocks the installation. Is this the same situation?
kalirobot said:
I have got FRP : ON, will FRP block me? When i flash a twrp, FRP blocks the installation. Is this the same situation?
Click to expand...
Click to collapse
Yes if its frp lock, try flashing no verity zip latest version using AP tab of odin. If it fails too, then you need to install custom rom through odin, then install twrp recovery.
Sent from my S7 Edge using XDA Labs
shah22 said:
Yes if its frp lock, try flashing no verity zip latest version using AP tab of odin. If it fails too, then you need to install custom rom through odin, then install twrp recovery.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Odin don't recognizes the zip, so i have to flash it only writing his route. But the flashing don't start anyway.
You can't flash or boot custom binaries with FRP lock on.
You need to disable FRP lock by enabling OEM unlocking under developer options (You tap on build number 7 times in settings, about phone, software information).
More information about flashing dm-verity here: https://forum.xda-developers.com/showpost.php?p=70488012
benjamen50 said:
You can't flash or boot custom binaries with FRP lock on.
You need to disable FRP lock by enabling OEM unlocking under developer options (You tap on build number 7 times in settings, about phone, software information).
Click to expand...
Click to collapse
I can install only a Factory binary firmware that don't has got the OEM option!
kalirobot said:
I can install only a Factory binary firmware that don't has got the OEM option!
Click to expand...
Click to collapse
You are pretty damn stuck, did you tried samsung smartswitch? You have dm verity error which wont let you boot stock rom and then you have oem unlock off which prevents from installing custom roms, so you are pretty badly stuck. Any advanced member with adb shell knowledge can help you now. But try smartswitch atleast.
Sent from my S7 Edge using XDA Labs
Smart switch doesn't work in this situation, i need help with adb.
Adb doesn't work durng the download mode.Adb works only during the "factory binary rom" mode. With some command i get errors of root permission. If nobody can help me with Adb, can i took the phone to somebody that has got the box to restore the original imei? Can i resolve the error in this way?
kalirobot said:
Adb doesn't work durng the download mode.Adb works only during the "factory binary rom" mode. With some command i get errors of root permission. If nobody can help me with Adb, can i took the phone to somebody that has got the box to restore the original imei? Can i resolve the error in this way?
Click to expand...
Click to collapse
https://www.androidsage.com/2017/06...w-to-enable-oem-unlock-on-any-android-device/
See this and try the fastboot method, and yes a box should fix this oem lock issue.
Sent from my S7 Edge using XDA Labs
shah22 said:
https://www.androidsage.com/2017/06...w-to-enable-oem-unlock-on-any-android-device/
See this and try the fastboot method, and yes a box should fix this oem lock issue.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
i'm following your guide, adb works but when i cornfirm the command to reboot in fastboot mode, the phone restarts itself normally in my factory binary rom... I need your help.
kalirobot said:
i'm following your guide, adb works but when i cornfirm the command to reboot in fastboot mode, the phone restarts itself normally in my factory binary rom... I need your help.
Click to expand...
Click to collapse
Bro if it didn't work for you then i guess it wont, you should try using box, these adb commands don't work for every device, but here are the steps, give commands without commas ;
1. Make sure usb debugging is enabled in developer options.
2. Type 'ADB devices' to see if it displays your device.
3. Type 'ADB reboot bootloader'
4. Type 'ADB fastboot devices' and it should display your device in fastboot
5. Now type 'fastboot OEM unlock'
6. Again type 'fastboot OEM device-info' to check the status of oem unlock.
7. Last type 'fastboot reboot' to reboot phone to OS.
If these commands don't work for you, then i am sorry only a box can solve your issue. Good Luck.
Sent from my S7 Edge using XDA Labs
Hello guys, i resolved the problem with a box. Now i have got Android 7.0. The phone works well and now FRP is on off. But there is now another problem. The bluetouth doesn't start and when i turn off the wifi, the phone forgets all the saved wifi passwords. I need your help. Thanks of all.
Ps: Who repaired my phone yesterday, installed an app called "OctoNetwork". Without it internet(2g 3g 4g) doesn't work.
kalirobot said:
Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.
Click to expand...
Click to collapse
first if ur phone boots then turn on oem unlock and then try flashing whatever u want
try flashing the stock rom again but this time make sure
to tick the box next to update bootloader

Got stuck on Android one logo

Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.
Hi Rakesh,
Is you issue get resolved?
I have also got warnings of internal storage full in my MI-A1 and after that my phone got switched off. I also tried to switched on and it got stuck at android one logo.
Please help me out if your issue get resolved?
Try booting in TWRP and using the file manager to delete some user data to make space.
barrack1 said:
Try booting in TWRP and using the file manager to delete some user data to make space.
Click to expand...
Click to collapse
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
saurabhsh23 said:
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
Click to expand...
Click to collapse
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
manpildo said:
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
Click to expand...
Click to collapse
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
saurabhsh23 said:
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
Click to expand...
Click to collapse
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
manpildo said:
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
Click to expand...
Click to collapse
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
Click to expand...
Click to collapse
Yes, unlocking bootloader wipes data.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
Click to expand...
Click to collapse
No, if you wipe your phone through recovery you won't need to flash anything. It just deletes all your stuff without touching the system.
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Any update here please?
vaibhav08 said:
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Click to expand...
Click to collapse
Guys pls help me i got stuck on boot logo i want to flash stock rom pls help me
I'm in the same boat. Unable to access developer options as phone won't boot and its stuck at the android one logo.
Fastboot oem unlock gives error Flashing Unlock is not allowed.
Is there anyway around this?
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Face_11 said:
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Click to expand...
Click to collapse
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
jack_21 said:
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
Click to expand...
Click to collapse
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Face_11 said:
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Click to expand...
Click to collapse
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
jack_21 said:
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
Click to expand...
Click to collapse
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Face_11 said:
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Click to expand...
Click to collapse
If you see a triangle, you are in recovery mode
You need to press a button combination to see options, Search on Google for that

Categories

Resources