I'm getting this "mismatched partition size recovery" error after flashing any of the TWRP recovery mods, i tried flashing the newest one 3.0.2.2 and even the older ones 2.8.x.x. I get the same error again and again and when i try booting into recovery i get the android logo saying no command.
did you ever find out how to fix this?
Leave the TWRP Partition mismatch warning message as it is
That shouldn't affect the Recovery installation. It's just a warning message. This is due to the difference in the size of partition that was made by the stock recovery vs TWRP.
This does not affect the installation. After trying all the versions of the TWRP, I finally managed to install and settle with TWRP 3.0.2.2 and ROM as CM 14.1 [Nougat 7.1.1] on Moto X 2014 (XT1092)
I am now working on getting the Google Assistant activated.
I have same issues. Are you sloved?
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
Surya-S2 said:
That shouldn't affect the Recovery installation. It's just a warning message. This is due to the difference in the size of partition that was made by the stock recovery vs TWRP.
This does not affect the installation. After trying all the versions of the TWRP, I finally managed to install and settle with TWRP 3.0.2.2 and ROM as CM 14.1 [Nougat 7.1.1] on Moto X 2014 (XT1092)
I am now working on getting the Google Assistant activated.
Click to expand...
Click to collapse
I don't understand. I have same issues. After i flash twrp, then I go to fastboot screen, choose recovery then my phone displays: No command
Related
Every time i try and flash Super su or magisk it fails, TWRP is unable to mount anything and when i try to reboot TWRP says no os installed. I then have to flash stock recovery to get the phone to boot normally, I have rooted phones in the past but i just dont get why this is happening. Can anyone shead any light on this please
Phone and FRP unlocked
P8 lite 2017 8.0.0.383(C432)
Android (stock) and EMUI version 8
TWRP 3.2.1.0
I don't think the normal root method works anymore on genuine EMUI 8. I believe that we need to flash Askuccio's TWRP (hard to find without knowing it exists already), and then a custom treble rom (of which there are many), and then flash magisk over it. Not too difficult, but personally I've been having troubles with actually booting into custom ROMs.
I can't flash the Ashuccio TWRP - keep getting FAILED (remote: partition length get error)...any help?
You have to type to flash: fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img
Thank you - I missed the ramdisk command
---------- Post added at 12:02 PM ---------- Previous post was at 11:20 AM ----------
Dru79 - now that I have TWRP - and many thanks for that, would you guide me quickly through the next steps for a custom ROM (I have read all sorts of posts that say you have to flash stock then a ROM then do all sorts - things have REALLY changed since I did this last!). I am on And 8 and emui 8 and want (ideally) as close to asop as poss with the ability for adoptive storage a must. Just unsure exactly how to progress, ie is it super SU (which most now seem to say no) or magisk etc....I really would appreciate a simple guide.
Thanks
So I followed the steps here to get TWRP on my phone and then flash the unofficial lineage OS ali on my motorola g6 and I got it done but it's not booting into the new OS but instead TWRP. How do I get rid of TWRP so that I can use my new system image?
Removing a recovery is always a bad idea and if you want to try a custom ROM you can always go for phussson's treble builds
I myself use AOSP 8.1 [V25] and it seems to be a daily driver material.
Either way if you want to remove TWRP, you can flash the stock recovery via fastboot.
trashprogrammer said:
So I followed the steps here to get TWRP on my phone and then flash the unofficial lineage OS ali on my motorola g6 and I got it done but it's not booting into the new OS but instead TWRP. How do I get rid of TWRP so that I can use my new system image?
Click to expand...
Click to collapse
You might have not cleared the PCB properly when you formatted data. You don't get rid of your recovery. While in TWRP have you tried selecting reboot system. Or reboot bootloader and then in bootloader select start.
Hi all,
I flashed a (now, very old) version of Epic ROM (v7.5.4) on my MIX shortly after its release. I used it as my daily for about 2 years and never had the desire to update beyond that, as it included everything I needed.
Soon, my MIX is no longer going to be my daily, so I figured I'd explore what newer ROMs were available. The highest usable version of TWRP on my device is 3.0.2-0 (MrRaines) and any attempt to flash anything remotely modern to my device either reports an 'Error Code 7' or reads [This package is intended for "lithium" devices, your device is type " "].
I've attempted to update my TWRP (via the Official TWRP App) to a newer version, and that renders the recovery useless, as it has no touch screen functionality; so I have to revert to 3.0.2.
What do I have to do to get my device recognized as type "lithium," so that I can go about flashing newer stuff, and how do I go about resolving the touchscreen issue?
Thanks
Mr. Raines TWRP will not let you flash a newer TWRP.
You have to fastboot flash a new TWRP from a Windows computer.
After that you should have no problem.
Official TWRP is dead, you should use the latest updated one by Blunden-Raupe
Flashing is not the issue
I can flash any TWRP (including the one you mentioned) just fine using the app or using the fastboot method. It doesn't matter - the touch screen doesn't work on any newer [than 3.0.2-0] versions of TWRP.
I understand that I need a newer recovery to flash newer stuff and I know how to flash a new recovery. My issue is that I cannot get from the old recovery to a new WORKING recovery because of touchscreen support.
Do I need to go find the stock version of MIUI that came with the phone, revert to that, and then use upgrade to a newer OEM Xiaomi ROM to achieve "lithium" status (the lack of which is what I'm assuming is causing touch issues with newer TWRP versions)?
You probably have to do something like that, so the TWRP matches the firmware to get touch working.
It has been such a long time since I had these problems so I don't remember exactly.
Now yshalsager has made firmwares available without having to flash an entire rom, you could try that.
https://forum.xda-developers.com/android/software-hacking/devices-xiaomi-firmware-updater-t3741446
Addendum:
I would either fastboot flash the latest official rom, and then flash the latest TWRP, or -
try flashing via TWRP the latest TWRP and firmware zip file at the same time.
---------- Post added at 04:58 PM ---------- Previous post was at 04:09 PM ----------
At the end of the official TWRP thread someone has just posted a modified TWRP with working decryption.
https://forum.xda-developers.com/mi...y-official-twrp-xiaomi-mi-mix-t3498960/page67
A link to Blunden-Raupes most recent TWRP is on a previous page in that thread.
The official TWRP is not supported, does not work.
Device variant: XT19121-2 James
Chipset: MSM8920
After repeated failed flashes I am on stock firmware using this guide. Phone boots and works normally right now, but I can't seem to flash any Custom ROMs on to my phone. I was using this post to flash Lineage OS 15.1, which worked successfully at first, but the WiFi wasn't working so I reflashed it. It still didn't work so I did it again, wiping Dalvik/Cache too. After the second flash attempt, my phone began to only flicker on and off. I made sure to always clean flash, factory resetting, wiping Cache and Dalvik, even formatting data, but no matter what I do it doesn't work. Also attempted other GSI images (arm, A-only) like AOSP, ResurrectionRemix and phhusson's Lineage OS 15.1 But they all failed too. I am using TWRP for James v 3.3.1 although I did also try other TWRP images like v 3.2.1 . But it makes no difference. Also used Magisk v19 like some guides suggested but whether I have Magisk or not, it doesn't work. Even made sure to push the fstab.qcom file to /vendor. Anytime a Custom ROM is flashed whether zip or GSI img it goes past the initial "bad key" or "N/A" screen and starts flickering on and off. Bootloader and TWRP works fine, but that's about it. Everytime a flash fails I go back to stock firmware (which always works) and try another ROM. I wonder why the first attempt worked but doesn't anymore even if I mirror the exact steps I took from stock. If anyone has any solutions I would be really grateful. Let me know if you need any more information.
have you taken any recent OTA updates?
mikeshutte said:
have you taken any recent OTA updates?
Click to expand...
Click to collapse
Nope. Still on the 8.0.0 version the stock firmware comes in.
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
tkhan7916 said:
Nope. Still on the 8.0.0 version the stock firmware comes in.
Click to expand...
Click to collapse
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
I also just noticed you are using the latest version of TWRP 3.3.1. I'm not sure if you originally rooted and installed TWRP with the original patched version by Cody or not, but if so make sure with the new version that you format your data partition to f2fs. As this will ensure correct mounting of the data partition.
mikeshutte said:
Okay give this a try, I'm assuming you have old root access and TWRP installed.
Download any Android 9 GSI of your liking, boot to TWRP.
Do a complete nandroid backup of the stock firmware.
Do a factory reset then wipe system partition.
Next flash your GSI that you downloaded to your system partition.
After flashing is complete of the GSI reboot to recovery.
After reboot completed flash your open Gapps zip. Then reflash Magisk.
if you get a error message when flashing g apps then you will need to use magic g apps with magisk as it will install them systemless. I have to do this on my device because the partition doesn't have enough space.
Give that a try and let me know how it goes if you have any questions feel free to ask.
Click to expand...
Click to collapse
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
I am having the same issue
Using XT1921-1
Latest TWRP
Have tried LOS 15, LOS 16, AOSP 8.1, AOSP 9.0
Have tried flashing in fastboot and TWRP
Have tried every combo of wipe/factory reset/format data and magisk flash possible
have tried stock recovery, have tried no verity, have tried stock boot.img
nothing works. only able to produce powered on (black and blank) screen that turns on and off for a minute before returning to bootloader
PLEASE HELP
think i might need a 8.0 GSI but cant find one anywhere
I eventually got RR to boot on the james xt-1921-3 I installed XT1921-3_JAMES_T_MPCS_8.0.0_OCPS27.91-150-5-1-3_cid21 as a base, then used boot and vendor partitions from JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC and it finally worked.
tkhan7916 said:
Followed these steps exactly, including formatting the data partition to f2fs, and the same problem still persists. Screen just keeps turning on and off in a loop without booting into the ROM. I downloaded the Lineage OS 16.0 GSI A-only Arm version for reference.
Click to expand...
Click to collapse
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Download the file from this post https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 , then using fastboot, flash the vendor and boot img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
then boot into recovery and flash the file from that post to disable dm-verity and force encrytion, after that flash magisk, then reboot to bootloader, at command prompt-
fastboot erase userdata
fastboot erase cache
fastboot reboot
that should get you booted - profit
mrbox23 said:
Message me, I'll host a TWRP backup for the XT-1921-3 that boots RR 6.1
Click to expand...
Click to collapse
Do you still have that back up by any chance and could ypu send it to me?
[RECOVERY] TWRP 3.3.1-0 - TeamWin Recovery Project
Hello, I am releasing an official version of TWRP I have been working on for the last 6 weeks. If you download the patched fastboot image as described in the device installation page, you can use TWRP to repack the non-fastboot image for a permanent installation. Currently encryption is supported in the fastboot version and the permanently installed version. Thanks for your patience waiting for official support.
I was kindly given the device from Asus, and will not be blind supporting this device.
X01WD Device Config: https://github.com/TeamWin/android_device_asus_X01WD
DOWNLOAD:
All official devices are listed at the top of the page on the Team Win website. Search for the device in the textbox.
http://twrp.me
Reserved 1
Reserved 2
Amazing news! I'm expecting to receive my Zenfone 6 30 edition tomorrow, so the timing couldn't be more perfect.
Is it working with LOS 16 encryption?
Yes. I merged in the good work from Peter Cai for wrapped key support. First it will try a non wrapped key. If that fails it will try a wrapped key. I tested both LOS and Omni.
bigbiff said:
Yes. I merged in the good work from Peter Cai for wrapped key support. First it will try a non wrapped key. If that fails it will try a wrapped key. I tested both LOS and Omni.
Click to expand...
Click to collapse
stuck on Trying Decryption for several minutes after fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img
I can boot twrp without password and flash persistent version. Maybe it will work then?
Nope. Cannot boot recovery after flashing. Only LOS booting.
Here is my experience:
Lineage for me is really broken, after a while if I reboot my phone I eventually get stuck in a bootloop, I always customise many settings and haven't narrowed done what the issue is. I was hoping this official TWRP would help with this (constantly reinstalling everything was getting really annoying) but it didn't seem to change much.
Flashing the first IMG (the second download) is the IMG file that works otherwise I bootloop. The flash seems to not in into as many mounting errors as the previous mod and flashing lineageos works but only through ADB sideload or you will again bootloop. This is an improvement because before side loading was not possible.
After flashing the twrp installer zip thus successfully passes but never installs correctly and every time I went through an install I would be taken to lineageOS recovery. From here side loading twrp doesn't work but side loading magisk and mindthegapps is fine with no errors that would occur before.
Booting lineage for the first time didn't open the factory wipe error screen as well.
TLDR; TWRP doesn't stick on the phone but I haven't had a reboot leading to an eventual bootloop so far. So far a partial success
Are you on the most recent firmware? Did you install the image in the download link through the fastboot installer version of TWRP through the repack recovery ramdisk option of TWRP?
Grom8 said:
Here is my experience:
Lineage for me is really broken, after a while if I reboot my phone I eventually get stuck in a bootloop, I always customise many settings and haven't narrowed done what the issue is. I was hoping this official TWRP would help with this (constantly reinstalling everything was getting really annoying) but it didn't seem to change much.
Flashing the first IMG (the second download) is the IMG file that works otherwise I bootloop. The flash seems to not in into as many mounting errors as the previous mod and flashing lineageos works but only through ADB sideload or you will again bootloop. This is an improvement because before side loading was not possible.
After flashing the twrp installer zip thus successfully passes but never installs correctly and every time I went through an install I would be taken to lineageOS recovery. From here side loading twrp doesn't work but side loading magisk and mindthegapps is fine with no errors that would occur before.
Booting lineage for the first time didn't open the factory wipe error screen as well.
TLDR; TWRP doesn't stick on the phone but I haven't had a reboot leading to an eventual bootloop so far. So far a partial success
Click to expand...
Click to collapse
no way to decrypt
Hi,
sorry for bothering, I'm on Stock Rom -189 ( Asus ZF6 8/256 ), I tried fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img after entering my personal "PATTERN" the TWRP stucks on " Updating partition details... " ... see the image
I can't extract a "recovery log" for the STATE of the system ( no MTP )
digitalpixel
encryption destroyed
Hi,
I tried to boot my Rom but nothing happen ... Stuck on the Zenfone logo .. no OS
Very Sad :crying:
digitalpixel
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
HELP
Hi,
there is a way to retrive the data partition ?? I have important personal document not BU over there :crying::crying::crying:
digitalpixel
digitalpixel said:
Hi,
there is a way to retrive the data partition ?? I have important personal document not BU over there :crying::crying::crying:
digitalpixel
Click to expand...
Click to collapse
Depending on where in data you file is stored you can try "adb pull /path/to/you/file.txt".
Adb works even while twrp is stuck during decryption.
If that does not work try booting into bootloader > fastboot boot twrp3.3.1-19 image from mauronofrio. In twrp 3.3.1-19 flash the twrp3.3.1-19 installer.zip and magisk.zip. Reboot system. That worked for me on omnirom.
isthisadagger said:
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
Click to expand...
Click to collapse
Hi isthisadagger,
no way I can't decrypt , I think I LOOSE ALL ...
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
isthisadagger said:
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
Click to expand...
Click to collapse
I tried like you said, no way to decrypt data partition in TWRP -19 and no way to boot to system
---------- Post added at 07:50 PM ---------- Previous post was at 07:43 PM ----------
isthisadagger said:
What happens when you install 3.3.1-19 and
1. Try to boot to system?
2. Boot to recovery and enter you password to decrypt?
Click to expand...
Click to collapse
I think the custom roms have the ability " I suppose " to restore the Key ... the stock NO
I hope some one didn't mess with "wrappedkey and non-wrappedkey"
digitalpixel
digitalpixel said:
Hi,
I tried to boot my Rom but nothing happen ... Stuck on the Zenfone logo .. no OS
Very Sad :crying:
digitalpixel
Click to expand...
Click to collapse
Re-reading thread
isthisadagger said:
So i tried to flash the zip:
I am on the latest omnirom 2019-08-31 with unofficial twrp 3.3.1-19 from mauronofrio. I flashed omnirom coming from stock 191 if it matters.
Twrp 3.3.1-19 successfully decrypts.
I flashed twrp-installer-3.3.1-0-I01WD.zip and magisk.zip from twrp 3.3.1-19 > reboot to recovery. Enter decryption pin > trying decryption. Thats where i am stuck after waiting a few minutes.
Forcing a reboot with vol down + power recovery starts again. I can not boot system.
After a few minutes of waiting nothing happens after "using secdis" in the recovery.log.
Rebooting into bootloader and fastbooting twrp 3.3.1-19 and installing it works as does booting to system after.
Click to expand...
Click to collapse
What zip are you flashing? I am only supporting flashing the recovery image through the fastboot installer and using TWRP's repacking tools.
digitalpixel said:
I tried like you said, no way to decrypt data partition in TWRP -19 and no way to boot to system
---------- Post added at 07:50 PM ---------- Previous post was at 07:43 PM ----------
I think the custom roms have the ability " I suppose " to restore the Key ... the stock NO
I hope some one didn't mess with "wrappedkey and non-wrappedkey"
digitalpixel
Click to expand...
Click to collapse
TWRP only updates the key in memory and it shouldn't overwrite the local data key. If it's unable to decrypt normally, it will attempt to use a wrapped key in memory.