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 ...
Related
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery <cwm filename>". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
tbazett said:
I've tried installing ClockworkMod Recovery 5.0.2.0 and ClockworkMod Touch Recovery 5.8.1.8 on my AT&T Atrix 4G with the same results:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
The result is that I can boot to recovery and flash CM7 to the phone, but ROM Manager does not recognize the recovery partition. To install CWM I used "fastboot erase recovery" and "fastboot flash recovery ". It was unlocked and rooted using Pete's Motorola Tools.
This has appeared on other threads that have been closed and appear to end around November 2011. I can't find a definitive answer in the forums - there appears to be disagreement on whether or not there is a reliable ClockworkMod Recovery image. Some tips refer to removing /system/etc/install-recovery.sh, but this file is not present.
Is this a known issue? Is there a fix? Have I missed something obvious?
Click to expand...
Click to collapse
Same problem, can't locate an answer. Can someone weigh in, point us to the solution, etc.?
Thanks.
Edit: never mind. Touch removed, issue solved.
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
matrixx333 said:
Phone: Atrix 4G (2.3.6)
Carrier: AT&T
I began this process with a stock phone. I wanted to install Cyanogenmod and was following the instructions listed on their site. The title of the article was 'Motorola Atrix 4G: Full Update Guide'. I was able to install the unlocked bootloader, but when I go to try and install CWM I am also receiving the:
Flashing partition recovery
Flashing MBR to device
Flashing Stormgr partition: SOS
messages. I have booted into the OS and browsed my /system/etc for anything called install_recovery.sh, but this file does not exist. I would love to continue installing Cyanogenmod, but have hit a brick wall.
Also if I boot into fastboot and do a 'fastboot erase recovery' I receive a different error:
StorMgr Formatting SOS
Any help is appreciated!
Click to expand...
Click to collapse
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
vladeco said:
That is not an error actually. That's how fastboot shows you are currently formatting Recovery partition (and it calls it SOS).
It happens when you erase or flash recovery. If you look closely, when you tell moto-fastboot to erase webtop, the phone calls it "osh".
I personally only use TWRP recovery, and I would recommend that over CWM (or CWM Touch).
Click to expand...
Click to collapse
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
Did you try rom manager. download it from the market and flash CWM through it.
matrixx333 said:
Thank you for the fast reply, but I also receive the exact same message when trying to install twrp 2.2.
*sigh*
Click to expand...
Click to collapse
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
harishatrix said:
Did you try rom manager. download it from the market and flash CWM through it.
Click to expand...
Click to collapse
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett said:
I've come to the conclusion that it is an error, probably due to hardware, and it's not going to be fixed. The main disadvantage is that the ROM Manager app doesn't recognize the recovery partition so you can't use any of the features there that require it. I just use CWM directly and it seems to work just fine. I've been running CWM Touch, switching between CM7 and CM9 several times, for the past 5 months and it's good enough for backing up, recovering, and flashing.
Click to expand...
Click to collapse
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
matrixx333 said:
harishatrix,
From reading the 'THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs' information I was under the impression that rooting and unlocking the bootloader are two seperate things. I did unlock the bootloader, but I thought you had to 'root' the device in order to install ROM Manager. Am I mistaken?
tbazett,
You said you use CWM directly. How do you do this? I thought you were getting the 'SOS' error when you tried to install CMW. Was there a work-around that you used to bypass this message?
Click to expand...
Click to collapse
If I remember correctly, it just stays at the SOS error message so I had to pull the battery to turn it off. After putting the battery back in I was able to turn it on, access the boot menu (using volume down button), and then boot up to the recovery partition.
I don't know what causes the error, but my guess is there is something at the very end of the process that fails, like a checksum or some sort of signature. The result is that it actually works fine on it's own but the ROM Manager fails to recognize it.
Tbazett,
Do you remember how long you waited before you pulled the battery? Im curious if im just not waiting long enough for the install to complete.
Also, would i access CWM by powering down, holding vol down + power, then use the vol down button to cycle to 'android recovery'?
Sent from my MB860 using xda app-developers app
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
matrixx333 said:
HA! I just rebooted into android recovery for the heck of it and twrp 2.2 was installed successfully!!!
Now im on my way to modding!
Thanks again to everyone, I found everyone's advise helpful!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Cool - check out CM9 from Jokersax. You just download the cm9 zip and the google apps zip and flash both in that order.
Here's the forum for it: http://forum.xda-developers.com/showthread.php?t=1445052
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.
Recently i was trying to install custom rom "du_n7000_v.7.0_20140411.zip" on to my note GT N7000, initially i got an error saying status 7.
after that i searched for the same error and got a solution, asking to delete couple of lines from the script file after unzipping the zip file.
I deleted the extra lines which were causing the status 7 error, after that i got Verification Error, and none of the 4.4 roms can be installed or ported on to my GT N7000 device.
IF there is any other way than please do let me know.
Thanking in Advance.
djp007s29 said:
Recently i was trying to install custom rom "du_n7000_v.7.0_20140411.zip" on to my note GT N7000, initially i got an error saying status 7.
after that i searched for the same error and got a solution, asking to delete couple of lines from the script file after unzipping the zip file.
I deleted the extra lines which were causing the status 7 error, after that i got Verification Error, and none of the 4.4 roms can be installed or ported on to my GT N7000 device.
IF there is any other way than please do let me know.
Thanking in Advance.
Click to expand...
Click to collapse
Which recovery and version are you using? You need one that has SELinux support for KK roms. Also, it's recommended to also factory reset your phone after installing the rom and gapps for KK roms, according to the Omni thread for N7000.
Samsung GT N7000
es0tericcha0s said:
Which recovery and version are you using? You need one that has SELinux support for KK roms. Also, it's recommended to also factory reset your phone after installing the rom and gapps for KK roms, according to the Omni thread for N7000.
Click to expand...
Click to collapse
I am using CWM v6.0.3.3. i also used the advance Touch CWM recovery but still i am not able to install 4.4 roms, 4.3 is not a problem at all, it gets installed without any problems, but when i try to install 4.4 roms it gives error of " Status 7"
Thanking you for your prompt reply. If there is any solution for it than do let me know.
It's definitely your recovery. That version came out in middle of last year and Kit Kat & SELinux being necessary wasn't a thing. You need one of the newest recoveries from CWM, Philz Touch (modded CWM - if you like CWM, you'll probably like Philz better), or TWRP.
Samsung GT N7000
es0tericcha0s said:
It's definitely your recovery. That version came out in middle of last year and Kit Kat & SELinux being necessary wasn't a thing. You need one of the newest recoveries from CWM, Philz Touch (modded CWM - if you like CWM, you'll probably like Philz better), or TWRP.
Click to expand...
Click to collapse
I used Philz touch (Advanced Touch CWM) but even after using Philz Touch, i get Status 7 Error and after removing the mentioned files from script i get authentication error. And this error comes for all 4.4 Roms, if i install 4.3 through Philz Touch it gets installed like a charm, so now i really can not understand what exactly is the problem for installing 4.4 roms.
djp007s29 said:
I used Philz touch (Advanced Touch CWM) but even after using Philz Touch, i get Status 7 Error and after removing the mentioned files from script i get authentication error. And this error comes for all 4.4 Roms, if i install 4.3 through Philz Touch it gets installed like a charm, so now i really can not understand what exactly is the problem for installing 4.4 roms.
Click to expand...
Click to collapse
I'm not sure how to be more clear. The version of the recovery you are using is out of date. It's very simple. Update your recovery to something that has support for flashing 4.4 roms. It does not matter that 4.3 roms install fine with that recovery as 4.3 does not equal 4.4 and the install methods have changed somewhat. The only other time you are gonna get the Status 7 errors is when you are trying to install the rom that's built for another phone or version of the phone you are using and the updater-script has an assert to check the build.prop to make sure you install it to the right device. But update your recovery first and go from there.
es0tericcha0s said:
I'm not sure how to be more clear. The version of the recovery you are using is out of date. It's very simple. Update your recovery to something that has support for flashing 4.4 roms. It does not matter that 4.3 roms install fine with that recovery as 4.3 does not equal 4.4 and the install methods have changed somewhat. The only other time you are gonna get the Status 7 errors is when you are trying to install the rom that's built for another phone or version of the phone you are using and the updater-script has an assert to check the build.prop to make sure you install it to the right device. But update your recovery first and go from there.
Click to expand...
Click to collapse
I am downloading 4.4 roms from XDA Samsung Galaxy GT - N7000 , still i can not install the roms, if you have any 4.4 rom for Galaxy Note GT-N7000 than do let me know i would try to install that rom on to my Galaxy Note.
Appreciate your help on time.
Thanking you
Regards
Galaxy Note GT-N7000
djp007s29 said:
I am downloading 4.4 roms from XDA Samsung Galaxy GT - N7000 , still i can not install the roms, if you have any 4.4 rom for Galaxy Note GT-N7000 than do let me know i would try to install that rom on to my Galaxy Note.
Appreciate your help on time.
Thanking you
Regards
Click to expand...
Click to collapse
I have Successfully Installed du_n7000_v.7.0_20140411.zip.
Steps taken.
1. Wipe Cache Partition
2. Wipe Data/Factory reset
3.Advance/Wipe Dalvik Cache
Any body who gets Status 7 error, please follow these steps. Now i dont get Status 7 error or Authentication error and the rom got installed.
Regards
djp007s29 said:
I have Successfully Installed du_n7000_v.7.0_20140411.zip.
Steps taken.
1. Wipe Cache Partition
2. Wipe Data/Factory reset
3.Advance/Wipe Dalvik Cache
Any body who gets Status 7 error, please follow these steps. Now i dont get Status 7 error or Authentication error and the rom got installed.
Regards
Click to expand...
Click to collapse
This is basically the steps to take when installing any new custom rom. How WERE you trying to install the rom??
S1
es0tericcha0s said:
This is basically the steps to take when installing any new custom rom. How WERE you trying to install the rom??
Click to expand...
Click to collapse
The only thing i never did was step 1. Ie Wipe Cache Partition.
but without doing step 1, i was able to install all other versions of rom but could not instal 4.4 rom. when i did Wipe Cache Partition, i could install 4.4 Rom without Status 7 Error and also now not getting authentication error.
Regards
djp007s29 said:
The only thing i never did was step 1. Ie Wipe Cache Partition.
but without doing step 1, i was able to install all other versions of rom but could not instal 4.4 rom. when i did Wipe Cache Partition, i could install 4.4 Rom without Status 7 Error and also now not getting authentication error.
Regards
Click to expand...
Click to collapse
Ah ok. Well, the factory reset should also wipe the cache too, but it is not uncommon for Samsung's of this vintage to need extra wiping. Dunno why, but have seen it before.
Hi,
I've been hitting my head against a wall trying to install a new Rom on my Galaxy S3 I9300 device.
My device has super user permissions, I've installed CWM, also installed Super User, Root Checker, and confirmed that the device does have root access.
The issue is, when trying to install a new ROM, Revolution and also tried Hypermax. When I try to install Revolution my device doesn't go anywhere but just reboots. When I try to install Hypermax, I get the error;
"e:signature verification failed"
I've followed the following tutorials to get the steps to change the ROM;
http://joyofandroid.com/install-android-revolution-hd-custom-rom-on-samsung-galaxy-s3/
http://forum.xda-developers.com/galaxy-s3/development/rom-hypermax-v8-t2755048
To try and go around the error above, I've downloaded CFRoot, successfully installed, but the same issue again when trying to install either ROMs above.
Have also tried to install superuser.zip but again, I get the "e:signature verification failed" error.
The main issue I think is that when I boot into recovery, I don't have the option to access the advanced options so can't toggle email signature options. The advanced options I'm missing are like that in the first image on the following link; http://www.recovery-android.com/root-android-in-recovery-mode.html
If anyone can help, would really appreciate it.
Cheers.
eamokeno said:
Hi,
I've been hitting my head against a wall trying to install a new Rom on my Galaxy S3 I9300 device.
My device has super user permissions, I've installed CWM, also installed Super User, Root Checker, and confirmed that the device does have root access.
The issue is, when trying to install a new ROM, Revolution and also tried Hypermax. When I try to install Revolution my device doesn't go anywhere but just reboots. When I try to install Hypermax, I get the error;
"e:signature verification failed"
I've followed the following tutorials to get the steps to change the ROM;
http://joyofandroid.com/install-android-revolution-hd-custom-rom-on-samsung-galaxy-s3/
http://forum.xda-developers.com/galaxy-s3/development/rom-hypermax-v8-t2755048
To try and go around the error above, I've downloaded CFRoot, successfully installed, but the same issue again when trying to install either ROMs above.
Have also tried to install superuser.zip but again, I get the "e:signature verification failed" error.
The main issue I think is that when I boot into recovery, I don't have the option to access the advanced options so can't toggle email signature options. The advanced options I'm missing are like that in the first image on the following link; http://www.recovery-android.com/root-android-in-recovery-mode.html
If anyone can help, would really appreciate it.
Cheers.
Click to expand...
Click to collapse
what version of android do you have before u start rooting? is it 4.1 or 4.3?
which version of CWM?
Hi, the version of CWM is 5.5.3.1 and the android version is 4.3.
Thanks
Hello
You need to install the lastest CWM recocery
Sent from my GT-I9300 using XDA Free mobile app
Hi,
Yeah that was it. That worked for me. Thanks a lot for your help.
Cheers.
KeTuRr74 said:
Hello
You need to install the lastest CWM recocery
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
eamokeno said:
Hi,
Yeah that was it. That worked for me. Thanks a lot for your help.
Cheers.
Click to expand...
Click to collapse
You're welcome
Sent from my GT-I9300 using XDA Free mobile app
Hi,
Now any application from Google me does not work ... I get an "Application been stopped."
By this, I can not run the part on the function of the system and I can not download or update the application.
I decided that I install the new ROM (Mokee), but Interestingly, during the installation of CWM appears "Instalation aborded Status 7".
I made all the steps of the Internet, which had to delete this mistake, but it did not help ...
I have a phone Huawei Ascend Y550-L01 (c8817d - code name).
I also have a CWM version 6.0.5.1.
I have granted root privileges (administrator)
Please, quick help, because the hard-purpose a phone in this way ...
Comb0 said:
Hi,
Now any application from Google me does not work ... I get an "Application been stopped."
By this, I can not run the part on the function of the system and I can not download or update the application.
I decided that I install the new ROM (Mokee), but Interestingly, during the installation of CWM appears "Instalation aborded Status 7".
I made all the steps of the Internet, which had to delete this mistake, but it did not help ...
I have a phone Huawei Ascend Y550-L01 (c8817d - code name).
I also have a CWM version 6.0.5.1.
I have granted root privileges (administrator)
Please, quick help, because the hard-purpose a phone in this way ...
Click to expand...
Click to collapse
I can tell you the status 7 error in recovery means you need to update the recovery to the newest version, that may be where your problem lies
Sent from my Nexus 5
ShapesBlue said:
I can tell you the status 7 error in recovery means you need to update the recovery to the newest version, that may be where your problem lies
Sent from my Nexus 5
Click to expand...
Click to collapse
For my phone is the latest version. Unless otherwise compatible with my device ... Anyone know if there is another version compatible with my phone?
Can I install the ROM .zip file from your computer?
Is there any other way to install the rom?
Comb0 said:
For my phone is the latest version. Unless otherwise compatible with my device ... Anyone know if there is another version compatible with my phone?
Can I install the ROM .zip file from your computer?
Is there any other way to install the rom?
Click to expand...
Click to collapse
Maybe try another recovery if cwm isn't working properly?
Sent from my Nexus 5