Hello everyone, I had to buy a new motherboard (6/128) due to a motherboard failure, before the motherboard failed, I made a TWRP backup (4/64), so as I mentioned in the title, can I install the 4/64 TWRP backup on the 6/128? Will there be a problem?
Note: I use translation, sorry if I misspelled it.
Which partitions did you back up?
Lucas Schmidt said:
Which partitions did you back up?
Click to expand...
Click to collapse
Hi, I backed up all the partitions. it didn't cause a problem when I restored it. I'm using it properly now.
note: never install an EFS backup.
SpectrumWolf said:
Hi, I backed up all the partitions. it didn't cause a problem when I restored it. I'm using it properly now.
note: never install an EFS backup.
Click to expand...
Click to collapse
Good job.
Related
So I flashed a very bad ZIP file that hard bricked my phone.
Now my phone has come from Repair Service and its motherboard (or so to speak Chip Card) has been changed. The phone's IMEI has also changed during the process. :silly:
I have a backup of a well working ROM that was made with phone before the chip card renewal. Can I safely restore the backup after I've rooted and installed TWRP to the repaired phone?
I assume the backup is very important (of the current Stock Rom) but can the backup be restored in a safe way?
Assuming they didn't hack together some other phone's motherboard into your phone (not likely at all), then yes you can restore the backup. Your IMEI doesn't matter. Anyone can restore a backup from the same kind of device.
You'll likely have to do any kind of backup first (modem is fine), then move your of backup into the folder it created.
Sent from my VK810 4G
EiNESTEiNi said:
So I flashed a very bad ZIP file that hard bricked my phone.
Now my phone has come from Repair Service and its motherboard (or so to speak Chip Card) has been changed. The phone's IMEI has also changed during the process. :silly:
I have a backup of a well working ROM that was made with phone before the chip card renewal. Can I safely restore the backup after I've rooted and installed TWRP to the repaired phone?
I assume the backup is very important (of the current Stock Rom) but can the backup be restored in a safe way?
Click to expand...
Click to collapse
can you guide me from where you changed your motherboard? mine is hard bricked too.
EiNESTEiNi said:
So I flashed a very bad ZIP file that hard bricked my phone.
I assume the backup is very important (of the current Stock Rom) but can the backup be restored in a safe way?
Click to expand...
Click to collapse
Only if you don't restore EFS, misc and other phone-unique partitions. tz, rpm, data, system and cache are ok.
EiNESTEiNi said:
So I flashed a very bad ZIP file that hard bricked my phone.
Now my phone has come from Repair Service and its motherboard (or so to speak Chip Card) has been changed. The phone's IMEI has also changed during the process. :silly:
I have a backup of a well working ROM that was made with phone before the chip card renewal. Can I safely restore the backup after I've rooted and installed TWRP to the repaired phone?
I assume the backup is very important (of the current Stock Rom) but can the backup be restored in a safe way?
Click to expand...
Click to collapse
How did you make the backup? TWRP or Nandroid Backup
itsbighead said:
How did you make the backup? TWRP or Nandroid Backup
Click to expand...
Click to collapse
Not trying to be picky, but, a TWRP Backup is a NANDroid Backup. I think you may mean; How did you make the Backup? TWRP or CWM Recovery? TWRP and CWM have similar feature sets, and there’s little practical difference between them. They do have different user interfaces and are not compatible with one another. A Nandroid backup made on one cannot be restored using the other.
Backup restored - followup question.
573v3 said:
Not trying to be picky, but, a TWRP Backup is a NANDroid Backup. I think you may mean; How did you make the Backup? TWRP or CWM Recovery? TWRP and CWM have similar feature sets, and there’s little practical difference between them. They do have different user interfaces and are not compatible with one another. A Nandroid backup made on one cannot be restored using the other.
Click to expand...
Click to collapse
I did the Nandroid backup with TWRP.
I did take the risky method and decided to Restore the backup "as is" (every partition of the made backup).
It definately took some time to boot and also on initial boot the cell phone signal from carrier wasn't being received until about a minute had gone. After that though everything has worked as it should 100%. :angel: I did have a lot of setup done in the backup and that was the main reason I wanted to get the phone state back to what it was (before sending the phone to service). On the side note I would have definately been very pissed off had I bricked the phone again when I restored the previous backup. :cyclops:
I did a backup of the stock firmware before restoring the previous backup (= old "chip card's backup" or better said the backup made with phone having different IMEI code) and now I'm wondering whether of not I should restore some specific partition of that stock backup with TWRP. I quess the old saying "if it ain't broken don't fix it" applies here. Would be interesting to know if someone has better knowledge concerning this.
I absolutely recommend the if it ain't broke, don't fix it angle. It's unlikely that your TWRP backup contained any partitions that weren't safe to restore on your new phone.
Sent from my VK810 4G
roirraW "edor" ehT said:
I absolutely recommend the if it ain't broke, don't fix it angle. It's unlikely that your TWRP backup contained any partitions that weren't safe to restore on your new phone.
Sent from my VK810 4G
Click to expand...
Click to collapse
+1 :good:
I have no mobile network and while I wait for the firmware to download from filefactory, does anyone have an EFS backup who is on the RETEU software channel?
If someone had one from RETBR would be good too, I have the same problem as you, I lost my IMEI don't exactly how but I think it had something to do with the EFS
In the meantime I've been going down the QPST route to restore my IMEI with no success. I have thw two IMEIs set to 0, so a TWRP backup + IMEI editing should work well if anyone could upload one for us.
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
kkarora said:
can anyone backup their "efs" and upload it here so that i can restore it and get back my imei.
plzzz. needed indian efs
Click to expand...
Click to collapse
You may as well give up
Sent from my XT1635-02 using XDA-Developers Legacy app
Unfortunately it doesn't work like that. It's either a motherboard replacement from Motorola or a new phone. Sorry, but I learnt the hard way. (£120 mobo replacement) Don't use the chinese TWRP.
Really_Rekt said:
Don't use the chinese TWRP.
Click to expand...
Click to collapse
Do you know what action did the problem? For me the Chinese twrp works fine.
But there are two Chinese twrp! One from the all-in-in guide, and I've from another thread. Both are same version, but different in size. Having a look at both, I'm using the one from the all-in-one thread (don't remember why but I found it to be better). Maybe you had problems with the other?
Hello what have you done to lose the imei? thank you very much
regards
tag68 said:
Do you know what action did the problem? For me the Chinese twrp works fine.
But there are two Chinese twrp! One from the all-in-in guide, and I've from another thread. Both are same version, but different in size. Having a look at both, I'm using the one from the all-in-one thread (don't remember why but I found it to be better). Maybe you had problems with the other?
Click to expand...
Click to collapse
I accidentally wiped my efs partition with it. I think the one from the original rooting guide thread.
tag68 said:
Do you know what action did the problem? For me the Chinese twrp works fine.
But there are two Chinese twrp! One from the all-in-in guide, and I've from another thread. Both are same version, but different in size. Having a look at both, I'm using the one from the all-in-one thread (don't remember why but I found it to be better). Maybe you had problems with the other?
Click to expand...
Click to collapse
Do you use alberto's? Thank you
regards
No but everyone should from now on. He told me his recovery has no risk of efs wiping
Really_Rekt said:
I accidentally wiped my efs partition with it.
Click to expand...
Click to collapse
If you really tapped efs, then wipe, it is not the problem of the twrp. Thought it would misbehave in some way. It is a really bad idea to change anything on efs partition, but a recovery is not intended to prevent you from doing things you shouldn't do.
TWRP doesn't normally have access to the efs partition. That's why Alberto's one has no risk of wiping it.
Really_Rekt said:
TWRP doesn't normally have access to the efs partition. That's why Alberto's one has no risk of wiping it.
Click to expand...
Click to collapse
Hello then with the one of alberto you can do wipes format and restore nandroid backup without any risk? Why did some people say they lost it by installing their own firwmare via rsdlite or fastboot? I feel my English
regards
iron maiden said:
Hello then with the one of alberto you can do wipes format and restore nandroid backup without any risk? Why did some people say they lost it by installing their own firwmare via rsdlite or fastboot? I feel my English
regards
Click to expand...
Click to collapse
I restored from nandroid with alberto's twrp, there is no problem
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
mr.banana said:
Hi everyone. My phone doesn't boot up after restoring twrp backup. Yesterday I made a Full backup and now if I try to restore that my phone just go into a bootloop. How can I resolve this problem?
Click to expand...
Click to collapse
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
indian84 said:
It depends on a lot of factors.
What ROM, what TWRP version, what partitions did you back up, etc.
If you want to get your phone working, you can flash any ROM of your choice from TWRP or restore stock image.
Click to expand...
Click to collapse
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
mr.banana said:
TWRP Version is the last one (I think). I backup every partition so I made a full backup of everything. The rom Is the simple aosp. I very want back all my stuff
Click to expand...
Click to collapse
Backing up all the partitions was the mistake.
Getting your stuff back looks difficult.
If you flash ROM using TWRP, your media files and anything stored on your phone won't be deleted.
But all your apps and stuff will be lost.
Has anyone been able to restore a TWRP backup recently?
I have TWRP 3.2.2.0 and it does not seem to be able to restore the backups made by itself?
xclub_101 said:
Has anyone been able to restore a TWRP backup recently?
I have TWRP 3.2.2.0 and it does not seem to be able to restore the backups made by itself?
Click to expand...
Click to collapse
What partitions are you trying to restore?
xclub_101 said:
Has anyone been able to restore a TWRP backup recently?
I have TWRP 3.2.2.0 and it does not seem to be able to restore the backups made by itself?
Click to expand...
Click to collapse
I have backed up and restored a few times. It seems if I restore to the same slot I backed up on I don't get that internal error. So far so good
Badger50 said:
What partitions are you trying to restore?
Click to expand...
Click to collapse
It does not seem to be able to get that far in the first place - when entering the restore menu it is not even able to find the backups - it seems to not be able to recognize folders (created by itself and/or TWRP 3.2.1-2) of the type
1970-05-07--02-18-11_OPM2171019029
1970-06-08--04-10-46_OPM2171019029B1
1970-07-19--11-15-21_OPM2171026006H1
HI all, so I accidentally flashed the persist.img from my oneplus 7 pro onto my oneplus 9 pro, and the fingerprint sensor won't work anymore. Does any one have a persist.img backup that I could have to fix my phone please and thanks.
Just backup your and use the msm to restore everything.
Why were you touching persist in the first?
harpin14789 said:
Just backup your and use the msm to restore everything.
Why were you touching persist in the first?
Click to expand...
Click to collapse
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.
dej1i said:
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.
Click to expand...
Click to collapse
You should have a backup on the other slot if you remember which slot you flashed the wrong persist to. Then you can restore that. How did you not take a backup of your persist
Here is my persist. Flash at your own risk
harpin14789 said:
Here is my persist. Flash at your own risk
Click to expand...
Click to collapse
Thank you!!
dej1i said:
I tried msmtool already. It didn't restore the persist.img cause my fps is still broken.
Click to expand...
Click to collapse
hm, msm tool would definitely flash a new persist, it repartitions the phone and flashes completely back to stock, so that's odd that it didn't work for you.
harpin14789 said:
Here is my persist. Flash at your own risk
Click to expand...
Click to collapse
It won't do anything for him. Persist partition is encoded to be specific to device.
Bummer.
I just backed up my persist and modem partitions today using Wanam's Partition Backup.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
I'd share but it sounds like it wont help.
I'm TMO if it matters.
Persist.img
Burt Squirtz said:
It won't do anything for him. Persist partition is encoded to be specific to device.
Click to expand...
Click to collapse
That's what I told him as well, but he still seemed to want to try so I let him try and see. I don't think msm seems to help either. Might need to send phone to device to get it restored.