Related
hi people, this is my first post, so please be nice!
i've had the galaxy s and it's been rooted for a while, with a custom MIUI rom installed (not sure which one it is... but it's NOT the 2.3.4 one in the development section, it's version 1.7.1). i want to switch roms now, since the battery life is terrible, though the rom is great.
i've been looking through the development section for a new rom to flash, but a lot of them require some change to the firmware, bootloader, etc. the problem is, i don't know what bootloader, firmware, etc version i have
i rooted this phone when it was on STOCK 2.1 eclair ( i know, old), and i did flash a 2.2 rom before flashing this version of MIUI (2.3.4).
do roms change the bootloader? i came from an HTC device, so i don't really have an idea on whats the deal with the Galaxy S. HTC devices were a LOT easier (IMO).
i did a google search, but it didn't really help... O_O
so, if anyone can point me in the right direction, i will be VERY grateful.
thanks
'Settings -> About Phone' will show you your current firmware, etc.
Bootloaders usually only change for major revisions. If you're on Froyo (2.2) and want to flash a Gingerbread (2.3) firmware, you would need to upgrade from Froyo to Gingerbread bootloaders. If you're flashing from 2.3.3 to 2.3.4, you won't need to upgrade bootloaders. Flashing is done using the program Odin or Heimdall (or using a flashable zip via recovery, such as Clockworkmod Recoevery). Heimdall has the "flash bootloaders" right there for you to tick/untick, if I recall correctly. Some firmware files (pit, tar, etc—the files you flash with Odin) have bootloaders, some do not. I can't recall if there's an option within Odin to specify whether to flash the bootloaders or not. Either way, if you flash to an AOSP Gingerbread firmware, it's likely the bootloaders will be included.
So basically, just grab Odin/Heimdall and the necessary firmware files, and you're good to go! But before you do that, verify that download mode (volume down + home + power) works. If it does not, you'll need to get it working before you start flashing—otherwise you risk bricking your device.
If you have anymore questions, feel free to ask. We're here to help.
upichie said:
'Settings -> About Phone' will show you your current firmware, etc.
Bootloaders usually only change for major revisions. If you're on Froyo (2.2) and want to flash a Gingerbread (2.3) firmware, you would need to upgrade from Froyo to Gingerbread bootloaders. If you're flashing from 2.3.3 to 2.3.4, you won't need to upgrade bootloaders. Flashing is done using the program Odin or Heimdall (or using a flashable zip via recovery, such as Clockworkmod Recoevery). Heimdall has the "flash bootloaders" right there for you to tick/untick, if I recall correctly. Some firmware files (pit, tar, etc—the files you flash with Odin) have bootloaders, some do not. I can't recall if there's an option within Odin to specify whether to flash the bootloaders or not. Either way, if you flash to an AOSP Gingerbread firmware, it's likely the bootloaders will be included.
So basically, just grab Odin/Heimdall and the necessary firmware files, and you're good to go! But before you do that, verify that download mode (volume down + home + power) works. If it does not, you'll need to get it working before you start flashing—otherwise you risk bricking your device.
If you have anymore questions, feel free to ask. We're here to help.
Click to expand...
Click to collapse
when i go to settings/about phone it shows this:
model number: GT-19000
android version: 2.3.4
baseband version: 19000XXJVK
kernel version: [email protected] #1
build number: MIUI 1.7.1
so how do i know what my bootloader version is?
thanks for your help, still confused though...
Okaham said:
when i go to settings/about phone it shows this:
model number: GT-19000
android version: 2.3.4
baseband version: 19000XXJVK
kernel version: [email protected] #1
build number: MIUI 1.7.1
so how do i know what my bootloader version is?
thanks for your help, still confused though...
Click to expand...
Click to collapse
Unfortunately, you won't be able to tell what bootloader you have. Since you're running 2.3.4, which is Gingerbread, I'd assume you have a Gingerbread bootloader—but if you flashed from Froyo to MIUI, it's likely you only have a Froyo bootloader.
If you're currently running MIUI, the best way to change to another custom ROM would be to flash (via Odin/Heimdall) to the latest AOSP Gingerbread firmware (including the bootloaders), and then flash via recovery (using a flashable zip) to the custom ROM of your choosing—unless they have a package to flash using Odin.
upichie said:
Unfortunately, you won't be able to tell what bootloader you have. Since you're running 2.3.4, which is Gingerbread, I'd assume you have a Gingerbread bootloader—but if you flashed from Froyo to MIUI, it's likely you only have a Froyo bootloader.
If you're currently running MIUI, the best way to change to another custom ROM would be to flash (via Odin/Heimdall) to the latest AOSP Gingerbread firmware (including the bootloaders), and then flash via recovery (using a flashable zip) to the custom ROM of your choosing—unless they have a package to flash using Odin.
Click to expand...
Click to collapse
i was on the stock 2.1 eclair galaxy s rom, and then i downloaded and flashed the baldoz rom, which used to be 2.2 (not sure if it still is). did that custom rom change my bootloader? so if i had the stock eclair 2.1 bootloader before, wouldn't i still have that bootloader right now? since you said MIUI doesn't change the bootloader?
Okaham said:
i was on the stock 2.1 eclair galaxy s rom, and then i downloaded and flashed the baldoz rom, which used to be 2.2 (not sure if it still is). did that custom rom change my bootloader? so if i had the stock eclair 2.1 bootloader before, wouldn't i still have that bootloader right now? since you said MIUI doesn't change the bootloader?
Click to expand...
Click to collapse
If you used a flashable zip to flash via CWM, your bootloaders wouldn't have been changed. If you flashed via Odin, they may have been, depending on whether or not bootloaders were included in the files. (Although, for the most part, I don't believe many custom ROMs would include bootloaders, if any at all.)
Either way, your current bootloaders shouldn't matter much. I would still advise upgrading to Gingerbread bootloaders, as per the custom ROMs requirement (which I'm assuming most up-to-date ROMs will require, or at the very least recommend. For example, CM7 can run off of Froyo bootloaders or Gingerbread bootloaders, but battery life is negatively affected if you're using Froyo bootloaders.)
upichie said:
If you used a flashable zip to flash via CWM, your bootloaders wouldn't have been changed. If you flashed via Odin, they may have been, depending on whether or not bootloaders were included in the files. (Although, for the most part, I don't believe many custom ROMs would include bootloaders, if any at all.)
Either way, your current bootloaders shouldn't matter much. I would still advise upgrading to Gingerbread bootloaders, as per the custom ROMs requirement (which I'm assuming most up-to-date ROMs will require, or at the very least recommend. For example, CM7 can run off of Froyo bootloaders or Gingerbread bootloaders, but battery life is negatively affected if you're using Froyo bootloaders.)
Click to expand...
Click to collapse
thank you so much!
and can you please give me the links or something on how to flash the gingerbread radio in ODIN?
THANK YOU
Okaham said:
thank you so much!
and can you please give me the links or something on how to flash the gingerbread radio in ODIN?
THANK YOU
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1139050
I googled it for you, and while I only skimmed that, it appears to be a very thorough tutorial.
Have fun! And thanks for the thanks.
upichie said:
http://forum.xda-developers.com/showthread.php?t=1139050
I googled it for you, and while I only skimmed that, it appears to be a very thorough tutorial.
Have fun! And thanks for the thanks.
Click to expand...
Click to collapse
thank you kind sir
this changes the bootloader to a 2.3 gingerbread one right?
Okaham said:
thank you kind sir
this changes the bootloader to a 2.3 gingerbread one right?
Click to expand...
Click to collapse
Assuming the files you use to flash (via Odin/Heimdall) include the bootloaders, but it's likely they will.
Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
galaa said:
Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
Click to expand...
Click to collapse
It is advisable to upgrade with Kies, do not use odin.
If you have confidence then only use odin, safe is Kies.
galaa said:
Just wondering what will happen if a rom is flashed into a phone which has an incompatible baseband, kernel and/or OS version?
For example, my phone currently is using a kj4 baseband, and kj6 kernel and running android 2.3.5.
If I flashed a rom which is based on a kka baseband and kernel and android 2.3.6, what will happen?
Will the phone be bricked? Or will it still function but with weird results?
And is it advisable to upgrade my OS to 2.3.6 if I'm flashing to a rom based on that version, or can I just stay at 2.3.5?
Thanks.
Click to expand...
Click to collapse
you can flash the 2.3.6 ROM. Backup your data, clear your dalvik cache and factory reset, then flash the ROM in CWM recovery... restore your data.... and voilà!
Do you have CWM recovery? if no, then install a kernel from a thread in the 'android development forum', you'll find instructions in the thread.
Happy Flashing!
edit: If you have no idea what I'm talking about, say so, I'll explain the details.
I just traded my i717 note for the n7000. After reading random forums on here, i'm a bit flustered but hanging in there.
Just a question, I currently have this set up on my phone:
Android Version: 2.3.6
Baseband Version: N7000XXLP1
Kernel Version: 2.6.35.14-FM-2.0-g399c932 [email protected])
Build: Gingerbread.XXLA6
My questions are:
1) Is XXLP1 an ICS modem?
2) I want to revert this phone back to a good stock image. I was thinking a German image. What do you think? (so I can update to ICS stock/root)
Your help would be appreciated.
Basically I just wanted to know if it's safe for me to flash stock rom/kernel without worrying about bricking my device and can I flash traingleway by chainfire to remove yellow triangle and reset counter without bricking my device. Please. Help
Stock is completely fine. Just the recoveries are giving people problems. Also LP modems are ICS
whatsaqazza said:
Stock is completely fine. Just the recoveries are giving people problems. Also LP modems are ICS
Click to expand...
Click to collapse
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Alright, so if I flash stock rom and kernel, will it flash the baseband back to stock? Also which stock would you recommend?
ps. There is currently CWM on my phone, should I flash a factory recovery or just leave it as is?
chasmodo said:
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Click to expand...
Click to collapse
So that means I traded for a messed up phone? CRAP!!!
But all that is ICS is the baseband (modem), the kernel and rom are stock gb, right?
adv1sory said:
So that means I traded for a messed up phone? CRAP!!!
Click to expand...
Click to collapse
Yep, Sammy did a crap job of official updates. All of them can mess up your EMMC.
However, you have an option to flash any of the CM9-based Roms, and you will be fine (those mentioned in the previous post).
........................
I chose Asylum, but one of the requirements is that recovery has to be:
on a proper working recovery, (DAFUQ, CM9 or a GB recovery ONLY)
The phone currently has CWM 5.0.2.7.
chasmodo said:
Stock is completely safe my hairy arse. Even large file deletion can cause a hard-brick.
Stick to:
CM9
Asylum
ParanoidAndroid or
MIUI.
These Roms contain a safe kernel. Everything else carries the risk of a hard-brick.
Be warned.
Click to expand...
Click to collapse
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
adv1sory said:
I chose Asylum, but one of the requirements is that recovery has to be:
on a proper working recovery, (DAFUQ, CM9 or a GB recovery ONLY)
The phone currently has CWM 5.0.2.7.
Click to expand...
Click to collapse
You can flash it directly if you are on any Gingerbread rooted Rom.
whatsaqazza said:
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
Click to expand...
Click to collapse
Steer clear of any official ICS Roms for now.
whatsaqazza said:
I thought complete stock, without recovery or anything flashed through odin was. Sorry if I'm wrong
Click to expand...
Click to collapse
I'm confused.
If I currently have a gb rom and kernel, shouldnt it be okay to flash stock gb? Or because I have an ICS baseband it makes it a problem?
If I were to follow the instructions posted here,
http://forum.xda-developers.com/showpost.php?p=23052721&postcount=10
Couldn't I be worry free about bricking?
adv1sory said:
I'm confused.
If I currently have a gb rom and kernel, shouldnt it be okay to flash stock gb? Or because I have an ICS baseband it makes it a problem?
Click to expand...
Click to collapse
Flashing on GB is completely ok, don't worry about modems. Sorry for the confusion. Just steer clear of any of the ICS roms that weren't mentioned as safe... All GB ROMs are safe as far as I know
whatsaqazza said:
Flashing on GB is completely ok, don't worry about modems. Sorry for the confusion. Just steer clear of any of the ICS roms that weren't mentioned as safe... All GB ROMs are safe as far as I know
Click to expand...
Click to collapse
PERFECT! So I didn't buy that much of a crappy phone. All I have to do is flash a stock GB rom and kernel. Then I'm able to install any gb custom rom, but should steer clear of any ICS roms that are deemed unsafe. Cool!
Taking the plunge!
I feel my heart racing ....
UPDATE: ALL FINE!!!! I don't have to worry about hardbricking my device. Currently running Open Europe stock rooted rom.
Can't be happier. Thank you all for your help! I greatly appreciate the quick responses I received on this thread!!
Hi, I have an international varient of the Galaxy Note GT N7000 which using Chainfire's Got Brick App v1.1 says:
eMMC Chip
Type: VYL00M
Revision: 0x19
Verdict: Danger! This eMMC chip is "Known" to have the brick bug!
I once had installed a custom Kingdroid ROM v3 and wiped it but it had resulted in a Hardbrick/Superbrick so i had to take it Samsung Service Center to get it fixed. They have repaired it and given me back the handset with the Stock ICS ROM. Here are the details:
Model Number: GT-N7000
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version: 3.0.15-N7000JPLPD-CL643396
[email protected]#3
SMP PREEMPT Thu May 31...
Build Number: IM74K.JPLPD
Now i have done some researched and found that this bug is only triggered with kernels (ICS stock & leaked) which have the eMMC_Erase function/command. GB kernels are not known to have this erase function so they are safe.. Also the two safe kernels are franco r3 and speedmod k3 (Correct me if im wrong). Can anyone please guide me on the following:
1) Should I flash Stock Gingerbread OR ICS Kernel(franco/speedmod)?
2) Should I use Recover or ODIN?
3) Plz Provide the links for the Kernels - Franco R3 & Speedmod K3 which are safe?
4) Will the above Kernels provide root access?
5) Is abyss kernel safe (because it supports GPU overclock)?
6) Can i flash an ICS kernel over a Gingerbread ROM?
For answering please answer in a similar numbered way so that it is easy to read and understand for me as well as future audience! Thanking everyone who takes time to read and answer!
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
You Flash it in Odin, It will give you CWM and Root too !
Ive attached the kernel to the post for you.
Abyss kernel is safe, But its for GB ROMs only, You are on ICS so it wont work.
I dont know if you can flash ICS kernel over GB ROM, However, Your are on ICS so you shouldnt need to worry about that.
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
azzledazzle said:
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
Click to expand...
Click to collapse
Thanks for the confirmation mate, one more thing to ask you: Is the speedmod kernel faster than the stock ICS kernel? Is there any flaws such as battery drain/WIFI problem with it? Also does it support GPU OC? Thanks once again for your help!
little-vince said:
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
Click to expand...
Click to collapse
Firstly get your Galaxy Note checked using Chainfires App (Gotbrick v1.1). If the verdict says "Danger" only then does your device have this problem. My Galaxy Note (Rev 0x19) had this problem and came with GB out of the box and i upgraded it to ICS through Samsung Kies and it worked fine. So i do not think that while updating to ICS via Kies will cause this problem. As of what i know it is triggered when a command eMMC errase is triggered when either doing a factory reset or wipe through recovery. The update as such did not brick my device, however this does not mean it cannot brick yours. I am no expert on this so be a little cautious while updating. I would suggest stick to GB until Samsung Releases a safe stock ICS ROM with a safe Kernel. Cheers!
really easy
1: (optional ) in GB do factory reset (after you have made a backup with TB)
2: put phone in Download mode.
3: use PC odin flash STOCK ICS rom
4: reboot device let it load
5: put device back into download mode
6: use PC ODIN flash Speedmod k3-3
7: reboot
8: launch CWM and tell it to reboot in cwm recovery
9: load your custom rom of your choice
i HIGHLY recommend doing ONLY THE FACTORY RESET WIPE data and cache in GB before you start anything.
ONCE you are in ICS and have successfully loaded speedmod or franco's kernel then it is safe to do a factory wipe if you want. but ONLY after one of those 2 Kernels are on your device.
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
rp4k said:
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
Click to expand...
Click to collapse
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
little-vince said:
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
Click to expand...
Click to collapse
Yes, this bug is known to trigger usually when you do a wipe using the recovery. However there have been some cases when doing a factory reset via the settings has also resulted in a brick. However if you stay away from recovery and do not intend to doing flashing/wipes then i guess you should be ok. And it is a matter of time before Samsung Comes up with a solution. They are said to be working on this bug already. I have the N7000 which i bricked once while flashing and then wiping but i got it repaired since i had warranty. Since then i have stayed away from wiping or installing any custom roms so the device has not given any problems. Hope this info helps! Cheers!
Rom doesnt load during boot
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
cuteglen said:
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
Click to expand...
Click to collapse
What rom are you on? Have you performed any wipes or factory resets?
Sent from my GT-N7000 using xda premium
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
SpyderTracks said:
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
iraqi4ever80 said:
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
Click to expand...
Click to collapse
Only from GB kernel such as abyss. If you flash from ics kernel you WILL brick. This goes for all cm based roms.
Sent from my GT-N7000 using xda premium
kyllerbuzcut said:
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
Click to expand...
Click to collapse
Hiya, yep, you can just delete the zimage file, no need to replace, it will just skip writing that partition.
Sent from my GT-N7000 using xda premium
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Try mobile odin. If you point to the tar, it should load all the components. You can then review which components are being flashed.
Sent from my GT-N7000 using xda premium
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Add goku, dafuq, gl-notecore and abyss42 (GB) to your list.
2. Only do it from a GB firmware or at least a GB kernel like abyss42. SPECIFIC instructions per firmware is listed for a reason. Follow those instructions to the letter.
3. No.
Sent from my GT-N7000 using xda app-developers app
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Stock rom in a zip? Are you sure you are nit flashing a custom rom? Point us to the file/thread please.
If it is a custom rom, the it is meant to be via CWM.
1. Flash abyss42
2. Reboot recovery
3. Do your wipes
4. Flash.
Im sure there is a specific instruction on where you got that file. Or better yet, go to dr. Ketans thread and get your stock rom from there.
Sent from my GT-N7000 using xda app-developers app
It's just the standard rom file from sammobile.It does come as a zip you know. If you unzip it, then use rar on it you can see all the bits. I thought if I just put a different zimage in there it would just go ahead and use that, but didn't seem to like it after I zipped it all back up again.
Tonight I've ended up getting chainfires excellent CF-Root kernel.Flashed that through odin, over my speedmod kernel.
Put just the factoryfs part of the stock rom zip onto the SD card and flashed that using the cwm app that CF-Root installs for you.. Now have CF-Root kernel and 4.0.4 firmware.
If you don't already have a "safe" kernel then I dunno what the brick chances would be, but since I had a safe one already I thought it couldn't hurt to try it out.
The reason I haven't flashed the hidden, cache, model and sbl parts of the zip is that simply they wouldn't fit on my SD card If it behaves funny or I can make space then I'll try the rest too. And the reason I didn't flash the zimage from the zip should be fairly obvious. Because I don't want a brick
EDIT: I managed to clear some space on the SD and flashed the rest of it. Seems to be working ok, so far anyway. I'm hoping the battery issues from 4.0.3 will be a little better. This is a really good way of doing it all as you can just swap out a potentially bad kernel for one that has been 'protected' by having te emmc cap erase turned off.
Hi everyone,
Recently my phone loses IMEI after flashing any ROM, even after flashing kernel only (Semaphore 3.0.0 on CM10.1.3, for example). I have flashed the phone many of times before with different ROMs, kernels, sounds, fonts, animations, etc., but never had this issue before. Something has changed and I don't know what it is. It's getting annoying I just did a full cycle by the book: Format int/ext storage -> One-click stock ROM -> One-click Corn kernel -> Cyanogen 10.1.3 Stable (flash to repartition, flash the again). The phone works perfectly. Flashed another JB ROM to test, the same one I have flashed many times before with no issues (HellyBean 4.2.2, CM-based), and bam - lost IMEI again!
I have no problem restoring IMEI. The question is why the phone loses IMEI now after ROM change but never before?
What you describe suggests something has changed in the install scripts on either the CM or Helly roms.
It seems like flashing 10.1.2. instead of .3 would test CM as cause.
sent from one of my two SGH-I897 Captivates
I was thinking about this, it started somewhere around CM 10.1.2. But if the cause is changes in CM installation, then am I the only one experiencing this issue? I don't see many comments about lost IMEI on 4.2.2 ROMs. Yes, I know it happens, but not on every flash. I tried flashing Xylon 2.3.3 ROM, the one I flashed at least 3 times before with no issues, and same thing - lost IMEI. Seems like EFS is now in a place that gets wiped every time I flash something.
I tried installing cyanmod 4.2.2 and lost my imei. So I flashed back to 2.3.5 I think ill leave it where its at
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
I tried installing cyanmod 4.2.2 and lost my imei. So I flashed back to 2.3.5 I think ill leave it where its at
Click to expand...
Click to collapse
Try again. Android 4.2.2 is much better than stock 2.3.x.
Val D. said:
Try again. Android 4.2.2 is much better than stock 2.3.x.
Click to expand...
Click to collapse
Will It erase it again? I took me forever to unlock it to T-Mobile. I don't want to loose that.
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
Will It erase it again? I took me forever to unlock it to T-Mobile. I don't want to loose that.
Click to expand...
Click to collapse
The phone will stay unlocked. Just try again and you"ll be fine. Use latest CM10.1.3 Stable release.
Is it a one click Odin file. I have the one for 2.3.5
Sent from my SAMSUNG-SGH-I897 using xda premium
Pajar0913 said:
Is it a one click Odin file. I have the one for 2.3.5
Click to expand...
Click to collapse
No. Read this Guide how to update your phone.