Long story short, I decided to flash a zip file of the CatOs 1.2 into my stock firmwarevIt doesn't have it.
I really need that for some work but don't know if that is possible?
Or is there any software or a .zip that I can flash to install this component of the stock firmware
Related
Ok, I gotta be a noob for a second. I've been married to this message board since Thanksgiving when I got my Rezound, I've read nearly every word written over the last week since we got unlock/ root..... but I am lost on one thing....
What is this boot.img file all about? There is a lot of talk about how to flash it, but I am not clear on when or why you need it. It sounds like it's part of the ROM zip file, but I'm running BAMF and it does not contain a boot.img file, and it doesn't appear that it was needed in this case since everything is working.
Can someone hook me up with a quick 101 course on this file?
Basically that file is the kernel of the OS.
The big deal with it is the fact that we can not flash the file directly as part of the normal ROM flashing procedure. This is because we do not have S=off. No ROMs for the Rezound will include a boot.img in the .zip, other devices with S=off will have the boot.img
This means that whenever we flash a ROM, the kernel is untouched by the ROM flash, we must then use fastboot to flash the kernel necessary for the ROM.
This isn't a big deal for ROMs strictly based on the stock ROM. Just flash the ROM and go, you can even switch between stock based ROMs with no problem or need to flash the kernel. (as long as you have not flashed a different kernel)
Now if the ROM is stock based but uses a kernel different than the stock kernel, you must flash the kernel it comes with after you flash the ROM.
This goes for any ROMs not stock based as well. AOSP, MIUI, and others will need to have a separate boot.img file available for download that you will need to flash in fastboot in order for the ROM to boot.
The real problem comes when you want to run a custom kernel (One that did not come with the ROM originally, or not purposely designed for the ROM you are using) This is because there are files within the ROM itself that are unique to the kernel being used. If you want to use a custom kernel then you must alter these files to be compatible with the new kernel. you then must flash those files into the ROM before you flash the new kernel.
Luckily we have a new tool that can do this for us, but the process is still a pain.
Marine6680 said:
Basically that file is the kernel of the OS.
The big deal with it is the fact that we can not flash the file directly as part of the normal ROM flashing procedure. This is because we do not have S=off. No ROMs for the Rezound will include a boot.img in the .zip, other devices with S=off will have the boot.img
This means that whenever we flash a ROM, the kernel is untouched by the ROM flash, we must then use fastboot to flash the kernel necessary for the ROM.
This isn't a big deal for ROMs strictly based on the stock ROM. Just flash the ROM and go, you can even switch between stock based ROMs with no problem or need to flash the kernel. (as long as you have not flashed a different kernel)
Now if the ROM is stock based but uses a kernel different than the stock kernel, you must flash the kernel it comes with after you flash the ROM.
This goes for any ROMs not stock based as well. AOSP, MIUI, and others will need to have a separate boot.img file available for download that you will need to flash in fastboot in order for the ROM to boot.
The real problem comes when you want to run a custom kernel (One that did not come with the ROM originally, or not purposely designed for the ROM you are using) This is because there are files within the ROM itself that are unique to the kernel being used. If you want to use a custom kernel then you must alter these files to be compatible with the new kernel. you then must flash those files into the ROM before you flash the new kernel.
Luckily we have a new tool that can do this for us, but the process is still a pain.
Click to expand...
Click to collapse
Thanks Man This Information Is Greatly Appreciated. I Definitely Had The Right Idea In My Head And Now You've Clarified That For Me And Anyone Else Who's Wondering.
Much thanks Marine, that's exactly what I was looking for. My confusion has been alleviated... for now at least....
I currently have busines gingersense ,which by the way is sweet ,thanks Nills ,I have my stock Rom backed up w/ amon ra. Now if I want to try business ICS and then go back to gb, will I be able to reload in recovery like any other Rom or does this require special steps, I have read about other ics roms not being able to recover so easily, if so would anybody care to do a step by step. Thanks ...
Sent from my ADR6425LVW using XDA App
You need to flash the stock kernel to use GB ROMs if you have used an ICS ROM (a copy is located in scotts GB based ROMs, just unzip the file and find the boot.img)
You can flash the kernel before or after you restore the backup.
I find it easier to do before, then selecting the reboot to recovery option, allowing me to then flash the new ROM or backup.
Use the cleanflash tool to flash the kernel (boot.img) if you need a simple method.
Would the following work as a way to try out, for example Cyanogenmod 10. I am currently running a 4.1.2 install (pretty much stock just rooted/cwm via Philz as per the tutorial). I have a complete backup made via Philz recovery of this rom along with the kernel (which I believe is still stock from that) and efs.
1) Install a custom kernel (eg. dorimanx 9.x?) via the Philz recovery.
2) Install cm-10.2-20140102-NIGHTLY-i9100.zip.
3) To return to the original rom, reflash the original kernel (with whatever CWM is included in dorimanx) - then reflash the backed up rom via the same recovery?
I hope this is clear enough a question.
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Donnie Sins said:
I believe you have to flash a stock rom through Odin, to return to complete stock. Just flashing a stock kernel isn't enough, and is surely not going to work (so don't do it).There are also tutorials how to remove the yellow triangle afterwards.
Please correct me if I'm wrong
Click to expand...
Click to collapse
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
TopherBrink said:
This is the part I'm most unsure of. Ideally I'm trying to figure out the process that lets me go from CM10.2 (and whatever recovery) to the point I am running the backed up rom rooted with PhilZ-cwm6-XWLSW-XEU-5.06.1-signed.zip again. Very confused on how to do so.
Click to expand...
Click to collapse
Topher,
If you have rooted and cwm via philz, you already have a modified kernel installed. I believe the philz-cwm6 should be as close to stock kernel with the CWM incorporated. You don't need to add another kernel, because it will be replaced when you install the custom ROM. You should just be able to flash the cm10.2 via philz or via odin. You can then flash the dormanix kernel if you want - can't comment on that kernel - or if it has cwm included.
I would also suggest that you consider backing up you /efs folder (one with you imei information etc) prior to flashing any custom roms. People have been using hcKtool to do the backups and also an actual copy as well.
Depending on the custom rom, you may have connection problems with your network. So you may want to consider keeping a copy of your modem.bin file from your stock rom handy in case you need to flash onto the custom rom.
If you want to go back to stock, then you just need to flash the stock rom - you can check sammobile website for your stock rom or use the backup that you made.
I should point out that I have yet to do any of the above - I gathered this from reading the forums. Some more experienced forum users can add corrections. I rooted my phone a couple of months ago and now considering installing custom rom in the next couple of months.
Thanks.
if u flash a custom rom (cm10.2 for example), it already included kernel as well. so if u want to try out other custom kernel, i can flash it after you are done flashing a custom rom but make sure it is compatible with your android version. (u cant use custom kernel that not support android 4.3 with a custom rom running android 4.3)
I have D/L a few stock recovery .img files with different file sizes.
Q: Are all TMO stock recovery images same?
I have 4.3 sense 5.0 latest firmware and would like the kitkat OTA.
Q: What stock recovery .img do I need to flash and where may I get it?
Thanks.
Oh this is for USA country code..NEW YORK.
I am rooted using the TWRP recovery.. latest 3.3
Thanks.
Whenever I have had need to swap back over to the stock recovery (such as the KK upgrade, which I'm just getting finished up right now) I've always used the stock recovery image from the zip file that Behold_this puts together in his thread, http://forum.xda-developers.com/showthread.php?t=2355814
I think it's been updated now to include the KK firmware, so you may or may not want to download the previous version. If you are curious, the size of the recovery.img that I have is 11.6MB (12,245,248 bytes).
After trying a few custom ROMS, I decided to revert to full stock. CM12 did mess up with my recovery : it installed Cyanogen Recovery, even if I didn't want to and even if the option to install it was disabled in the dev settings ! Since then, I can't flash another ROM or if I can, it will be buggy for no reason (apps not working, etc.).
So I decided to revert to stock with a proper FTF file using Flashtool in flashmode...however, it won't work !
It won't flash the rom properly : the flash last 3 seconds. It says it went fine but as you can imagine, in 3 seconds, it didn't flash anything really. As a mater of fact, if I'm booting the tablet, I'm still under CM12.
Is there a way to revert to stock in another way ? I tried using Fastboot, after extracting the .ftf file but same issue : it looks like it's flashing but it's way too short to flash the system.
Any idea ?
Screw CM12 anyway, forcing their crappy recovery is a **** move.