MAJOR UPDATES (MAJOR THANKS TO THE FIRMWARE TEAM!!!)
AT&T 4.0.4 ICS FIRMWARE (for AT&T users on the official final ICS to return to stock ICS) - SEE HERE
MEARET, SEARET, HKTW, ASIAOPS, CHN 4.0.4 ICS FIRMWARES - SEE HERE
INTRO
With the arrival of ICS, and with the multiple international versions of the A2, it's getting kind of confusing about who should use what FXZ package to return their phone to stock when in trouble. Let's try to straighten this out, shall we?
The purpose of this thread is to clear up the confusion a bit, and for anyone to post general questions about fxz packages and processes.
First off, there are multiple threads, including JRW 28's great Beginner's Guide, which go over the process of flashing the "official" stock images and files, also known as the fxz, so I will be brief. And, I apologize beforehand for the slant towards AT&T A2 users, but it's what I am most familiar with - and we seem to have gotten the worst of it
NOTE TO AT&T A2 USERS ON OFFCIAL FINAL ICS
UPDATE 10/29/12 - new 4.0.4 FXZ for ATT users is available HERE
-You can not downgrade back to GB. The FXZ package in the above link should get you back to stock 4.0.4 ICS
FXZ FOR AT&T A2 USERS ON ICS (FIRST LEAK ONLY)
That, being said, anyone on the first AT&T ICS leak has a choice to flash back to stock 2.3.5 or 2.3.6 Gingerbread by using one of the fxz packages found in this thread ONLY! You may be on any one of the appropriate ROM's that are provided in the dev section, and still use these fxz's as long as you were originally on the first AT&T ICS leak. Note that your bootloader will still remain ICS version A0.72.
NOTE TO NON-AT&T A2 USERS
If you are on an another version of the A2 besides AT&T (and that's not only the actual carrier, AT&T is typically printed on the phone) then you need to locate the proper fxz package for your device. It has been noted that some ICS users other than AT&T, may still fxz back to 2.3.6 regardless of official ota or not. For now, you are kind of on your own with that, but I hope to clear that up and confirm with this thread. See below for the link to available fxz packages.
WHAT YOU NEED
I just came across this page, which looks like it has what we need:
- RSDLite (6.0 is the latest)
- Moto Drivers (you should already have them installed if you've used your USB cable in every mode)
Also needed:
- at least 40% battery left (actual needed remaining battery varies, but 40% is a relatively safe number)
- rear USB port on your computer (or a very reliable one on your laptop)
Next - the proper fxz package... A dedicated and resourceful group of individuals known as The Firmware Team (Kent_lkc - Kwachu - daywalker04 - Pzyduck - Skrilax_CZ) hunts down, or produces from thin air, Motorola OEM firmwares and maintains this site (and others): sbf.droid-developers.org Be sure to give them a big THANKS if you see them around the forums!
SEE HERE >>> http://sbf.droid-developers.org/edison/list.php <<< for available A2 fxz packages.
FXZ DIRECT LINKS
!!ONLY USE THE ORIGINAL FIRMWARE/REGION THAT CAME ON YOUR PHONE!!
ATT US ICS LEAK#1 USERS ONLY (from first ICS leak to GB)
See here: [UTILITY] Return to GB from ICS fxz script -- Now includes 2.3.6 fxz 09/26/2012
ATT US
2.3.5 (not really needed - but, if you do, remember the replace.zip)
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip
2.3.6 (GB to GB.. for those currently on GB only, who have never installed ICS)
InlineFlashing_edison_5.5.175.25_cfc_p3_APBP.xml.zip
4.0.4 (will return you from ICS, or one of the JB-based roms to final/official stock at&t 4.0.4)
InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip
Retail Asian (SEARET)
2.3.5 (fully compatible with all versions of ICS & GB)
5.5.1-EDEM-27-SEARET_cfc.xml.zip
2.3.6 (fully compatible with all versions of ICS &GB)
5.5.1-EDEM-28-37-SEARET_cfc.xml.zip
Retail South Africa / UAE (MEARET)
2.3.5 (fully compatible with all versions of ICS & GB)
5.5.1-EDEM-27-MEARET_cfc.xml.zip
2.3.6 (fully compatible with all versions of ICS & GB)
5.5.1-EDEM-28-37-MEARET_cfc.xml.zip
Retail Hong Kong / Taiwan (HKTW)
2.3.? (not sure of version or compatibility - see jim's note - please confirm)
5.5.1-1_GC-90_EDSHKTW-2_cfc.xml.zip
2.3.? (not sure of version or compatibility - see jim's note - please confirm)
5.5.1-1_GC-90_EDSHKTW-6_cfc.xml.zip
2.3.? (not sure of version or compatibility - see jim's note - please confirm)
5.5.1-1_GC-90_EDISON-11_HKTW_cfc.xml.zip
2.3.? (not sure of version or compatibility - see jim's note - please confirm)
5.5.1-1_GC-109_HKTW_cfc.xml.zip
Asia (Operator) (ASIAOPS)
2.3.5 (not sure of compatibility, please confirm)
5.5.1-EDEM-27-ASIAOPS_cfc.xml.zip
2.3.6 (not sure of compatibility, please confirm)
5.5.1-EDEM-28-37-ASIAOPS_cfc.xml.zip
Retail Chinese (CHN) (please confirm version and compatibility)
5.5.1-1_GC-90_EDISON-11_CHN_cfc.xml.zip
China Unicom (CU) (please confirm version and compatibility)
5.5.1-1_GC-90_EDISON-11_CU_cfc.xml.zip
Telecom New Zealand (TNZ) 2.3.6
5.5.1-EDEM-28-TNZ_cfc.xml.zip
Unknowns
(IUSACELL-MX): 5.5.1-EDL-32-IUSACELL-MX_cfc.xml.zip
(UNEFON-MX): 5.5.1-EDL-32-UNEFON-MX_cfc.xml.zip
---BE PATIENT AND LET THE FLASHING PROCESS COMPLETELY FINISH---
Looks good everything on order awesome work!!!!!
Edit: Not to sure about if this could go on OP Check it out????? If no good will remove from my post.....
alteredlikeness said:
NOTE TO NON-AT&T A2 USERS
If you are on an another version of the A2 besides AT&T (and that's not only the actual carrier, AT&T is typically printed on the phone) then you need to locate the proper fxz package for your device. It has been noted that ICS users other than AT&T, may still fxz back to 2.3.6 regardless of official ota or not. For now, you are kind of on your own with that, but I hope to clear that up and confirm with this thread.
Click to expand...
Click to collapse
Does the "locked bootloader can only be upgraded" feature prevent us from fxzing GB after ICS upgrade? Obviously I don't want to brick by trying the same, but is there any way to (1) check current bootloader version in phone, (2) unzip a fxz and check for bootloader version (in some file name), and (3) compare the versions of 1 and 2 and attempt fxzing only if 1=2. I'd really like to know if I can fxz back if I mess things up.
I wish a ICS fxz leaks from Motorola.
Thanks for putting this together, hopefully this will answer a lot of questions for everyone unsure of what they can/should do. Nice work, alteredlikeness! :thumbup:
Sent from my rooted Mayan Calendar
Excellent condensed info. Could this be sticky material?
hankbizzo5 said:
Looks good everything on order awesome work!!!!!
Edit: Not to sure about if this could go on OP Check it out????? If no good will remove from my post.....
Click to expand...
Click to collapse
Thanks man. Yup, I think that script works for at&t 2.3.6 users to flash back to 2.3.5 - I have never used it.. but, good to leave the link as a reference. In theory, one might be able to take the script file from that and use it with the 2.3.6 package.
kousik said:
Does the "locked bootloader can only be upgraded" feature prevent us from fxzing GB after ICS upgrade? Obviously I don't want to brick by trying the same, but is there any way to (1) check current bootloader version in phone, (2) unzip a fxz and check for bootloader version (in some file name), and (3) compare the versions of 1 and 2 and attempt fxzing only if 1=2. I'd really like to know if I can fxz back if I mess things up.
I wish a ICS fxz leaks from Motorola.
Click to expand...
Click to collapse
Well, I assume you are not using an at&t phone, so I am still hoping to gather more info for you guys here.
But, to my understanding, it's not so easy as to just compare bootloaders versions - those will change and stay changed (0.65 to 0.72, I believe).
What we did in order to use the 2.3.6 fxz (from the link in the OP) for ICS was to remove the mbmloader.bin from the package and the .xml file. This allowed us to flash to gb from the first att ics leak, but keep the ICS bootloader.
To use the 2.3.5 fxz for returning from 2.3.6 (and later from ics leak#1), we needed a few files from the 2.3.6 ota and to edit the xml. (Well, jim had to put a bit more into it for the leak#1 fxz... some .img files if I'm not mistaken - thanks again, Jim!) - but then we got the 2.3.6 fxz.
Still hoping to get some more info and clear everything up for the non-att users, and we definitely don't want anymore bricks around here..
Sent from my phone's mind
Hey alteredlikeness, you might also mention that the HK/TW phones are exactly like the att versions, in that their ICS leak # 1 is just like ours, with the same hacks needed for their fxz, and that their ICS OTA/ leak # 2 is prolly just like the att one as well.
I'm at risk of asking a stupid question, but here goes - this post covers flashing back to stock. What if were to OTA to ICS and then try to flash a ROM? Would that be affected?
Feel free to punch me if you want this in a different place or a different sub-forum
Pilgrimtozion said:
I'm at risk of asking a stupid question, but here goes - this post covers flashing back to stock. What if were to OTA to ICS and then try to flash a ROM? Would that be affected?
Feel free to punch me if you want this in a different place or a different sub-forum
Click to expand...
Click to collapse
Lol.. it's fine. But that brings up a good point that I should have made more clear in the OP...
Whether you are on leak#1 or any other version of ICS firmware, you may still do whatever you want with your phone (of course read the OP of the ROM thread, and make sure it's for ICS). The difference is that only the folks that were originally on leak#1 have a way out by fxz if the proverbial kaka hits the fan.
So, installing a ROM should not affect your ability to fxz or not. It basically only changes the system partition.
But, things like ROM Toolbox, mods for different system versions, other hacks gone wrong, etc.. - can send you in a bootloop.
Things like having no valid backup, testing new builds or otherwise botching cwm recovery, etc.. - can force you to require an fxz.
Also, flashing the wrong fxz should be avoided at all costs - that can brick you for good.
Sent from my phone's mind
alteredlikeness said:
Lol.. it's fine. But that brings up a good point that I should have made more clear in the OP...
Whether you are on leak#1 or any other version of ICS firmware, you may still do whatever you want with your phone (of course read the OP of the ROM thread, and make sure it's for ICS). The difference is that only the folks that were originally on leak#1 have a way out by fxz if the proverbial kaka hits the fan.
So, installing a ROM should not affect your ability to fxz or not. It basically only changes the system partition.
But, things like ROM Toolbox, mods for different system versions, other hacks gone wrong, etc.. - can send you in a bootloop.
Things like having no valid backup, testing new builds or otherwise botching cwm recovery, etc.. - can force you to require an fxz.
Also, flashing the wrong fxz should be avoided at all costs - that can brick you for good.
Sent from my phone's mind
Click to expand...
Click to collapse
That, my friend, was extremely helpful, concise, and clear. Thank you.
alteredlikeness said:
Lol.. it's fine. But that brings up a good point that I should have made more clear in the OP...
Whether you are on leak#1 or any other version of ICS firmware, you may still do whatever you want with your phone (of course read the OP of the ROM thread, and make sure it's for ICS). The difference is that only the folks that were originally on leak#1 have a way out by fxz if the proverbial kaka hits the fan.
So, installing a ROM should not affect your ability to fxz or not. It basically only changes the system partition.
But, things like ROM Toolbox, mods for different system versions, other hacks gone wrong, etc.. - can send you in a bootloop.
Things like having no valid backup, testing new builds or otherwise botching cwm recovery, etc.. - can force you to require an fxz.
Also, flashing the wrong fxz should be avoided at all costs - that can brick you for good.
Sent from my phone's mind
Click to expand...
Click to collapse
So, at the risk of asking another stupid question if I am an U.S. AT&T customer on 2.3.6 GB that was flashed OTA (shortly after I got my A2), and I want to give the ICS leak #1 a try, I should go back to 2.3.5 using the ZIP file linked above before flashing the leak, correct? I'm asking here because I've read so many threads now, I can't keep the info straight any longer. I was hoping that AT&T would bring us at least up to ICS over the air, but it's looking like that ain't gonna happen, so I want to make sure I don't brick my A2, as it is no longer under warranty, and I can't upgrade for another year. TIA!
Scrondar said:
So, at the risk of asking another stupid question if I am an U.S. AT&T customer on 2.3.6 GB that was flashed OTA (shortly after I got my A2), and I want to give the ICS leak #1 a try, I should go back to 2.3.5 using the ZIP file linked above before flashing the leak, correct? I'm asking here because I've read so many threads now, I can't keep the info straight any longer. I was hoping that AT&T would bring us at least up to ICS over the air, but it's looking like that ain't gonna happen, so I want to make sure I don't brick my A2, as it is no longer under warranty, and I can't upgrade for another year. TIA!
Click to expand...
Click to collapse
Several steps involved:
#1 Flash back to 2.3.5
#2 OTA to 2.3.6
#3 Don't log into anything or do anything - not even Google services
#4 Flash ICS leak #1
Be informed, though, that a soak test for ICS is currently underway and we should be getting an official ICS OTA soon.
This is all outlined in the following thread
Scrondar said:
So, at the risk of asking another stupid question if I am an U.S. AT&T customer on 2.3.6 GB that was flashed OTA (shortly after I got my A2), and I want to give the ICS leak #1 a try, I should go back to 2.3.5 using the ZIP file linked above before flashing the leak, correct? I'm asking here because I've read so many threads now, I can't keep the info straight any longer. I was hoping that AT&T would bring us at least up to ICS over the air, but it's looking like that ain't gonna happen, so I want to make sure I don't brick my A2, as it is no longer under warranty, and I can't upgrade for another year. TIA!
Click to expand...
Click to collapse
No, you do not need to go back to 2.3.5. There are fxz's for 2.3.6 (the official one if you have never been on ICS, or the one from Jim's fxz thread for the first leak only).
And, the ics ota will only fail if you have modded/removed system files and/or installed a bootstrap/cwm on boot.
Also, the official ota for at&t is coming within a matter of days..
Sent from my phone's mind
Well, since both the responses say that the official update is imminent, I'll be patient a bit longer. Thanks!
Cualquier novedad o info que tengamos, sera publicado al instante el Firmware, por Firmware TEAM
===============================================
Any news or info we have, will be published instantly Firmware for Firmware TEAM
Sorry my bad english
Pzyduck said:
Cualquier novedad o info que tengamos, sera publicado al instante el Firmware, por Firmware TEAM
===============================================
Any news or info we have, will be published instantly Firmware for Firmware TEAM
Sorry my bad english
Click to expand...
Click to collapse
Thank you and the Firmware TEAM for all of the mysterious and hard work!! Please do continue to keep up the good work
===============================================
Gracias a usted y Firmware TEAM para todo el trabajo duro y misterioso! Por favor, siga manteniendo el buen trabajo
Sorry for my bad spanish... thank goodness for google translate.
alteredlikeness said:
Thank you and the Firmware TEAM for all of the mysterious and hard work!! Please do continue to keep up the good work
===============================================
Gracias a usted y Firmware TEAM para todo el trabajo duro y misterioso! Por favor, siga manteniendo el buen trabajo
Sorry for my bad spanish... thank goodness for google translate.
Click to expand...
Click to collapse
+1000
I also want to thank the moto firmware team!! Keep up the excellent work!
Sent from my SAMSUNG-SGH-I747 using xda premium
Consider this bumped..
Thank you!
Thanks a lot for the guide. Just the information I was looking for
PS: I already hit the thanks button
I have MEARET MB865 in middle east region.
The 27 spl is 2.3.5
The 28.37 is 2.3.6
Good luck that i can flash any 2.3.5 or 2.3.6 from MEARET or SEARET spl's anytime.
And I tried all ICS leaks including ATT firms.
But I never tried to flash any ATT spl's
Related
Okay, so anyone here still on FROYO?? And I nid some help if I should flash to DXKP9 or not. THX!!
I'm pretty sure DXKP9 is just an Asia-specific version for XXKPQ.
and flashing to GB depends on you.
I've just read and confirmed that GB has dark video recording. If you're not bothered by that, flash it.
Just read up or find some comparison videos on YouTube.
!n0x said:
I'm pretty sure DXKP9 is just an Asia-specific version for XXKPQ.
and flashing to GB depends on you.
I've just read and confirmed that GB has dark video recording. If you're not bothered by that, flash it.
Just read up or find some comparison videos on YouTube.
Click to expand...
Click to collapse
And y are so many people on XXKPQ?? And are there any improvements from FROYO to DXKP9? I am on my custom ROM based on FROYO now... THX!!
Yeah, I'm on KB4 and haven't been offered any updates for my UK unlocked I9003.
I know that I can upgrade to GB using Odin, but I'm reluctant to flash non-UK firmware onto the device. It seems only Russian ROMs are available on samfirmware.com
I did complain to Samsung UK and they've confirmed that GB is coming, but they can't say when. I don't actually think there have been any UK updates since May 2011, so I have no idea what they're playing at.
crazbanditz said:
And y are so many people on XXKPQ?? And are there any improvements from FROYO to DXKP9? I am on my custom ROM based on FROYO now... THX!!
Click to expand...
Click to collapse
Many are on XXKPQ since most of the mods/ROMs/themes being developed at the moment (with the exception of some, e.g. CM9, CM7 (?) and MIUI(?)), are based on this firmware.
DXKP9 is Gingerbread-based, so there's bound to be improvements. You can try Googling the differences.
OR
http://www.differencebetween.com/difference-between-android-2-2-froyo-and-android-2-3-gingerbread/
^this
The most noticeable is the new status bar.
davew said:
Yeah, I'm on KB4 and haven't been offered any updates for my UK unlocked I9003.
I know that I can upgrade to GB using Odin, but I'm reluctant to flash non-UK firmware onto the device. It seems only Russian ROMs are available on samfirmware.com
I did complain to Samsung UK and they've confirmed that GB is coming, but they can't say when. I don't actually think there have been any UK updates since May 2011, so I have no idea what they're playing at.
Click to expand...
Click to collapse
you can try taking note of your firmware (is it a DX (e.g. DXKP9)? an XX(e.g. XXKPM, XXKPN)? or something else?), then try to find the firmware in the Web when you want to downgrade back to Froyo.
It's a shame that Russian ROMs are available. But it's better than nothing.
you can try taking note of your firmware (is it a DX (e.g. DXKP9)? an XX(e.g. XXKPM, XXKPN)? or something else?), then try to find the firmware in the Web when you want to downgrade back to Froyo.
It's a shame that Russian ROMs are available. But it's better than nothing.
Click to expand...
Click to collapse
The phone reports my firmware versions as
PDA: I9003XWKB4
PHONE: I9003XXKB1
CSC: I9003XXKB2
I haven't been able to find any reference to this firmware anywhere on the net, except one thread on an italian forum and one on a spanish forum complaining the same about the lack of updates. If I could find a copy of this firmware I'd probably give one of the russian gingerbreads a try because I could always go back.
As I understand it, there isn't a nandroid backup for the I9003 working - and even when nandroid does work, it can be dodgy if partitions change format type or the bootloader is changed (so I've heard).
I have also read up on how to make your own Odin-flashable ROM by dumping your own firmware, but I'd have no idea if I done the procedure properly until I had to use the backup - and by then it'd be too late.
So right now I'm hoping that Samsung UK will get their act together and release the GB firmwares that everyone else in the world already seems to be enjoying
So now my question is do u tink I shud update to DXKP9 or XXKPQ?? And if I shud which firmware should I update to?
For me I wouldn't do it unless I can get a backup of my current ROM that I know will work in the event of problems with the flash.
If that issue doesn't bother you, and you're not bothered about voiding your warranty, then just flash whatever you like the look of best - but follow the instructions to the letter. As I understand it, you can't flash from Froyo straight to the latest GB version as the older ROMs contain three files and the newer ones only one.
If you were going with European ROMs (XX) you'd have to flash KPE twice first before flashing KPQ. So I'm told. I've not tried it, at your own risk etc.
davew said:
For me I wouldn't do it unless I can get a backup of my current ROM that I know will work in the event of problems with the flash.
If that issue doesn't bother you, and you're not bothered about voiding your warranty, then just flash whatever you like the look of best - but follow the instructions to the letter. As I understand it, you can't flash from Froyo straight to the latest GB version as the older ROMs contain three files and the newer ones only one.
If you were going with European ROMs (XX) you'd have to flash KPE twice first before flashing KPQ. So I'm told. I've not tried it, at your own risk etc.
Click to expand...
Click to collapse
I haven't tested the Samsung warranty. But didn't have any problem with Motorola and Sony-Ericsson when my Moto C385 and my SE K610 stoped working. The both services fixed me the phones without problems.
So, if I where you I'll flash the phone with XXKPQ (is what I done hehe)
update to KPQ if you are alright with dim recording of video... IMO its not really that bothersome
KPQ has the highest amount of developer support, but now it seems that most 2.3.6 firmwares work well with stuff designed for kpq, so take a pick! I for one do not find any difference between different regions 2.3.6 roms like xxkpq,ddkp2 etc is there actually any difference or is it just region specific versions?
Oh kay... Thanks
More people are using KPQ and more mods are made for it, so KPQ is a good choice
Hello dev,
For those with Canadian version of 6210, can someone upload a rooted 6201XXLB2 rom? I I notice the 6210 version in the dev does not contain the XXLB2 rom.
Thanks.
Cheers everyone especially to the amazing dev
If anyone can help with this it would be really appreciated. Guess who upgraded to the ICS Rom, found out that my wifi was unworkable, and now had to load the "regular North American Retail Rom with the Peel app etc that I cant use
ben_2g0 said:
Hello dev,
For those with Canadian version of 6210, can someone upload a rooted 6201XXLB2 rom? I I notice the 6210 version in the dev does not contain the XXLB2 rom.
Thanks.
Cheers everyone especially to the amazing dev
Click to expand...
Click to collapse
I don't think the XXLB2 is anywhere to be found around here. You might just have to stick with the XXLPL release until the XXLB2 is uploaded by someone or is released. I honestly don't know if its even released. I just looked for it and couldn't find it anywhere.
I'm in the same situation I search for the LB rom for P6210 but for LA3 just uninstall PEEL soft with titanium backup
MacZzang said:
I don't think the XXLB2 is anywhere to be found around here. You might just have to stick with the XXLPL release until the XXLB2 is uploaded by someone or is released. I honestly don't know if its even released. I just looked for it and couldn't find it anywhere.
Click to expand...
Click to collapse
Thank you very much anyway, The Canadian version P6210 has the XXLB2. which means it has been released. Will I have no problem with the XXLPL? I am satisfied with this rom but needs to change some few things. I am just being cautious if something happens.
I did a nandroid backup of the original unmodified LB2 in clockworkmod, before I started changing settings and installing apps.
You need to have garyd9's "CWM-based Recovery v5.x.x.x" installed in order to restore this nandroid backup:
garyd9's "CWM-based Recovery v5.x.x.x" post
I notice someone posted a newer version of CWM v6 - from what I understand, the newer CWM version is not compatible with the v5 backups.
If anyone finds this useful please reply and let me know. I also need recommendation on upload sites which are easy to use (ie. no registration etc.) and won't kill the upload quickly.
Slim_thumb,
Sorry, I was out for quite some time. Thank you for posting the link. It helped me a lot. I presummed that you have tried some ICS, what could be the best ICS replacement to our XXLB2 for the moment while waiting for our upgrade turn?
slim_thumb
Could you post you're backup for LB2 version!?
ben_2g0 said:
Thank you very much anyway, The Canadian version P6210 has the XXLB2. which means it has been released. Will I have no problem with the XXLPL? I am satisfied with this rom but needs to change some few things. I am just being cautious if something happens.
Click to expand...
Click to collapse
What is the big difference between XXLPL and XXLB2? I have XXLPN is it better to flash to XXLB2?
Verstuurd van mijn GT-P6210 met Tapatalk
@ben_2g0
No I have not tried ICS (official or custom).
@scagnetwork
Check your PM (I don't want the upload link to be killed too soon by posting it open)
@terrandroid
LB2 is the HC firmware specific to the GT7+ sold in Canada. It is not ICS. We have not received the OTA ICS update yet.
XXXLB2 firmware
If anyone has the XXLB2 firmware, could you please post it up. I would like to go back to stock for when ICS is released. Thank you in advance.
biathlonc7 said:
If anyone has the XXLB2 firmware, could you please post it up. I would like to go back to stock for when ICS is released. Thank you in advance.
Click to expand...
Click to collapse
Check your PM
Does anyone else with the Canadian LB2 P6210 get the message in KIES that this model's firmware cannot be updated through KIES?
Gazorninplat said:
Does anyone else with the Canadian LB2 P6210 get the message in KIES that this model's firmware cannot be updated through KIES?
Click to expand...
Click to collapse
Yep
But a quick flash of the latest ICS from SamFirmware.com via Odin soon fixed that problem.
CromDubh said:
Yep
But a quick flash of the latest ICS from SamFirmware.com via Odin soon fixed that problem.
Click to expand...
Click to collapse
Oh wait, but I thought the current ICS firmwares don't work for the LB2 Canadian version because of the wifi?
Did you backup your current HC firmware before flashing or did you just risk it?
Gazorninplat said:
Oh wait, but I thought the current ICS firmwares don't work for the LB2 Canadian version because of the wifi?
Did you backup your current HC firmware before flashing or did you just risk it?
Click to expand...
Click to collapse
The previous firmwares were problematic for me, but the US version that was released yesterday works perfectly....24hrs and counting >
http://www.sammobile.com/firmware/?page=8&view=5965
---------- Post added at 02:41 PM ---------- Previous post was at 02:39 PM ----------
Gazorninplat said:
Oh wait, but I thought the current ICS firmwares don't work for the LB2 Canadian version because of the wifi?
Did you backup your current HC firmware before flashing or did you just risk it?
Click to expand...
Click to collapse
and yep, I have a nandroid backup.....just in case... fingers crossed I don't need it....
CromDubh,
I followed the other thread of SrumerJohn in Adnroid Development and installed that ICS firmware. I am not happy about the performance of that firmware.
I am glad you find the latest US firmware satisfactory. Did you use the temporary CWM method to root this US firmware, followed by installing permanent CWM?
I did try the original UK ICS firmware but unfortunately not very extensively..(no wifi being a bit of a deal breaker for me)....but I'm pretty happy with North American version.
As for rooting, I used the same rooting method as was used for the older ICS without a problem. I didnt install permanent CWM, just the the temp, but I'm sure I'll end up with the permanent one when its time to start playing with JB
CromDubh said:
I did try the original UK ICS firmware but unfortunately not very extensively..(no wifi being a bit of a deal breaker for me)....but I'm pretty happy with North American version.
As for rooting, I used the same rooting method as was used for the older ICS without a problem. I didnt install permanent CWM, just the the temp, but I'm sure I'll end up with the permanent one when its time to start playing with JB
Click to expand...
Click to collapse
The ICS version is slightly faster and more fluid than HC in terms of screen transition and opening apps, but my biggest problem is the Flash video performance. Interestingly, I had no wifi problem with the UK ICS version (this problem must be router-related).
I have problem with Flash video playing in the browser in both firmware versions. Not all video sites are affected equally - eg. Youtube 1080p does not play smoothly (used to play smoothly in original HC); Vimeo HD completely stutters (used to play smoothly in original HC).
Adobe apparently stopped supporting Flash and it disappears from Google Play store. I tried several older versions of Flash 11 (and even 10) posted as .apk (eg. at apktop), but none of them work smoothly (some of them even force close the browser) - and yes I did get the correct ICS version of Flash player.
I use Dolphin browser, and I tried the Flash video with the stock browser but the result is the same. Therefore it has nothing to do with the browser.
I have since gone back to my original HC through nandroid backup.
P.S. I followed StrumerJohn's guide to flash permanent CWM onto the US ICS version, and it works. However, at your own risk always.
Add ons:
VRBLK1 Modem
VRBLK1 RPM
I saw that on the developement thread and had no idea what it was, what is this and what does it do? Thanks.
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Taken verbatim from Droidestyle's amazingly concise guide: http://forum.xda-developers.com/showpost.php?p=28530426&postcount=3
RPM: http://rootzwiki.com/topic/36114-wip-rpm-explained/
Also, the "VRBLK1" refers to the software version. Specifically, this is the third JellyBean TouchWiz leak for Verizon. They are in order as follows:
ICS
VRALF2
VRALG1
VRALG7
VRALHD
VRALHE
JellyBean all are leaks aka not official [yet]:
VRBLI5
VRBLJ1
VRBLK1
Thanks, I really appreciate the help! :good:
Getting a s3 tomorrow, hopefully I can root and flash it sucessfully
SlimSnoopOS said:
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Taken verbatim from Droidestyle's amazingly concise guide: http://forum.xda-developers.com/showpost.php?p=28530426&postcount=3
RPM: http://rootzwiki.com/topic/36114-wip-rpm-explained/
Also, the "VRBLK1" refers to the software version. Specifically, this is the third JellyBean TouchWiz leak for Verizon. They are in order as follows:
ICS
VRALF2
VRALG1
VRALG7
VRALHD
VRALHE
JellyBean all are leaks aka not official [yet]:
VRBLI5
VRBLJ1
VRBLK1
Click to expand...
Click to collapse
Wow great explanation!!!
No problem folks. Please disregard this line from my quoted though, it doesn't belong nor refer to the GSIII in any way, shape, or form:
"The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs."
Sent from my SCH-I535 using xda app-developers app
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
I'm currently running the old version of SkyFall (1.3) based on the old firmware, and I updated my firmware today with no problems. So it should be fine, though ymmv. But whatever ROM you want to run will probably be updated soon anyway.
Sent from my VZW HTC One M8
Joeysface said:
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
Click to expand...
Click to collapse
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
hgoldner said:
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Joeysface said:
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Click to expand...
Click to collapse
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
santod040 said:
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
Click to expand...
Click to collapse
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
G
Joeysface said:
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
Click to expand...
Click to collapse
Firmware is just firmware.
It's not a Rom. It's something that gets updated with the ota that cannot be flashed in a custom Rom.
So before updating to a newer software version based on the update it's best to flash the firmware as well or you just get the software and no firmware by flashing just the Rom.
The firmware is at a lower level on the device and persists through Rom flashing unless you take an ota or flash an ruu.
When running custom roms it's general rule of thumb not to take otas.
Less issues that way.
So to update everything like you would had you taken the ota, you flash firmware and software to be up to date.
In other words, I've provided the firmware part of the OTA.
You just need someone to post a rooted version of the software update now.
Sent from my HTC6525LVW using Tapatalk
NOT AT&T OFFICIAL FIRMWARE
The ROM in question is a 5.0.1 Android build and according to the original source should be good for GT-I9500/9502/9508/9508v versions. The nice folks over at XDA have been playing around with the new software for a few hours now and it appears to be a legitimate official Samsung firmware as opposed to the recent Aurora ports of the leaked Note 3 software.
A few things need to be noted about the Galaxy S4 ROM, though. First of all it has a Chinese region, so even though English is available as a system language, along with two variants of Chinese, some system messages will remain regionalized and so will some functions, like the weather widget.
A stock English keyboard is also missing, but that is easily fixable. Other than that the build seems to be doing well in terms of functionality. NFC, sbeam, GPS, Bluetooth, 3G DATA, Wi-Fi, all sensors for motion and light, hotspot function, Multiwindow all seem to be in working order, as reported by various early adopters.
If you are feeling adventurous and decide to check out the leaked Lollipop software remember to back everything up, as update will almost definitely wipe your internal storage. And if you are a little bit skeptical and wish to wait for the official OTA to start seeding, it shouldn't be long now, as the ROM seems to be just about ready for public consumption.
~~~ FROM THE MODERATOR ~~~ This is not as easy as some may Think...... Caution and an advanced understanding of your phone is recommended before flashing anything "Cutting Edge" releases as this is ....... Caveat ..... Remember you, and only YOU, are responsible for what you do to your phone...no one else.......... ~~~ oka1
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-5-0-1-android-lollipop-official-t3005979
Please Make It For AT&T S4 ...
jack_ssl said:
Please Make It For AT&T S4 ...
Click to expand...
Click to collapse
This isn't as easy as it sounds... for several reasons.
I'm not going to really go into the details but basically if your not a firmware with LOKI support you won't getting to run a 5.0 ROM on the S4 for the time being. Updates to Safestrap, among other things need to be made, and with the changes in Lollipop it remains to be seen if it will work. Not to mention the build is Chinese, would be better of waiting for the official update for the U.S, Canada, or the U.K
We'll see what happens though ~
NighthawkXL said:
This isn't as easy as it sounds... for several reasons.
I'm not going to really go into the details but basically if your not a firmware with LOKI support you won't getting to run a 5.0 ROM on the S4 for the time being. Updates to Safestrap, among other things need to be made, and with the changes in Lollipop it remains to be seen if it will work. Not to mention the build is Chinese, would be better of waiting for the official update for the U.S, Canada, or the U.K
We'll see what happens though ~
Click to expand...
Click to collapse
It appears to be a ROM that you flash through ODIN. Would Safestrap and LOKI even matter at that point?
Apoplectic1 said:
It appears to be a ROM that you flash through ODIN. Would Safestrap and LOKI even matter at that point?
Click to expand...
Click to collapse
Even so, flashing it to your device will likely cause issues when trying to go back. If someone is brave enough to take the plunge go ahead and pull up terminal and check the aboot increment. Mind you, this isn't for our model and may brick your device.
We hopefully wait for lollipop for our beloved S4 it's matter of days already so we have to be patient
Sent from my SGH-I337M using XDA Premium 4 mobile app
Its also for the Octacore variant I believe, NOT the i9505 which is similar to our i337 (minis it has unlocked bootloaders). So ATT Variants I HIGHLY suggest not trying to flash this
RockRatt said:
Its also for the Octacore variant I believe, NOT the i9505 which is similar to our i337 (minis it has unlocked bootloaders). So ATT Variants I HIGHLY suggest not trying to flash this
Click to expand...
Click to collapse
I337 is non compatible with this rom.. After install you reboot to recovery.. Appears there is now a i337 edition bootloader providing..
As this is not working for this model before someone damages their phone I am closing this thread
Please don't post firmwares as "Official" if they are not meant for the exact model phone
Thanks
FNSM