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.
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.
PROBLEM SOLVED thanks to digixmax for the bootloader zip
http://forum.xda-developers.com/showpost.php?p=57096448&postcount=11
Cyanogenmod 11.
Tablet was acting weird. Wasn't turning on in general, just black. Then I tried to reset it using the n and power buttons for 30 seconds. It did boot up eventually.
Then it froze and rebooted, and ever since only boots to CWM.
I've tried factory reset and reflashing to no avail, only cwm will boot.
I read it might have something to do with bootdata.
Like I said, I got it to work initially after it would only boot to a black screen, then it froze, now this. I'm worried I might have corrupted the EMMC way way back with an older rom.
It's likely that your problem is one that is described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1 (the post was written for the Nook Tablet, but the BCB & BootCnt exist and work same way for the HD/HD+), in which case you can try to reset/restore BCB & BootCnt by flashing flashable_fix_bootdata-hummingbird.zip available at http://www.mediafire.com/download/04qhwylk36sofbl/flashable_fix_bootdata-hummingbird.zip.
If resetting BCB & BootCnt does not help then I'd suggest you try re-installing CM11.
thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.
Status 4 is a problem with the script in the zip. Double triple checked search and I've seen it before myself.
http://forum.xda-developers.com/showthread.php?t=2355223
Just a thought that since you can get into cwm, you could try using adb and browsing the emmc to see if its there and intact. twrp (just put it on an sdcard) has a file manager built-in as well. Is that worth doing? If need be you could save files that way too if its still intact.
Thistleknot said:
thx for the advice
albeit, I received an error when flashing the file using cwm.
Code:
EMMC CWM-based recovery v6.0.4.6
-- Installing: /external_sd/flashable_fix_bootdata-hummingbird.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /exteranl_sd_flashable_fix_bootdata-hummingbird.zip
(Status 4)
Installation Aborted.
Click to expand...
Click to collapse
I fixed the error in the file-name of "updater-script" in the flashable zip file.
You can re-download flashable_fix_bootdata-hummingbird.zip and give it another try.
redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata
Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed
Thistleknot said:
Okay, I figured out what I was supposed to fix to get past error 4
Name: META-INF/com/google/android/updater-script
SHA1-Digest: 29co0QiSKyDerOQ5Ggv0EV16f9g=
so i changed updater-script-bootdata to updater-script in the META-INF/com/google/android/ folder
then...
I got a different error
Code:
assert failed: getprop("ro.product.device") == "hummingbird" || getprop("ro.build.product") == "ovatino"
E:Error in /external_sd_/flashable_fix_bootdata-hummingbird-diff.zip
(Status 7)
Some flag check fails. This is a nook hd with cm11 emmc installed
Click to expand...
Click to collapse
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app
The script could be fixed to eliminate status 7 error on cm11 recovery, but without any changes its like leapinlar says.
leapinlar said:
You need to use a CWM older than v6045. The ones made for CM11 will not work.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Thistleknot said:
redownloaded the same zip as instructed: flashable_fix_bootdata-hummingbird.zip; in the 1st mediafire link http://www.mediafire.com/download/04...ummingbird.zip you have posted. (which has an uploaded date of 9-21-2014) Same issue.
btw. I have flashed cm11 over this, that will flash (but not fix my nook, still boots only to cwm). However, this update file will not take.
How should this file structure look like unzipped? I keep reading about an update script file. the only file I see named update is buried way deep in some android subfolder
update-binary
updater-script-bootdata
Click to expand...
Click to collapse
Use this link for the corrected zip file: http://www.mediafire.com/download/30leabd7tjeytn4/flashable_fix_bootdata-hummingbird.zip.
Updater-script in folder META-INF\com\google\android\ is indeed the script used to flash BCB and BootCnt into /bootdata.
---------- Post added at 05:10 PM ---------- Previous post was at 04:45 PM ----------
Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
You can get the old version of verygreen's CWM from his CM10.1 thread or from https://www.mediafire.com/#6a4rivb8kkdfu -- the EMMC version is (recovery.img) in his flashable cwm-recovery-ovation-3.zip, the SD version is (ramdisk.cwm) inside his emmc-cwm-early2.1.img or inside verygreen_emmc-cwm-early2.1-boot.zip at https://www.mediafire.com/#6a4rivb8kkdfu (verygreen_emmc-cwm-early2.1-boot.zip has the same complete set of CM10.x compatible SD-based boot/CWM files as emmc-cwm-early2.1.img but packed in a .zip file).
Thistleknot said:
I wonder how much further down this rabbit hole I got to go...
where can I get get an older version from?
Click to expand...
Click to collapse
From my HD/HD+ CWM thread linked on my signature.
Sent from my BN NookHD+ using XDA Premium HD app
looks like
Use this link for the corrected zip file: http://www.mediafire.com/download/30...ummingbird.zip.
Click to expand...
Click to collapse
is working. I got past cwm at least.
derp, sorry I missed your [leapinlair] signature links. I swear I looked and didnt' see them.
WORKING GUYS. You guys are really too good to the community.
Hi Guys
I already unlock my fone, but at firt time that I try to install a new room a error messagem shows like this:
Installing '/sdcar1/'......
checking for MD5 file.....
Skipping MD5 check: no MD5 file not found
Error flashing zip ''/sdcard1/'.....
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
Failed!
BinhoDigital said:
Hi Guys
I already unlock my fone, but at firt time that I try to install a new room a error messagem shows like this:
Installing '/sdcar1/'......
checking for MD5 file.....
Skipping MD5 check: no MD5 file not found
Error flashing zip ''/sdcard1/'.....
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
Failed!
Click to expand...
Click to collapse
What rom are u trying to flash?
Plz provide a link
Moto G User said:
What rom are u trying to flash?
Plz provide a link
Click to expand...
Click to collapse
I allready try with stock, cm12, paranoid android and pac man roms...
Im using TWRP 2.8.6.0, in other operations like Wipe data, cache and dalvik give the same message in red:
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
I try to wipe all units, copy the rooms from sdcard again and the message error continue
Solved
Hello friends!!!
The newest version of TWRP ( 2.8.7.0 ) solve my problem!
TKS!
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!