Well. I had my SII a long time ago, but luckily my chip was sane and I had exactly the right software version as the newest philz kernel. This time I got my friend's phone who asked me to put cm11 in it. Unfortunately his chip is insane as well there is no version matching to philz kernel's versions at all. He has XXMS7. The closest version of philz I see is XXMS1 but I'm not entirely sure if it's close enough to use it safely(especially with insane chip in the phone).
Any advices or soultions? Need help a lot.
T4underbolt said:
Well. I had my SII a long time ago, but luckily my chip was sane and I had exactly the right software version as the newest philz kernel. This time I got my friend's phone who asked me to put cm11 in it. Unfortunately his chip is insane as well there is no version matching to philz kernel's versions at all. He has XXMS7. The closest version of philz I see is XXMS1 but I'm not entirely sure if it's close enough to use it safely(especially with insane chip in the phone).
Any advices or soultions? Need help a lot.
Click to expand...
Click to collapse
First, no need to worry about the chip. There are chips that proved to be dangerous in relation to trim, which your friend has. AFAIK there are no other concerns with the chip.
I have never tried to root my phone with another kernel, but I'm pretty sure that one would be fine.(In the philz thread, he says most XW and XX kernels are interchangeable) If you are only trying to install CM11, I think you can just flash that kernel, then just reboot straight to recovery. Make sure you have a "kitkat compatible" recovery to flash from the xxms1 recovery, reboot to recovery again, then flash CM11 and gapps etc. This is what I would do. And if you have issues, you can always flash the stock rom again with odin
noppy22 said:
First, no need to worry about the chip. There are chips that proved to be dangerous in relation to trim, which your friend has. AFAIK there are no other concerns with the chip.
I have never tried to root my phone with another kernel, but I'm pretty sure that one would be fine.(In the philz thread, he says most XW and XX kernels are interchangeable) If you are only trying to install CM11, I think you can just flash that kernel, then just reboot straight to recovery. Make sure you have a "kitkat compatible" recovery to flash from the xxms1 recovery, reboot to recovery again, then flash CM11 and gapps etc. This is what I would do. And if you have issues, you can always flash the stock rom again with odin
Click to expand...
Click to collapse
Thanks for the feedback. I'll try to do that.
Related
Getting a bit confused about all this, so am wondering if i've got it right. A rom is the whole thing, it includes a kernel and so forth? So a Kernel is a part of the rom right? And you can flash kernels individually without flashing a whole new rom? But what is a firmware then? Just another name of a rom?
Also on the Galaxy S2 can you flash custom roms, like Lite'ning, without getting root first? Or do you need to get root before flashing custom roms? If you can flash custom roms first without rooting, will the custom rom then give you root as long as it includes it?
And you also got recovery, which is a separate thing again? Galaxy S2 comes with a very basic one if i've understood correctly, but there is others out there that you can install, which also gives you the ability of flashing roms straight from the microsd/phone storage?
So have i gotten any of this? Hope am not to far off
Edit: http://forum.xda-developers.com/showthread.php?t=1246131 looks like most of my questions where answered there, though am still a bit unsure if it's possible to flash a custom rom before you root?
ROM's and FIRMWARE: The ROM or Read Only Memory is the internal flash memory where the core operating system resides. The Firmware is a device specific part of the ROM that controls various hardware components. So the firmware is contained in the ROM but in the context of Android the terms are often used interchangeably.
KERNELS: Different kernels offer different advantages, some are fast, some are light weight on the battery and some are a mix, so yes you can in most cases flash a different kernel with a ROM, and then your phone will be running the custom ROM you picked with the new kernel you flashed.
Rooting: You must have a rooted phone inorder to flash a custom rom, but rooting in my opinion seems really safe and it really easy to do on the SG2
There are things that allow you to flash from your SD card and you do that by entering clockworkmod revovery, apps like rom manager also allow you to flash from sd card, but you can always use odin, which is safe and fast
hope this helps
Thanks, and very nicely explained =) Another question then, what is the reason one need root before you can flash custom firmwares? As i heard Galaxy S2 doesn't really have any safety measures put in to stop things, like HTC do with their bootloader. Another thing is that i checked the thread for the Lite'ning rom, and saw the installation procedure, and it doesn't mention anything about having root before starting, so am getting a bit confused there.
You don't need to root before flashing a custom ROM as long as you can enter download mode (power up with volume down, home and power button pressed) and can flash the ROM via Odin.
If the ROM is flashable only via ClockWorkMod recovery (a zip that you copy on your phone) then you need to flash something that includes that recovery before flashing the rom (like CF-Root or any kernel that includes CWM).
Lite'ning ROM that you mentioned earlier is flashable via Odin so no problem.
Every ROM includes a Kernel, the only thing they sometimes don't include is the modem like in VillainROM, you have to flash it separately. And also, if a ROM is announced as rooted, when you flash it, you will have root regardless of the state before flashing
Thanks once again =)
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Nitrius said:
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Click to expand...
Click to collapse
Yes it will revert back everything
Nitrius said:
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Click to expand...
Click to collapse
If you dont flash a modem it will just use the one you had before. They talk about it in the old thread and also in the new but not in the firsts posts, you'll have to do a search.
Plus Modem Kernels are interchangeable .
KH3 Firmware with KI4 modem and KH1 kernel .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
jje
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
On S2, cwm can be flashed without a kernel
Kernels based on stock and that only include cwm and root are affected if not specifically patched
Sent from my GT-I9100 using Tapatalk 2
donalgodon said:
I've read all the info I could find here on the brickbug regarding the CWM recovery and the 4.0.4 leaks, but one question that still perplexes me is:
Why does the ROM itself have anything to do with this issue if the flags from the kernel are what triggers the bad erase command in the first place?
I mean, at this point, the ROM isn't even loaded, is it, so why does it matter if we use a custom recovery, say from Siyah, for example, on a leaked ROM, since the CWM recovery is part of the kernel and not the ROM itself?
What am I missing?
Click to expand...
Click to collapse
Your missing nothing actually, you are totally right in the fact its the kernel itself, but since the kernel is part of the rom, when you flash with odin, that is the reason the warnings are about...
so the best thing is actually just avoid the specific roms, and have a known good kernel...
FWX
Hello!
A softbricked i9100 just fell on my lap for me to try and fix. I have access to CWM 5.0 and I believe it had a MIUI ROM before it was softbricked, probably installed around 2011. It has all the signs of a bad USB port, so no ODIN for now (I have ordered a spare part). Also, let's assume it has the insane chip.
Since I don't know a whole lot in terms of flashing, etc, I have been reading the tutorials. However, I would greatly appreciate any input/advice on my options.
What I want to do is to make it as stock as possible until the spare part comes. I was thinking of flashing something through CWM to make it stable and ready for a future JB stock flash when the USB is up and running again. However, I'm a bit scared of flashing stuff without knowing what I'm doing. Can anyone point me in the right direction for the proper kernel and rom to flash, considering all of this?
Many thanks!
Download proper stock rom and flash it via mobile odin.
grisoxxl said:
Download proper stock rom and flash it via mobile odin.
Click to expand...
Click to collapse
It's softbricked, so I can ony access CWM.
EDIT: I'm concerned about just putting any ROM through CWM, since I don't know what kernel is in it. This might be a stupid question, but can a ROM be incompatible with a kernel to the point where it hardbricks it?
Sorry for bad post.
If you already sortbricked try first install custom kernel like syiah after that instlall rom compatible with that kernel.
Keep getting install failed /system and /data. No os found
what ROM are you trying to install? how did you install TWRP?
by the way, the way it works on this phone is that the recovery is packaged with a kernel. whatever the kernel has, you're stuck with. unless you flash a kernel that has an alternative recovery (example: one of hhp's Devil TWRP kernels) you can't just flash a recovery. so maybe you have a bad flash if you tried doing that.
Also you need to quit spamming every spot in the fascinate fourms.
there are only maybe a dozen of us real active, we can read your posts.
I've explained over and over the process,
Keep on reading, reading and then read some more.
Very thankful for all the help
hhp_211 said:
Also you need to quit spamming every spot in the fascinate fourms.
there are only maybe a dozen of us real active, we can read your posts.
I've explained over and over the process,
Keep on reading, reading and then read some more.
Click to expand...
Click to collapse
sorry i was getting desprate. I apologizes.
is their a radio that can boost the 3g reception? (besides the one's in the guide)
that cm-11 rom runs super. i installed JB then the cm-11.
have a question about kernels but going to read up first about them,
Sorry for the spamming.
Thanks for the help btw
skepticmisfit said:
what ROM are you trying to install? how did you install TWRP?
by the way, the way it works on this phone is that the recovery is packaged with a kernel. whatever the kernel has, you're stuck with. unless you flash a kernel that has an alternative recovery (example: one of hhp's Devil TWRP kernels) you can't just flash a recovery. so maybe you have a bad flash if you tried doing that.
Click to expand...
Click to collapse
I was trying to install pa_fascinatemtd-4.2-BETA1-20140318.
i tried to install TWRP through CWM. But when i used ROM manager to select recovery 3.x and it detected TWRP. i installed JB from avatar then flashed cm-11-20140221-UNOFFICIAL-fascinatemtd and PA__Gapps after factory/reset and dalvik wipe. but the menu was from cwm4_fixed_for_cm7-ODIN even though ROM Manager said TWRP recovery
right now running
Android 4.4.2
Band EH3
Kernel version 3.0.101-ge40c0be don't know which kind it is. don't know if it install from CM-11 or the avatar rom i first installed.
doing research on kernels and radio to see if there is a radio that can boost 3g connction
jgmedina said:
doing research on kernels and radio to see if there is a radio that can boost 3g connction
Click to expand...
Click to collapse
there are a few radios for the fascinate. the gingerbread radios are EH03 (the one you have right now from the official VZW OTA, i use this one and am ok with it), EC09 (from an old gingerbread leak, some people prefer this radio over the others). i know there's other radios but the only older one you should probably use is ED05 from an old Froyo OTA.
thanks. this upgrade help alot though. have to test yuoube app.also was having issue with that too.
I've beeing trying to change my ROM. I'm trying to install Clockworks recovery and it doesn't work. I've tried using Rom Manager, EZ recovery and doing it manually. Each time it just goes into the default recovery. I've also tried twrp. Any help?
GT-I9200T
Andriod version: 4.1.2
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
MistahBungle said:
I assume you mean you have an I9100T ?
1) The reason your recovery isn't sticking after you reboot is because recovery is 'baked' into the kernel on the I9100, so any recovery flashed independently will only persist until the next reboot.
2) Do not use Rom Manager with the I9100. At all. Ever.. Eventually, it will break recovery & cause your phone to reboot. The only fix is to flash stock via Odin & do a factory reset. And as most people here don't make regular backup, it sucks to be you in this situation because you lose your data.
3) Easiest way to get CWM that will stick is to flash a custom kernel; you have several options, a search will reveal your choices (PhilZ seems to be what many people use these days for simplicity's sake). From there you can then flash whatever custom rom (or kernel) you want.
If you don't have an I9100, clarify exactly what you have & we'll organise mods to move your thread.
Click to expand...
Click to collapse
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Also what about Rom Toolbox? Will that be bad aswell?
AcademyA said:
Sorry, I've got a 19100T. My bad. As for losing data I don't mind, I've got my contacts backed up and that's all I need. It seems PhiZ is only for Galaxy S4's. :crying:
Click to expand...
Click to collapse
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
MistahBungle said:
No, PhilZ is not only for Galaxy S4's. The S4 version is a recovery only, as the partition layout on the I95x phones is different (kernel & recovery are separate). PhilZ for the I9100 is a kernel with recovery built into it.
You should be able to find the thread easily; I found it in 2.3 seconds with a Google search 'I9100 PhilZ XDA' at top of results. As to which file to use, you need to take the time to read the thread to work that out for yourself. Failure to read/learn before doing leads to busted phones.
Click to expand...
Click to collapse
When finding the Kernel code, I type in getprop in terminal. I see stuff like the build number but I can't find the Kernel code anywhere. The only thing I see that is related to Kernel is ro.kernel.qemu: [0]
What are you doing in terminal ? You're overthinking this. I realise it's in the thread, but that's completely unnecessary nonsense
Phone settings/about device - build number.
My final post to this thread. You're on your own.
Alright! Everything's working now. Thanks for the help.