Hello everyone, does anyone know if this error is from the game or from the phone itself?
My phone is a OnePlus 6T
What happens is that I had the bootloader unlocked but I never rooted the phone and I only had TWRP and when I entered fortnite it wouldn't let me play since it eliminated me when I fell from the bus and I decided to install the factory rom and relock the bootloader but the same error keeps happening that eliminates me from the game
Excerpt from Fornite Android FAQ
If you’re unable to match make on Android with a message about your device being rooted, an unlocked bootloader, the Android Debug Bridge, or has failed the SafetyNet check this is because your device meets at least one of the above criteria. If this happens, your device will not be able to play Fortnite.
As stated in the message, any attempts to bypass this check may result in an account ban. We understand this is disappointing but Epic Games Player Support is unable to remove this message or ban from your device.
Click to expand...
Click to collapse
xXx yYy said:
Excerpt from Fornite Android FAQ
Click to expand...
Click to collapse
There is this problem, I am not a root user and I don't have the bootloader unlocked either and I tried everything and I still can't play it
At the moment it passes the SafetyNet test
To force relock the boot loader and reset the device, run the
Code:
fastboot flashing lock
command on the device.
Then re-install Fortnite.
xXx yYy said:
To force relock the boot loader and reset the device, run the
Code:
fastboot flashing lock
command on the device.
Click to expand...
Click to collapse
What I get is this message XD
C:\adb>fastboot flashing lock
...
FAILED (remote: Device already : locked!)
finished. total time: 0.005s
My recommendation: contact EPIC
https://support.epic-portal.io/hc/en-us/
Related
Hey there, first of all I just signed up at this forum but know and love it for a long time, so please bare with me if I make some formal mistakes.
But to the Problem.
I think I played a little bit too much with my old Honor 8 FRD L09 and wiped a little bit too much but basically now it's stuck in boot (where the blue Honor logo is) and doesn't boot further.
Can go into fastboot ( Phone Unlocked, FRP Lock)
Can't go into Twrp or maybe I just don't know how (I could go into TWRP yesterday but then I did something and now I can't)
Can go into Huawei eRecovery but everytime I try to recover I get the errorcode "getting package info failed"
I don't know what version of Android is on there but I didn't do systemupdate for a long time so I think it can be as low as Android 5.X.X if thats possible ^^
When I connect with ADB devices the list of devices is empty
When I do fastboot flash recovery it give me:
C:\Users\user\Downloads\platform-tools>fastboot flash recovery_ramdisk RECOVERY-V2.img
Sending 'recovery_ramdisk' (9100 KB) OKAY [ 0.223s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
So yeah, I honestly don't know further and all the other Threads here to recover my phone didn't work (most of them say go into fastboot but the I always get the same error on every recovery image I try)
So is there a greater fate to my tried and true Honor 8 than beeing remembered as a bottleopener?
Pls fast help, thx guys
You have relocked your bootloader, because of that you can't install flash recovery. Now you should unlock bootloader in fastboot with this command: fastboot oem unlock <unlockcode>. Unlock code is the code which you use for unlocking the bootloader.
Sujanth said:
You have relocked your bootloader, because of that you can't install flash recovery. Now you should unlock bootloader in fastboot with this command: fastboot oem unlock <unlockcode>. Unlock code is the code which you use for unlocking the bootloader.
Click to expand...
Click to collapse
Bootloader should be unlocked cus every time I go into fastboot mode on my phone it says bootloader unlocked, but I'll devinitaly give it a try later when I am at my computer
When I tipe the code in I get this:
C:\Users\sarah\Downloads\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
C:\Users\sarah\Downloads\platform-tools>fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
I don't have the Unlock Code anymore. I tried to get it from the Huawai homepage but there I can register with my Huawai ID but I can't find the unlock code and I also don't know if it's even saved in my account on the homepage.
I also tried third party apps to unlock the bootloader, but with all the apps I used the phone has to be turned on and that is not possible
Check out my post for a fix
https://forum.xda-developers.com/ho...tion-guide-t3788129/post76469677#post76469677
if it helped you please hit thanks:good::good:
I was trying to downgrade to android 6 (FRD09), phone stucked at bootloop. Cant do anything. i just waited to let the battery died, and now i cant charge the phone. When i plug it to charger the screen is blinking with thunder image, so doesnt charge. When ı connect it to pc just on fastboot mode connecting. How can i restore this phone?
Hi,
I have a new X95 with Android 10 go edition. aperently I get an error message when I use some apps.
do not disturb access this feature is not available on this device
Is there anything I can do, to solve this problem?
I would like to flash another img file to the device but got all the time <wating for device> any solution for that?
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
tennoguchi said:
Constantly get 'unauthorised', oem boot set to unlocked, usb debugging enabled, tried revoking and re-enabled no change....help
Click to expand...
Click to collapse
Use only this command:
Fastboot flashing unlock
I too want to unlock, root and customize the X95... And failed at the very first steps.
I hope some of the forum gurus watches this phone/thread
Here's the steps I took and the errors I got, any help would be appreciated!
1. enable "OEM unlocking" in development options
2. adb reboot fastboot
3. a) fastboot flashing unlock FAILED (remote: 'Unrecognized command flashing unlock')
3. b) fastboot oem unlock FAILED (remote: 'Command not supported in default implementation')
Also, this phone seems not to be recognized in bootloader mode (displays only "=> fastboot", but fastboot doesn't recognize any device).
When booting to recovery, entering fastboot from there (same as after "adb reboot fastboot"), I can get to the point of failure above.
I'm really uncomfortable with the current setup, any help would be appreciated!
Someone got root
Someone got root.
Thank you.
gatolocox said:
Someone got root.
Thank you.
Click to expand...
Click to collapse
This answer/question (?) is not really helpful, can you please elaborate?
Any news on how to root the x95?
Olize said:
Any news on how to root the x95?
Click to expand...
Click to collapse
I haven't tried since the failure reported above, meanwhile I got a redmi note 9s for 119€, so I'm using this one on a custom setup now.
Still using the x95 as an AP, I'm interested on any progress made on the topic..
Recently rooted my new Zenfone 7. Is it possible to remove Bootloader unlocked Warning message at the start up of the system? Thanks for an answer.
re-lock the bootloader
Boot into fastboot, then send this command from your pc.
fastboot oem asus-lock
how did you get root to work? I followed the instructions listed and it would not work for me.
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Jkm15 said:
I followed the instructions there: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/ in fastboot mode you should update android drivers manually through device manager to get it work otherwise you'll get " waiting on device " error and it won't flash TWRP.
Click to expand...
Click to collapse
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Jkm15 said:
Is it possible to remove Bootloader unlocked warning without re-locking device though?
Click to expand...
Click to collapse
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Joeb2000 said:
Getting TWRP on and working was fine. It was when I went and tried to flash Magisk that it kept causing a bootloop.
Why? Unless you plan on overwriting TWRP, there is no benefit to having it unlocked all the time. TWRP will still work after it is re-locked. and you can unlock it again via the app anytime you need to update.
Click to expand...
Click to collapse
Had locked bootloader on device with magisk. Result is fastboot loop =|
Same wish here. that warning screen is ugly....
I'm trying to flash a custom Android ROM on my Huawei Y6 2018 but when i'm in fastboot mode it says:
Phone: locked
FRP: unlock
I want to know how to unlock phone because when i try to install the ROM using
fastboot flash system "system_img_name".img
it says
FAILED (remote: Command not allowed)
AFAIK Huawei decided in 2018 to generally deny unlocking their devices' bootloader. Recently, they also have stopped providing bootloader unlock code to any Huawei device.
Whyte_Real said:
I'm trying to flash a custom Android ROM on my Huawei Y6 2018 but when i'm in fastboot mode it says:
....
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
In addition of the upper response, I wanted to add that some websites pretend to be able to root/unlock your Huawei device for money. They're mostly scams so please do not go there (for your sake)
And actually there are ways (very specific tho, and patched) to brute force the bootloader unlock, but the chances that it works are slim to none. (In fact I precise that because I'm sure some will come and say "No Ur. Wrong I saw that dude do it")
Have a nice day
Nevermind I just gave up trying, I unlocked everything, even bootloader and frp, but when I go installing the .img with TWRP it does not reboot after install succeed. I gave up, thanks anyway
My device is a OnePlus 8T originally purchased from T-Mobile. I unlocked the bootloader to flash OxygenOS 12 in the open beta. Everything is working splendidly, but I can't seem to relock the bootloader. Using fastboot flashing lock, I get an error message asking me to flash the unlock token first. When attempting fastboot flash cust-unlock unlock_token.bin, I get an error asking to turn on OEM unlocking. OEM unlocking is greyed out because the bootloader is unlocked. Can you help? Thanks!
scothouse said:
My device is a OnePlus 8T originally purchased from T-Mobile. I unlocked the bootloader to flash OxygenOS 12 in the open beta. Everything is working splendidly, but I can't seem to relock the bootloader. Using fastboot flashing lock, I get an error message asking me to flash the unlock token first. When attempting fastboot flash cust-unlock unlock_token.bin, I get an error asking to turn on OEM unlocking. OEM unlocking is greyed out because the bootloader is unlocked. Can you help? Thanks!
Click to expand...
Click to collapse
here brother:
Thanks, but my phone asks for an unlock token when I execute fastboot oem lock or fastboot flashing lock I get the error message: FAILED (remote: 'Please flash unlock token first.') When attemptIng to flash the token, I get the error message: FAILED (remote: 'Please turn on OEM unlocking in Settings - Developer option'). I heard back from OnePlus Support, and it sounds like I would need to perform a factory reset in order to lock the bootloader. That would revert the phone to the T-Mobile OxygenOS 11 image. I unlocked the bootloader so that I could flash the global OxygenOS 12 image. Also, I'm hearing from other folks in the OnePlus Community that the bootloader should remain unlocked if I'm in the beta. I'm not sure about that, but, for now, I haven't found a way to lock the bootloader and retain the beta image. Thanks, tho, I appreciate the link.
scothouse said:
Thanks, but my phone asks for an unlock token when I execute fastboot oem lock or fastboot flashing lock I get the error message: FAILED (remote: 'Please flash unlock token first.') When attemptIng to flash the token, I get the error message: FAILED (remote: 'Please turn on OEM unlocking in Settings - Developer option'). I heard back from OnePlus Support, and it sounds like I would need to perform a factory reset in order to lock the bootloader. That would revert the phone to the T-Mobile OxygenOS 11 image. I unlocked the bootloader so that I could flash the global OxygenOS 12 image. Also, I'm hearing from other folks in the OnePlus Community that the bootloader should remain unlocked if I'm in the beta. I'm not sure about that, but, for now, I haven't found a way to lock the bootloader and retain the beta image. Thanks, tho, I appreciate the link.
Click to expand...
Click to collapse
Yeah, there is no way to retain the beta image until OnePlus Gives an official update of OxygenOS 12 for your phone. and if you want to lock bootloader, u have to be on the official version.
BUT THERE IS NO WAY TO LOCK BOOTLOADER AND USE OxygenOS 12 FOR NOW. SO STOP SEARCHING
Gotcha - makes sense and will do. Thanks again!
Spuffyffet said:
BUT THERE IS NO WAY TO LOCK BOOTLOADER AND USE OxygenOS 12 FOR NOW. SO STOP SEARCHING
Click to expand...
Click to collapse
There is no mentioning of unlocking bootloader for OB1 OOS12 in official thread.
@scothouse I ran into a smiliar situation with the OnePlus 8 5g tmobile. After installing the global Rom and upgrading to android 12 i couldnt relock it.
so what i did was downgrade my phone to android 11. the OEM unlocking was still greyed out but i was able to execute the fastboot flash cust-unlock unlock_token.bin command. then voila i locked it.
once you do that then update your phone then you are down.
Just use MSM tools. Of course everything will be factory reset
samdaman91 said:
@scothouse I ran into a smiliar situation with the OnePlus 8 5g tmobile. After installing the global Rom and upgrading to android 12 i couldnt relock it.
so what i did was downgrade my phone to android 11. the OEM unlocking was still greyed out but i was able to execute the fastboot flash cust-unlock unlock_token.bin command. then voila i locked it.
once you do that then update your phone then you are down.
Click to expand...
Click to collapse
Were you able to re-upgrade to Android 12 once the bootloader was locked again?
jefffeely said:
Were you able to re-upgrade to Android 12 once the bootloader was locked again?
Click to expand...
Click to collapse
Yes with OTA
In case anyone is on Android 13, I was able to re-lock the bootloader without issue.
I didn't need the unlock_token back when I flashed the global ROM to replace the Tmo one. I do need the token for the re-lock purpose though