Hello.
My English is very terrible.
I make a backup with TWRP type NAndroid before the change the ROM for verify if the error that had with the antena WiFi was to level the software or hardware, result is the software. When go to restore backup, show up a error.
extractTarFork() process ended with ERROR=255
I have the pass the is post http://forum.xda-developers.com/showpost.php?p=61041108&postcount=475 and show up to me
ROM: CyanogenMod 4.4.3
Recovery: TWRP 3.0.2
Device: Galaxy Nexus GT-I9250
Capture:
http://i.imgur.com/JEADXAD.jpg
http://imgur.com/5mL78DX
Please check memory space in Internal Storage. It needs to be wiped for storing /data.
[ Backup with ADB through Recovery TWRP 3.0.2-r5 or TWRP 3.1.0-0 ]
I found out how to backup easy through Recovery with ADB and create this software to help you get easy with that, just execute it and follow what is write in there!
Download the zip, extract the folder, boot in twrp and plug the usb cable, open the folder and execute the exe file, select the option and follow what is write. The backup files will be stored in Rom_Backup folder!
To restore the partitions you need to do a backup first from the same partitions then do a restore!
ROM_BACKUP.zip
https://mega.nz/#!Mk5kEI6B
Key: !K9o8aIgvB_nozTj386MxEBL7ukBMdmZUs0_1dk1QtiA
Very easy!
Try it and tell me!
@panchovix
Hi!
I found out how to use the ADB backup with recovery!
Try the software i create from above!
:laugh: :silly:
.
Hello.
Forgive my silly question, but I want to be sure I don't create a mess.
In May I was with stock rom rooted with 8+8 GB and I've done a backup with your tool, so now on my pc I have the file Backup_14052017.bak.
Then I've flashed LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl.
Now I want to go back to that stock rom.
Can I do it just restoring that backup, right? And then I'll have back the stock rom 8+8, and all the data I had in may, correct?
Thanks.
Luigi.
Stick with Lineage - personna bricked his phone .........
OOps, doesn't suond funny...
Bricked using the restore option???
So, I'm trying to restoring that backup.
I've rebooted the phone in TWRP, plugged it to pc, launched ROM_BACKUP.exe, choosen 1 - Restore Backup and written backup's name.
But I get the error "adb: unable to connect for restore" (see attachment).
I have debug usb enabled and USB Computer Connection set on Camera(PTP).
What am I missing?
Thanks.
Luigi.
solquest3 said:
So, I'm trying to restoring that backup.
I've rebooted the phone in TWRP, plugged it to pc, launched ROM_BACKUP.exe, choosen 1 - Restore Backup and written backup's name.
But I get the error "adb: unable to connect for restore" (see attachment).
I have debug usb enabled and USB Computer Connection set on Camera(PTP).
What am I missing?
Thanks.
Luigi.
Click to expand...
Click to collapse
The latest TWRP from FireLord. You need to be on the recovery for restore to work.
Huskied said:
The latest TWRP from FireLord. You need to be on the recovery for restore to work.
Click to expand...
Click to collapse
Which version is the latest? I have 3.1.0-0.
I've turned off the phone, then pushed power+volume up for booting on TWRP.
I'm in the initial screen, the one with 'Install', 'Wipe', 'Backup', 'Restore', 'Mount', 'Settings', 'Advanced', 'Reboot' when trying to restore.
Mabe is something wrong on my pc with adb.
In my ROM_BACKUP folder I have (don't remember if they were originally there or if I've moved something in that folder)
adb.exe
AdbWinApi.dll
AdbWinApi_build.dll
AdbWinUsbApi.dll
Backup_14052017.bak
ROM_BACKUP.exe
I've tried opening command line from that folder and writing 'adb devices' for seeing if everything was ok.
I've got the message 'List of devices attached' but nothing about the device.
So it seems there's something missing...
Thanks as usual!
solquest3 said:
Which version is the latest? I have 3.1.0-0.
Click to expand...
Click to collapse
Check in Android Development. Again, FireLord's TWRP is the latest.
Huskied said:
Check in Android Development. Again, FireLord's TWRP is the latest.
Click to expand...
Click to collapse
Thanks.
Found it, but in the download page it says
twrp-3.1.1-idol3.img
for the Alcatel Idol 3 5.5, by FireLord
Will it work also on Alcatel Idol 3 4.7?
solquest3 said:
Thanks.
Found it, but in the download page it says
twrp-3.1.1-idol3.img
for the Alcatel Idol 3 5.5, by FireLord
Will it work also on Alcatel Idol 3 4.7?
Click to expand...
Click to collapse
Ehhhh... I don't know. I would suggest hitting someone up to build the latest TWRP for the 4.7 Idol 3.
solquest - I would suggest you use personna's TWRP he made - that is the one he used to check this works on his phone
check his posts
k500zm said:
solquest - I would suggest you use personna's TWRP he made - that is the one he used to check this works on his phone
check his posts
Click to expand...
Click to collapse
Do you mean TWRP 3.0.2-r5 and TWRP 3.1.0-0?
Tried them both but always got this message:
command id: 'adbrestore' and there is no value
E:Unable to find file system (first period).
E:Unable to find file system (first period).
E:Unknown restore method for '/system'
E:ADB Restore failed.
Done processing script file.
Checking online, mine doesn't seem the only case: https://github.com/omnirom/android_bootable_recovery/issues/133
Well the latest TWRP is by alecbl on the lineage thread towards the end - 3.1.1.0 - try that one and see if that works....
k500zm said:
Well the latest TWRP is by alecbl on the lineage thread towards the end - 3.1.1.0 - try that one and see if that works....
Click to expand...
Click to collapse
Found and tried.
Restoring finally worked and it said it restored system and also data (while I thought with ROM_BACKUP I would have restored only system).
The problem now is that phone doesn't boot... I get the ALCATEL ONETOUCHE powered by ANDROID screen, then the Idol 3 screen, then the blue android forming and then it reboot.
Any idea on what to do?
solquest3 said:
Found and tried.
Restoring finally worked and it said it restored system and also data (while I thought with ROM_BACKUP I would have restored only system).
The problem now is that phone doesn't boot... I get the ALCATEL ONETOUCHE powered by ANDROID screen, then the Idol 3 screen, then the blue android forming and then it reboot.
Any idea on what to do?
Click to expand...
Click to collapse
Wipe Data. Sometimes it kills phones.
Huskied said:
Wipe Data. Sometimes it kills phones.
Click to expand...
Click to collapse
I've wiped Data, Cache and Dalvik, but nothing changes.
Sometimes I just get the first screen (ALCATEL onetouch - powered by Android) and then it reboots, sometimes it goes a bit further with the other two screens (Idol 3 and the droid getting blue) but then it reboots again.
Should I try with Repair or Change File System?
On TWRP I've tried to restore data (but don't know if that would have helped) but when I select the Package to restore (2017-05-14-07-37-44_LRX22G_release_keys) I get the error 'No partition selected for restore'.
I've wiped Data, Cache and Dalvik, but nothing changes.
Sometimes I just get the first screen (ALCATEL onetouch - powered by Android) and then it reboots, sometimes it goes a bit further with the other two screens (Idol 3 and the droid getting blue) but then it reboots again.
Should I try with Repair or Change File System?
On TWRP I've tried to restore data (but don't know if that would have helped) but when I select the Package to restore (2017-05-14-07-37-44_LRX22G_release_keys) I get the error 'No partition selected for restore'.[/QUOTE]
Hello.
I've tried restoring that backup again.
Here's the messages I got while restoring:
Wiping System
Formatting System using make_ext4fs...
Restoring System...
[System sone (315 seconds)]
Wiping Data (excl. storage)
Wiping data without wiping /data/media...
Done.
Restoring Data (excl. storage)...
[Data (excl.storage) done (1246 seconds)]
Restoring Recovery...
[Recovery done (6 seconds)]
Restoring Boot...
[Boot done (7 seconds)]
Restoring EFS...
E:Unable to find dile system (first period).
E:Unknown restore method for '/efs2'
E:ADB Restore failed
Done processing script file
Done again 'wipe Data, Cache and Dalvik' before rebooting, but then it keeps rebooting again.
Any chance to get back to 5.0.2 stock rom without restoring that backup?
In case, could I install again LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl?
Thanks.
---------- Post added at 12:42 ---------- Previous post was at 12:33 ----------
On TWRP when I try to restore data (hoping that this would make phone booting ok) I am asked 'Select Partition to Restore:' but there's nothing I can select... and if I swipe to resore I get the error 'No partition selected for restore'.
Can't I restore the backup I've done with TWRP?
---------- Post added at 13:30 ---------- Previous post was at 12:42 ----------
trying to flash LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl again I get these messages:
Installing zip file '/external_sd/lineage-13.0-20170408-UNOFFICIAL-idol347.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1491616539
detected filesystem ext4 for /dev/block/mmcblk0p25
unmount of //system failed (-1): Device or resource busy
Patching system image unconditionally...
Verifying the update system image...
system partition has unexpected contents after OTA update
in red: Updater process ended with ERROR: 7
in red: Error installing zip file '/external_sd/lineage-13.0-20170408-UNOFFICIAL-idol347.zip'
Updating partition details...
...done
I've wiped cache/dalvik and tried installing again
I get these messages:
Installing zip file '/external_sd/lineage-13.0-20170408-UNOFFICIAL-idol347.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 1491616539
unmount of //system failed (-1): Device or resource busy
detected filesystem ext4 for /dev/block/mmcblk0p25
mount: failed to mount /dev/block/mmcblk0p25 at /system: Device or resource busy
Patching system image unconditionally...
Verifying the update system image...
Verified the updated image.
detected filesystem ext4 for /dev/block/mmcblk0p25
mount: failed to mount /dev/block/mmcblk0p25 at /system: Device or resource busy
unmount of //system failed (-1): Device or resource busy
script succeded: result was [0.200000]
Updating partition details...
...done
When I've rebooted system nothing changes (keeps rebooting after the first screen)
Booted phone in recovery, wiped dalvik, system, data, internal storage and cache.
Then tried restore via adb and got the message:
command is: 'adbrestore' and there is no value
E:Error opening TW_ABD_BU_CONTROL
Done processing script file
Then wiped again data and cache and flashed again LineageOS 13.0 for Alcatel ONETOUCH IDOL 3 4.7 rom by alecbl (with august security patch).
But still the phone keeps rebooting after the first screen.
So I've wiped data, cache and dalvik again and tried with 'adb restore Backup_14052017.bak' and got these messages:
Here's the messages I got while restoring:
Wiping System
Formatting System using make_ext4fs...
Restoring System...
[System sone (232 seconds)]
Wiping Data (excl. storage)
Wiping data without wiping /data/media...
Done.
Restoring Data (excl. storage)...
[Data (excl.storage) done (996 seconds)]
Restoring Recovery...
[Recovery done (6 seconds)]
Restoring Boot...
[Boot done (5 seconds)]
Restoring EFS...
in red - E:Unable to find file system (first period).
in red - E:Unknown restore method for '/efs2'
in red - E:ADB Restore failed
Done processing script file
Done again 'wipe Data, Cache and Dalvik' before rebooting, but then it keeps rebooting (or after the first screen or when the droid is getting blue)...
Try mobile Q upgrade in DOWNLOAD MODE.
https://forum.xda-developers.com/idol-3/help/mobile-upgrade-q-5-0-0-t3349508
I seem to have a damaged data partition on my Nook HD. All attempts to wipe, restore or write to the partition are unsuccessful using multiple TWRP versions and CWM. Attempts to flash ROMs, including all stock ROMs are unsuccessful. Once in a while I see a warning: "This /data backup was made with ext4 file system! The backup may not boot unless you change back to ext4." (Yes, that's ext4 x 2, but restoring usually just exits on an error).
Does anyone know a way to reformat or otherwise repair my /data partition?
Thank you.