Related
I've played with a lot of great kernels lately, but it is getting hard to compare them against the stock kernel, as I haven't used that in a while. I'd like to get back to the stock kernal (using a almost-stock ROM)
My question is: How can I get back to the stock kernel? Is there a zip file I can flash somewhere (searched and couldn't find)? I could Nandroid back, but I don't want to have to redo a bunch of tinkering I've done lately.
If not, can I push the stock kernel to the phone via ADB? After searching, it seems that the kernel is in the boot.img? Can I just grab a stock boot image from FRG83 and flash it to the phone via ADB command line/ terminal? Something tells me it's not that easy.
I've also read alot about building a kernel in linux using repositories and repacking it. I'm not sure I am up for that quite yet...
tech338 said:
I've played with a lot of great kernels lately, but it is getting hard to compare them against the stock kernel, as I haven't used that in a while. I'd like to get back to the stock kernal (using a almost-stock ROM)
My question is: How can I get back to the stock kernel? Is there a zip file I can flash somewhere (searched and couldn't find)? I could Nandroid back, but I don't want to have to redo a bunch of tinkering I've done lately.
If not, can I push the stock kernel to the phone via ADB? After searching, it seems that the kernel is in the boot.img? Can I just grab a stock boot image from FRG83 and flash it to the phone via ADB command line/ terminal? Something tells me it's not that easy.
I've also read alot about building a kernel in linux using repositories and repacking it. I'm not sure I am up for that quite yet...
Click to expand...
Click to collapse
If you can get a stock boot.img (that you're sure matches up with what you're running), you should be able to flash that while in hboot mode with the following command:
Code:
fastboot flash boot boot.img
errr I would definitely advise against just flashing the boot.img
Those updated kernels often bring re-compiled modules (like for WiFi), if you just flash the boot.img, the stock kernel won't be able to interface with those modules and you could have all kinds of bugs.
Plus (although I'm not sure), I think you need more than the boot.img and modules...
Good catch. I forgot about that aspect. Though I suppose you could flash the boot.img and push the various required modules. But it would really just be easier to reflash a stock rom.
From what I searched this thread and others, I believe this is not possible, because a CRC check in bootloader or kernel I think.
Now that sources are out, couldn't we flash RECOVERY + Kernel (maybe downgrade bootloader) at the same time and avoid the bootloop?
This is not my current phone anymore so I'm not really up to date to the new developments, but, there is nooby's repack, that allows CWM, couldn't that mod somehow be applied directly to 30B (or any ICS version) trough adb or something?
Alternate solution: ?
Going to recovery atm resets the phone to factory settings, as that is the way the default recovery acts, and actually I don't need a working recovery, a way to block the phone to reset itself is also acceptable!
Flash Image Gui
I think my question was not understood properly, so I'll try to reformulate it:
Flash Image Gui is a program that allows kernel images to be flashed on HTC one S directly from Android. If the cip inside our Black is somehow compatible, we could hack the program to flash a recovery friendly kernel.
Now, is that possible?
mihaiolimpiu said:
I think my question was not understood properly, so I'll try to reformulate it:
Flash Image Gui is a program that allows kernel images to be flashed on HTC one S directly from Android. If the cip inside our Black is somehow compatible, we could hack the program to flash a recovery friendly kernel.
Now, is that possible?
Click to expand...
Click to collapse
Problem is nothing to do with kernel. Possible reason for it not working :
Bootargs incompatible
Bootloader locked
CRC bootarg forbids running custom kernel/recovery.
I'm leaning towards the 3rd one, but either way it won't work.
It's not so hard making a program like that for our phone. You just need a program that extracts the boot.img replaces the new zImage and packs the boot.img again and flash it to device. You can make a script that does that from your phone.
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...
As I understand it by reading the threads, FAQ, etc. I do NOT need root to install CWM. Is that correct?
I'm trying to get my head wrapped around the differences, because on Samdung devices, you cannot get CWM installed without root.
The bottom line is I want to install CyanogenMod. That's what I'm bying the Xperia for.
I need both CWM and unlocked bootloader to do that, correct?
Hi again lol
If your device is unlocked, the best way to get recovery is to flash a kernel that has recovery included.
Usually CM comes in a zip file, inside the zip there is a boot.img file. Extracting that file and flashing it via flashtool provides you with a recovery, root, and a bootable kernel. From there on, you'll only need to flash the zip file from recovery to get a working rom.
DrKrFfXx said:
Hi again lol
If your device is unlocked, the best way to get recovery is to flash a kernel that has recovery included.
Usually CM comes in a zip file, inside the zip there is a boot.img file. Extracting that file and flashing it via flashtool provides you with a recovery, root, and a bootable kernel. From there on, you'll only need to flash the zip file from recovery to get a working rom.
Click to expand...
Click to collapse
That's exactly what I needed to know, because on the S3, the recovery is separate, so flashing the zip doesn't do anything to the custom CWM recovery version you have installed.
Just to clarify: The CM file includes the ROM, the kernel, and a CWM recovery in the zip and the current CWM recovery will be overwritten by it?
I can use flashtool and I don't need to install the zip via CWM recovery?
donalgodon said:
That's exactly what I needed to know, because on the S3, the recovery is separate, so flashing the zip doesn't do anything to the custom CWM recovery version you have installed.
Just to clarify: The CM file includes the ROM, the kernel, and a CWM recovery in the zip and the current CWM recovery will be overwritten by it?
I can use flashtool and I don't need to install the zip via CWM recovery?
Click to expand...
Click to collapse
The last time I checked, yes, kernel, rom and recovery are included in the zip. Although I don't know about latest 4.3 builds, been away from CM a couple of weeks, but the first builds lacked recovery.
You will still need to flash the zip via recovery, because flashtool uses another type of images (.ftf files). On flashtools you can only flash the kernel (boot.img), the kernel includes recovery, from recovery you can flash the zip file containing the rom. So you need two separate steps to flash CM for the first time. Next time, for updating, you will need to flash the zip via recovery and the recovery will be overwritten.
DrKrFfXx said:
The last time I checked, yes, kernel, rom and recovery are included in the zip. Although I don't know about latest 4.3 builds, been away from CM a couple of weeks, but the first builds lacked recovery.
You will still need to flash the zip via recovery, because flashtool uses another type of images (.ftf files). On flashtools you can only flash the kernel (boot.img), the kernel includes recovery, from recovery you can flash the zip file containing the rom. So you need two separate steps to flash CM for the first time. Next time, for updating, you will need to flash the zip via recovery and the recovery will be overwritten.
Click to expand...
Click to collapse
So, okay:
I use the stock kernel/ROM currently installed to use flashtool to flash the extracted kernel from the zip, but to use the custom kernel, I need an unlocked bootloader.
Is that correct?
You mentioned in the other thread your comments on CM. I am curious to know more of what you think. In the S3, the problems were related to the lack of userspace drivers, but it was my understanding that the Z was more friendly and had better driver support.
Is the sound quality that much different? By that, I mean is there increased signal noise? I'm not into special effects and tweaks, but the Wolfson DAC on the S3 was about the best I've heard and didn't need anything to make it sound great. What the lack of userspace drivers did was introduce noise into the audio that did not really exist on stock.
I'd appreciate your thoughts on the camera and sound. I also assumed the battery drain issues would be resolved. Is that not the case? I mean, with proper managment, I was able to approach stock battery levels, camera was fine, but sound was never close to stock.
So, okay:
I use the stock kernel/ROM currently installed to use flashtool to flash the extracted kernel from the zip, but to use the custom kernel, I need an unlocked bootloader.
Is that correct?
Click to expand...
Click to collapse
You can't install any separated kernel if you are locked. Because it needs ADB access via fastboot, and on locked devices you have no access to that option. Kernels with embedded recovery are custom, unsigned kernels. Locked devices don't run unsigned kernels.
If you are locked you will need to root first to install a recovery. But even with recovery installed, you won't be able to install anything but stock (kernel) based roms.
You mentioned in the other thread your comments on CM. I am curious to know more of what you think. In the S3, the problems were related to the lack of userspace drivers, but it was my understanding that the Z was more friendly and had better driver support.
Click to expand...
Click to collapse
¡
The last time I checked the sound quality from the headphone out, the sound was unbearable. High noise, low instrument separation and soundstage, lack of bass extension and recessed mids. Very poor quality when paired to my Sennheiser Momentum.
I'd appreciate your thoughts on the camera and sound. I also assumed the battery drain issues would be resolved. Is that not the case? I mean, with proper managment, I was able to approach stock battery levels, camera was fine, but sound was never close to stock.
Click to expand...
Click to collapse
I heavily underlvolted my device, greenify every other app, etc, and I was barely getting 4.5h of screen time.
On stock based I am getting 6h of screen time. Same settings. Same brightness.
Camera launches faster on CM, much much faster, so point and shoot might work better on CM. But there seem to be too much noise, even in normal light conditions.
Hello all,
as long as I would like to test new CM12 official nightlies as they become available for my Xperia T, I'd also like to have a fast and easy way to revert back to my previous ROM.
This would be easily done with the backup and restore function of any CWM based recovery, but every time I flash a nightly I get my recovery replaced by Cyanogen's one, that (AFAIK) lacks this useful feature.
Is there any way to prevent my current recovery from being replaced every time I flash a nightly, or a simple way to put it back?
I tried hard not to, but today I ended up restoring bootloader lock, stock firmware and all, then repeating all the steps to install a custom recovery.
Please, tell me there's another way 'round it.
You can flash a boot.img that includes CWM before restoring your backup.
I recommend DoomKernel for this purpose.
Another way would be to flash a revovery for FOTA partition, which will replace all recoveries in kernel.
I flashed DoomKernel v12 via fastboot and it worked really nicely. It's a fast way to put a recovery on my device when I want to flash something, and I can even choose what recovery to use. Thanks!
Having installed a FOTAKernel recovery, are there any precautions I must take while flashing other ROMs if I want to keep the recovery in place? Also, what operations will erase it or make it unavailable?
Darsil said:
I flashed DoomKernel v12 via fastboot and it worked really nicely. It's a fast way to put a recovery on my device when I want to flash something, and I can even choose what recovery to use. Thanks!
Having installed a FOTAKernel recovery, are there any precautions I must take while flashing other ROMs if I want to keep the recovery in place? Also, what operations will erase it or make it unavailable?
Click to expand...
Click to collapse
No rom I know of contains an integrated FOTA recovery, so you shouldn't have to worry about that when flashing a new rom.
The only way to revert to stock recovery is to flash a stock ftf via Flashtool.