Related
Hi, is there something i'm doing wrong, some wrong step?
1. Desire is S-OFF.
2. Mounted /system/app as r+w through Root Explorer.
3. Copied app to this directory (Google Earth, AutoSketch)
4. Made them 644 permissions. Rebooted.
5. Apps were installed, but they force close, no way to open them.
What could be the error from the above ?
Tnx
Can really see anything wrong here. Are the apps installed to begin with in data/app? If so, there is no need to change the permissions (even too the permissions might be correct, really don't know) also is there enough room on the system partition?
Last thing is that it might not work on Oxygen RC, no idea why but that was the first time I had FC after moving stuff to the system partition.
m4dm4n123 said:
Hi, is there something i'm doing wrong, some wrong step?
1. Desire is S-OFF.
2. Mounted /system/app as r+w through Root Explorer.
3. Copied app to this directory (Google Earth, AutoSketch)
4. Made them 644 permissions. Rebooted.
5. Apps were installed, but they force close, no way to open them.
What could be the error from the above ?
Tnx
Click to expand...
Click to collapse
try to clear Dalvik-cache after pushing apps.
Tried clearing Dalvik-Cache, same error.
Something from the logcat :
"[ 01-03 20:33:05.650 983:0x3d7 I/ActivityThread ]
Publishing provider com.google.earth.SuggestionProvider: com.google.earth.SearchSuggestion
[ 01-03 20:33:05.710 983:0x3d7 W/dalvikvm ]
Exception Ljava/lang/UnsatisfiedLinkError; thrown during Lcom/google/earth/EarthActivity;.<clinit>
[ 01-03 20:33:05.710 983:0x3d7 W/dalvikvm ]
Class init failed in newInstance call (Lcom/google/earth/EarthActivity
[ 01-03 20:33:05.710 983:0x3d7 D/AndroidRuntime ]
Shutting down VM
[ 01-03 20:33:05.710 983:0x3d7 W/dalvikvm ]
threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)"
Most simple way:
Install the apk the usual way ("run" the file)
Use "root explorer" to move the installed apk from /data/app to /system/app
Reboot...
Done!!!
Sent from my HTC Desire using XDA App
Tnx man, that did it. Uninstalled previous versions of apps in /system/app if they existed, moved some of the apps from the /data/app to the /system/app.
Rebooted to recovery , cleared Dalvik Cache (this is,i believe, a must because old apps files will remain), and that's that.
what do you gain by installing app as a system app and if is s-off needed?
Since I'm on Cyanogenmod, I have 125 MB unused space on 250 MB /system partition. /data partition is ultra small, and there is always a space problem with it.
Until Alpharev makes partition tables for PVT-4 Desires (/system=150MB, /data=200MB), this workaround will just have to do. I don't like it when "internal memory" is only 25MB free, and /system has plenty of space waiting.
S-OFF is definitely a must, because of r+w privileges on a /system partition.
P.S. I don't care about Anything2SD solutions, I like it clean and transparent.
I am suddenly unable to upgrade the nightlies, which I've been previously able to do: I'm currently stuck on the version from 8/11/11 (#157?). After doing the recovery reboot here are the messages:
rcS!
Populating /dev using udev: done
Initializing random number generator… done.
modprobe: chdir(2.6.32.9): No such file or directory
Starting network..
Detected Standard B&N nook layout, emmc first
It appears the SD card is already properly formatted
Skiping format
Mounting /dev/nmcblk1p1 as /boot
Looking for the install images…
Installing package cm_encore_full-166.zip
Archive: /boot/cm_encore_full-166.zip
unzip: short read
updating kernel
Updating bootloader
Checking for Dalingrin kernel update …not found, skipping
creating synlinks and updating permissions
cat: can’t open ‘META-INF/com/google/android/updater-script’ : No such file or directory
Deleting install file
Rm: can’t remove ‘/boot/cm_encore_full-166.zip’ : Read-only file system
Let’s see if you have gapps installer too
Gapps installer not found, skipping installation
Flushing caches
Cleaning recovery flag
1+0 records in
1+0 records out
All steps complete, flushing caches again
Preparing to shutdown
I've tried various nightlies since then and they all end up with the above message (except for the different version #'s) Seeing as I'd prefer to not have to start over any assitance would be appreciated.
Thanks.
Here the link to the newest roms for the doogee x3
www.needrom.com/category/doogee/x3-doogee/
I am using linux and use the sp flash tool with wine with looks good so far,i have to study it first before starting,but i want to start the thread already.
first problem is unpacking the rar file ..... syntax error nearby unexpected symbol 'newline' after the command #unrar e <DOOGEE-X3-6.0.rar >solved,installing unrar and reboot system(!)...
second problem rooting phone after installing ...BETA-SuperSU-v2.50.zip... recovery said installation aborted...
Than smart phone flash tool wont recognice the doogee x3...
phone is connected through usb and connected as usb storage...(i am googling for advice...)
thanks for some advice
(SOLVED see post from 9okt)rooting DOOGEE X3
After putting BETA-SuperSU-v2.50.zip. on my sdcard i went in recovery mode,volume up and power button pressed, than choosed update system by sdcard,pressed power button,choose BETA-SuperSU-v2.50.zip and pressed power button.... recovery said installation aborted..
what to do...
thanks for some advice
after flashing the recovery i got the following result...
a red line(download DA 100%) and an popup telling ERROR: S_ TIMEOUT (1042)
on the terminal....
[[email protected] SP_Flash_Tool_exe_Linux_v5.1632.00.100]# ./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
Qt: Session management error: None of the authentication protocols specified are supported
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_browser_clicked()
QThread::setPriority: Cannot set priority, thread is not running
"07-30-2016"
QObject::moveToThread: Cannot move objects with a parent
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.0
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.1
[email protected]/devices/pci0000:00/0000:00:13.2/usb2/2-5/2-5:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1472583651.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_TIMEOUT
Disconnect!
BROM Exception! ( ERROR : S_TIMEOUT (1042)
[HINT]:
)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
thanks for some advice...
connecting not as root but as user after setting gtk theme in user dir
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1472900250.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
Connect BROM failed: S_COM_PORT_OPEN_FAIL
Disconnect!
BROM Exception! ( ERROR : S_COM_PORT_OPEN_FAIL (1013)
[COM] Failed to open COM port.
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,85))
solved,i installed ubuntu followed al the instructions put the flashtool on upgrade connectthe phone and android 6.0 was installed after a few minutes.
devrieshh said:
solved,i installed ubuntu followed al the instructions put the flashtool on upgrade connectthe phone and android 6.0 was installed after a few minutes.
Click to expand...
Click to collapse
I made it in Windows yesterday successfully. There is also a way to flash TWRP on Doogee X3 running Android 6.0.
Look here: http://4pda.ru/forum/index.php?showtopic=713470&st=100#entry51434308
The Problem is, I don't understand russian and I even can't type it. Also the Captcha is a major problem. I think there is an account needed to be able to download the board attachments. Otherwise "404" error. Could anyone Download TWRP for Android 6.0 from this site + the scatter file there ? Would be awesome :highfive:
EDIT: I got it and already installed it. it works ! twrp on doogee x3 running android 6.0. just flash it with sp flash tool. you know how if you had flashed 6.0 already
link: http://www18.zippyshare.com/v/yAM5FXOt/file.html
have fun
EDIT: don't try to root it. doesn't work. neither supersu, kingo root nor kingroot. i tried it and my nvram was corrupt after trying with supersu. had to flash back imei and wifi mac address. i'm back on android 5.1 for this device.
Flashing didnt work,it said coudnt find files or path wasnt right,a red line...
after a wile the flash window got black and wite got frosen,i closed it started to reload and then the flash window didnt showed up and the message in the therminal was ...
:~/Desktop/SP_Flash_Tool_exe_Linux_v5.1520.00.100$ ./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
QObject::moveToThread: Cannot move objects with a parent
so i dont know what to do now for the moment
solved,reinstalled ubuntu.. flashed TWRP_3.0.2_Doogee-X3_Android-6.0.zip
Ok i managed to root our doogee X3,tryed it with an old root tool used with my samsung gio,flashed with the TWRP 3.0.2.
SOLVED (file is already .img ,not .dat) trying to port cm-13.0-20160817-UNOFFICIAL-TECNO W4-nana (MTK 6580) i got a problem after the ./sdat2img.py command .../S2603_DG_A42_PUBLIC_M_V0.2.8_S160628$ sudo ./sdat2img.py system.transfer.list system.new.dat sys
tem.img
Traceback (most recent call last):
File "./sdat2img.py", line 131, in <module>
main(sys.argv)
File "./sdat2img.py", line 75, in main
version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "./sdat2img.py", line 43, in parse_transfer_list_file
trans_list = open(TRANSFER_LIST_FILE, 'r')
FileNotFoundError: [Errno 2] No such file or directory: 'system.transfer.list'
anybody know what to do...
doing the same with the cm 13 rom...
/cm-13.0-20160817-UNOFFICIAL-TECNO W4-nana$ sudo ./sdat2img.py cm-13.0-20160817-UNOFFICIAL-TECNO
%20W4-nana .transfer.list system.new.dat system.img
Traceback (most recent call last):
File "./sdat2img.py", line 131, in <module>
main(sys.argv)
File "./sdat2img.py", line 75, in main
version, new_blocks, commands = parse_transfer_list_file(TRANSFER_LIST_FILE)
File "./sdat2img.py", line 43, in parse_transfer_list_file
trans_list = open(TRANSFER_LIST_FILE, 'r')
FileNotFoundError: [Errno 2] No such file or directory: 'cm-13.0-20160817-UNOFFICIAL-TECNO%20W4-nana'
devrieshh said:
Ok i managed to root our doogee X3,tryed it with an old root tool used with my samsung gio,flashed with the TWRP 3.0.2.
Click to expand...
Click to collapse
[at first for everyone to know: it affects Android 6.0 for the Doogee X3. Android 5.1 is no problem.]
root checker told me my device is rooted after I flashed your zip. The problem I experienced was, I got no asking for root triggered by any app which uses root permission. And also when I try to update SuperSU binary inside the app it tells me there is no "su data" and it couldn't update it. I think to get a flawless root permission it would take a while
SOLVED $mkdir working and than.... $ sudo mount -t ext4 -o loop /img-tools/sys.raw working/
so i did succeed to format the system.img to sys.raw but after trying to mount the sys.raw image i got the following response after the in the tortual suggested command
Am I right that you are already working in the directory "/img-tools" and want to mount the sys.raw file in it ? So then, if you determine to mount "/img-tools/sys.raw" that this could be interpreted as mount "/img-tools/img-tools/sys.raw", a directory that doesn't exist ?
Or am I seeing something wrong ?
i have compiled the system.img file to sys.raw and i want the sys.raw folder so that you can swich framework,apps and other folders with roms to port
i want to have the outcom from the sys.raw ext4 file mounted in the /base home/working folder..
see .http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
mounting system.img should do the job ,so you do not have to format it to sys.raw.
i made a map working in the img-tools map,but with the command below i got ...mount point working/ does not exist
base home/img-tools$ sudo mount -t ext4 -o loop system.img working/
mount: mount point working/ does not exist
devrieshh said:
i have compiled the system.img file to sys.raw and i want the sys.raw folder so that you can swich framework,apps and other folders with roms to port
i want to have the outcom from the sys.raw ext4 file mounted in the /base home/working folder..
see .http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452
mounting system.img should do the job ,so you do not have to format it to sys.raw.
i made a map working in the img-tools map,but with the command below i got ...mount point working/ does not exist
base home/img-tools$ sudo mount -t ext4 -o loop system.img working/
mount: mount point working/ does not exist
Click to expand...
Click to collapse
I'm more familiar with DOS. But the principle should be the same.
i will try to understand the link you posted...will keep you informed
EDIT: if i'm right, then you are inside the "img-tools" folder and trying with this command to mount system.img to a folder named "working" in it.
e.g.: /base home/img-tools/working
but you want to mount it to the folder /base home/working, right ?
so you have to type it in another way. try: sudo mount -t ext4 -o loop system.img /base home/working/
I'm not sure what Linux expect. maybe the slash before "base home" in my example is not needed.
fixt it http://stackoverflow.com/questions/8663891/how-to-mount-the-android-img-file-under-linux
/Downloads/doogee x3 porting/base/base home/img-tools$ mkdir sys
[email protected]:~/Downloads/doogee x3 porting/base/base home/img-tools$ sudo mount -t ext4 -o loop sys.raw sys/
[email protected]:~/Downloads/doogee x3 porting/base/base home/img-tools$
i had to use my sys.raw file and make a sys map with ...mkdir sys ... command
How to convert .img to .raw... download img-tools extract it in a folder (http://forum.xda-developers.com/chef-central/android/guide-how-to-port-lollipop-marshmallow-t3283452) put the system.img from base rom with it and run the command... ./simg2img system.img sys.raw
I sat the whole night to find any supersu which roots flawless our doogee x3 on android 6.0. and i found it ! i flashed, installed, reflashed about hundred of times another supersu version by version downwards. it's the version 2.61 which works properly ! and yes, you can still use the playstore update of supersu + binary update inside the app without losing root or getting a boot stuck. see linked zip for working supersu you'll better save it safely
http://www89.zippyshare.com/v/iUH99ub0/file.html
EDIT: I'm not sure it could be important, but I kept the system partition as read only as I installed SuperSU. Maybe you want to do it also.
i bought a doogee x5 so i am no longer active in this forum
Hiya XDA, So i'm trying to back up my phone (Running CM13) to my memory stick, and it worked before, but now it seems to have broken and I don't know what the issue is. My log (adb pull /tmp/recovery.log) is below
Heres what I've tried
Reflashing TWRP
Going to a slightly older version (3.0.2-1)
Enabling and disabling encryption
with and without compression
Skipping MD5 and leaving it on
[BACKUP STARTED]
* Backup Folder: /usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/
Backing up Boot...
I:Reading '/dev/block/mmcblk0p34', writing '/usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/boot.emmc.win'
Iartition Backup time: 4
Backing up System...
Error opening: '/system/addon.d' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /usb-otg/TWRP/BACKUPS/ENU7N15A10005575/recovery.log
I:Set page: 'action_complete'
Iperation_end - status=1
E:error opening '/usb-otg/LOST.DIR' -- error: No such file or directory
E:error opening '/usb-otg/TWRP' -- error: No such file or directory
Looks as though your memory stick isn't formatted correctly. Try Fat32 or possibly EXT4
It is Fat32?
frap129 said:
Looks as though your memory stick isn't formatted correctly. Try Fat32 or possibly EXT4
Click to expand...
Click to collapse
I don't have access to a Linux machine, but I could format it in my phone?
I'll try that. and will post any updates.
UPDATE:
Formatted it in Android, still same error
UPDATE 2:
Tried a different USB stick, same error.
The USB sticks I am using are:
amazon.com/SanDisk-Cruzer-Orbit-Drive-SDCZ58-032G-B35/dp/B00BPHTH4C
and
amazon.com/SanDisk-Ultra-Flair-Performance-SDCZ73-064G-G46/dp/B015CH1NAQ/
Remove /system/addon-d in twrp ?
Will my phone work properly after doing that?
UPDATE:
Renamed it to addon-dee in my prefered Filemanager (ES) and it's backing up now.
(thank god I decided to use a USB3 stick this time)
UPDATE 2:
Phone backed up and now is working fine! thanks.
I was having the same error until I updated TWRP to the unofficial 3.0.2-3
I have this problem and l have 17g free space in my internal storage but receive error 255 and i don't find addon in my storage plz help me for fixing this error
Sent from my Le X820 using XDA-Developers mobile app
m890 said:
I have this problem and l have 17g free space in my internal storage but receive error 255 and i don't find addon in my storage plz help me for fixing this error
Sent from my Le X820 using XDA-Developers mobile app
Click to expand...
Click to collapse
Should be under /system/ . Are you rooted? I don't know if you can see that part of system if you're not rooted.
My device is rooted but this file isn't there.
Sent from my Le X820 using Tapatalk
m890 said:
I have this problem and l have 17g free space in my internal storage but receive error 255 and i don't find addon in my storage plz help me for fixing this error
Sent from my Le X820 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's not always the same file. Look at your log to see which file/dir is problematic.
SOLVED createTarFork() process ended with ERROR=255
SOLUTION
This solution worked on my Zenfone 3, running lineage Android 7.1.2.
I tried many other things, like flashing different versions of TWRP, deleting the recovery directory, renaming files and all the like.
You may deselect compression, change the TWRP-date / time : nothing works !
You need an PC / Notebook with adb installed.
- start your phone in recovery-mode (TWRP)
- connect to PC and get the recovery.log with following adb command
adb pull /tmp/recovery.log
You will find a copy of the file recovery.log in the directory, from which you started the command
- open an editor or choose your favourite file viewer to open recover.log
- search for the last entry of the word "Error"
- in the line before that, the recovery.log states the name of the file that causes the problem
(in my case it was /system/addon.d)
- disconnect phone from PC.
- restart your phone in "normal" restart (do NOT boot to recovery mode)
- use a root file browser (I used ES-explorer with root enabled) and navigate to that directory/file
- delete the file (which I did not do - I tried some other steps)
- restart phone
This took 3-4 minutes, but I did not delete the file addon.d right away. Instead, I did this:
step 1
navigated to /system/addon.d and copied addon.d to SD-card
step 2
in /system/ , I renamed addon.d "addon_BU.d".
This was successful. In /system/ , the only file visible was now "addon_BU.d"
step 3
tried to create a directory named addon.d inside /system/ because my recovery.log said quote\ ... system/addon.d (not a directory) ... \unquote
FAILED. The directory could not be created by ES-explorer
step 4
copied my backup file addon.d from SD-card back into its original location /system/.
This, I though, would work just fine, because I had renamed the original addon.d to addon_BU.d.
So after restoring addon.d , the only thing left to do would be delte addon_BU.d.
ES-explorer reported no error, but - surprise - there was no file "addon.d" present in /system/
The only file still there was "addon_BU.d"
well, let's go to
step 5
rename addon_BU.d back to it's original name "addon.d" using ES-explorer
FAILED.
addon_BU.d could not be renamed - this file really was screwed up big time !!!
I ended up with no addon.d - so I could have deleted it right away istead of starting my trial with step 1 ...
step 6
Anyway. Shut dowm my phone.
Rebooted my phone normally (not to recovery mode !!!)
This took considerably longer than normal - my heart rate had began to increase slightly if not to say I began to feel like a squirrel on red bull...
After roughly 3 minutes, I had a successful reboot to my OS (lineage Android 7.1.2)
step 7
Reboot again, this time to recovery mode (=TWRP)
and: backups work again.
Don't ask me why this worked and if it will work for you, but hey, give it a triy and let me know...
TheLMGN said:
Hiya XDA, So i'm trying to back up my phone (Running CM13) to my memory stick, and it worked before, but now it seems to have broken and I don't know what the issue is. My log (adb pull /tmp/recovery.log) is below
Heres what I've tried
Reflashing TWRP
Going to a slightly older version (3.0.2-1)
Enabling and disabling encryption
with and without compression
Skipping MD5 and leaving it on
[BACKUP STARTED]
* Backup Folder: /usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/
Backing up Boot...
I:Reading '/dev/block/mmcblk0p34', writing '/usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/boot.emmc.win'
Iartition Backup time: 4
Backing up System...
Error opening: '/system/addon.d' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
I:InfoManager saving '/usb-otg/TWRP/BACKUPS/ENU7N15A10005575/2016-12-10--16-58-06_cm_angler-userdebug_6.0.1_MOB30Z_b4fbca03c0/system.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /usb-otg/TWRP/BACKUPS/ENU7N15A10005575/recovery.log
I:Set page: 'action_complete'
Iperation_end - status=1
E:error opening '/usb-otg/LOST.DIR' -- error: No such file or directory
E:error opening '/usb-otg/TWRP' -- error: No such file or directory
Click to expand...
Click to collapse
1gnc said:
SOLUTION
This solution worked on my Zenfone 3, running lineage Android 7.1.2.
I tried many other things, like flashing different versions of TWRP, deleting the recovery directory, renaming files and all the like.
You may deselect compression, change the TWRP-date / time : nothing works !
You need an PC / Notebook with adb installed.
- start your phone in recovery-mode (TWRP)
- connect to PC and get the recovery.log with following adb command
adb pull /tmp/recovery.log
You will find a copy of the file recovery.log in the directory, from which you started the command
- open an editor or choose your favourite file viewer to open recover.log
- search for the last entry of the word "Error"
- in the line before that, the recovery.log states the name of the file that causes the problem
(in my case it was /system/addon.d)
- disconnect phone from PC.
- restart your phone in "normal" restart (do NOT boot to recovery mode)
- use a root file browser (I used ES-explorer with root enabled) and navigate to that directory/file
- delete the file (which I did not do - I tried some other steps)
- restart phone
This took 3-4 minutes, but I did not delete the file addon.d right away. Instead, I did this:
step 1
navigated to /system/addon.d and copied addon.d to SD-card
step 2
in /system/ , I renamed addon.d "addon_BU.d".
This was successful. In /system/ , the only file visible was now "addon_BU.d"
step 3
tried to create a directory named addon.d inside /system/ because my recovery.log said quote\ ... system/addon.d (not a directory) ... \unquote
FAILED. The directory could not be created by ES-explorer
step 4
copied my backup file addon.d from SD-card back into its original location /system/.
This, I though, would work just fine, because I had renamed the original addon.d to addon_BU.d.
So after restoring addon.d , the only thing left to do would be delte addon_BU.d.
ES-explorer reported no error, but - surprise - there was no file "addon.d" present in /system/
The only file still there was "addon_BU.d"
well, let's go to
step 5
rename addon_BU.d back to it's original name "addon.d" using ES-explorer
FAILED.
addon_BU.d could not be renamed - this file really was screwed up big time !!!
I ended up with no addon.d - so I could have deleted it right away istead of starting my trial with step 1 ...
step 6
Anyway. Shut dowm my phone.
Rebooted my phone normally (not to recovery mode !!!)
This took considerably longer than normal - my heart rate had began to increase slightly if not to say I began to feel like a squirrel on red bull...
After roughly 3 minutes, I had a successful reboot to my OS (lineage Android 7.1.2)
step 7
Reboot again, this time to recovery mode (=TWRP)
and: backups work again.
Don't ask me why this worked and if it will work for you, but hey, give it a triy and let me know...
Click to expand...
Click to collapse
Hi, thank you for a fix but this is an 10 month old thread. The issue was with TWRP 3.0.2-2. Along with an EFS issue that plagued TWRP 3.0.1-2, both issues have long since been resolved.
Sent from my Nexus 5X using Tapatalk
simple and working solution :
by @yannick818
"looks like it's an error with parallel apps oder multiple users. since i do not use something like that, i just removed this user with the android terminal emulator:
su
pm remove-user 999
everything was fine after that"
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
Hi,
I am trying to install the latest Lineage version on my Samsung Nexus 10 via twrp, but so far it always immediately fails with
Error E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/lineage-17.1-20220318-UNOFFICIAL-manta.zip'
I tried wiping the entire system, cache and all and I tried both the adb push method and sideloading adb and they all produce the exact same error.
This is my first time doing this type of thing, so any help would be greatly appreciated.
P.S. I am currently running Windows 10, but could boot into a Linux Live Medium if that would be useful.
Edit: I was following this tutorial for the setup.
I'm facing exactly the same issue here with the installation of `lineage-17.1-20220919-UNOFFICIAL-manta.zip` file.
I'm currently on the latest original Google Android ROM flashed with `image-mantaray-lmy49j.zip` and want to update the system to the lineage OS as above.
I'm using TWRP v3.6.2_9.
What I did:
- uploaded `lineage-17.1-20220919-UNOFFICIAL-manta.zip` to `/sdcard` location;
- wiped out `dalvik-cache` and `cache` partitions;
- tried to install `lineage-17.1-20220919-UNOFFICIAL-manta.zip` as a single installation file;
Got this error. Here is an output from recovery.log:
Code:
Installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Unmounting System...
I:Update binary zip
I:Extracting updater binary 'META-INF/com/google/android/update-binary'
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment not used in updater.
No path given to file labeling backend
selinux_android_file_context: Error getting file context handle (No such file or directory)
Warning: No file_contextsTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keysTarget: google/mantaray/manta:5.1.1/LMY49J/2640980:user/release-keys
Extracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 2 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 4 args
Backup/restore is not possible. Partition is probably empty
Patching system image unconditionally...
performing update
blockimg version is 4
maximum stash entries 0
creating stash /cache/recovery/4dd6bf24fbba9cc76c352f5c4cfaed0074be0244
535756800 bytes free on /cache (0 needed)
/cache/recovery/last_command doesn't exist.
erasing 3367 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,225950,228864,229947,230400]
new data receiver is still available after executing all commands.
Patching system image unconditionally...script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 0 second(s).
Error installing zip file '/sdcard/lineage-17.1-20220919-UNOFFICIAL-manta.zip'
Does anyone have any clue on what could be wrong here and why it fails?
unpack zip remove lines, then pack zip and try again. voilla
or utube eroor 7
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Cpluo said:
I'd the same problem with twrp but does did successfully for version 16 installation. I tried the above listed way but failed again. Same thing happened even I unchecked the system in twrp before flashing again. Need expert to help fix the issue. Appreciate in advanced!
Click to expand...
Click to collapse
Not enough space on /system. Resize the partition. After 17.1 is running for me. https://www.hovatek.com/forum/thread-32750.html
Thanks a lot Daniel! I will try your way.