Database Develop

Bad SBF

Hi guys!Sorry for my post but i don't know where to post.So,let's start.
First i install a sbf file from sbf room's.The process was a success.When i start the phone to look i saw i don't have the Play Store and File Manager to install a new ROM.
When i try to install the ROM i have an error:
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
E:failed to open /sdcard/update.zip(No such file or directory)
E:signature verification failed
Installation aborted.
I have a Motorola Milestone A853.It is rooted.
I need help because i don't want to go in service because i know we can fix this problem.This SBF is bat because the battery is go to 0% in just few hours.Sorry for my bother but i need much help.Thanks you!

You have to flash vulnerable recovery again.

Eiertschik said:
You have to flash vulnerable recovery again.
Click to expand...
Click to collapse
ok i will try

dragosneagu95 said:
ok i will try
Click to expand...
Click to collapse
I had made the root.Everything goes ok.My phone was rooted again.But the error with sd card persist.:crying:
I don't know what can I do....

Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?

Eiertschik said:
Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?
Click to expand...
Click to collapse
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.

dragosneagu95 said:
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take a look and reply please.

Guys do you know some answers or can i go to service?

Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.

Eiertschik said:
Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.
Click to expand...
Click to collapse
no,they didn't come
but if i install a SBF over SBF i brick my phone?I tried this solution on a Defy and i bricked.Tell me please.

You can get the stock SBFs from HERE.

Erovia said:
You can get the stock SBFs from HERE.
Click to expand...
Click to collapse
Ok but who is the original SBF?
And if I install a SBF over SBF I brick my phone?

These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.

Erovia said:
These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.
Click to expand...
Click to collapse
I will try and I'll come with news

GOD Bless You!I fix the problem with yours answers,special Erovia(your guidance was great),but all members.Sorry for my raunchy style to write but I was sad.Thanks you again!:fingers-crossed:

Gear Live 5.1.1 OTA Url

Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip

elitistphoenix said:
Grabbed this from a logcat of my freshly reset watch
https://android.googleapis.com/pack...1f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf
.zip
Click to expand...
Click to collapse
Thanks. Installing it right now. Do you by any chance have a backup of recovery partition? The one that is newer than or KNX01Q
Wohoo they included wifi support in this(unlike some other android wear watches that were promised wifi, but didn't get one with update).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sorry not at the moment

how do you install it?
EDIT:
I figured it out:
1. reboot into boot menu(samsung logo + diagonal swipe)
2. select recovey
3. use adb to update
4. adb sideload file.zip

https://android.googleapis.com/pack....signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip

any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use

What about power saving for wifi? In advanced setting is set to 120 minutes, but I don't know what does this mean: disconnects from wifi after 120 minutes?

And I don't have my charge cradle at the office.
Guess I will do this tonight!

insaned said:
any other option other than sideload? I'm having hard time with TWRP and win drivers for sideload use
Click to expand...
Click to collapse
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Follow this video https://www.youtube.com/watch?v=WSi0yuRkfPk
2. In TWRP click on install
3. Go into /sdcard/ folder in the TWRP filemanager
4. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
5. swipe and install

aligatro2010 said:
Yea, sideload on TWRP doesn't work for me too. What I did was I modified updater-script in ota zip, pushed zip file using adb into watch storage and just installed it as update.
1. Download https://dl.dropboxusercontent.com/u/36544414/updater-script
2. Open your 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip using winrar
3. Place file from 1 into \META-INF\com\google\android
4. load into TWRP and on pc do adb push 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip /sdcard/
5. In TWRP click on install
6. Go into /sdcard/ folder in the TWRP filemanager
7. click on 1e8de7cfe6d5fece253b47a727bb7f1580f31f21...
8. swipe and install
Click to expand...
Click to collapse
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."

insaned said:
Thanks for the detailed steps.
However I still get a error flashing the zip..
"Error executing updater binary in zip..."
Click to expand...
Click to collapse
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.

aligatro2010 said:
Hmm I should probably zip that updater-script as the windows might be screwing up the endlines when you save it. What is the full error?
https://dl.dropboxusercontent.com/u/36544414/updater-script.zip Here you go.
Click to expand...
Click to collapse
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
E:Error executing updater binary in 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip "
Error flashing zip '/sdcard/1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip'
Click to expand...
Click to collapse

insaned said:
Thanks.
I even deleted the file in the 1e8de7cfe6d5fece253b47a727bb7f1580f31f21.signed-sprat-LDZ22J-from-LWX49K.1e8de7cf.zip.zip and inserted your file there.
Still the same error.
will you mind upload the full zip you used and share it? Thanks for all the trouble.. I guess my watch is fighting back this update by all means!!
Click to expand...
Click to collapse
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk

aligatro2010 said:
Try this one.
https://dl.dropboxusercontent.com/u/36544414/updater-script 2.zip I've redone it from scratch. And tested it flashing.
If that doesn't work, just follow this short video I made. Note that I am using notepad++
https://www.youtube.com/watch?v=WSi0yuRkfPk
Click to expand...
Click to collapse
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch

insaned said:
Tried both methods but something still returning this error.... it is like if I was trying to inject in in other watch
Click to expand...
Click to collapse
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.

aligatro2010 said:
What happens if you try to flash the unmodified firmware file. Does it still return the exact same error or is it complaining about wrong fingerprint?
I am gonna upload my modified zip. its gonna take some time. my upload speed sucks.
Looking at your pictures, it seems that the file app_process2, on your watch, has a different checksum than what is supposed to be. So, either your have older firmware than LWX49K(5.0.2) or that file became corrupted or something else happened to it.
Click to expand...
Click to collapse
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!

insaned said:
I have LWX49K (5.0.2) so I really dunno what might happened.. or it was doing root or I don't understand..!
Click to expand...
Click to collapse
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Click to expand...
Click to collapse
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk

insaned said:
If reseting device would fiznthe file I can do it straight, but I'm not sure of that!
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I don't think it will since its located in the system partition. When you do reset it formats userdata partition.

aligatro2010 said:
Well if thats the only file corrupted, I can give you a backup of mine.
Hmm now that I think about it, I can't because I already upgraded, but I can give you the one from newer firmware and remove check for that one file in the updater-script.
Ok so find this line in your updater-script and just remove it
apply_patch_check("/system/bin/app_process32", "a92a761aef714b5e97bc2f27991d6c6d3432e0eb", "ee28188953742e905c1b20a5349a2184581e2972") || abort(""/system/bin/app_process32" has unexpected contents.");
in TWRP fist go into "mount" and make sure that "system" has checkmark in front of it.
Then get a backup of your file by adb pull /system/bin/app_process32 . Save it to a safe place
Download https://dl.dropboxusercontent.com/u/36544414/modified OTA 81/app_process32
And do adb push app_process32 /system/bin/
Click to expand...
Click to collapse
Thanks , I will trybit noe as soon as I arrive home sinxe I came to e work
Sent from my SM-G920F using Tapatalk

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64

Nice, that is what we need .. Thanks Liam

How can i load twrp? Fastboot boot command, didnt work

DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread

Not working for me get a error file is to large to download when try to flash

dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools

liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same

Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?

Not working for me. Both sims dissapear and phone keeps FC.

pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app

error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash

pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared

liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app

NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc

Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it

mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?

liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1

Great thanks!
But can we update OTA to B2 with this?

@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?

Patch boot image without using Magisk App

Hello,
I'm trying to patch my boot image without using Magisk App.(via PC) Is there any way to do this?
This is because everytime I do security update every month, I have to:
1. Download factory image
2. Unzip and get boot.img
3. Put boot.img in my phone
4. Patch boot.img with Magisk App
5. Move boot_patched.img to my pc and flash via fastboot
I find this very unefficient, and I want to automate 1~4 by just doing all the process in my PC.

Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?

Andrologic said:
Why wouldn't you install your update and before re-booting the phone go to the Magisk app and let it do the patching for you with "Direct Install" (or "Install to Inactive Slot" if you have device with dual partition)?
Click to expand...
Click to collapse
@Andrologic This is because I root for VoLTE(Voice over LTE) patch and after that, I assume that I cannot update my phone via OTA. Long ago I tried updating with OTA and for as long as I remember it failed. Ever since that happened, I usually unroot first, do an update with either sideload or OTA or factory image(very often), root again with all the steps above, and so on..

If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh

Didgeridoohan said:
If that's what you really need, just do what Magisk does. It's all on GitHub:
https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
Click to expand...
Click to collapse
Ah, this was what I was looking for. Thank you.

@Didgeridoohan Do you happen to know where I can get the essential magiskinit and magiskboot binary?
From magisk v22.0 I see that magisk core and magisk manager got merged into one, and now I can't find the latest executable. (x86 too)

They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.

Didgeridoohan said:
They're in the /lib/x86 and folder inside the .apk. If I remember correctly it should just be a matter of renaming them to magiskinit and magiskboot respectively.
Click to expand...
Click to collapse
You are talking about these "lib<binaryname>.so" files right?

Yup

Didgeridoohan said:
Yup
Click to expand...
Click to collapse
Thank you for the answer. I really appreciate it.

After update, make a boot.img backup via twrp (copy in twrp folder and rename to boot.img) patch via Magisk and flash new patched boot.img.
Os. I do not like a new method too.

Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.

Sathors said:
Thank you guys, with these ideas I have been able to write a bash script to automate the whole process of downloading the latest build of lineageos, patch it on the phone using magisk (using adb shell), and flash it in fastboot mode, without needing any user intervention whatsoever.
Click to expand...
Click to collapse
Can you share your script?

Hey @eyal1izhaki , sorry for the late reply.
You can find the script I am using here: https://github.com/NicolasWebDev/reinstall-magisk-on-lineageos
If you find any problem or have a suggestion, please tell me!

Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script

eyal1izhaki said:
Oh nice, I tried to run boot_patch.sh on my Ubuntu, didn't go well.. I'll try to run it on my samsung phone as you did.
In not running lineageos but it should be the same process.
Thanks for the script
Click to expand...
Click to collapse
https://github.com/Taewan-P/crosshatch-magisk-generator
This is my automation script FYI.
It's mostly close to an automation workflow though...

Also, you should not use the x86 binaries to patch a boot img of an aarch64 device. Flashing the mispatched img will make you boot loop the device.

i have a big dum dum poopy brain i dont know how to do anything will one of you big brain gentlemen please tell me how to patch the boot.img file with the script you guys are talking about and which app do i use and where do i use it and how do i use it. i can't use magisk because it gets stuck on the splash screen with the logo so i'm trying to patch the boot.img file without it. also will it be a problem that the boot.img file has .lz4 at the end (boot.img.lz4). aight thanks im gonna try elongating my neck by tying it to a fan with a rope.

Hi. I am sorry for bumping this thread but I am finding a solution for patching multi-model boot to add Magisk root without a phone.
Will this be possible?
I read the @Sathors script but he pushes the boot file to the android system to patch it. Can this step work on any phone or must on the exact model of the boot.img

Hi @Tungtata . If you look at the boot_patch.sh script in Magisk (https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh), in the header it says the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it seems that to work it needs the corresponding binaries, scripts and files. Maybe you can find all of these files in the Magisk repo, maybe not, in my case it seemed too much hassle to try and find out, knowing that it is working when done on the phone.
But if you really need to do that, then here is a path you can follow.
As for needing the exact phone model to patch the boot image, I don't think so because the script in itself is generic, but it depends on the other files it requires. Anyway, doing a real-life test should be quick.

Question Hi friends!

Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA

Frankie1975 said:
Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA
Click to expand...
Click to collapse
Here:
https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/

sorry not run....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
Why install the twrp since there is currently no flashed custom rom and there won't be any soon because of the mediatek soc which is little or not developed.
Have you unlocked the bootloader?

Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
There is no [recovery] partition on this phone.

yes i unlocked it, how do i recover the partition?

Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
this is A/B device it doesn't have recovery partition

Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
But why?(Again).
If it is to change rom version use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

not running

Frankie1975 said:
not running
View attachment 5609485
Click to expand...
Click to collapse
https://www.droidwin.com/fix-status-read-failed-too-many-links/

changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....

Frankie1975 said:
changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....
Click to expand...
Click to collapse
Again why would you want to install the TWRP?

I am Italian and know little English I have no reference guides for your procedure ....

Frankie1975 said:
I am Italian and know little English I have no reference guides for your procedure ....
Click to expand...
Click to collapse
use google trad https://translate.google.fr/?sl=it&tl=en&op=translate

too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..

Frankie1975 said:
too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..
Click to expand...
Click to collapse
No need Twrp to root

and how do you install the magisk?

Frankie1975 said:
and how do you install the magisk?
Click to expand...
Click to collapse
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.

thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello

Frankie1975 said:
thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello
Click to expand...
Click to collapse
Usb 3 is not recommended, I already told you on a previous post.