Related
Hello,
After the purchase of my phone i unlocked the bootloader, installed a custom rom of android M, everything went fine, twrp, root, etc.
Few days ago I wanted to give a shot at Nougat. I went through a couple roms but lacking certain functions i needed. I then tried one last stock nougat beta rom (from this link : https://forum.xda-developers.com/honor-8/development/beta-android-7-0-emui-5-l04c567b320-frd-t3529465
This was the worst rom i've encountered. Please don't use it.
Three reasons : No bluetooth, TWRP gone, and no keyboard pre-installed.
Yes. You can only first boot this rom with google voice typing. I'm not joking.
More than that i cannot finish the initial boot of the rom, i get stuck at the "enter your google account" (try to enter yours with google voice...)
I can't even ignore it, it says that "This device was reset. To continue, sign in with a Google Account that was previously synced on this device".
Anyway, now that I lost TWRP i wanted to flash it back. My bootloader being still unlocked (phone shows "your device has been unlocked and cannot be trusted" at each boot), i went to adb to flash twrp.
I got this message after trying to flash it :
...
FAILED (remote: Command not allowed)
...
I get this message after i try to flash TWRP, update, boot or anything.
I've read that i need to enable oem unlock in the developer settings. Thing is I'm stuck before i can access any parameters.
I even tried Huawei Multi-Tool, with boot, recovery, unbrick, but again, can't flash anything.
tl;dr :
- Nougat 7.0 EMUI 5.0
- Stuck in initial boot
- Only type with google voice
- No TWRP
- FAILED (remote: Command not allowed) error when trying to flash anything
What can I do ?
EDIT : I did manage to enter my google account, but it says that i need to log in with one of the owner's account. I never entered any other account on my phone... Definitely stuck.
This question was already answered a million times before! Just use the search button!
This Honor 8 forum is full of threads created by newly come member that just create a new thread without any use when they could just search for the already answered questions!
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Telperion said:
Plug in USB to computer, hold down power + volume down until you enter bootloader. Flash recovery system image again, then reboot into recovery and re flash another ROM.
Click to expand...
Click to collapse
Even when i'm in fastboot mode I can't flash anything, boot.img, recovery.img, system.img... nothing.
Fastboot mode shows "PHONE Unlocked" "FRP Lock", if that helps.
I tried using the rollback solution shown here https://forum.xda-developers.com/honor-8/help/totally-screwed-honor-8-t3556678/post71033483#post71033483. Intermediate package did apply but the full android 6.0 firmware failed to update.
And yes I've been searching around this forum before posting, but I can't find a post talking about my problem, being unable to access the rom in normal boot, unable to flash anything.
Is there a way to fix the "FAILED (remote: Command not allowed)" error message ? As it is the only think keeping me from doing anything on my phone
Or maybe trick the phone into flashing a rom through recovery (like a rollback but with a random custom rom instead) ?
Hi, did you ever find a fix for this?
Rommco05 said:
Are you missing some stuff from the system?
Click to expand...
Click to collapse
I don't believe so. Why?
Rommco05 said:
You need to install zip data. Which is your model and build number?
Click to expand...
Click to collapse
FRD-L04, and my Build Number is whatever the build number is for the first Nougat Beta from last year haha.
But how would I install zip data if flashing stuff via fastboot isn't working?
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
---------- Post added at 09:16 AM ---------- Previous post was at 09:14 AM ----------
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Are you referring to the Data Fix.zip? Also, I haven't been able to flash the 6.0 Stock ROM Via ercovery.
Rommco05 said:
FRD-L04 US model, right? First beta was maybe B320..?? Via dload
Click to expand...
Click to collapse
Rommco05 said:
For flash to 6.0 u need rollback packages and full M rom. Is your phone US model? I try send u links if is
Click to expand...
Click to collapse
Yeah I have the US model
Rommco05 said:
First install biggest second small, over dload methodhttp://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v72309/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Click to expand...
Click to collapse
Thanks, so what's the install method for this?
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.
Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.
Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...
I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....
Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"
Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?
Let's see
Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?
shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4
So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.
Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.
The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)
I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
x-fighter said:
i had the problem, when the cell, automatic restarted and it stuck on this screens, but it never came back, i already tried flashing the cellphone, and i already tried adding a custom bootloader, but no luck, it gave me the information that it mismatch, and attempts to enter the bootloader, without luck, i also already tried to only boot with fastboot, and no luck, it stucks on the twrp or m screen or shows different issues like screen fading or rumbling without reason, attempted to enter the recovery and only got to normal recovery from android, attempted to sideload the zip, and got a verification error, and it fails, again, i cant install a custom recovery, it always fails, and i dont know what to do... i really need help, any suggestion?? i already searched and didnt found any tools, flasher tool v.2 not found, and other tools are not able to help as well, help!!
edit, forgot to add, its an moto g. 2013 , xt1032 ANDROID LOLLIPOP
Click to expand...
Click to collapse
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
sd_shadow said:
which bootloader?
locked?
which firmware?
flashed how?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
https://m.imgur.com/nSFMea9
http://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg
Sent from my PH-1 using XDA Labs
---------- Post added at 01:48 PM ---------- Previous post was at 01:47 PM ----------
neither one of those says what files you are trying to flash
Sent from my PH-1 using XDA Labs
attached
Sent from my PH-1 using XDA Labs
x-fighter said:
i am unable to use other than the normal bootloader, htt p://cdn.droidviews.com/wp-content/uploads/2014/02/moto-g-bootloader-mode.jpg but mine says unlocked code 3, i used fastboot to attempted to flash the phone, and nothing changed. it has the stock firmware lollipop 5.0.2, codename falcon, i flashed it with fastboot, but no luck, attempted to added by sideload on the android recovery default, and it gives me the errorhttp s://i.imgur.com/nSFMea9.jpg and i am unable to add any file, it doesnt has external sd
Click to expand...
Click to collapse
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
tepar said:
From the picture you uploaded, says that your bootloader is locked, so that is why you can't flash any custom recovery. First you need to unlock your bootloader first but BACKUP FIRST, cause it will erase your internal storage when you unlock your bootloader. After unlocked, then you can flash custom recovery. Hope that helps.
Edit: but if your bootloader is really already unlocked, than try this, flashed twrp, then power down your phone by pressing the power button, then boot to twrp by press power button + volume down buttom. Don't reboot to twrp using the option im bootloader mode or using adb.
Click to expand...
Click to collapse
i will upload a more reccent one, where i already unlocked it, but i will try whaat you edited, thank you!! let me try and post results
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Please someone help me i spend 2 days and still nothing! How can i open this phone? Stock rom, with/without root, custom rom whatever, just tell me how can i open this phone
up
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
shae23 said:
You get that command when trying to flash the wrong recovery partition, was your room nougat or Oreo based?? If nougat it's fastboot flash recovery recovery.img and Oreo fastboot flash recovery_ramdisk recovery.img I think you are trying to flash the wrong partition
Click to expand...
Click to collapse
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
cannurkars said:
No, my twrp is not wrong, i installed before, and i used long time, till broken. I installed wrong twrp recovery over correct recovery (i was trying to chance recovery because project treble). Thats why my twrp broken. Now i try to correct one, but adb says "not allowed". My custom rom nougat based.
Click to expand...
Click to collapse
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
I will try it. Thank you very much.
cannurkars said:
Guys i have a really really big problem with mate 9 (MHA-L29). I broke both twrp and system same time (please don't ask why.)
Now, my phone don't open, just fastboot&rescue mode, useless huawei recovery (which can't format data neither install stock rom). Besides, i can't install stock rom because i tried once, and i downloaded wrong system file, and i can't format the phone now. Because of that, stock rom that i download sd card not working too. Because there is a dload file in phone.
worst of all, i can't install twrp again, because my fastboot screen tell me that: "Phone Unloced" (with red) "FRP Lock" (with green). When i try to install twrp, adb says "Failed, remote command not allowed"
Now, if can install the twrp, all my problems will be solve. There is 1 custom rom (RomAur) and 1 system backup.
How can i install twrp with this situation?
Click to expand...
Click to collapse
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
ConnerZhao929 said:
During startup the menu there is a option to go in Huawei e-recovery, when you are at the start up menu hold volume up for about 5 second.
Click to expand...
Click to collapse
No it wasn't work for me. But thank for your attention. I'm glad to find a good person to help me and my problem solved about 1-2 hour ago.
Special Request
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
ante0 said:
With FRP lock you'll have to use DC-Phoenix.
But it costs €19 (For 3 days usage).
Simply put you can bypass FRP with it by force closing DC-Phoenix when it has activated the backdoor, after this you can flash anything from fastboot (until you reboot).
So you could use it to flash back TWRP.
Or you can use it to install stock firmware
Click to expand...
Click to collapse
AniMaL92 said:
Hey ante . Is it possible to help me ? I rooted my phone 2 days back and messed it up while downloading a framework app which ended me up in a bootloop. I have been reading and following your posts of you helping others. I don't really get the steps what I should follow.
My phone is unlocked. FRP shows Unlock.
Rooted on oreo and I tried e-recovery and fastboot steps you mentioned in other threads using kernel and ramdisk etc. ( After this I have lost access to TWRP and I am simply getting EMUI Screen with options for Factory Data Reset and Wipe Cache Partition. I don't know where it is going to lead me next :-/.
Also downloaded Huawei Extractor and tried to extracted specific files but the firmware file I have doesn't have CUST.img file.
Also the site link you mentioned for download firmware is in some other language and I am unable to search for my firmware.
I also tried the placing update file in the dload on my sd card but fails at 5%. The file was correct and I am sure I did'n download the wrong firmware.
Currently it shows this on the fastboot screen.
Andorid reboot reason
: AP_S_ABNORMAL 32
NA
Just don't know what I should be doing ? PLEASE HELP BRO?
Click to expand...
Click to collapse
What's your firmware now?
You can get that info in Fastboot using
Code:
fastboot oem get-product-model
fastboot oem get-build-number
Since your recovery and fastboot still functions you probably will only need to use HWOTA to get back to stock.
It can be found here: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
But post your cust/build before proceeding.
Also cust.img is found in UPDATE.APP in the hw data zip.
Problem Solved - Somewhat
Hey ante. Thanks for the promt reply. I got it solved by using CHIMERA tool.
Would like to suggest others also stuck with same issue to use CHIMERA.
Note - It is a paid tool and 100% legit and it can help with all problems related to FRP, Bootloader Lock / Unlock & also flashes back to factory firmware.
However what I am facing now I have flashed another version of firmware which isn't my region and some features of my phone like fingerprint scanner and other things are not working but phone is back to live. So Im glad and looking forward to searching for clean Oreo Firmware for my region to flash using CHIMERA Again.
Also, the sick and stupid part of it. I went to the service center and a person non-technical told me straight that you lost your device and it's of no use now. We cannot fix such issues 99% but I'll still ask my team and let you know after 3 days.
Thank God I didn give them and wasted my time and money.
As soon as I returned, I followed up to things and got it done myself. :good:
Anybody can possibly suggest a official firmware Oreo EMUI for Middle East Region!? If not which one can be flashed instead and where to download from?
My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!
[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek
does encryp work on this ? dont need to backup just hide data part if fone is stole
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.
SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp
Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before
OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?
I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.
fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?
lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.
Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)