Hi, I tried to restore a full image with TWRP including firmware. Everything went smooth, only with the firmware I got the message "extractTarFork Process ended with error 255." My system (Resurrection 7.02) boots, but finger reader, Wi-Fi and Bluetooth don't work. What can I do?
tempe222 said:
Hi, I tried to restore a full image with TWRP including firmware. Everything went smooth, only with the firmware I got the message "extractTarFork Process ended with error 255." My system (Resurrection 7.02) boots, but finger reader, Wi-Fi and Bluetooth don't work. What can I do?
Click to expand...
Click to collapse
I solved like this:
copied twrp backup onto computer, used winrar to unpack firmware.vfat.win -> firmware.vfat -> image folder
phone booted into TWRP, enabled MTP, copied image folder to sdcard
mount system and firmware partition in TWRP and copy image folder from sdcard to /firmware folder using file manager from TWRP
I recommend to backup and to restore EFS partition also when sim problem after flashing ROM. I had this problem flashing crDroid.
Keep in a safe place outside your phone persist/modem/firmware/EFS backups for the future.
I worked for a week only to get out from a bootloop generated because "extractTarFork Process ended with error 255." on firmware partition.
Rebooted and everything was fine.
I have now crDroid 5.3 working on a2 lite.
Related
I was experimenting with the xposed framework and got stuck in a boot loop after restarting for a second time to install some more modules. The safe mode booting didn't work and neither did the included restore zip file for getting out of it. I tried to restore from the backup on the phone, but it already had the xposed framework in it and it got into a boot loop too!
I tried to adb sideload the backups that I made, and that didn't work either.
I keep backups, made from CWM Recovery, and I pull these to my computer using a WiFi file explorer. (I don't have enough storage to keep two alternative backups so I always have the second stored on my computer)
Anyway, I cant seem to get the restore file that I uploaded to my computer (a restore image) to reload on to my phone and restore. I have attempted to transfer it back to the phone into the folder it came from, but the file wont flash as a zip and it doesn't show up to be restored if I select the restore feature. (BTW-The restores have plenty of SD room to restore on, that isn't the issue)
I realize that the WiFI File Explorer that I use may be zipping the files, so shouldn't I be able to "install zip" in CWM recovery and it restores the image? (apparently not, can you explain why, and what I can do?)
Can I get access to the mnt/shell/emulated/clockworkmod/backup/ to put the file there to be restored again?
Or,.. How do I put the restore file on my phone (in the correct place) to be restored again?
Is my problem being caused by where I am pulling/pushing the file from(mnt/shell/emulated/clockworkmod/backup/)?
What am I missing/doing wrong?
Nexus 4
CM11 installer version xnpq08q
Rooted Unlocked
CWM Recovery
I'm running twrp 2.7.1 and have quite a few problems but I'll just start out with the backup and restore options.
The tutorials I've reviewed instructs to simple backup your stock rom and to reinstall, choose the file and restore.
Why isn't the wipe and factory restore procedure performed?
I followed the instructions and attempted to restore the latest backup but when I hit reboot I get the no OS installed warning, this is without any wipe. I doubled check the checksum of this backup for accuracy.
If I choose the earliest file from the restore list, I get no OS warning and am able to reboot back to the "older" flash of the stock rom. I actually performed the same procedure after a failed install of a custom rom with wipe. Got the OS warning after loading the latest backup but no warning with the oldest.
This only scratches my problem but I'd like to address and hopefully fix this first.
Thanks for any suggestions.
If the nandroid was made with a different version of twrp, maybe try reflashing that version and try again.
Alternatively, you could just flash whatever rom is backed up, then try to only restore the data portion.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Just tried your suggestion choosing latest backup and restoring data only. Now after the splash screen it wants to setup language, email etc. again.
What I meant was flash whatever rom it was that you were trying to restore. If its the sane rom in another backup that's fine though. Did the data restore pass the md5 check?
You can try again, but afterwards go to twrps advanced menu and copy log to SD. It may provide some clue as to what's wrong. Attach it here if you want me to take a look.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Well I'm starting to think twrp is corrupt.
I tried to load the ndroid backup I made yesterday but the log showed it was done in 8 seconds. I attempted to flash back to the original image I made 2 months ago which I have been successful doing..I thought everything was flashing when I noticed the screen is now says...
Could not do normal boot.
ODIN MODE
Product Name: SGH-1747
CUSTOM BINARY DOWNLOAD:Yes (3 counts)
CURRENT BINARY: Custom STATUS: Custom
QUALCOMM SECUREBOOT: Enable
Downloading....
Do not turn off target!!!
It's been stuck on this screen for a while.
Sounds like something got corrupted, or you need to try with a different recovery. Either way its in download mode for flashing with Odin.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Have you tried using Philz Touch? I was using TWRP but ran into problems flashing ROMs. I switch to Philz and the problems went away.
Unfortunately, Philz can't restore TWRP nandroid backups.
Could I please get some advice on what to do next?
Okay, I was able to pull the battery and boot into twrp, restore the old stock rom and safely reboot but this is one of many problems.
I haven't been successful installing any roms. I've downloaded Liquid Smooth, Gummy, Carbon and Slim 4.4.4 versions and encounter the following error message.............E: Unable to open zip file
Error flashing zip / external_sd / custom rom / "file name"
I'm using a 64 gb card but am not sure how it's formatted. I've created files with the roms in the internal card but twrp doesn't see it.
I've read tutorials and researched some of the blogs and I assure you that I'm not doing anything haphazard but the amount of problems I'm having is absurd.
the only thing i can think of (and hopefully someone more knowledgeable will chime in) is if in twrp settings see if 'md5 check ' is checked. if it is then uncheck it and try to flash again. srry thats all i got right now. (or bad idea doc ?)
good luck.
err on the side of kindness
Try flashing from internal SD. Don't know why but its worked for a couple other people so far. If it still doesn't work, please use the copy log to SD option and attach it here.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Challenged_101 said:
Okay, I was able to pull the battery and boot into twrp, restore the old stock rom and safely reboot but this is one of many problems.
I haven't been successful installing any roms. I've downloaded Liquid Smooth, Gummy, Carbon and Slim 4.4.4 versions and encounter the following error message.............E: Unable to open zip file
Error flashing zip / external_sd / custom rom / "file name"
I'm using a 64 gb card but am not sure how it's formatted. I've created files with the roms in the internal card but twrp doesn't see it.
I've read tutorials and researched some of the blogs and I assure you that I'm not doing anything haphazard but the amount of problems I'm having is absurd.
Click to expand...
Click to collapse
I suggest Philz Touch as a substitute for TWRP. I was having problems with TWRP until I switched to Philz.
I noted that I tried to flash from the internal card but twrp could't find the folder I created.
Twrp still didn't see the files after i moved them out of the folder and placed them among the other folders.
Challenged_101 said:
I noted that I tried to flash from the internal card but twrp could't find the folder I created.
Twrp still didn't see the files after i moved them out of the folder and placed them among the other folders.
Click to expand...
Click to collapse
Open a file explorer like es file explorer..create a new folder and put the ROM zip in the external SD..I had to do that and I use cwm
I created files with Astro file manager but twrp still doesn't see them on the internal card just the external but won't open the zips.
I'm just not getting much feedback on my problem. Will posting on a different forum help?
If the external sd is formatted as exFat, recovery may not be able to read it correctly. Since its a 64gb card, I bet this is the problem.
Have you gone into the mounts menu and remounted your internal sd and/or /data? Maybe its just not mounted...
You might also want to try twrp 2.6.3.1 or 2.8.0.1. You can get them from the link in my sig.
Or try philz recovery as suggested before.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I put TWRP on it and can boot to recovery. However, it fails flashing the Cyanogenmod zip because (it says) you need to wipe the device due to an incompatible device layout. So I tried that and naturally it wiped the zip off the /sdcard. Then I mounted the sdcard from TWRP but I couldn't write to it from my computer. (I could see the now-empty drive.) So I said what the heck and rebooted the system and had a like-new device.
I had backed that up before I did anything. So transferred another copy of the cyanogemod zip to the tablet, rebooted to TWRP and tried to install it again. Still no luck. I then transferred my backup to my tablet and restored the backup so I'm back where I started.
Is there another way I haven't thought of?
I put 12 on my n5110 before I found slim rom 4.4.4. Had no trouble with the install of either one. Have you tried putting the cm zip on the external sd card and installing from that using twrp? I also think you can use either Odin or adb but as I recall the methodology will be different. Lots of people with a lot more experience here maybe someone else has some suggestions as well.
Regards
Expat
Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Hi,
currently I am running CyanogenMod 13 on my Samsung Galaxy S4 Mini (serranoltexx). Now, as it get's outdated and insecure, I am about to update it to LineageOS. But I am worried, because I can't just flash the ROM over CM, but I have to wipe everything. Sure, I can take backups of all my data, but my question is:
What do I have to select in Clockworkmod Recovery in order to clean up for LineageOS? And the second point is that I parted my SD-Card to use Android's option to emulate one partition as internal storage. So if I wipe, can I keep the partitions and what do I have to save before?
Oh and.. I have tried to do a Nandroid Backup, but I can't copy it onto my PC because the storage is mounted differently within CyanogenMod (the 2 partitions I wrote about) and ADB doesn't work for this either.
I hope somebody can help me
Done! /ReqClose
Hi,
I'm glad to say that I have done it yesterday. The thread can be closed and for all who have the same questions I had:
First of all I took a backup of all my data (Apps, Music, Photos etc) and put LineageOS, GApps & SuperSU on my SD-Card. Then I booted into my recovery (CWM) and wiped all data. Unfortunately it didn't work (CWM said something like "error in lineageos.zip") so I decided to use TWRP for it. There was just an unofficial build but I didn't care too much, so I used this one. It was an img file, so I needed to convert it to .tar.md5 first using a tool I found in the Internet. So I flashed TWRP then using Odin. When I booted into TWRP everything seemed to work, but when I tried to install the zip file it just rebooted immediately without an installation. So I finally used ADB sideload, and it finally worked! Now my phone is working fine!
Hope this helps someone!!