Q!
Apologies if this has already been resolved, I did a search but did not find my exact problem.
I screwed up, I installed the ROM from http://forum.xda-developers.com/showthread.php?t=1092332 but I failed to install the GAPPS zip the first time.
So I tried to install it again with gapps but I keep getting a "Verification failed Installation aborted" message.
So then I downloaded the stock HTC ROM from http://forum.xda-developers.com/showthread.php?t=804692 but I get the same error message.
Can somebody tell me how to either get this ROM to work with gapps or go back to stock? I need to learn to read the entire post before assuming every ROM installs the same.
Thanks for reading, and thanks for your time.
Download the correct gapps package and make sure the download is corrupted.
EDIT: isn't, lol fail
Thanks. I was not able to find a gapps package that worked. I dl'ed a signed version successfully but I couldn't get past the setup screen. It just was not working.
So I went with CM7 instead and I actually like it a lot better. I've got my Google apps and everything's running smooth. Yay for ROMs.
CM7 is very sexy... runs on my Wildfire S but the WIFI is broken on my specific model right now *sadface*
I think your problems lead you in a better direction at least!
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Anybody? I'm not sure how often the second page gets glanced at around here. Even an inkling of an idea might put things in motion.
I believe Status 7 usually indicates the wrong update file.
You might try...
androidforums.com/nexus-s/588179-jelly-bean-update-status-7-error.html
highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
ibtimes.co.uk/articles/499093/20130814/galaxytab2-p3100-p3110-p3113-android43-jellybean-cyanogenmod102. htm
Best of luck.
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
True, this is usually the case, but not this time. I tried all these, but the root of this issue is with the symbolic links and setting permissions. I am starting to really think it's all about getting data to unmount, but I haven't been able to get this to happen.
back to the stock rom
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
[/COLOR]
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
try to get back to the stock rom firmware, I have the same
problem few days ago, cant flash any rom
n I think the problem b'cause wrog flash when rooting or
flashing the image cwm/bootloader
that's all I know,
Well it's good to know that I'm not the only person who has had this problem. I managed to get back to stock. I'm not sure what I can do from here, though. I don't want to try anything because I don't want to break it.
I'm on 4.4 right now and I just reviewed the ota but when it finished downloading, it went stock recovery and just said "error". Obviously I was pissed so I then went the adb root but that wouldn't work either. Something about it not being able to find "update.zip" when it is clearly in the same folder. After that I decided to flash a custom recovery, not clockwork but the other one. Whenever I try to go that route it still says it failed. I have been looking at posts and none have helped so far.
I am rooted, I don't have busybox/xposed, I am using art. I read something about having to have all of the stock apps. I had a modded playstore on here but I didn't work so I re-download one and installed it, could that have anything to do with my problems? And if so, where can I find another playstore app?
also, this is what it says in the custom recovery: /system/framework/core-libert. Jar unexpected E:Error executing updater in zip I tried googling but to no avail.
That modded play store might have changed some system files that prevent the update. You can try flashing one of the stock 4.4.2 Roms available in the android development forums. I used the one by bigxie.
Sent from my Nexus 5 using Tapatalk
Thanks man. Should I use an odex or deoxdex? And what's the difference?
I have this problem too....i'm rooted and get the error logo when i try to update too.....
paulbadassbriant said:
I have this problem too....i'm rooted and get the error logo when i try to update too.....
Click to expand...
Click to collapse
Try what the guy who replied to me said, it worked for me
I am stuck. My phone won't accept any ROMs I try to install. It keeps giving me the "Status 7" Error and I can't figure out why!
the backup recovery failed.
I am using TWRP as my recovery, but it is an old version (V2.2.1.1). I have tried multiple releases for CM, but none of them work, not even the stable ones.
The phone has already been wiped so i cant get back into stock android to fix much.
I have tried going into the "updater-script" file and deleting the code for checking the device matches the rom, but no luck. i have also tried installing a rom that wasn't cyanogenmod but i ran into the same problems.
CAN ANYONE HELP ME?!?!?
I really dont want to have to throw away a good phone because i missed something.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2