[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.
Anyone have any idea?
Thanks
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?
You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes
I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.
you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)
Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.
Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/
Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.
I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Gaby_64 said:
I have the latest twrp, formated data and everything, still appears,
the only rom that succeeds in installing without that appearing is pure nexus
tried supersu, magisk, no-verity-opt-encrypt patch
Click to expand...
Click to collapse
Does TWRP print anything about "successfully decrypting /data with default password" in the console when it starts?
Go WIPE > ADVANCED WIPE > check the box next to "Data" > REPAIR OR CHANGE FILE SYSTEM. What does it say the file system of /data is?
Edit: Did you format /data before or after the issue happened? Never mind, you have to have formated /data afterwords if you were trying different ROMs.
ext4
i dont see the console
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
troy5890 said:
Im having the same problem when i try install RR. It keeps saying "To Start Android, enter your password". im on twrp 3.0.4-1 . Anybody know whats wrong?
EDIT: Nevermind, ext4 data was f2fs for some reason
Click to expand...
Click to collapse
i tried as both f2fs(performance is worth it) and ext4
Gaby_64 said:
ext4
i dont see the console
Click to expand...
Click to collapse
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Doc Ames said:
Hit the menu button (on the nav bar) after TWRP boots.
I dunno man. I've had this happen to me twice and the same thing worked for me both times:
* TWRP reports /data as ext4 (expected because that's what I use)
format /data (returns error 255 and various other errors)
reboot TWRP
* TWRP reports /data as f2fs
change /data back to f2fs
Worst case scenario, I think an EDL flash that wipes /data would fix it.
When you say format data do you mean using the "format data" option in the wipe menu (as opposed to a regular wipe)?
---------- Post added at 10:34 PM ---------- Previous post was at 09:42 PM ----------
Now that I think about it there might not be anything wrong with your data partition. You might have changed ROMs without removing your PIN first.
Use TWRP's file manager to delete the following files:
/data/system/gatekeeper.password.key
/data/system/gatekeeper.patern.key
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
You should boot into Android and unlock without a PIN. If it does ask try the last PIN you used.
Click to expand...
Click to collapse
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
troy5890 said:
I noticed on twrp 3.0.4-1, when i format data, the file system turns i to f2fs and i have to keep turning it back to ext4. ive been trying to go back to stock, but when i do, i check the status bar to see if everything is alright because i normally see old setting from a custom rom on there. this indicates that my data was not wiped properly. i was wondering if anyone has been having this issue?
Click to expand...
Click to collapse
May I ask, why are you using that version of TWRP?
Choose an username... said:
May I ask, why are you using that version of TWRP?
Click to expand...
Click to collapse
It's the only version that will boot up successfully when flashed through fastboot.
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
It's the only version that will boot up successfully when flashed through fastboot.
Click to expand...
Click to collapse
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Choose an username... said:
but can't you download the 3.1 img and flash it on twrp itself with the flash image option?
Click to expand...
Click to collapse
I tried but it ended up not flashing successfully
Sent from my ZTE A2017U using XDA-Developers Legacy app
troy5890 said:
I tried but it ended up not flashing successfully
Click to expand...
Click to collapse
all hail axon7tool then :v
Choose an username... said:
all hail axon7tool then :v
Click to expand...
Click to collapse
Looks like I'll give that a try, thank you
Sent from my ZTE A2017U using XDA-Developers Legacy app
Hello everyone,
I have a problem with my Le Pro 3. I installed an update a few days ago over the Lineage 15.1 settings. Like always the phone restarted in TWRP and everything went fine. But after that it did not reboot normally. Instead the Recovery mode was booted. At this point I should mention that I bought the phone used with Lineage 15.1 and have never flashed Android before.
So I read a lot (really a lot) and tried everything I could find in this forum until nothing worked anymore
Last chance I found in the forum was QFIL using FlashOne.
This worked fine (after a few tries). After that I could reinstall TWRP (tried different versions) using TOOL ALL IN ONE and enter Recovery Mode again.
After bringing it back to life I decided to install Lineage 15.1 again. So first formatting Internal Storage, then wiping everything and give it a go. No problem during installation but phone boots in Recovery Mode again.
So nothing new. Next try: Installing the latest versions of TWRP and Lineage 16.
I started again with FlashOne to clean everything up. Installed TWRP version from the Lineage 16 thread.
But I was not able to format Internal Storage: "Failed to mount '\vendor' (invalid argument)"
Okay. Tried to install Lineage 16 anyways. Again 2 errors: "Updater process ended with ERROR: 7 Error installing zip file '\sdcard.......zip' " AND "Failed to mount '\vendor' (invalid argument)".
At the moment I am not sure what to do because I am really new to the topic. I read a lot and tried everything.
Is this a possible hardware problem or did I do something wrong/ miss anything?
Would love to use my Le Pro 3 again. Love this phone.
Thanks for any advice,
Max---Power
UPDATE:
Managed to install the latest TWRP 3.2.3 TREBLE LP3 in ALL In ONE TOOL and after that I could format and install Lineage 16 without errors.
When restarting the phone TWRP does not say "no OS on phone", so I think Lineage is ready to use.
But after restart same issue: Boots in Recovery Mode.
Please help
Okay. Still no progress.
Tried different Firmwares and started all over again with FlashOne2.0.
ATM I managed to install TWRP with Magisk over TOOL ALL IN ONE , then Firmware 20S, then a partitions.zip and then Lineage 16.
No Errors, everything was okay. Vendor is mountable and TWRP does not say "No OS installed".
But it still boots to Recovery Mode.
Can I check somehow if Lineaoge OS ist really installed over the FileManager in TWRP?
Or any other tips to verify the Installation?
Max---Power said:
Okay. Still no progress.
Tried different Firmwares and started all over again with FlashOne2.0.
ATM I managed to install TWRP with Magisk over TOOL ALL IN ONE , then Firmware 20S, then a partitions.zip and then Lineage 16.
No Errors, everything was okay. Vendor is mountable and TWRP does not say "No OS installed".
But it still boots to Recovery Mode.
Can I check somehow if Lineaoge OS ist really installed over the FileManager in TWRP?
Or any other tips to verify the Installation?
Click to expand...
Click to collapse
First, you didn't need to use Qfil for this issue.
Okay, I am leaving my house at this very moment so I can only give you a few minutes. But will provide more details in a few hours.
Potential Quick Fix
If you can get into TWRP : Use my Recovery to restore your phone.
https://forum.xda-developers.com/showpost.php?p=75021582
Instructions are on that page
Basics
It has to be placed on your SD card and unpacked. Use Twrp to restore and select all options except for EFS, Your EFS is not damaged and you would only want to change this in a worse case scenario.
After restoring the recovery, you will have an older version of TWRP, root and EUI.
From there you can start over.
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Max---Power said:
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Click to expand...
Click to collapse
When you go into TWRP, Reboot to Recovery, yes check boxes to install the TWRP manager. When you boot into TWRP > do not choose read only mode.
You may have an encryption issue, which can be resolved but try this first.
Once back in Twrp, go to restore, you should see the folder that stasrt with 1970-xxx.xxx etc
Choose that
No you will see choose Partitions to restore choose everything except for EFS > then select Swipe at the bottom.
\When that is finished reboot to Twrp ,
You are now back on a clean version of EUI with Root and Twrp.
Now at this point you need to update to the latest version of TWRP ( only the version that is compatible for your device. ) Flash new TWRP and Reboot to Recovery > At this point , using a OTG usb drive would be the easiest way to go forward.
If you don't have one , Place your Rom in the SD storage, along with Magisk 17.3 and a compatible Gapps ( choose something that is still supported such as AICP of Lineage)
Flash the Rom by clicking install, next flash Gapps and then Magisk > Reboot to recovery, then reboot to system > Finished
If you are still having issues after all of this> Send me a PM and I can help you over the phone/team viewer as I just did for Roger. His similar issue is resolved and he is now using Android 9.0
Right now its 7:00 pm EST, I will not be available until 10 pm EST
---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------
Max---Power said:
Thank you very much for this quick guide.
You made my day already!
So I started all over again with the following steps:
1. QFIL via FlashOne
after that Windows says: You have to format the drive
2. TWRP (3.2.2 LP3) via TOOL ALL IN ONE with Magisk 17.3
3. TWRP-> Wipe-> Format data to get the full volume of the drive
4. Reboot to Recovery to get TWRP Folder created
5. Copied Backup to sdcard\TWRP
6. Wipe Dalvik, System, Cache and Data
4. TWRP-> Restore-> extracted folder
5. Everything except EFS
6. Reboot-> Recovery
7. Reboot-> System
TWRP asks to install the app, so I guess there is an OS.
Even if I reboot System the Phone starts Recovery Mode.
Problem unfortunately not solved :crying:
Click to expand...
Click to collapse
Also click under my post and click reply, otherwise, I will not get your message. To PM click my name and you will see the option to send a message.
tsongming said:
When you go into TWRP, Reboot to Recovery, yes check boxes to install the TWRP manager. When you boot into TWRP > do not choose read only mode.
You may have an encryption issue, which can be resolved but try this first.
Once back in Twrp, go to restore, you should see the folder that stasrt with 1970-xxx.xxx etc
Choose that
No you will see choose Partitions to restore choose everything except for EFS > then select Swipe at the bottom.
\When that is finished reboot to Twrp ,
You are now back on a clean version of EUI with Root and Twrp.
Now at this point you need to update to the latest version of TWRP ( only the version that is compatible for your device. ) Flash new TWRP and Reboot to Recovery > At this point , using a OTG usb drive would be the easiest way to go forward.
If you don't have one , Place your Rom in the SD storage, along with Magisk 17.3 and a compatible Gapps ( choose something that is still supported such as AICP of Lineage)
Flash the Rom by clicking install, next flash Gapps and then Magisk > Reboot to recovery, then reboot to system > Finished
If you are still having issues after all of this> Send me a PM and I can help you over the phone/team viewer as I just did for Roger. His similar issue is resolved and he is now using Android 9.0
Right now its 7:00 pm EST, I will not be available until 10 pm EST
---------- Post added at 08:14 PM ---------- Previous post was at 08:13 PM ----------
Also click under my post and click reply, otherwise, I will not get your message. To PM click my name and you will see the option to send a message.
Click to expand...
Click to collapse
Thank you very much for your effort! I like the way you describe and hope this will work out.
I did all you described. First part is up until my point 6.
I keep on numbering. Here is what I did afterwards:
8. TWRP-> Install-> twrp-3.2.3-0-20181031-codeworkx-zl1.img-> Recovery selected
9. Reboot-> Recovery (Version is the updated one)
10. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
Failed to mount '/vendor' (invalid argument)
-> I got that already. I have to install partition.zip
11. Install-> partition.zip
12. Wipe Dalvik, System, Cache and Data
13. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
-> Told you I read a lot: This could be the wrong Firmware
14. Install-> firmware-20S-X720-le_zl1.zip
15. Reboot Recovery
16. Wipe Dalvik, System, Cache and Data
17. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
-> finally without errors
18. Install-> Magisk-v17.3.zip
19. Install-> open_gapps-arm64-9.0-pico-20181125.zip
20. Reboot Recovery
Install System App? -> YES
7. Reboot System
Same as before. Not booting to System. TWRP starts.
Could it be the encryptionm issue? Or some other ideas?
If you want you can reply here, so everyone can read.
If it gets too complicated we cann arrange Skype or TeamViewer. Problem with that is that I live in Europe -> MEZ. It is 5:30PM right now.
Max---Power said:
Thank you very much for your effort! I like the way you describe and hope this will work out.
I did all you described. First part is up until my point 6.
I keep on numbering. Here is what I did afterwards:
8. TWRP-> Install-> twrp-3.2.3-0-20181031-codeworkx-zl1.img-> Recovery selected
9. Reboot-> Recovery (Version is the updated one)
10. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
Failed to mount '/vendor' (invalid argument)
-> I got that already. I have to install partition.zip
11. Install-> partition.zip
12. Wipe Dalvik, System, Cache and Data
13. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage.....zip'
-> Told you I read a lot: This could be the wrong Firmware
14. Install-> firmware-20S-X720-le_zl1.zip
15. Reboot Recovery
16. Wipe Dalvik, System, Cache and Data
17. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
-> finally without errors
18. Install-> Magisk-v17.3.zip
19. Install-> open_gapps-arm64-9.0-pico-20181125.zip
20. Reboot Recovery
Install System App? -> YES
7. Reboot System
Same as before. Not booting to System. TWRP starts.
Could it be the encryption issue? Or some other ideas?
If you want you can reply here, so everyone can read.
If it gets too complicated we can arrange Skype or TeamViewer. Problem with that is that I live in Europe -> MEZ. It is 5:30PM right now.
Click to expand...
Click to collapse
Okay , there seems to be a Brand NEW bug with the most recent version of TWRP ( your Vendor issue) I saw this issue yesterday with someone else that I helped privately
Use this version of TWRP instead
https://forum.xda-developers.com/le-pro3/development/recovery-twrp-3-x-p-codeworkx-t3844528
If so reason, you get the same error use an old version of non treble TWRP first and then the one from my link.
This will absolutely fix this issue, so that you can go forward.
Edit after re-reading your post -
On point 6 you mentioned wipe> Format resolves encryption, wipe does not.
Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
You do not need the partition zip files, that is for an outdated version of TWRP
Try the old version of TWRP first, install the Rom> Gapps> Magisk> Reboot to Recovery
Flash new Treble TWRP to the Recovery partition. > Issue should be resolved
tsongming said:
Okay , there seems to be a Brand NEW bug with the most recent version of TWRP ( your Vendor issue) I saw this issue yesterday with someone else that I helped privately
Use this version of TWRP instead
https://forum.xda-developers.com/le-pro3/development/recovery-twrp-3-x-p-codeworkx-t3844528
If so reason, you get the same error use an old version of non treble TWRP first and then the one from my link.
This will absolutely fix this issue, so that you can go forward.
Edit after re-reading your post -
On point 6 you mentioned wipe> Format resolves encryption, wipe does not.
Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
You do not need the partition zip files, that is for an outdated version of TWRP
Try the old version of TWRP first, install the Rom> Gapps> Magisk> Reboot to Recovery
Flash new Treble TWRP to the Recovery partition. > Issue should be resolved
Click to expand...
Click to collapse
Hello and thanks for the quick help!
That is the link I got the orther TWRP from I guess.
I now tried the oldest Version listed there, did not work.
The second latest does. (twrp-3.2.3-0-20180919-codeworkx-zl1.img)
I like numbers
22. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
23. Reboot-> Recovery
24. Wipe Dalvik, System, Cache and Data
25. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
E:String resource 'zip_compatible_err' not found. Using default value. Zip Treble compatibility error!
Error installing zip file '/sdcard/lineage....zip'
->This is a new one. Lets try a newer TWRP-version
26. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
27. Reboot-> Recovery
28. Wipe Dalvik, System, Cache and Data
29. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
30. Install-> open_gapps-arm64-9.0-pico-20181125.zip
31. Install-> Magisk-v17.3.zip
32. Reboot Recovery
Install System App? -> YES
33. Reboot System
Same issue again. Rebooting in Recovery Mode.
I am going crazy. Did I do anything wrong?
Hope you are not going crazy
---
Saw your edit too late, so here is my EDIT:
After I reached point 33 I did the following:
34. Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
35. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
36. Reboot Recovery
37. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Same Error like before. So new TWRP...
38. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
39. Reboot Recovery
40. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
41. Install-> open_gapps-arm64-9.0-pico-20181125.zip
42. Install-> Magisk-v17.3.zip
43. Reboot Recovery
Install System App? -> YES
44. Reboot System
Again: going directly into Recovery Mode
Max---Power said:
Hello and thanks for the quick help!
That is the link I got the orther TWRP from I guess.
I now tried the oldest Version listed there, did not work.
The second latest does. (twrp-3.2.3-0-20180919-codeworkx-zl1.img)
I like numbers
22. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
23. Reboot-> Recovery
24. Wipe Dalvik, System, Cache and Data
25. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
E:String resource 'zip_compatible_err' not found. Using default value. Zip Treble compatibility error!
Error installing zip file '/sdcard/lineage....zip'
->This is a new one. Lets try a newer TWRP-version
26. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
27. Reboot-> Recovery
28. Wipe Dalvik, System, Cache and Data
29. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
30. Install-> open_gapps-arm64-9.0-pico-20181125.zip
31. Install-> Magisk-v17.3.zip
32. Reboot Recovery
Install System App? -> YES
33. Reboot System
Same issue again. Rebooting in Recovery Mode.
I am going crazy. Did I do anything wrong?
Hope you are not going crazy
---
Saw your edit too late, so here is my EDIT:
After I reached point 33 I did the following:
34. Wipe> Format> type Yes> Wipe>Reboot to Recovery> Advanced Wipe> Reboot to Recovery
35. Install-> twrp-3.2.1-0-20180413-codeworkx-zl1.img-> Recovery selected
36. Reboot Recovery
37. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
Same Error like before. So new TWRP...
38. Install-> twrp-3.2.3-0-20180919-codeworkx-zl1.img-> Recovery selected
39. Reboot Recovery
40. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
41. Install-> open_gapps-arm64-9.0-pico-20181125.zip
42. Install-> Magisk-v17.3.zip
43. Reboot Recovery
Install System App? -> YES
44. Reboot System
Again: going directly into Recovery Mode
Click to expand...
Click to collapse
So there is still a problem with your storage, did you ever change the partition type from Ext4 to F2FS? I could be wrong but I am going to guess that maybe you did> Since a format should have resolved this issue, yesterday. F2FS is a bad idea and there is no benefit. > so change it back to EXT4 > Of course only if you did in fact change the format type.
Don't worry too much, you are not the first person that this has happened to, and there will be someone else with issue next week.
As far as numbers, how about asterisks, I typed similar instruction out a hundred times within the Leeco threads, search and you will see that I used instructions with numbers a thousand times already so I am switching it up :silly:
Try this:
Click Mount , make sure that System, Vendor, Cache, Data, are selected > Click Home key
Format storage once again , Reboot to Recovery, Click Advanced> Click File Manager > What do you see here?
It should only show a TWRP folder and nothing else > If you see more that folder the storage is not getting formatted.
If you only see the TWRP Folder
Flash Rom Twice, Flash Magisk> Reboot to Recovery, ( check Boxes)
Boot to system, and see If it boots. If it boots to system > Go back to Recovery > wipe cache > Flash Gapps> Boot to system
Still have an issue
Do Full Wipe ... Yes Again...unfortunately.
flash Rom
flash Magisk
flash dm-verity & force encryption disabler : http://zackptg5.com/android.php#disverfe
Flash Gapps
Reboot to Recovery > Wipe cache ( only cache) Reboot to system > Did this work? Yes, thats awesome that will be $5.99
Oh my God, you still have an Issue
Let me know, there is still other things that we can try.
tsongming said:
So there is still a problem with your storage, did you ever change the partition type from Ext4 to F2FS? I could be wrong but I am going to guess that maybe you did> Since a format should have resolved this issue, yesterday. F2FS is a bad idea and there is no benefit. > so change it back to EXT4 > Of course only if you did in fact change the format type.
Don't worry too much, you are not the first person that this has happened to, and there will be someone else with issue next week.
As far as numbers, how about asterisks, I typed similar instruction out a hundred times within the Leeco threads, search and you will see that I used instructions with numbers a thousand times already so I am switching it up :silly:
Try this:
Click Mount , make sure that System, Vendor, Cache, Data, are selected > Click Home key
Format storage once again , Reboot to Recovery, Click Advanced> Click File Manager > What do you see here?
It should only show a TWRP folder and nothing else > If you see more that folder the storage is not getting formatted.
If you only see the TWRP Folder
Flash Rom Twice, Flash Magisk> Reboot to Recovery, ( check Boxes)
Boot to system, and see If it boots. If it boots to system > Go back to Recovery > wipe cache > Flash Gapps> Boot to system
Still have an issue
Do Full Wipe ... Yes Again...unfortunately.
flash Rom
flash Magisk
flash dm-verity & force encryption disabler : http://zackptg5.com/android.php#disverfe
Flash Gapps
Reboot to Recovery > Wipe cache ( only cache) Reboot to system > Did this work? Yes, thats awesome that will be $5.99
Oh my God, you still have an Issue
Let me know, there is still other things that we can try.
Click to expand...
Click to collapse
I did not change anything at the format of Internal Storage. Maybe it was done by the previous owner?
I tried cheking over Wipe-> Advanced Wipe-> Select Internal Storage-> Repair or change File System
But it says "Invalid partition selected" and deselects Internal Storage. Dont know if that is nomal.
45. Mount-> Select System, Vendor, Cache and Data-> Home key clicked
46. Wipe-> Format Data-> YES (prompt says "Formatting Data using make_ext4fs" so I guess thats right)
47. Reboot Recovery
48. Advanced-> Filemanager
In sdcard is just TWRP-folder which is empty.
49. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
50. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
51. Install-> Magisk-v17.3.zip
52. Reboot Recovery
53. Reboot System
Boots into Recovery
So once again!
54. Wipe-> Format Data
55. Reboot Recovery
56. Wipe Dalvik, System, Cache and Data
57. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
58. Install-> Magisk-v17.3.zip
59. Install-> Disable_Dm-Verity_ForceEncrypt_11.26.2018.zip
60. Install-> open_gapps-arm64-9.0-pico-20181125.zip
61. Reboot Recovery
62. Wipe Cache
63. Reboot System
Boots into Recovery
I am getting crazy...
I am doing this step by step with numbering that I (and everyone who has no clue) can understand what I do.
Dont worry about your 5.99$... If we can get this going I will name my firstborn child after you, if you want
Max---Power said:
I did not change anything at the format of Internal Storage. Maybe it was done by the previous owner?
I tried cheking over Wipe-> Advanced Wipe-> Select Internal Storage-> Repair or change File System
But it says "Invalid partition selected" and deselects Internal Storage. Dont know if that is nomal.
45. Mount-> Select System, Vendor, Cache and Data-> Home key clicked
46. Wipe-> Format Data-> YES (prompt says "Formatting Data using make_ext4fs" so I guess thats right)
47. Reboot Recovery
48. Advanced-> Filemanager
In sdcard is just TWRP-folder which is empty.
49. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
50. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
51. Install-> Magisk-v17.3.zip
52. Reboot Recovery
53. Reboot System
Boots into Recovery
So once again!
54. Wipe-> Format Data
55. Reboot Recovery
56. Wipe Dalvik, System, Cache and Data
57. Install-> lineage-16.0-20181119_175337-UNOFFICIAL-zl1.zip
58. Install-> Magisk-v17.3.zip
59. Install-> Disable_Dm-Verity_ForceEncrypt_11.26.2018.zip
60. Install-> open_gapps-arm64-9.0-pico-20181125.zip
61. Reboot Recovery
62. Wipe Cache
63. Reboot System
Boots into Recovery
I am getting crazy...
I am doing this step by step with numbering that I (and everyone who has no clue) can understand what I do.
Dont worry about your 5.99$... If we can get this going I will name my firstborn child after you, if you want
Click to expand...
Click to collapse
Okay this one needs to be brief. Because, I only have a few minute at the moment.
First, I am assuming that you have tried other Roms such as a Nougat Rom. Nougat Gapps etc.
Yes? Next.
Download the All in One tool (AIT) ,
https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
Ensure it's up to date and not blocked by your firewall.
Use the AIT, to double check that the bootloader is still unlocked. Next, use the advanced option to remove encrypted data/wipe phone.
Use AIT to download stock Rom, to fully restore phone to stock, which should also repair any partition damage
After, phone has been restored, you can check to see that Leeco recovery has also been restored.
Next, boot to and setup the system, including through basic Google. Setup.
If you can do all of those steps to then you should surely be able to go forward and prepare the phone for a custom Rom.
Hopefully, this will finally get it.
Well that was longer than intended, and I didn't check for typos. Do look past those.
Sent from my LEX727 using XDA Labs
tsongming said:
Okay this one needs to be brief. Because, I only have a few minute at the moment.
First, I am assuming that you have tried other Roms such as a Nougat Rom. Nougat Gapps etc.
Yes? Next.
Download the All in One tool (AIT) ,
https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
Ensure it's up to date and not blocked by your firewall.
Use the AIT, to double check that the bootloader is still unlocked. Next, use the advanced option to remove encrypted data/wipe phone.
Use AIT to download stock Rom, to fully restore phone to stock, which should also repair any partition damage
After, phone has been restored, you can check to see that Leeco recovery has also been restored.
Next, boot to and setup the system, including through basic Google. Setup.
If you can do all of those steps to then you should surely be able to go forward and prepare the phone for a custom Rom.
Hopefully, this will finally get it.
Well that was longer than intended, and I didn't check for typos. Do look past those.
Sent from my LEX727 using XDA Labs
Click to expand...
Click to collapse
First: Thank you very much for your effort. Don't be stressed, I have time. No need to hurry with a reply!
Yes I have tried Oreo before. But lets do that again:
64. Install-> lineage-15.1-20181129-nightly-zl1-signed.zip
65. Install-> Magisk-v17.3.zip
66. Install-> open_gapps-arm64-8.1-pico-20181129.zip
67. Reboot Recovery
68. Reboot System
Boots into Recovery
Lets try AIO:
(numbering from 1 because I can only count up to 70)
My X720 (64GB/6GB) is detected as LEX727, ist that alright?
1. Bootloader Status
Unlocked
2. Erse All Data / Decrypt Internal Storage
3. Flash Factory Image-> LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip
with Wipe all Data and Reboot after Flash
-> it reboots, vibrates two times and boots Recovery Mode (EUI with chinese checkboxes)
4. Long press Powerbutton
Boots into Recovery
At this point AIO says "no devices found" and the phone is not listed in Windows Explorer anymore.
Tried this before already. At this point I always used QFIL.
Any other plans, or am I screwed?
Max---Power said:
First: Thank you very much for your effort. Don't be stressed, I have time. No need to hurry with a reply!
Yes I have tried Oreo before. But lets do that again:
64. Install-> lineage-15.1-20181129-nightly-zl1-signed.zip
65. Install-> Magisk-v17.3.zip
66. Install-> open_gapps-arm64-8.1-pico-20181129.zip
67. Reboot Recovery
68. Reboot System
Boots into Recovery
Lets try AIO:
(numbering from 1 because I can only count up to 70)
My X720 (64GB/6GB) is detected as LEX727, ist that alright?
1. Bootloader Status
Unlocked
2. Erse All Data / Decrypt Internal Storage
3. Flash Factory Image-> LE_ZL1_LEX720-CN-FN-WAXCNFN5902012312S-5.9.020S-FASTBOOT.zip
with Wipe all Data and Reboot after Flash
-> it reboots, vibrates two times and boots Recovery Mode (EUI with chinese checkboxes)
4. Long press Powerbutton
Boots into Recovery
At this point AIO says "no devices found" and the phone is not listed in Windows Explorer anymore.
Tried this before already. At this point I always used QFIL.
Any other plans, or am I screwed?
Click to expand...
Click to collapse
Within the EUI Recovery: Reset the phone and then try boot.
You would not be able to access the phone from the PC until the system is setup. However, this should have fixed the issue if if was merely encryption or corruption.
Stockware does not resolve it and restoring my full backup recovery doesn't solve the issue. Then you could try flash the bootloader again, after using Qfil. Or try my Recovery one more time: https://forum.xda-developers.com/showpost.php?p=75021582
Outside of that we are beginning to run out of options. This issue is highly unusual and I now also talking to other people via PM with a very similar issue. A rare coincidence? These issues are always fixed with everything we have tried. Unfortunately, it could be a hardware issue.
tsongming said:
Within the EUI Recovery: Reset the phone and then try boot.
You would not be able to access the phone from the PC until the system is setup. However, this should have fixed the issue if if was merely encryption or corruption.
Stockware does not resolve it and restoring my full backup recovery doesn't solve the issue. Then you could try flash the bootloader again, after using Qfil. Or try my Recovery one more time: https://forum.xda-developers.com/showpost.php?p=75021582
Outside of that we are beginning to run out of options. This issue is highly unusual and I now also talking to other people via PM with a very similar issue. A rare coincidence? These issues are always fixed with everything we have tried. Unfortunately, it could be a hardware issue.
Click to expand...
Click to collapse
Within EUI the upper checkbox is update and the lower is reset, right?
So select the lower checkbox and click the right button.
Then it displays and error in red:"*chinesesymbols*Data*chinesesymbols*"
So probably something is wrong with Data...
I click the chinese OK and it goes on with wiping Cache.
Then I return to main screen and click the left button for reboot.
Phone vibrates twice and goes back into Recovery.
So once again from the beginning:
1. QFIL via FlashOne (zl1_qfil.zip)
2. AIO Bootloader Status: Unlocked
3. AIO Lock Boatloader
4. AIO Unlock Boatloader
ERROR:
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
5. command in adb: fastboot oem unlock-go
6. AIO Unlock Boatloader
Device already: unlocked!
This does not sound right.. Any clue?
If we cant get it fixed make a suggestion for a new (used) phone, pls
Should I buy LeEco again? Only had it for 4-5 month now.
Max---Power said:
Within EUI the upper checkbox is update and the lower is reset, right?
So select the lower checkbox and click the right button.
Then it displays and error in red:"*chinesesymbols*Data*chinesesymbols*"
So probably something is wrong with Data...
I click the chinese OK and it goes on with wiping Cache.
Then I return to main screen and click the left button for reboot.
Phone vibrates twice and goes back into Recovery.
So once again from the beginning:
1. QFIL via FlashOne (zl1_qfil.zip)
2. AIO Bootloader Status: Unlocked
3. AIO Lock Boatloader
4. AIO Unlock Boatloader
ERROR:
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
5. command in adb: fastboot oem unlock-go
6. AIO Unlock Boatloader
Device already: unlocked!
This does not sound right.. Any clue?
If we cant get it fixed make a suggestion for a new (used) phone, pls
Should I buy LeEco again? Only had it for 4-5 month now.
Click to expand...
Click to collapse
After everything that has been done, I feel that you without a doubt have a hardware issue, and unfortunately it is very likely the main board. It would be cheaper to buy another phone.
Ordinarily, I would say absolutely get another Leeco, I found a Brand new X727 on Ebay for $175. But, the more I think about it I would suggest moving on to another phone from a company that is still in business. Technically, Leeco still exists, but I doubt that they will do anything new with phones for a while. The have lost face, and it would be dificult for them to repair trust in their home country and attract investors.
As far as getting something else. I guess it depends on your budget. If you want stay around $200 I would consider the Xiaomi A2, Its plenty power enough, looks expensive and modern. Has plenty of Ram, HD space, and the battery is big enough. Plus it comes bloat free.
If you can spend $300 to $350 - Maybe consider the Xiaomi Poco F1 , Mi 8 or mi8 Lite. All stellar phones. The Mi8 is probably the overall best of the 3.
Hello,
I found this guy that had my similar problem,
I hope it's not my main board.
I have a x720
I tried to flash AICP 9.0 over dirtly ove the prevous ROM,
Got error 7 and /vendor unable to mount.
I donwloaded stock rom from LEECO but before that I've done a "Erase all data and decrypt internal storage" with "MAURO ALL IN TOLL", now that i think about it, very dumb move, anyway.
When I try to flash the LEECO stock rom i get those errors + Unable to mount /system
Hope anyone can help me.
fiume97 said:
Hello,
I found this guy that had my similar problem,
I hope it's not my main board.
I have a x720
I tried to flash AICP 9.0 over dirtly ove the prevous ROM,
Got error 7 and /vendor unable to mount.
I donwloaded stock rom from LEECO but before that I've done a "Erase all data and decrypt internal storage" with "MAURO ALL IN TOLL", now that i think about it, very dumb move, anyway.
When I try to flash the LEECO stock rom i get those errors + Unable to mount /system
Hope anyone can help me.
Click to expand...
Click to collapse
Your issue is not the board or even a big deal at all.
Can you boot into TWRP Recovery ( by pressing the volume up and power? ) If not go to the all in one thread and read the instructions
You can use the All in One tool to flash TWRP, Once TWRP has been installed,
Boot to Recovery
Format Storage
Type “Yes.”
afterwards select Wipe > Factory Reset
Now Reboot to Recovery > Check Boxes for TWRP Manager installation if you see them
Now you can try Installing your Rom, Gapps, and Magisk > Reboot to Recovery again /Check Boxes
Clear Cache ( Not Dalvik)
Reboot to System > You should now be fine.