Currently running ICS via XXLPH on a GT-I9100P. Unfortunately, that version doesn't include NFC support, which annoys me, since I paid extra for a phone with NFC hardware.
My question is - I see via the sammobile page that there is a firmware update for my phone more recent than what I have, albeit one with a different PDA to my current one (I9100XXLPH vs I9100PBVLP8).
What exactly does this mean? Does this mean it's simply different software, but still designed to run on the same hardware? If so, it should be compatible with my phone, no? Or are there other things I should be checking for compatibility?
(Also - would that update even help with NFC?)
I recognize that ultimately whatever I do when screwing around is on me. And I realize that flashing a different official ROM is pretty tame compared to all the unofficial ROMs here (though most of them don't seem designed for the P version of the SGS2). But I'd rather not brick my phone at the moment.
Note - this is not a phone I got from a carrier, and I rooted it, so waiting for OTA upgrades is not an option.
Faqa42 said:
Currently running ICS via XXLPH on a GT-I9100P. Unfortunately, that version doesn't include NFC support, which annoys me, since I paid extra for a phone with NFC hardware.
My question is - I see via the sammobile page that there is a firmware update for my phone more recent than what I have, albeit one with a different PDA to my current one (I9100XXLPH vs I9100PBVLP8).
What exactly does this mean? Does this mean it's simply different software, but still designed to run on the same hardware? If so, it should be compatible with my phone, no? Or are there other things I should be checking for compatibility?
(Also - would that update even help with NFC?)
I recognize that ultimately whatever I do when screwing around is on me. And I realize that flashing a different official ROM is pretty tame compared to all the unofficial ROMs here (though most of them don't seem designed for the P version of the SGS2). But I'd rather not brick my phone at the moment.
Note - this is not a phone I got from a carrier, and I rooted it, so waiting for OTA upgrades is not an option.
Click to expand...
Click to collapse
make a bkp of ur exsisting rom and then flash the I9100PBVLP8 and see for the NFC issue if it resolves u can keep it else restore the original one back
since pda is the modem if its diff no issue u can always change the same if its not wrk'ng properly for u
Thank you. So all I should care about in ROM flashing is the underlying hardware? PDA and CSC differences should not brick my phone?
You may want to check this out it should add NFC to any rom.
http://forum.xda-developers.com/showthread.php?t=1407808
Hello everyone
I have a SGS II GT-i9100T which is a gift from my brother from New Zealand.
I´m running CM 10.1.3 and sometimes my signal drops, "Emergency calls only"! I´ve tested the Simcard on other phone and it´s fine.Could anyone suggest me a modem to flash to my phone?
I´m living in Germany and using O2-de.
Thank you.
Here is some info in case you need them:
i am not very sure whether geographical location affects modem or not, but there was a country based thread for India. They have some popular modems listed out here -
http://forum.xda-developers.com/galaxy-s2/general/i9100-modem-reviews-india-user-based-t2184193
You can get flashable modems here - http://veyka.co.uk/sgs2/radios/
have fun testing them.
Forget the fact you're in Germany; stick to modems bundled with stock roms released by carriers who sold the I9100T. Go to Samfirmware, use the pulldown boxes to make a list of all the stock roms released by carriers which sold the I9100T (there aren't many). If you click through each stock rom in turn it will list the modem - make a list of all the modems. Then search for CWM flashable versions of these modems on here (easily found with a search), download them, and start testing them out.
Only if you get to the point where you've tried all of these modems & they don't improve your connectivity should you consider flashing regular I9100 modems (I know this because I have an I9100T).
You might also be suffering from a long standing problem with CM roms where connectivity just goes away for no particular reason at all. The way you'd test if this is the case or not is to do a clean install of a stock rom released by a carrier which sold the I9100T (doesn't matter which, but don't flash 4.0.4).
I missed on seeing that the phone involved here is i9100T. My Bad.
Apologies for feeding you wrong info here.
sorry for "ruining" this thread, but:
1. How to know what the best modem is for you (I live in the netherlands).
2. Can you flash a modem on any android version? (I'm on carbon 4.4.2 rom).
3. Is it safe like rom flashing?
^^^
1) The way I always tell people to approach this is similar to what I said to the OP; go to Samfirmware, find all the stock roms released by your carrier, click through on each one & make a note of the modem. Search here/Google for CWM flashable versions of each modem, and test them out. If you find you go through all the ones bundled with stock roms released by your carrier & your connectivity is still bad, do the same with modems bundled with stock roms released by other carriers in your country. If your connectivity is still bad after that, flash any modem you can get your hands on.
But for most people, modems bundled with stock roms released by their carrier should work best; rationale being you'd hope the carrier would have fully tested them to ensure they work for most people most of the time on their network.
If your connectivity is currently fine, there's no need to go messing around with modems. Chances are you'll make it bad if you do I.E if it ain't broke don't fix it. Only mess around with modems if you have problems with connectivity.
2) Yes, modems are independent of Android version.Same risk as flashing anything else (I.E very small risk of the flash going bad with any given flash).
3) Risk should be minimal; I've never heard of anyone borking a phone with a modem misflash, but anything is possible I guess.
First of all this is my first post. Hello to everyone. I have been searching/reading thru these forums. Great source of info.
Phone info:
Currently S-OFF, unlocked, lateset AT&T 4.4.2 firmware, viperone 6.2.1, twrp
I have a pretty good comprehension of how to install or revert pretty much anything that can be done to this phone and have done so with great success. What I don't understand is the relationship between the firmware base of an RUU and the build of any given ROM. How is it that a custom Rom based off let's say x.xx.401.x work with x.xx.502.x main version? The devs say to update to the most current available firmware. Does that mean I have to flash a firmware base that matches what the Rom base for optimal performance? Because I originally thought that was the case and when I did my phone developed syncing issues particularly with the stock mail and weather apps. They would only sync over WiFi. Everything else about the phone worked as normal. Believing there was a problem with the Rom I flashed a few different popular roms on here. Always returning to full AT&T stock first. I later fully converted to GPE and to my surprise everything worked as normal. So I then converted to stock developer edition by way of zip flash and RUU exe. (By the way, when I say stock I mean s-off & unlocked but otherwise factory.) Received all the ota's. Main version would show as x.xx.1540.x. supposedly this would make my phone a dev edition with AT&T as the provider. And yet the syncing problems returned. So once again I returned back to factory AT&T 4.4.2 and all returned to normal. I then decided to try and use a Rom based off 4.4.2 and not one from 4.4.3; expecting the syncing issues to return only this time they didn't. So now I am really confused.
My questions are:
If coming from 4.4.2 factory firmware, is it best to run a Rom from the same base or am I doing something wrong and I should be able to use a Rom from a newer base on an older firmware?
If the developer edition and GPE can be carried by AT&T then why was I having syncing issues with the developer edition and not GPE?
I thought by being s-off I should be able to flash any RUU from any carrier without problems, just that I would be limited to the network capabilities of the actual service provider.
Everything I know about this stuff I learned from this forum. But I think I missed something.
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
clsA said:
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
Click to expand...
Click to collapse
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
ANGRY_robert said:
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
Click to expand...
Click to collapse
I think I figured this out. I continued to flash different ROMs and firmwares with the same results as I posted in the OP. Then earlier tonight I decided to try to convert to developer edition again (x.xx.1540.x) and flashed an ruu.zip, went thru the setup process, and as before the same issues returned. Then I had an idea; lets try something I haven't done yet. I pulled the SD card and factory reset the phone. After I completed the basic setup process I inserted the SD card and let the phone do its thing. The phone now works as it should (same as it does with the AT&T xx.502.x firmware installed).
Just figured I would pass this along.
Cheers
I give up
I thought I had this figured out. Last night after to converting to dev edition with all updates, everything seemed normal. I flashed the latest viperone rom as it is the rom I want. Turn the phone on this morning and the sync problems are present once again. I have searched thru a tom of pages on this sight alone. I cant find an answer. So its back to stock at&t.
I solved the problem. Incorrect settings in 4636 menu.
I have stock rom from nandroid backup that i've downloaded. android 4.4.2.
So the question goes like that, AT&T release the OTA 4.4.4 yet?
If so, why can't i see the OTA?
I have stock root does it a problem ? should i remove root? if so how i do that?
I need to make stock bootloader and all that stuff?
Last question, when AT&T will release the android lolipop 5 ?
ben33891471 said:
I have stock rom from nandroid backup that i've downloaded. android 4.4.2.
So the question goes like that, AT&T release the OTA 4.4.4 yet?
If so, why can't i see the OTA?
I have stock root does it a problem ? should i remove root? if so how i do that?
I need to make stock bootloader and all that stuff?
Last question, when AT&T will release the android lolipop 5 ?
Click to expand...
Click to collapse
I hesitate to answer this because so much is already in posts and threads....
1. AT&T has released the 4.4.4 OTA already
2. I don't know why you can't see it. Are you using an AT&T SIM card? Are you logged onto the AT&T network?
3. Root doesn't matter, but a stock recovery is required to actually install the update (but not to download it)
4. Stock bootloader isn't required. I don't know if it needs to be locked or not (probably not - just guessing).
5. Please contact AT&T for the answer to your version 5 update question.
DanGeorges said:
I hesitate to answer this because so much is already in posts and threads....
1. AT&T has released the 4.4.4 OTA already
2. I don't know why you can't see it. Are you using an AT&T SIM card? Are you logged onto the AT&T network?
3. Root doesn't matter, but a stock recovery is required to actually install the update (but not to download it)
4. Stock bootloader isn't required. I don't know if it needs to be locked or not (probably not - just guessing).
5. Please contact AT&T for the answer to your version 5 update question.
Click to expand...
Click to collapse
about 2, i dont think..
about 3, how i flash or whatever it called, the stock recovery?
ben33891471 said:
about 2, i dont think..
about 3, how i flash or whatever it called, the stock recovery?
Click to expand...
Click to collapse
If you're not using an AT&T SIM card or on the AT&T network, you will not be able to receive an update from AT&T. I'm not sure how you thought that might happen.
Please search this XDA forum on how to install a recovery (stock or otherwise). There are LOTS of threads on this. And if you don't know what it is, you probably shouldn't be mucking around with your phone yet. Read as much as possible first - If you don't, you'll be asking how to unbrick your phone.
DanGeorges said:
If you're not using an AT&T SIM card or on the AT&T network, you will not be able to receive an update from AT&T. I'm not sure how you thought that might happen.
Please search this XDA forum on how to install a recovery (stock or otherwise). There are LOTS of threads on this. And if you don't know what it is, you probably shouldn't be mucking around with your phone yet. Read as much as possible first - If you don't, you'll be asking how to unbrick your phone.
Click to expand...
Click to collapse
I'm from Israel so i dont think i connected to AT&T network.. My phone is from at&t but my carrer newtork is Orange(Israel)
So that means i can't update my phone ever?
kinda weird, my brother have m8 but T- Mobile and he is already have recived the OTA 4.44 a long time ago.
ben33891471 said:
I'm from Israel so i dont think i connected to AT&T network.. My phone is from at&t but my carrer newtork is Orange(Israel)
So that means i can't update my phone ever?
kinda weird, my brother have m8 but T- Mobile and he is already have recived the OTA 4.44 a long time ago.
Click to expand...
Click to collapse
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
3. You can still update your M8 to version 4.4.4 - but you'll need to ensure you have the proper firmware installed or you'll have problems. Version 4.4.4 has a different data structure than 4.4.2.
Again - read up on the general and Q/A threads on this forum. You can get your device updated to whatever version you want, it's just a matter of reading.
DanGeorges said:
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
3. You can still update your M8 to version 4.4.4 - but you'll need to ensure you have the proper firmware installed or you'll have problems. Version 4.4.4 has a different data structure than 4.4.2.
Again - read up on the general and Q/A threads on this forum. You can get your device updated to whatever version you want, it's just a matter of reading.
Click to expand...
Click to collapse
That's such a headache .. I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
This whole thing is complicated.. was so much easier on the galaxy 4 to flash roms and what not..
ben33891471 said:
That's such a headache .. I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
This whole thing is complicated.. was so much easier on the galaxy 4 to flash roms and what not..
Click to expand...
Click to collapse
Question - is the ROM on your phone from AT&T or from Orange, or was it flashed from some other source? The ROM is specific to a device, not a carrier, so you SHOULD be able to flash the ROM of your choice, as long as it works with the device (but keep in mind the fact that you will need a ROM for the GSM version of the M8, as opposed to, say, a Verizon or Sprint variant).
If it's from AT&T, you may be able to apply the updates from saved OTA file (not sure how to apply, but it can be done).
DanGeorges said:
Question - is the ROM on your phone from AT&T or from Orange, or was it flashed from some other source? The ROM is specific to a device, not a carrier, so you SHOULD be able to flash the ROM of your choice, as long as it works with the device (but keep in mind the fact that you will need a ROM for the GSM version of the M8, as opposed to, say, a Verizon or Sprint variant).
If it's from AT&T, you may be able to apply the updates from saved OTA file (not sure how to apply, but it can be done).
Click to expand...
Click to collapse
This is a nandroid backup and yes this one is AT&T rom.
I want to flash the ViperOne 3.2.1. i've been with 1.7.1 version but didn't really like it. a lot of bugs..
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
ben33891471 said:
This is a nandroid backup and yes this one is AT&T rom.
I want to flash the ViperOne 3.2.1. i've been with 1.7.1 version but didn't really like it. a lot of bugs..
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
Click to expand...
Click to collapse
I flashed Viper 3.2.1, and it worked nicely. Make sure to update your firmware before installing.
I also tried an L version 5 ROM, but didn't like the fact that it didn't work with Xposed modules, which I like and use.
DanGeorges said:
OK - here's the scoop:
1. If you've put an Orange SIM card into your unlocked HTC One M8 (AT&T branded), it is an Orange device now. AT&T is just a label on the phone (logo on the lower back of the device).
2. If Orange Israel releases an update, you will most likely get it. Both T-Mobile and AT&T released updates about a month ago, which is why your brother got the update on T-Mobile.
Click to expand...
Click to collapse
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
ben33891471 said:
That's such a headache ...
Click to expand...
Click to collapse
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
ben33891471 said:
I'll just stay with the nandrid backup i guess.. i almost bricked my phone a month ago, but fixed it somehow..
Click to expand...
Click to collapse
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
ben33891471 said:
Last question, when AT&T will release the android lolipop 5 ?
Click to expand...
Click to collapse
God knows. There is never any firm release date for AT&T (one of the many reasons to avoid US carrier branded devices if you are in another country). They just released 4.4.4 a couple weeks ago. It was delayed for months due to issues implementing Voice Over LTE. Hopefully, the LP update won't suffer the same length of delay.
redpoint73 said:
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
Click to expand...
Click to collapse
Correct. I updated my responses - I thought that the OP had an Orange M8 ROM installed.
ben33891471 said:
I want something with lollipop 5. and a STRONG battery , of course a smoothly rom with no bugs.
Click to expand...
Click to collapse
Since there is no LP stock ROM or "official" firmware for AT&T, you won't be able to run Sense LP at this time unless you have s-off (and can then update the firmware by "unofficial" means).
You can however flash a Lollipop GPE or AOSP ROM, but you will still likely need to update to at least Android 4.4.4 to get a firmware and/or hboot that supports the specific ROM.
Battery and performance are always going to vary from one user to the next. Variables such as how one uses the phones; and especially your local reception will greatly impact battery life. There is never going to be one ROM that has "strong" battery for every user in every situation. Your best bet is to try the ROMs out, and see what works best for your situation.
DanGeorges said:
I flashed Viper 3.2.1, and it worked nicely. Make sure to update your firmware before installing.
I also tried an L version 5 ROM, but didn't like the fact that it didn't work with Xposed modules, which I like and use.
Click to expand...
Click to collapse
Alright , there is a nandroid backup 4.4.4? i think this is the only way i can update my phone, if this possible.
redpoint73 said:
These points are not correct. Yes, the phone is being run on the OP's local network Orange (not AT&T). But the phone will only receive and be able to install an Orange OTA if its on Orange software and Orange CID/MID. If its running AT&T software, it will not receive OTA is most foreign countries. AT&T is the oddball here, as most other variants will still update on other networks. AT&T devices must be connected to the AT&T network to get official OTA.
The way to update the device by official means (when not on AT&T's network) would be the AT&T RUU.
---------- Post added at 10:33 AM ---------- Previous post was at 10:26 AM ----------
If you don't want such headaches, don't buy carrier branded US devices for use in other countries. I strongly believe this.
You didn't "almost brick" the device. A brick means that you phone is totally inoperable to the point the screen doesn't even power on; and the only way to recover is by opening the phone and JTAG or replacing the mainboard.
You probably just put the phone in a condition where it would not boot; which is a fairly common issue that crops up for just about anyone modding phones, at one time or another. And how to recover from such conditions is pretty basic info; and something anyone who is modding phones should now how to do.
I'm sorry if any of this seems harsh. But I believe the above to be more FACT than opinion, and for your own good. I agree with the former notions that you (and anyone who want to mod the hone) should always research thoroughly and understand before messing with the phone.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
God knows. There is never any firm release date for AT&T (one of the many reasons to avoid US carrier branded devices if you are in another country). They just released 4.4.4 a couple weeks ago. It was delayed for months due to issues implementing Voice Over LTE. Hopefully, the LP update won't suffer the same length of delay.
Click to expand...
Click to collapse
I don't know what RUU means.. There is a simple way to update to 4.4.4 ?
redpoint73 said:
Since there is no LP stock ROM or "official" firmware for AT&T, you won't be able to run Sense LP at this time unless you have s-off (and can then update the firmware by "unofficial" means).
You can however flash a Lollipop GPE or AOSP ROM, but you will still likely need to update to at least Android 4.4.4 to get a firmware and/or hboot that supports the specific ROM.
Battery and performance are always going to vary from one user to the next. Variables such as how one uses the phones; and especially your local reception will greatly impact battery life. There is never going to be one ROM that has "strong" battery for every user in every situation. Your best bet is to try the ROMs out, and see what works best for your situation.
Click to expand...
Click to collapse
ben33891471 said:
I don't know what RUU means.. There is a simple way to update to 4.4.4 ?
Click to expand...
Click to collapse
RUU = ROM update utility. Its an official .exe (Windows PC required) that completely re-images the phone, including stock ROM, stock recovery and all firmware.
If this is the path you choose, its pretty simple:
Download the RUU to your PC.
Backup any personal data, as the phone will be wiped by RUU.
Connect the phone to PC in fastboot mode.
Relock the bootloader with command fastboot oem lock (not required with s-off).
Simply run the RUU .exe, and it will do the rest (you click a few confirmations dialogs, but that is it).
RUU and more detailed instructions at the following link, under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
As RUU installs stock recovery, you will need to unlock the bootloader again, and flash custom recovery again if you want to root or flash custom ROMs.
redpoint73 said:
RUU = ROM update utility. Its an official .exe (Windows PC required) that completely re-images the phone, including stock ROM, stock recovery and all firmware.
If this is the path you choose, its pretty simple:
Download the RUU to your PC.
Backup any personal data, as the phone will be wiped by RUU.
Connect the phone to PC in fastboot mode.
Relock the bootloader with command fastboot oem lock (not required with s-off).
Simply run the RUU .exe, and it will do the rest (you click a few confirmations dialogs, but that is it).
RUU and more detailed instructions at the following link, under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
As RUU installs stock recovery, you will need to unlock the bootloader again, and flash custom recovery again if you want to root or flash custom ROMs.
Click to expand...
Click to collapse
Which ROM do you think the best. I'm thinking about ViperOne 3.2.1 , Android Revolution hd 34.0 or CM 12 .
I really like the design of the CM12 but i heard that the boomsound ain't works, is that true? that's means the quality of the speakers will be very bad?
ben33891471 said:
Which ROM do you think the best. I'm thinking about ViperOne 3.2.1 , Android Revolution hd 34.0 or CM 12 .
I really like the design of the CM12 but i heard that the boomsound ain't works, is that true? that's means the quality of the speakers will be very bad?
Click to expand...
Click to collapse
I don't believe in recommending "best" ROMs. What's best for me, may no be the best for you. Especially since our network requirements are very different. And the choice of ROM is also largely a matter of personal preference and taste. In fact, until recently the XDA rules did not allow posting of "best ROM" threads as the discussions are largely irrelevant, and just resulted in fanboy pissing contests.
You really can't go wrong with any of the mentioned ROMs.
Although be aware that current ARHD is based on Android 5.0. So you need to update to Lollipop firmware or else suffer major bugs (broken WiFi is the most common). For the AT&T version of this phone, you can only update to LP firmware if you have s-off (until a LP is released by AT&T, for you by RUU).
Yes, any features that require Sense framework will not be present on CM12, including Boomsound and dual camera. Whether the sound is "bad" or not, I can't say. I'm not a CM12 user. But remember that Boomsound is just a software enhancement. The high quality of the speakers (for a smartphone) is largely a factor in the sound quality. If you like CM12 design, why not flash it (once on the proper hboot) and see for yourself what you think?
redpoint73 said:
I don't believe in recommending "best" ROMs. What's best for me, may no be the best for you. Especially since our network requirements are very different. And the choice of ROM is also largely a matter of personal preference and taste. In fact, until recently the XDA rules did not allow posting of "best ROM" threads as the discussions are largely irrelevant, and just resulted in fanboy pissing contests.
You really can't go wrong with any of the mentioned ROMs.
Although be aware that current ARHD is based on Android 5.0. So you need to update to Lollipop firmware or else suffer major bugs (broken WiFi is the most common). For the AT&T version of this phone, you can only update to LP firmware if you have s-off (until a LP is released by AT&T, for you by RUU).
Yes, any features that require Sense framework will not be present on CM12, including Boomsound and dual camera. Whether the sound is "bad" or not, I can't say. I'm not a CM12 user. But remember that Boomsound is just a software enhancement. The high quality of the speakers (for a smartphone) is largely a factor in the sound quality. If you like CM12 design, why not flash it (once on the proper hboot) and see for yourself what you think?
Click to expand...
Click to collapse
The RUU file isn't open. I boot into bootloader and type the command but then this says something failed and reboot my device. Then i boot into fastboot again and i saw its says relocked so i guess that's ok.
Fine, tried to plug into my PC while the phone is awake and open, the file can't seems to open, not even when i plug it while im in the bootloader.
did i do something wrong?
ben33891471 said:
The RUU file isn't open. I boot into bootloader and type the command but then this says something failed and reboot my device. Then i boot into fastboot again and i saw its says relocked so i guess that's ok.
Fine, tried to plug into my PC while the phone is awake and open, the file can't seems to open, not even when i plug it while im in the bootloader.
did i do something wrong?
Click to expand...
Click to collapse
Make sure you have HTC drivers installed on your PC. Phone should be connected in in fastboot mode.
If the RUU application doesn't even open, it doesn't sound like an issue with the phone. Even if there was an issue with the phone (wrong RUU , unlocked bootloader, etc.) the RUU would still open and start to run, but it would just give you an error message telling you what was wrong. Maybe just a bad download, try to download again.
redpoint73 said:
Make sure you have HTC drivers installed on your PC. Phone should be connected in in fastboot mode.
If the RUU application doesn't even open, it doesn't sound like an issue with the phone. Even if there was an issue with the phone (wrong RUU , unlocked bootloader, etc.) the RUU would still open and start to run, but it would just give you an error message telling you what was wrong. Maybe just a bad download, try to download again.
Click to expand...
Click to collapse
Bro, i managed to upgrade to 4.4.4 . I flashed ViperOne 3.2.1 at first, didn't like it, so i tried android revolution hd 34.0 and this ROM is amazing, love the design love it!
Have only 2 problems so far, first, the TV app , just got every 1-2 min a message: TV stopped .. so i kinda deleted this, but fine i can live without it.
But the problem that actually do me a troubles, is the screenshot, when i try to take a shot of my screen it's says. couldn't take a screenshot, not remaining space or program does not support..
Sorry about my English if you can't understand what i say..
SM-a520W model. I bought cause I know I've seen this version include it.
don't care so much for root... want to keep warranty... whats the best stock rom to flash?
also is odin 3.04 ok to use? build number a520wvls1bqk1 if curious for reference on it currently.
The SM-A520F has the radio fm apk, try to install it and see if it works. I don't recommend to install other variant's ROMs since antennas and software frequencies might differ from your original ROM, rendering your phone useless. Chances are it won't even flash.
Edit: Try searching the radio app on apkmirror. The latest version on my device (Nougat) is 2.1.68
rashisp said:
The SM-A520F has the radio fm apk, try to install it and see if it works. I don't recommend to install other variant's ROMs since antennas and software frequencies might differ from your original ROM, rendering your phone useless. Chances are it won't even flash.
Edit: Try searching the radio app on apkmirror. The latest version on my device (Nougat) is 2.1.68
Click to expand...
Click to collapse
I remember on older phones we only needed to install the PDA to flash the phone... is this not the case with this model? even next radio was blocked...
tryed DL and install the fm radio apk.... I get "app not installed package conflicts with existing package with same name"
Canadian carriers are SO GREASE. we should complain to the CRTC
am I hooped/limited in options if I wanted to flash custom rom down the line cause I have the canada model?
supertac said:
I remember on older phones we only needed to install the PDA to flash the phone... is this not the case with this model? even next radio was blocked...
tryed DL and install the fm radio apk.... I get "app not installed package conflicts with existing package with same name"
Canadian carriers are SO GREASE. we should complain to the CRTC
am I hooped/limited in options if I wanted to flash custom rom down the line cause I have the canada model?
Click to expand...
Click to collapse
Return it and demand a new one with the correct software and the radio in it
Nick312 said:
Return it and demand a new one with the correct software and the radio in it
Click to expand...
Click to collapse
sadly I bought from someone else wanting to save dollar :/
all I see on market are Canadian galaxy a5 520w....
I haven't bought a new phone in years.... this is actually the newest peice of tech thatI've ever had... .actually the a5 2017 just turned a year old.
I'm searching online like a bastard for info on how to's.... custom roms and flashing have gotten more advanced since 2012... more security more issues... like before we just flashed the PDA and we were good to go... now we have to flash everything? haven't even tried yet, very nervous to do anything- don't want to trip knox or soft brick the phone- I'm shocked a re flash from odin doesn't reset knox tripping. Also shocked we haven't found a way to reset completely from factory after knox tripping. never really had to worry this much years back. I understand rooting a phone can be very dangerous but having more features and features from other phones is a major bonus
this phone is too new for me... not enough research done on hacking... also I find out this model never came out in the states! only canada! damn no wonder why it doesn't have a much support... also its not an galaxy S line which has more customers. missing that. but NA models were always different (and inferior) anyway... so many things to think about
ok so then... honestly.... the 520W CANT BE THAT DIFFERENT from the 520F and 520F/DS.... besides the modem.... all the hardware has to be the same. correct?
really all I want out of this is the stock working FM radio and a clean rom to flash with. I can go with standard features from there.
ok... so I DLed and tried a new zealand rom... OEM lock on, lets do this. nervous as hell
only Downloaded the AP portion like the old days... I think I tried the bootloader.... no I didn't I didn't load it.
it was a successful flash... but it hung. "could not mount misc, could not verify" when I went to boot it up.
wipe cache, wipe partion, run system update...
and....it boots up UK/New Zealand Rom
FM radio is there a working.... choopy to start I'll test it.
phone and internet work.... same modem keep in mind, now it shows 4G instead of LTE. I wonder if the speeds are the same....
all clear so far I'll test alittle more. looks like it is indeed exactly the same hardware, and the fm radio is software blocked on the canada model. Samsung Pay and secure folder won't work... yet I never rooted.
........
custom binary blocked by frp lock
after logging in with google account and turning off
this sucks. I gotta turn this one in as soon as I recover it... too much hastle to get one thing going- its so much easier to mess around with older phones and they aren't that much worse in preference....
does anyone have a 520w rom for fast download?
supertac said:
custom binary blocked by frp lock
after logging in with google account and turning off
this sucks. I gotta turn this one in as soon as I recover it... too much hastle to get one thing going- its so much easier to mess around with older phones and they aren't that much worse in preference....
does anyone have a 520w rom for fast download?
Click to expand...
Click to collapse
There you go: https://www.sammobile.com/firmwares/galaxy-a5/SM-A520W/
thanks I mannaged to DL from https://samsung-firmware.org/ payed extra for faster DLs.
I flashed back to XAC 520W model back to normal. it no longer shows LTE but instead 4G... reception works with my carrier though. tried coloning the fm radio with cloning APK... didn't work. wanted to try Sprit2... wasn't sucessful to flash. boatloader locked couldn't flash that...
but I did manage to flash a UK stock rom.
here are some pictures for reference.
its possible... I messed up my phones software a bit (battery shows twice) I think my first problem was flashing a firmwire that was ahead in security update as the canada one as of this post is behind...
so FM radio works... yet it sounds choppy. I go to a local mall to test a 520X (demo model) running marshmallow and the reception on that one is way better- make no mistake 520W Canada users are getting screwed- I'm running the UK firmware and its working as it should. Nextradio still doesn't work.
now.... can I get Samsung pay and secure folder to work again? I don't believe in the "efuse" hype. software always has a way to reset. even still I'm sure these apps can work with tripped knox... but how? is their a way?
sadly I don't see as much community support on galaxy A models vs galaxy S
as you can see I'm ambitious to get this to work... messed up the phones PDA part a bit to make it happen. I hope there will be cleaner ways and tie ins to 520W and 520F software considering this is the very same damn phone (unlike galaxy S models which change snapdragon and exynos) and hopefully with Samsung new announcement to support FM radio on new phone recent phones from the past few years will see updates to FM radios.
supertac said:
I don't believe in the "efuse" hype. software always has a way to reset.
Click to expand...
Click to collapse
WOW!
You need to believe in this because it is true.
I've come to Samsung Galaxy A5 2017 from Motorola X Play. The Moto bricked after I attempted to revert to Marshmallow using official OTA update after flashing MM (I wanted to try a few things and learn custom ROM building on an established device).
Why did it brick?
eFuse, my myopic friend....e..... fuse.
To quote cinema."ye wanna start believing in ghosts"
Move on. Adapt. Overcome.
hey man... asking me to move on... your speaking to someone who still uses the galaxy s3 (i9300) as their DD... for 2 and some years... 3 years after the guy before me
A520W FM Radio
I found a solution here if you're phone is rooted:
https://forum.xda-developers.com/ga...apps-and-mods/fm-radio-sm-a530w-t3883199/amp/