hello,
i always had HTC's and still have the ONE X
i would like to know if the firmwares update, updated other partitions, that custom roms dont update ?
if so, its a good thing to always update to the last firmware ?
Firmware updates basically include
- ROM (system environment)
- Kernel
- Mobile network modem
Updating ROM and Kernel is not required since the ROM of your choice already includes these. Additionally you might even have flashed another kernel.
So the only thing that remains is the modem which can quite easily be flashed through Odin or CWM.
So no need to update to Stock roms if you're running custom roms.
the - ROM (system environment) has only the /system ?
i see there are other imgs.
so... i think will be good.
boot.img
cache.img
hidden.img
modem.bin
recovery.img
system.img
we can always expect bug fixes and performances improvement in the latest roms, but some time it break up stuffs too(not yet so far in s3). so if you have less time better read the feedbacks in the sticky firmware thread and flash it later.
flashing an update via odin (tar file) updates all the partition
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 have owned multiple Vibrants, but I can't understand the problem with this one specifically that I recently purchased. It seems to be farcical, but it is the case.
The problem: Beside stock and CyanogenMod roms, no matter what other roms I installed, whether it is Paranoid Android, SlimBean, AOKP, the baseband gets undetected either immediately after flashing, or while using the device. This is even if the /radio/modem.bin file is still exist with the correct permission and the IMEI is correct. After the baseband become undetected, the only way to fix it is to reflash a rom.
Example: I might be using the phone fine with baseband available and then suddenly it disappeared while the phone is turned on or after a reboot (which then means no more phone number, no more signal, call and data capability).
Exception: The only time the baseband stay put is with stock Odin image or Cyanogenmod rom. I don't know why specifically its okay with CyanogenMod roms. If I flash a non-CyanogenMod roms file that have modem.bin included within it, then it will not work, the baseband still goes missing, ie AOKP and Paranoid Android rom.
Things I have tried that doesn't fix the problem:
-Odin JDF or KB5 + repartition -> KB5 kernel & modem CWM patch -> CM7 -> ICS Passion -> CM10 -> SlimBean or AOKP
(immediately after flashing SlimBean the baseband is no longer detected, even though /radio/modem.bin exist)
(after flashing AOKP / Paranoid Android, the radio is detected, but while using the phone or after a reboot, the baseband goes undetected)
-manually deleting the modem.bin file from /radio, then flashing another rom that has modem.bin included (doesn't help, unless its CM10)
-fixing permissions in CWM
-Odin JDF -> Kies update to Android 2.2 -> CM7, etc.
-Switch between Froyo and GB bootloaders
-Switching sim cards
Other:
-I bought this one used, the IMEI of the device doesn't seem to match with the IMEI on the box that the buyer gave. I don't know if this means anything though.
-Also I don't know about EU bug, but this device can detect both internal storage and sdcard slot without problem, but could this be related?
-Could this be kernel related and is there any kernel recommended to flash?
Do anyone have an Odin image of just the modem that I can try flashing? I can not flash CWM modem patches to the JellyBean roms since the patches are only compatible with the older version of CWM.
I would be perfectly content with CM10 only in this device if I can figure out how to add the sliding brightness bar feature that is available from AOKP.
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)
Just flashed 6.0.1 and am now seeing the battery percentage in values way above 100%. For example, my battery percentage is at 4,110%. Is anyone else seeing this?
Yeah I'm getting the same issue also.
Sent from my Nexus 9 using Tapatalk
Is this happening on a stock and unrooted device ???
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
oias.heeda said:
Mine is stock, rooted.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
kernal says 3.10.40-g909db78
[email protected] #1
fri aug 28 21:16:30 UTC 2015
before updating I was on elementalx
This has to do with the boot.img. I'm using chainfires modified one, but it is for MRA58N. Does anyone have the modified one for MMB29K? I might have to look into modifying myself but I've not done this before...
the.teejster said:
Every report I've read about this issue is due to someone not running the stock kernel. Does this apply to you ?
Reverting back to the stock kernal or installing a kernal that's been updated to support 6.0.1 seems to have solved the problem.
Click to expand...
Click to collapse
Makes sense. My N6 was doing this with a rooted kernel, and the problem went away when I flashed back to stock.
According to most accounts of this problem, the user forgot to flash the appropriate boot.img, vendor.img, or system.img before flashing the kernel/ROM.
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
Worked for me as well!
This worked perfect for me. I didn't need to reflash the system image either. Just the stock boot.img, then supersu, then ex kernel. All from within TWRP. Then reboot. That battery percentage was driving me nuts though. Thanks.
Neptaliuss said:
So I have a solution for my case!
I was originally on Stock 6.0 unencrypted and rooted, and running a custom Kernel (ElementalX). Then I flashed the stock 6.0.1 System.img and encountered this exact problem, and even updating my custom kernel to the latest (and supported) version did not fix things.
So this is what I did:
- Flash the stock 6.0.1 Boot.img (DON'T boot into System after this or it may Force-Encrypt, if you care about that).
- RE-Flash the stock 6.0.1 System.img
- Boot into your Custom recovery (TWRP for me)
- Flash SuperSU v2.61 - this is an experimental version but seems to work (I also had to ADB Push this zip file since I didn't want to boot into System yet)
- Flash the latest EX Kernel N9-4.05 (Also ADB Pushed this zip)
- Reboot to System
And that's it! all working back to normal now. I realise that most people won't need to go through all that trouble, but if you're like me and didn't want to do a clean install, or wanted to remain rooted/unencrypted/using a custom kernel, then this might help you!
Click to expand...
Click to collapse
here it is http://www.samsungdeck.com/2016/04/26/samsung-rolls-security-update-galaxy-a3-europe/
Hi there. I just flashed the BPC2 upgrade to my A300FU via Odin and it failed. Since then, it seems that every rom I flash fail (even those I previously flashed with no trouble at all). Something like a partition problem (wrong size of some...)
Anyway, I could solve this by flashing the BOL3 version which failed, but immediately after flash the autoroot by Chainfire then original recovery to have my phone working.
But I tried again to flash any stock rom and it fails the same every single time. Someone would have a solution?
Also I cannot use the BPC2 version, autoroot seems to not work on it. Maybe related to security updates?