Pre requisites:
Unlocked bootloader
adb tools installed, I used These
The dirty:
Download the latest TWRP(3.0.2-1) Here
Download the latest SuperSU Beta Here I used 2.76-2 (for systemless root)
Put your phone in Bootloader mode (VolDown+Power)
Connect phone to your PC
Via ADB, and type fastboot flash recovery <path>/twrp-3.0.2-1-angler.img
- If you do not want to flash it permanently, just "fastboot boot <path>/twrp-3.0.2.1-angler.img".
- Also, if you flashed it, and you want to go back to stock recovery, you'll have to wait *for now* until the NRD90M factory image is uploaded to https://developers.google.com/android/nexus/images, then it can just be extracted and fastboot flash'd...
Select boot recovery from the little menu
It will ask for your pass/pin, enter to access. The new TWRP allows you to.
Once inside, proceed to install the SuperSU zip you downloaded in step 2.
Thanks!
Can you decrypt phone using this method? I have crypted 7.0 phone with root but lost TWRP when update crypted all the data. Would be quite nice to have it decrypted without wiping data.
Pyrres said:
Can you decrypt phone using this method? I have crypted 7.0 phone with root but lost TWRP when update crypted all the data. Would be quite nice to have it decrypted without wiping data.
Click to expand...
Click to collapse
You can't. You need a kernel that doesn't enforce encryption and you need to format userdata.
Nexus 6P with Chroma rocks!
CyberZeus_Viva said:
You can't. You need a kernel that doesn't enforce encryption and you need to format userdata.
Nexus 6P with Chroma rocks!
Click to expand...
Click to collapse
I have ElementalX as my kernel. But what about the stuff I keep reading about that newest TWRP could decrypt data? Does it work or can it be used in this instance?
Pyrres said:
I have ElementalX as my kernel. But what about the stuff I keep reading about that newest TWRP could decrypt data? Does it work or can it be used in this instance?
Click to expand...
Click to collapse
Newest TWRP decrypts data on the fly but doesn't decrypt permanently. Do you get the difference?
Nexus 6P with Chroma rocks!
CyberZeus_Viva said:
Newest TWRP decrypts data on the fly but doesn't decrypt permanently. Do you get the difference?
Nexus 6P with Chroma rocks!
Click to expand...
Click to collapse
Does this mean it can be used with crypted phone as it can decrypt the data it needs or am I missing how it works.
Pyrres said:
Does this mean it can be used with crypted phone as it can decrypt the data it needs or am I missing how it works.
Click to expand...
Click to collapse
I can't make myself clear... TWRP decrypts data in memory leaving your data crypted. Got it?
Nexus 6P with Chroma rocks!
CyberZeus_Viva said:
I can't make myself clear... TWRP decrypts data in memory leaving your data crypted. Got it?
Nexus 6P with Chroma rocks!
Click to expand...
Click to collapse
Yes and no . Basic question, does it work when the phone is crypted or not? Can I have a phone that is crypted and still use TWRP?
Pyrres said:
Yes and no . Basic question, does it work when the phone is crypted or not? Can I have a phone that is crypted and still use TWRP?
Click to expand...
Click to collapse
Yes. But that phone will remain crypted
Nexus 6P with Chroma rocks!
CyberZeus_Viva said:
Yes. But that phone will remain crypted
Nexus 6P with Chroma rocks!
Click to expand...
Click to collapse
Thanks, but I will still lose all my data when installing or can I now keep all my data and just install TWRP as I have already once installed it or does it matter in my case?
Pyrres said:
Thanks, but I will still lose all my data when installing or can I now keep all my data and just install TWRP as I have already once installed it or does it matter in my case?
Click to expand...
Click to collapse
Installing TWRP doesn't wipe data
Nexus 6P with Chroma rocks!
Pyrres said:
Thanks, but I will still lose all my data when installing or can I now keep all my data and just install TWRP as I have already once installed it or does it matter in my case?
Click to expand...
Click to collapse
You won't lose your data, I didn't lose mine.
TWRP comes and decrypts on the fly, because your password/pin matches the one you set up on the OS; after allowing it to decrypt, you can flash whatever you want.
The decryption is not permanent, meaning your phone will still be crypted, as in; no one will decrypt your data unless you give them the access.
There is no need to flash boot IMG?
McQueefus said:
There is no need to flash boot IMG?
Click to expand...
Click to collapse
I didn't flash a modified boot image previously, when I flashed SuperSU, it took care of patching that for me.
Worked like a charm, I was even able to edit the build.prop and enable tethering. You Sir, are awesome!
I'm n Android N with locked bootloader. I have to unlock the bootloader,then install TWRP then format user data to decrypt and flash su via TWRP? Is that order correct? Or any suggestions please?
Dhanabalan said:
I'm n Android N with locked bootloader. I have to unlock the bootloader,then install TWRP then format user data to decrypt and flash su via TWRP? Is that order correct? Or any suggestions please?
Click to expand...
Click to collapse
The steps are right on the first page, first post.
McQueefus said:
Worked like a charm, I was even able to edit the build.prop and enable tethering. You Sir, are awesome!
Click to expand...
Click to collapse
How?
Dhanabalan said:
I'm n Android N with locked bootloader. I have to unlock the bootloader,then install TWRP then format user data to decrypt and flash su via TWRP? Is that order correct? Or any suggestions please?
Click to expand...
Click to collapse
1. You have to unlock the bootloader, which wipes your data.
2. You have to choose wether you want to be encrypted or not, if you do not want an encrypted device you can follow the other guide in the topics list.
3. If you do choose to go encryped, boot once, setup your pass/pin
4. Reboot back to bootloader, install TWRP
5. Boot to Recovery (twrp), input your pass/pin setup on step 3
6. flash SU via TWRP.
McQueefus said:
Worked like a charm, I was even able to edit the build.prop and enable tethering. You Sir, are awesome!
Click to expand...
Click to collapse
Sweet, man!
Related
http://www.pocketables.com/2016/08/official-android-nougat-released.html
Pulled directly from my device and uploaded to my AFH site.
https://drive.google.com/open?id=0B0OpOqUNqeKkb19UbGxBV2NPc28
Stock, decrypted boot image, w. Verity disabled.
What version of android where you coming from?
spunks3 said:
What version of android where you coming from?
Click to expand...
Click to collapse
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
digitalhigh said:
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
Click to expand...
Click to collapse
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Deadlights said:
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Click to expand...
Click to collapse
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
What steps did you follow to get TWRP and root ?
So how is OTA different from full image?
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
MRL3GS said:
What steps did you follow to get TWRP and root ?
Click to expand...
Click to collapse
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Deadlights said:
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
Click to expand...
Click to collapse
Yep, /vendor is included, as well as updates to bootloader, etc.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It does not encrypt if you were not previously encrypted, this is the biggest difference
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
When i try to setup pay I get "android pay cant be used" :S
MRL3GS said:
When i try to setup pay I get "android pay cant be used" :S
Click to expand...
Click to collapse
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
digitalhigh said:
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
Click to expand...
Click to collapse
Thanks all working now
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
Working great for me! Thanks again man!
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Worked for me Thank you!!!! Still kept super su and twrp!!!
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
hutzdani said:
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Click to expand...
Click to collapse
Flash the TWRP image file from TWRP? And what is the modified boot image?
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
Click to expand...
Click to collapse
Me everything works fine tho just i cant get root to wrk the app keeps freezing on me can't grant root?
Sent from my Nexus 6P using Tapatalk
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Hi mates, here you have the latest LEX727USA update for our LEX720 devices.
It´s the original stock not modified, you can make a custom rom if you want.
If you have the LEX727 you only need to change a setting with a text editor in "System/Build.prop":
-persist.radio.multisim.config=dsds
to
-persist.radio.multisim.config=NA
its simple.
Rom:
-EUI5.8.21s(Stock)
Install:
-Twrp or custom recovery
-Wipe data,cache, dalvik and system
-Install the Rom
-Reboot to system
No problem with the fingerprint reader?
Because on the rom of Steve, the reader was not recognized.
meuhmeuh51 said:
No problem with the fingerprint reader?
Because on the rom of Steve, the reader was not recognized.
Click to expand...
Click to collapse
No problem with nothing
OK, thank You.
meuhmeuh51 said:
OK, thank You.
Click to expand...
Click to collapse
:good:
Thanks for the rom, everything perfect only problem I'm having and that in the twrp is asking for password has some way to solve?
gersonrsj said:
Thanks for the rom, everything perfect only problem I'm having and that in the twrp is asking for password has some way to solve?
Click to expand...
Click to collapse
If I say no nonsense, it is that the rom of the united states is encrypted. Me, i erased everything with twrp, and then installed the rom.
meuhmeuh51 said:
If I say no nonsense, it is that the rom of the united states is encrypted. Me, i erased everything with twrp, and then installed the rom.
Click to expand...
Click to collapse
I've done this, but it's always back to rom and very good, but if you have an update, it's impossible to use
gersonrsj said:
I've done this, but it's always back to rom and very good, but if you have an update, it's impossible to use
Click to expand...
Click to collapse
Even using otg via twrp?
meuhmeuh51 said:
Even using otg via twrp?
Click to expand...
Click to collapse
I do not know if it works ota with twrp, I'll put the original recovery and wait for the next update
What language?
gersonrsj said:
Thanks for the rom, everything perfect only problem I'm having and that in the twrp is asking for password has some way to solve?
Click to expand...
Click to collapse
I think that you have installed the latest version of twrp wich make problems with encrypted data.
- Install the boot.img via fastboot (fastboot flash boot boot.img)
-Format data partition via fastboot (fastboot format userdata)
-Remove the latest twrp and install the old (fastboot flash recovery twrp-3.0.2.img)
I have no problem with that twrp.
villarleg said:
I think that you have installed the latest version of twrp wich make problems with encrypted data.
- Install the boot.img via fastboot (fastboot flash boot boot.img)
-Format data partition via fastboot (fastboot format userdata)
-Remove the latest twrp and install the old (fastboot flash recovery twrp-3.0.2.img)
I have no problem with that twrp.
Click to expand...
Click to collapse
Thanks, I got it by installing the old twrp
kixx22 said:
What language?
Click to expand...
Click to collapse
Default would be English.
Hello, I am going to flash this via twrp soon. But one thing I need to know, can I flash supersu 2.79 on this? Because of kernel tweak.
crazy1990 said:
Hello, I am going to flash this via twrp soon. But one thing I need to know, can I flash supersu 2.79 on this? Because of kernel tweak.
Click to expand...
Click to collapse
Yes, you can flash the latest SuperSU 2.79 SR3 (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip) normally without issue
bayad said:
Yes, you can flash the latest SuperSU 2.79 SR3 (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip) normally without issue
Click to expand...
Click to collapse
has anyone tried to root his phone with this. I am new at flashing things and i don't want to break my phone
mertsamet said:
has anyone tried to root his phone with this. I am new at flashing things and i don't want to break my phone
Click to expand...
Click to collapse
Yes, I flashed my Le Pro 3 with this SuperSU version many times without problem
I wanted to ask a question: this ROM, compared to the overall performance (including fuel consumption) of the 20s, how are you? The translation in some languages I know not be perfect, but it does not matter. What they would press me to know is whether it is worth abandoning the 20s for this stock. Thank you all for the answers.
PS: excuse for my very bad english
Sent from my Le Pro3 using XDA Labs
where can i get a 21s rom for 727 without the modified build.prop? it's annoying me that the phone is thinking that he's 720
Hello! I just updated to Android Pie and i've been wondering if there is any way to root the phone. Any help would be SUPER appriciated! Thanks!
Sure it is possible. With Magisk..
bb2k22 said:
Sure it is possible. With Magisk..
Click to expand...
Click to collapse
And how do you flash it?
borksek said:
And how do you flash it?
Click to expand...
Click to collapse
Take the boot.img out of the firmware package and transfer it to the phone. Install Magisk Manager, open it and click install.
Chose "patch boot image" option. When it's done, transfer "patched_boot.img" to pc and use fastboot to flash.
Code:
fastboot flash boot patched_boot.img
tys0n said:
Take the boot.img out of the firmware package and transfer it to the phone. Install Magisk Manager, open it and click install.
Chose "patch boot image" option. When it's done, transfer "patched_boot.img" to pc and use fastboot to flash.
Click to expand...
Click to collapse
Why not with twrp just flash zip?
borksek said:
Why not with twrp just flash zip?
Click to expand...
Click to collapse
I didn't wanna format data at the time to be able to mount it in TWRP, which is needed for flashing magisk since it writes to /data/adb.
tys0n said:
I didn't wanna format data at the time to be able to mount it in TWRP, which is needed for flashing magisk since it writes to /data/adb.
Click to expand...
Click to collapse
Why not just decrypt
borksek said:
Why not just decrypt
Click to expand...
Click to collapse
I tried a few zips for that when I was on O, but with no success.
There's more ways for decryption to try, like your fstab edit, but I would have to format data anyway.
Otherwise it won't boot after disabling forced encryption, because the data itself is still encrypted and won't be decrypted on boot.
tys0n said:
I tried a few zips for that when I was on O, but with no success.
There's more ways for decryption to try, like your fstab edit, but I would have to format data anyway.
Otherwise it won't boot after disabling forced encryption, because the data itself is still encrypted and won't be decrypted on boot.
Click to expand...
Click to collapse
Hello Tys0n, can you please help me with bootloop? I tried to install a magisk module and my phone bootloop. Please help me I just got my phone. Step by step i beg you.. I don't want to lose the phone..
Edit: nvm i fixed it by flashing stock rom
Bro
My Mi 8 Lite had stock, rooted (Magisk) MIUI Oreo and I dirty flashed MIUI Pie with TWRP 3.2.3. It booted up again with no problems and everything works but when I boot into recovery it now asks for a password to decrypt the data partition. Needless to say, the PIN for unlocking the screen is not accepted by TWRP. I'm hoping I won't need to wipe the data partition to fix this. Any ideas?
Thanks
<bump> anyone?
Sent from my MI 8 Lite using Tapatalk
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
chan200606 said:
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
Click to expand...
Click to collapse
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
dwl99 said:
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
Click to expand...
Click to collapse
I had the same problem (TWRP asking for password to decrypt data partition) and I have the 1003 version. So I am going to flash 0121, 0212 or 0330. Which do you recommend?
0330
Sent from my MI 8 Lite using Tapatalk
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
This device has 3 different touchscreen panels (that I know of) and one of them is not fully supported. Which seems to be the one you have. To fix the problem the recovery needs some additions on source and then compiled. I suggest connecting to a pc and copying what you need off the internal storage and then use a recovery that your touchscreen works with and format the data partition using the option that asks you to type yes. This will remove encryption and allow you to access data no matter what recovery you use.
Maybe it's a stupid question bud wat is soue8and ?
tuytel said:
Maybe it's a stupid question bud wat is soue8and ?
Click to expand...
Click to collapse
My arthritis is bad today and it causes some issues with phone keyboard. It should say "source and". I went back and corrected it.
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
DarthJabba9 said:
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
Click to expand...
Click to collapse
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
MelvinGt5 said:
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
Click to expand...
Click to collapse
Yes, that is the correct download link.
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
redblack68 said:
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
Click to expand...
Click to collapse
Looks like you typed something wrong
cidxtc said:
Looks like you typed something wrong
Click to expand...
Click to collapse
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
redblack68 said:
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
Click to expand...
Click to collapse
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
cidxtc said:
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
Click to expand...
Click to collapse
No, no root. I would like to flash twrp to root with magisk
redblack68 said:
No, no root. I would like to flash twrp to root with magisk
Click to expand...
Click to collapse
Your bootloader was unlocked with mi unlocker?
cidxtc said:
Your bootloader was unlocked with mi unlocker?
Click to expand...
Click to collapse
Yes exactly
but now if i turn on my phone in fastboot, when i give an adb / fastboot command, the screen goes black and in the top left there is a very very small image " any key to shutdown". The same if i connect my phone in fastboot mode with mi unlocker