Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
http://forum.xda-developers.com/galaxy-s2/help/to-mod-s2-t3189884
I've just tried this, didn't work also. I even had to flash the recovery and the kernel again after trying to flash the file in the link, because the phone wouldn't boot normal or in recovery mode.
mcb25 said:
Hey,
I got a problem with my S2g. I'm currently on Android 4.1.2, with cwm 6 and blazing v-5 kernel. Both were flashed per odin and work fine. However I can't flash a custom rom. Every time I try it I'll get a Status 7 error. I've already tried 4 different ROMs and I'm really annoyed by now. I also tried to factory reset the phone before I flash the ROM, but it didn't make any difference. I also tried deleting the assert command in the updater-script file but somehow my changes in the file won't be saved.
If anyone could help me I would be really thankful!
Click to expand...
Click to collapse
Try using philz recovery on your phone. It should flash most ROMs fine.
gsstudios
gsstudios said:
Try using philz recovery on your phone. It should flash most ROMs fine.
Click to expand...
Click to collapse
I just did, I still get the Status 7 error. I tried to flash the cm 12.1 and the cm 13.0 nightly rom. I also tried deleting the assert command in the updater-script file but it still won't work. There was no Status 7 error but it still said "Installation aborted".
Does anyone else got an idea how to fix this?
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
mcb25 said:
http://forum.xda-developers.com/galaxy-s2/development/kernel-blazing-kernel-v16-t2275275
I used this Kernel, I just noticed, that it's only compatible with Android 4.1, 4.2 or 4.3.
I then tried to install the DorimanX Kernel for LP and MM (http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-dorimanx-lp-5-x-x-t3145879) but my phone stucks at the boot screen.
Click to expand...
Click to collapse
Apologies, I only just noticed you have a i9100g, not a i9100. You can't just flash i9100 kernels as they simply won't work!
You can follow the guide in the CM13 OP here:
http://forum.xda-developers.com/galaxy-s2/development/rom-cyanogenmod-13-0-t3381511
gsstudios
Related
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Can't install Jellybam???
fountain79 said:
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Click to expand...
Click to collapse
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Thanks
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Trying now...
Its working
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Thanks again for sharing the info very helpful.
did that work
fountain79 said:
Thanks again for sharing the info very helpful.
Click to expand...
Click to collapse
Hi All
Did the method of installing Siyah Kernel and then flashing JellyBam work to resolve "error code 7" issue ??
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
i had the same issue
nikal said:
I have SGP311 4.2.2 stock rooted with this kernel and regularly I am trying to install varius custom ROMS but I am always getting Error Status 7 and flashing stops. The only way to overcome this issue is to install first the boot.img from the ROM that I am going to install and then through the Recovery of the new boot.img I can install the custom ROM without errors.
I know this is not a normal behaviour and I am trying to figure out what's wrong. I tried to edit updater-script by removing all the getprop lines but then I got the same error when the set_perm command is executed.
Could you help me ?
Thanks!
Click to expand...
Click to collapse
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
hassanman1997 said:
i had the same issue while i was flashing cyanogen mod 10.1.3 , any ways i kept trying, i still recieved an error
afterwards i tried to download the rom again and then i placed it into my internal sd storage, after soo many tries, i finally got it working
maybe its the issue with your zip file, try downloading it again, place it into your internal storage, not external, then flash it
Click to expand...
Click to collapse
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
nikal said:
Hi and thank you for the reply.
I tried to install from the internal flash though I didn't believe that the result would be different and I had the message (set_perm Error Status 7). It's very strange that no other users mentiong this problem. I am thinking maybe it's something with my stock ROM or some other setting.
Click to expand...
Click to collapse
i think you have mentioned that you flashed the boot.img before you tried flashing the rom, i would recommend to flash the right boot.img again from the rom, this is the most common issue when u get status 7 error,
other wise, backup all of your important data, return to stock by using flash tool / factory data reset, root again and then flash the boot.img and then flash the rom
thats what i do when im desperate for the rom :laugh:
------------- SOLVED! --------------
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Steelbear said:
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Click to expand...
Click to collapse
please read the thirst post in a rom/kernel/whatever thread. and maybe if you havent done it already you should also read the stickies in general section.
FAQ (Read before post !!)
- If you obtain Error 7 when you tried to install ROM in CWM or TWRP
Install the latest version of CMW or TWRP
Click to expand...
Click to collapse
BTW latest philz touch recovery works too
Since you went back to stock and you already know how to root, I suggest you go to Play Store and download ROM Manager to help you install latest CWM recovery on your device.
Or you can simply go to CWM website, pick the version of the recovery for your phone and flash it via Odin.
Hope it helps.
Steelbear said:
Hello all,
First of all I want to say I'm pretty new to flashing ROMs etc.
Currently I'm at stock 4.3 Jellybean and I want to flash my SGS3 to the new CM 11 ROM.
I rooted my phone following this tutorial: vvvvvv.telefoonrooten.nl/samsung/samsung-galaxy-s3-root/ (sorry if its in Dutch, but it uses the CF-Root-SGS3-v6.3 and Odin).
After I rooted I copied both the CM11 ROM and GAPPS to my external SD, I went to recovery and tried to install the new custom ROM but I got an error (status 7) and it was aborted.
Also if I try to reboot it won't boot normally as it should be but it goes back to recovery mode automatically...
I fixed to get back to Jellybean by flashing the stock rom (unrooting?) it via Odin.
Anyone else got the exact same problem as I do and knows a solution to be able to flash CM 11?
Thanks in advance,
Steelbear
Click to expand...
Click to collapse
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Blackwolf10 said:
I had the same problem the fix is quite easy
flash the latest CWM 6.0.4.4 and flash cm11 it will work fine
Click to expand...
Click to collapse
Indeed it worked! I found it out myself yesterday. Went to the CWM site and downloaded the latest version (6.0.4.4.) and flashed it through Odin. But thanks for your input anyways (to all who replied) !
An alternative solution that I often use is to open the Updater Script in META-INF folder in the ROM's zip and delete first lines, where it gets device model as property.
Obviously it's an UNSAFE operation (because that lines avoid to install ROMs of other phone on mine) but when I'm sure that ROM I've downloaded is for my phone I do it and it works
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.