Related
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
kunal_07 said:
Ok, I messed up somewhere.
I had Nexus 6p running on MM, rooted along with xposed.
I had downloaded the beta OTA but not installed it.
I used flashfire to flash the old 6p image (the same one that was installed) and flashed system, boot, recovery, cache and vendor.
Then I updated using the downloaded OTA to N. When I did that , the phone showed me the corruption message and booted to recovery. My phone was being detected by adb in normal mode, but not by fastboot in the bootloader, somehow I was able to get it to detect and installed my older TWRP 2.8.7.2 recovery, which was able to decrypt data. After that, I sideloaded Android N via TWRP and even flashed TWRP 3.0.0.1, but it hangs whenever I try to boot to recovery, never been able to go past the TWRP bootlogo. Is there anyway I can get TWRP to work again without wiping data/userdata? I'm guessing it's all happening because of encrypted data.
Click to expand...
Click to collapse
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
Is there a reason you're messing around with Flashfire and sideloading instead of doing it the proper way via fastboot? I'd suggest taking that route now. I have instructions on flashing factory images in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
kunal_07 said:
I just had a phone next to me at that time, so I thought I'd be able to do it without a pc. Now I know it wasn't a good idea
So you suggest I fastboot flash everything like you've mentioned in the guide without formatting userdata and data? Also, should I flash twrp at that time as well? Do I need the modified boot mentioned in http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
Click to expand...
Click to collapse
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Heisenberg said:
Yes, flash everything except userdata. Personally, I'd be wiping data with TWRP first though, just to make sure there's no lingering data causing problems moving forward. You can use Titanium to make a backup of your user apps first, and then restore them afterwards. No you don't need the modified boot.img.
In response to one of your initial statements though, I don't think TWRP is hanging due to not being able to decrypt. The 3.0.0-1 build has been patched so that it can decrypt.
Click to expand...
Click to collapse
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
kunal_07 said:
any other way I can do that? I'm not rooted, and I cant flash supersu without booting to recovery, right?
Click to expand...
Click to collapse
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Heisenberg said:
Instead of relying on the recovery partition on the phone, you can live-boot TWRP with fastboot. This will boot into TWRP using the TWRP image on your PC, via the fastboot connection. The command is as follows:
Code:
fastboot boot twrp-3.0.0-1-angler.img
Then you can flash SuperSU, make your backup with Titanium, and continue on.
Click to expand...
Click to collapse
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
the log says:
E:Unable to decrypt with default password, you may need to perform a format data.
E:unable to mount storage
E:unable to mount settings storage during GUI startup.
kunal_07 said:
sorry to bug you often, but i had no luck with live booting 3.0.0-1. I tried with 2.8.7.2 and it booted, asked to decrypt data. tried my pin/pattern as well as default_password but no luck.
Click to expand...
Click to collapse
That's odd, I can't think of why 3.0.0-1 wouldn't boot, but 2.8.7.2 definitely won't work as it obviously can't decrypt. You might not be able to backup.
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
kunal_07 said:
Enabling 'require pattern at startup' allowed 3.0.0-1 to boot but this time it was stuck at decrypting.
Click to expand...
Click to collapse
I think you're pretty much stuck, you could try disabling all security.
is it possible to sideload supersu somehow?
kunal_07 said:
is it possible to sideload supersu somehow?
Click to expand...
Click to collapse
Maybe, you could try adb sideload in TWRP, but SuperSU needs to access the data partition which TWRP can't decrypt.
I tried it and it got to
**Boot image patcher**
patching sepolicy.
Failure, aborting.
i seem to have the same issues too. unable to access recovery and lost root. phone cant be detected in fastboot.
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Great news
1. Yes.
2. I don't think such a command exists. You'd need to use the "fastboot format userdata" command instead if you want to decrypt anyway. Just remember to backup all your data first.
3. You'd need to flash a custom kernel today doesn't force encryption. Otherwise your data well will automatically encrypt on the first boot after formatting.
kunal_07 said:
supersu 2.69 to the rescue. chainfire auto root worked with encrypted data
1)So, now the best way forward is to backup via Titanium and format data?
2) will fastboot erase data erase userdata as well?
3) after the format, will data remain decrypted or do I need to do something else?
Click to expand...
Click to collapse
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
kauemelhado said:
Is there a link for the CF Auto root?
I tried searching, but didn't find anything =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
kunal_07 said:
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
Click to expand...
Click to collapse
Tks,
I found it 2 seconds later I asked you. LOL
Anyhow, thank you bro.
Hey guys,
I unlocked my bootloader and flashed a recovery succesfully. When I entered into recovery mode, I enter into TWRP, get to install SuperSU, but when I reboot my device, it is stuck on "warning etc..."
What could I have done wrong? How can I fix this? Any help would be very much appreciated.
I have a MXP XT1563
I installed this TWRP http://forum.xda-developers.com/devdb/project/?id=11587#downloads
And this SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
I honestly can't remember what fastboot files I download, but I suppose it was ok since I got to enter my unlocking code and unlock it.
Thanks in advance.
Regards from Mexico
When I enter into TWRP and enter somewhere, for instance Install, I can see my folders: amazon, kindle, whatsapp, etc... I suppose that's good news.
I've tried doing a factory reset from Wipe, no sucess.
Please help! I will be uncommunicated until I solve this
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
bablu048 said:
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
Click to expand...
Click to collapse
hi bablu048, I did not "nandroid" before flashing su. I did it after I flashed it and when I try to restore it it says it's read only.
Do I download su 2.62-3, copy it into my storage and flash it again, no matter all I've done by now?
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
bablu048 said:
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
Click to expand...
Click to collapse
ok, this is what I did: I downloaded the su, put in internal storage, went into recovery mode, got into twrp, installed new su.
Now it gets past the warning, but gets stuck now in the water-ish motorola logo...
When I go into Restore, I can see two back ups, when I try to restore any of them, it says "cannot restore system - - mounted read only" and no option to modify it.
thanks a lot for your help! I'm trying to follow your every advice as best as I understand it
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
bablu048 said:
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
Click to expand...
Click to collapse
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
fsae3 said:
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
Click to expand...
Click to collapse
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
bablu048 said:
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
Click to expand...
Click to collapse
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
fsae3 said:
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
Click to expand...
Click to collapse
yes it will wipe,
that's the correct firmware. 6.0.1
always take a nandroid before flashing su 2.62-3
after flashing twrp again when you boot into twrp do "swipe to allow modifications to /system"..you didn't do this that's why you were not able to restore backups.
bablu048 said:
yes it will wipe,
that's the correct firmware. 6.0.1
Click to expand...
Click to collapse
hi bablu048,
I found in here a "unSu" guide. I ran it, it deleted Su, then ran Su you recommended and I still got suck in the watery logo.
Then I "unSu" it again, now didn't run any Su, reeboted device and it finally started.
I think su is the problem. Where can I check what su should I use?
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
bablu048 said:
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
Click to expand...
Click to collapse
Ok, I get it now. I backup my device with nandroid to make sure I have it there in case something goes wrong. If I have no info I want to save (my phone is blank, it's factory resetted from the bootloader unlocking) is it still necessary to nandroid? It's necessary in case a su fails right?
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.
bablu048 said:
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.try
Click to expand...
Click to collapse
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
fsae3 said:
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
Click to expand...
Click to collapse
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
bablu048 said:
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
Click to expand...
Click to collapse
ok, finally! My device is rooted. Thanks a lot!
I think I forgot to select external storage when taking a nandroid, so it went into internal storage, it filled a little more than 5 GB. I can't see this backup neither in TWRP, PC or an android file explorer. How can I get rid of those 5 GB? I take a nandroid on external storage and already copied it in my PC.
Is there a way via TWRP to get rid of it? Wiping something? I'm very cautios from now on.
it's stored at /data/media/twrp delete those backups. or boot into twrp >restore> it'll show all the backups delete those.
edit: Im stuck in the "watery logo" I need help unistalling SU can some1 point me to that guide?
I've already flashed SuperSU 2.62-3
edit 2: I flashed SU 2.65 and it did the trick! solved, i think
original post:
Hi guys hope you can help me
I have a XT1563, single sim. I unlocked bootloader, flashed recovery, went directly to TWRP to flash SuperSU v2.46, it finished, I restarted using TWRP option but hasnt restarted is stuck in the warning screen "Warning bootloader unlocked...your device's bootloader has been unlock...." I do not know what to do
I press power-off and any key combination and it doesnt do anything is just stuck at that warning screen. Unlike the OP I dont get the watery logo
I'm not sure what happened, I was flashing a kernel, and suddenly my device stopped booting, getting stuck at the OnePlus logo, with 'Powered by android". TWRP was installed, so I tried restoring a backup, but that didn't help. I tried flashing the stock 4.5.5 full zip, it would still stay at the OP logo screen. I tried wiping the phone, flashing the stock full zip, still stuck at boot. I tried going back to the stock recovery (I know, risky), and it succeeded in flashing, but when I boot to recovery, the screen just goes black, and I have to hard-reboot. I can however flash TWRP back, and it seems to work fine. When I look in the file manager on TWRP, I can see things in the system partition, but I still can't boot to it.
I'm starting to panic now, so any help would be appreciated.
To clarify, even doing fastboot boot OP5_recovery.img brings be to the black screen
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
s3axel said:
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
Click to expand...
Click to collapse
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
0xTJ said:
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
Click to expand...
Click to collapse
Please change the title of this thread to: "[SOLVED] Soft-Bricked OnePlus 5, TWRP works, but nothing else". That will help others who may get into a similar plight.
OK, I played with Titanium Backup and removed some Samsung apps like S health... Now I am stuck at boot loop and phone wont start. I am on stock rom 6.01 rooted. tried everything I could read:
- installed TWRP - did not quite work, gave me an error "is not seadroid"
- installed CWM - I can boot into it, but not much I can do to fix the boot, I tried wiping the partition cache and dalvik, but not help
- installed root again with stock recovery, nothing..
If I install the latest version of stock firmware, will I loose my app data? All I care about is to preserve my notes from ColorNote I read somewher that if a rom does not have userdata img, it wont wipe. Does the stock firmware have that? I am just looking for a way to get back in, backup stuff, and then reflash properly.
I tried going the adb route, but nothing there either. In cmd it says now unlock your phone for the pull command to compete, which obviously I cannot do.
Any other options to save my ColorNotes and Pictures?
OK, I was able to execute:
adb pull / C:\Myfile
This copied system files pretty much. How do I copy the app data or personal data - that's what I actually need
Got lucky...
I had to flash the latest stock firmware, but because I was running it anyway, just not the latest security patch, I the system ended up upgrading and all my files were preserved. It is as if I simply got the monthly patch.
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Pro4TLZZ said:
I had error 255 when restoring the data partition on my elephone p9000, for me it was because it was a bad data write and it was corrupt.
Click to expand...
Click to collapse
What was corrupt? How did you fix it?
keeganjk said:
What was corrupt? How did you fix it?
Click to expand...
Click to collapse
Something in the partition, so I didn't restore that
Pro4TLZZ said:
Something in the partition, so I didn't restore that
Click to expand...
Click to collapse
Which partition? I just wiped my device and reinstalled FreedomOS.
keeganjk said:
Which partition? I just wiped my device and reinstalled FreedomOS.
Click to expand...
Click to collapse
Userdata partition
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
OK.
Pro4TLZZ said:
Userdata partition
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
keeganjk said:
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
Click to expand...
Click to collapse
I'm sorry I can't help you more
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
What's the difference between TWRP and bluspark TWRP?
dago said:
Hi guy, i had the problem, try to flash blue spark recovery and retry restore, if rom bootloops, try to dirty flash your rom
Click to expand...
Click to collapse
I can't restore; I deleted all my backups in an attempt to free up space.
I think I found the solution!
1. Go to Wipe in TWRP, swipe to factory reset
2. Download:
OnePlus Recovery: http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
OxygenOS: http://oxygenos.oneplus.net.s3.amaz...3_OTA_015_all_1708252353_e6d7756780064352.zip
3. Rename recovery image as recovery.img, boot phone into fastboot, plug into computer, run these commands on the computer:
fastboot devices
fastboot flash recovery recovery.img
fastboot boot recovery.img
4. Open recovery on phone
5. Select Forgot Password, will wipe all leftover files in SD Card.
6. Boot back into recovery, select reload, select Install over ADB or Install Over USB or something similar and plug phone into computer.
7. Run 'adb sideload oxygen-os-filename' without quotes on computer.
8. Let it install OxygenOS, it may appear to be frozen at some points; it probobaly isn't, so don't shut it off or unplus USB.
9. Download Bluspark TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=26601&task=get
9. Reboot into fastboot, plug into computer and run these commands on the computer:
fastboot devices
fastboot flash recovery bluspark-twrp-filename-location.img
fastboot boot bluspark-twrp-filename-location.img
10. Success (hopefully)
Oh. Wait. Now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
the solution to this was to boot to your previous rom that u have made nandroid backup with and then setting up the same password/pin in settings > security. When you then boot into twrp it will ask you for the pin/password to decrypt your data partition and then you can flash the nandroid backup(you have to have the same password there). here it is obvious that you are trying to flash data partition that uses different encryption password (in case of stock rom there is non) and this obviously wont happen.
maybe another solution would be to connect externally usb and unmounting data partition and then restoring from usb...
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Need4Sneed said:
I'm having the exact same issue, but trying to create a Nandroid, not restoring one. Happened on Codeworkx TWRP 20180414. I always remove my passwords, fingerprint, pattern, and face data before I backup, update, etc. since I'm encrypted to avoid issues, and it still happened. I flashed the latest blu_spark TWRP and got the exact same error in the same spot in the data partition backup.
Never had an issue like this before. I even tried saving the data partition separately and still got the same error. Very strange indeed.
All other partitions backup without issue.
I'm on xXx v10.5 w/ ElementalX v3.04, Encrypted
If anyone has any insight, it would be greatly appreciated.
Thanks much!
?
Click to expand...
Click to collapse
For me flashing normal oxygenos with magisk 16 and formatting data and trying to make it boot with the new flash and then rebooting into recovery and restoring made it work. I guess it has to do with the right filesystem having to be made first.
hi guys,
i've read all the thread in XDA related to ERROR 255, can't find anything to solve my problem trying to backup on TWRP ending with this error 255.?
I'm not using any parallel apps, not using Apps Locker, don't have any folder 999 (searched using Root Browser).
I've tried deleting all fingerprint, face unlock and screenlock as well.
No joy.
I'm using latest TWRP 3.2.2-1, OOS 5.1.7, Rooted.
Appreciate any help or sharing experience.