I had GOOHMA rom or something like that.
I returned to stock,locked the bootloader installed back the stock recovery and removed root.
And now i'm using 5.0.1 always while i try to install 5.0.2 update.
It tell's me "installation aborted status 7"
How can i fix it?
yot2703 said:
I had GOOHMA rom or something like that.
I returned to stock,locked the bootloader installed back the stock recovery and removed root.
And now i'm using 5.0.1 always while i try to install 5.0.2 update.
It tell's me "installation aborted status 7"
How can i fix it?
Click to expand...
Click to collapse
Just relock your bootloader mate
Related
Ive just about tried everything to get my phone to do a system update. When i do try to update it. It starts up Teamwin Recovery and says updated aborted. So i tried to flash the update manually by going to /downloads then trying to flash the OTA Sharp shooter and thats when i get the E:Error in /tmp/sideload/package.zip (status 7) at the end. So if anyone could help would be greatly appreciated.
blupo said:
Ive just about tried everything to get my phone to do a system update. When i do try to update it. It starts up Teamwin Recovery and says updated aborted. So i tried to flash the update manually by going to /downloads then trying to flash the OTA Sharp shooter and thats when i get the E:Error in /tmp/sideload/package.zip (status 7) at the end. So if anyone could help would be greatly appreciated.
Click to expand...
Click to collapse
What do you mean by System Update? What are you on now? Are you trying to flash a ROM? Going to /Downloads and flashing OTA sharp shooter; not sure what you mean by this at all......
blupo said:
Ive just about tried everything to get my phone to do a system update. When i do try to update it. It starts up Teamwin Recovery and says updated aborted. So i tried to flash the update manually by going to /downloads then trying to flash the OTA Sharp shooter and thats when i get the E:Error in /tmp/sideload/package.zip (status 7) at the end. So if anyone could help would be greatly appreciated.
Click to expand...
Click to collapse
A HTC OTA update cannot be flashed using a custom recovery, that is why you are getting the second error. Also a OTA will fail when HBoot attempts to run it when you have a custom recovery installed, that is probably the source of. First error.
Bottom line is that an OTA cannot be installed when you have a custom recovery, so just fine a custom, rooted Rom that is based on the OTA and flash that instead.
all you gotta do is go to recovery try to install it when you get the error pull the battery and go back into recovery from bootloader
Thanks i would make you kool-aid but im fresh out... and that didnt work either
---------- Post added at 12:45 AM ---------- Previous post was at 12:40 AM ----------
Yea i think your right... O well
Hey guys,
I had a similar problem when trying to flash my Nexus s with CyberGR mod.
Tried pretty much everything from trying to wipe system/dalvik/cache/factory reset and also disabled signature check.
Nothing really happened, i kept getting the error again.
Then i had flashed the recovery image (had a TWRP 2.0 running... changed it to CWM) and then the flash went on just fine.
So my guess is that this something to do with the recovery ROM. I would want to ensure that the recovery image used by the dev and mentioned in the install instructions be used.
Hope this helps.
I just reboot recovery and that fixes it when that happens. Have you tried that? No need for battery pull imo
Problem -
Using twrp v2.3.3.0 every ROM i try to flash i get a failed message (status 7).
Basically my phone is semi bricked.
I think my solution is to update to the latest twrp and try to reflash my ROM.
Question -
How do i install a new recovery if all i have on my phone is twrp (v2.3.3.0)?
dsswoosh said:
Problem -
Using twrp v2.3.3.0 every ROM i try to flash i get a failed message (status 7).
Basically my phone is semi bricked.
I think my solution is to update to the latest twrp and try to reflash my ROM.
Question -
How do i install a new recovery if all i have on my phone is twrp (v2.3.3.0)?
Click to expand...
Click to collapse
Odin flash Philz recovery
dsswoosh said:
Problem -
Using twrp v2.3.3.0 every ROM i try to flash i get a failed message (status 7).
Basically my phone is semi bricked.
I think my solution is to update to the latest twrp and try to reflash my ROM.
Question -
How do i install a new recovery if all i have on my phone is twrp (v2.3.3.0)?
Click to expand...
Click to collapse
The best way to recover a soft bricked phone is to download a firmware from Sammobile and install it on your phone using Odin. That will restore your phone with stock firmware and recovery. Then you can flash a custom recovery and root your phone again. Your phone still shows as "Added" in Odin, when in download mode and connected via USB cable to your computer or laptop?
dsswoosh said:
Problem -
Using twrp v2.3.3.0 every ROM i try to flash i get a failed message (status 7).
Basically my phone is semi bricked.
I think my solution is to update to the latest twrp and try to reflash my ROM.
Question -
How do i install a new recovery if all i have on my phone is twrp (v2.3.3.0)?
Click to expand...
Click to collapse
I had this error awhile ago. Error status 7 in Cwm Or Philz Cwm or TWRP
i fixed this issue following this Thread.
http://forum.xda-developers.com/showthread.php?t=2535367
Thanks for the replies.
I managed to use Odin to flash a new updated twrp recovery image. Using the latest twrp, i selected exactly the same ROM and it worked. So the problem lay with an outdated twrp.
I can thoroughly recommend against the package i used to install twrp, it screwed me for a while.
Get Odin and do it yourself
I just rooted my AT&T Galaxy S3
Specs:
Model number: SAMSUNG-SGH-I747
Android Verson: 4.3
I am trying to install the AOKP Rom for my device. I have it all downloaded and know how to install it but I keep getting Status error 7. What is happening? I read a little online and it says this error is for whenever you have the incorrect ROM version? Please help!
SheldDaaady said:
I just rooted my AT&T Galaxy S3
Specs:
Model number: SAMSUNG-SGH-I747
Android Verson: 4.3
I am trying to install the AOKP Rom for my device. I have it all downloaded and know how to install it but I keep getting Status error 7. What is happening? I read a little online and it says this error is for whenever you have the incorrect ROM version? Please help!
Click to expand...
Click to collapse
Did you unlock your bootloader?
Do you have CWM or TWRP?
Do you get the "Status error 7" after installing or before? And did you do a factory/wipe data reset?
Auxiliarus said:
Did you unlock your bootloader?
Do you have CWM or TWRP?
Do you get the "Status error 7" after installing or before? And did you do a factory/wipe data reset?
Click to expand...
Click to collapse
I am not sure about unlocking the bootloader. What exactly is that?
I am using CWM.
I get the error before. It says it is loading and then I get the error. I did factory/wipe data reset. I also cleared the cache. I also tried with a different ROM called HellFire and it gives the same status error.
EDIT: I got it. I downloaded the ROM Manager App by CWM and I got it to work first try!!!
SheldDaaady said:
I am not sure about unlocking the bootloader. What exactly is that?
I am using CWM.
I get the error before. It says it is loading and then I get the error. I did factory/wipe data reset. I also cleared the cache. I also tried with a different ROM called HellFire and it gives the same status error.
EDIT: I got it. I downloaded the ROM Manager App by CWM and I got it to work first try!!!
Click to expand...
Click to collapse
Bascially, bootloader is a software that before your operating system, it allows your operating system to load, unlocking bootloader allows you to install new OS's, and a locked bootloader doesn't.
Bascially, it's like rooting the software that opens your OS, and changing it load a custom OS.
You can unlock a bootloader with adb and fastboot, they are found in Android SDK.
Code:
adb reboot bootloader
fastboot oem unlock
And if you still continue to have problems with your OS, try reinstalling it the same way, except formatting /system before doing-so.
You may need to install a higher vergion of cwm .. try the touchz vergion ...
Here is a link on what error im getting (after installing some ROMs) only on this Baseband I605VRUEMJ9 I get this error I use to be able to install any kind of ROM but after I605VRUEMJ9 update I can't install some ROMs. I can some ROMs but not all the error I get it says i'm losing Root after successfully installing a ROM (I get no errors installing a ROM) but after I swipe dalvik & cache it says I have lost root and TWRP says if it will fix my root but it doesn't I've stayed on Samsung NOTE II sign for more than 10 minutes and nothing i've also installed the latest SUPERSU zip file after installing a ROM and still nothing can anyone tell me what i'm doing wrong or what I need to do please,,, thanks in advance!!!!
https://www.dropbox.com/s/hskv5j7gjlhq99r/2014-02-07 03.00.53.mp4
Do you have the latest TWRP?
MunkinDrunky said:
Do you have the latest TWRP?
Click to expand...
Click to collapse
Yes sir I do have latest TWRP.
I'm stuck having this problem ever since i Flash Stock Firmware 5.1.1 on my SM-G925I
Previously, i was running on Stock Firmware 5.0.2 with Root without any Custom Rom. What i did was... I just Flashed the new Firmware i've downloaded from SamM0bile. Done! So next i just try to Root my phone again using the AndroidRootz method (which i did for my 5.0.2 Firmware) & while trying to get into Recovery Mode i get this error.
I click on my SuperSU app which was already installed on previous Root it does nothing, then i check for a Software Update it says my Device is modified.
I have this feeling is related to the TWRP.tar file i Flashed.
PLEASE HELP.....
As soon as you put on that custom recovery you will get that error on 5.1.1, I get that everytime I boot my phone with a custom rom.
dwarfer66 said:
As soon as you put on that custom recovery you will get that error on 5.1.1, I get that everytime I boot my phone with a custom rom.
Click to expand...
Click to collapse
Any remedy??
No mate, thats Samsungs way of punishing us users of custom roms!