Hello,
my dad accidently encrypted his phone, forgot the password as well as his google account. After that i factory reset the phone just to get FRP lock.
I would like to flash TWRP, root the device and install a custom rom.
Can someone please tell me if the bootloader is locked?
If it is locked, is it possible to unlock it while the phone is in download mode (obviously i cant get into OS Options)?
Will this whole action acutally kill FRP?
Thank you very much.
OEM Unlock, try to restore the original firmware
dokmanXYX said:
OEM Unlock, try to restore the original firmware
Click to expand...
Click to collapse
I already flashed Stock Rom which die Not help. Can you please Tell me How to find ans flash Stock Firmware?
humanica said:
I already flashed Stock Rom which die Not help. Can you please Tell me How to find ans flash Stock Firmware?
Click to expand...
Click to collapse
How did you flash the stock rom? What were your exact steps?
The more we know the better we can help.
Normally you have to do the following steps:
If you haven't stock firmware you can use smartswitch to download the stock rom.
Then you can use odin to flash the rom.
Here is a description what to do:
https://androidmtk.com/flash-samsung-stock-rom-using-odin
When your phone is working you have to enable oem unlock in the developer options. Then you can flash twrp via odin. in TWRP you can flash custom roms.
spirit_of_the_ocean said:
How did you flash the stock rom? What were your exact steps?
The more we know the better we can help.
Normally you have to do the following steps:
If you haven't stock firmware you can use smartswitch to download the stock rom.
Then you can use odin to flash the rom.
Here is a description what to do:
https://androidmtk.com/flash-samsung-stock-rom-using-odin
When your phone is working you have to enable oem unlock in the developer options. Then you can flash twrp via odin. in TWRP you can flash custom roms.
Click to expand...
Click to collapse
I loaded the stock rom from a site linked by xda developers and flashed it by odin.
The Stock Rom boots but google lock is still active so i cant unlock oem.
I already tried to flash twrp which does not work (i tested different versions of odin as well as twrp, different usb ports/cables) because the Bootloader is locked as well.
It always showed "fail" at the end of flashing.
humanica said:
The Stock Rom boots but google lock is still active so i cant unlock oem.
Click to expand...
Click to collapse
I read on a Website that you have to login with that google account to unlock frp after a factory reset. This was invented to prevent thievery.
You have to recover the password but if the account is totally lost. I have no idea how solve this at the moment.
Also read this:
https://www.google.de/amp/s/www.and...-locked-out-your-phone-after-resetting-it?amp
humanica said:
I loaded the stock rom from a site linked by xda developers and flashed it by odin.
The Stock Rom boots but google lock is still active so i cant unlock oem.
I already tried to flash twrp which does not work (i tested different versions of odin as well as twrp, different usb ports/cables) because the Bootloader is locked as well.
It always showed "fail" at the end of flashing.
Click to expand...
Click to collapse
did u got this fixed? if yes..pls share the process..
you could try loading a samsung developer option app through a usb stick because samsung file explorer pops up automatically and while in option you could try to erase the phone or activate OEM unlock . Just a thought thou
akadriu said:
you could try loading a samsung developer option app through a usb stick because samsung file explorer pops up automatically and while in option you could try to erase the phone or activate OEM unlock . Just a thought thou
Click to expand...
Click to collapse
doesnt work that way...i tired.
Hi, were you able to find a solution?
I had an online chat with Samsung, if I bring the phone and proof of purchase, they can remove frp for A$66.
Guys i have the same problem and don’t know what to do
Flashed stock rom with odin but i get DRI error
Did you fix that?
I'm sorry you run into the dumbest "feature" ever.
If someone's gonna steal a phone they won't look up whether or not the device has this kind of "protection" and they will find a way around it eventually. All it does is to make regular people pay the manufacturers several times for the same device as it passes through the hands of friends or family.
That being said, I've had to deal with this a few times after the kid who inherited this phone accidently turned off developer options on a rooted (ad/tracker blocked) phone with google family link. This was the process I went through:
Keep trying to get it into Download mode.
When you do you will still see the frp lock notification up in the left corner with the other info.
Keep trying to flash the stock rom, it will work eventually. Took me like... 5 or 6 times I think before it magically worked all of a sudden.
Once you're in System, use one of the bypass google account verification methods - I can't remember which one worked for me as I only had to do it once when we first got the phone. since then I've known the new account we made and can reset the password through google family link in case the kid changes the password as they do sometimes.
When/if you get in and changed the OEM unlock setting, you can flash a custom recovery and try one of the attached files to remove frp "forever".
You should be allowed to boot once with a custom rom at this point. To test if the "frp destroyer" worked, I turned off the OEM unlock setting and rebooted the device and frp lock was back. I'm not sure exactly which partition frp lock is on, the attached "frp destroyer" does:
Code:
#!/sbin/sh
mount /system
mount -o remount,rw /system
Build=/system/build.prop
chmod 0644 $Build
sed -i "/ro.frp.pst=.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*.*.*/d" "$Build"
echo "# FRP Destroyed" >> $Build
umount /system
but seeing as clean flash wipes /system I guess there's a backup of it somewhere on some other partition which is later restored there.
I ended up making sure OEM unlock was always on to allow for reboots. After a few months we swapped to LOS14.1 and forgot to double check OEM and frp made our lives hell again.
I'll try and find the stock rom I used cause sammobile has archived a bunch of them for the J3 since I last did this but I'm pretty sure I have a copy of the file on some external drive somewhere (I hope). If I find it I'll come pack and post the link to an upload.
good luck!
p.s: (i'm moving on from android to postmarketOS to hopefully contribute to a stable enough linux phone that tech illiterate people in the family can use. I thought android was going to be this when I got my first galaxy s1 but since then it's become more and more like iOS with bloat features "for our protection/their profit".)
bambiii said:
I'm sorry you run into the dumbest "feature" ever.
If someone's gonna steal a phone they won't look up whether or not the device has this kind of "protection" and they will find a way around it eventually. All it does is to make regular people pay the manufacturers several times for the same device as it passes through the hands of friends or family.
That being said, I've had to deal with this a few times after the kid who inherited this phone accidently turned off developer options on a rooted (ad/tracker blocked) phone with google family link. This was the process I went through:
Keep trying to get it into Download mode.
When you do you will still see the frp lock notification up in the left corner with the other info.
Keep trying to flash the stock rom, it will work eventually. Took me like... 5 or 6 times I think before it magically worked all of a sudden.
Once you're in System, use one of the bypass google account verification methods - I can't remember which one worked for me as I only had to do it once when we first got the phone. since then I've known the new account we made and can reset the password through google family link in case the kid changes the password as they do sometimes.
When/if you get in and changed the OEM unlock setting, you can flash a custom recovery and try one of the attached files to remove frp "forever".
You should be allowed to boot once with a custom rom at this point. To test if the "frp destroyer" worked, I turned off the OEM unlock setting and rebooted the device and frp lock was back. I'm not sure exactly which partition frp lock is on, the attached "frp destroyer" does:
Code:
#!/sbin/sh
mount /system
mount -o remount,rw /system
Build=/system/build.prop
chmod 0644 $Build
sed -i "/ro.frp.pst=.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*.*/d" "$Build"
sed -i "/ro.frp.pst=.*.*.*.*.*/d" "$Build"
echo "# FRP Destroyed" >> $Build
umount /system
but seeing as clean flash wipes /system I guess there's a backup of it somewhere on some other partition which is later restored there.
I ended up making sure OEM unlock was always on to allow for reboots. After a few months we swapped to LOS14.1 and forgot to double check OEM and frp made our lives hell again.
I'll try and find the stock rom I used cause sammobile has archived a bunch of them for the J3 since I last did this but I'm pretty sure I have a copy of the file on some external drive somewhere (I hope). If I find it I'll come pack and post the link to an upload.
good luck!
p.s: (i'm moving on from android to postmarketOS to hopefully contribute to a stable enough linux phone that tech illiterate people in the family can use. I thought android was going to be this when I got my first galaxy s1 but since then it's become more and more like iOS with bloat features "for our protection/their profit".)
Click to expand...
Click to collapse
Thank you! I finally unlocked my FRP on my ASUS ZenPad 8.0 Z380M (P00A). I failed to overwrite my FRP-partition with SP-Flash-Tool, but with TWRP 3.2.1 and FRP_Destroyer_v3.0 it worked finally!
I originally found this thread (FRP Destroyer - flashable zip), which did not have all the versions. Luckily @Bambii posted them here.
I have an Huawei P30 Lite stucked with FRP from my company.
What is the first step? Do i need a custom ROM to use FRP destroyer?
xiconqoo said:
Thank you! I finally unlocked my FRP on my ASUS ZenPad 8.0 Z380M (P00A). I failed to overwrite my FRP-partition with SP-Flash-Tool, but with TWRP 3.2.1 and FRP_Destroyer_v3.0 it worked finally!
I originally found this thread (FRP Destroyer - flashable zip), which did not have all the versions. Luckily @Bambii posted them here.
Click to expand...
Click to collapse
HOW DO I DO THIS IF I CANT EVEN GET INTO THE PHONE?? I ENTER THE EMAIL ADDRESS AND PASSWORD ATTACHED TO THE PHONE BUT IT SAYS ERROR TRY AGAIN IN 24 HOURS
Holhat said:
HOW DO I DO THIS IF I CANT EVEN GET INTO THE PHONE?? I ENTER THE EMAIL ADDRESS AND PASSWORD ATTACHED TO THE PHONE BUT IT SAYS ERROR TRY AGAIN IN 24 HOURS
Click to expand...
Click to collapse
not sure but u must restart in download mode ad with Odin install TPW and after restarting in TPW install FRP_Destroyer_v3.0
Related
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
jumam21 said:
Hello.
I try to make ENG-boot file from ENG ROM (combination)
I uncompress Combination File and take sboot.bin , boot.img file to make .tar
And I flash that file show adb enable message but phone is Infinite boot
Then stuck in samsung galaxy S8 LOGO
How can I make adb enable file
Model : korea g950
Click to expand...
Click to collapse
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Re
rudimenta said:
Why dont you flash with odin? Easier plus you can easily select a suitable firmware package from one of the sites?
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
I mean How can I make ADB enable file from combination File.
jumam21 said:
I mean How can I make ADB enable file from combination File.
Click to expand...
Click to collapse
Exynos? I hope so because there is no sboot file for snapdragon ?
You don't need the factory boot for exynos. Just enable OEM unlocking
partcyborg said:
Exynos? I hope so because there is no sboot file for snapdragon
You don't need the factory boot for exynos. Just enable OEM unlocking
Click to expand...
Click to collapse
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
noidodroid said:
He most likely cannot access that due to having his phone google locked. If that is the case. More than likely is by what he is asking. There is a program called FRP Hijacker by Hagard that allows making an adb enabled boot.img but it never works for me at least on newer android OS 7+. Havent checked logs yet to see why. The file flashes fine but of course is not adb enabled. Im thinking signing and other issues. for some. If anybody knows a solid way please post here. I am researching so probably will find my solution soon i hope.. Reason for the need that most have is due to not having a combination file (engneering firmware) for a certain device to pull the boot.img or boot.img + system.img to flash when enabling ADB and settings on a specific binary Samsung FRP (Google Locked) device.
Click to expand...
Click to collapse
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
partcyborg said:
Frp bypass is not a kosher topic here as it's most common use case is to unlock stolen hardware. If that is his problem he should either give the phone back to its original owner, it if it's his account go through the password recovery process with Google
Click to expand...
Click to collapse
This has also been told to me by a mod ive spoke with time to time but the others really don't seem to mind as long as it is to help others and such. Which is what i do when i put up a manual tutorial. I usually do all by freestyling (no looking into anything unless really needed). If the same PartyCyborg from Android Forum Community. We don't know each other but I have used your work past and present and had a swell time finding through archives but this i enjoy. Very cool work man esp the last bit i asked you about on i believe an older Samsung 2014? device to action with your Rom's latest. Alright back to AndroidForum Community I have explained my whole outlook & debated the whole FRP issue with phones today. It's a challenge and it's helpful to those that aren't running masses of stolen phones through boxes (hey even stolen hardware once seized returns back to the community and has to be delt with.. i as do others get some devices from LEA property) and also that huge majority of people who quickly create accounts without jotting down and remembering info. Then i could go back into bulk onto stores who legally obtain (auction for example) then have to either a) find a way to fix frp and or 2) resell these devices 3) part out as google locked LB's etc. Google Lock and FRP in general is a VERY good thing IMHO. I want to see us make a move to more secure reliable FRP locks such as iClouds. We also have a security section here on XDA where all sorts of the latter and even deeper is discussed. Win Win for Security overall if you think about it all and take it in. I've said this before in other Areas of the internet I am from and I will say it again in similar words "they build it, we bypass it, they improve it.......(reversing.. updating.. learning.. phase) and the process continues.". We are improving security on everything be it my old days email filters (especially the old ways) or be it Google Lock Security & FRP and the countless other companies small and big across the globe with related protection put in place. Don't put a dark hat on it all.. at least just yet. -not directed toward you by any means or anyone else.. just my quickie worth of that whole 2 cents for what its worth.
I've tried about a dozen sets of threads about go into Fastboot, run Fastbook OEM Lock or Fastboot Flashing Lock etc and every time I just get a message saying its not allowed on the PC. In the Fastboot on the phone it says Secure Boot = Yes, Device State = unlocked. It was a long while back that I unlocked and then flashed it and although I never used a custom ROM I can't remember exactly what I did or the order I did it in.
I just want to take the phone back to its original vanilla state.
Sorry if this has been covered elsewhere.
When the phone is in Fastboot mode - in Windows 10, it is not seen using the command adb devices but it is using fastboot devices
When the phone is fully booted up - in Windows 10, it is seen using adb devices but not using the command fastboot devices
USB debugging is enabled on the phone
As I say, sorry if its a daft question and I'm sure I'm overlooking something obvious but going round in circles here.
Thanks in advance,
David
adb and fastboot is not set properly on you system
and for usig Stock ROM you dont need to lock bootloader
surajloharia said:
adb and fastboot is not set properly on you system
and for usig Stock ROM you dont need to lock bootloader
Click to expand...
Click to collapse
Thanks, but with respect that's pointing out the obvious rather :/ what I am looking for is advice on how to do it properly... its already clear that I haven't done so thus far.
So what do I do to enable my phone to automatically update again? Every time it attempts to it fails it downloads fine, but always fails when it attempts to install the update. Surely there must be something else I need to do to remove all the previous stuff I've done?
DavidElders said:
Thanks, but with respect that's pointing out the obvious rather :/ what I am looking for is advice on how to do it properly... its already clear that I haven't done so thus far.
So what do I do to enable my phone to automatically update again? Every time it attempts to it fails it downloads fine, but always fails when it attempts to install the update. Surely there must be something else I need to do to remove all the previous stuff I've done?
Click to expand...
Click to collapse
Updates fail when System partition is altered
either manually with file replacements or you have rooted your phone with magisk/Su
The best way is to flash latest Full ROM zip and device will return to get updates automatically
surajloharia said:
Updates fail when System partition is altered
either manually with file replacements or you have rooted your phone with magisk/Su
The best way is to flash latest Full ROM zip and device will return to get updates automatically
Click to expand...
Click to collapse
Phone was rooted. So there's no way to unroot at all? Or does flashing a full ROM do that? Thanks for the advice
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
There are a lot of great video tutorials on YouTube. Just search for Odin flashing tutorials and watch a recent one.
Also these types of posts should go into the General forum and not the Development one.
gavin watson said:
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
Click to expand...
Click to collapse
Samsung devices do not support FASTBOOT nor do they have a FASTBOOT mode, So you will not be able to do this even if you root.
gavin watson said:
Hi all,
I've been trying for hours to root my Samsung Galaxy Tab A (SM-T510) and am completely stuck...
I have managed to unlock the bootloader, enabled developer mode, that is fine but when moving to Odin I'm getting stuck, have read all kinds of guides and can't get past the next stage.
I'm actually unclear as the the correct steps, my only reason for rooting is because I need to issue this command so that I can have the device boot automatically when the charger is connected:
Code:
fastboot oem off-mode-charge 0
Do I first use Odin to load twrp and then I install the ROM? I'm not sure of that part.
One other thing I'm noticing is that when I try and and use Odin to flash twrg is that on the tablet in red it says 'Only official released binaries are allowed to be flashed', is this relevant and how to resolve?
One thing I have successfully done is to flash back the stock ROM from Sammobile (via Odin) and that worked fine.
Would really appreciate some help on this. I do not have a preference on which ROM to load, I just need to be able to run the above command.
Thanks in advance!
Click to expand...
Click to collapse
RTFM!!! There was a post just yesterday in the discussion forum on how to unlock the bootloader and that has to be done FIRST. Until recently, the only Samsung tablet with locked bootloaders were those tied to a "carrier". That is no longer true. In oder to flash ANYTHING other than a stock ROM, you must first UNLOCK THE BOOTLOADER!!!!!!! And you DON"t do it with ADB or fastboot.
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..