I've been using RemICS 1.3.1 ROM for a while. And now I'd like to upgrade to current 4.2.1 version but I'm getting Status 7 error: assert failed. I've found that I should try using Icy Glitch v14 kernel to flash a new rom but all links to this kernel are dead and I can't find it. Can someone help me to upgrade?
BTW: Should I expect some new bug on JB ? GPS is still not working there I guess...
lorendroll said:
I've been using RemICS 1.3.1 ROM for a while. And now I'd like to upgrade to current 4.2.1 version but I'm getting Status 7 error: assert failed. I've found that I should try using Icy Glitch v14 kernel to flash a new rom but all links to this kernel are dead and I can't find it. Can someone help me to upgrade?
BTW: Should I expect some new bug on JB ? GPS is still not working there I guess...
Click to expand...
Click to collapse
I had the same thing at some point last night as well, along with all the unknown upload mode errors and a series of other issues. The best advice I can give is to just keep trying different combinations.
I did end up going all the way back to stock a number of times. This might sound silly, but if I remember correctly, I successfully flashed ICZen and then I installed RemICS-JB from there. Had to swap the vold.fstab of course, but it's running very smoothly with RemICS-JB and Semaphore 2.9.
Sorry I couldn't be of more assistance, but with the amount of combinations and paths I tried, it's all a jumble.
Hi,
It gave me Status 7 error. Then I pulled the battery and rebooted into CWM. But after that it gave me freezed kernel screen
and I again did a battery pull and booted into CWM which was then converted to semaphore. Then I flashed the ROM again and gapps successfully
Hope this helps
tc
Related
Before reading, please note that this problem was resolved - of course thanks to those who helped with tips and tricks... Continue reading towards the end if you wish to know how to fix this issue if you encountered it.
Original message:
Hello folks,
I'm not exactly a total n00b but I've been a hardcore iPhone fan then entered the world of Android when I got my SGS2 a few months ago. I need some feedback here with flashing Cyanogenmod 7 or 9 (I WISH)
I have my At&t rooted with Zedomax kernel and Odin v1.85
Root functionality is all good, and "superuser" does everything I ask it to
Now, I had tried to flash the "Unnamed" Rom and it worked before... Then went bacl to stock (using the backup I had before)
Now... the problem is that getting Cyanogenmod (whether 7 or 9) has been a complete challenge, but I'm loving it and won't give up
I tried CM7 as well as CM9. Always get the error message below.
Please note that I had also tried everything alltogether while on the (Siyah-v2.6.11-att) which is great too. But same thing happens every time (below is the log)
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxys2"
.........and this line repeats then same exact line except it mentions "GT-I9100" like twice (2 lines) and same line again but "GT-I9100M" and then "GT-I900T"
Then last line in the log is E:Error in /sdcard/update....(mentions full path of zip file) then (status 7)
Something that might help is that I (unfortunately) updated my phone when At&t released this minor update back in December/early January... So my firmware is "UCKK6"
What exactly is causing this error?? If "Unnamed Rom" worked fine, then why is Cyanogenmod being stubborn??
Thanks for any help... Would really appreciate it
sounds to me like you are trying to flash the WRONG cm7....you need the one made for the phone, found in the dev section
First you really should get rid of Zedomax kernel and keep using Siyah or Entropy.
The kernel you are using is way outdated and I am sure Entropy can give you a dozen reasons why not to use it.
Second do not try flashing CM9, cause you won't have a functional phone if you do.
When flashing CM7 did you try flashing it twice before rebooting?
Pirateghost said:
sounds to me like you are trying to flash the WRONG cm7....you need the one made for the phone, found in the dev section
Click to expand...
Click to collapse
Was about to mention that as well, beat me to it.
Thanks Pirateghost.
I got the rom from the Cyanogenmod website, and it's the only stable mod for AT&T SGS2. So it's the right rom/mod.
But as I'm typing I'm downloading the latest nightly for AT&T and will give it a shot.
LiLChris06 said:
First you really should get rid of Zedomax kernel and keep using Siyah or Entropy.
The kernel you are using is way outdated and I am sure Entropy can give you a dozen reasons why not to use it.
Second do not try flashing CM9, cause you won't have a functional phone if you do.
When flashing CM7 did you try flashing it twice before rebooting?
Was about to mention that as well, beat me to it.
Click to expand...
Click to collapse
@LilChris06
Thanks for the tips man
Just got rid of Zedomax lol... now back on Siyah, and will give Entropy a go later tonight.
TahrirSquare25 said:
Thanks Pirateghost.
I got the rom from the Cyanogenmod website, and it's the only stable mod for AT&T SGS2. So it's the right rom/mod.
But as I'm typing I'm downloading the latest nightly for AT&T and will give it a shot.
Click to expand...
Click to collapse
I hope your not getting this one - http://www.cyanogenmod.com/devices/samsung-galaxy-s2
That is more than likely for the i9100 version.
Grab this one - http://forum.xda-developers.com/showthread.php?t=1471365
Next time check the development forums before flashing things.
LiLChris06 said:
I hope your not getting this one - http://www.cyanogenmod.com/devices/samsung-galaxy-s2
That is more than likely for the i9100 version.
Grab this one - http://forum.xda-developers.com/showthread.php?t=1471365
Next time check the development forums before flashing things.
Click to expand...
Click to collapse
W0W!!! So those mods on the official Cyanogenmod website for SGS2 are ONLY for non-U.S. model!!!!!! Thanks a bunch man!!
I went ahead and got the latest nightly mod (02012012) but it came back with "Can't open /sdcard/..... (bad) installation aborted"
Will try my luck with earlier nightlies, perhaps this zip (02012012) is corrupt.
TahrirSquare25 said:
W0W!!! So those mods on the official Cyanogenmod website for SGS2 are ONLY for non-U.S. model!!!!!! Thanks a bunch man!!
I went ahead and got the latest nightly mod (02012012) but it came back with "Can't open /sdcard/..... (bad) installation aborted"
Will try my luck with earlier nightlies, perhaps this zip (02012012) is corrupt.
Click to expand...
Click to collapse
i also had the same issue
To flasb CM7 and NOT get the get.prop error( which you will get coming from the siyah kernel and trying to update/or install CM7) download this kernel reverter/kernel cleaner http://db.tt/s6xToyVV MAKE SURE to put this kernelreverter/cleaner on your internal sdcard along with this newest build fojnd here of a CM7 KANG build https://s3.amazonaws.com/cyanogenmodbuild.s3.mortimer.me.uk/index.html
Then boot to recovery, choose the kernel reverter.zip and flash it, before rebooting then choose the newest updated nightly kang build and flash it, then reboot phone. Yoh should NO LONGER have an issue. ALSO MAKE SURE TO FLASH GAPPS if you want the market and other google apps like gmail etc.
Next if you want you can then reinstall siyah kernel over on top of the cm7 build. When you go to flash a NEWER nightly update then AGAIN flash the kernel reverter/cleaner then the newer update. If you are on the siyah kernel you will get the get.prop error if you DON'T flash the kernel reverter first.
Sent From My KickAss ATT SGS2 SPORTING CM7
THANKS A LOT RockRatt
For the tip, as well as the excellent tool "kernel reverter/cleaner"
It took care of the error, and installation went well.
Afterwards I was stuck with the CM7 boot loop, but searched and found a quick fix that took care of it - wiping /data once more after the actual install.
CM7 up and intact
Now, I will play around with tweaks and themes.
Can't wait for the first stable CM9 mod for i777.
I am using ics passion rom for past 5 months .....recently tried flashing iczen and encountered these problems .......1-whenever I flash an ics rom it bootloops and each time I have to remove battery and rebot again ...like this for nearly 3 to 5 times if I do after that it boots properly after that It runs fine .....2-after installing iczen for 1 day it worked fine later it was not recievieng any calls but i was able to call others ....for information I stay in India so worried of doing something as I won't get any support here ....now I'm on ics passion ...plz help me out.
Well the problem is, and maybe this is why no one replied, you need to do a full wipe and a cache wipe before flashing into diff roms like from passion to iczen
Sent from my SGH-T959 using xda app-developers app
Aside from wiping properly, you might have downloaded the problematic ICZen 1.8.5, check your MD5 against what I have posted in that OP.
For about 12 hours I had one posted that had a problem with the ramdisk in the kernel, and it was not compatible with the Froyo RIL that was included with the AOKP milestone6 source MP used to build the ICZen base. The rom has since been updated with a good kernel that supports both RIL types, and a new MD5 is posted in the thread so you can verify if you have the correct version. Not all phones had the issue, but some did, it was a weird one, but it caused exactly what you are experiencing, loss of signal and ability to receive calls and texts.
Also, you might want to try the Stock RIL, thats posted on the other site, in mr_psycho's subZero kernel thread. Its a flashable zip. The kernel currently in ICZen_1.8.5 is compatible with both RILs now, so if you redownload the rom, you'll be safe either way.
after flashing 1.8.5 again its working properly ......thanx for helping another thing does baseband version changes after flashing a rom? I have same version in both ics passion and iczen is this normal?
ICZen won't flash the modem if you already have a valid modem in place. In other words, if you come from a Twiz based build, then it flashes the KB5 modem, but coming from another ICS rom, it won't flash a modem since there is already one there.
Hi,
For the past while i was getting the SOD only using Siyah based kernels and Phenomenal was working fine for me, but after updating to version 6.1 my phone has started to switch off again. Is this a problem with hardware and do i need to send the phone away for repair or can it be fixed by myself some other way?
I have went back to Phenomenal 5,5 kernel and am waiting to see if i still get the problem.
Cheers.
jpopgt said:
Hi,
For the past while i was getting the SOD only using Siyah based kernels and Phenomenal was working fine for me, but after updating to version 6.1 my phone has started to switch off again. Is this a problem with hardware and do i need to send the phone away for repair or can it be fixed by myself some other way?
I have went back to Phenomenal 5,5 kernel and am waiting to see if i still get the problem.
Cheers.
Click to expand...
Click to collapse
What rom are you on? Can you refer to the thread in my sig for the info you need to include to get results.
Sent from my Nexus 7 using xda premium
kilometers4 said:
What rom are you on? Can you refer to the thread in my sig for the info you need to include to get results.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hello,
I have tried just about all the latest ICS and JB roms......
The make of your phone. There are many different variants of your device. I9100 G/M/P/T
Are you rooted/unrooted?
What rom you are using? -and- What kernel are you using?
Have you flashed any mods/scripts/themes?
Have you changed DPI? If yes, to what?
I have a UK T-Mobile Samsung Galaxy S II I9100XXLQ6
I am rooted
I was Dual Booting with SuperNexus JB Build 2 and Portal Rom 2.4 using the latest siyah kernel and i got the SOD using SuperNexus, i then removed The second rom and used the ultimate kernel cleaning script to remove Siyah and installed Phenomenal 6.1 with Portal Rom and i got the SOD a day later.
I am not using any mods or extra scripts
I have not changed the dpi
I noticed this problem when i first tried a dual boot a few months ago but has been stable until now only with Phenomenal 5.5. i have tried the other siyah based kernels and i still got the SOD.
Yesterday i flashed the Phenomenal 5.5 along with Portal rom and it's been fine so far but i can get 2-4 days before it happens then it happens a few times daily after the first SOD.
EDIT: Thats it switched off again. Think i will need to send it in for repair?
Ok update again,
Changed the recovery to the cwm4 fixed for cm7
Eh03 rom
Atlas_v2.2 pit
Latest cm7.2/gapps
http://forum.xda-developers.com/sho... could it be my sdcard?
thanks for the help!
Idk much about cm7 but I suggest moving to something newer like cm10.1 (4.2.2) you wont be disappointed its fast, more stable than any GB ROM, and its on the latest version of android
Sent from my SCH-I500 using Tapatalk 2
(Solved) Running CM
Well something worked, I'm running CM. I went and re downloaded the rom and gapps directly to the phone and bam, things went off without a hitch, seems it was a major case of user error .
Finally managed to get my phone working again...But can someone tell me what went wrong?
I was running JB NEATROM with SIYAH 4.1.5 Kernel. Strde I flashed GS2Wiper and then Dorimanx 9.42 kernel, then flashed CM 10.2. Booted and found all normal. went back and flashed Gapps system showing google maps , playstore error . Unable to use phone. Tried back flashing CM 10.2 and Slimbeam Rom working fine, but when flashing Gapps system gets stuck in booting logo.
Finally flashed old siyah kernel 4.1.5 and flashed NEATROM and to my big relief system operational. I want to update to JB 4.3 .Can someone please advice
are you doing a wipe and factory reset after all the different roms you are trying?
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
gastonw said:
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
Click to expand...
Click to collapse
Gaston, good to see you mate! Been stuck in another book for a few weeks?
@ OP: Beautiful summary by gastonw right here. Read the OP of the thread 2-3 times before flashing. You want to make sure it's compatible with your device, other mods/firmware, and that you know what you're doing during the install process.
Hey hopper, no, it's the UFC era now
Sent from the little guy