Error=255 - Zenfone 2 Laser Q&A, Help & Troubleshooting

Update : sorry, I solved it. Not sure what happened but the 4th time trying completed the restore with no change in twrp. Go figure.
I searched for help on this but I'm not finding an answer.
I tried to restore my stock nandroid backup yesterday after being on RR nougat build (great build as well as cm14.1 but I had a few glitches that I want worked out before I make it my main rom). I had previously restored with NO problems at all but when I tried to restore I got through most of the process then was given an "error=255". I don't have a complete log so if that helps to solve this, I will try again and grab it. The only thing that is different other than the new rom is that I updated to twrp 3.0.2-5 from the 3.0.2-4 that I made the backup with. Should I revert back to that twrp then try to restore?

Related

[solved]can not restore after efs corruption (online nandroid/twrp)

hi !
i ran into a problem and i couldn´t find a working fix(if any) by myself, hope the community can help.
i had an issue with corrupted efs. i was able to restore efs from an older backup i made with twrp - phone is working again.
i then restored my latest backup which is made with the online nandroid backup app.
it restores but all my apps, settings - everything beside custom boot animation is gone.
when i open the backup in the nandroid backup manager manager, i am able to restore apps manually, so they are present in this backup.
in twrp, normally it says "backup completed". this does not happen, at the end of the process the ui resets(teamwin splashscreen showing) but no error is shown.
already wiped, flashed stock rom and twrp again with odin.
thanks for helping
A.N.Droid said:
hi !
i ran into a problem and i couldn´t find a working fix(if any) by myself, hope the community can help.
i had an issue with corrupted efs. i was able to restore efs from an older backup i made with twrp - phone is working again.
i then restored my latest backup which is made with the online nandroid backup app.
it restores but all my apps, settings - everything beside custom boot animation is gone.
when i open the backup in the nandroid backup manager manager, i am able to restore apps manually, so they are present in this backup.
in twrp, normally it says "backup completed". this does not happen, at the end of the process the ui resets(teamwin splashscreen showing) but no error is shown.
already wiped, flashed stock rom and twrp again with odin.
thanks for helping
Click to expand...
Click to collapse
Which variant do you have?
donalgodon said:
Which variant do you have?
Click to expand...
Click to collapse
it´s the international 9005, snapdragon.
i use x-note 6.0 rom.
problem solved.
it didn´t have anything to do with the efs corruption.
all online nandroid backups i made were faulty.
tried several things to make it work.
seems like reinstalling busybox finally fixed it.

[Q] Restoring from backup

Hello,
I'm running TWRP v2.8.4.0 on a G900T. Before testing out my first custom rom after rooting the device I made a full backup through TWRP. I was having some difficulties with the ROM I chose and decided to restore my backup so I could use my phone still while figuring things out. Unfortunately, after restoring the backup file through TWRP and rebooting I am receiving crash report after crash report of a long list of apps.
I tried searching the forums but no such luck with the wording that I've used for a fix.
I've tried disabling MTP and Fixing Permissions (without the "SELinux contexts" option) after doing another factory reset (Wiping Data, Cache, and Dalvik.
If there is anything else that I could try or read up on that would be great. Thank you!
**Update**
The only thing I can think of is something to do with downgrading from Lollipop 5.0 to Stock 4.4.2. I'll update this thread if I end up getting something to work.
I ended up flashing the Alliance Rom to get it back to something very close to stock. Still interested in possible solutions to restoring that original backup though as if I need to send it in for maintenance that's the one that I'll need to use.

Stuck at boot screen after restoring ány Nandroid backup.

Hey,
I've had this problem for ages now, and always gave up on my data, but now I really want to fix this for good.
Yesterday I was ready to update my CM12 nightly to the lastest version (didn't see it was actually CM13), and did a backup in cwm before the update. The backup succeeded, but it gave the message that .android_secure couldn't be found and it didn't back that up. It always gives me this message after a backup and after google searching, it seems to me that it doesn't matter.
After installing the update, I noticed it was CM13, and my gapps wasn't updated to the marshmellow stock, as expected, so errors occured all the time.
I didn't want to upgrade to CM13 just yet, so I decided to restore my backup.
As always, the restore process goes without errors, but upon reboot I'm stuck at the CM logo. I can wait untill the battery is dead or ignites from the heat, but nothing happens. This has also happened to me every time I make a backup. I've watched about every video on youtube on how to do a proper backup and how to restore one, so I'm confident that I did it right.
For some reason, any backup I make, no matter what android version (didn't work with stock kitkat, either, before I switched to CM12) it never works and I'm forced to do a clean install and start over again.
I've tried to do partial restores from the backup file, and if I only restore the data partition (and wipe dalvik) It does boot, but gives me non stop errors that apps are crashing.
I've tried to do a dirty flash to no avail, always endless error messages.
When I do a clean install and check the MK5 of the backup with nandroid manager it gives no errors.
Is there anything wrong with my phone or something? I'm not making backups to be unable to restore them.
Can anyone help me out with this?
(I have a i9505)
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
GDReaper said:
Try a different recovery. CWM is outdated. TWRP is nice. Worked for ne every time. There are TWRP flashable zips so you won't have to mess around with Odin.
Click to expand...
Click to collapse
Won't changing recovery make my old backups useless? I'm all for changing to TWRP, but first I'd love to restore my CWM backup...
Yes it will. Unfortunately I don't know what to suggest. Haven't used CWM since I switched to the S4.

Impossibly persistent problem even after reset

I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I knew wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Suggest you ask in the SPRINT forum .
uscpsycho said:
I have a Sprint Note 3 and I am having the dreaded "Unfortunately, the process android.process.media has stopped" problem.
I tried every single fix I found online. Even the stupid ones I new wouldn't work. I finally caved and did a full wipe. Low and behold, on the very first setup screen the error message immediately popped up.
I am stock (whatever the latest version is) and rooted.
If factory reset doesn't work I don't know what else would work. That's usually the last recourse. Any suggestions? HELP!
Do I maybe need to re-flash the stock rom? If so, can someone please provide a link?
Click to expand...
Click to collapse
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
ShaDisNX255 said:
Yes, you need to re-flash stock ROM (search in updato). I'd also suggest you do a full DATA wipe with TWRP before and THEN flash stock ROM. Make sure you backup everything before anything.
Click to expand...
Click to collapse
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
uscpsycho said:
Holy crap. I downloaded a stock ROM from Updato and my phone isn't bricked but I'm worse off now.
Somehow, nothing at all changed on my phone after I flashed the ROM. All my apps, data, screens, everything is still there. However, I lost root and I lost my custom recovery and I still have the problem I had before.
Two questions:
1) I still have a Nandroid backup of my rooted phone from before I flashed the stock ROM. Can I restore this Nandroid backup with the stock recovery?
2) If not I will install TWRP again. At that point can I just restore the rooted Nandroid and gain root again or do I have to root first and then restore the Nandroid?
What a mess. Why did everything stay the same after flashing the stock ROM? Is updato a legit website?
Click to expand...
Click to collapse
It's a legit website but you need to wipe everything before flashing stock ROM. The order would have been: Boot into TWRP -> Wipe/Factory reset -> Format Data -> Reboot to download mode -> Flash stock
Yes, you will have to re-install TWRP again and restore your nandroid backup.

Help!! go from 8.1 to 6.0

I explain my problem, after taking time trying roms 8.1 I decided to give a second chance to the stock-based roms. After several attempts with a couple of roms, I always get the same problem after installation (so not installed). I have read that it may be a problem with the version of twrp (right now with the latest version). Before trying to download the version I have to do something special, install as an image and go? Do I lose information when doing it?
What steps should I follow to go down to 6.0?
Besides this, I have a backup made of the gizrom, every time I want to restore it I get the same message: so not installed
Thank you
encerrao said:
I explain my problem, after taking time trying roms 8.1 I decided to give a second chance to the stock-based roms. After several attempts with a couple of roms, I always get the same problem after installation (so not installed). I have read that it may be a problem with the version of twrp (right now with the latest version). Before trying to download the version I have to do something special, install as an image and go? Do I lose information when doing it?
What steps should I follow to go down to 6.0?
Besides this, I have a backup made of the gizrom, every time I want to restore it I get the same message: so not installed
Thank you
Click to expand...
Click to collapse
Backup everything on your internal storage while you are on 8.1 rom. Or restore 8.1 rom and do the backup now.
Even you had tried to restore 6.0 stock rom (unsuccessfully) you can still restore the 8.1 Twrp backup it should work.
Go back from 8.1 to stock 6.0 you can restore the 6.0 backup in Twrp as normal. But after restore the backup done you will need to format data. From Twrp menu go to: Wipe > Format data (here you will lose everything on internal storage). The stock 6.0 restored rom/system will still there and working.
You can restore the app data of the backup rom after you done with the format data.
If you don't do the format data the 6.0 rom will not work I think. It will show something about encryption stuff when it try to boot and enter the system.

Categories

Resources