[RECOVERY][bacon] TWRP 3.1.1-0 touch recovery [2017-05-19]

Search This thread

wollah_91

Senior Member
Dec 9, 2014
87
23
solved

You went from an unofficial version to the official one I suppose. If this is the case you have to delete the .twrps file.

i solved my problem by doing the following:

1. flash the latest twrp 3.0.2.0
2. try backup - failed
3. went to settings
4. tapped 'use default settings'
5. tried backup again - no errors
6. fixed!

Hope this help someone.
 

chaoscreater

Senior Member
A user on the OnePlus forums told me in a thread that to backup EFS properly you need to do the following...Is this in the new script?


Post 1:

dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
dd if=/dev/block/mmcblk0p15 of=/sdcard/efs.img bs=4096

people also seem to forget EFS is useless without these backups

dd if=/dev/block/mmcblk0p12 of=/sdcard/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/sdcard/oppostanvbk


Post 2:

you need EFS.img as well modemst1 modemst2 is not enough


Post 3:

IMEI backups are also hidden in these partitions. which phone will check for

dd if=/dev/block/mmcblk0p19 of=/sdcard/PARTITION_BKP/fsc
dd if=/dev/block/mmcblk0p18 of=/sdcard/PARTITION_BKP/fsg
dd if=/dev/block/mmcblk0p29 of=/sdcard/PARTITION_BKP/grow
dd if=/dev/block/mmcblk0p21 of=/sdcard/PARTITION_BKP/misc
dd if=/dev/block/mmcblk0p1 of=/sdcard/PARTITION_BKP/modem
dd if=/dev/block/mmcblk0p10 of=/sdcard/PARTITION_BKP/modemst1
dd if=/dev/block/mmcblk0p11 of=/sdcard/PARTITION_BKP/modemst2
dd if=/dev/block/mmcblk0p12 of=/sdcard/PARTITION_BKP/oppodycnvbk
dd if=/dev/block/mmcblk0p13 of=/sdcard/PARTITION_BKP/oppostanvbk
dd if=/dev/block/mmcblk0p9 of=/sdcard/PARTITION_BKP/pad


Does the latest TWRP (whether official or unofficial) back up these partitions? Backing up modemst1 and modemst2 isn't enough. This post says it all:
https://forums.oneplus.net/threads/anyone-successful-in-backup-the-efs-imei.91986/page-2

I'm using the unofficial one and while it does offer EFS and persist partitions backup, I don't think it backups all of those 10 partitions mentioned above. Looking at the recovery log, partitions oppodycnvbk, modemst1 and modemst2 are backed up, but oppostanvbk and the rest aren't. I know this isn't the unofficial TWRP thread but EFS/IMEI is so important and I have seen so many posts about recovering it. Just wondering if this is to be implemented or whether there is a reason why it's not? I've used official TWRP 3.0.2.0 for other devices and they provide EFS backup.
 

danieldmm

Senior Member
Dec 18, 2008
5,191
12,054
France
Modemst1 and Modemst2 are the only partition needed to backup EFS on OPO, at least it was... Don't think they changed that.
 
Last edited:

chaoscreater

Senior Member
Modemst1 and Modemst2 are the only partition needed to backup EFS on OPO, at least it was... Don't think they changed that.

Don't think that's enough. My OPO lost the EFS partitions and I've made no backups. Someone on XDA posted their modemst1.bin and modemst2.bin files which I flashed, no IMEI. Tried with another set of files that another person gave me, still no IMEI. I've tried a lot of things already, including using the qualcomm msm tool, flashing colourOS and oxygenOS etc. This leads me to strongly believe that you need to restore partitions oppodycnvbk and oppostanvbk as well. This falls in line with the following post below, as well as the posts in my previous reply:

https://forums.oneplus.net/threads/partition-info-and-dd-backup.49114/page-2#post-11417267


In fact, I have read several guides that suggest deleting the modemst1 and modemst2 partitions (fastboot erase modemst1 and modemst2). I have done that and it makes no difference. Here's one of the guides:
http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Read the bottom of the first post.

There's also this post here:
http://xdaforums.com/showpost.php?p=55543630&postcount=23

"modemst1/2 is NOT the EFS, those are some kind of temp or buffer partitions, present on the Note 3 as well, you can format them, nothing bad happens, they will get regenerated, but if those are corrupt (happened on Note 3), no more IMEI and constant FCs and reboots (on the Note 3)."

This is why some people without any EFS partition, were able to recover their IMEI by flashing ColorOS/OxygenOS or whatever. This never worked for me though. From my personal experience, restoring modemst1 and modemst2 from someone else's backup will not restore their IMEI onto my phone. My IMEI will show as 00 instead.
 
Last edited:
  • Like
Reactions: rolarocka

Anghirrim

Senior Member
Apr 29, 2011
1,172
278
Google Nexus 5
Samsung Galaxy J5
Don't think that's enough. My OPO lost the EFS partitions and I've made no backups. Someone on XDA posted their modemst1.bin and modemst2.bin files which I flashed, no IMEI. Tried with another set of files that another person gave me, still no IMEI. I've tried a lot of things already, including using the qualcomm msm tool, flashing colourOS and oxygenOS etc. This leads me to strongly believe that you need to restore partitions oppodycnvbk and oppostanvbk as well. This falls in line with the following post below, as well as the posts in my previous reply:

https://forums.oneplus.net/threads/partition-info-and-dd-backup.49114/page-2#post-11417267

oppostanvbk is a part of the officials fastboot COS images.

I don't think this contains anything IMEI related.

What is oppodycnvbk?
 

Timmmmaaahh!

Sr. Mod / Mod Cmte / Recognized Xmas Avatar Themer
Staff member
Sep 11, 2012
6,659
1
18,952
From From eh... Belgium!
OnePlus One
OnePlus 6T
Hi! I hope this is the right place to post in as I'm running TWRP TugaPower-3.0.2-1 on Bacon.
I sometimes get to see abnormal percentage and transfer numbers (see image attached), stating something like 7211141375271MB of 6740MB, 2147483647% I'm pretty sure it's not copying 7TB but it does have me worried if backup is running as it should in that case.
Backing up to a brand new OTG drive (SanDisk Ultra 64GB) while seeing these abnormal numbers caused my OnePlus One to reboot upon (or nearing) completion. I've now reset settings (cheers @hosseltietjes1990 , leuke naam btw) and backup ran as expected. Anyone else experienced this?
 

Attachments

  • DSC06339.jpg
    DSC06339.jpg
    253.8 KB · Views: 408
  • Like
Reactions: wollah_91

danieldmm

Senior Member
Dec 18, 2008
5,191
12,054
France
Hi! I hope this is the right place to post in as I'm running TWRP TugaPower-3.0.2-1 on Bacon.
I sometimes get to see abnormal percentage and transfer numbers (see image attached), stating something like 7211141375271MB of 6740MB, 2147483647% I'm pretty sure it's not copying 7TB but it does have me worried if backup is running as it should in that case.
Backing up to a brand new OTG drive (SanDisk Ultra 64GB) while seeing these abnormal numbers caused my OnePlus One to reboot upon (or nearing) completion. I've now reset settings (cheers @hosseltietjes1990 , leuke naam btw) and backup ran as expected. Anyone else experienced this?
It's not the right place, my recoverys are posted on the unnonficial thread. The answer to your problem it's to updated the TWRP to my lattest build. TugaPower-3.0.2-3

Enviado do meu A0001 através de Tapatalk
 
Last edited:
  • Like
Reactions: Timmmmaaahh!

Timmmmaaahh!

Sr. Mod / Mod Cmte / Recognized Xmas Avatar Themer
Staff member
Sep 11, 2012
6,659
1
18,952
From From eh... Belgium!
OnePlus One
OnePlus 6T
It's not the right place, my recoverys are posted on the unnonficial thread. The answer to your problem it's to updated the TWRP to my lattest build. TugaPower-3.0.2-3

Enviado do meu A0001 através de Tapatalk

Cheers for replying nonetheless! I looked for "TugaPower" and seemed to find nothing but ROM threads. Found the right one now via your profile, will follow that one instead. Sorry to bother! :)
 
  • Like
Reactions: danieldmm

juvezavala

Senior Member
Apr 25, 2012
61
12
Salinas, CA
Hey everyone! Looks like decryption and mounting /data isn't working again. I'm on the latest CyanogenOS build, SU'd and running TWRP 3.0.2-0 but can't seem to decrypt and mount /data. The only recent change I can think of on my setup is allowing that new Google 2 factor "Google Prompt" feature to run on my A0001. Thanks!

Edit: Nevermind, I already asked Dees about this one before on Google+. I forgot: Go under Lock Screen Settings and make sure you check "Require X to start device". Hope it helps someone.
 
Last edited:

speakxj7

Member
Nov 14, 2011
43
3
boston
Hey everyone! Looks like decryption and mounting /data isn't working again. I'm on the latest CyanogenOS build, SU'd and running TWRP 3.0.2-0 but can't seem to decrypt and mount /data. The only recent change I can think of on my setup is allowing that new Google 2 factor "Google Prompt" feature to run on my A0001. Thanks!

Edit: Nevermind, I already asked Dees about this one before on Google+. I forgot: Go under Lock Screen Settings and make sure you check "Require X to start device". Hope it helps someone.
hrm. i'm on a cm13 nightly from the last week or so and twrp 3.0.2 and i require my pattern to start. decrypting still fails.
will read back through the thread for clues.
 

Signor Rossi

Senior Member
Sep 13, 2013
484
75
To give everyone some more background.

I did a Nandroid backup using TWRP Official.
By mistake I did a Factory reset, when I wanted to do a wipe cache/Dalivk.
Did boot up and realized I did the wrong wipe.
Booted into TWRP and restored the Nandroid Backup.
Booted into CM and realized CM is not accepting my PIN (SIM Card is not detected)
 
Last edited:

danieldmm

Senior Member
Dec 18, 2008
5,191
12,054
France
To give everyone some more background.

I did a Nandroid backup using TWRP Official.
By mistake I did a Factory reset, when I wanted to do a wipe cache/Dalivk.
Did boot up and realized I did the wrong wipe.
Booted into TWRP and restored the Nandroid Backup.
Booted into CM and realized CM is not accepting my PIN (SIM Card is not detected)
Re-flash full cm rom, check if sim card it's working, then try restoring only the data backup partition.

Enviado do meu A0001 através de Tapatalk
 

Top Liked Posts

  • There are no posts matching your filters.
  • 172
    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.




    CHANGELOG for 3.0.2-0:

    -Backups will now include adopted storage keys (Dees_Troy)
    -Fixed an adb restore issue (bigbiff)
    -Fixed rebooting when no OS is present (Dees_Troy)
    -Fixed line wrapping in the GUI terminal (_that)
    -Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)


    CHANGELOG for 3.1.0-0:

    -vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
    -adb backup to stream a backup directly to or from your PC, see documentation here: https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9 (bigbiff)
    -tweak MTP startup routines (mdmower)
    -support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
    -support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
    -better indicate to users that internal storage is not backed up (Dees_Troy)
    -improve automatic determination of TW_THEME (mdmower)
    -minimal getcap and setcap support (_that)
    -try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
    -shut off backlight with power key (mdmower)
    -timeout during FDE decrypt (Dees_Troy and nkk71)
    -support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
    -boot slot support (Dees_Troy)
    -TWRP app install prompt during reboot (Dees_Troy)
    -support for AB OTA zips (Dees_Troy)
    -support new Android 7.x log command (Dees_Troy)
    -update recovery sources to AOSP 7.1 (Dees_Troy)
    -numerous bugfixes and improvements by too many people to mention

    CHANGELOG for 3.0.2-0:

    -Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
    -Add Greek translation to some builds.

    CHANGELOG for 3.0.1-0:

    -support new CM 13.0 pattern encryption (sultanqasim)
    -fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
    -libtar updated to latest upstream and fixes (jcadduono)
    -fixes for loading custom themes (_that)
    -TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
    -translation updates - added Italian, Czech and Polish and significant updates to Dutch
    -progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
    -fix input box text display (Dees_Troy)
    -reboot option after zip install complete (bigbiff)
    -other mostly invisible bug fixes and improvements

    CHANGELOG for 3.0.0-0:

    -Completely new theme - Much more modern and much nicer looking (by z31s1g)
    -True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
    -Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
    -Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
    -Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
    -Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
    -SuperSU prompt will no longer display if a Marshmallow ROM is installed
    -Update exfat, exfat fuse, dosfstools (by mdmower)
    -Update AOSP base to 6.0
    -A huge laundry list of other minor fixes and tweaks

    WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.

    Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.

    Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.

    We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!

    DOWNLOAD:
    1) Install the TWRP app from the Play Store or grab the apk from our website
    2) Open the app, agree to the terms, and enable root access
    3) Select TWRP Flash
    4) Search for your device and select the version you wish to download
    5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
    OR:
    Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
    1) Download the latest version from our website on your device
    2) Reboot to TWRP
    3) Hit Install and tap the "Images..." button in the lower right
    4) Browse to the location of the TWRP image on your device and select it
    5) Select recovery from the partition list and swipe to flash
    OR:
    You can find more information and download links on our website.

    BUGS:
    If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!

    SUPPORT:
    Live support is available via #twrp on Freenode with your IRC client or just click this link.
    35
    The main reason we provide image files instead of zips is because:

    Code:
    make recoveryimage

    spits out an image file.

    Making a zip after that requires more work that yes, can be scripted eventually. In a few cases, namely with loki images, I do produce zips. Still it's more work. Further, you cannot flash those zips on devices that are running stock recovery. Noobs are incredibly noobish and I guarantee you I would get support emails from noobs saying "zip signature verification failed" from people trying to flash the zip in the stock recovery.

    But really, it boils down to what's the least amount of work for me. Supporting recovery is a LOT of work, especially when you're supporting 60 to 80 devices. Don't claim to know what's best or debate how it should be done until you're doing it yourself at a large scale.
    34
    Reserved

    Device page on our website

    Download folders with current and previous versions:
    Mirror 1
    Mirror 2
    17
    You must be rooted.
    Open an ADB shell or install a terminal emulator like this one https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
    After that, write the following 3 commands:

    su (press Return)
    dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512 (press Return)
    dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512 (press Return)

    Backup files modemst1.bin and modemst2.bin will be created on the root your internal storage.