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 got my Note and am coming from a htc desire. Just trying to get up to speed on the different "lingo" and software for rooting that the device seems to have? can someone give me the coles notes.
Flashing customization
CWM vs Odin
- Whats the basic difference between these two options (only experience is with CWM) when flashing roms, can any update.zip be flashed by either CWM or Odin ?
Terminology
- Im seeing Firmware, ROM and Kernel being thrown around regularly... Kernel and Rom I get but, I haven't heard the term firmware with any flashing on the desire... I'm assuming that the firmware is just the android OS + Samsung customization ?
rock_80 said:
Just got my Note and am coming from a htc desire. Just trying to get up to speed on the different "lingo" and software for rooting that the device seems to have? can someone give me the coles notes.
Flashing customization
CWM vs Odin
- Whats the basic difference between these two options (only experience is with CWM) when flashing roms, can any update.zip be flashed by either CWM or Odin ?
Terminology
- Im seeing Firmware, ROM and Kernel being thrown around regularly... Kernel and Rom I get but, I haven't heard the term firmware with any flashing on the desire... I'm assuming that the firmware is just the android OS + Samsung customization ?
Click to expand...
Click to collapse
CWM is flashing a .zip file on your phone in recovery, for custom rom`s/kernel`s
Odin is flashing a .tar file by unzipping a zip file twice from your computer and/or from your phone (mobile odin by chainfire), for samsung firmware
Firmware is mostly used for the firmwareversion like XXKKA or XXKL7 etc.
Update.zip is generally not used.
Never flash custom software (kernel or rom) with Odin from your computer, it initiates the binary flash counter. Will void you warranty when returning your phone to a store for repair!
Link for rooting http://forum.xda-developers.com/showthread.php?t=1331784, read well before beginning!
Thanks for the info, Im already rooted just trolling the custom rom threads now looking for one to test out ! so far I've just been running stock and removing all the bloat from samsung
rock_80 said:
Thanks for the info, Im already rooted just trolling the custom rom threads now looking for one to test out ! so far I've just been running stock and removing all the bloat from samsung
Click to expand...
Click to collapse
Try Rocketrom v12, is to be released in about an hour or so, is very good. Been using v11 for a week now, rockstable and fast
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .
Alucard1989pl said:
I haven't problem with IMEI. The deodexed rom has already root so i don't know why you installed root before you install my deodexed xxlk3 rom -_-" LOL. Try reflash rom with odin than my deodexed rom and at last custom kernel . . .
Click to expand...
Click to collapse
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.
Viprdxd said:
Hey Alu, i tried all methods but result is the same i lose IMEI number, not to worry for now i will try another deodexed. BTW any eta on when you will release 15 toggle for XXLK3? this will motivate me to try again.
Txs for the reply.
Click to expand...
Click to collapse
I'll try in this weekend make this mod for xxlk2 and xxlk3.
Alucard1989pl said:
I'll try in this weekend make this mod for xxlk2 and xxlk3.
Click to expand...
Click to collapse
Good stuff :good:
Viprdxd said:
Recently i have come across a puzzling bug when i flashed deodexed UK firmware S5830IXXLK3 (by Alucard1989PL) and was wondering if anyone else had come accross this,
I flash my phone via ODIN 3.07 to stock XXLK3 UK firmware as normal , this gives me stock kernel & ROM.
I fire up ODIN and flash either Rafael or Hells kernel (it doesnt matter which), reboot, check phone status and i have IMEI.
I root my phone via CWM next just to make sure and check that debug is ticked, reboot.
I then flash the S5830IXXLK3 deodexed ROM via CWM, no problem. When the phone boots i check the phone status and each time i have lost my IMEI number.
On all previous deodexed ROMS i have used i have never come accross this, could it be the latest firmware thats been deodexed or am i overlooking a simple detail here?
Any comments would be appreciated.
Click to expand...
Click to collapse
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!
makeyourself said:
Hi Viprdxd, I have also just experienced this problem after flashing the same XXLK3 UK firmware and then flashing a custom deodexed ROM that I am currently building. My custom ROM is currently based on XXLI1 firmware and I thought there may be some incompatibility problem. However obviously you have flashed Alucard's XXLK3 deodexed ROM so it can't be that. You say its not a kernel issue either so at the moment I currently have very little idea what is causing this. I need to find out though to make my custom ROM compatible with all firmwares so I will be investigating this issue.
I'm just glad I got my IMEI back by reflashing the XXLK3 firmware with ODIN cause I've already permanently lost it once before when I was a bit of a noob and didn't have a backup or anything!
Click to expand...
Click to collapse
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.
Viprdxd said:
Yeah I know that feeling all to well when you see your IMEI number missing I'll keep playing around to see if I can find out why but my feeling is its an issue ROM side with XXLK3., Hey good luck with your ROM I'll defo check it out when its done.
Click to expand...
Click to collapse
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!
makeyourself said:
Nice one thanks :good:
Edit: Sorry Actually I still can't figure this out, if I flash XXLK3 with ODIN, IMEI number is fine. If I install Rafael's kernel, nothing else, it disappears.
If I extract the XXLK3 ROM and flash it in recovery no problems, if I deodex it no problems, if I install custom kernels then IMEI dissappears.
Which leads me to the conclusion its a problem with custom kernels except for the fact that if I flash the ROM I'm building on stock kernel IMEI also dissappears!! So for now it remains a mystery!
Click to expand...
Click to collapse
I have concluded that its not a problem with XXLK3 or The custom Kernels as both work, let me explain, XXLK3 standard and deodexed on stock (came with package) kernel works as it should. Raf's or Hell's Kernel works fine on every other firmware.
It seems to be a problem of compatibility of the two maybe Samsung changed some small detail or a tweek is needed in the kernels or both? I don't know as I am not a dev.
My thread on what I found: http://forum.xda-developers.com/showthread.php?t=2052690
:highfive:
i, know that the title may sound a bit idiotic , but before telling me to flash this and that plz read out the entire problem,
So here goes..
I have a 16 gb Moto X xt 1052 (India) and weirdly I am not able to flash some custom roms present here, i flashed
[ROM][4.4.4][SlimKangs Moto X][SaberMod 4.8][Linaro][Build 7][2014/07/12]
and it flashed like a breeze, also eclipse rom
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-v3-2-2-4-4-2-blur-t2521509
but, i haven't been able to install PA rom , CM11, Carbon, Dirty Unicorn , or any other rom saying unified built for msm8960dt
Plz tell me what should i do, and of course I tried , flashing them on TWRP, and CWM
i_piss_on_apple said:
i, know that the title may sound a bit idiotic , but before telling me to flash this and that plz read out the entire problem,
So here goes..
I have a 16 gb Moto X xt 1052 (India) and weirdly I am not able to flash some custom roms present here, i flashed
[ROM][4.4.4][SlimKangs Moto X][SaberMod 4.8][Linaro][Build 7][2014/07/12]
and it flashed like a breeze, also eclipse rom
http://forum.xda-developers.com/moto-x/development/rom-eclipse-moto-x-v3-2-2-4-4-2-blur-t2521509
but, i haven't been able to install PA rom , CM11, Carbon, Dirty Unicorn , or any other rom saying unified built for msm8960dt
Plz tell me what should i do, and of course I tried , flashing them on TWRP, and CWM
Click to expand...
Click to collapse
This is probably the problem: Did you flash the entire stock SBF file for your carrier -before- you tried to install the roms that aren't working?
I didn't check them all, but the Eclipse rom you linked specifically says in the OP that you need to do this. It is because it requires you to be on the 4.4.2 boot.img (kernel) and baseband. You likely have mismatched versions because you have been flashing other ROMS.
Just follow the instructions in the "Return to Stock" thread to flash back to the most recent OFFICIAL firmware you were on. DO NOT ATTEMPT TO DOWNGRADE! If at any point you had the 4.4.3 OFFICIAL ROM on the phone, do NOT flash 4.4.2
Also, if you ever had the 4.4.3 boot.img (kernel) on there, Eclipse specifically says it requires you to be on the 4.4.2 Kernel/baseband.
You need to be really careful to not downgrade. Doing this has left many X users with bricks...
Can you give that a shot and let us know if it fixes your issue?
Good Luck
No, plz Check the other rom , that rom too is a cm based rom i gues but it doesn't give me any trouble,
Also I tried flashing those rom over my stock rom but TWRP just says FAILED
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Have you all tried Smart Switch?
CodeNameRedNeck said:
Have you all tried Smart Switch?
Click to expand...
Click to collapse
Yes... Smart Switch gave me an error in 2 ways of restoration.
ZEDEK said:
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Click to expand...
Click to collapse
Paper-weight? That's bad... Can't you flash a custom recovery on Odin and install a custom rom? I still can do that.
diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
Click to expand...
Click to collapse
Interesting... So maybe I can wait for a nougat ZTO ROM an then try to flash? Anyway, thanks for the help
MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and ..
Click to expand...
Click to collapse
Good catch, I hadn't even thought of that.
CodeNameRedNeck said:
Good catch, I hadn't even thought of that.
Click to expand...
Click to collapse
Well I figured out you can downgrade from Nougat to Marshmallow but that's only to a specific firmware version. Depending upon what bootloader has been flashed (meaning if you flashed Nougat bootloader you can only go back to Marshmallow with the same bootloader level).. But this is only working (surprisingly) on the locked bootloaders of Verizon and AT&T.. The other S6 Edge Plus I have with an unlocked bootloader and tripped knox that I recently acquired will not accept nothing stock which is unusual, but I'm still working on that one.