Hello,
i've reading a lot about all methods of flashing kernels via Odin and flashing new ROM's. I've my N7 rooted and running custom ROM and experienced several ROMs and kernels with my old Galaxy Ace.
Saying this. I've been searching around about ways of backing up the exact image of my stock ROM with operator logos at the beginning and everything like it came from factory since I would not be able to turn it back to warranty service if it doesn't run original stock ROM, which is not in the net -i've searched and have found nothing-.
If I flash let's say: Siyah kernel to avoid risk of bricking from 4.0.4 then root and create a nandroid backup image and then after running some ROMs I decide to run back to nandroid backup, the kernel that I would have had it would be siyah kernel with operator firmware, right?
Any idea, hint or advice would be strongly appreciated.
esponges said:
Hello,
i've reading a lot about all methods of flashing kernels via Odin and flashing new ROM's. I've my N7 rooted and running custom ROM and experienced several ROMs and kernels with my old Galaxy Ace.
Saying this. I've been searching around about ways of backing up the exact image of my stock ROM with operator logos at the beginning and everything like it came from factory since I would not be able to turn it back to warranty service if it doesn't run original stock ROM, which is not in the net -i've searched and have found nothing-.
If I flash let's say: Siyah kernel to avoid risk of bricking from 4.0.4 then root and create a nandroid backup image and then after running some ROMs I decide to run back to nandroid backup, the kernel that I would have had it would be siyah kernel with operator firmware, right?
Any idea, hint or advice would be strongly appreciated.
Click to expand...
Click to collapse
If you want to return to a stock rom, just flash it with Odin (roms are on www.sammobile.com and also here on xda). There are also ways to reset your flash counter. That would be all.
To answer your question: if you root your device with Siyah and you make a Nandroid back up, yes, your device will be running the stock rom with the Siyah kernel if you restore this after trying other roms/kernels.
Sent from the Matrix
Donnie Sins said:
If you want to return to a stock rom, just flash it with Odin (roms are on www.sammobile.com and also here on xda). There are also ways to reset your flash counter. That would be all.
To answer your question: if you root your device with Siyah and you make a Nandroid back up, yes, your device will be running the stock rom with the Siyah kernel if you restore this after trying other roms/kernels.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for your reply, but in Samfirmware the firmware for my mobile company it's not uploaded so I would not be able to run back to original kernel. That's why I need to know if there's a way to backup the kernel or not losing in order to get cwm.
Cheers
I have found what it looks to be a free stock rom for my country running the same kernel than my mobile company kernel. Is it a way to just install the kernel from the file that samfirmware.com provides? My plan is to run the nandroid backup with my original stock rom with custom kernel <whatever name> then just flash the original kernel taken from the stock rom provided by samfirmware.com .
Related
Getting a bit confused about all this, so am wondering if i've got it right. A rom is the whole thing, it includes a kernel and so forth? So a Kernel is a part of the rom right? And you can flash kernels individually without flashing a whole new rom? But what is a firmware then? Just another name of a rom?
Also on the Galaxy S2 can you flash custom roms, like Lite'ning, without getting root first? Or do you need to get root before flashing custom roms? If you can flash custom roms first without rooting, will the custom rom then give you root as long as it includes it?
And you also got recovery, which is a separate thing again? Galaxy S2 comes with a very basic one if i've understood correctly, but there is others out there that you can install, which also gives you the ability of flashing roms straight from the microsd/phone storage?
So have i gotten any of this? Hope am not to far off
Edit: http://forum.xda-developers.com/showthread.php?t=1246131 looks like most of my questions where answered there, though am still a bit unsure if it's possible to flash a custom rom before you root?
ROM's and FIRMWARE: The ROM or Read Only Memory is the internal flash memory where the core operating system resides. The Firmware is a device specific part of the ROM that controls various hardware components. So the firmware is contained in the ROM but in the context of Android the terms are often used interchangeably.
KERNELS: Different kernels offer different advantages, some are fast, some are light weight on the battery and some are a mix, so yes you can in most cases flash a different kernel with a ROM, and then your phone will be running the custom ROM you picked with the new kernel you flashed.
Rooting: You must have a rooted phone inorder to flash a custom rom, but rooting in my opinion seems really safe and it really easy to do on the SG2
There are things that allow you to flash from your SD card and you do that by entering clockworkmod revovery, apps like rom manager also allow you to flash from sd card, but you can always use odin, which is safe and fast
hope this helps
Thanks, and very nicely explained =) Another question then, what is the reason one need root before you can flash custom firmwares? As i heard Galaxy S2 doesn't really have any safety measures put in to stop things, like HTC do with their bootloader. Another thing is that i checked the thread for the Lite'ning rom, and saw the installation procedure, and it doesn't mention anything about having root before starting, so am getting a bit confused there.
You don't need to root before flashing a custom ROM as long as you can enter download mode (power up with volume down, home and power button pressed) and can flash the ROM via Odin.
If the ROM is flashable only via ClockWorkMod recovery (a zip that you copy on your phone) then you need to flash something that includes that recovery before flashing the rom (like CF-Root or any kernel that includes CWM).
Lite'ning ROM that you mentioned earlier is flashable via Odin so no problem.
Every ROM includes a Kernel, the only thing they sometimes don't include is the modem like in VillainROM, you have to flash it separately. And also, if a ROM is announced as rooted, when you flash it, you will have root regardless of the state before flashing
Thanks once again =)
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Nitrius said:
Another question, if one want to get back to stock, flashing one of these "official firmwares": http://forum.xda-developers.com/showthread.php?t=1075278 well revert everything right? Even if i got CWM recovery, after flashing on of those "official firmwares" will give me back the original recovery as well?
Click to expand...
Click to collapse
Yes it will revert back everything
Nitrius said:
Edit: Also you mention "modem", if one ROM don't include one, do you have to flash it separately for the ROM to function at all? Or will it just use the modem that's already on the phone or something? Checked out the VillainROM thread and it doesn't say anything about a modem.
Click to expand...
Click to collapse
If you dont flash a modem it will just use the one you had before. They talk about it in the old thread and also in the new but not in the firsts posts, you'll have to do a search.
Plus Modem Kernels are interchangeable .
KH3 Firmware with KI4 modem and KH1 kernel .
Guide
http://forum.xda-developers.com/showthread.php?t=1125282
jje
I am currently learning and experimenting with rooting, custom roms etc.
Wondered if someone that knows more than me can help me with a few questions I have?
I have rooted my GS2 using CF Root XWKI8 kernel on Odin. I have full root access now and I have made a backup of my factory ROM which is Three firmware.
The questions I have are:
1) How do I remove root access if I need to? Would that be by putting the original kernel back on?
2) Some people have said you can remove the yellow warning triangle by re-loading the original kernel but would that remove the root access if this is how you unroot a CF rooted phone?
3) I am thinking about loading CM7 on the phone using clockword mod. When you load up a new firmware does it have its own kernel that is then put on the phone?
4) If after loading up CM7 onto the phone I then decide to restore the original Three firmware using clockwork mod, what kernel would go back onto the phone? Would it be the CF rooted kernel as that would have been the current kernel when I performed the backup?
Its important to me that I understand everything completely before I play about anymore!
Many Thanks
Dave
1) You can flash a Stock Kernel with Odin to remove root.
2) To remove the yellow warning you first flash a rooted kernel (such as CF-Root), then you flash a Stock Kernel and when it reboots, you use CWM Manager to flash the image kernel from there. That way you keep root and CWM, but the yellow warning doesn't appear any more.
3) Many ROMs have their custom kernel in the same package, so it will overwrite your current kernel. All custom ROMs have a rooted kernel, so despite changing the kernel, you will still have root and CWM.
4) If you did a nandroid backup, you could restore the kernel from which the nandroid was done. If you don't have a nandroid backup, you can flash a Stock ROM to leave the phone as you bought it.
Many thanks for your help.
As I first of all rooted my phone using a CF Root kernel and then did a nandroid backup in clockwork mod of the Three firmware. Would the backup now include the CF Root kernel when I restore from CM7 back to Three firmware or would the original kernel still reside within my Three backup and be restored instead?
If you have the European Galaxy S II (I9100) can you use the CM7 stable build thats on the official CM website or do we need to find one within the dev section here? Anyone know please?
@DJGREEN1980: Since you've done your nandroid backup with CF-Root, when you restore it you will have CF-Root again. If you want to revert CM7 to Stock you can directly flash a Stock ROM, instead of restoring your nandroid backup.
@mikeDCMDVA: There are only 2 versions of CM7 for SGS2. One is for AT&T mobiles and the other is for the rest, so you should be able to flash this last one on your phone. If you have further questions about CM7 I would suggest you post them on CM7 post on XDA or CM7 forum, since CM7 users would surelly have more knowledge than me about that.
Do you know where I would get the stock rom from? My phone is locked and branded with Three firmware.
Thanks for your help
There's a post with all stock ROMs up to date here: http://forum.xda-developers.com/showthread.php?t=1075278
Brilliant. Thanks. So restoring to the latest Three rom XWKI8 would bring the warranty back for the phone after using a custom rom?
Dave
DJGREEN1980 said:
Brilliant. Thanks. So restoring to the latest Three rom XWKI8 would bring the warranty back for the phone after using a custom rom?
Dave
Click to expand...
Click to collapse
Its not that it will bring the warranty back, its more that you could send it to Samsung Support without them noticing you've used a custom ROM. I recently send my HTC Desire to HTC support reverting it to a Stock ROM without problems.
AzureusPT said:
Its not that it will bring the warranty back, its more that you could send it to Samsung Support without them noticing you've used a custom ROM. I recently send my HTC Desire to HTC support reverting it to a Stock ROM without problems.
Click to expand...
Click to collapse
unless u reset the binary counter how will this work ??? of course buy a jig from ebay which im sure he forgot to mention
I'm struggling with the battery life on my S3 and as a last resort have decided to investigate an alternative ROM/kernel. My question is: if I do an Nandroid backup of my current stock ROM (which I have rooted), does it include the kernel? i.e. if I want to get back to EXACTLY the same state if other ROMs and kernels aren't stable can I do this by restoring my Nandroid backup?
Yes it does include the kernel, and everything else.
However its not exactly stock as it has a rooted kernel >> flash stock kernel if required .
jje
Hi,
So unfortunately yesterday i (hard)bricked my phone. (yes my version is 4.0.4 BUT i've flashed five ROMs previously without any problems)
I tried to find other solutions such as Jig and JTAG but no luck for me here (in Sweden)
So instead i, today, went to the service department in the store which i bought my GT-i9100 from. They have now sent it to another location specified in repairing mobile phones.
Obviously my phone was rooted and as far as i know my warranty has been vioded.
So that's why i wonder: if they actually can open my phone, will they see that it has been rooted or does the phone somehow format everything and goes back to factory settings?
And if they can open it and see that it has been rooted, what can they do with my phone then?
Thanx for time
If you corrupted the emmc via the 4.0.4 emmc bug in kernel then I wouldn't worry about it as they will simply open device and replace motherboard. You can avoid emmc bug in future by simply flashing a custom kernel, keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again.
Btw, JTAG fix is for when you corrupt bootloader. If you corrupt emmc, depending on how bad it is (you may be able to connect/partition) the only way to fix is to replace the IC (nand) chip or more simply/quickly to replace whole board.
TheATHEiST said:
If you corrupted the emmc via the 4.0.4 emmc bug in kernel then I wouldn't worry about it as they will simply open device and replace motherboard. You can avoid emmc bug in future by simply flashing a custom kernel, keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again.
Click to expand...
Click to collapse
I do have a custom kernel - Siyah. I've used Siyah on all my ROMs yet. (except for those ROMs which came with it's own kernel, but then i re-flashed Siyah) And as far as i know Siyah should be completely free of the brick bug.
" keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again"
If i flash stock ROM wont i just get the stock kernel also? And for what purpose should i re-flash a custom kernel after flashing stock ROM?
Thank you theAtheist. Appreciate your work (helping others in the way necessary ) And also giving answer to All questions asked.
WardenBerret said:
I do have a custom kernel - Siyah. I've used Siyah on all my ROMs yet. (except for those ROMs which came with it's own kernel, but then i re-flashed Siyah) And as far as i know Siyah should be completely free of the brick bug.
" keeping in mind that if you re-flash stock then you need to also re-flash a custom kernel again"
If i flash stock ROM wont i just get the stock kernel also? And for what purpose should i re-flash a custom kernel after flashing stock ROM?
Thank you theAtheist. Appreciate your work (helping others in the way necessary ) And also giving answer to All questions asked.
Click to expand...
Click to collapse
Because a kernel is the link between Hardware and ROM.
You can flash as many kernels as you wish, as long as they're compatible with your current ROM.
Brick bug shows up only in 4.0.4's kernels, that's why flashing a safe kernel (like siyah) is recommended to avoid it.
So I was having some issues with feedback during calls with almost all custom ROMS. I reverted back to the gingerbread stock rom via odin to see if it was just a ROM problem and I found the source of the initial problem. But now when I boot into the recovery, it won't flash any new ROM I want to go back to. I do the normal flash/wipe + the cache for good measure, and apply the zip and It'll say "Short write of /tmp/sideload/package.zip (no space left on the device)." But I have 4gb free on my phone so i'm definitely not out of space. I've tried the AOKP JB rom, shoshock, and the newest cyanogen mod. No luck on any of them.
What am I doing wrong?
Tell us more details about your process, from stock through root and kernel, and we can help you out better.
aspen1135 said:
So I was having some issues with feedback during calls with almost all custom ROMS. I reverted back to the gingerbread stock rom via odin to see if it was just a ROM problem and I found the source of the initial problem. But now when I boot into the recovery, it won't flash any new ROM I want to go back to. I do the normal flash/wipe + the cache for good measure, and apply the zip and It'll say "Short write of /tmp/sideload/package.zip (no space left on the device)." But I have 4gb free on my phone so i'm definitely not out of space. I've tried the AOKP JB rom, shoshock, and the newest cyanogen mod. No luck on any of them.
What am I doing wrong?
Click to expand...
Click to collapse
cyril279 said:
Tell us more details about your process, from stock through root and kernel, and we can help you out better.
Click to expand...
Click to collapse
Well the process is fairly straight forward. I think Ive explained the details as well as I can. I flashed the stock firmware through Odin and can't reflash any new rom or kernel. I made a nanbackup before doing this but the factory stocks kernel doesn't support backup/restore. I need to go from this old stock gingerbread rom back to shoshock or anything else to restore my backup.
In your explanation, I didn't see mention of how you rooted the device, or what custom-kernel you chose, or how (or if) you flashed the custom kernel. The stock recovery won't allow the installation of firmware that was not signed by Samsung, and Odin-flashing custom firmware is not the preferred method.
>>This Guide<< is the most up-to-date, and straight-forward method that I'm aware of for the I777, I highly recommend it.
aspen1135 said:
Well the process is fairly straight forward. I think Ive explained the details as well as I can. I flashed the stock firmware through Odin and can't reflash any new rom or kernel. I made a nanbackup before doing this but the factory stocks kernel doesn't support backup/restore. I need to go from this old stock gingerbread rom back to shoshock or anything else to restore my backup.
Click to expand...
Click to collapse
Once you're rooted and kernel'd, and can tell us what android version firmware you're trying to get to, we can better suggest which custom kernel to flash prior.
cyril279 said:
In your explanation, I didn't see mention of how you rooted the device, or what custom-kernel you chose, or how (or if) you flashed the custom kernel. The stock recovery won't allow the installation of firmware that was not signed by Samsung, and Odin-flashing custom firmware is not the preferred method.
>>This Guide<< is the most up-to-date, and straight-forward method that I'm aware of for the I777, I highly recommend it.
Once you're rooted and kernel'd, and can tell us what android version firmware you're trying to get to, we can better suggest which custom kernel to flash prior.
Click to expand...
Click to collapse
Sorry for not elaborating. The stock ROM (the one i'm on now) thats flash-able through odin, is pre-rooted.
I got it from this thread here: http://forum.xda-developers.com/showthread.php?t=1286432
But other than root, its completely stock gingerbread, Stock kernel, Bloatware, ETC. I'm trying to get to at least jelly bean or higher. I was on the shoshock rom before I decided to revert to the factory rom to test some things out. The signed package thing you mentioned makes sense because signature verification fails whenever i try to flash a different kernel. But it wont let me flash any of the jelly bean ROMS either (refer to my first post's error).
I visited the link you provided, and want to give the method a try. But mobile odin lite has been giving me constant trouble. it keeps saying I need to install another ad on in order to flash stuff and when I hit OK, the link takes me to my browser, but doesnt direct me to the web page that provides the ad-on download. Where do I go from here?
The add-on that mobile odin is trying to download is the i777 flash kernel that it needs to perform its magic. It's in post #10 of the mobile odin thread. Whether you use mobile odin lite or pro, you need this flash kernel. I'm not sure why it wouldn't download it from within the app.
aspen1135 said:
Sorry for not elaborating. The stock ROM (the one i'm on now) thats flash-able through odin, is pre-rooted.
I got it from this thread here: http://forum.xda-developers.com/showthread.php?t=1286432
But other than root, its completely stock gingerbread, Stock kernel, Bloatware, ETC. I'm trying to get to at least jelly bean or higher. I was on the shoshock rom before I decided to revert to the factory rom to test some things out. The signed package thing you mentioned makes sense because signature verification fails whenever i try to flash a different kernel. But it wont let me flash any of the jelly bean ROMS either (refer to my first post's error).
I visited the link you provided, and want to give the method a try. But mobile odin lite has been giving me constant trouble. it keeps saying I need to install another ad on in order to flash stuff and when I hit OK, the link takes me to my browser, but doesnt direct me to the web page that provides the ad-on download. Where do I go from here?
Click to expand...
Click to collapse
cyril279 said:
The add-on that mobile odin is trying to download is the i777 flash kernel that it needs to perform its magic. It's in post #10 of the mobile odin thread. Whether you use mobile odin lite or pro, you need this flash kernel. I'm not sure why it wouldn't download it from within the app.
Click to expand...
Click to collapse
Thank you thank you! I will try this out when I get a break from my classes. IDK why it wouldn't either. Much thanks!
aspen1135 said:
Thank you thank you! I will try this out when I get a break from my classes. IDK why it wouldn't either. Much thanks!
Click to expand...
Click to collapse
Just wanted to confirm that the mobile ODIN method worked and I now have my phone restored to how it was. Thanks again for all the help.