I seem to be stuck in a boot loop after installing custom 4.4 kitkat, upon trying to shut don and reboot, the device loads up recovery menu..... when I try to install cm-11-20141030-NIGHTLY-p3110 I keep getting a status 7 error??? I have deleted the assert lines from the ini file on the update zip but im still getting the error? any help would be appreciated....
Some nightly's don't install unless your running cm11 already. They are updates.
Pp.
CloudsurferTom said:
I seem to be stuck in a boot loop after installing custom 4.4 kitkat, upon trying to shut don and reboot, the device loads up recovery menu..... when I try to install cm-11-20141030-NIGHTLY-p3110 I keep getting a status 7 error??? I have deleted the assert lines from the ini file on the update zip but im still getting the error? any help would be appreciated....
Click to expand...
Click to collapse
I just had the same problem.
Try getting a newer recovery. I just used CWM 6.0.4.7 and it finally worked for me.
Hope this helps
Status 7 error fix is just to flash a newer recovery, Go ahead to Android-Andi Recoveries thread and download recovery
As @Hassan 4 said, go to @Android-Andi's recovery thread. I'll add that TWRP (also in that thread) is really user friendly and easy to use touch interface.
Related
Hello all,
Last night I was trying to install the latest Gummy release on my Verizon Galaxy S3. This was the first time I have tried to flash a rom on this phone. It failed, and I rebooted my phone, and now it will only boot into the clockwork recovery.
I thought it may have been damaged as i was transferring the file to the device. I had an SD card in my droid X, So I put it in my Galaxy and formatted it with clockwork. Then I transferred the gummy release (that I also re-downloaded) from my computer to the SD card via a memory card reader. I put it in my Galaxy and tried to install the release, and it gave me a different error
Code:
E: Can't Open /external_sd/Gummy-2.1-01-09-14-NIGHTLY-d2vzw.zip
(bad)
Installation aborted.
Edit: Tried a few other roms and they had the same issue, but Cyanogen Mod 10.2 worked. Anybody have any guesses why?
Edit2: Further developments, Trying to do the latest nightly fir the CM yields the same issue that Gummy's release gave me initially. It reports as follows:
Code:
E: Error in /external_sd/cm-11-20140110NIGHTLY-d2vzw.zip
(Status 7)
Installation aborted
Is there possibly a firmware issue at play?
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
twistedillutions said:
Did u unlocked ur recovery. And if ur trying to flash a KITKAT rom u need the latest clockwork recovery
Click to expand...
Click to collapse
Sorry, forgot to mention, I did unlock with EZunlock. Would the clockwork on the play store be the latest one, or is there another place with more up to date versions?
Cappurnikus said:
I'm having this exact issue except I currently have TWRP 2.6.3. I wiped data, cache and internal and it actually booted the below ROM (the first boot) but once I got everything setup and rebooted the device it will not boot beyond recovery. It hangs on the Samsung boot logo. I've tried to restore to a 4.1.2 ROM as well as install 4.3 and 4.1.2 again multiple times but they will not boot. Any direction would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2601536
Click to expand...
Click to collapse
Do you get the same error on install that I'm getting, ro are the installs finishing, but not booting?
Try goo manager or ez-recovery to install the latest recovery
right now i can think of
factory reset format data. Make sure u backup ur internal
Wen changing from rom to rom is a good thing to do a clean install
get the right gapps.
The 1st boot always takes time at least on me.
Sorry i cant think of more helpful things.. Been drinking
Looks like my recovery just needed an update. Thanks everyone.
Sent from my Nexus 7 using Tapatalk
Confirmed also an old recovery for me as well. Thank you very much!
I've searched and found a few different solutions for each of my problems. However, nothing has resolved the issue.
I tried to flash CM 11.0 to my Galaxy Tab 2 (GT-P3110) and now I can't get anywhere but my CWM Recovery screen.
When I try to install the ROM, I get a "Status 7" error. I've attempted the steps found here but they have not worked.
So, I decided to just recovery what I had before - easy enough. But then when I attempt to recover, I get an error of "MD5 Mismatch".
I've looked up ways to resolve this issue, but I can't complete the steps for 2 reasons. Firstly, I can't get to my File Explorer because my tablet won't completely boot. Secondly, my laptop has stopped recognizing my tablet for some reason. So, I'm unable to edit the file from there.
Lastly, when I just try to reboot system, I get an error explaining that I "may" have lost root access. If I select to "fix" this, it does nothing - just reboots back to recovery. If I choose no, same thing.
I've cleared dalvik, cleared cache partition, cleared data/factory reset, and formatted system - nothing makes a difference.
Any help is greatly appreciated. Thanks everyone.
IS there kitkat update for tab 2. Please inform about That}.
chandru andriod said:
IS there kitkat update for tab 2. Please inform about That}.
Click to expand...
Click to collapse
I believe so, yes.
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Android-Andi said:
@ohhello update your recovery. your recovery needs to be up-to-date to flash KitKat Roms. Link in my signature, all my latest recoverys can handle KitKat-Roms.
Click to expand...
Click to collapse
Okay - easy enough.
If I'm unable to get to ROM Manager, is there a way to update my Recovery within Recovery Mode?
I've zipped the .img file for the update.
Should I just install the zip from Recovery Mode?
THANKS!
download a flashable zip for your device from my thread and flash it in recovery. after that reboot the recovery to see the new recovery.
So I've been play with Android for a few years now and I love it. Got the Samsung Galaxy Note 10.1 in the fall of 2012 and had a custom rom installed not long after. Periodically I check XDA to see if there is a new custom ROM I want to try. Finally there is, OMNIRom. It says I need a recovery image that can handle the new SELinux. After poking around for an easy way to update I findout that the goo.im has a new recovery that it will install. And that's where things go south. I installed the new TWRP v2.6.3.0 via the goo.im and then reboot into the recovery. I go to flash the new ROM and it fails. I try downloading the ROM again and flashing it. It fails again. Okay, shouldn't be a problem... I'll just flash my prior rom. It too fails. Uh-oh.... If I try to boot normally, it just loads directly to the faulty TWRP. If I try to boot to the bootloader so I can use Heimdall to flash over a new recovery, it boots to TWRP....
I found a new recovery in a ZIP format finally and tried to use that, but it fails too.
Any advice? Suggestions? Please help.
I have a rooted (Superuser 3.1.3) TF101 with TWRP 2.7.0.1. I HAD Katkiss 4.3 installed. One day the tablet locked up and then starting bootlooping. I went into recovery, wiped everything, did factory reset, format /system.
Then I tried to reflash Katkiss 4.3_020, it failed with "set_perm: some changes failed". I then tried katkiss 4.4.2_023c - it failed with a similar error message. Tried flashing stock (US_epad-user-9.2.1.27) - same thing. The first part of the error message for all three ROMs is the same set_perm failure. The next couple of lines gives different error messages depending on the ROM. Generally something like: "E: error executing updater binary in zip".
Now I have a tablet with no ROM on it (when I tried to boot it hangs at the ASUS screen). I can get into the TWRP recovery menu just fine - I can flash other things like superuser or gapps without error. But any ROM I try to flash gives the set_perm error.
Any thoughts?
Chris
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Thanks but...
Easyflasher doesn't seem to work for me anymore (odd because it is what I first used to root/update my TF101). It runs and declares success - but nothing gets pushed to my device. Tried both SBK1 and SBK2. Using universal naked 0.72 and 0.73 on win7 64 bit.
I tried to find an older version of TWRP like you suggested - but I couldn't. Seems they want you to use "goo manager" from the play store... which doesn't work for me since I can't boot... And the goo website doesn't list an older TWRP for my device.
In any case, the latest TWRP seems to work in every other respect. I read somewhere that superuser can set an "immutable" bit that can survive a wipe? If true - could that be my permissions problem?
Chris
stuck on load screen
*Detection* said:
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Click to expand...
Click to collapse
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
ldwhyte said:
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Click to expand...
Click to collapse
ChrisG12 said:
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
Click to expand...
Click to collapse
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
ldwhyte said:
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Click to expand...
Click to collapse
Ok - back to my problem - I installed a new recovery and get the same error. The two recoveries I have tried are TWRP (2.3 and 2.7.0.1) and cwm-6.0.2.1-notouch-hybrid. Both seem to work fine (and I had no trouble previously with my device running TWRP and Katkiss 4.3).
After a crash I needed to reinstall a ROM. I've copied four ROMs to my sdcard (Katkiss 4.3, Katkiss 4.4.2, Omni 4.4.2, and stock asus). I've tried all 4 ROMs with both recoveries. I get the same error when I try to install the zips. Usually it is "set_perm: some changes failed". Though stock asus zip fails with a different message "Assert failed: package_extract_file(“blob”, “/tmp/blob”)".
Any ideas on what is keeping a recovery from installing the zip? Note they can install other zips fine (i.e. other recoveries, superuser, gapps, etc.). But not the ROM.
ChrisG12 said:
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
Click to expand...
Click to collapse
No it's not, but I can't get anything onto the SD card, only the ext card and I CWM will not mount it to flash from. if I'm missing something and I sure I am, Im greatful for any help, and thanks again..
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse