Database Users

[Q] No modem partition in TWRP backup

Hi,
I'm installed TWRP 2.7.0.0 via GooManager and that went smoothly. But when I went to do a nandroid backup, the modem partition isnt there. The other partitions (boot, system, cache, data, efs) are there. In "Mount" the modem partition wasn't mounted so I tried to mount it, but that didn't add it to the available partitions to backup either. Is it normal for the modem partition to be missing? How can I back it up?

The modem is never backed up. All you need to back up are system, data, and boot
Edit, it would be good to backup only the efs partition once and store a copy off your phone in case that ever gets messed up
Sent from my Nexus 5

jd1639 said:
The modem is never backed up. All you need to back up are system, data, and boot
Edit, it would be good to backup only the efs partition once and store a copy off your phone in case that ever gets messed up
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks. :good: It's a bit confusing as I see some posts talking about backing up modem with TWRP....and other posts talking about grabbing a modem file from a developers thread and using that. I guess I'll go with the latter based on your large number of posts and >2000 Thanks received. :fingers-crossed:

DoughMucker said:
Thanks. :good: It's a bit confusing as I see some posts talking about backing up modem with TWRP....and other posts talking about grabbing a modem file from a developers thread and using that. I guess I'll go with the latter based on your large number of posts and >2000 Thanks received. :fingers-crossed:
Click to expand...
Click to collapse
Trust him, a modem don't need backup because it never been touched, only Odin can touch and modify modem when you flash a stock ROM
Sent from my GT-I9505G using Tapatalk

Factory image / OTA and F2FS

Hi there,
I searched a lot on the subject, but I'm still not sure if/how this would work:
Can you install a factory image or an OTA update on a F2FS formated Nexus 7 2012?
Currently I have a lollipop custom ROM and kernel, with all F2FS and TWRP running on my Nexus 7. Could I install a custom F2FS kernel on my F2FS formated Nexus 7, like Phantom, and then only flash system.img and userdata.img from a lollipop factory image? Then, could I simply flash future OTA update zips?
Thanks!

It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.

bill3508 said:
It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.
Click to expand...
Click to collapse
Hi,
I got as far as (in short):
- Flash factory image
- Flash openrecovery TWRP
- Backup system and data (you have to make some space on system first, e.g. by moving some apps over to data)
- Format system, cache and data to F2FS in TWRP
- Restore system and data backup with "Use rm -rf instead of formatting" checked in TWRP settings
- Flash boot.img from Phantom kernel
I got this to work with LP 5.02, but for some reason with 5.1 the system restore failed so far... As for updates, I thought that, in the same way, you could just restore a system backup of a newer factory install over your actual system, but I haven't tried that yet.
Then again, this all is quite tedious. I'm not very advanced in img or ROM modification, but I'd like to know what one would have to modify in factory images or ROMS to make them F2FS compatible. For JB there are ressources out there, but I haven't found anything for LP so far... Anyone?

All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.

Simply formating cache to f2fs makes already such a difference? Interesting, will give this a try. This would be a fairly easy solution to have a fast stock experience. I might try formating data to f2fs as well (and restoring backup), but leaving system on ext4. This way you may be able to simply flash the system image from future factory images to update your system, that would be a good enough solution for me.

First try updating to 5.1.
5.1 is running and performing so much better than on 5.0.2.
Even with ext4 filesystem and stock kernel.
Sent from my Nexus 7 using XDA Free mobile app

I already am on 5.1. Intitially it ran pretty good indeed, but I'm starting to get occasional lags again now. Not as bad as before, but still not as smooth as with JB when it was new... Like I said earlier, I haven't managed to do the TWRP f2fs backup and restore method for some reason with 5.1, but keeping system on ext4 might do the trick, so I'll try that and see if it improves upon stock 5.1...

rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.

maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
I'm using Franco Kernel(r82). It supports F2FS(formatted /cache and /data to F2FS) and it works flawlessly.

TWRP backups fail on stock 5.1 with f2fs/franco?
I downloaded the 5.1 factory image; installed it using the included batch file; installed franco r82 and formatted /cache and /data to f2fs. It seems to run reasonably well, but TWRP 2.8.5.1 and 2.8.6.0 both fail to make a backup, giving an unspecified error when backing up the data partition. Do you experience the same thing? Do you know of a workaround?

maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.

rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
rbeavers said:
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.
Click to expand...
Click to collapse
Running really good so far with Franco Kernel and Cache and Data in f2fs. Thanks guys.
I also don't get that wake delay btw. Maybe wipe cache again?
@CCarson: I made a successful backup using TWRP 2.8.6.0. Maybe backup your sdcard and then re-format data. Also, don't know if this applies to you, but if you have the 16GB model, the 5.1 factory image formated mine to 8GB, so I had to re-format data once to get it back to 16GB and only then I changed it to f2fs.

TWRP sayd system not mounted, then rebooted during restore, phone is softbricked

I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.

When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.

dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.

I ended up just flashing the stock google image and that at least gave me a working phone back.

Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.

dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)

Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.

If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk

zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?

Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk

mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything

Twrp Backup Options

Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS

kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data

Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?

Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.

kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?

Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.

kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4

kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).

I have a pattern lock and fingerprints and restore my backup without any problems?

Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?

I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91

TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.

Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.

Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!

Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)

So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones

survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.

Stuck on Google Logo after TWRP Backup Restore.

Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.

Tried clearing cache? Also, what things did you precisely backup?

DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache

setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.

DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?

Try it without the system image.

DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.

setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something

setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?

Yes

oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.

setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.

setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through

oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.

Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?

oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.

okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg

setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!

I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.

Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!