What are the current ways to do a complete backup (similar to a system image backup on windows)? - General Questions and Answers

Now that I have my phone rooted, I want to start off doing a complete backup in case I screw something up down the line. Can someone give me a basic list of instructions needed? I want to have the backup stored both on the device and on my computer for redundacy. Also what would happen if I lost my device, could I get another identical model into a rooted state and restore the backup so I don't have to set up all the customizations/modules from the beginning?

Terrrabyte said:
Now that I have my phone rooted, I want to start off doing a complete backup in case I screw something up down the line. Can someone give me a basic list of instructions needed? I want to have the backup stored both on the device and on my computer for redundacy. Also what would happen if I lost my device, could I get another identical model into a rooted state and restore the backup so I don't have to set up all the customizations/modules from the beginning?
Click to expand...
Click to collapse
We usually use TWRP, but you didn't write what kind of device you have, so it's hard to point you to further help.

ze7zez said:
We usually use TWRP, but you didn't write what kind of device you have, so it's hard to point you to further help.
Click to expand...
Click to collapse
My device is a SM-S9180 S23 Ultra. My advisor said that this device isn't compatible with Nandroid or TWRP, is that correct?

Related

Most directions "how to root" seem to be from 2012...

On July 20th 2013, I bought a new Verizon Galaxy S3 i535 (no contract due to I need unlimited data). As a 50 year old guy, I admit that I never rooted before. I decided to do some research on the web which also included this XDA site. By the way, this is the best site!!
As someone who never rooted, I found multiple different ways of rooting which caused great confusion. Some told me to download Odin, while some did not. Some told me to download a superSU or something like that, while other directions did not, and so on and on......
But what really concerns me is that most of the directions were written back in 2012. Should this be a concern?
I don't want to seem like a retard or impose, but would someone do a video skype with me and walk me thru rooting my phone for the very first time? Perhaps during that skype session I could ask a few questions? I would pre download all files so that the session would not take too long.
Any volunteers?
Respectfully,
Bryan
All you need to Do is visit this link:
http://forum.xda-developers.com/showthread.php?p=42791826
Those are the most straight forward directions you can find. And it will Root, unlock your bootloader, and install a custom recovery.
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
BKSinAZ said:
thank you for the reply. this is yet another way off rooting. why does this not use Odin? will this method allow me to undo or fix something if something goes bad?
Click to expand...
Click to collapse
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
funnyperson1 said:
It doesn't use Odin because it doesn't need to. The one click solution includes all the tools needed to make the necessary changes to your phone.
If something goes wrong, then you would use Odin to go back to stock no matter what root /unlock method you used. This is because Odin has the lowest level access to your phone, and can rescue it as long as you can boot into download mode.
As long as you don't flash files intended for other phones (including s3s from other carriers) your phone should be safe.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
I'm going to pop in here and help out. Once you do the casual root process, it will also install a recovery for you. You can make a nandroid backup with your recovery and just keep that somewhere safe. There are also directions on how to recover and return your phone to Verizon here. Hope that answers your question.
BKSinAZ said:
Ok... here is one of my last questions before I begin the root process....
Do I need to make a backup of my stock phone? There are no pictures or music, but do I need to make a backup in anyway first so if things go bad I can return to stock?
Click to expand...
Click to collapse
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
funnyperson1 said:
No, as I said above, as long as you can reach download mode on your phone you can always Odin back to stock. If you somehow break download mode, then your phone is pretty much bricked without sending it out to someone with a JTAG programmer. The risk of that happenning though is minimal unless you flash a ROM intended for a different device (such as the international i9300 S3).
Click to expand...
Click to collapse
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
funnyperson1 said:
It sounds like you were successful in rooting and unlocking your phone's bootloader. The program you are seeing (TWRP recovery) allows you to flash roms/mods (install), backup your phone, wipe and restore your phone. However, this shouldn't be what you see on bootup unless you pressed volume up while booting. Your stock ROM may have been wiped during the root process.
I suggest you dive into the world of Custom ROMs with CleanROM which is basically a de-bloated and tweaked version of the stock ROM.
Download the file from here:
http://forum.xda-developers.com/showthread.php?t=1832070
Use your PC to put it on a microSD card. In TWRP recovery, perform a Factory Reset (from the Wipe Menu), then navigate to the external_sdcard and install CleanROM (from install menu). Wipe caches and reboot once installation is finished. You should boot straight into CleanROM.
Click to expand...
Click to collapse
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
BKSinAZ said:
OK... did exactly what you and the directions stated. Upon the phone booting up, there is a 'padlock' and the option to swipe. When I swipe, I am not as the home screen that I am accustomed to. I am in the Team Win Recovery Project" with the only option to 'select zip to install" and 6 buttons to press (install, backup, mount, advanced, wipe, restore, settings, reboot)
This was an unexpected step and was wondering what to do next?.... or did I mess things up?
Click to expand...
Click to collapse
If you're not ready to flash roms just touch reboot and you'll be back to your stock jellybean. In regards to the padlock, I also got that after using CASUAL and underneath the padlock it says custom. I haven't gotten a definitive answer about that but the general consensus is that it's nothing to worry about. I suppose it's just Verizon letting you know that they detected changes to your phone.
Do yourself a favor and read for days and days before you start flashing roms. You'll find the answers here and YouTube.
BKSinAZ said:
It seems that when I went into the backup area and made a backup (a backup of what, I do not know because I am totally new to this) and after the backup the phone rebooted to the normal home screen with all the normal icons. I even just received a phone call so I guess all is good.
I don't know what to do now that my phone is rooted. My goal was just to uninstall unwanted programs etc, So when I get the courage, I will use the CLEANROM.
Question.... do I now have to constantly update my existing root or Cleanrom once installed? Do I now avoid Verizon or Samsung updates?
Click to expand...
Click to collapse
Great. The backup you made is what is called a "nandroid" backup. By default it includes the Android System, your apps, and associated application data and settings. This is great because it basically includes everything you need to restore your phone to it's previous state. So if you were to flash a custom ROM and ended up not liking it you could always restore this backup and it would restore your phone to how it is now.
Being rooted allows you to install and use applications from the Play store that require root. There are tons of them. The one I use most often is called Titanium Backup. It's primary purpose it to backup and restore your data and applications on an individual basis. I use it mostly to save my text messages and game save data between ROM flashes. It also allows you to uninstall, wipe data, and freeze (disable) any application on your phone.
Right now since you are still running stock rooted, you want to avoid installing any official updates, otherwise you may have to re-root. Beanstown may have disabled system updates through the rooting method, but I am not sure. If a new update is released, keep your eyes on the forums here, someone will create a flashable zip of the new firmware that maintains root/unlocked bootloader, you can then flash that in TWRP. Also once you flash a custom ROM like CleanROM, they removed the Samsung Firmware updater most likely so you don't have to worry about it.

[Completed] Questions about backup / restore feature on twrp recovery nandroid

Hi guys,
I've got 60 phones to setup, and that's just the biginning. I looked for some solutions to mass deploy them, the fastest way possible. I of course already know titanium backup and applications like that, but i would prefer not to root phone...
I was pretty confident about a nandroid backup : flashing the recovery of the phone is really quick, and i would just have to backup on card or on usb on the go on the master phone, and to restore the backup on all the phone remaining. But it didn't worked as expected, it happens that on each phone, twrp is generating backup in a folder named something like "420khg66g6cca200" and which is different on each phone, and when you put the card in another phone, this one doesn't see the main backup.
I of course tried to sneak arround and generate a backup on the second phone, which i replaced with the content of the first one, but the phone doesn't even boot anymore.
I used twrp because i dind't find another recovery avaiable for the phone, which is by the way a samsung Xcover 3 also known as SM-G388F.
I tried to backup only system, system image, and data and to restore it and the phones is stuck on boot screens.
I tried to backup again with boot partition, same thing happen'd. There's something i don't understand tho, there's some warning about /system partition which can't be mounted when i look around on the recovery of the slave phone.
I'm on stock rom, no root. I looked for similar post (really), but there's mostly guys which make backup / restore on the same phone, and i didn't find my answer.
My questions are : is there someone's who did this before ? Why the phone doesn't boot anymore ? Is there something that's making the backup unrecoverable on another phone ?
In this case, is there anyway to bypass that ?
Thank you by advance.
chnateag said:
Hi guys,
I've got 60 phones to setup, and that's just the biginning. I looked for some solutions to mass deploy them, the fastest way possible. I of course already know titanium backup and applications like that, but i would prefer not to root phone...
I was pretty confident about a nandroid backup : flashing the recovery of the phone is really quick, and i would just have to backup on card or on usb on the go on the master phone, and to restore the backup on all the phone remaining. But it didn't worked as expected, it happens that on each phone, twrp is generating backup in a folder named something like "420khg66g6cca200" and which is different on each phone, and when you put the card in another phone, this one doesn't see the main backup.
I of course tried to sneak arround and generate a backup on the second phone, which i replaced with the content of the first one, but the phone doesn't even boot anymore.
I used twrp because i dind't find another recovery avaiable for the phone, which is by the way a samsung Xcover 3 also known as SM-G388F.
I tried to backup only system, system image, and data and to restore it and the phones is stuck on boot screens.
I tried to backup again with boot partition, same thing happen'd. There's something i don't understand tho, there's some warning about /system partition which can't be mounted when i look around on the recovery of the slave phone.
I'm on stock rom, no root. I looked for similar post (really), but there's mostly guys which make backup / restore on the same phone, and i didn't find my answer.
My questions are : is there someone's who did this before ? Why the phone doesn't boot anymore ? Is there something that's making the backup unrecoverable on another phone ?
In this case, is there anyway to bypass that ?
Thank you by advance.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
You can post your query Android Q&A,Help and Troubleshooting .You'll get support from the experts there
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
You can post your query Android Q&A,Help and Troubleshooting .You'll get support from the experts there
___
v7
XDA Assist
Click to expand...
Click to collapse
ok, sorry for the wrong category.

Most powerful backup possible

Hi,
I just want to know what the most powerful backup solution is.
I explain myself: I would like to do dangerous operations on my phone and I would like to have a much more powerful backup solution than a TWRP backup if one of these operations fails and my phone is hard bricked.
So I'm looking for a very powerful backup method that works even if tools like fastboot are broken.
If such methods do not exists, what is the nearest solution?
Thank you in advance for all the information you will be able to give me
Translated with www.DeepL.com/Translator
Except a nandroid backup with everything that it's in the phone (and so not a normal TWRP backup, but a full one with every partition available to be backed up in TWRP menu), i didn't understand exactly what kind of backup you're referring to. I suggest apps like Titanium Backup, MyBackup, Super Backup and similar ones to backup apps data also, but i think the TWRP backup is the strongest one.
RedSkull23 said:
Except a nandroid backup with everything that it's in the phone (and so not a normal TWRP backup, but a full one with every partition available to be backed up in TWRP menu), i didn't understand exactly what kind of backup you're referring to. I suggest apps like Titanium Backup, MyBackup, Super Backup and similar ones to backup apps data also, but i think the TWRP backup is the strongest one.
Click to expand...
Click to collapse
Thanks for your answer
I don't want to backup my apps and data, I want to backup every single partition of my phone.
Sometimes you can break you're phone very badly and even Fastboot can't recover it (recovery: dead, fastboot: dead, your phone: hard bricked). My request is There is a solution in this case to get back to live the phone with some kind of super-mega-backup software ?
siffrein said:
Thanks for your answer
I don't want to backup my apps and data, I want to backup every single partition of my phone.
Sometimes you can break you're phone very badly and even Fastboot can't recover it (recovery: dead, fastboot: dead, your phone: hard bricked). My request is There is a solution in this case to get back to live the phone with some kind of super-mega-backup software ?
Click to expand...
Click to collapse
TWRP can do just that, backup EVERY SINGLE PARTITION there is on your phone, and then restore them all.
But honestly if you brick your device that bad, I don't know if you will be able to boot TWRP to restore the backups...
Sent from my BLN-L21 using XDA Labs
Exactly, as i said. TWRP backup everything and you'll have the best phone image you can have. Just don't let your device explode

Can you fix EFS Partition?

Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Juwapa said:
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Click to expand...
Click to collapse
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video --> https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Mr.FREE_Bird said:
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video -->
&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Click to expand...
Click to collapse
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Juwapa said:
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Click to expand...
Click to collapse
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Mr.FREE_Bird said:
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Click to expand...
Click to collapse
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Juwapa said:
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Click to expand...
Click to collapse
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Mr.FREE_Bird said:
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Click to expand...
Click to collapse
So I finally had time to sit down and make backups of my device. I made a backup of just the EFS and Modem Partition only and I made another complete backup of everything. This should be all I need right?
And yes, I will keep the backups on my PC and on the flash drive I keep my current rom, recovery, kernel, and magisk on.
Shyciii said:
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Click to expand...
Click to collapse
I could be wrong, but I don't think I had KernelTweaks on to begin with. I keep reading people are having problems with it, so I think I'll just stop using it. And it wasn't reboots that were the problem, I only had the one reboot. The problem was my phone wasn't recognizing my sim card nor did it give me my IMEI number, which is why I thought I might of messed up the EFS Partition. But thank you for the reply.
I'm about out of options anyone tried using smt download mode on msm tool.? Then restoring efs partitions.? And had any success. I'm getting a sha 256 does not match error on msm tool when trying to download super partition. Op8 verizon bricked.

Question S22 ultra

hi, I need some info, is it possible to restore the phone which, when first turned on, lets you choose the language etc etc like when it's new without doing a restore? perhaps by deleting something
nobody can tell me
massimomax74 said:
nobody can tell me
Click to expand...
Click to collapse
What you are describing is the normal behaviour of an Android phone on first boot after reset (or when fresh from factory). There is nothing to restore, the phone is not yet set up and there is no data on it....
If the phone was indeed not new/reset: If you need some help it would be helpful to describe more in detail what happened, what you did to get there and/or what you are trying to achieve ....
Just my 2 cents
I agree with above post. What are you wanting to restore? In my opinion you will have to factory reset if you want to start from scratch. Unless your device is International and you are rooted with Twrp and you created a backup...then you would have something to restore.

Categories

Resources