Hello everyone. I tried to wipe my kindle and replace the rom last night but its not letting me install anything. I have been running a version of Smoothrom for months now without any issues. I am giving the kindle to my gf so I wiped it and tried to upgrade to a kitkat rom first. I did a complete wipe of everything then loaded the roms on via usb. Now, when I try to install a new rom I get an error which Ill post below. I am using TWRP 2.5.0.0. I tried loading several different 4.4 roms and they all get the same error:
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/AmazonHfk2.8-20131220-Stable-otter.zip
Error flashing zip '/sdcard/AmazonHfk2.8-20131220-Stable-otter.zip
Updating partition details.......
It stays like that. If I try to reset it I get a message saying "Root permissions appear to be lost, fix root permissions now?"
Any ideas would be really appreciated.
SOLVED: I tried a few different Roms and it seems like its just the 4.4 roms that are failing. Im assuming its just my version of TWRP so ill try to update it. Feel free to delete this thread. Sorry for clogging up the forum.
Related
I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.
Did you re download and check md5?
PonsAsinorem said:
Did you re download and check md5?
Click to expand...
Click to collapse
I re downloaded twice. And I thought it always checked md5, it's at least never had a problem when it did..
Hypherism said:
I've been running albinoman's AOSP JB Rom for a while now.
However, when upgrading from RC2 to RC3, I receive an error pretty early in the installation.
Installing AOSP Android 4.1.1
Creating symlinks
Setting permissions
set_perm: some changes failed
E:Error in /sdcard/clockworkmod/download/jellbeanrc3/Jellybean-Inc-RC3.zip
(Status 7)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
I've been installing roms for a long time, and haven't run into this problem until now.
Tried the installation several times, and always run into the same problem. The error makes it impossible to boot, so I have restore my RC2 backup.
I really want to run this, and it's been the cause of quite a bit of frustration this past week. Thanks for your time.
Click to expand...
Click to collapse
Install from twrp cwm is a broken recovery
Sent from my ADR6300 using Xparent Red Tapatalk 2
Status 7 usually means there is a problem with the updater script in the rom file. What recovery are you using? Try TWRP if thats not what your using. Either the rom developer made an error in the rom zip, or the file is getting corrupted during download.
Also the md5 is not automaticly checked, you must check it your self.
Thanks very much for your assistance fellas. Unfortunately, I have an entirely new problem on mis manos.
So, after the most recent failure of the rom to install, I restored my backup of my RC2 rom.
It wouldn't get past the nexus boot animation. (I waited for 15+ minutes, I don't know why) So I
went back to recovery, and attempted to install RC3 again.
No problems installing. When I booted up however, after it had notified me that it was "Finishing installation" and that Android was "upgrading"
I was met with a plethora of errors. android.process.acore has stopped etc.
So, I ended up doing a factory reset/wiped user data.
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:
cmlusco said:
Also the md5 is not automaticly checked, you must check it your self.
Click to expand...
Click to collapse
Depends on how you get it. If downloaded from the Goo Manager app, the app auto checks md5.
Hypherism said:
The reinstallation of RC2 as well as the upgrade to RC3 went off without a hitch. So thanks guys, but I did something I didn't want to do, and it worked out in the end.:good:
Click to expand...
Click to collapse
Good to hear it worked out for you.
I tried to flash to Intergalactic Rom and it failed, so I tried to flash it again, but when I was wiping the files I accidentally wiped my SD card with my nandroid. So does anyone have one they can upload or another idea? Thanks.
CipherC233 said:
I tried to flash to Intergalactic Rom and it failed, so I tried to flash it again, but when I was wiping the files I accidentally wiped my SD card with my nandroid. So does anyone have one they can upload or another idea? Thanks.
Click to expand...
Click to collapse
what was the error message?
if we find your problem is not fixable via flashing a different rom, etc, you could consider downloading and flashing stock firmware in odin and starting over
Reason for most failed installs is outdated recovery or bad download. Just download a ROM again and put it on your ext ad card. Flash an updated recovery in Odinand then flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda premium
Alright, sorry I was in a rush to get back to work.
"assert failed: getprop( … ) == "d2att" E: Error in /emmc/Intergalactic_v2.8.zip "
That is the error that I am getting when I try to flash it. I searched the page and found that the error is because my CWM is out-of-date.
It flashed the second time I tried which is what bricked the phone, so now I can't upgrade my CWM via the two ways that I have found online which both require a working ROM.
If I can flash another ROM with CWM 5.5 that would be great. If anyone knows of a ROM that is compatible please let me know.
CipherC233 said:
Alright, sorry I was in a rush to get back to work.
"assert failed: getprop( … ) == "d2att" E: Error in /emmc/Intergalactic_v2.8.zip "
That is the error that I am getting when I try to flash it. I searched the page and found that the error is because my CWM is out-of-date.
It flashed the second time I tried which is what bricked the phone, so now I can't upgrade my CWM via the two ways that I have found online which both require a working ROM.
If I can flash another ROM with CWM 5.5 that would be great. If anyone knows of a ROM that is compatible please let me know.
Click to expand...
Click to collapse
here's a link to a cwm recovery flashable update. this is cwm 6.0.2.3. should work. flash it in cwm then "reboot recovery"
http://d-h.st/8qP
and if you want to make sure it's done right, here's a compilation of the best way to root/flash/backup your device. stick with these methods and you'll have far fewer problems
http://forum.xda-developers.com/showthread.php?t=2179330
Thanks, but the update was a No-Go. It's giving me the getprop error again. I'll just suck it up and start over.
CipherC233 said:
Thanks, but the update was a No-Go. It's giving me the getprop error again. I'll just suck it up and start over.
Click to expand...
Click to collapse
odin back to stock. here is a link to stock firmware with root already injected. download the correct carrier version and flash in odin. http://forum.xda-developers.com/showthread.php?t=1739426
install rom manager (http://download.clockworkmod.com/recoveries/RomManager.apk). flash recovery via rom manager. i think latest release is 6.0.3.0. make sure rom is still on your phone.
boot into recovery and make a backup before you do anything else.
then wipe data
wipe cache and dalvik
install rom
after successful boot, wait 10 minutes and reboot.
---------- Post added at 11:41 PM ---------- Previous post was at 11:29 PM ----------
While you're back at the beginning, I would take the time to backup your imei/efs stuff. Better safe than sorry. This is a step that many skip.
This is a beginning to end guide
http://forum.xda-developers.com/showthread.php?t=2179330
Cheers
I am not exactly sure where things started to go wrong. I just recently installed the latest ROM of Task650's Jellybean 4.2.2
I have been trying to update to the latest ROM and I recieve:
[assert failed: getprop("ro.product.device") == "E: Error in /external_sd/ROMs and Gapps /aokp_JB_4.2.2_d2att-ota-eng.task650-4.26.2013.zip
(Status 7)]
I have looked up the issue and updated the Kernel and updated to the latest CWM and still get the same error.
Another thing I have noticed is that I cannot flash any other ROMs like CyanogenMod or anything
I also noticed in my devices folders, that I basically have mulitple of the same folders in multiple directories... I am not sure if this is from flashing too many times... I have never had this many problems with my device before. I like to have everything updated, which I have been able to do before, but now I can't do anything.
Can I get some advice on what to do?
if you have an i747 (d2att), was that a d2att cwm update you applied? it will say in the updater-script (in the recovery zip) what model it's for.
each time you flash a 4.2.2 ROM you're likely adding the multiple folders. a known issue. follow the link in my signature for some more details on this down in post #2 of that thread. essentially, back everything up (either to a micro sd card or your PC) and perform a full wipe before flash (including /system and /data + /media) to avoid this problem. we'll work on that once you've got this first issue fixed.
Fixed my issue!
I'm guessing I had flashed the wrong CWM:good: for my phone.
I'm trying to install Liquid Smooth's latest 3.1 build on my phone , and i keep getting an error every time i try
I have had problems with other 4.4 ROMs(i can install 4.3 ROMs like LS v2.37), and it keeps happening
I've been doing this for three years, so I'm not that much of a newbie, I'm just not used to errors and complicated things
The Log in TWRP says :
Erasing System...
Mounting System
Installing System
Creating Symlinks
set_metadeta_recursive:some changes failed
E: Error in /external_sdcard/LS-KK-v3.1-OFFICIAL-
(Status 7)
Error flashing zip '/external_sdcard/LS-KK-v3.1-OFFICIAL-
Updating Partition details
FAILED
Does anyone know what's wrong ?
Im going to be gone until about 5pm EST, so thanks in advance
Update TWRP. Also after you wipe, but before flashing the rom, reboot back into recovery. Say No to fixing SU when you do. Then try and flash the rom.
MrJenks said:
I'm trying to install Liquid Smooth's latest 3.1 build on my phone , and i keep getting an error every time i try
I have had problems with other 4.4 ROMs(i can install 4.3 ROMs like LS v2.37), and it keeps happening
I've been doing this for three years, so I'm not that much of a newbie, I'm just not used to errors and complicated things
The Log in TWRP says :
Erasing System...
Mounting System
Installing System
Creating Symlinks
set_metadeta_recursive:some changes failed
E: Error in /external_sdcard/LS-KK-v3.1-OFFICIAL-
(Status 7)
Error flashing zip '/external_sdcard/LS-KK-v3.1-OFFICIAL-
Updating Partition details
FAILED
Does anyone know what's wrong ?
Im going to be gone until about 5pm EST, so thanks in advance
Click to expand...
Click to collapse
Maybe try philz if you can't get it with twrp ive have to do that a few times
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Double0EK said:
Update TWRP. Also after you wipe, but before flashing the rom, reboot back into recovery. Say No to fixing SU when you do. Then try and flash the rom.
Click to expand...
Click to collapse
Thanks dude, i never knew you had to update twrp, its probably because everytime i have a phone it doesn't last over 6 months, but the note 2 has been through alot, and its durable compared to my other phones
Permissions have to be set in a different way in 4.4.x ROM's. Commands like "set_metadeta_recursive" need updated binary which is included in updated TWRP and CWM recoveries.
Hello,
This is my first time posting here as I have encountered a very frustrating issue. I am sorry in advance if this is not the area to post such a topic. For several months now I have been trying to install a custom ROM (specifically, CM11) for my Samsung Galaxy SGHT999L on T-Mobile, and every time I try, I cannot manage to flash CM. I tried on the most recent version of CWM and CWM touch, as well at TWRP and every time I have gotten an error and I was forced to reflash the stock ROM with Odin. At first I encountered an error 7, but I found threads here and corrected the issue via the updater-script method. I tried again and I got no error message, just installation aborted. Now I tried looking in the logs, but I have no idea what I am looking for.
Another unrelated issue that I am experiencing (maybe it is related?) is that whenever I try to restore my phone, it completes, but I get stock on the T-Mobile boot screen.
Please any assistance would be greatly appreciated as I really want to install CM11 for Android 4.4 and begin development on my own ROM maybe sometime in the future. Thank you so much!!!
After editing tge updater script, did you delete the 3 signature files in the meta-inf folder?
If you try again and it fails, copy log to sd and attach it here.
How are you restoring?
Sent from my SAMSUNG-SGH-I747 using Tapatalk