Related
Hi,
quite a noob here, I red http://forum.xda-developers.com/showthread.php?t=1313659
because I need a warranty replacement.
I would like to go to I9100XWLPT_I9100XEULPA_XEU
What about the brick bug ? What about the bootloader ?
Quite lost here.
Thank you
hubertes said:
Hi,
quite a noob here, I red http://forum.xda-developers.com/showthread.php?t=1313659
because I need a warranty replacement.
I would like to go to I9100XWLPT_I9100XEULPA_XEU
What about the brick bug ? What about the bootloader ?
Quite lost here.
Thank you
Click to expand...
Click to collapse
Gingerbread bootloader will work for ICS Roms.
-once you upgrade to 4.0.4 Note that:
If you are going to mess with your phone ,Just flash a custom kernel like Siyah, speedmod, Dorimanx, Dream at once, if you have plans to root your phone.
- If you are going to stay without ROOT, then you are safe, there it's no need to worry about the brick bug.
Why?
-Because stock ICS 4.0.4 kernel has a brick bug enabled on it.
-This bug is also present on all kernels based on stock 4.0.4 kernel. CF-ROOT (maybe) and all insecure kernels fall into this category
What will happen?
-If after rooting your phone after upgrading to 4.0.4, and you wipe your phone or try ROM backup while running stock/stock based kernels then say goodbye to your phone.
Swyped from Samsung Galaxy SII
Thanks !
Jokesy said:
Gingerbread bootloader will work for ICS Roms.
-once you upgrade to 4.0.4 Note that:
If you are going to mess with your phone ,Just flash a custom kernel like Siyah, speedmod, Dorimanx, Dream at once, if you have plans to root your phone.
- If you are going to stay without ROOT, then you are safe, there it's no need to worry about the brick bug.
Why?
-Because stock ICS 4.0.4 kernel has a brick bug enabled on it.
-This bug is also present on all kernels based on stock 4.0.4 kernel. CF-ROOT (maybe) and all insecure kernels fall into this category
What will happen?
-If after rooting your phone after upgrading to 4.0.4, and you wipe your phone or try ROM backup while running stock/stock based kernels then say goodbye to your phone.
Swyped from Samsung Galaxy SII
Click to expand...
Click to collapse
So better stay with a 4.0.3 stock rom ?
From Revo HD6, is there a specific operation to chnage kernel/bootloader ?
Can I root the phone for 2 or 3 days and unroot, so thaht the warranty department get a clean SGS2 (have a jig)
thanks again
hubertes said:
Thanks !
So better stay with a 4.0.3 stock rom ?
From Revo HD6, is there a specific operation to chnage kernel/bootloader ?
Can I root the phone for 2 or 3 days and unroot, so thaht the warranty department get a clean SGS2 (have a jig)
thanks again
Click to expand...
Click to collapse
1. If you don't want to change your kernel, then stay with 4.0.3 (LPG or UHLPS), however 4.0.4 is the most stable ICS version.
2. When you flash a new ROM, tor kernel will be changed.
Manually Changing kernel is very easy especially, when you root your phone
3. Rooting ICS is the easiest thing on earth, much easier than gingerbread.
4. UNrooting is even easier than rooting.
5. There is no need for you to change your bootloader, except you are looking for something else
Swyped from Samsung Galaxy SII
thanks again
Jokesy said:
1. If you don't want to change your kernel, then stay with 4.0.3 (LPG or UHLPS), however 4.0.4 is the most stable ICS version.
2. When you flash a new ROM, tor kernel will be changed.
Manually Changing kernel is very easy especially, when you root your phone
3. Rooting ICS is the easiest thing on earth, much easier than gingerbread.
4. UNrooting is even easier than rooting.
5. There is no need for you to change your bootloader, except you are looking for something else
Swyped from Samsung Galaxy SII
Click to expand...
Click to collapse
1. OK. i'll go on 4.0.4 after the rma
2. Just want to be sure that the kernel will be "stock" as well for rma
3.4. Just need titanium for 4 or 5 days. here the procedure ? : techclap.com/9754/root-unroot-samsung-galaxy-sii-stock-android-4-ics-firmware/ ? Or just flash the stock rom again to unroot ?
5. Ok
hubertes said:
thanks again
1. OK. i'll go on 4.0.4 after the rma
2. Just wabnt to be sure that the kernel will be "stock" as well for rma
3.4. Just need titanium for 4 or 5 days. here the procedure ? : techclap.com/9754/root-unroot-samsung-galaxy-sii-stock-android-4-ics-firmware/ ? Or just flash the stock rom again to unroot ?
5. Ok
Click to expand...
Click to collapse
You can use that method to UNROOT too or just reflash stock kernel again.
Swyped from Samsung Galaxy SII
Hi S2 user, :angel:
I will buy a new S2 phone soon. I need a little help from you guys. I need to know something about S2 :laugh:
My old phone is Xperia Arc S. This phone need following step to flash kernel and rom.
Kernel:
For flash a new kernel, I need to unlocked the bootloader first. Then this phone can flash any kernel anytime. But unlocking the bootloader will void the warranty.
Rom:
For flash a new rom, as long as the rom does not need to have specific kernel, in other word, stock based rom, no unlocked bootloader required. Just install the CWM and flash the rom.
How about S2 guys? Do I need to unlock something before flash kernel and rom? Can someone explain clearly or likes how I explain my old phone.
p/s- i read in some thread, doing a factory reset in cwm will make S2 brick? hard brick? can't even power on the phone. OMG is it true?
its very scary because in Xperia Arc S, i always flash a new rom. flasholic
I don't want my new S2 brick
I hope you guys can help me. Thanks
faiz5200 said:
Hi S2 user, :angel:
I will buy a new S2 phone soon. I need a little help from you guys. I need to know something about S2 :laugh:
My old phone is Xperia Arc S. This phone need following step to flash kernel and rom.
Kernel:
For flash a new kernel, I need to unlocked the bootloader first. Then this phone can flash any kernel anytime. But unlocking the bootloader will void the warranty.
Rom:
For flash a new rom, as long as the rom does not need to have specific kernel, in other word, stock based rom, no unlocked bootloader required. Just install the CWM and flash the rom.
How about S2 guys? Do I need to unlock something before flash kernel and rom? Can someone explain clearly or likes how I explain my old phone.
p/s- i read in some thread, doing a factory reset in cwm will make S2 brick? hard brick? can't even power on the phone. OMG is it true?
its very scary because in Xperia Arc S, i always flash a new rom. flasholic
I don't want my new S2 brick
I hope you guys can help me. Thanks
Click to expand...
Click to collapse
You don't have to unlock. Just download Odin and flash all the ROMs/kernels you want. As for the cwm brick bug, your phone will only brick if you factory reset through CWM in 4.0.4. In other versions you should be fine.
Sent from my GT-I9100 using xda app-developers app
S2 is the best phone to flash No problem with bootloader lock, you download Odin und happy flashing
Gesendet von meinem GT-I9100 mit Tapatalk 2
preseodymium said:
You don't have to unlock. Just download Odin and flash all the ROMs/kernels you want. As for the cwm brick bug, your phone will only brick if you factory reset through CWM in 4.0.4. In other versions you should be fine.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
faiz5200 said:
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
Click to expand...
Click to collapse
I am currently installing 4.1.2, unofficial of course
The brick Bug problem by 4.0.4 only with Stock Kernel ! when you have 4.0.4 on your phone you flash a save Kernel (Siyah, Dorimanax .....) with Odin (only Odin not Cwm )
and it was save .After you can flash wath you want
smooth 123 said:
The brick Bug problem by 4.0.4 only with Stock Kernel ! when you have 4.0.4 on your phone you flash a save Kernel (Siyah, Dorimanax .....) with Odin (only Odin not Cwm )
and it was save .After you can flash wath you want
Click to expand...
Click to collapse
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
faiz5200 said:
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
Click to expand...
Click to collapse
enjoy ur s2, i just got the s2 and flash over 20 roms like crazy!! jajaja is very good phone
faiz5200 said:
I see. So the brick bug actually come from the kernel inside firmware 4.0.4. Not the entire 4.0.4 firmware. Is other custom kernel likes you mention (Siyah, ..) is 100% safe?
Click to expand...
Click to collapse
100% safe! Her is ohter 100% safe Kernel http://forum.xda-developers.com/showthread.php?t=1877270
for 4.0.4 Stock In this thread you found more to the theme brick bug.
I flash my S2 i don t know:victory: 100× no Problem S2 likes flashing
faiz5200 said:
Thanks for your reply. For the brick bug, how come I want to factory reset when flashing new rom? And I think latest firmware for S2 is 4.0.4. Correct me if im wrong.
Click to expand...
Click to collapse
You factory reset when installing ROMs to make sure there are no errors. Plus with siyah kernels, you can't be 100% sure your phone won't brick when factory reset in CWM. Best is to flash 4.0.3 before doing anything else.
Sent from my GT-I9100 using xda app-developers app
Rooting
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
faiz5200 said:
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
Click to expand...
Click to collapse
I'm not sure about CF root though. Although the ROM I am in now has built in kernels, I still think its best to root first as some ROMs may not have the built in kernel (never searched other ROMs not entirely sure). I might recomment siyah kernel though
Sent from my GT-I9100 using xda app-developers app
preseodymium said:
I'm not sure about CF root though. Although the ROM I am in now has built in kernels, I still think its best to root first as some ROMs may not have the built in kernel (never searched other ROMs not entirely sure). I might recomment siyah kernel though
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
uhh.. So root is come from kernel? Ermm.. so it different than xperia. So if I flash siyah kernel, I do not need to root?
faiz5200 said:
Guys.. 1 more question.
When I get my S2, I plan to flash custom rom like aosp or aokp but not stock rom.
Do I need to root my S2 first before flash any rom? Because my Xperia Arc S, I do not need to root because root come inside with the custom rom zip. So when I flash a new rom, my Xperia automatically root. No need to do other step.
I'm curious about this because I see in some thread, talking about cf root or something like that. The thread is very updated. Looks like it very necessary to do it at least once to have root before flash any custom rom.
Please explain for me about this root. Thanks guys.
Click to expand...
Click to collapse
Some people want to simple root their phone and don't care too much for custom roms and stuff. So for such people, they can simply root their phone using one of the many rooting methods mentioned.
However, if your primary aim is to install a custom rom/ kernel, you can use Odin to flash a custom kernel on your phone. (like siyah, dorimanx, Philz, the list goes on..) and you'll have root. Thereafter you can install a custom rom compatible with the kernel. Earlier on it was simple. Flash siyah or dorimanx and any custom rom will work on it. Kinda like a 'one size fits all' deal. However, right now with new mali drivers etc, some versions of a kernel are reqd based on which rom you plan to install. (JB with new mali drivers or JB without those new mali drivers/ICS)
CF-Root is the method I'd used..but right now it's not recommended, since if you're on certain 4.0.4 firmware, that is susceptible to the emmc brickbug I'm sure you've read about. Siyah, dori, etc kernels are safe.
HAXTREME said:
Some people want to simple root their phone and don't care too much for custom roms and stuff. So for such people, they can simply root their phone using one of the many rooting methods mentioned.
However, if your primary aim is to install a custom rom/ kernel, you can use Odin to flash a custom kernel on your phone. (like siyah, dorimanx, Philz, the list goes on..) and you'll have root. Thereafter you can install a custom rom compatible with the kernel. Earlier on it was simple. Flash siyah or dorimanx and any custom rom will work on it. Kinda like a 'one size fits all' deal. However, right now with new mali drivers etc, some versions of a kernel are reqd based on which rom you plan to install. (JB with new mali drivers or JB without those new mali drivers/ICS)
CF-Root is the method I'd used..but right now it's not recommended, since if you're on certain 4.0.4 firmware, that is susceptible to the emmc brickbug I'm sure you've read about. Siyah, dori, etc kernels are safe.
Click to expand...
Click to collapse
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
faiz5200 said:
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
Click to expand...
Click to collapse
For S2 we can. Because it won't increase your flash counter. But I never tried flashing through CWM.
Sent from my GT-I9100 using xda app-developers app
faiz5200 said:
I see. Thanks. Flash kernel using odin. I see in this thread http://forum.xda-developers.com/showthread.php?t=1125282 , he said flashing a kernel is same like flashing a custom rom which is in CWM. Flash kernel in CWM? I thought the only way is using odin.
Click to expand...
Click to collapse
There are two ways of flashing a kernel.
1. Use the .tar version of the kernel and flash via Odin
(the same way you'd flash the cf-root kernel you'd mentioned in a post above. I'll assume you know the steps as they're mentioned in chainfire's post. Or there are many posts on that topic)
Advantages: tried and tested route, simple one step method. You're rooted and have a custom kernel in about 30 secs.
Disadvantage: You rely on Odin and the connection to your computer which some don't trust. Increases flash counter.
2. Use the .zip version of the kernel and flash via CWM.
Since in this case you need CWM to start off with, you can use Rachmat3's method described HERE to get temporary CWM first.
Advantages: No computer needed. Everything happens through your phone. Flash counter isnt increased.
Disadvantages: Can be a little finicky at times..but you'll get there eventually. Involves 2 steps. First get temporary CWM, then install custom kernel via cwm.
You can start off with a very popular kernel. Gokhanmoral's siyah kernel.Both the zip and tar versions are available downloadable from HERE
HAXTREME said:
There are two ways of flashing a kernel.
1. Use the .tar version of the kernel and flash via Odin
(the same way you'd flash the cf-root kernel you'd mentioned in a post above. I'll assume you know the steps as they're mentioned in chainfire's post. Or there are many posts on that topic)
Advantages: tried and tested route, simple one step method. You're rooted and have a custom kernel in about 30 secs.
Disadvantage: You rely on Odin and the connection to your computer which some don't trust. Increases flash counter.
2. Use the .zip version of the kernel and flash via CWM.
Since in this case you need CWM to start off with, you can use Rachmat3's method described HERE to get temporary CWM first.
Advantages: No computer needed. Everything happens through your phone. Flash counter isnt increased.
Disadvantages: Can be a little finicky at times..but you'll get there eventually. Involves 2 steps. First get temporary CWM, then install custom kernel via cwm.
You can start off with a very popular kernel. Gokhanmoral's siyah kernel.Both the zip and tar versions are available downloadable from HERE
Click to expand...
Click to collapse
Another disadvantage of "not using" odin is when you cant enter cwm.
I use cwm and mobile odin.I flashed a kernel and couldnt access cwm nor phone would boot.
So I had to fix it using my pc via odin.
I've always used custom roms on my galaxy. I was even using in dual-boot, a Jelly Bean Revolt and other stock. I was testing a new stock, and flashed it with Odin Mobile. I ended up losing custom. Since then, I can no longer flashing custom roms, even having problems flashing a new kernel. I use the CWM, do the wipes and flash the* rom, but after the reboot, it starts a boot loop with the galaxy s2 logo. The phone is inoperable. At least the download mode works, and I ended up going back to stock a few times. I even tried and flash another custom roms, but the same problem happens.
Anyone know how to help??
gu_cad said:
I've always used custom roms on my galaxy. I was even using in dual-boot, a Jelly Bean Revolt and other stock. I was testing a new stock, and flashed it with Odin Mobile. I ended up losing custom. Since then, I can no longer flashing custom roms, even having problems flashing a new kernel. I use the CWM, do the wipes and flash the* rom, but after the reboot, it starts a boot loop with the galaxy s2 logo. The phone is inoperable. At least the download mode works, and I ended up going back to stock a few times. I even tried and flash another custom roms, but the same problem happens.
Anyone know how to help??
Click to expand...
Click to collapse
Flash a 3-parted stock firmware and activae "re-partition" in Odin.
After this flash a rooted kernel .tar (cf-root, speedmod, etc.) via Odin.
Now start flashing again.
Hope this works.
CHEERS
Hannibal226 said:
Flash a 3-parted stock firmware and activae "re-partition" in Odin.
After this flash a rooted kernel .tar (cf-root, speedmod, etc.) via Odin.
Now start flashing again.
Hope this works.
CHEERS
Click to expand...
Click to collapse
I've read about emmc brick. And this problem started after using a LQ6 4.0.4 stock rom.
I even used the "emmc brick check", and it shows "YES. Insane chip".
I flashed now a 2.3.6 stock rom. But i haven't tried to flash another custom rom yet.
Should i proceed as you say???
And sorry for my noobness, but what is a 3 parted stock rom?
gu_cad said:
I've read about emmc brick. And this problem started after using a LQ6 4.0.4 stock rom.
I even used the "emmc brick check", and it shows "YES. Insane chip".
I flashed now a 2.3.6 stock rom. But i haven't tried to flash another custom rom yet.
Should i proceed as you say???
And sorry for my noobness, but what is a 3 parted stock rom?
Click to expand...
Click to collapse
it contains a .pit file for re-partition and 2 other files,but u should be carefull in using the .pit file though, since it could potentially hardbrick ur device ma8
instead try updating ur device from GB 2.3.6 to a stock v4.0.3(do not flash any 4.0.4 ICS firmware) ICS firmware either thro 'KIES' or 'ODIN', then root ur phone and try installing a custom ICS rom of ur choice and see
Sun90 said:
it contains a .pit file for re-partition and 2 other files,but u should be carefull in using the .pit file though, since it could potentially hardbrick ur device ma8
instead try updating ur device from GB 2.3.6 to a stock v4.0.3(do not flash any 4.0.4 ICS firmware) ICS firmware either thro 'KIES' or 'ODIN', then root ur phone and try installing a custom ICS rom of ur choice and see
Click to expand...
Click to collapse
I'll try what you're saying.
I'm updating to a 4.0.3 through odin. After root, can i install directly a Jelly bean rom?
gu_cad said:
I'll try what you're saying.
I'm updating to a 4.0.3 through odin. After root, can i install directly a Jelly bean rom?
Click to expand...
Click to collapse
after root first install a custom kernel either siyah or dorimanx latest and then try installing a JB rom compatible with them and see
Sun90 said:
after root first install a custom kernel either siyah or dorimanx latest and then try installing a JB rom compatible with them and see
Click to expand...
Click to collapse
I've already updated to 4.0.3
If i'm flashing Jelly Bam Rom for an example, do i need to install these kernel before, since the rom already has it in the AROMA installer???
And should do the wipes before it/??
Thanks!
gu_cad said:
I've already updated to 4.0.3
If i'm flashing Jelly Bam Rom for an example, do i need to install these kernel before, since the rom already has it in the AROMA installer???
Thanks!
Click to expand...
Click to collapse
yes it will be there in Aroma but for a perfect trouble free install i suggested the same, rest is ur call ma8, fell free todo so the way it looks good for u
Sun90 said:
yes it will be there in Aroma but for a perfect trouble free install i suggested the same, rest is ur call ma8, fell free todo so the way it looks good for u
Click to expand...
Click to collapse
Thanks.
It only worked with with previous instalation of dorinmax kernel. So i had to use Revolt Jelly Bean Rom.
When i tried to flash Jelly Bam Rom, got into galaxy s2 loop, after reboot.
At least, i've got one custom rom.
Now it's so much more difficult to install a rom on my phone. Only because i used that 4.0.4.
There's no way back, right?
My warranty ends in November 30th.
:/
gu_cad said:
Thanks.
It only worked with with previous instalation of dorinmax kernel. So i had to use Revolt Jelly Bean Rom.
When i tried to flash Jelly Bam Rom, got into galaxy s2 loop, after reboot.
At least, i've got one custom rom.
Now it's so much more difficult to install a rom on my phone. Only because i used that 4.0.4.
There's no way back, right?
My warranty ends in November 30th.
:/
Click to expand...
Click to collapse
That's why I said to completely go back on a stock firmware with Odin.
But 3 parted (and for sure with .pit-file then, forgot to say this) and check repartition.
But u have to choose... A phone which turns screen on an just looping or a chance from 80% to 20% for getting phone working again or bricking it.
I personally hadn't any prob til now, but only went back 4-5 times ins 2-3 years (also did the same with SGS before SGSII)
So u got my answer u have to choose.
Anyway u can send it back because warranty and if they fix it, it's fine... If not u can try it by urself anyway
CHEERS
Send from my SGSII-i9100, running RootBox nightly with Dorimanx Kernel.
Hi all,
I just purchased a used GT-I9100 after hard bricking my old one (Odin froze at Set Partition).
Anyway, this 'new' phone had stock 4.0.4 ICS and kernel, AND it had the insane chip. Thus, I immediately flashed the Siyah 4.1.5 kernel to it. Now, I want to update to JB. I should be safe to do so, right? Also, is there a guide to update directly to a custom JB based rom and kernel? I just need some reassurance after bricking my old S2
Thanks!
kekekekyle said:
Hi all,
I just purchased a used GT-I9100 after hard bricking my old one (Odin froze at Set Partition).
Anyway, this 'new' phone had stock 4.0.4 ICS and kernel, AND it had the insane chip. Thus, I immediately flashed the Siyah 4.1.5 kernel to it. Now, I want to update to JB. I should be safe to do so, right? Also, is there a guide to update directly to a custom JB based rom and kernel? I just need some reassurance after bricking my old S2
Thanks!
Click to expand...
Click to collapse
It should be fine if you have a safe kernel. Just boot to recovery, wipe data/cache and install the rom you want
pasanjay said:
It should be fine if you have a safe kernel. Just boot to recovery, wipe data/cache and install the rom you want
Click to expand...
Click to collapse
Thanks, now running Dorimanx + CM10.1
ok so I have an unrooted galaxy s 2 I1900 running stock 4.0.4 and I was wondering to flash siyah on my device do I need a certain kernel or bassland version ?
Siyah ís a kernel... Just make sure you flash the right version. Information is available on www.gokhanmoral.com.
Sent from the Matrix
SamzWorldOfMusic said:
ok so I have an unrooted galaxy s 2 I1900 running stock 4.0.4 and I was wondering to flash siyah on my device do I need a certain kernel or bassland version ?
Click to expand...
Click to collapse
No, just flash Siyah v4 (.tar version) via ODIN. v5 also supports ICS but as far as I remember it had some issues.
ok well the kernel I want to flash is the newest for the galaxy s 2 (siyah v5.0.1) so am I ready to flash or is there anything I need to check or do first? BTW is there a possibility I can brick my phone because my mum won't be happy if I brick it
So what bugs does this kernel have that effects ics because im planning to do a nandroid backup then install cyanogen mod 10.1 jellybean?
SamzWorldOfMusic said:
ok well the kernel I want to flash is the newest for the galaxy s 2 (siyah v5.0.1) so am I ready to flash or is there anything I need to check or do first? BTW is there a possibility I can brick my phone because my mum won't be happy if I brick it
Click to expand...
Click to collapse
You can flash it with Odin. Read about it first, so you won't end up bricking it because you've missed something. But if you follow the correct steps you won't brick it.
SamzWorldOfMusic said:
So what bugs does this kernel have that effects ics because im planning to do a nandroid backup then install cyanogen mod 10.1 jellybean?
Click to expand...
Click to collapse
You can do a Nandroid back up after flashing Siyah. There won't be anything wrong with this back up.
Sent from the Matrix
ok im having thought because my first phone was a htc wildfire that I rooted and installed cyanogen mod without a problem
but when I got my htc one V I bricked it so im very cautious but shell I go for it and flash it now. also could you quickly tell me what part of odin will I put the file in (bootloader,PDA,Phone,CSC
SamzWorldOfMusic said:
ok im having thought because my first phone was a htc wildfire that I rooted and installed cyanogen mod without a problem
but when I got my htc one V I bricked it so im very cautious but shell I go for it and flash it now. also could you quickly tell me what part of odin will I put the file in (bootloader,PDA,Phone,CSC
Click to expand...
Click to collapse
PDA.
SamzWorldOfMusic said:
ok so I have an unrooted galaxy s 2 I1900 running stock 4.0.4 and I was wondering to flash siyah on my device do I need a certain kernel or bassland version ?
Click to expand...
Click to collapse
Make sure you dont perform and wipes or cleans before flashing siyaah kernal. Your on 4.0.4 ics which the stock kernal that has the brickbug. I repeat be careful not to wipe, clean or backup anything before you install siyaah kernal. After you have, then its all good mate. Good luck.
Sent from my GT-I9100 using xda premium
ok well from what I see I think il just wait for the jellybean update to be released in the uk but thanks guys il keep in mind for the future