I got my AT&T HTC One on Thursday and was so excited heading straight to unlocking bootloader, flashing custom recovery and then made mistake by skipping turning to s-off and went straight to custom rom.
The rom installed upto 97% and gets stuck at something to do with data_recursive: while trying to assign permissions.
Now i'm stuck with a device which I'm not sure can be helped to atleast back to stock rom with s-on
Any help will be greatly appreciated
marvoh said:
I got my AT&T HTC One on Thursday and was so excited heading straight to unlocking bootloader, flashing custom recovery and then made mistake by skipping turning to s-off and went straight to custom rom.
The rom installed upto 97% and gets stuck at something to do with data_recursive: while trying to assign permissions.
Now i'm stuck with a device which I'm not sure can be helped to atleast back to stock rom with s-on
Any help will be greatly appreciated
Click to expand...
Click to collapse
So you are s - off or s - on? past here your hboot info
Sent from my HTC One using Tapatalk 2
marvoh said:
I got my AT&T HTC One on Thursday and was so excited heading straight to unlocking bootloader, flashing custom recovery and then made mistake by skipping turning to s-off and went straight to custom rom.
The rom installed upto 97% and gets stuck at something to do with data_recursive: while trying to assign permissions.
Now i'm stuck with a device which I'm not sure can be helped to atleast back to stock rom with s-on
Any help will be greatly appreciated
Click to expand...
Click to collapse
don't need s-off to flash most roms....
what rom were you trying to flash?
can you get back into recovery or bootloader??
Managed to go back to stock then got s-off then tried to go to custom rom because AT&T doesn't have some features like internet-passthrough enabled only to get stuck at the same place. My screen is broken cannot read the whole error message but it occurs when rom is about to finish, something to do with additional symlinks and permissions
Here's the log file snippet
Finalizing Install
Creating toolbox symlinks
Installing busybox
about to run program [/system/xbin/busybox] with 4 args
Creating additional symlinks
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Solved
marvoh said:
Finalizing Install
Creating toolbox symlinks
Installing busybox
about to run program [/system/xbin/busybox] with 4 args
Creating additional symlinks
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Click to expand...
Click to collapse
Overcame this by using latest TWRP, apparently the version in the All in One tool is old
Related
Hi,
So im trying to flash the viper one (6.2.1) rom on my HTC one (m7) but it doesnt seem to work.
i came from cyanogenmod , now im back on stock , but still rooted, and have the latest TWRP recovery.
these are the errors at the logs i saved that i get.
Kernel Flashed.
Finalizing Install
Creating toolbox symlinks
symlink(): created [/system/xbin]
symlink(): created [/system/xbin/bb]
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Sat Jun 7 03:59:49 2014
I did wipe my date, cache etc, i did everything that i needed to, but i have no idea why this one doesn't work.
thanks in advance.
unaga123 said:
Hi,
latest TWRP recovery.
Click to expand...
Click to collapse
what version number would "latest" refer to? recommend you use 2.6.3.3 or .4
185
2.7 , but i managed to fix the problem by just reinstalling the Rom zip , i just flashed it again and had no error or anything oO , i hope it works now its booting, and thanks for the fast reply
unaga123 said:
2.7 , but i managed to fix the problem by just reinstalling the Rom zip , i just flashed it again and had no error or anything oO , i hope it works now its booting, and thanks for the fast reply
Click to expand...
Click to collapse
the 2.7 series TWRP are not always reliable, i still recommend you revert to 2.6.3.3 or .4
cheers
oh, okay thanks for the advice ^^
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
StATicxTW0T said:
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
Click to expand...
Click to collapse
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
BinBug said:
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
Click to expand...
Click to collapse
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
The first error or the second error
StATicxTW0T said:
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
Click to expand...
Click to collapse
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
BinBug said:
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
Click to expand...
Click to collapse
That error is caused by the version of TWRP you are using. Something about different versions and different updater scripts. Some have had sucess with 2.8.1, some with 2.6.3.1 and some with 2.7.1.1. You will need to try all three until you find the one that works for you. Do not touch the power supply file, that's whats causing my first error. Somehow it got deleted, and restoring to complete stock does not replace it, thats why i need someone to upload theirs.
Hi,
I have a problem with my Moto G 2014 XT1068 which is described in topic: forums.androidcentral.com/moto-g-2013/391289-something-seriously-wrong-my-moto-g.html#post3668518
I can't do these steps, because dialog window shows up all the time, and i cant go further.
I have disabled usb debugging option and can't disable ART runtime.
First of all "Factory" in bootloader doesn't work. Wipe and factory reset via stock recovery has no effect; old android remains, the same using TWRP:
"E:Unable to open 'cache/recovery/.version' but ends successfully
and PHilz.
I've tried to flash many roms using many recoveries( TWRP - few versions up to 2.8.5 because 2.8.6 has display flickering bug, few Philz, and few others that also flicker) and fastboot and msfastboot(both on linux).
When i flash via fastboot or mfastboot using xml.zip roms everything looks ok, there are no errors, but flashing has no effect - I have still old ROM with old issue.
When i flash via different recoveries always some errors appears. For example flashing latest CM 12.1 nightly
via TWRP i get:
"E:Error executing updater binary in zip '/sideload/package.zip'
or via stock recovery (ADB sideload) get:
"(...)
Verifying update package...
E:Failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Partition erase in fastboot despite "OKAY" message in CLI has no effect. As i understand this should remove all files from partitions.
This problem showed up when i discharged battery to 0% and turned on the phone.
Have you any ideas what should i try more?
Thanks in advance.
Hi,
I've tried other things to back my phone to life, like turn on usb debugging or even delete files, all via adb shell in recovery, but it is impossible. In TWRP or PhilzTouch I remount partitions with rw privileges, it look like I'm able modifying files via vi and cat to check results but when remount one more time old files still exist, so it is like there is some buffer? (maybe some security lock?), when try rm -rf files it shows up that i can't delete because it read only... (but mount says rw). After remount partitions with rw privileges wipe /data in twrp ended successfully but has no effect.
Do you know why everything looks ok, but it is not? Of course android boots up but is useless and after few minutes phone turns off.
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Sounds like you both have a failed eMMC. If that is the case, and I'm certain it is, there is nothing that can be done to "save" or "restore" your devices.
Sent from my XT1031
hi, maybe any1 has already found a solution?
dihcar said:
i have the exact same problem with xt1064 that shuts off after bootanimation, all flashing and wiping look ok, but stuck in same result.
i read in some threads it's due to corrupt partitions and there's no solution yet to this problem, i hope this is not true, please share if you make any progress, i will do the same. best of luck.
Click to expand...
Click to collapse
I have exactly the same issue with my XT1063. Reading a lot for a solution, traying all without success.
Hopping someone can help us!
I have an H811 with an unlocked boot loader and rooted with BETA-SuperSU-v2.67-20160121175247.zip. I do not have TWRP installed, but instead opt for fastboot boot trwp-xxx.img when I want to make a nandroid backup. I did not install TWRP specifically so I could use the OTAs when they come in from Tmo. The other day, one came in but the install fails. This is the error message. I'm not sure why GoogleTTS.odex and Hangouts.odex are missing.. I may have froze them in Titanium Backup or accidentally removed them during a bloat cleansing., but it doesn't seem to be barfing on those two Google packages.. just the boot partition. Why?
I've not installed any mod kernels. Only thing I can think of is the unlocked bootloader. I have a stock nandroid that I can restore to the phone, and then possibly apply the patch, but if this is due to the unlocked bootloader that won't matter.
Second question: I have a saved copy of the update.zip from Tmo. I've read that trying to install this from TWRP is a bad idea. Is there another way to kick off the install instead of waiting for the download from Tmo again every night?
Thanks
HTML:
Verifying current system...
failed to stat "system/app/GoogleTTS/oat/arm/GoogleTTS.odex": No such file or directory
failed to stat "system/app/Hangouts/oat/arm64/Hangouts.odex": No such file or directory
contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391
file "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
"EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
[LGE][Recovery] Installation aborted. no valid image in CACHE.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
[email protected]:/cache/recovery #
Nevermind. After some more searching, this is a really common problem with rooting and OTA. Sorry for the static. I'm new to all this.
Hi everyone.
I need some help!
Some years ago I rooted my Kindle Fire HD 7" (2nd gen) and installed CM. Recently I was trying to update my CM and did something wrong (can't remember what).
Now y have my Kindle Fire getting into TWRP instead of booting, and can't install anything. I've tryed downloading and installinf diffrent ROMS, but y always get the same message "FAILED"
in the log i can read this:
E:Unknown File System: 'datamedia´
Updating partition details...
Running boot script...
Finished running boot script.
Installing ´/sdcard/cm-12.1-20160606-NIGHTLY-tat.zip´...
Checking for MD5 file...
Skipping MD5 check.: no MD5 file found.
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/omap/...
detected filesystem ext4 for /dev/block/platform/omap...
ApplyParsedPerms: lsetfilecon of /system/etc/ppp/...
ApplyParsedPerms: removexattr of /system/etc/ppp/...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-12.1-20160606-NIGHTLY-tate.zip
(Status 7)
Error Flashing zip ´/sdcard/cm-12.1-20160606-NIGHLTY-tate.zip´
Updating partition details ...
Failed
Does anybody knows what I'm doing wrong and how i can fix this?
Please!!! Help me!!!
THANK YOU!!!!
negrooblackk said:
Hi everyone.
I need some help!
Some years ago I rooted my Kindle Fire HD 7" (2nd gen) and installed CM. Recently I was trying to update my CM and did something wrong (can't remember what).
Now y have my Kindle Fire getting into TWRP instead of booting, and can't install anything. I've tryed downloading and installinf diffrent ROMS, but y always get the same message "FAILED"
in the log i can read this:
E:Unknown File System: 'datamedia´
Updating partition details...
Running boot script...
Finished running boot script.
Installing ´/sdcard/cm-12.1-20160606-NIGHTLY-tat.zip´...
Checking for MD5 file...
Skipping MD5 check.: no MD5 file found.
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/omap/...
detected filesystem ext4 for /dev/block/platform/omap...
ApplyParsedPerms: lsetfilecon of /system/etc/ppp/...
ApplyParsedPerms: removexattr of /system/etc/ppp/...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-12.1-20160606-NIGHTLY-tate.zip
(Status 7)
Error Flashing zip ´/sdcard/cm-12.1-20160606-NIGHLTY-tate.zip´
Updating partition details ...
Failed
Does anybody knows what I'm doing wrong and how i can fix this?
Please!!! Help me!!!
THANK YOU!!!!
Click to expand...
Click to collapse
Do you have the latest version of twrp installed? I see you're flashing cm12, what version were you coming from?
squ89r97 said:
Do you have the latest version of twrp installed? I see you're flashing cm12, what version were you coming from?
Click to expand...
Click to collapse
thanks for answering!
i´m flashing CM12 right now, buy already tried with other ROMS having the same problem. I really don´t care that much on what ROM to install, I just want my Kindle to come back to life again
regardin TWRP, I cant remember what version I´m using, but i don´t think its the latest one. Do you recommend me to try this? I´ll check and let you know.
any other suggestions?
thanks!!
negrooblackk said:
thanks for answering!
i´m flashing CM12 right now, buy already tried with other ROMS having the same problem. I really don´t care that much on what ROM to install, I just want my Kindle to come back to life again
regardin TWRP, I cant remember what version I´m using, but i don´t think its the latest one. Do you recommend me to try this? I´ll check and let you know.
any other suggestions?
thanks!!
Click to expand...
Click to collapse
Well, twrp tells you what version it is when it starts up, so that should be easy to report. And I know you're flashing cm12, I asked what you were running before that. It's possible that you need to update twrp in order to flash newer base versions of Roms. Especially after you say it was a few years ago when you rooted it.