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
Related
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.
Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Noam Chomsky said:
Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Click to expand...
Click to collapse
You're right, they're talking about flashing a ROM from the new stock 4.3 software, not if you've already successfully rooted, flashed a custom recovery, and flashed a ROM. You'll be fine, just do a factory reset/wipe before flashing.
It's a little strange that they'd mention 4.2.2, since the S3 never had an official 4.2.x release from Samsung, we went straight from 4.1.2 to 4.3.
Brilliant, thanks so much Jacquestrapp. Downloading that snapshot now - hoping for a bit more stability!
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
Right. Actually there is a fairly recent stable version of CM10, 10.2.1, released just last month.
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
I don't think you'll need to downgrade, I'm running the latest of the CM nightlies and, so far, it's good. There were some problems with the camera, WiFi, etc. with the earlier nightlies but they seem to be all worked out and CM 11 is my daily driver now. Hope it works as well for you.
Hey Guys,
yesterday I needed to unbrick my device. I took the uploaded stock from this thread . It's an US stock 4.2.2 firmware but I got a huge update via Kies after flashing. And now guess! Yeah I'm on absolutely official KitKat 4.4.2 . I'm from germany and tested one another right before matching to my location, just to check but it's not available here (yet).
Yeah Its out for a while
@NeoPreacher & @LegendSmoker
It is true KK is an old story. But still I find interesting what NeoPreacher is saying.
One he may be telling others that even when you could be in a region without an update yet that if you install a US/Canada version you can get the Kies upgrade. Now this is not that important to me.
But I am understanding that when he said "I needed to unbrick my device" that he has some sort of a MOD Rom! Is this true? So then I find interesting that by uploading the file he mention he got Kies to upgrade him. I was in the confusion that once you mod your firmware you could not get OTA nor Kies to upgrade you. So @neopreache could you confirmed that you had tested any of the posted Roms here or had Custom Recovery or Roorted your device previous of recovering with kies? Thanks
Yes I tested some other stuff posted in dev section. But I did something very wrong so I needed Odin to unbrick.I own my tab just for a few days, so it was more a playing around than knowing what to do.I often read about an unstable 4.2.2 stock, so I thought it might be interesting for people in regions out of north America to see that there is another possibility to stay on official stock and get an update for their machines.
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
xiaoguazh said:
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
Click to expand...
Click to collapse
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
H4X0R46 said:
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
Click to expand...
Click to collapse
Yes the rom is a still expected to boot,though,the recommended frimware is to be used so as to avoid any bugs.
However,some roms do require the recommended frimware in order to boot but I don't think even if flash any rom which needs recommended frimware will take you in any kind of brick condition as when you flash a rom on incompatible frimware you'll see error in Twrp,if so happens you just need to have recommended frimware in your storage and flash it then flash the rom again and you'll not face any errors.
Good luck!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1. If you are using TWRP, nothing will happens. Because when you flash a ROM, TWRP will comparing your phone model with build.prop on the targeted ROM. Because based on my experience, somehow i download LineageOS for d802 and flash it to my bacon. TWRP gives an error and didn't flash any firmware. I don't know about CWM or other recovery
2. I'm using Lineage OS. It's pretty good so far. No bug or whatever
3. TWRP is good for all ROM. i think any recovery will do
I'm a bit confused because I can't seem to find everything about that and will my cm11 ROM that I currently have installed and any other hboot2.15 ROMs still work after upgrading to 2.16 and does anyone else have any experience (bad or good) after upgrading to 2.16?
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you very much for explaining it really well, same as for the problem that I'm experiencing with the "2nd partition" in app2sd! As soon as my dad gets home, he and I will update the firmware.
Danke vielmals! ^^
Edit:
Oh, and what is the most stable running android rom that you'd recommend? I don't really want to upgrade to the newest android versions because I don't want any lags :/
-----------Update----------------
Never mind, I already found my current ROM that I am using for HBOOT2.16 to download from F-L-Y-E-R
All android 7 roms are stable and they aren't laggier than the stock rom.
Link to the Lineage thread
Link to the Resurrection Remix thread
A link to the latest TWRP version for firmware 4.x can be found in my signature
I'm now also running lineage as I already installed it yesterday. As of now the ROM hasn't let me down just yet, and it seems that I will be able to use it as my daily driver ^^
So far I'm really enjoying lineage!