I was using miui 8 the past month and wanted to try something new. So I flashed.a MM.Rom, CM13 from this forum. I did a system backup before. I am using twrp 3022.
After trying the Rom i decided to restore my miui backup, but when i try that I get an error saying:
extractTarFork() process ended with ERROR=255
I tried it several times but i always get this error after 85-87% of the restoring progress.
Is it because one rom is based on LP and one on MM? I never changed the twrp 3022.
I've read somewhere that it can be because of not having enough space but it's a system backup, so doesn't it mean, that it restores the whole system and data i had on that phone?
Please help
Edit
Restoring the cm backup works but the miui dies not work
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate ?
Jordan Jacob said:
Download and clean install Vova's AOSP rom first, let it boot, restart into recovery and try to restore your backup again. I've face this problem before, and this method works. Good luck mate
Click to expand...
Click to collapse
The Lollipop Rom?
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Jordan Jacob said:
Yups..
http://forum.xda-developers.com/redmi-note-2/development/cm-aicp-mokee-resurrection-bliss-t3383140
Click to expand...
Click to collapse
ok thanks i will try it
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
gasperoni said:
I still get the error 255 at 87%. I wiped the data and installed that aosp rom but it didn't help
Click to expand...
Click to collapse
Did you wipe the data partition or did you format it? Try doing the latter ...
First i wiped cache+dalvik+data+system, everything but intern storage. I thought that must be enough. My last chance was wiping internal storage as well. I tried that and now it works. It really seems that it was a problem of space. I want to go back to a CM13 based Rom, when it's getting more stable.
Glad to hear your problem solved..
Jordan Jacob said:
Glad to hear your problem solved..
Click to expand...
Click to collapse
thanks bro, me too :good:
I've had this problem too - exact same error message, with the last two versions of TWRP.
I originally made a backup of my Nexus 7 2012 3G (Tilapia) with the modified KOT49H ROM installed, with TWRP (3.0.2.0, I think). I installed one of the Lollipop ROMs (I forget which) then restored that KOT49H based backup with no problem. Then I tried a different Lollipop ROM (Resurrection Remix, something) then tried to restore the same KOT49H based backup as before, and got this error.
I went from there to the Nougat ROM I'm currently using - an AOSP one by AndDiSa, and made a backup of that installation shortly after. After making some changes, I tried to restore that backup and got the same error (see OP).
I deleted as much stuff as I reasonably could, updated TWRP to 3.1.0.0 via fastboot and tried the restore again - same error. Also, my tablet then wouldn't boot, though that might be an unrelated problem. I took the battery out, which possibly I didn't need to, put it back, and noticed it was charging. It eventually booted, and seemed to have restored the backup, though I cant' be sure. Since it was the same ROM, it's possible all it restored was the data partition.
My main question is, if this is related to free storage, just how much is needed, to be able to restore a backup? I don't see wiping internal storage as much of a solution, on the Nexus 7, because there isn't a microSD slot, so that's the only place I can put the backup I'm trying to restore.
Hello. Can you please give me the twrp nvram backup or just the protect_f.img and protect_s. Thank you
Had same error, went back to old twrp ,all problems fixed
Steveromingagain said:
Had same error, went back to old twrp ,all problems fixed
Click to expand...
Click to collapse
what version TWRP to fixed problems ? i use TWRP version 3.0.2.2 always Error...
Related
Hey guys
I need some guru help here :/
I've flashed cyanogenmod 13 with android 6.0.1 on my i9300 along with some gapps (stock version). Everything works well, besides the cell reception.
I've been able to see other networks around but couldn't connect to neither of them. (i'm on roaming, in germany, while my sim card and the phone are from poland)
I have applied no signal fix from here which didn't change anything.
Then I've flashed this (the one with "Poland" next to it), but that only made things worse, as the whole "cellular network" menu in settings is greyed out.
What I've figured out is that when typing *#06# the phone app makes some noise and hangs, and in the settings there is no IMEI number.
This leads me to the conclusion that EFS (seems empty in the TWRP file browser) is broken/cleared.
I've seen many instructions on bringing it back to life, non of them are clear to me, and all use Windows. Is there a way to do that on Mac OS, or.. basically is it THE way to go for?
I would appreciate all the help as I need that phone in the next days :/ thanks!
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
rp158 said:
@krecio4:
1. Look for efs-backup. Some kernels create this. Or as part of TWRP-backup. Restore it.
2. Flash latest firmware with Odin. If IMEI is still gone afterwards, try KIES repair function.
3. Let it repair in service center.
Click to expand...
Click to collapse
thanks a lot @rp158!
I've tried searching for an efs backup but no luck :/ any idea where do they create it? restore option only has those files that I've backed up.
latest firmware you mean the official one, right? Is there a way to do it on mac os?
cheers
@krecio4: TWRP backup contains efs-partition, if you chose/ticked it. Kernels (Boeffla, Agni) store it in sdcard0, but if you never flashed a special kernel, it's over.
Firmware means Samsung's stock 4.3 from sammobile.com. Look there, if they offer Odin and KIES for Mac. Otherwise lean a Windows pc. It's useless to make it more complicated by struggling software.
@krecio4: read this. That's not the solution, but if that all caused by actual CM13-nightly, there comes perhaps any...
I have the same problem with latest nightly. This work fine: "cm-13.0-20160523-NIGHTLY-i9300.zip".
@krecio4 I think that you have to first flash latest firmware then root your phone and then you have to use z3x box, hope it will fix :good:
thanks for your sugestions guys
What I did is to get the latest firmware from sammobile, restored it with Odin, phone was working, I was receiving calls and texts.
So I installed TWRP, backed up EFS, System, Data, and one more thing that was marked.
Then i did a factory reset and installed latest CM13 + gapps in one run (as a batch of files, selected the CM13 first, than the gapps in the que)
rebooted
Again - CM13 works well, but it says "please insert SIM card" :/
No IMEI, IMEI SV (Unknown)
Cellular networks in settings are off, and greyed out inside, "preferred network type" is "Invalid Network Mode (-1). Ignore"
Do you think there is any hope?
I noticed that EFS is empty, after restoring it from backup, and rebooting, it's empty again.
so tired of everything, I went back to the original software using this method (even easier than Odin) http://forum.xda-developers.com/galaxy-s3/general/how-to-factory-installed-firmware-sgs3-t1838480
If you come up with some solution, I'd love to try Cynanogenmod for longer and.. for real
1. Be happy, that your efs-data are ok. Make in TWRP a backup of this partition only, for worst cases.
2. Try @mexit's advice.
Can I with no problem have a custom recovery installed while using original firmware?
So you are saying that it might be with the last 3 nightlies that they are messing up with backed up EFS? If so, I'll try installing the one you've mentioned, but now I've list 2-3 days for the whole crap so I will wait until I have too much time But thank you very much for your support!
BTW, I found this as well: http://forum.xda-developers.com/galaxy-s3/general/tool-backup-restore-efs-imei-sgsiii-t1901098
Posting for anybody, as I digged the whole internet for any answers
Install this: https://download.cyanogenmod.org/get/jenkins/162926/cm-13.0-20160524-NIGHTLY-i9300.zip
http://forum.xda-developers.com/showpost.php?p=67034195&postcount=5968
Click to expand...
Click to collapse
ok, as I don't give up easily, as you can see, I did another approach. Backup, backp EFS only.
Installed the edition from 23rd of mai. All good! But during the "installing apps" during the initial boot, close to the end, the battery died (after the screen flickering). but reboot and it all seems to work well Any issues that could appear after an unexpected reboot during the first boot? Do you suggest to do factory reset and flash CM13 + gapps again?
If I understand well, battery died during compiling Dalvik/ART. Should be happen again after cleaning both caches. But to avoid any mess, I would clean flash the ROM again.
So you suggest to do the factory reset, install CM13, install gapps, reboot ?
No.
Wipe system, data, cache, Dalvik cache.
Flash CM13. Wipe cache, Dalvik cache.
and gapps installation shouold be along the CM13 in a que right?
@krecio4: flash GApps afterwards. Read the last posts of CM-thread: your problem was probably caused by a modem-bug in CM, should be gone now.
after the wipe cache & Dalvik?
so CM13, wipe, gapps, reboot?
Ok, very precisely:
flash cm13, wipe 2 cashes, reboot
if net and wifi ok, make a backup of this state
flash GApps, wipe 2 cashes, reboot
case closed
edit - problem solved......
biggary said:
Hello there, long time member of XDA, but a new user of Honor 5x - Nice to see some devs create some nice roms....but I have a problem.....
I unlocked bootloader via the proper way, and its flashed, rooted etc, and its happily running the newest resurrection remix rom.....but.....
I went to download the great modaco roms by @paulobrien , done what was said, but the phone reboots, and it does the splash screen thing....and thats it....as far as it goes, I try leaving for half a hour, but still nothing......
sometimes i get the error in TWRP that /system cant be mounted, and although it flashes, when rebooting, it says NO OS installed, so i flash it again, and no error but, reboots and sticks at the 'HONOR' logo....
My model is L21, when i clean for a new rom, I advance wipe all sections except internal and external memory, and i also do a factory reset, as I have done with many many other phones
is there a step i am missing? i have read about swap - what is that?
All I want is a nice stock rom which i can debloat, install the htc home launcher, and a few useful apps.....
Who can help me???
Click to expand...
Click to collapse
If you wipe system before flashing the rom you get that error
don't wipe system the rom does it for you
to flash the rom after wiping the system choose reboot / recovery now the rom will flash
Arobase40 said:
"Honor 5x running Resurrection Remix Marshmallow"... ^^
Click to expand...
Click to collapse
@Arobase40 I know my Sig says runing RRemix, but what im asking for, is going back to a stock rom, i can flash any of the CM based roms, but have problems when returning to stock.
Hey Guys. I currently have CM13 and TWRP recovery. I'm slightly confused on how I should try out the latest OOS 3.1.
Can I simply flash the OOS zip through TWRP? Or will I need to flash the stock recovery, flash 3.0.2 and then flash 3.1?
Any guidance here for a quicker turnaround will be helpful.
Thanks!
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
level5music said:
You need a clean flash. The way I prefer to do it is to get the pro version of Titanium Backup, and backup all your user apps. You can do the system apps if you think you might return to CM. You can also dump the backup to your PC or an OTG USB if you want. When you're ready to flash, go into TWRP and wipe all except Storage, then flash the OOS zip. When you get back in and setup, get Titanium Backup again, and restore your backed up user apps. Only do the user apps, system apps from CM will likely fail. You may want to stay away from any OTA updates though, I think it borks TWRP so you have to re-do all of that, maybe someone else can confirm this because I'm not 100% sure. Happy flashing, let us know how it goes.
Click to expand...
Click to collapse
Not an issue with Titanium backup. I carry the load of backups along regularly.
I was concerned about flashing it via TWRP, which you confirm shouldn't be a problem. And I guess it shouldn't overwrite my recovery too? Perfect. I will try and spend some time on this over the weekend to compare with the CM. Thanks!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
rezapatel said:
Did you go the OTA mode, update flash or full flash? Also, I believe if it's a big change, a clean flash would be the better option over dirty flash.
You can also try wiping cache / dalvik and turning on app optimization. Might work? Can also try custom kernel?
I'm so intrigued where I read somewhere, that the Antutu benchmark jumped upto 80k on OOS 3.1.
Thanks!
Click to expand...
Click to collapse
I tried the OTA update like i do for every build. Its just not my problem, my friends phone is also behaving same even after factory reset. 3.0.2 was better in terms of battery. But the performance of 3.1.0 is better than 3.0.2. Its very smooooooth.
So I might as well stay away from it? Honestly I'm fairly happy with CM13 except for the fact that double tap feature turned on makes the phone vibrate when talking on a call!
Doesn't beat the snapiness on CM13. I'm back!
Techgod said:
My device never goes to deep sleep mode on 3.1.0.
Please dont go to 3.1.0. Its is very very bad for battery
Click to expand...
Click to collapse
That's not true. I get 6 hours of SOT and over 24 hours of standby with stock 3.1.0 with no modification at all.
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Nocturnal22 said:
A "script kiddie" here, tried to customize my phone for the first time, accidentally installed a wrong version ROM, the phone went into a bootloop and so i decided to completely wipe the internal storage (that was so very dumb...)
Now after a day of struggle i managed to install everything i wanted - TWRP and a custom MIUI, but ever since that memory wipe i lost my signal. After searching around some, it seems that my IMEIs got lost (disconnected, corrupted, i dont know how to call it) and the phone can not detect either of my SIM cards. WiFi works fine. I do not have "nvram" folder or file anywhere on my phone.
Click to expand...
Click to collapse
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
stympy said:
Look in Q&A section/IMEI NVRAM Restore Tools post. That is allmost the only way to restore lost IMEI.
Good luck.
Click to expand...
Click to collapse
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Nocturnal22 said:
Im getting lost in that wall of text. Cant i just replace my damaged "nvram" with someone elses working one? Switching IMEI to mine afterwards of course.
Also it says i dont have a baseband, should i be fixing that first?
Click to expand...
Click to collapse
At the end of that tutorial look for a small word tutorial zipped. Read that one first.
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Nocturnal22 said:
Turns out all i had to do was mess around with firmware re-flashing until i got a working baseband and then use Chamelephon to set up IMEIs.
Everything was that easy.
Click to expand...
Click to collapse
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
stympy said:
Try this: reset the phone to factory defaults. Then try to see if IMEI'S are still there.
Tell me what firmware worked. It is a valuable information for others.
Thanks.
Click to expand...
Click to collapse
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Nocturnal22 said:
I wiped all the factory settings and the ROMs i used to mess around were: P780_S124_ROW_140403, flashed through flashtool, supposed to be the "official" ROM (the one i got the stable baseband from) and MIUISU_4.4.2v_P780_7.2.24_ROW (the one im using currently). All the IMEIs got restored through Chamalephon as soon as i got a working baseband and i can send/accept calls and SMS with no problem. However there is a bug with constantly changing MAC now.
Click to expand...
Click to collapse
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
stympy said:
Hi. Did you installed MIUISU over s124 ?
If you did, you must update to s228 Kitkat.
S124 is jellybean. You will get errors, if you install kitkat over jellybean.
Click to expand...
Click to collapse
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Nocturnal22 said:
No, i installed s124 backed up the baseband and nvram files through MTK. Then i flashed the system, installed MIUI and recovered my baseband. The unstable MAC error started in s124 already.
Click to expand...
Click to collapse
Ok. I understand.
long story short after full wipe, for the newest lineage os , ,gyroscope dosnt work anymore
ive tried with TWRP to go back to my last rom full backup (oldder lineage ver)
almost everything was there's (beside the gyroscope \screen rotation )
what can i do?
thanks
solve it (by flash stock ROM)
ok.. something weird.. after getback to any lineage still no gyro anymore
Superrman said:
ok.. something weird.. after getback to any lineage still no gyro anymore
Click to expand...
Click to collapse
Are you trying official or berni's?
Hi.
Have you found any solution? I am having quite the same problem.
All sensors (acceleration, compass, gyroscope, light, proximity) stopped working at my XZ5c.
Using Official LineageOS 14.1 latest version (14.1-20190207).
What I have tried:
Did an upgrade of LinOS, wiped dalvik and cache.
Even after a wipe of data all sensor are not working.
Tried something I found in the Xperia Z1 section
execute the following shell command (...):
kill $(pgrep sensors.qcom)
This kills the sensors.qcom process. ( It will restart automatically )
Click to expand...
Click to collapse
But it did not take any effect.
How do i know: Proximity sensor is not working when using telephone.app. Automatic screen brightness is not working. All other sensor readings only show up a "–" when reading out e.g. with SatStat.app.
Any ideas??
solve it (by flash stock ROM)
Click to expand...
Click to collapse
Did the same. Now sensors are working again.
Also see this Post.
Still: Someone knows how that happens? Would like to avoid all the flashing and restoring for the future if this is possible...
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
TheVan28 said:
I just got the same issue after going from lineage os to resurrection remix...
Is there a way to fix it without losing data?
is flashing stock rom + restoring the backup good enough to solve the issue?
Click to expand...
Click to collapse
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Son-Y said:
After new installation of TWRP & LineageOS I did a restore of /data which I had backed up before. In my case it worked. All my app-data was restored. Sensors are working again.
But if you have a different OS or OS-build this might not work for you.
Click to expand...
Click to collapse
My problem is that, even if i do a complete wipe, i still get the sensors issue
if i open an app like cpu-z they litterally don't exist, i get a blank page
I had the same problems and also persisting after a complete wipe.
My solution was:
Flashing Sony StockROM as descirbed in ( this post) .
This sorted my sensor issues. Check your sensors while in StockROM to make sure they are phyically OK
Then you can go back to whatever TWRP/CustomROM you like.
Hope that helps!
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Yep. I also cannot tell why it worked, could only tell you how...
Son-Y said:
Tried something I found in the Xperia Z1 section
But it did not take any effect.
Click to expand...
Click to collapse
I think pgrep no longer works on Nougat.
Code:
kill $(pidof sensors.qcom)
should work.
TheVan28 said:
I finally flashed the stock rom and then, even without making a full wipe but just restoring the backup worked.
I'm happy that it's fixed, but it's also kinda weird
Click to expand...
Click to collapse
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
berbigou said:
Hello,
I have this problem with LineageOs 14.1-suzuran.
That happens each time I mess up and restore from TWRP. So now, I flash stock kernel and restore that way (quite long):
-> flash stock kernel: full install in flashtool: all included, all wiped, non excluded
-complete reboot (with nfc bug, power off, ...)
-had to setup wifi (maybe for the date)
-no Google nor Sony account, unknow sources+adb activated
-reboot
THEN
-> install TWRP (with flashboot)
AND
-> restore boot/cache/data/system ONLY, from a previous backup of lineagesOS
I made a backup of my freshly restored stock kernel, in Read-Only mode, but no way ((
I think a startup script runs on stock kernel that activates sensors.
Hope that'll help
Click to expand...
Click to collapse
Can you be more clear about the steps? how do you install stock kernel?