Question Secure check fail modem - Samsung Galaxy A52s 5G

Got this error when trying to flash NcX S21FE may release, and when tried to flashed the march ncx release, the error now is bootloop. I can still go to my twrp recovery
Can someone help me , please? thanks

You need to flash the latest stock ROM firmware with Odin and then flash vbmeta, TWRP and NcX again.
That error you're getting happens due to the firmware in NcX being too new for the firmware on your phone.

Related

bootloader help pleaeseeee :(

Im currently on atom v9, which is 4.2.2, but i wanna flash the new pa 3.1 which is full 4.2.2 which needs the updated baseband and bootloader. My bootloader is currently PRIMEKK15, and i tried to flash the new primcl03 zip but it just says failed in twrp. is there any way around this?
how did you flash the TWRP?? do it as the same way you did flash custom recovery using fastboot
you can get the latest bootloader and radio (in the factory image tgz file) at http://developers.google.com/android/nexus/images

[Q] Problem flashing PA 3.6

I just updated my TWRP to the latest version of 2.5.0.0; I then tried to flash the Paranoid Android 3.6 rom and I get "asset failed: getprop(ro.bootloader")
I've been flashing roms for the past two years and have never received this error before....
Any ideas on what this is or how to fix this?
Thank you
There's 20 posts regarding this issue. It's your bootloader that needs to be updated to the newest MD4 bootloader. Here is a link to latest md4 firmware aio update http://db.tt/Qt6NcH0a just flash this in recovery boot up and go back into recovery and flash the rom.
Sent from the future via Tapatalk 4

Unable to flash CM 11 using TWRP

Hello
I am currently running the latest version of TWRP (openrecovery-twrp-2.8.1.0-d2att) and I am trying to flash CM 11, but I get an error in red "Failed"
I am even getting a failed error as well when flashing the bootloader in the thread below.
I have successfully been able to flash SlimKat 4.4.4 and Dirty Unicorn with no problems. I think I had the same problems as well when trying to flash Paranoid Android.
I have tried flashing the files from both the external SD card and Internal. No go.
This is the thread I am following: http://forum.xda-developers.com/showthread.php?t=2682905
Here is the error I get when flashing:
You cannot flash from your current bootloader. Current version: I747MVLUEFNE6
E: Error executing updater binary in zip '/external_sd/Flash/CM/1/boot_CWM_I747MVLUEMK5.zip'
Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
audit13 said:
Try using the latest version of Philz Touch for the d2lte to flash files.
You can flash the most recent zip from TWRP.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Click to expand...
Click to collapse
Ok, so I flashed the latest zip using the TWRP App rebooted into PhilZ Recovery and tried to flash the bootloader ( boot_CWM_I747MVLUEMK5.zip) from here: http://forum.xda-developers.com/showthread.php?t=2321310
Still got an error: Please upgrade to latest binary...You cannot flash from your current bootloader. Current version: I747MLUFNE6
E: Error in /storage/sdcard1/Flash/CM/1/boot_CWM_I747MVLUENK5.zip (Status 7) Installation aborted
Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.
audit13 said:
Do not flash any bootloader to your phone. It is good that it did not flash mk5 over ne6. This will brick for phone.
Click to expand...
Click to collapse
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.
Iv never had any issues using philz touch to flash.
drakemiller40 said:
Ok thanks. Where can I find the latest boot-loader for my device? I was trying to follow this guide to flash CM11 and it told me to download the latest boot-loader and update it: http://forum.xda-developers.com/showthread.php?t=2682905
I guess the thread I wrote above is an outdated guide to flashing CM11. Would you happen to know the steps I should take to flash cm11 for my device with my current bootloader?
BTW I still can't flash the CM11 Rom in Philz Touch Recovery.
Click to expand...
Click to collapse
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?
audit13 said:
You have the ne6 bootloader. Do you have an i747m or i747? It will make a difference when it comes to flashing an updated bootloader and modem.
Are you downloading the latest CM11 from the cyanogen site?
Click to expand...
Click to collapse
Thanks for helping out so far. My Model number that shows up in "About Device" in my phone's settings say SGH-I747M. Yes I am downloading the latest CM11 Nightly build here : http://download.cyanogenmod.org/?device=d2lte
P.S.
Will I bay able to go back to stock if I don't like CM11? I heard that it will brick my phone from rolling back the boot loaders. What if I restore from a nandroid backup, will that work to restore to stock without bricking my device?
With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.
audit13 said:
With a custom recovery, you can create a backup, flash your ROM, and you can restore the backup if you don't like cm11.
Click to expand...
Click to collapse
Ok thats good. Though I still have the problem of flashing CM11. It still fails on me on TWRP or Philz Touch Recovery. Any ideas on how to fix this problem?
What error are you getting? What cm11 ROM are you flashing?
audit13 said:
What error are you getting? What cm11 ROM are you flashing?
Click to expand...
Click to collapse
Never mind, found out that I had to run the factory reset in PhilZ Touch first then flash the rom. Alls good, but didn't like CM11.
Though why didn't it work on TWRP?
I had issues with TWRP flashing ROMs too. Once I switched to Philz which is based on CWM, I had no issues flashing the same ROMs that TWRP would not flash.

Flashing echoe rom & then updating to the latest stock firmware

hey guys,
i will be flashing Echoe Zen Rom v3 [2.20.40.165] which is the latest rom & will then flash the latest kernel available (Ael Zen v3.5) which was released yesterday... The only doubt i have here is if i flash this rom will be able to flash the latest stock firmware from asus? and if yes how can i flash it... I have seen people having issues with twrp & updating stuff so do i also have to edit the updater script? Please someone enlighten me on this issue of updating to latest stock rom after flashing echoe rom... I know the flashing of entire rom i.e boot.img, system.img etc with adb but is there any other way like ota or flashing directly of stock rom via twrp? i dont wanna edit the updater script & stuff everytime we get an update...
The best way back to complete stock is to use root with CWM recovery and flash the stock zip from your external SD card as the phone goes back to complete stock. Bootloader is locked again after you do this.

Flashing stock firmware without TWRP

I was trying to unlock and flash custom ROM on my Realme x2 RMX 1991 device.
I succeed to unlock the device. but still have some issues with flashing TWRP as a custom recovery.
I was thinking to flash an old version of firmware like A14 instead of my current version A16. and try to re-flashing TWRP after that.
Is it worth it? and how can I flash stock firmware without using custom recovery?
I tried to flash with regular recovery, but it's juts failed because it's older than the current firmware version.
the boot image shows up but ony for less than a second and when i try to go in fastboot its the same .... less than a second

Categories

Resources