Database Users

Recovery lost

I need help guys because i lost my twrp recovery while flashing the xenon rom. The problem is now my phone is also not detected in adb devices in my laptop. I am running windows 10 i had installed twrp from this laptop. When ever i connect and give command ADB DEVICES the it doesn't show any devices found. I had installed all the drivers. My phone is running in the xenonhd rom. Pls help me how i can install twrp and how to correct adb.
Sent from my Lenovo A6000 using XDA-Developers mobile app

Lenevo A6000 Unbrick/Fix For Any Problem
It's common since, when modified, the A6000 doesn't have a way to directly boot into recovery without a System or ADB command (Power Hold > Reboot > Recovery and "adb reboot recovery" respectively). However you can always boot into Download mode which acts as an emergency subsystem at any time. Have a quick guide on how to do that and you'll be flashing away custom ROMs again in no time.
(Optional but recommended steps will be market with an asterisk (*))
Disclaimer: You are doing everything out of your own free will and volition. I am in no way responsible to any potential damage you might cause to your device. This can occur in cases of not following the guide properly.
Below is the fix for problems when the phone has no OS to reboot from. In case of Xenon which is rooted, follow this:
Easy Guide
(This is for when a phone already has an OS to boot from)
1. Open Terminal Emulator
2. Write
Code:
su
reboot recovery
(On any Superuser permissions pop-ups press Grant.)
3. Follow Steps 4 and 5 from the guide bellow.
Downloads
If you are on Kitkat (4.4.X), Download This (Mirror)
If you are on Lolipop (5.X.X), Download This (Mirror)
If you are not sure, download both and try both, no damage should be done.
[Source]
Instructions
1. Download all the prerequisite files.
2. Power Off Your Phone by removing the battery.* (See Note 1)
3. Hold the Volume Down and Power keys until the phone vibrates once and the Lenovo screen appears. At the bottom it should say "Powered by Android" and under it some small Chinese letters and "Power key long press can reboot phone". (See Note 2)
4. Extract the downloaded ZIP files anywhere you want. You should end up with a "TWRP" folder.
5. Open that TWRP folder and run "Boot-TWRP_A6000.bat"
6. If everything went well, you should be in TWRP recovery. Flash your desired ROM following the instructions from their thread, and everything should now be fine. (See Note 3)
Notes
1. I have noticed that sometimes my phone will not recognize that it's in Bootloader mode and will try to boot normally after a few seconds along with the fastboot not recognizing it. Theory: it doesn't shut down completely when rebooted via Holding the Power button, and tries to boot like nothing is wrong. I don't have a concrete fix, the best i can offer is to try different button combinations. (Vol. Down+Power / Vol. Up+Power / Vol. Up+Vol. Down+Power)
2. If you get the problem described in Note 1 do steps 4 and 5 before step 3. The .bat script will wait for the phone, as soon as it detects the Bootloader it will do it's job.
3. If something went wrong, leave a reply, I'll see if i can guide you through it. Remember to follow instructions carefully!

i had a simple sol....
Just boot into bootloader by Press n hold vol - an power ... den do wht u r doing .. Connect cable .. to pc.. n do the command in cmd.. That it

I have simple method
1. First root with kingoroot it is on click root method.
2.then install rashr
3.then flast twrp recovery img
4.then reboot to recovery.
---------- Post added at 03:56 PM ---------- Previous post was at 03:50 PM ----------
It is link for kingoroot
https://root-apk.kingoapp.com/kingoroot-download.htm
Download rashr via play store

I was totally in awe when my phone won't reboot to to recovery and download mode even tho i can reboot system normally and after I flash some recoveries all of them bootlooped my phone but that fix by AXAzor completely worked. Very huge thanks to @AXAz0r

blaspheme000 said:
I was totally in awe when my phone won't reboot to to recovery and download mode even tho i can reboot system normally and after I flash some recoveries all of them bootlooped my phone but that fix by AXAzor completely worked. Very huge thanks to @AXAz0r
Click to expand...
Click to collapse
Glad to hear that, cheers

flash twrp using flashify,rashr

----- Root Moto M S356 Android 7 -------

Hi guys,
I have started this thread so that you guys can root your moto M XT_1663_S356 andriod (7.0)
First of all i'm not responsible if your phone bricks burns or dies.
A big thanks to VVizard from lenovo RU forum with out him, it was not possible.
Thanks to Chainfire for the SuperSu.zip
To check Build number go to Settings -> About Phone-> Build number
Note -
1 - This only works for Moto M which is having build number XT1663_S356_170621_ROW. If you are on any other build number then please don't proceed.
2 - All the files are attached
3 - Install all the Motoral drivers and Minimal and adb folder.
4 - Following link contains all files needed to root the phone.
https://drive.google.com/file/d/0B3eDb0dWRU-uUjk4ZS1tdFpRR1U/view?usp=sharing
Rooting Moto M phone is divided into 3 Parts
1) Unlocking BootLoader
2) Flashing TWRP
3) Flashing SuperSu.zip
unlocking the bootloader
Note - This will wipe out all the data hence take a backup before unlocking boot loader
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot oem unlock
12 - Check your phone you would have written"do you really want to unloock bootloader ? "(something like this). Just select yes using volume up and down button and press power button to confirm it .
13 - Congrats your bootloader is unlocked
Install TWRP
Note - You should have your bootloader unlocked before proceeding.
Copy the boot_XT1663_356.img and TWRP_Moto_M.img to Minimal adb folder
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot flash boot boot_XT1663_356.img
12 - To flash the recovery, Type the command
fastboot flash recovery TWRP_Moto_M.img
13 - Congrats! you have successfully installed TWRP.
Rooting Phone.
Note -
You should have your bootloader unlocked.
You should have TWRP installed.
You should have supersu.zip copied in your phone.
1 - Switch off your phone. Now press volume down + power button till phone vibrates. Once it vibrates release the power button you should see android logo.
2 - Now with the help of volume up and down button select 'Recovery mode' and press power button.
3 - TWRP should start up.
4 - Select 'Allow Modification' and proceed.
5 - Select 'Install' and then select the 'SuperSu.zip' file and flash it.
6 -Restart the Phone.
7 - Congrats! your phone is rooted.
Note -
I have tried all this steps and have successfully rooted my phone i'm not responsible for any damage.
I have not build the boot_M_S365/ img file this is done by VVizard and really very thank full to him.

I am making a video on this!

Method Issues
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?

manandua01 said:
Thanks bro, I will give you credits ^_^
Click to expand...
Click to collapse
Cool!

manandua01 said:
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
Click to expand...
Click to collapse
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.

TWRP Recovery
akash.mahadeshwar said:
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
Click to expand...
Click to collapse
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?

manandua01 said:
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
Click to expand...
Click to collapse
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.

akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)

manandua01 said:
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
Click to expand...
Click to collapse
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen

akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
EDIT: Here's what was on my cmd after flashing the recovery http://prntscr.com/ft3t1l

manandua01 said:
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
Click to expand...
Click to collapse
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..

akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6

manandua01 said:
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
Click to expand...
Click to collapse
Ext_sdcard folder is ur memory card folder and sdcard folder is the internal memory folder in twrp

BAM!
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------

I really thank you for this great effort
all things went good but I had a problem that I didn't find the SuperSU-v2.82-201705271822.zip although I am sure that I put it in the internal memory
please help

Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware

pdf5 said:
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
Click to expand...
Click to collapse
May I have the firmware file, just in case? Is it ok if firmware country code doesn't match? Do you get imei?

any idea? when image for new build will be released?

rajesh280392 said:
any idea? when image for new build will be released?
Click to expand...
Click to collapse
Well, yes ... The new boot.img for removing encryption. Especially for post-OTA updating to XT1663_S364_170803_ROW.
boot_XT1663_364.img

Does anyone know how to keep your Moto M rooted even after updating to the new security update of 7.0? Do we just flash the new .img file or what? Kinda newb here

Android 7.1.1 Doogee X5PRO

I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hi, and thank you, I already had downloaded the BETA3 version from needROM.com but it seems this is updgraded
---------- Post added at 06:35 PM ---------- Previous post was at 06:33 PM ----------
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?

I've been using beta4 (and beta3 previously) for months and quite like them. Also, since the original factory rom is filled with adaware, isn't as up-to-date with Android's security patches and doesn't pass SafetyNet, you're gaining a lot and not losing anything switching or rooting for that matter.
Though I still prefer magisk over rooting since it's more secure and more than enough for adaway.
juancarloscuba said:
Just a question, I have to use the Flashtool to flash the firmware and after that the TWRP and Supersu options?
Click to expand...
Click to collapse
You can but you don't have to. I had a problem flashing beta4 and twrp at one go but booting the phone once with just beta4 and then powering off and flashing twrp and\or rooting afterwards solved that.
Btw, the dev is developing gesture modules for the kernel (built-in beta4) and an app to go with them: http://getbest.ru/kernel_gesture.htm I didn't find the feature useful enough to keep around but it works as advertised and, once again, magisk was enough.
Overall, the rom is an absolute must as far as I'm concerned and I wouldn't be using this phone if it wasn't available. It would have been nice if the dev could keepup with android's patches better but seeing how he's doing a better job than doogee and for free I can't really complain.

Do the camera and fingerprint work?

Hi. I wish to give my really thanks to the developer of this rom.
It solve my problems:
Stock rom R16:
sim card WIND (IT) poor 4G/LTE reception
sim card VODAFONE (IT) no 4G/LTE reception
(tested switching 1-2, various city zones)
This Rom:
both full 4G/LTE reception!!
M.A.

Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?

****_ve said:
I have searched, found and tested this rom.
It is a beta but it works very well, I leave the links of the original web where all the information of download and installation is.
I hope this humble contribution helps you.
web : http://getbest.ru/doogee_x5pro_nougat_beta.htm
TWRP : https://drive.google.com/file/d/0B3nYb3vN0P9VakpJWVU1Unh1NGc/view?usp=sharing
Flash Tool Firmware x32 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Flash Tool Firmware x64 : https://drive.google.com/file/d/0B3nYb3vN0P9VVGZvZlVIeEdQcG8/view?usp=sharing
Super SU : https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!

The Seeker said:
Hello Maria and thanks for your experience.
What can you say to me about the fingerprint and camera functionality?
Do they work fine on this rom?
Click to expand...
Click to collapse
Hi.
My phone (X5pro) hasn't fingerprint reader.
The camera seems to work in normal way.
M.A.
P.S.: May be it depends by my phone, but sometimes touch is not reponsive; I have to push the power button ("stand-by") and push it again to have normal touch response.
---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------
Racxie said:
Can you please assist me with flashing this ROM? (either 32bit or 64bit) - I've tried using the Flash Tool guide, but with 32bit the clean install scatter file does nothing, and with 64bit the clean install scatter file comes up with error: "chip type not match!! target efuse value: 0xa4020000"
I've tried with and without battery, I have installed Android USB driver, and I've followed this guide: https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Please help!
Click to expand...
Click to collapse
The flash guide you linked is the right guide.
What exact model of phone you have?
Does the scatter and other files are in the same folder? (unzipped, you know).
Does the flashtool give any error message with the 32bit version?
Regards
M.A.

I tried both the 32bit and 64 bit versions of this rom, it's pretty good for a beta. However I had a problem with the screen going dark while using it and once the screen inverted colours randomly. Has anyone else had this problem with this rom? I'm currently using the android 6 stock rom but would love to get 7.1.1 working perfectly.

installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
Flashed from ubuntu linux 16.04:
Download Only option (should I have choosen Firmware Upgrade?)
Scatter-loading File MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (should I have choosen MT6735M_Android_scatter.txt?)
I had the bootloader locked in development options (had it to be open?)
I also had USB debugging ON
Any tips?

xe7um said:
installed with SP flash tools x5pro-7.1-x32-BETA4 from a stock kernel 6.0 (R16)
with no luck. At booting snowcatPDA logo shows for a while and continuously reboots.
.....
Any tips?
Click to expand...
Click to collapse
Hi.
Now I'm at home.
Tomorrow morning, when I'll be at office I'll write down steps by steps I did.
(home... office..., reverse of natural manner, because I do all my mobile hobbies at lunch pause; at home PC is used by others )

Hello, here I am.
The follows are the steps, more or less, that I did.
(maybe you already did some of these)
1-Start from official R16 ROM
2- Developer option
#a. Enable USB debug​#b. Enable OEM unlock​
3- Security: allow unknown origin installation
4- Unlock bootloader
#a. Connect in fastboot, from ADB command mode:​type: adb reboot-bootloader ___ (Wait 1-3 second)​type: fastboot devices ___ (verify device is detected)​#b. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: yes​= unlocked: no​#c. unlock bootloader​type: fastboot oem unlock ___ and you get​-> start unlock flow​---> on screen appear:​vol UP=Yes; void warranty, clear ALL data​vol DWN=no; no unlock​Press Vol UP​#d. verify bootloader unlock status​type: fastboot getvar all ___ and you get​= warranty: no​= unlocked: yes​#e. May be phone restart​
5- shut down phone ___ AND ___ get out battery
6- Flash phone with
MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt​as per normal way (You know this , after some trying...)​
7- WITHOUT starting phone, ___ Flash TWRP with
MT6735M_TWRPx32_scatter.txt (or the 64, according to the ROM you flashed)​
9- Put battery in ___ AND___ start in TWRP recovery
#a. hold Vol Up, press ON button until appear a micro menu, release buttons​#b. choose recovery with Vol Up and confirm with Vol Down​
10- in recovery, choose wipe, and on bottom of the screen slide for factory reset
11- on TWRP main, choose reboot, power off
12- get out battery for some seconds
13- get in battery and start up (It can take a lot, may be leave the phone connected to main)
This is what I did (if I remember all the single steps...)
Try and report to us.
M.A.

Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo

xe7um said:
Nope!, in step 9 when trying to start in TWRP recovery I get a continuous bootloop showing SnowcatPDA logo
Click to expand...
Click to collapse
Hummmm....
It seems won't go in recovery mode, I think.
Try this:
1- flash entire stock ROM
(may be take this ===http://www.doogee.cc/bbs/viewtopic.php?t=29=== just in case)
2- start phone normal, up to home screen (so the phone is as just brougt)
3- power off and try to enter stock Recovery
If it works (and your bootloader is unloked) then try this
Connect phone to PC in fastboot
and enter
fastboot devices (I do this each time, just in case PC don't detect phone)
fastboot boot recovery.img
where recovery.img is your TWRP
The phone should start in TWRP recovery
The fastboot boot recovery.img command
send recovery (kernel?) image to temp phone folder/ram
and boot from that.
It unaffect normal rom/recovery.
By this step, we check If your phone accept this TWRP and sort out some possible troubles.
M.A.

when doing 'fastboot boot TWRP-3.1.1-X5PROx32.img' I get:
USB transferring...
USB transmission OK
and doesn't reboot into recovery but it boots normally
since I'm doing this from stock kernel R16 I wonder whether it's 32 or 64 bits
However I've found recovery-twrp-3.2.0-git-20171204.img that boots!. But I don't have scatter file, only .img! This recovery is from Lineage 14.1, but since this custom ROM installs from TWRP there is no need of scatter file

I've found another TWRP that boots with fastboot boot img: the TWRP recovery for 6.0 in needrom. This one has a scatter file

xe7um said:
I've found another TWRP that boots with fastboot boot img: https://www.needrom.com/wp-content/uploads/2016/12/TWRP_DG_X5Pro.rar
Click to expand...
Click to collapse
I get this error:
Needrom do not authorizing, the links referred by another website for download the ROMs.
The link must obligatory be clicked from of Needrom.com
Click to expand...
Click to collapse
Can you please link it correctly so we can download it?

The Seeker said:
I get this error:
Can you please link it correctly so we can download it?
Click to expand...
Click to collapse
Hi.
You have to select the file direct from the Needrom site.
www.needrom.com
(up)categories-doogee
on the right, click: Serial X
again, on the right, click: X5pro
and select the TWRP you desire.
(second line, second from left)
(click on "TWRP DG X5Pro (977 dls)")
Regards
M.A.
P.S.: even the link is
https://www.needrom.com/server/download.php?name=/2016/12/TWRP_DG_X5Pro.rar
you have to download from the site.

I'll try all this at the weekend, but my two cents are that it won't work. At first attempt I flashed BETA4 with MT6735M_Android_scatter-WIPE-CLEAN_INSTALL.txt (so no need to enter recovery and wipe cache/Dalvik) with a bootloop result.
My guess is that there are different ROM versions of X5 pro, and newest are incompatible with SnowcatPDA 7.1.1 firmware. Will see in a few days...

As I was suspecting I get a bootloop after logo. Now the question is: Is there a stable custom ROM (7.1 or newer) that I could use daily instead of MM 6.0 (R16) stock ROM?

5S/5G Roms and Root Mega thread [Updated November 2022]

Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________

TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.

Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated

josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)

Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear

As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.

Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.

Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.

I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks

josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.

josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img

sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need

Is it ok to flash Eu rom to my NA/asia rom?

After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please

Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.

Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.

sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?

josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock

josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock

After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed

[HOWTO]/[ROM] [UNOFFCIAL] How to Flash Lineage OS 19.0

Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.

Reserved 1

Reserved 2

Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"

exault said:
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
Click to expand...
Click to collapse
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers

DerTopher said:
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
Click to expand...
Click to collapse
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.

ALL sensors ok ?
Fingerprint ok ? In this ROM

exault said:
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
Click to expand...
Click to collapse
Sorry to hear mate. Unfortunately I cannot hell you solve this issue. There is a telegram channel for custom roms on the A51 with many motivated people. One of them might have the answer you need!
See: https://t.me/samsunga51
If you find it, please post it, so others can profit from it. With your agreement I would also like to add info about the solution - should you find it - to my initial post.
hacker812c said:
ALL sensors ok ?
Fingerprint ok ? In this ROM
Click to expand...
Click to collapse
Don't know about fingerprint as I do not want to provide biometric data to my phone. Maybe someone else using the ROM can answer this; Or you, if you decide to flash it post your results.
Apart from that I have not had any problems with the ROM apart from the following:
-The resulotion of the native lineage camera app is not satisfactory. When I find an app that works better, I'll let you know.
- Restarting the phone after empty battery requires a soft reset sometimes (power+vol -)
-> A solution to this problem might be given in this post. Will try it later.

Thank you, @DerTopher , but unfortunately the link to your LOS file does not work any more. How do I get the file now?

THIS GUIDE ONLY WORKS ON ANDROID 12!!!
sunnyy15 said:
I have concluded all my experiments, and now I can confirm that the "twrp-a51-3.5.0_10-1_ianmacd.tar" on this website only works for Android 10 as instructed by Admin. This does not for Android 11. For Android 11 you have to flash a different file called "Twrp+vbmeta_A11.tar". Details are given in the following link: https://forum.xda-developers.com/t/...-sm-a515f-one-ui-3-0-dub1-android-11.4231543/
Click to expand...
Click to collapse
@DerTopher , please change your OP to specify that this guide ONLY works for Android 12. I just bootlooped my device when trying this on Android 10 stock firmware
See this excelent post for more info: https://forum.xda-developers.com/t/...-ui-2-5-ctj1-android-10.4213443/post-84750027

Anyone knows how to remove the native SU, so that magisk doesn't complain about "abnormal state" su file ?

when i flash something in twrp i have an error failed to mount '/odm4 no such file or directory Can some help me please i am stuck here

DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS

dmudo said:
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net

i have a question
in step 3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
i try to flash chondoe and i tried to add de system.img, and it prompt me to what partition
This are the partitions that apears to me
- Boot
- DTBO Image
- Optics Image
- Prism Image
- Recovery
- Param
- VBmeta Samsung
- VBMeta Samsung
- Super (system vendor product odm)
Does anyone know where ?

DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51​
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.​1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number​1.2. Enable USB debugging in Developer Options​1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...​1.4 After triggering OEM unlock option shutdown your phone.​1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.​1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!​1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.​
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.​When flashing is complete hold Vol - and Power until reboot.​Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.​
3. Actual Flashing:
3.1. Necessary Files:​Make sure to load all files necessary to your SD before flashing:​ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)​​As for the LOS Image I used this file here, which already includes gapps:​lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img​​If you don't want gapps pick an image that says "BvS" instead of "bgs"​​3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"​
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.3.8. Reboot​
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
3.3.7 format data or wipe?