I'm using OrangeFox recovery - when doing a backup, all partitions are visible (Boot, Cache, Recovery, Data, Vendor Image, System Image), except for "System".
Please help me fix it!
rossarnie said:
I'm using OrangeFox recovery - when doing a backup, all partitions are visible (Boot, Cache, Recovery, Data, Vendor Image, System Image), except for "System".
Please help me fix it!
Click to expand...
Click to collapse
Really! Have you even read the OrangeFox instructions on making backups?
DarthJabba9 said:
Really! Have you even read the OrangeFox instructions on making backups?
Click to expand...
Click to collapse
Thank you. Yes I have. It says that it's better to back-up "System image" than "System". I'm trying to understand why "System" isn't even in the list of my phone's partitions.
rossarnie said:
...I'm trying to understand why "System" isn't even in the list of my phone's partitions.
Click to expand...
Click to collapse
So that people who didn't read or understand the instructions cannot possibly try to make a backup of it?
Must you be so offensive?
Must you be such a dumbass?
Related
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!
So I just updated TWRP (3.1.0-7 ), converted to F2FS, and flashed the latest build of PureNexus.
When booting into TWRP to perform a backup, there seem to be duplicate partitions (specifically System and Vendor), whereas before this was not the case. Although if I go to the Wipe option within TWRP, there are no duplicate partitions listed. Is this an issue within TWRP or by design? or have I jacked something up?
[x] = Selected by default
[x]Boot
[x]System
System Image
Vendor
Vendor Image
[x]Data (excl. storage)
Cache
Recovery
EFS
jacksheadache said:
So I just updated TWRP (3.1.0-7 ), converted to F2FS, and flashed the latest build of PureNexus.
When booting into TWRP to perform a backup, there seem to be duplicate partitions (specifically System and Vendor), whereas before this was not the case. Although if I go to the Wipe option within TWRP, there are no duplicate partitions listed. Is this an issue within TWRP or by design? or have I jacked something up?
[x] = Selected by default
[x]Boot
[x]System
System Image
Vendor
Vendor Image
[x]Data (excl. storage)
Cache
Recovery
EFS
Click to expand...
Click to collapse
That's normal Bro. I think you misworded what you said. They aren't duplicates as one is the system and one is the image for the system and same for the vendor. I can't remember why that shows but maybe it is because f2fs works different than ext4 with partitions.
Thank you. Sorta kinda slightly almost assumed that was the cause, as I understand the system partition has a fallback (sure that's the technical term for it) So maybe it's the newer TWRP being more capable of showing these - as I do not remember seeing them on prior versions.
jacksheadache said:
So I just updated TWRP (3.1.0-7 ), converted to F2FS, and flashed the latest build of PureNexus.
When booting into TWRP to perform a backup, there seem to be duplicate partitions (specifically System and Vendor), whereas before this was not the case. Although if I go to the Wipe option within TWRP, there are no duplicate partitions listed. Is this an issue within TWRP or by design? or have I jacked something up?
[x] = Selected by default
[x]Boot
[x]System
System Image
Vendor
Vendor Image
[x]Data (excl. storage)
Cache
Recovery
EFS
Click to expand...
Click to collapse
Those have always been in TWRP for both 2015 Nexus devices.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Those have always been in TWRP for both 2015 Nexus devices.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You're wrong. Or I'm seeing things. More likely I'm seeing things.
Thank you
jacksheadache said:
You're wrong. Or I'm seeing things. More likely I'm seeing things.
Thank you
Click to expand...
Click to collapse
You are seeing things. The images have been there for years.
jacksheadache said:
You're wrong. Or I'm seeing things. More likely I'm seeing things.
Thank you
Click to expand...
Click to collapse
Hello, i think those are here since Nexus 6P release. Anyway, if you want a "proper" explanation of the difference between system/system image, here it is:
https://twrp.me/faq/whattobackup.html
Cheers...
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
anmolkakkar said:
I'd recommend you to completely wipe and flash Stock OOS from here : https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
That should sort all your problems related to partitioning. Let me know how it goes.
Click to expand...
Click to collapse
Already tried flashing the Full ROM earlier, but that doesn't fix the missing partition. Unless flashing with Stock Recovery would make a difference. Need a link to stock recovery to try that
Was looking into dumping partitions off a working OP5.
https://forum.xda-developers.com/showthread.php?t=2450045
Don't have a second OP5 (128GB) to dump partitions, but I did generate some .img files using this method. Optimally, flashing a proper userdata.img through fastboot should fix the partition, I believe.
aenews said:
I accidentally deleted the data partition. Everything else works fine including Recovery/Fastboot. Normally I'd be using the Mega Unbrick Guide to restore the partition, but not an option right now for the 5 (128GB). Assistance would be appreciated. Maybe flashing a userdata.img would work?
Click to expand...
Click to collapse
fastboot format userdata ?
Hastaloego said:
fastboot format userdata ?
Click to expand...
Click to collapse
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
aenews said:
The partition doesn't exist right now. It cannot be mounted or formatted. If someone could use the guide above and pull a userdata.img from a 128GB OP5, pretty sure that would restore the partition if I flash it in fastboot.
Click to expand...
Click to collapse
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Funk Wizard said:
You can also try restore the nandroid uploaded on my thread
Sent from Funk Tuned 3T
Click to expand...
Click to collapse
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Welcome buddy
Funk Wizard said:
Welcome buddy
Click to expand...
Click to collapse
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
try flashing the stock zip from twrp.
electronicghandi said:
So I managed to do the same thing, but with my system partition. I can't figure out what img to flash to system or where to get it from. Can anyone help me please?
Also, first thing I did was attempt to repair the partition via TWRP but no dice on that...
Click to expand...
Click to collapse
Restore the Nandroid
Sent from my OnePlus5 using XDA Labs
Worked for me to on a OnePlus 3
flame360 said:
Have you tried going into TWRP > Wipe> advance wipe > data >change or repair filesystem > change filesystem> ext4?
This should help.
Click to expand...
Click to collapse
That did it on my girlfriends OnePlus3 thank you very much!
aenews said:
Thanks that worked! And much simpler and faster. I didn't realize there was an easy way to repair the filesystem in TWRP (derp) but that's awesome.
Thanks for the tip!
Also I *think* I was able to extract a userdata.img after I fixed the partition. In case that's ever needed in the future...
Click to expand...
Click to collapse
Can you please share the userdata.img for 128gb and also fastboot image files for one plus 5t, my phone is dead please help
Hi. I accidentaly changed file system of data partition to EXT4 and now when I try to restore my backup I get a warning that the backup was done with f2fs file system. The problem is that TWRP is not showing up the f2fs option when I go to change file system menu. Any help?
Thanks!
I think you can restore the data anyway? I backed up my ext4 data partition, formatted it as f2fs and then restored the backup and it gave me the warning but it worked anyway. If it doesn't let you proceed, reflash TWRP and try again.
hernaner28 said:
Hi. I accidentaly changed file system of data partition to EXT4 and now when I try to restore my backup I get a warning that the backup was done with f2fs file system. The problem is that TWRP is not showing up the f2fs option when I go to change file system menu. Any help?
Thanks!
Click to expand...
Click to collapse
What ROM are you trying to restore, may I ask?
jeshanp said:
I think you can restore the data anyway? I backed up my ext4 data partition, formatted it as f2fs and then restored the backup and it gave me the warning but it worked anyway. If it doesn't let you proceed, reflash TWRP and try again.
Click to expand...
Click to collapse
Yes i could restore it but it worries me that I can't keep the original stock filesystem. I never changed it and I would like to have it as it was, there must be a reason it is f2fs and not ext4.
corlatemanuel said:
What ROM are you trying to restore, may I ask?
Click to expand...
Click to collapse
It is a stock backup.
Thanks for your replies.
I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
cyborgium said:
I tried creating a system backup through TWRP just now for the first time ever. Throughout the process, it gave me multiple messages saying "unable to mount data" and the same for some other folders, and when the backup supposedly finished, it just said failed.
Is there anything I can try without actually wiping either of the partitions? This obviously because I'm trying to create a backup so I can wipe afterwards.
Click to expand...
Click to collapse
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
spawnlives said:
In twrp main menu screen select ' Mount ' menu and make sure mount data is ticked then go back and try backing up again.
Click to expand...
Click to collapse
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
cyborgium said:
Thanks for your reply, it doesn't actually let me tick that box. Nothing happens when I tick it. It also says that the data partition is 0mb. Any idea what that might mean?
Click to expand...
Click to collapse
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
spawnlives said:
Which version of twrp are you using
Latest is 3.2.3.0 which should fix the data issue ( it"s a known issue).
Click to expand...
Click to collapse
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
cyborgium said:
That's the TWRP version that I've got installed.
I just reinstalled both stock firmware and reflashed TWRP but the exact same issue persists. At first I was able to mount data though, I could flash zips such as Magisk etc. But after having set everything up again on my phone, I couldn't mount data anymore.
Click to expand...
Click to collapse
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
spawnlives said:
Not sure on your steps to install twrp
Have you tried going into twrp in wipe menu and format data
Click to expand...
Click to collapse
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
spawnlives said:
Sounds like your device is still encrypted
Did you flash the no Verity encrypt zip file
Also I said to format data not wipe.
In the mount menu these are the options I have enabled.
Click to expand...
Click to collapse
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
cyborgium said:
You're right, I formatted data, not wipe.
I did flash the no verity zip, does the order in which I flash Magisk, no-verity and RMM state unlock matter?
Click to expand...
Click to collapse
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
spawnlives said:
The instructions I followed to install twrp
Flash twrp (which you have done)
Format data
When finished reboot back into twrp(use twrp reboot menu option)
Flash no-verity zip via twrp ( have to make sure you have it on internal storage or SD card)
Then flash everything else
Not sure if you need RMM state unlock if your bootloader(OEM) is already unlocked in developer options though.
Click to expand...
Click to collapse
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
cyborgium said:
I've just done everything you stated above, still the same issue, can't mount /data.
Really don't understand what it is that im doing wrong or if I'm even doing anything wrong..
Thanks for your help anyway though, appreciate it.
Click to expand...
Click to collapse
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
spawnlives said:
Just as matter of curiosity I use FX file explorer (root) in the menu filesystem it should tell you what format your data partition is mine or ext4. I have read that some people through twrp have changed it to something like ext3 and then back to ext4
Also this is the thread I used to install my twrp
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
This thread may also help you out
https://forum.xda-developers.com/ga...ment/fix-data-mount-fix-s8-twrp-oreo-t3769254
Click to expand...
Click to collapse
I think that second thread you linked may have done the trick.
At first it didn't seem to help, but when I tried it again after reflashing everything, I am now able to mount /data.
I'm still in the dark as to why this happened and hasn't happened to anyone else other than the person who created that file, but either way, thank you very much for your help.
cyborgium said:
Maybe I wasn't very clear.
I flash the stock firmware, set that up to enable OEM unlock. Then flash TWRP, wipe /data, flash magisk and other required zips (at this point, data is mounted). I then set that all up however I want, install apps etc.
If I want to create a backup after all that, it doesn't work cause of the unable to mount /data and /storage.
Click to expand...
Click to collapse
Try the modded twrp from nx thread