NM: I've was able to flash 10.3.4...but my internal storage got wiped out. It's saying I have 105GB of 108GB free...I have backups but my backup is corrupted since I forgot to remove my security pattern...oh well...
just4sc said:
HI!
I tried looking in the 255 error thread but couldn't find a solution and was thinking maybe it has something to do with the -32 version of TWRP so I went to the TWRP thread but no answer so here I am hoping someone here can help.
I made a backup however I found out later that I had forgotten to remove my security pattern prior to backup. Don't know if that's the issue but upon doing a restore I'm getting the dreaded 255 error. I also forgot to run magisk uninstall and don't know if that's the issue too (yeah, not a good idea to be working on stuff like this in the middle of the night and lacking sleep).
I haven't rebooted yet fearing I won't be able to get in.
I have since tried running the magisk uninstall (gave me an error - didn't write it down and now I can't see it anymore).
Tried installing magisk again (installed ok).
Install 10.3.4 ROM and that went ok.
Still not rebooted - thinking the install of 1.0.3.4 might have solved my problem I reinstalled TWRP -32 and then tried restoring my backup again. Of course I still have the 255 error.
I hoping someone has gone down my path or have some advise so that I can restore my backup.
Again, I still haven't rebooted yet so maybe that's my issue?
Edit: So, I rebooted and it gives me a crash dump. I can get into TWRP still but tried flashing the full 10.3.4 rom and it completes but it just goes into the crash dump again. I noticed while looking at Filemanager in TWRP all the filenames in storage are jumbled. Does that mean the encryption is messed up and I am hosed? I've tried searching but there's just so much information I'm a bit tired and am hoping someone point me to the right direction and maybe let me know if I can still recover. Thanks
Click to expand...
Click to collapse
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Yes you have to format data
Forget the backup it's useless
Format Data install 10.3.4 and magisk to both slots and your back in business
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks!
Related
I I have a Galaxy S4 with KitKat 4.4.2 and TWRP installed. I have been using Nandroid for backups.
Today I (stupidly) deleted the CSC.apk file with Uninstall and the phone started acting really strangely. I tried restoring the CSC app but it wouldn't do it (I tried multiple times). So I booted into TWRP recovery mode and did a full restore which worked fine...until I rebooted the phone.
I have quite a few apps that continually crash with:
Unfortunately, (App Name) has stopped
and then all I can do is tap the OK button. After tapping OK the errors popup continuously.
Is this normal? How can I fix this without reflashing the phone? This is my first restore ever done with Nandroid Any ideas? Annoyingly I also lost the activation for my GPS app (CoPilot). I thought Nandroid was an exact clone/backup so when you screw the phone up you can restore back to EXACTLY how the phone was when the backup was done?
Anyway, appreciate any help or thoughts on how I can get my apps to work without the constant stopping popups!
Thank you!
Can anyone help please?
Go back into recovery and wipe both the regular cache and dalvik cache.
As to the lost CoPilot activation, you'll need to contact CoPilot, then explain the situation to them, and they should be able to help you.
Strephon Alkhalikoi said:
Go back into recovery and wipe both the regular cache and dalvik cache.
As to the lost CoPilot activation, you'll need to contact CoPilot, then explain the situation to them, and they should be able to help you.
Click to expand...
Click to collapse
Thanks! I tried that but after wiping both caches and rebooting the phone and entering my SIM PIN, I am still constantly getting the "Unfortunately, (App Name) has stopped".
Is there anything else I can try? I'm a but confused by this as I thought Nandroid was an exect image of the phone! I'm not worried about CoPilot at all but the rest is important
Do a factory reset from within TWRP, then restore from the nandroid backup. How old is this nandroid?
Strephon Alkhalikoi said:
Do a factory reset from within TWRP, then restore from the nandroid backup. How old is this nandroid?
Click to expand...
Click to collapse
I'll give that a try tonight. I am running Nandroid 4.4.5 and the backups were created about a week ago.
Many thanks for your help!
BB007BB said:
I'll give that a try tonight. I am running Nandroid 4.4.5 and the backups were created about a week ago.
Many thanks for your help!
Click to expand...
Click to collapse
So I tried doing a factory reset from TWRP and then doing a Nandroid restrore but after rebooting the phone I was still getting LOTS of errors with applications not working. Even the firewall wouldn't work as it couldn't find the config file.
I don't get it, I thought Nandroid made an EXACT image of your phone so if something went wrong and you performed a restore, your phone would be back to a working state?
BB007BB said:
So I tried doing a factory reset from TWRP and then doing a Nandroid restrore but after rebooting the phone I was still getting LOTS of errors with applications not working. Even the firewall wouldn't work as it couldn't find the config file.
I don't get it, I thought Nandroid made an EXACT image of your phone so if something went wrong and you performed a restore, your phone would be back to a working state?
Click to expand...
Click to collapse
It does, but your backup can get corrupted.
Recipe:
TWRP 2.8.7.2
TWO Nexus 6Ps on 6.0.1
One N6P systemless rooted
Official Android SDK (fastboot)
So I got a replacement N6P from Fi as I noticed some slight bending on my original, and I was working on moving my data over using TWRP so I could keep all my app data, etc. When I backed up my original 6P, I forgot to remove screen and boot security, so when I flashed on to my new 6P, I was locked out (as expected, known bug). I tried this fix to get in to my system, and it worked! I was able to log in. However, I noticed that my old fingerprints were still enrolled and I wanted to start those fresh, so I tried to remove them. When I selected "Delete" for each enrolled fingerprint, nothing happened. This was the first clue. I then tried to enroll new fingerprints and got the following message:
Code:
[B]Enrollment was not completed[/B]
Fingerprint enrollment didn't work. Try again or use a different finger.
The other odd thing is that on the lockscreen, I was getting a red text error message that read something like "Fingerprint hardware not available."
So I figured something got messed up security wise from the fix I tried after flashing a locked nandoird. I then went back and made a new nandroid backup (boot, system, data) on my old phone making sure that all security was turned off. Same thing!
Wondering if the hardware did actually get messed up somehow, I flashed back to official stock 6.0.1 from Google. Fingerprinting then started working!
So nothing I have done since then has made any difference when trying to restore my userdata from my old phone. I've tried wiping cache/dalvik, and removing the locksettings.db file, but these didn't change anything either.
Has anyone had this issue before? It seems really bizarre to me. I'm probably going to end up flashing stock and restoring userdata via TB, but that is a headache compared to nandroid so if possible I'd like to get this to work.
Tried wiping userdata then flashing userdata from my old 6P and that did not work either.
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
DanielF50 said:
Have you tried wiping data, setting up the device again, and then checking if you can add a fingerprint?
I tried restoring data from a device I had to RMA too, and got that exact message every time - I gave up in the end as I tried wiping everything but the only thing that worked was clearing userdata & restoring my apps from the nandroid via TiBu.
All in all, I presume it's something to do with the fingerprint scanner having a different hardware key/serial to the new one and retaining that info somewhere in the data partition when you back it up.
Click to expand...
Click to collapse
Yup I did try that, didn't work either. I'm right where you were too, currently restoring apps for TB. Your hypothesis seems plausible to me, I hadn't thought of that. Kind of a bummer for swapping devices if that is the case. I wonder if we could find where the fingerprint key is stored in userdata and back it up prior to flashing the nandroid?
Thanks for the reply!
No problems & yes, it is, though I presume it's either been done for some sort of security, or as a complete oversight - I can't see Google deliberately doing so, especially on a Nexus device.
I think it's probably highly likely that someone will find the hardware/serial file soon and find a way to stop it from being overwritten when TWRP restores the data partition, though it is annoying that it hasn't been discovered yet... Thankfully restoring from a nandroid through TitaniumBackup isn't too bad nowadays!
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
erikem said:
Srry for necro but I think I might have found a workaround solution to this problem or at least the problem which is very similar to this one. Please check "symptoms" in the description of the solution to make sure we are talking about the same issue.
Here's the link to the solution: http://forum.xda-developers.com/showpost.php?p=68374321&postcount=1446
Click to expand...
Click to collapse
Sorry for another necro, but this doesn't work for me on Android 7.1.1
Edit: Correct fix here: https://forum.xda-developers.com/showpost.php?p=68199207&postcount=9
Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.
boostin91tsi01 said:
Hello All!
Before you tell me to search or check threads, I already have. This problem does not have anything to do with forgetting to disable the pins and fingerprints before backing up. My problem has do do with I have already disabled/removed security before backing up my nandroid. I check/select everything that I can to backup and it successfully completes. When I go to restore, everything looks to be properly restored, but alas, there is a problem. When I reboot, it asks me for a password to get into TWRP (apparently "default_password). But when I get in and go to file explorer to find anything, my entire storage is wiped. Like no OS or any files. The only other issue I've had besides this is when restoring a nandroid, it doesn't complete and reboots to a bootloop.
I am on the newest version of TWRP, 3.0.3-0. Any help would be greatly appreciated as I, and anyone who has had to redo the complete phone setup/customization, do not enjoy taking over an hour to get things back up and running. Cruddy thing is I did a Titanium Backup for my apps and settings, but they got wiped.
Click to expand...
Click to collapse
I am genuinely interested in this because I back up on a regular basis after each security update but I have never had to restore. Now it is my understanding that even if security is disable the data is still encrypted. Perhaps I'm wrong about that but if you ever did have a password or pin to log into the phone with have you tried to enter that into TWRP?
Sent from my Nexus 6P using Tapatalk
You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html
redduc900 said:
You only need to back up the defaults... system, data, and boot.
What should I back up in TWRP?
https://twrp.me/faq/whattobackup.html
Click to expand...
Click to collapse
I understand the web is full of opinions, but I've read somewhere to backup EFS? I have also read somewhere before that what you said to backup, while is plenty sufficient, if you have space, to backup everything. I followed that and it lead me to an hour plus of restoring back to how it was. I will give it a go, hoping that I never have to use it, but it will work when the situation arises.
I've only ever backed up those three partitions, and never had an issue with restoring backups. You can certainly create a backup of the EFS/IMEI, but keep it stored in a safe place like on your computer or a thumb drive. One thing I should note is when restoring a backup, make sure to also flash the correct vendor.img if necessary.
I usually backup vendor with it but as earlier indicated I don't believe it's completely necessary. As far as EFS is concerned yes I would agree with backing that up however what I do is back it up to a separate backup folder and only write it if something were to ever happen to it otherwise leave it alone. That way you don't take a chance I'm corrupting something in that partition.
Sent from my Nexus 6P using Tapatalk
I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.
jhs39 said:
I've never successfully restored a backup on the Nexus 6P regardless of what version of TWRP I used. Different builds of TWRP give me different problems but none has ever worked. I've completely given up doing nandroid backups on this phone because it's a waste of time and disc space. I never had a similar issue on any other phone that I have ever owned and am not a newbie when it comes to rooting and custom roms. What I always ended up doing after a problem restoring a backup is flash the complete factory image using the flash-all.bat command and start over with everything I want to flash.
Click to expand...
Click to collapse
I have the same problem, so now I've started doing a TiBU and Verizon Messages backup, after all those are completed, transfer and save it to my PC. If I have any problems, I transfer from the PC to phone and it's less headache... kinda sorta.
Restore never worked to the fullest. I tried different versions of TWRP, same problem. Restore starts a red error line in beginning of the restore process an at the end it shows ‘Restore complete’. When I restart, everything looks restored but with bugs like:
-network or sim itself is not shown
-Bluetooth, wifi wont connect
-Quicksetting tiles not responding etc…
The idea of backing up via TWRP is to get every bit RESTORED properly, but it doesn’t work.
I take a full back up before moving to update the firmware version (example MIUI 10), if I do not like the firmware then I want to go back to the previous firmware version (example MIUI 9) and TWRP RESTORE feature never works. I have to again flash the rom and then restore everything via Titanium backup.
I always take a TWRP backup of all the items available:
System
Data
Cache
Cust
Recovery
Boot
EFS
Persist
Still it never restores properly. It’s a mere time waste or the restore option to be removed from TWRP as it never worked across of its versions.
Can anyone explain me in a line, what is Cust, EFS and Persist?
I really appreciate if anyone help me understand where I’m going wrong.
Hey guys,
So I just got my OP5 today... the first thing I did after taking it out of the box was unlock the bootloader (obviously). I then installed TWRP so I could backup my stock image. Since then I've been fighting with my phone all day because my apps say I don't have an SD card. 1) I can't download apps, 2) I can't take pictures 3) I can't create a folder on my internal storage with the file manager.
I have tried wiping system and wiping data. ( I'm currently on FreedomOS rom since I wanted to try wiping everything ) The weird thing is I was able to download ES file browser, Root Checker, and Titanium backup before the SD card stopped working. Is there any way I can try to fix this??? Kinda worried I received a defective unit.
you need to wipe data then reboot you will find the problem is fixed
予而不语 said:
you need to wipe data then reboot you will find the problem is fixed
Click to expand...
Click to collapse
Unfortunately I tried this a few times to no avail. Fortunately for anyone else with this problem I think it's fixed. After wiping I ran Fix Permissions in TWRP... that seems to have done the trick. I'm up and running now, no bugs. Thanks for the input!
Blackdrag said:
After wiping I ran Fix Permissions in TWRP... that seems to have done the trick.
Click to expand...
Click to collapse
sounds to me you somehow erased your data partition and didnt wiped/format it.
you are not the first one with that problem: https://forum.xda-developers.com/showpost.php?p=72807646&postcount=8
maybe a twrp or bootloader unlock problem ?
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
yosry said:
if this not the right section kindly link me to the correct section
Yesterday my wife's phone capacitive buttons stoped working on OXYGEN OS 9.0.0 OP5
so i tried downloading from oneplus site the latest update and i have ended downloaded 8.1.0 instate of 9.0.2
and i flashed it locally but unfortunately things got worse and every thing stopped working wifi, launcher, apps, google, almost every thing stopped working and i realized what i just did
then i have searched for 9.0.2 from external website and downloaded and installed locally on op5 and things was good buttons came to work and every thing was fine except one little issue the contacts app and phone app is not working any more even i tried to install google contact with no luck
after every update i have wiped cash and rebooted
kindly advice and any help will be appreciated
Click to expand...
Click to collapse
Try wiping cache and data on those two apps from settings/apps
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
yosry said:
Already tried no change and i forgot to mention that in sync setting contracts showing (something went wrong)
Click to expand...
Click to collapse
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
strongst said:
Oh, you've downgraded 9.0.0 to 5.1.7 and then updated to 9.0.2
That isn't a good idea... Anyways, let's see how we can help you.
Is your wife's phone rooted and has unlocked bootloader and TWRP? Anything?
Click to expand...
Click to collapse
Nope its not rotted
And if there is a way to avoid rooting would be better
yosry said:
Nope its not rotted
And if there is a way to avoid rooting would be better
Click to expand...
Click to collapse
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
strongst said:
So it also means the bootloader is NOT unlocked and you don't have a twrp recovery installed?
Click to expand...
Click to collapse
Right
yosry said:
Right
Click to expand...
Click to collapse
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
strongst said:
You can reboot to stock recovery and wipe cache and reboot. Let's see if it works.
Click to expand...
Click to collapse
Done no change i mentioned in the 1 St post that i cleared cache after every install
yosry said:
Done no change i mentioned in the 1 St post that i cleared cache after every install
Click to expand...
Click to collapse
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
strongst said:
I'm sure the issue is cause of down and updating in a dirty way. You can maybe try again install 9.0.0 then 9.0.2
Otherwise a factory reset is the next option you should consider cause there's no way to wipe separate partitions or backup anything with stock recovery and without root or external help.
Click to expand...
Click to collapse
Ok i will try to install 9.0.0 then 9.0.2 again lets see if it will work thanks
Hey there i tried downgrading to 9.0.0 then to 9.0.2 with no luck leaving me with no choice but to factory reset and thankfully it worked eventually after talking a backup
So thank you all guys for support and appreciate your help