can anyone link to a stable CM11 rom for a galaxy s2 i9100T? ive tried a couple of the nightly builds from the CM download page but i get an error status 7 everytime, which im guessing is something to do with it not being the 'right' rom for my phone
ive been able to install CM10.1.3 fine but not CM11
i dont want to force it by removing the assert lines from the script updater!
Hi...
I have the same issue and I guess it's because the phone model (i9100T) doesn't match the phone model of the ROM (i9100).
I've tried to download the newest version of the kernel (Siyah v6.05b) I read it could help, but nothing so far.
I'm still getting the status 7 massage when I'm trying to flash to a CM11.
Because there are not hardware difference between the i9100t and i9100 I believe nothing will happen if I'll solve/ignore the statue 7 and continue anyway but I have no guaranties the this will work.
I really don't want to hard bick my phone!
Can any body help me with this issue?
Thanks
You both need to flash a KK compatible CWM (6.0.4.5 or newer) first........
Just make sure the ROMs you are trying to flash ARE compatible with your phones first.
My wife says I'm a phone geek....She's probably right
Guys.....this is BASIC stuff/info......and something that you both WOULD have known if you'd read the first post of the thread where you got your ROMs.......
My wife says I'm a phone geek....She's probably right
keithross39 said:
You both need to flash a KK compatible CWM (6.0.4.5 or newer) first........
Just make sure the ROMs you are trying to flash ARE compatible with your phones first.
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
My girlfreind says it too... so you're in good company.
I tried your method but it didn't work, I tried flashing it with odin and when I reboot the device it was in soft brick.
I flashed it back with the old kernel and got it back to work.
All guides that reffers to flashing KK with sgs2 are reffering to model i9100. it seems people with i9100 don't suffer from our issue so I guess the problem is with our specific model i9100t and not a CWM problem.
I investigated the status 7 issue and it seems to happend when the model of the device don't match the ROM targeted model device.
Do you have any other ideas?
Thanks for helping
Maybe you should try re-dowloading the ROM. This can *sometimes* happen if the download gets corrupted.......
My wife says I'm a phone geek....She's probably right
kiwijas said:
can anyone link to a stable CM11 rom for a galaxy s2 i9100T? ive tried a couple of the nightly builds from the CM download page but i get an error status 7 everytime, which im guessing is something to do with it not being the 'right' rom for my phone
ive been able to install CM10.1.3 fine but not CM11
i dont want to force it by removing the assert lines from the script updater!
Click to expand...
Click to collapse
If you've got as far as successfully flashing 10.1.3, then the only reason you can't flash 11 is the version of CWM you are currently running........
My wife says I'm a phone geek....She's probably right
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
royialtman said:
All guides that reffers to flashing KK with sgs2 are reffering to model i9100. it seems people with i9100 don't suffer from our issue so I guess the problem is with our specific model i9100t and not a CWM problem.
I investigated the status 7 issue and it seems to happend when the model of the device don't match the ROM targeted model device.
Do you have any other ideas?
Thanks for helping
Click to expand...
Click to collapse
The OP states he is running 10.1.3 (which I assume is an i9100 rom).....
Maybe you could try it this way.....an incremental upgrade......
Root....flash 10.1.3....flash KK CWM....flash 11....
My wife says I'm a phone geek....She's probably right
CM10.3/CM11 i9100 images both directly support install asserts for the i9100T (as well as several other 99%+ similar variants with different model numbers), see https://github.com/CyanogenMod/android_device_samsung_i9100/blob/cm-10.2/BoardConfig.mk
The OP is probably having issues because of not updating kernel/recovery to something recent enough to install CM11.
keithross39 said:
If you've got as far as successfully flashing 10.1.3, then the only reason you can't flash 11 is the version of CWM you are currently running........
My wife says I'm a phone geek....She's probably right
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
The OP states he is running 10.1.3 (which I assume is an i9100 rom).....
Maybe you could try it this way.....an incremental upgrade......
Root....flash 10.1.3....flash KK CWM....flash 11....
My wife says I'm a phone geek....She's probably right
Click to expand...
Click to collapse
I made it!!:highfive::highfive::highfive::good::good::good:
I finally updated the phone to CM11.
I installed KK kernel with CWM and then I flashed the CM11 ROM..
Thanks for all the help!!
Related
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
Hello.
I just rooted my ATT GS2 I777 phone using a method over at galaxys2root.com. i then installed the latest kernel 3.5.1 Sayah WITHOUT mic swap. Can someone please tell me the difference between WITH and WITHOUT mic swap and what it is exactly?
I'm looking for a rom to install now and seem to be having issues finding one that isn't based off the 9100 phone even though they are listed in the I777 forums. I would like to install Serendipity9 or Galaxy Nexus ROMs but not sure if I needed the 3.5.1 WITH mic swap rom or not.
Please help.
Thanks.
With Without mike swap is for I777 stock roms and custom roms made from I777 stock as base, ie Semi. Mike swap is for roms made from I9100 base, or aosp roms.
It doesn't really matter though, because when you install a custom rom, it will also install the kernel that comes with the rom. If it doesn't come with your preferred kernel, then you can flash the kernel or your choice after you flash the rom of your choice.
I think you meant to say for your first word is "Without", correct?
I'm going to try to install Serendipity9 even though I can't find anything about the change log to see what kernel is included.
jackal2001 said:
I think you meant to say for your first word is "Without", correct?
I'm going to try to install Serendipity9 even though I can't find anything about the change log to see what kernel is included.
Click to expand...
Click to collapse
Yes. Fixed it, lol.
The kernel is CherryPicker. See here. I think it's been a while since the rom has been updated. I think Mikey is working on something else now.
I did get the Serendipity 9.4 installed and then ran Siyah 3.5.1 Kernel (with mic swap) and so far everything seems to be working ok.
Thank you for your help.
I would flash something else asap.. Here's a hint, anything it our development section!
Clay
Team Pirate
Sent from my PINK SGH-I777
Please don't talk secret code. I don't have my decoder ring.
If there is something wrong with something I used, please let me know.
jackal2001 said:
Please don't talk secret code. I don't have my decoder ring.
If there is something wrong with something I used, please let me know.
Click to expand...
Click to collapse
There is no code... If you can't understand that you shouldn't be messing with your phone
jackal2001 said:
I just rooted my ATT GS2 I777 phone using a method over at galaxys2root.com
Click to expand...
Click to collapse
Flash something ASAP and get off of that sh¡t - and NEVER use anything from that site again.
It's for your own good.
Clay
Team Pirate
Sent from my PINK SGH-I777
Not sure what you are talking about.
I rooted my phone using their method (odin and siyah kernel). yes now my phone boots saying I9100 and the yellow triangle.
I then Installed Serendipity 9.4 Rom from their official site.
I then Installed Siyah Kernel 3.5.1 from here.
I didn't want to brick my phone by rooting and there are a lot of methods to do so and a lot of old information out on the forums.
What is wrong with what I did?
I plan on going to Jellybean and the latest siyah when the time comes when more stable.
I did see this post over here:
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
I was thinking about doing the below and following the instructions, but no description was there for what this actually did and I'm new to all this.
Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders
I would appreciate it if you can point me in the right direction on how to properly put the phone back and then how to properly root it again.
Well basically this site had a lot of great info and awesome devs. But other sites take their stuff, post links to download the roms and never give proper credit. As far as what yer asking, are u asking how to return to stock? If so, just Google XDA i777 download repository. Here's a link to it. http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 I would go with the stock rooted 2.3.4 without boot loaders. Flash it with Odin. Or mobile Odin pro.
Sent from my SGH-I777 using Tapatalk 2
I'm asking (since they are telling me to get this **** off my phone) how to get it properly rooted and then go from there.
So if I just run Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders, that will properly put my phone back to factory + being rooted. Correct?
The only issue I have with my phone is it boots with an I9100 screen instead of the I777 screen. If I run the above with that properly show the I777 screen or not?
I'm guessing I have some bootloader on my phone since it is showing the I9100 screen??? That is why you guys are telling me to get that off there???
jackal2001 said:
Not sure what you are talking about.
I rooted my phone using their method (odin and siyah kernel). yes now my phone boots saying I9100 and the yellow triangle.
I then Installed Serendipity 9.4 Rom from their official site.
I then Installed Siyah Kernel 3.5.1 from here.
I didn't want to brick my phone by rooting and there are a lot of methods to do so and a lot of old information out on the forums.
What is wrong with what I did?
I plan on going to Jellybean and the latest siyah when the time comes when more stable.
I did see this post over here:
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
I was thinking about doing the below and following the instructions, but no description was there for what this actually did and I'm new to all this.
Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders
I would appreciate it if you can point me in the right direction on how to properly put the phone back and then how to properly root it again.
Click to expand...
Click to collapse
There's nothing wrong with what you did. You rooted your phone and installed a custom firmware without causing any problems. If you are satisfied with your phone as it is, do not flash back to stock just because of some of the posts here.
There are problems with GalaxyS2Root.com. Some of the files that are available there cause people to brick their phones, or have other problems. When the name comes up, people here react to it. That accounts for some of the posts here. But in your case, since you had no problems, and your custom flash went ok as well, not to worry.
Because you flashed a custom kernel using Odin when you rooted with the GalaxyS2Root method, you incremented the flash counter, which also causes the I9100 boot screen with the yellow warning triangle. That can be cleared with a USB jig, or with the application Triangle Away by codeworx which can be used only on ICS or above.
---------- Post added at 08:54 PM ---------- Previous post was at 08:49 PM ----------
jackal2001 said:
I'm asking (since they are telling me to get this **** off my phone) how to get it properly rooted and then go from there.
So if I just run Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders, that will properly put my phone back to factory + being rooted. Correct?
The only issue I have with my phone is it boots with an I9100 screen instead of the I777 screen. If I run the above with that properly show the I777 screen or not?
I'm guessing I have some bootloader on my phone since it is showing the I9100 screen??? That is why you guys are telling me to get that off there???
Click to expand...
Click to collapse
You did not flash I9100 bootloaders. Samsung was lazy, when they made the firmware for I777 they didn't update that image, so it still says I9100.
Oh, and I would suggest that you avoid GalaxyS2Root.com in the future for your own peace of mind.
Creepy,
Thanks again. I did send you a PM as well.
I don't know what a bootloader is and thought maybe the cause of the I9100 screen is due to a bootloader which may cause problems or something for future installs of Kernels and ROMs.
Since my phone is already rooted I plan to just continue to use this site for ROMs and Kernels. I'm still learning.
jackal2001 said:
Creepy,
Thanks again. I did send you a PM as well.
I don't know what a bootloader is and thought maybe the cause of the I9100 screen is due to a bootloader which may cause problems or something for future installs of Kernels and ROMs.
Since my phone is already rooted I plan to just continue to use this site for ROMs and Kernels. I'm still learning.
Click to expand...
Click to collapse
Yeah absolutely man! Sorry I was confused about your question. Thought u wanted to return to stock just to start over fresh. Didn't mean to confuse u or try to cause you any additional work. If it isn't broke, like creepy said, no need to do anything. good luck!
Sent from my SGH-I777 using Tapatalk 2
Thanks but it was the other guys that had me worried as they said to get rid fo that immedately.
I would start over fresh if needed but it looks like I'm ok anyway. I'll move to Siyah 4.1.1( or later) and Jellybean at a later time when more stable I guess.
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
aspen1135 said:
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
Click to expand...
Click to collapse
I would use Heimdall to flash if possable also i would flash Siyah's new kernel also check the md5 to verify the rom you are trying to flash sometimes during download things get goofed after that make sure you wipe everything data/cache/dalvik and then try flashing your rom
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
This link explains how to edit build prop to get rid of status errors.
http://forum.xda-developers.com/showpost.php?p=24266658&postcount=471
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Phalanx7621 said:
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
Click to expand...
Click to collapse
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
aspen1135 said:
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
Click to expand...
Click to collapse
Cause I'm trying right now. Wish me luck I'll report after I'm done with excessive flashing
RatusNatus said:
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
MotoMudder77 said:
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
Click to expand...
Click to collapse
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
gregsarg said:
Unsupported CWM image ...
Your CWM or TWRP is not compatible with your rom...
Flash the CWM from the "everything " thread ...
Then try again ....it seems this version is the most stable ....IMHO
Edit :
It's non touch ...but it's rock solid ...g
Click to expand...
Click to collapse
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
RatusNatus said:
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
Click to expand...
Click to collapse
This problem has been occurring for a long time now. And has nothing to do with your version of cwm. It has to do with the script IN THE ROM YOU ARE FLASHING. If it has the script in the rom to check what phone model u have, and it detects something other than what it should, it basically says "hey! This guy doesn't have our phone! Stopppp!" And won't let u flash. Status 7 error. To fix this, either manually remove the script that checks for this in the rom yer flashing, modify the build.prop in the rom yer currently ON to reflect the model number of the rom u want to flash, or flash another rom that already has this script checking removed to get your build.prop to reflect the new model number u want it to show. Either way none of it has to do with your version of cwm.
Sent from my SGH-I777 using Tapatalk 2
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...and thanks for unresume my resume.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
You had a different issue then. most likely just a corrupt recovery. as there are NO problems flashing from one version of CWM to the next.
The common status 7 error, is caused by the updater.script searching the build.prop. as stated a million times in almost every thread.
hello fellow xdas
while back i had gotten my hands dirty with the CM10 project as i just couldn't wait for the official update! i learned quickly that i had serious problems with antenna/reception. i tried carious base bands (as recommended on forums) using GetRil/flash.Odin. this didnt seem to help, even though i would get better reception, my signal was unstable. In the process i tried other roms like JellyBam and had the same issue.
As this is my main phone and i do actually need to call with it, i went back to the stock rom i downloaded. but surprisingly i still have the same issue! GetRil also shows that i have incompatible RIL/baseband. this is what it shows:
RIL: I9100NELP2; I9100XXKI4
Baseband: I9100XXLPQ
FYI: i am located in the Netherlands and use T-mobile network.
so have i installed the wrong ROM or done something wrong in the process... ? does anyone have any experience with this? i much rather have CM10 but only if i can get to call normally once again?
thanks
ozeeo said:
hello fellow xdas
while back i had gotten my hands dirty with the CM10 project as i just couldn't wait for the official update! i learned quickly that i had serious problems with antenna/reception. i tried carious base bands (as recommended on forums) using GetRil/flash.Odin. this didnt seem to help, even though i would get better reception, my signal was unstable. In the process i tried other roms like JellyBam and had the same issue.
As this is my main phone and i do actually need to call with it, i went back to the stock rom i downloaded. but surprisingly i still have the same issue! GetRil also shows that i have incompatible RIL/baseband. this is what it shows:
RIL: I9100NELP2; I9100XXKI4
Baseband: I9100XXLPQ
FYI: i am located in the Netherlands and use T-mobile network.
so have i installed the wrong ROM or done something wrong in the process... ? does anyone have any experience with this? i much rather have CM10 but only if i can get to call normally once again?
thanks
Click to expand...
Click to collapse
Use either of the 2 links below to download either the NELP2 modem of the XXKI4 modem, and them flash them onto your phone via Recovery Mode. That should resolved your incompatible RIL issue.
[REF] Modem+RIL CWM Installers
[REF] Galaxy S 2 Shipped Modem Collection
---------- Post added at 11:55 AM ---------- Previous post was at 11:46 AM ----------
OR .... use the link below to find and reflash the entire correct firmware for your region, which should flash the correct modem and RIL along with it.
[ROM+Guide] Official i9100 Firmwares LPE/Q/7/2/F/S/4/7/G/9/W/D/F Download
zee54 said:
Use either of the 2 links below to download either the NELP2 modem of the XXKI4 modem, and them flash them onto your phone via Recovery Mode. That should resolved your incompatible RIL issue.
[REF] Modem+RIL CWM Installers
[REF] Galaxy S 2 Shipped Modem Collection
---------- Post added at 11:55 AM ---------- Previous post was at 11:46 AM ----------
OR .... use the link below to find and reflash the entire correct firmware for your region, which should flash the correct modem and RIL along with it.
[ROM+Guide] Official i9100 Firmwares LPE/Q/7/2/F/S/4/7/G/9/W/D/F Download
Click to expand...
Click to collapse
thanks a lot zee54,
can i just go back to my CM10 or JellyBam, install the above mentioned radios and get everything working? or does it depend on the RIL which that ROM is running! I have tried a number of modems when i had CM10, but dont know if i tried those... i did try BVLP7 for sure
Based on this forum right here i need to have the I9100BOLPD ROM as stock for Netherlands T Mobile!
ozeeo said:
thanks a lot zee54,
can i just go back to my CM10 or JellyBam, install the above mentioned radios and get everything working? or does it depend on the RIL which that ROM is running! I have tried a number of modems when i had CM10, but dont know if i tried those... i did try BVLP7 for sure
Based on this forum right here i need to have the I9100BOLPD ROM as stock for Netherlands T Mobile!
Click to expand...
Click to collapse
The modem is independent of the ROM, mate. So it wont make much of a difference whether you install the radio on stock firmware or on CM10. You could try using the modems mentioned by zee54 with CM10 and seeing if it helps. Also, give it about a day or so..since the phone tends to take a while to get 'used' to a new modem.
ozeeo said:
thanks a lot zee54,
can i just go back to my CM10 or JellyBam, install the above mentioned radios and get everything working? or does it depend on the RIL which that ROM is running! I have tried a number of modems when i had CM10, but dont know if i tried those... i did try BVLP7 for sure
Based on this forum right here i need to have the I9100BOLPD ROM as stock for Netherlands T Mobile!
Click to expand...
Click to collapse
The unstable signal or "RIL Crash" as it it called isn't actually caused by having an incompatible RIL and Baseband (modem). It is a more complicated issue which I don't fully understand myself. But what I do know is that it currently affects all customs roms that are based on CM10 and use the CM Kernel. So switching modems might help recude the frequency of the problem but probably won't irradicate it completely.
You should not experiencing this problem if you go back to stock samsung firmware. If you experience problems you might want to do a full wipe (Data, Cache, Dalvic-cache) before reflashing and fix permissions afterwards.
On a more positive note, I have found that using the Siyah Kernel with your custom rom does seem to eliminate this problem, or at least reduce it occurance to such that I have not noticed it happening.
So personally i would suggest that if you wish to go back to CM10 or JellyBam ROMs, then do so but also install the latest Siyah Kernel for the S2 from here http://www.gokhanmoral.com/
(Here's the XDA Thread for the Siyah Kernel - [KERNEL] SiyahKernel v4.1.5 (v5.0a2))
I am currently running CM10 with the Siyah Kernel v5.0b2 and it is working very nicely
great stuff guys... 2x thanks for both of you!
Zeey54, i just had Siyah v5 Kernal installed, installing the latest JellyBam right now! so lets see what happens. i was suspecting that beside the RIL/baseband there were other factors as i did not see any significant difference between them. but then again i dont trust my judgement on such issues as my knowledge is quite limited.
will send an update with the result after installation in a few min.
ozeeo said:
great stuff guys... 2x thanks for both of you!
Zeey54, i just had Siyah v5 Kernal installed, installing the latest JellyBam right now! so lets see what happens. i was suspecting that beside the RIL/baseband there were other factors as i did not see any significant difference between them. but then again i dont trust my judgement on such issues as my knowledge is quite limited.
will send an update with the result after installation in a few min.
Click to expand...
Click to collapse
Good luck mate. I hope it all goes well
zee54 said:
Good luck mate. I hope it all goes well
Click to expand...
Click to collapse
installed the BOLP7 modem, overall reception is much better! data connectivity is also better and faster. but i still have some periods which my receptions drops and goes back up, seems like radio/modem crash (if im right). dont know if that is due to the kernel or modem or ...?
the reason i went for BOLP7 modem was because the latest official stock rom from t-mobile Netherlands was I9100BOLPM_I9100TNLLP8_I9100BOLP7, so i thought that would be the best one to try!
will wait a little more to see if this improves as the modem settles.
4th official ROM too much coverage you please make a review ?
need modem
First of all, thank you mate for your hardwork and awesome utility.
I have a Samsung galaxy S2 I9100G , recently flashed jelly bam custom rom. I am based in Saudi Arabia, the reception is not clear and people complain that it is switched off or out of network. I tried calling with another mobile and i got a response that my mobile is switched off, at the same time i checked my S2 mobile , it shows the full signal of the network in status bar.
what should i do? Which modem should i flash. the getRIL shows RIL/baseband is matching (I9100GDDLP5).
cheers
Rizwan
First off, hello guys and girls, a long time forum crawler but i've only just bit the bullet and registered
Recently picked myself up an SIII (i9300) rooted up and decided to go with Omega, but i've found that whenever i flash a kernel, all will go ahead as normal, flashes fine and i reboot, to be left with a black screen and some varying vibration patterns depending on the kernel flashed... I've tried Perseus (the main one i'd like to see working) aswell as siyah, but neither chose to boot.
Both specified to work on samsung based roms, and i'm not on 4.2.2 (only 4.2.1) so that isn't the problem... So here i am; Where am i going wrong?
Thank you ahead of time
are you sure you've got a i9300?
Glebun said:
are you sure you've got a i9300?
Click to expand...
Click to collapse
Absolutely positive, any idea's?
Ailio said:
Absolutely positive, any idea's?
Click to expand...
Click to collapse
im pretty sure it doesnt work with the samsung 4.2 roms. if you flash 4.1.2 it will work.
Drew071
---------- Post added at 01:55 PM ---------- Previous post was at 01:41 PM ----------
drew071 said:
im pretty sure it doesnt work with the samsung 4.2 roms. if you flash 4.1.2 it will work.
Drew071
Click to expand...
Click to collapse
if you look on the perseus thread it states it does not work on 4.2.2 samsung roms. There arent any 4.2.2 sammy roms so im pretty sure its meant to say 4.2.1 and the OP mistyped.
drew071
yeah, missed that. most kernels don't support 4.2