[Q] (Status 7) Error on all 4.4.x ROMs for p3100 - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hi there,
I know there are a lot of topics about this issue, but I was not able to find anything to fix this.
I have:
gt-p3100 with 4.1.1 stock rom
3.0.31-321289 kernel
SuperSU v1.94
CWM 6.0.2.7 (latest version I was able to get from the CWM app)
want to install 4.4.2 slim or omni rom - but getting Status 7 errors
removing the section in install script doesn't work for me - installation aborts instead of status 7 error
anything else I can try?
TWRP better that CWM?

c-tec said:
Hi there,
I know there are a lot of topics about this issue, but I was not able to find anything to fix this.
I have:
gt-p3100 with 4.1.1 stock rom
3.0.31-321289 kernel
SuperSU v1.94
CWM 6.0.2.7 (latest version I was able to get from the CWM app)
want to install 4.4.2 slim or omni rom - but getting Status 7 errors
removing the section in install script doesn't work for me - installation aborts instead of status 7 error
anything else I can try?
TWRP better that CWM?
Click to expand...
Click to collapse
Try updating your recovery to the latest from Android-Andi http://forum.xda-developers.com/showthread.php?t=2548257 or http://forum.xda-developers.com/showpost.php?p=47964256 Should be good to go.

Thx
CSP III said:
Try updating your recovery to the latest from Android-Andi http://forum.xda-developers.com/showthread.php?t=2548257 or http://forum.xda-developers.com/showpost.php?p=47964256 Should be good to go.
Click to expand...
Click to collapse
Thanks updated the CWM fixed it!
Why isn't this version available from the official App? This sucks!
Thanks a lot!

Related

[Q] Can't install ROMs

Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved

[Q] cm11-nightly-20140906-gio.zip status 7

Hi,
I'm trying to install the weekly update 06092014 from androidarmv6 on my galaxy gio gt-5660 cm11-nightly-20140830-gio.zip with cwm-6.0.5.3 and it fail with status 7.
Anyone know if there is an updated cwm version?, i try to find it on jenkis site with no luck.
Thanks a lot
Solved i have to download the full rom zip and flash it from recovery and it works if i use the incremental one it dead with error 7.
Hope help.

[Q] Can't Install Slimkat : Status Error 7

Hi Buddy!
Greetings from a new guy here
Just basic question, few days back I'm trying to Install Slimkat ROM, I've done few steps below :
- Wipe data factory reset
- Wipe chache
- Wipe dalvik
- Format system
- Flash zip from Internal SD Card
But I'm getting status error 7 on installation proccess
I'm trying to Install another ROM (CM 10.3 Official & CM 12 Unofficial) its working just fine
Why I couldn't install Slimkat on my device?
Because you are using an out dated recovery, you need at least cwm 6.0.4.4 because KitKat requires selinux support and older recovery doesn't support it, get it from general section of tab 2 and flash it using existing recovery
Hope it works
shsagnik said:
Because you are using an out dated recovery, you need at least cwm 6.0.4.4 because KitKat requires selinux support and older recovery doesn't support it, get it from general section of tab 2 and flash it using existing recovery
Hope it works
Click to expand...
Click to collapse
Thanks! Its working now
But just wondering, I previously using CWM 6.0.2.8 but I can even install CWM 12 which lolipop based
Why it doesnt work on slimkat which based on kitkat? Kitkat is even lower than lolipop
aliarroughi said:
Thanks! Its working now
But just wondering, I previously using CWM 6.0.2.8 but I can even install CWM 12 which lolipop based
Why it doesnt work on slimkat which based on kitkat? Kitkat is even lower than lolipop
Click to expand...
Click to collapse
If you read what I typed carefully, KitKat uses selinux, lollipop doesn't,
So you can use any recovery made for your device to flash a lollipop based ROM,
But anyways people are getting trim bug that causes infinite Boot loop without any reason, that's why our supper hero Andi protects us with patches that prevent those things.

(error 7 ) in cwm

I have a p3113 ,as evryone suggested i tried a lot of p3110 lolipop roms.
Recently i tried to flash cm11 unoffcial version of android andi.
It says it cant flash the rom and says error in the zip file and( error 7 ) in recovery.
All this happens only for a kitkat rom but i can flash any other version of android like lolipop or jb.
Pls help me ..currently im on cm9 official build for p3113. I have a cwm recovery,version 6
update your revovery, you can download zip here: https://www.androidfilehost.com/?w=files&flid=25706 Flash it and reboot recovery, then it should work fine
iks8 said:
update your revovery, you can download zip here: https://www.androidfilehost.com/?w=files&flid=25706 Flash it and reboot recovery, then it should work fine
Click to expand...
Click to collapse
Thanks got it..
switch to TWRP
I would alse recomend TWRP. In my opinion runs better than cwm

Samsung Tab 2.7.0 P3100 - issues while installing CM 13

hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
sskj said:
hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
Click to expand...
Click to collapse
Any help ....????
sskj said:
Any help ....????
Click to expand...
Click to collapse
you should upgrade your recovery too. try twrp 3.0.2-3 from here https://www.androidfilehost.com/?fid=24591000424954613
and install it with your current recovery. make a reboot back into recovery.
wipe dalvik, cache, system and format data http://andi34.github.io/faq/faq_twrp.html
make a new reboot into recovery and install your rom and gapps.
OK
johneflik said:
Redowload the ROM again it might be corrupt and use the exact gapps
Best ROM for your tab is omni 4.4.4 or cm13 or omni 6.0.1
Just the latest TWRP go wipe then advanced wipe then wipe everything except the external SD. Install install your chosen ROM flash the equivalent gapps, flash super user update reboot you are done. all what you need is here in Andoid-Andi files http://andi34.github.io/
Click to expand...
Click to collapse
sskj said:
hi all,
I have Samsung Tab 2.7.0 P3100 and an year back i installed CM10. I think i have done some mistake while updating from CM 10 to CM latest version. I have wiped the date and cache.I have the ZIP files (CM 10 and GAPPS) in external memory. when i am trying to install the CM11 it is showing "INSTALLATION ABORTED with error number 7". But when I am trying to install GAPPS it completed successfully.
can someone please help me here to get my tab back in working condition ..!!!
Wondering, is it possible to install the Samsung normal OS back again ?
Any help on this issue is much appreciable.
Thanks
Shibin Shah K J
Click to expand...
Click to collapse
don't flash a separate supersu.zip if you would install cm13. supersu causes bootloops on cm13.
if you need root access on cm13, go to dev.-options and enable root access. set it to "apps and adb"
thats all.
cm13 is pre-rooted, so no need for flashing supersu.zip
OK
johneflik said:
[MENTION=457974].. yes you are right about super user. I think pmni6.0.1 needs a super user to be flashed. Any way I have seen SU on cm13 and no problem at all... Untill now. Do I need to remove it or keep the root access from dev tools disabled.
Click to expand...
Click to collapse
omni6 need supersu right.
if supersu are working on cm13 by Markox89 for you everything is fine. i would keep the root access from dev.-options disabled

Categories

Resources