Hello, if I want to put the firmware on it with Odin, it always gets stuck on the mobile phone.
supermaus100 said:
Hello, if I want to put the firmware on it with Odin, it always gets stuck on the mobile phone.
Click to expand...
Click to collapse
The official Binary error is caused by flashing non-stock firmware like TWRP recovery. This is because your KG state is showing Prenormal ( as seen in your download mode ). To flash TWRP etc. the KG state has to be showing checking state.
From your other post about samfirm not working try using frija to download firmware
[Tool] Frija - Samsung firmware downloader/checker
* * * PLEASE UNDERSTAND WHAT YOU ARE INSTALLING TO YOUR DEVICES AT ALL TIMES AND ME AND THE DEVELOPER ARE NOT RESPONSIBLE FOR ANY SORT OF DAMAGE TO YOUR DEVICE * * * Hey Guys :) Frija is a new tool (successor of now depreciated tool SamFirm)...
forum.xda-developers.com
spawnlives said:
The official Binary error is caused by flashing non-stock firmware like TWRP recovery. This is because your KG state is showing Prenormal ( as seen in your download mode ). To flash TWRP etc. the KG state has to be showing checking state.
From your other post about samfirm not working try using frija to download firmware
[Tool] Frija - Samsung firmware downloader/checker
* * * PLEASE UNDERSTAND WHAT YOU ARE INSTALLING TO YOUR DEVICES AT ALL TIMES AND ME AND THE DEVELOPER ARE NOT RESPONSIBLE FOR ANY SORT OF DAMAGE TO YOUR DEVICE * * * Hey Guys :) Frija is a new tool (successor of now depreciated tool SamFirm)...
forum.xda-developers.com
Click to expand...
Click to collapse
ANY HELP ON THIS ONE
spawnlives said:
The official Binary error is caused by flashing non-stock firmware like TWRP recovery. This is because your KG state is showing Prenormal ( as seen in your download mode ). To flash TWRP etc. the KG state has to be showing checking state.
From your other post about samfirm not working try using frija to download firmware
[Tool] Frija - Samsung firmware downloader/checker
* * * PLEASE UNDERSTAND WHAT YOU ARE INSTALLING TO YOUR DEVICES AT ALL TIMES AND ME AND THE DEVELOPER ARE NOT RESPONSIBLE FOR ANY SORT OF DAMAGE TO YOUR DEVICE * * * Hey Guys :) Frija is a new tool (successor of now depreciated tool SamFirm)...
forum.xda-developers.com
Click to expand...
Click to collapse
ANY HELP ON MY ONE PLS
any help on this one pls
Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy A700FD Qualcomm Snapdragon variant running 5.0.2 (lollipop).
Tested Safely on following devices.
Samsung Galaxy A700FD
Why TWRP ? Why not some rooted firmware which keeps warranty safe ?
TWRP is a custom recovery. It has many more functionality than stock recovery! if something goes wrong while flashing something you can always make a backup use this recovery which can be restored when things get messed. if mess is of large extend you can always flash stock firmware.
Why new TWRP Recovery ?
The older version which was released will not be compatible with cm structure due to mount points and hence this recovery will be supportable for all custom flashing.
Instructions
Follow the instructions carefully.
Step 1 :
Install Samsung Drivers and connect your device to PC. let it install drivers and if its updating let it update. your device drivers should be perfectly installed without a single failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery
Step 3:
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7 Logo
Press vol up to confirm
Step 4:
Now that you are in Odin Mode connect your device via USB cable.
Now open Odin3 3.09 or 3.07 that you have downloaded.
If there is a pop-up like Installing ADB drivers let it get finished it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing.verify twice only these 2 are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
Credits:
TWRP Team for their awesome recovery.
@RVR for testing recovery!
XDA:DevDB Information
TeamWin Recovery Project, ROM for the Samsung Galaxy A Series
Contributors
jackeagle
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.0.2.0
Stable Release Date: 2016-03-07
Created 2016-03-07
Last Updated 2016-05-25
Downloads
TWRP Build 1
TWRP Build 2 (V3.0.0)
TWRP v3.0.2.0 (Build 3)
TWRP v3.0.2.0 (Build 4)
Changelog
Code:
27/06/2016
- Added Compatibility for Samsung Marshmallow Firmware Release
- Merged with Samsung Marshmallow kernel release
- TWRP upstream merge.
25/05/2016
- Fixed Recovery Loop Issues.
- Fixed MTP Media Transfer on Recovery.
- Added EFS Partition Backup Option
- Fixed Brightness Slider
- Updated TWRP to latest v3.0.2.0
07/03/2016
- Updated TWRP to v3.0.0
20/11/2015
- Initial Release
Reserved 2
I need a custom recovery for Galaxy A8 (A800F) please.
Thanks
How to root Galaxy A700FD and install a recovery running on lolipop 5.0.2.
Developers please go for Samsung Galaxy A7 A700FD ..
Sent from my SM-A700FD using Tapatalk
Nice keep posting about A700FD
Sent from my SM-A700FD using Tapatalk
TWRP Link is dead.
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
jackeagle said:
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
Click to expand...
Click to collapse
build 2 is invalid ,help
nukedanoob said:
build 2 is invalid ,help
Click to expand...
Click to collapse
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
and what if I can't flash because of secure boot enabled?
(in download mode there is a line "Qualcomm Secureboot - Enabled (CSB)" and "Write Protection - Enabled". I think this is the cause).
what should I do? any help appreciated.
nevermind. it was a faulty cable.
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
thanks
A7000 want to twrp 3.0.0too
来自我的 SM-A7000 上的 Tapatalk
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
works fine,just rename the file
Qualcomm Secure Boot is enabled and trying to flash recovery gives this message on phone
secure check fail : recovery
Custom Binary(recovery) Blocked by A/L
Odin says Fail
Solved: Disabled Reactivation Lock in security settings
Phone booting into recovery each time when I reboot the phone. How to come out of recovery mode boot loop?
Can i use it on my a7000?
Hello jackeagle, I ask you to continue the CM13 E5 project, I enjoyed the rom! If I can help in any way! even a my donation and my friends for you to continue the rom!
Always get kernel not seandroid enforcing .... i cannot boot to the system i just installed... just a blank screen
. .
(PM me if i made a typo)
Procedure :
Step 1 : Update to the latest software update
Step 2 : Unlock bootloader ( c.realme.com/in/post-details/1110451594350034944)
Step 3: install Magisk Manager (magiskmanager. com)
Step 4: Flash Modded Boot.img (Using Fastboot)
Code:
fastboot flash boot boot.img
To boot into Bootloder to use Fastboot
Code:
adb reboot-bootloader
Software vertion Required: RMX1831EX_11_C.16 (Release date: 11/12/2019)
Download : mega.nz/#!ZchUEQCR!-6k1AIHIyK-oIeec3BOgsXMK4PT18qnrDycM4zyKkFA
FAQ
Dose this Work?
Ans: Yes. (i own this devise and worked for me)
Will this get Updates?
Ans: Yes. Depending on feedback i might stop
Why did i post a method for rooting this devise when their are 4 other threads doing the same?
Ans: because all those other methods did not work for me.(if they do pm me i will DELETE this thread)
PM me if you have any problems or need help or if i posted it in the wrong thread (I couldn't find my devise thread)
Thx if someone could make one
DONT USE
Method 2Bootless Root Method (MTK-SU)) (No longer works (causes kernel panic after the latest update))
Advantage : you don't need 2 unlock ur devise
Credits :
magiskmanager and realme
Status : Stable
Disclamer (just for courtesy) I will help u if anything hapens
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. (realme devises will not lose thare warranty )
I have also successfully rooted Realme Q2 UI1.0 android 10, but when Q2 updated UI2.0 android 11, rooting using that old method failed. So please ask if there is a way to achieve the goal of rooting Realme Q2 UI2.0 android 11 with good results? Thank you!
Hey,
I've been trying to root my newly bought M21, but can't seem to find a working TWRP version.
Everytime I tried to load any custom OS, magisk or twrp... it just got into a bootloop or getting some vbmeta verify error.
Anyone got a guide to installing magisk on this device?
Kind regards,
Paradox1990
@paradox1990
No need to have TWRP installed in order to root phone's Android by means of Magisk.
jwoegerbauer said:
@paradox1990
No need to have TWRP installed in order to root phone's Android by means of Magisk.
Click to expand...
Click to collapse
I've tried patching the stock firmware AP with magisk through the magisk manager and flashing it to my phone... keep getting vbmeta error.
Seems to also happen with other Samsung phones, but can't get it to boot (or it goes back to odin mode or bootloop).
error verifying vbmeta image: invalid vbmeta header (6)
Is the error I'm getting while trying to boot...
Doesn't matter if I flash magisk or twrp... it's the same everytime.
Now I'm getting the OK_NOT_SIGNED (3) error.
Can still not boot into recovery or boot my phone with magisk installed.
Flashed stock firmware and will wait until there's any news on fixing this.
@paradox1990 check here: https://forum.xda-developers.com/galaxy-m30/how-to/testers-m-series-t4169511
Let me know if you are okay for testing, and I will try and get a working ODIN (until TWRP comes).
delete
Sagarking said:
Their is twrp available for samsung galaxy m21. (Mod Edit: Link removed)
Twrp for m21
(Mod Edit: Link removed)
Click to expand...
Click to collapse
With latest builds of ROM, this does not work. Few tried and nothing worked.
My phone is rooted
This for letest Samsung version ( 2.5)
First unlock bootloader
Flash this file using Odin AP
That's it now download magisk apk
Unable to attach file , link because I am new member
Contact me on telegram @Rajnaik99
paradox1990 said:
Hey,
I've been trying to root my newly bought M21, but can't seem to find a working TWRP version.
Everytime I tried to load any custom OS, magisk or twrp... it just got into a bootloop or getting some vbmeta verify error.
Anyone got a guide to installing magisk on this device?
Kind regards,
Paradox1990
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21
Disclaimer: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this recovery before flashing...
forum.xda-developers.com
and please tell me if any rom worked for you.
Hello, I am very much new in rooting. Rooted only samsung s7 edge 2019. Recenly i bought samsung m21. Software version. Ui 3.1. Kindly let me know step by step process how to root m21 android 11. Ui 3.1.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you're getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I have extracted Stock Recovery for OnePlus Nord, Currently tested in Indian Version. EU and Global users please test it if you can.
There are two methods to restore stock recovery TWRP or Fastboot
Requirements:
- Working ADB and Fastboot (e.g. Google's Platform Tools)
- TWRP Backup or Stock Recovery
Steps for TWRP:
- Download archive from AFH
- Extract the content of archive, There will be a folder named 'BACKUPS'.
- Paste 'BACKUPS' directly into TWRP folder in your Internal Storage.
- Boot into TWRP and restore the recovery partition.
- Reboot
- Profit
Steps for Fastboot
- Download Recovery image from AFH
- Open terminal in your ADB folder
- type "adb reboot bootloader"
- Copy stock recovery image you have downloaded to your ADB folder
- type "fastboot flash recovery <file-name>.img where filename is the name of img file you have downloaded.
- Reboot
- Profit
Mirrors:
TWRP Backup
Recovery Image
I have extracted the backup by booting into TWRP and backing up the recovery partition. The img file has been extracted from my device with dd command.
Enjoy.
Reserved
**Reserved**
im in PixelExperience rom i want to go back to oxygen os can i do this method? or i will use msm tools?
Did somebody check the recovery with the EU model?
Or maybe have the EU recovery....
(I want to go full stock OOS11 after the Pixel Experience)
JD00 said:
Did somebody check the recovery with the EU model?
Or maybe have the EU recovery....
(I want to go full stock OOS11 after the Pixel Experience)
Click to expand...
Click to collapse
You can do it through unbrick tool for EU region. Unbrick tool for EU is only with android 10. You can flash it firstly and after that update to android 11.
Where can I get the "unbrick tool for EU region"?
robdg80 said:
Where can I get the "unbrick tool for EU region"?
Click to expand...
Click to collapse
Here
I had just unlocked my phone's bootloader, installed a custom recovery based on TWRP, and a custom ROM (PixelExperience).
I was using the phone just fine until I restarted it into recovery,
ever since, it's been rebooting none stop
But now I have no way to access my recovery/adb/fastboot
I can only put in Download Mode
I tried flashing via Download Mode using SP Flash Tool, but I have been receiving STATUS_BROM_CM_SEND_DA_FAIL error.
Is there any way to fix it?
After trying every tool out there + potentially having infected my pc with some virus (Hopefully that's solved too), I managed to bring my Narzo 30A to life.
To anyone facing this problem : your best bet would be an after-sales services,
Otherwise, if you're as desperate as I was (This really is a last resort option, since it could totally brick the phone as far as I know), here's what I did:
> I downloaded & installed
* All required drivers MTK drivers, VCOM...
* SP Flash Tool (spflashtool.com),
* mtk_bypass_rev4 from MobileGuru4.com
* The official ROM (.OZIP format) - I could access it using Winrar
* PBRP recovery (Based on TWRP)
> I then extracted in a folder (let's call it "C:/Flash/"):
* recovery.img from PBRP
* preloader_emmc.img, boot.img & vbmeta.img from the Stock ROM
> I looked for the appropriate Scatter + .AUTH + MT6768.DA files for my device and found them on the net
> I opened SP Flash tool,
* Used the MT6768.DA, scatter and auth files I downloaded
* Ticked only preloader, recovery, vbmeta & boot and associated each one to its relevant .img file (that I previously extracted)
* I entered into EDL mode
* I opened mtk_bypass_rev4
* Chose my MT model (mine's MT6768)
* Clicked on Bypass
* Once it said the bypass succeeded, I clicked on Download on SP flash tool
* Waited till it finished flashing
* After rebooting, my bootloader + recovery were restored