Database Users

[Q] TWRP / CWM Compatible - need data from old backup.

Long story short, my car charger 'melted' my main board on my N4. Sent in to LG for repair and they replaced it, free of charge. However, I lost everything since the memory is on the mainboard.
I have since re-rooted my phone and decided to go with TWRP instead of CWM that I had previously.
My questions are this:
I have an older CWM backup saved on my computer. Is there a way for me to 'explore' the backup with a Window program so I don't have to re-flash the whole image on the phone in order to save whatever data (pictures videos etc) and extract them somehow?
If not, can I flash a CWM backup onto the phone via TWRP? Are they compatible? Is there any harm in flashing an old CWM (4.2.2) onto a TWRP (4.3) to get my data back and then repeat the process?

usafle said:
Long story short, my car charger 'melted' my main board on my N4. Sent in to LG for repair and they replaced it, free of charge. However, I lost everything since the memory is on the mainboard.
I have since re-rooted my phone and decided to go with TWRP instead of CWM that I had previously.
My questions are this:
I have an older CWM backup saved on my computer. Is there a way for me to 'explore' the backup with a Window program so I don't have to re-flash the whole image on the phone in order to save whatever data (pictures videos etc) and extract them somehow?
If not, can I flash a CWM backup onto the phone via TWRP? Are they compatible? Is there any harm in flashing an old CWM (4.2.2) onto a TWRP (4.3) to get my data back and then repeat the process?
Click to expand...
Click to collapse
No, there is no problem in :
Flashing CWM, restoring the backup, then flashing TWRP, and create a backup.
Another way would be extracting the data from the backup, which would be a pain in the back, and it's not worth it.

Google for "diskinternals". There should be a program for windows that allows you to open/read linux files/partitions.
Good luck.
Sent from my Nexus 4 using xda app-developers app

So from what I am understanding a "CWM" backup won't load in TWRP? I would have to flash CWM recovery to load the backup and then rinse and repeat to get TWRP back on the device...
I'll Google that diskinternal - thanks

Well we can close this. I used Nandroid manager to browse the CWM backup - as suggested by a friend. Unfortunately, I did not choose to back up my SDCard when I did the backup. So now, everything is lost for good.
Lesson learned.

[HELP] Screwd up nandroid

Hello guys!
I was updating from 4.4.4 to lollypop via OTA, then I realized that even if I run the stock ROM, I am still unlocked + root, meaning that the OTA won't run.
I did a complete nandroid backup via Wugs Nexus Toolkit, including data.
Then I wiped and flashed the new 5.0 via Nexus Toolkit, but when I tried to restore only the data it didn't work.
I decided to go back to 4.4.4. and do things properly, but now I'm not able to restore anything.
I am not bothered with the apps and stuff, but I had plenty of pictures which I forgot to backup, and I want to restore them. I even tried to access the nandroid backup files, but no success!
I was accustomed with the old CMW, where you had the .img files, but I got no clue on what to do here!
I add the picture of the nandroid backup folder on my PC ( I think the data files are splitted, but I cannot open them in any case, not even with 7zip).
The nandroid was executed via Nexus Toolkit, but I guess it has been done through TRWP.
Long story short:
1) how can I access the pictures inside the nandroid backup?
2) how can I restore a nandroid backup that keeps failing?

theraizen said:
1) how can I access the pictures inside the nandroid backup?
Click to expand...
Click to collapse
Maybe CWM does things differently, I don't know, but with TWRP, a Nandoid backup doesn't back up your SD card partition, so if you wiped everything, all your pics are gone. Sorry.

Yeah, I guess so.. Managed to recover something with DISK DIGGER (its an app, free on the store). Just wanted to write it here, so if anyone has the same issue can recover this way!

What to backup to recover before flash ROM?

I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.

Splice_9 said:
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Click to expand...
Click to collapse
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.

I backed up all 53 partitions and stored in my harddisk. It's less than 5GB.
I left out only the data partition because for that I use Titanium Backup and RSync.
Yet I haven't backed up the partition table, also this is important...

NZedPred said:
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
Click to expand...
Click to collapse
if i backup my efs and persist in a custom rom 64 bits that backup won't work in stock right? it is intact

Backup everything... although it may be too late already, but any working backup is better than nothing.
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.

nicolap8 said:
Yet I haven't backed up the partition table, also this is important...
Click to expand...
Click to collapse
acejavelin said:
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
Click to expand...
Click to collapse
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?

prokaryotic cell said:
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
Click to expand...
Click to collapse
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).

acejavelin said:
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
Click to expand...
Click to collapse
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?

prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
Click to expand...
Click to collapse
Yes, you can restore your efi folder to correct this most of the time, if you have a clean backup. Otherwise you need to get it JTAG programmed

prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device.
Click to expand...
Click to collapse
Just to clarify that you understand, you can't return your bootloader status to untampered but you can lock it again. However it really isn't necessary to do that just to get OTAs. All you need to do is return to your stock with stock recovery and no-root (fastboot method not TWRP flashable.) OTAs work fine once you have done so. I have restored a TWRP backup just by booting into TWRP but it seems like I had some issue unrelated to OTA, although I don't recall what they were and is was on my previous phone (Moto G4).

TWRP corrupted? Won't restore, won't backup, won't wipe.

I bought a new XT1575 a couple of weeks ago. Once I'd read enough to have confidence I followed the instructions to extract that long number to paste into the form on the Motorola web site and ask them to send me a code. They did, I input the code, I got a notice that my bootloader was unlocked. Once that was done I installed TWRP via ABD (I think, whatever the directions said). TWRP worked, I wiped the stock OS, flashed a custom ROM (Lineage 14) and everything worked perfectly.
Today I wanted to backup my existing ROM, wipe the device and install a different custom ROM. I booted into TWRP and I think it completed the backup. When I went to wipe though, it would crash partway through and boot back to the bootloader unlocked screen. If I tried to simply overwrite the existing ROM with the new ROM that would crash and boot to the bootloader unlocked screen too. Now I can't complete a backup either.
As I'm writing this I'm wondering if the micro USB card could be at fault, since that's where I want to back up to and that's where the new ROM is. However, if it was a corrupted card wouldn't the wipe function still work?
Any idea if reflashing TWRP would solve my problem? Any better solutions?

First time ever installing a custom ROM. I have some questions. Moto G5 Plus stock.

I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!

Raploz said:
I have a completely stock Moto G5 Plus (XT1683 - 2GB of RAM) on stock Oreo 8.1 and I want to use the Pixel Experience 10. I've watched some tutorials online but I still have some questions:
1. I've seen many people complaining that they lost their IMEI and 4G, but I still couldn't figure out if that only happened with people that downgraded from a custom Oreo rom to a stock Nougat or if there's a chance of that happening by installing any custom ROM. My phone has the latest official Oreo version and I've never messed with the system before. Is my phone still at risk of losing its IMEI if I install Pixel Experience 10? What did those people do wrong?
2. Now let's talk about the procedures I have to take. After unlocking the bootloader it will wipe my system, right? If that's so, should I let it boot again into Android and turn off or should I immediately get into fastboot and flash TWRP? Will it make a difference? Will the persist and efs partitions be there on TWRP to be backed up or do I need to let Android boot so it can make them first?
3. After everything, if I get into TWRP and it asks for a password, should I just cancel and wipe the partitions to remove the encryption (can I keep the internal storage?) or do I need to install that dm-verity file instead? As I understand the dm-verity if only for when rooting the phone while keeping the stock system, right? (I don't plan to root my phone, only install a custom ROM. It would also be good if I could keep my files, but if I can't, that's fine too.)
My original plan was the following, please take a look to see if i'll do things correctly.
1. Unlock the bootloader
2. Install TWRP immediately, before it even has a chance to restart
3. If TWRP asks for a password, skip and wipe all the partitions, if it doesn't, wipe them anyway to install the new ROM.
4. Backup efs and persist to my SD Card (will they even be there after I wipe the partitions?)
5. Right after that install the custom ROM
6. Reboot, not get into a bootloop and still have my IMEI. Profit.
Is everything right or did I misunderstand something?
Thanks!
Click to expand...
Click to collapse
Answer for your questions
1) losing of IMEI no is possible on custom ROM too, but taking the backup of EFS and persist will retrieve them, so no problem. And losing of IMEI is random occur when moving from one rom to other.
2) just let the android boot once, so everything get loads up with unlock bootloader (no need to setup).
3)after installing the twrp, it won't ask for password since your device got format when unlocking bootloader, so it won't ask. If you want to remove encryption then format< type yes. It will remove your encryption.
4) for talking backup of EFS and persist use this method.
Code:
Use the following command to create a backup and save it at /sdcard/persist.img:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
To restore use the following command:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
If you have saved a backup using different name then use that name instead.
And seeing your plan, everything seem good, you can continue with your plan.
Note:- for some user PE won't work for them with 2gb version, so I suggest you to take a backup of stock ROM or keep an other rom file in case it needed.