Develop Bugs

[Recovery][Titan] TWRP 2.8.0.1 for Moto G 2014

TWRP 2.8.0.1​
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel
Click to expand...
Click to collapse
Download:
TWRP_2.8.0.1_Titan_v2.img
Instalation:
Unlock your Bootloader, click here
Go into bootloader mode (power off and hold power+vol down and release)
Connect the phone to your PC
Install Adb and Fastboot into your PC (if don't install yet) (Windows, Mac)
From CMD or Terminal go into your the download folder and execute:
fastboot flash recovery TWRP_2.8.0.1_Titan_v2.img
Click to expand...
Click to collapse
Credits:
Team Win Recovery Project
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Reserved

when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?

marcviado said:
when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?
Click to expand...
Click to collapse
connect your phone to your PC, open CMD in your adb folder and write adb reboot recovery, then press enter
It worked for me, I had the same problem

Try using this recovery by @suhas.holla TWRP v 2.8 but it has some issues while taking backup and clearing cache partition.
Thread Link : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
Else use TWRP v2.7 by @suhas.holla Working perfectly fine only bug is you cant backup to internal sdcard, backup to external sd is possible.
Link : https://drive.google.com/folderview?id=0B0AbMwIJ-N7xM25CdjlQOUl2Qlk

marcviado said:
when i try to flash this recovery i get a "mismatch partition size." when i reboot to recovery it just boots the phone back up. did i do something wrong?
Click to expand...
Click to collapse
"mismatch partition size" is normal, all non official image show this message. To access you have to select recovery from bootloader and press volume up button.

sharkymyn said:
Try using this recovery by @suhas.holla TWRP v 2.8 but it has some issues while taking backup and clearing cache partition.
Thread Link : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
Else use TWRP v2.7 by @suhas.holla Working perfectly fine only bug is you cant backup to internal sdcard, backup to external sd is possible.
Link : https://drive.google.com/folderview?id=0B0AbMwIJ-N7xM25CdjlQOUl2Qlk
Click to expand...
Click to collapse
My 2.8 don't have the backup bug, is fully working. The 2.7 flash fine and backup to external sdcard, but it have a problem with install that use data partition, every install that use data partition execute but don't record the data, essentially falling.

adrianom said:
My 2.8 don't have the backup bug, is fully working. The 2.7 flash fine and backup to external sdcard, but it have a problem with install that use data partition, every install that use data partition execute but don't record the data, essentially falling.
Click to expand...
Click to collapse
For me the TWRP v2.8, while taking backup of system partition the phone reboots. I am waiting for CWM recovery for our device. :fingers-crossed:

sharkymyn said:
For me the TWRP v2.8, while taking backup of system partition the phone reboots. I am waiting for CWM recovery for our device. :fingers-crossed:
Click to expand...
Click to collapse
You test my 2.8? Because this is working fine for me. The 2.8 from suhas have this problem, but this don't.
The CWM at http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586

adrianom said:
TWRP 2.8.0.1​
Download:
TWRP_2.8.0.1_Titan.img
Click to expand...
Click to collapse
Can you please share source code as well?

jheller said:
Can you please share source code as well?
Click to expand...
Click to collapse
Is a ported version, so the source is the same as official, only changed the config files in image.

adrianom said:
Is a ported version, so the source is the same as official, only changed the config files in image.
Click to expand...
Click to collapse
Ok, thanks. Still open, can you please share the config files in that case? Github would be nice , but just attaching to this post would work as well of course.

I installed this recovery ..but when i try to create a backup it gives an error saying that cannot crete a backup folder

I can take a twrp backup only in sd card... Cant take backup in internal memory.... Please help

Would you mind telling me what you changed?
I'm trying to get a tree for the phone.
Also, could someone with a stock phone boot into the stock recovery, reboot back to the os and give me the /cache/recovery/last_log file.

Please delete, I'm stupid

prateek.khurana31 said:
I installed this recovery ..but when i try to create a backup it gives an error saying that cannot crete a backup folder
Click to expand...
Click to collapse
prateek.khurana31 said:
I can take a twrp backup only in sd card... Cant take backup in internal memory.... Please help
Click to expand...
Click to collapse
You don't are using the recovery from this thread, the first version don't have sdcard support, so you probably are using the version from suhas.holla. Flash the recovery from this thread that you are be able to backup to internal memory.

Somcom3X said:
Would you mind telling me what you changed?
I'm trying to get a tree for the phone.
Also, could someone with a stock phone boot into the stock recovery, reboot back to the os and give me the /cache/recovery/last_log file.
Click to expand...
Click to collapse
I ported from Moto G v1 recovery, and I basically change the fstab and the property string, is essentially the same phone. A tree for this phone can probably be be a copy from Moto G v1 with small changes, the problem is that the kernel source don't was release yet.

New Version:
Changelog:
* Add support to external sdcard
Download:
TWRP_2.8.0.1_Titan_v2.img

adrianom said:
New Version:
Changelog:
* Add support to external sdcard
Download:
TWRP_2.8.0.1_Titan_v2.img
Click to expand...
Click to collapse
OK i will install this recovery and report !...
---------- Post added at 01:54 PM ---------- Previous post was at 01:46 PM ----------
prateek.khurana31 said:
OK i will install this recovery and report !...
Click to expand...
Click to collapse
Ok i flashed this recovery using the flash v1.2 tool and its working.... I can take backup in internal storage as well...
1 more question can someone port roms from moto g1 to moto g2?

[TWRP][UNOFFICIAL][Heart][3.1.1-0] TeamWin Recovery For Nokia 3

Code:
[SIZE=3]
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/[/SIZE]
Here is the TWRP 3.1.1-0 Recovery for Nokia 3 (heart) smartphone.
You can update it from old TWRP recovery else install it as fresh by using adb or flashify app from google play store.
</> CHANGELOG ? : </>
Code:
[SIZE=4]
*/
* Backups will now include adopted storage keys (Dees_Troy)
* Fixed an adb restore issue (bigbiff)
* Fixed line wrapping in the GUI terminal (_that)
* Updated TWRP source code to AOSP 7.1.2 (Dees_Troy) Updated TWRP source code to AOSP 7.1.2
*/
[/SIZE]
</> DOWNLOAD ? </>
TWRP-3.1.1-0-UNOFFICIAL-Heart.img
</> NOTE ? : </>
I have already worked on TWRP and tested for some weeks ago before my Nokia 3 got broken , but forgot to post it.
Kindly report any bug seen.​
Contributors
iykeDROID™
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Created 2018-03-13
Last Updated 2018-03-13

tnx for twrp, it works great, btw there is still bug with wrong battery percentage, but it doesn't affect flash performance.

ok, after some testing, i found a serious issue, i successfully reflashed xposed, but other zips that i flashed failed because it couldn't unzip file while it unzipped successfully on other twrp by @mediafire007

Here is a screenshot of that problem

okay, i will look into it.
but first, try to rename the file without "spaces" , save and flash it again.
report back.
thanks

SkaboXD said:
tnx for twrp, it works great, btw there is still bug with wrong battery percentage, but it doesn't affect flash performance.
Click to expand...
Click to collapse
with the battery, its a bug in the kernel, AFAIK.

ok, i found another bug, when i wanted to rename file in different ways to flash file, it didn't worked. But when i wanted to rename file with letters and numbers without spacing, it would display this error starting "mv".

Comparation between mediafire007 twrp and iykeDROID™ twrp:
mediafire007 twrp:
- battery percentage is incorrect
- have a bug that touch doesn't work for 5-10 seconds but then it works good
- it loads internal storage and sd card fast
- it flashes any file without problems
- it uses older twrp version
iykeDROID™ twrp:
- battery percentage is incorrect
- touch works smoothly
- it loads internal storage and sd card a bit slower
- it mostly fails at flashing files
- it uses newer twrp version
About backing up, only partition that can't be backed up is system image (system.img) on both twrp.
That's not twrp issue, it's because system image is protected by encryption.
I didn't tried flashing backup without system image so you will risk to bootloop. (Edit: it works, you can flash backup without problems)
I will update this post if new twrp version comes out and hopefully fix bugs.

nokia 3
ihave been received the new oreo update for my nokia 3 ta-1032

Bug report.
Hello developer of old TWRP for Nokia 3, i am going to report some bugs based on what i have seen and experienced, if you do see this message, please note that i am willing to become a tester for the recovery of this device, i am now going to start stating the problems, please also note that i am using Nokia 3 with Pie ROM, Bootloader unlocked, rooted with Magisk, i am using TWRP 3.2.3 from https://unofficialtwrp.com/nokia-3-root-twrp-3-2-3/, i also believe this is the same with the TWRP that @RevanthTolety made, i know that the TWRP you made is old, but still hopefully you could do something about this, let's begin.
i have attached the pictures of the bugs, as well as logs, to help you all regarding about this problem, i have messaged all five of you in hopes that some of you are still willing to develop a proper, working recovery for the Pie ROM of this device, or at least team up in making one, anything as long as this project will still continue or something will be done.
Bugs i have found:
1. Decrypting of data, the recovery is asking me for a password and i have no idea what to do, i have never encrypted my device, or anything, and here is what i have done so far:
1a. Formatted data through TWRP, rebooted into recovery and applied root.
1b. Wiped data through TWRP, rebooted into recovery, then applied with root.
1c. All of the above, except this time i flashed no verity opt encrypt, didn't work.
1d. Formatted data through fastboot, rebooted into recovery immediately and applied root.
For the most part, by the time i managed to format or wipe my data/userdata, i am able to gain access on it through TWRP, and the recovery isn't asking me for a password, but once i am able to fully set up my device and it reaches the home screen, not putting any screen locks, just Swipe, rebooting into recovery again, and now it asks me for a password, i tried "default_password" and "password" but it didn't work, at this moment, i can only flash zips through my MicroSD Card, the recovery doesn't have access to my internal storage and i couldn't make a backup with my userdata.
2. TWRP gets replaced with stock recovery if you do not boot into it immediately after flashing, trust me, this is where i got frustrated the most, i was about to smash the phone because of this! I still had to root to ensure that the recovery will stay, or else at next boot the stock recovery will be back.
3. Battery percentage is shown incorrectly, based on the 5 forums i've seen which is all related to porting TWRP for this phone, this error has been very consistent.
4. The recovery keeps showing me a prompt of asking whether to keep System read-only or not, even though i selected the box "Don't show me this screen again.", it still comes back anyway.
5. The recovery complains about '/hidden/emmc_hidden" not being found and all that.
6. I cannot save my language, even though i already toggled it through the settings of the recovery.
7. Touch is very slow during the first screen which is the "Keep System read-only?"
Here are the things i confirmed to be working:
MicroSD Card access
OTG access
Installing .zips
I cannot test the backup and restore option since i can't access data through it, i don't want to lose progress.
That's all of the bugs i have seen so far, i am going to use my friend's phone who happens to own a Nokia 3 for testing the recovery, if i still haven't received a response within 1 week i will return the cellphone, you could contact me through Telegram, Facebook and other social media sites such as Instagram, i am willing to take the risk, please contact me if you all are still willing to continue with the development of TWRP for this cellphone.

Can you give for nokia 3 android 9
Can you give for nokia 3 android 9 twrp please

Good job on this! I wouldn't have used this phone anymore without your recovery

I've tried flashing numerous types of stock Nokia 3 ROMS I've managed to lay my hands on. Every time I try it through this version of TWRP, from an sd card, it returns an error stating that it is an invalid ZIP file format. Attempting to flash the stock ROM through "fastboot flash the_name_of_the_.zip" gives an error stating it cannot determine the image filename.
Can anyone help me?

When i type fastboot flash recovery twrp.img it shows image file is corrupted

Please help me!!!!
I have unlocked bootloader of my Nokia 3. I have also flashed the TWRP successfully, but when I boot my Nokia 3 in recovery mode, it enters the stock recovery!
Please HELP!!!!

This is worked with nokia 3 ta-1032 android 9.0?

hello, I need help with my nokia 3 TA-1020, I think I lost the system, because It's booting straight to twrp So I wanna ask if there's any twrp backup of the stock android, so i can recover it and use it (even better if rooted)

TWRP for Moto G7 (river)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
​
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore.
There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring.
You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B.
Changing the slot in TWRP also tells the bootloader to boot that slot.
Warning:
Do NOT switch slots unless you have installed copy-partitions-AB.zip or manually flashed the bootloader on both the slots:
This device comes out of the box with the bootloader installed only on the active slot (eg: bootloader_a).
Once you manually switch slots, your device will use the other bootloader partition (eg: bootloader_b) which is empty because of this factory setup therefore the device won't be able to boot in any way.
For this reason you should install the bootloader on your own on both the slots with fastboot or copy the currently installed one to the inactive slot by flashing copy-partitions-AB.zip at least once.
Note:
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: https://github.com/TeamWin
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-07-02

I went insane to figure out decryption was not possible by just fastboot booting the image. I hope the hard work paid off

this is a blessing, i was working on twrp as well but hdd fail and it was music to my ears when it was mentioned this post went up in the tele group. so thanks bro

Awesome. Getting mine today now!! )
Sent from my LG-VS980 using Tapatalk

So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.

Is this for all moto g7 versions

Hello
Very happy to see we now have TWRP. In the interest of avoiding bootloops though, I'll wait to install until it's more stable
BTW, I don't know if you guys get this, but on a us retail Moto g7 (unlocked bl obv) every time I try to boot an unofficial image I get
Code:
Command failed: remote error ' '
Any idea on what is happening?

Awesome!
This is exciting stuff. Can't wait to get busy working on it

sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Does flashing work?
Sent from my moto g(7) using XDA Labs

Alberto97 said:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Unlocked bootloader is required.
​
This device has 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Decryption only works when TWRP is permanently installed.
Installation
To temporarily boot this recovery:
Code:
fastboot boot twrp-[B]version[/B]-[B]build[/B]-river.img
To permanently install it:
Temporarily boot TWRP
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-[B]version[/B]-[B]build[/B]-river.img /data/
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
If you previously installed Magisk: Select Fix Recovery Bootloop from Advanced to fix/avoid recovery bootloops
Done! Optionally you can delete TWRP from /data or from your external SD Card now.
Download
AndroidFileHost
XDA:DevDB Information
TWRP for Moto G7, Tool/Utility for the Moto G7
Contributors
Alberto97
Source Code: [url]https://github.com/TeamWin[/URL]
Version Information
Status: Beta
Created 2019-04-14
Last Updated 2019-04-14
Click to expand...
Click to collapse
I followed steps to unlock bootloader, then flashed stock AMZ river. Did a Google restore. Followed steps to install TWRP no issues. Follow steps exactly. Booted into system, no issues. Have not done a backup yet to test. Overall it went perfectly.
Thanks so Much!
Was able to install Magisk through manager. Again all went well and rooted. Successful backup ALSO made through TWRP.

clcombs262 said:
Does flashing work?
Sent from my moto g(7) using XDA Labs
Click to expand...
Click to collapse
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Sent from my moto g(7) using Tapatalk

sd86 said:
I didn't test yet, I'm sure someone will and let us know
Edit: Flashing works, tested flashing Magisk 19 via zip and it installed correctly.
Click to expand...
Click to collapse
Flashing works for me too....
Magisk v19 or v18.1 tho sends me into bootloops. Mind you, I'm running the RR GSI I flashed via TWRP

sd86 said:
So here's my experience so far.
Backup, works just fine, afaik.
Restore, System,etc results in bootloop. Data restore, gets "extractTarFork() process ended with ERROR: 255"
Not sure if this is already known but figured id share what ive experienced. also feel free to tell me if im doing stuff wrong, it's been a while since i messed with android more than just using it.
Edit: This is with it perm installed.
Click to expand...
Click to collapse
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
B__B said:
Is this for all moto g7 versions
Click to expand...
Click to collapse
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').

I ment the for the basic g7 and thanks it helps that's what I have

Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
Click to expand...
Click to collapse
This can be done with ADB interface as well....
Code:
adb disable-verity

Work moto g7 power??

Alberto97 said:
Did you restore "system" or "system image"? In the first case It's normal you get a bootloop, you changed the content of the system partition and that triggers verity. You can use "system image" that makes a bit per bit copy of the partition to avoid problems. Obviously that does not work if you manually changed even just a file.
TLDR: Just disable verity, you should be able to do that easily with Magisk.
About the extractTarFork() error instead it's something that I've seen on every device I used TWRP. I never figured out what means, I guess data was not backed up properly but I would not worry about that, it rarely happens. Just to know, did you backup on an external sd or internal storage?
It is for all G7 variants. G7 Play/Power/Plus are different devices and require different builds.
I hope that answered your questione somehow (I'm not sure what you meant with 'versions').
Click to expand...
Click to collapse
Internal and thank you very much for the information.
Sent from my moto g(7) using Tapatalk

Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.

Omegapsy said:
Do I just flash the standard Magisk zip after installing TWRP? The install process seems to have broken Magisk within Android and it is no longer detected.
Click to expand...
Click to collapse
Yes, install Magisk after TWRP and yes, Magisk might no longer work after installing TWRP. This happens because of some patching Magisk does to the kernel that gets reverted when you tap on "Fix recovery bootloop".

I haven't had any time to play with my G7 but is there recovery Treble enabled? I'm assuming yes. Has anyone try any of the GSI's for PIe out there? or even the Q beta GSI?

[MIUI][crDroid][TWRP] Recovery issue/question

Hi All,
I am having issues recovering my crDroid system. It was working fine for some time almost 2 years then I started getting some random Firefox or other browser terminations.
In result I have bricked the device as I was not careful enough and this is MediaTek device.
Previously I was on crDroid 7.x but definitely not 7.11 or 1.15. A version before 7.11 but I don't remember.
I have took a full system backup using TWRP 3.4.0_10 (what I see in recovery.log)
I have recovered to stock MIUI Global 12.0.8 and I tried to flash TWRP 3.4.0_4 recovery as I could not find exact _10 version but it does not work. It comes back to main system when I execute
Code:
adb reboot recovery
In my case only TWRP 3.3.1 or 3.3.2 by wzsx150 works but then I cannot restore backups from SD card. I reckon these TWRP backups made on 3.4.x are not back compatible with TWRP 3.3.x.
I can see backups on SD card but I cannot select the partitions to restore. On SD card I have 2 backups a year apart but none of them let me select the partitions so I am stuck.
Please advise.
Thank you

Kardell said:
Hi All,
I am having issues recovering my crDroid system. It was working fine for some time almost 2 years then I started getting some random Firefox or other browser terminations.
In result I have bricked the device as I was not careful enough and this is MediaTek device.
Previously I was on crDroid 7.x but definitely not 7.11 or 1.15. A version before 7.11 but I don't remember.
I have took a full system backup using TWRP 3.4.0_10 (what I see in recovery.log)
I have recovered to stock MIUI Global 12.0.8 and I tried to flash TWRP 3.4.0_4 recovery as I could not find exact _10 version but it does not work. It comes back to main system when I execute
Code:
adb reboot recovery
In my case only TWRP 3.3.1 or 3.3.2 by wzsx150 works but then I cannot restore backups from SD card. I reckon these TWRP backups made on 3.4.x are not back compatible with TWRP 3.3.x.
I can see backups on SD card but I cannot select the partitions to restore. On SD card I have 2 backups a year apart but none of them let me select the partitions so I am stuck.
Please advise.
Thank you
Click to expand...
Click to collapse
Have you tried a newer version of twrp recovery?
[NEW][RECOVERY][UNOFFICIAL] BLACK CAT TWRP 3.5.2 Unified v1.0 [begonia]
It is a theme with minimalist and dark lines that are integrated with the brand. Based on TWRP-UNIFIED-3.5.1_10.... Fastboot Flashing Code: fastboot flash recovery BLACKCAT-TWRP-3.5.2_v1.0_Unified_Flash.img Downloads: Black Cat TWRP IMG File...
forum.xda-developers.com

n/a

I have taken a test backup just to see what directory structure TWRP or BRP creates.
It created exactly the same structure but the SERIAL ID on the backup directory is slightly different to the old backup.
The other issue is the date of the new backup is very old like 2010-xx-xx so there must be something up with the date+clock in BRP.

I have moved the correct backup folder from one ID directory to the other parent directory that BRP can see.
Then I confirm that BRP can see the backup directory I want to restore.
I was able to select the backup and run Restore but after reboot it's in a bootloop.
I assume these TWRP of different versions are incompatible or I flashed too many partitions perhaps I should untick some of them.
At the time TWRP autoselected partitions for backup:
Code:
System
Vendor
Vendor Image
Boot
Data (excl. storage)
DTBO
Persist
Persist Image
NVCFG
NVDATA
NVRAM
Protect F
Protect S
VBMETA
and these all were selected and restored.
BRP digested all the backup files and found no issue but at the end of restore there was one problem:
Code:
Formatting Persist using mke2fs...
mke2fs -t ext4 -b 4096 /dev/bock/sdc10 18040
process ended with ERROR: 1
Unable to wipe Persist.
Is there anything that can be done about it?

Kardell said:
I have moved the correct backup folder from one ID directory to the other parent directory that BRP can see.
Then I confirm that BRP can see the backup directory I want to restore.
I was able to select the backup and run Restore but after reboot it's in a bootloop.
I assume these TWRP of different versions are incompatible or I flashed too many partitions perhaps I should untick some of them.
At the time TWRP autoselected partitions for backup:
Code:
System
Vendor
Vendor Image
Boot
Data (excl. storage)
DTBO
Persist
Persist Image
NVCFG
NVDATA
NVRAM
Protect F
Protect S
VBMETA
and these all were selected and restored.
BRP digested all the backup files and found no issue but at the end of restore there was one problem:
Code:
Formatting Persist using mke2fs...
mke2fs -t ext4 -b 4096 /dev/bock/sdc10 18040
process ended with ERROR: 1
Unable to wipe Persist.
Is there anything that can be done about it?
Click to expand...
Click to collapse
enable "use rm-rf instead of formatting" in settings if u want to restore persist.
Also don't restore nvcfg,nvdata,nvram,persist,protect f and protect s unless you have to cuz restoring these isn't easy
Also here are some TWRP images that will work.
MIUI 12.5 based (or Android 11):https://sourceforge.net/projects/be...rp-3.5.2_11-0-UNOFFICIAL-begonia.img/download
MIUI 12 based(or Android 10):https://sourceforge.net/projects/be...3.5.1_10-begonia_UNOFFICIAL_1604.img/download
MIUI 10 based(or Android 9):Just download the official one.

Question sha256sum/Ramdisk error after flashing rom

After flashing arrowos 11.0 with TWRP, I got this error message as follows:
cd / && sha256sum --status -c ramdisk-files.
sha256sum proess ended with ERROR: 1
ramdisk files have been modified, unable to create ramdisk to flash, fastboot twrp and try this option again or use the Install Recovery Ramdisk option.
Attached is a photo of the command lines.
I didn't know what to make do of this, much less know what ramdisk is (google is very confusing). No one seemed to be getting this issue too so I was unable to find a solution.
So I ignored the message, formatted as per instructions and booted it and it worked perfectly, but I am left wondering if this is a concern and something I should worry about. Will this affect the performance of my phone and how do I solve this?
I did have quite a few issues with the whole process of flashing the custom rom being my first time doing it prior to this, but I only used the common ADB commands, flashed twrp and arrowos and did a whole lot of wiping, formatting and factory resets. Also mounted everything (system_ext and product keeps getting unmounted when I change partitions)

omg same thing happened to me today!! i was on blissrom, all good and working great but 3 hours later after i woke up the bluetooth disconnected, took my phone out of my pocket and i couldnt boot the rom (well it does boot but then restarts 5 seconds later into twrp) and now all my storage has been wiped and right now im in the middle of flashing arrow os and restoring back my phone.... lucky i have resilio sync for my backups

There is a function in TWRP Advanced that allows you to install recovery ramdisk (as indicated in the error message). If you have a thumb drive (and USB-A to USB-C converter), you can put the TWRP recovery image onto it, connect it to your phone, then use that function with that file to restore the ramdisk.

Veiranx said:
There is a function in TWRP Advanced that allows you to install recovery ramdisk (as indicated in the error message). If you have a thumb drive (and USB-A to USB-C converter), you can put the TWRP recovery image onto it, connect it to your phone, then use that function with that file to restore the ramdisk.
Click to expand...
Click to collapse
I don't get it.... Can you please explain from the start?

Veiranx said:
There is a function in TWRP Advanced that allows you to install recovery ramdisk (as indicated in the error message). If you have a thumb drive (and USB-A to USB-C converter), you can put the TWRP recovery image onto it, connect it to your phone, then use that function with that file to restore the ramdisk.
Click to expand...
Click to collapse
I see it, but what is a twrp recovery image may I ask? Is it the same img file I used to install twrp the first time, the main download on their website?

batman823 said:
I see it, but what is a twrp recovery image may I ask? Is it the same img file I used to install twrp the first time, the main download on their website?
Click to expand...
Click to collapse
That's the one!