Hi, how are you guys?
Well, as the title says, i can not unlock the bootloader. I follow all steps to do it. I tried with SRK Tool, but after puting the bootloader code, it stays on "Waiting for device".
I have already installed Hisuite and the drivers on my pc. Hisuite do not recognise my cellphone as "connected". It always says "click to connect" or similar.
I have enabled the "developer options", but the "OEM unlock" do not appears.
Can anyone help me please?? I dont know what to do.
Thank you
Yeah this drove me fkn crazy also.
SRKTool works for everything else for me but not to unlock bootloader.
Try this (using 'Minimal ADB and Fastboot' instead of 'SKRTool') and worked for me following the instructions:
http://ministryofsolutions.com/2016/04/official-huawei-bootloader-unlock-tool.html
Also once you have
- unlocked bootloader (as above)
- installed twrp (with SRKTool)
- rooted (with SRKTool)
When rooting, it works but says could not mount data.
Same problem when I try to do a backup in TWRP
Found the reason to be because it is encrypted. Then if you change the format (as one video suggested), you won't be able to turn on your phone and will make you want to kill yourself.
pwoita said:
Yeah this drove me fkn crazy also.
SRKTool works for everything else for me but not to unlock bootloader.
Try this (using 'Minimal ADB and Fastboot' instead of 'SKRTool') and worked for me following the instructions:
http://ministryofsolutions.com/2016/04/official-huawei-bootloader-unlock-tool.html
Also once you have
- unlocked bootloader (as above)
- installed twrp (with SRKTool)
- rooted (with SRKTool)
When rooting, it works but says could not mount data.
Same problem when I try to do a backup in TWRP
Found the reason to be because it is encrypted. Then if you change the format (as one video suggested), you won't be able to turn on your phone and will make you want to kill yourself.
Click to expand...
Click to collapse
Didn´t work . It says "FAILED (remote: Command not allowed)
finished. total time: 0.016s "
Any idea?
Thank you for your answer
Good morning,
I unlocked the bootloader and rooted my Honor 5C a few months ago already, installed a TWRP and had since then no problem my phone.
However, a few days ago, I simply put my phone into my pocket, and half an hour later the screen showed a Huawei eRecovery page, without having done anything.
I then said no to whatever it was showing and proceeded to restart the device, only to get a bootloop leading me to the eRecovery page once again.
I tried to get the phone to be repaired through the eRecovery app but it says Getting package info failed each time.
I made some research and it seems like everyone is saying to flash the stock recovery and then to do the three button install with the dload folder.
Problem is, I don't know the exact reference of my phone. On the bill it says NEM-UL10 (NEM-L51), this version has a fingerprint sensor, and there are some Chinese characters followed by NEM-UL10 on the back of the phone. So, I don't know which version of stock recovery and which firmware I should use.
I can access my device through fastboot, and tried several update.app, but don't really know which one to use, and everytime it says wrong version.
The transfer from the computer to the sd card takes a long time and I don't really want to do the combination of all possible stock recoveries with all possible stock firmwares.
Could someone help me ? Try going a little bit into details as I'm not a pro, I know how to use basic commands of fastboot like flash recovery or flash boot but don't know anything about the rest.
Thank you for reading.
where you bought your device from?
thelous said:
where you bought your device from?
Click to expand...
Click to collapse
I bought it on a French website (since I'm French).
I'm trying to flash different versions using Huawei Multi-Tool, but each time it fails at writing the cust with a (remote: partition error), and with system it says (remote: sparse flash write failure).
MichelFou said:
I'm trying to flash different versions using Huawei Multi-Tool, but each time it fails at writing the cust with a (remote: partition error), and with system it says (remote: sparse flash write failure).
Click to expand...
Click to collapse
You might need oeminfo file of the version you are trying to move to
Thank you so much !
I installed the oemfile from this link https://forum.xda-developers.com/honor-5c/help/flash-european-rom-honor-5c-chinese-t3456794 and downloaded the rom accordingly.
At first the three button install told me "failed to check package content" at 50% but the only thing in the dload folder you had to have was UPDATE.APP, otherwise it won't work.
I updated to the latest version and everything is back to normal (except the fingerprint sensor which doesn't work anymore, saying Enroll failed instantly when trying to setup a new fingerprint, but I'll deal with it later).
Regards.
MichelFou said:
Thank you so much !
I installed the oemfile from this link https://forum.xda-developers.com/honor-5c/help/flash-european-rom-honor-5c-chinese-t3456794 and downloaded the rom accordingly.
At first the three button install told me "failed to check package content" at 50% but the only thing in the dload folder you had to have was UPDATE.APP, otherwise it won't work.
I updated to the latest version and everything is back to normal (except the fingerprint sensor which doesn't work anymore, saying Enroll failed instantly when trying to setup a new fingerprint, but I'll deal with it later).
Regards.
Click to expand...
Click to collapse
Great. Try doing the factory reset and finger print may work fine. Good luck
Hi !
I bought in January the nice P8 Lite 2017 and received a PRA-LX1C432 (dual sim europe no carrier).
It was with Android 7.0 and EMUI 5.0 and i wanted to root it.
I did it well, and was with the firmware PRA-LXA1C432B182 in stock and rooted with the tuto from this thread
https://forum.xda-developers.com/p8...ck-rom-huawei-prague-pra-xxxc432b182-t3727816
and uninstalled TWRP to put back stock recovery.
Later, I wanted to unroot my phone, and that's where things went wrong. I tried to do it with the superSU option and after a hard reset it was working and not rooted, but i'd still have the message "this phone can't be trust" so i tried to relock the bootloader and it did hard reset the phone again and now, i'm stuck with a phone that can send sms or go through the internet with LTE, but can't access fm, camera, google music, nfc is going on and off, calls don't work, etc... In dev options, Allow OEM unlock is greyed and I can't change anything. Phone is recognized by computer and I can acces memory of the phone.
I can hard reset it won't change, i ca also accessFastboot, or recovery or eRecovery, but in Fastboot mode it says "PHONE Unlock FRP Lock" and from my computer i can't do anything : if i try to flash twrp with fastboot command, i have the message "FAILED remote the command is not allowed", if i try to lock/unlock/relock bootloader it says "FAILED remote root type is risk".
Clearly, I don't know what to do. I'm used with rooting/unrooting smartphones from different brands (Samsung, LG, Sony, Huawei...), even though i'm far from being a master, and using Fastboot/ADB commands, but... I don't know.
If someone has any idea, I'm taking. I'm thinking about dload method but, of cooourse, I do NOT have a sdcard, so it's the last thing i would have tried from all i have seen on xda and elsewhere.
Thanks for reading and taking time to answer and help me, and sorry for not perfect english, i'm french but trying my best !
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Fr0nK said:
Run a eRecovery restore , it restore the entire smartphone to stock and also lock bootloader. Idk if this can solve your problems but i had ur same problem a days ago and i restored my phone enterely.
Click to expand...
Click to collapse
I can't, it says that it can not get package infos from server. :/
MrCrumble34 said:
I can't, it says that it can not get package infos from server. :/
Click to expand...
Click to collapse
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Fr0nK said:
If you have twrp or if you can install it in someway , i can provide to you and ominfo.img to flash via twrp in ominfo partition to restore and remove package info error.
Click to expand...
Click to collapse
TWRP is not installed, and I can't flash it in any way. Fastboot says "FAILED (remote : command not allowed)" if I try flashing recovery or system or anything. It also says "FAILED (remote : root type is risk) if I try to lock/unlock/relock the bootloader.
Ok, I'm actually trying something. I plugged the phone into my computer, and HiSuite told there was an update available for my phone, so I just clicked on it. It's doing right now, I will edit my post after it has finished (for good or bad).
EDIT : Ok, si it did work ! My phone is now on PRA-LX1C432B194, everything is working, not rooted. I relocked the bootloader with Fastboot, the command did work (guess I can root it again if I need now). But I think I'll leave it like that ^^'
Allow OEM unlock isn't greyed anymore, I came back to the original state of my phone but with an update not (yet) available in my country, no more "Device can't be trusted" message. Like if nothing had ever happened (expect it will be written PHONE Relocked).
This phone is really sensitive, haha^^
But as anyway I made it
Thanks anyway for trying to help !
Hi there!
Let me explain the complicated situation:
Fist some data: P20Pro - CLT-L09 C432 - 9.0.0.163. - Bootloader unlocked - Rooted.
The device was running Oreo and I've managed to rooted it (with TWRP) and updated it through HuRUpdater. The problem began when I updated the phone to Pie, using the same method with a newer version of HuRUpdater. It worked, kind of, but now I can't update it nor do a factory reset. Everything shows an error. The only way to connect the phone to a PC is only through HiSuite, otherwise the PC shows a "CD Drive" instead an external drive.
At first I wanted to downgrade the phone back to Oreo which I thought I might need FunkyHuawei, I contacted and send them the required information:
fastboot oem get-product-model:
(bootloader) CLT-L09
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem get-build-number:
(bootloader) :CLT-LGRP2-OVS 9.0.0.163
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
fastboot oem oeminforead-SYSTEM_VERSION:
(bootloader) :CLT-L09 8.1.0.161(C432)
They suggested some tutorials but they didn't guarantee me that it could work.
So I really don't know what to do any more. I would really like to flash the device completely deleting absolutely everything, like factory reset not but through eRecovery because it doesn't work.
May be there is someone out there with a possible solution?
Thanks in advance.
Have you tried THIS
nms247 said:
Have you tried THIS
Click to expand...
Click to collapse
I've tried so many things already that I can't remember. I will give it a shot and report ASAP.
Thanks.
nms247 said:
Have you tried THIS
Click to expand...
Click to collapse
I've posted in the thread you suggested me. Till now, after rebooting in TWRP and with the phone connected to the PC, the tool shows "< waiting for any device >" and nothing happens from there.
Do you know a method where I can flash everything through fastboot mode? And I mean EVERYTHING, I don't care if I have to delete the whole internal storage.
Never mind, after I played a little too much with the phone and bricked it... :silly:
THIS post saved my life... to say it better, saved the phone's life.
Bootloader is now relocked, but I don't care, at least I have a working phone.
Thanks.
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation
MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp