I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
custom bootloader?
avoid flashing bootloaders whenever possible. If your phone is working okay right now, leave it.
hottpockets said:
I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
Click to expand...
Click to collapse
There are no custom bootloaders. Since you flashed the one click ics leak you now have the secondary bootloader that came with that package. codworxx kernel and tasks' ics leak have no bootloaders and will not change them in any way.
As long as the secondary bootloader does not suffer from any corruption during the flash process and your phone boots up normally after flashing it, it will not cause you any problems (other than resetting the custom binary counter if that ever becomes an issue for you).
The danger of flashing packages with bootloaders is if something happens during the flash process to corrupt the bootloader it will hard brick your phone, as in dead paper weight brick.
So don't ever flash any package with bootloaders unless you are absolutely sure want too flash them and are aware of the risk.
Sent from my SGH-I777 using XDA Premium HD app
Related
i got my Atrix yesterday and immediately ota updated to 2.3.4, unlocked, fastboot "flashed?" my recovery with cwm, and installed alien. i winged it. thank god i'm not bricked. i had to use fastboot to flash my recovery twice, but since then i've been trying to get UOT to cook something that actually works and cwm seems stable now.
the question is, if i flash a rom based on 1.8.3 will that brick my device? or does the brick only happen if you go back to an unlocked rom? hmm..
anyway, thanks for all the hard work devs! keep it coming =D
edit: i did actually unlock first then update.
you will hard brick your phone if you go back to 1.8.3 after installing the OTA 2.3.4
why do you want to go back to 1.8.3?
i don't! i'm worried about flashing a custom rom based on 1.8.3 by accident not knowing that's what its based on
aaron.a said:
i don't! i'm worried about flashing a custom rom based on 1.8.3 by accident not knowing that's what its based on
Click to expand...
Click to collapse
Right now, most roms are flashed via CWM, which shouldnt touch your bootloader. The bricking occures because the official SBF files include an older bootloader which is now seen as an invalid version thanks to the burnt fuse. I dont want to say its impossible, but your not likely to hard brick through CWM. Just dont ever touch RSD/SBFs again and you should be set.
Not to mention, most of the Froyo based roms were made for the old CWM and probably dont work right on the unlocked version of CWM.
If you do decide to go back to Froyo for whatever reason, look for the fruitcake thread. That has CWM flashable firmwares without bootloaders in them, so there's no chance of a hard brick compared to SBFs.
Nevermind mispost
that's basically what i wanted to know. cheers!
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
Hi, I've flashed my S2 (Android 2.3.4) with litening rom (V2.0 XXKG1) a while back.
I've been wanting to root ICS on it with Odin (it's from the UK so I'd use the official firmware from Orange, if there's no better choice), but I'm afraid that since it contains a custom rom that was designed for gingerbread it might have some incompatibility issues.
Do I need to restore my phone to factory settings or can I just root ICS on top of what's already there?
Also, once I root the official new firmware will all those pesky stock apps from samsung come back?
Thanks for any help!
1) Follow whatever instructions the specific ICS rom has re: flashing it.
If it says it's OK to flash directly from GB, then go for it. If it says do something different, do that. If it doesn't mention flashing something else over the top of GB before flashing the ICS rom, I think you can pretty safely assume you don't need to (unless the dev of the ICS rom expects you to be a mind reader).
2) Re: restoring factory settings first, refer to 1 (but likely for most roms so you don't end up with a lot of FCs on system apps).
3) That will depend on whether the rom you flash has those pesky apps included and whether you need to do a factory reset/wipe or not (refer to 2; likely)
Hello,
I have flashed my SG S II with Lite'ning Rom v2.3 XWLP2. Previously i was on a gingerbread previous version of Lite'ning rom, which worked flawlesly for several months.
Everything seemed fine and i restored with Titanium only my missing apps+data (not the system data).
After a few hours, the phone started to at times not be able to see the sd card. More importantly, it would suddenly hung and reboot, appear to be working for a couple of minutes and reboot again. This would happen for 10 mins. Then without changing anything, everything would be normal again for 5-6 hours, after which rinse and repeat.....
Does anybody else have the same problem or did i do something wrong? Could anybody know if fs there anything i could do to fix it other than reflashing again?
Thanks in advance guys...
Factory reset in the first instance, then a reflash with a clean install of everything (No Ti restores).
MistahBungle said:
1) Follow whatever instructions the specific ICS rom has re: flashing it.
If it says it's OK to flash directly from GB, then go for it. If it says do something different, do that. If it doesn't mention flashing something else over the top of GB before flashing the ICS rom, I think you can pretty safely assume you don't need to (unless the dev of the ICS rom expects you to be a mind reader).
2) Re: restoring factory settings first, refer to 1 (but likely for most roms so you don't end up with a lot of FCs on system apps).
3) That will depend on whether the rom you flash has those pesky apps included and whether you need to do a factory reset/wipe or not (refer to 2; likely)
Click to expand...
Click to collapse
So basically all I need is to flash a Rom that has been updated to ICS and it will update my phone too? I thought I needed to update the firmware and then flash a Rom
As I said yesterday, follow whatever specific instructions the rom you're wanting to flash has; for example, CM7 is pretty specific about having to flash the rom twice, CM9 requires a wipe/factory reset if you're coming from another rom.
Rom is another name for firmware.
Modem is separate, a few roms come with a modem & overwrite/replace your existing modem, most do not. Kernels are also included with pretty much all roms & will overwrite/replace your existing kernel.
Gay-Lussac said:
So basically all I need is to flash a Rom that has been updated to ICS and it will update my phone too? I thought I needed to update the firmware and then flash a Rom
Click to expand...
Click to collapse
Hmm I suspected that firmware was the same as Rom but wasn't sure, thanks again.
MistahBungle said:
As I said yesterday, follow whatever specific instructions the rom you're wanting to flash has; for example, CM7 is pretty specific about having to flash the rom twice, CM9 requires a wipe/factory reset if you're coming from another rom.
Rom is another name for firmware.
Modem is separate, a few roms come with a modem & overwrite/replace your existing modem, most do not. Kernels are also included with pretty much all roms & will overwrite/replace your existing kernel.
Click to expand...
Click to collapse
Hi guys,
This is my first post(go easy on me) also english is my second language.
Anyway, i've had my ATT-i777 GS2 since launch & been keeping tabs on its development & such. I stayed on stock experience due to not having any issues at all. I think i waited long enough that i should try the ICS experience, ive' red quite a bit about it & learned of its huge improvement for Android.
So my question is what's the easiest way to get stock rooted ICS?
I have these options in mind:
1. update thru Kies & then use creepyncrawly guide UCLE5 Stock ICS with Root
- to me its risky because this have the brick bug
2. root GB with a custom kernel with CWM so then i be able to flash a CWM stock ICS rooted rom
- this one sounds more tedious to me but with this i can avoid KIES update(i think)
Keep in mind my phone is still bone stock GB 2.3.4 & this is my first attempt in flashing.
any more suggestions pls.
Whatever path you choose will be a little tedious. If you plan to flash a custom rom rather than stock ICS, then I would suggest that you root Gingerbread and install a custom Gingerbread kernel containing ClockworkMod Recovery, and then flash ICS from there. I suggest my guide for installing firmware without incrementing the flash counter. If it were my phone running 2.3.4, I would use zergrush toolkit to root, and mobile odin to install the kernel.
creepyncrawly said:
Whatever path you choose will be a little tedious. If you plan to flash a custom rom rather than stock ICS, then I would suggest that you root Gingerbread and install a custom Gingerbread kernel containing ClockworkMod Recovery, and then flash ICS from there. I suggest my guide for installing firmware without incrementing the flash counter. If it were my phone running 2.3.4, I would use zergrush toolkit to root, and mobile odin to install the kernel.
Click to expand...
Click to collapse
if i use the zergrush toolkit route is there any wipe/reset involve or necessary prior to doing so?
lvlark02 said:
if i use the zergrush toolkit route is there any wipe/reset involve or necessary prior to doing so?
Click to expand...
Click to collapse
No. Just root it and then flash a Gingerbread kernel. You'll still be on the same base, 2.3.4.
Then, when you are ready to flash a custom rom, which will obviously be another base, especially if it is an ICS rom, then you should do a wipe data/factory reset before you flash the rom.
creepyncrawly said:
No. Just root it and then flash a Gingerbread kernel. You'll still be on the same base, 2.3.4.
Then, when you are ready to flash a custom rom, which will obviously be another base, especially if it is an ICS rom, then you should do a wipe data/factory reset before you flash the rom.
Click to expand...
Click to collapse
sorry didnt got to reply soon enough, i got busy a bit. anyhow i think follow yer instructions & hope for best & ill let u knw bout the results.
Hi,
I know these types of questions has been asked/answered before, but I have not even by combining the different threads information managed to get a clear picture of what to do in my situation
Background info:
I inherited a samsung galaxy tab 10.1 (p7510), i.e. p4wifi, with JB installed.
It's currently running cm-10-20120816-experimental-p4wifi and clockworkmode recovery 5.8.3.1 with ROM Manager v5.0.2.1
I have SOD while charging, but everything else works fine. This makes me believe that i don't have the proper boot loader!?
What i want to do:
flash the new cm-10-20121017-experimental-p4wifi
a boot loader is also provided US_LPL_4.0.4_bootloader.zip
from: droidbasement.com/galaxy/roms/cm10/p4wifi/
Question(s):
Do I need to to take any special steps to get the correct boot loader in place (now that i'm already on cm 10 with an incorrect bootloader)?
Could i just use ROM Manager to flash both the boot loader and new cm-10-20121017-experimental-p4wifi or must i use odin?
If I need odin, do I need another recovery as well?
So the basic question is, in my situation running an older build of cm10 on a p4wifi, running an unknown boot loader and clockworkmode recovery, how do i get back on track with a correct setup of every part?
If someone could help me out with a step-by-step it would be greatly appreciated, please include links to necessary files e.g. if i first must flash a stock boot loader,recovery etc..
BR
Peter
Peppelito said:
Hi,
I know these types of questions has been asked/answered before, but I have not even by combining the different threads information managed to get a clear picture of what to do in my situation
Background info:
I inherited a samsung galaxy tab 10.1 (p7510), i.e. p4wifi, with JB installed.
It's currently running cm-10-20120816-experimental-p4wifi and clockworkmode recovery 5.8.3.1 with ROM Manager v5.0.2.1
I have SOD while charging, but everything else works fine. This makes me believe that i don't have the proper boot loader!?
What i want to do:
flash the new cm-10-20121017-experimental-p4wifi
a boot loader is also provided US_LPL_4.0.4_bootloader.zip
from: droidbasement.com/galaxy/roms/cm10/p4wifi/
Question(s):
Do I need to to take any special steps to get the correct boot loader in place (now that i'm already on cm 10 with an incorrect bootloader)?
Could i just use ROM Manager to flash both the boot loader and new cm-10-20121017-experimental-p4wifi or must i use odin?
If I need odin, do I need another recovery as well?
So the basic question is, in my situation running an older build of cm10 on a p4wifi, running an unknown boot loader and clockworkmode recovery, how do i get back on track with a correct setup of every part?
If someone could help me out with a step-by-step it would be greatly appreciated, please include links to necessary files e.g. if i first must flash a stock boot loader,recovery etc..
BR
Peter
Click to expand...
Click to collapse
You should be fine just flashing the new CM 10 build from Pershoot. If you want to update your bootloader you can do that too but I don't remember reading about any change in requirements from the earlier CM 10 build as far as the bootloader is concerned. What makes you think you are using an "incorrect" bootloader to begin with?
Always a good idea to have the stock firmware from Samsung to flash in Odin in case anything breaks. Remember if that happens to flash the ROM with Odin but then also do a factory reset afterwards.
suleimankhan said:
You should be fine just flashing the new CM 10 build from Pershoot. If you want to update your bootloader you can do that too but I don't remember reading about any change in requirements from the earlier CM 10 build as far as the bootloader is concerned. What makes you think you are using an "incorrect" bootloader to begin with?
Always a good idea to have the stock firmware from Samsung to flash in Odin in case anything breaks. Remember if that happens to flash the ROM with Odin but then also do a factory reset afterwards.
Click to expand...
Click to collapse
I was looking at the post in
http://forum.xda-developers.com/showthread.php?t=1787399&page=188 to page 203
And there was a lot of talk about having the correct boot loader or else strange flickering could appear, and as i interpreted (or maybe misinterpreted) it, shutdown while charging or SOD while charging, indicated that you are using the wrong boot loader?
So you are saying; as long as the previous build is running okay, I should be fine using ROM Manager / "clockwork mode" to flash the files from Pershoot?
Is it also okay to flash the bootloader using the ROM Manager / clockwork as well? (flash order: bootloader->cm->gapps)
Sry, if everything is just confusion from my part, it was 2 years since i previously flashed a custom ROM..
All the talk about matching boot loader with a certain build made me uncertain. I have always just considered the boot loader to be just the "kick starter" for the actual ROM/CM/OS "binary". But comments in the thread-posts indicating flickering/charge-errors is caused by having the incorrect boot loader made me uncertain about if I was running the correct loader (as i have charging shutdown problems)...
Is there a way of checking my version of the boot loader and/or making sure I have an unlocked boot loader (or is it unlocked for sure as I'm already running a custom ROM?)
Why all the talk about using odin? Is it just that people tend to find odin better than ROM Manager / Clock work mode or do they actually do different things?
Any answers sorting out the thoughts of a somewhat Custom-ROM-noob, whom has just risen from the ashes after sleeping for two years, would be greatly appreciated!