Related
Good news everyone,
People who have the Rogers X10a can now be updated using SEUS.
1. Download SEUS:
http://www.sonyericsson.com/cws/download/1/110/61/1275980198/Update_Service_Setup-2.10.6.21.exe
2. Follow the onscreen instructions
Happy Updating!
Great News! I hope the devs know about this, so they can update the x10a baseband for the root. This would mean no more audio jack problems for some X10a..s that get root!
Hows the in-call volume? Did it get a boost? Currantly cant hear well when theres noise around.
Is that the 2.1 or just a firmware update? I can't tell since i never got an update
-------------------------------------
Sent via the XDA Tapatalk App
No 2.1 with this update. All improvements listed in changelog thread present.
Excellent update.
In-call volume marginally improved.
Sent from my X10a using XDA App
Wht exactly gets depeted from the phone with
this and how do we prevent it.
Thanks for the heads up! By the way where do I find the change log thread? Where is it exactly?
Did you try rooting it after the update?
@forzanerazzuri
Nothing gets removed. Settings, contacts, email etc stay the same as prior to the update. There are two choices through SEUS. "Update" and "Factory Reset and Update". Choose Update and all remains set-up.
@Zaslav
Changelog thread is here:
http://forum.xda-developers.com/showthread.php?t=709650&highlight=changelog
augie7107 said:
@forzanerazzuri
Nothing gets removed. Settings, contacts, email etc stay the same as prior to the update. There are two choices through SEUS. "Update" and "Factory Reset and Update". Choose Update and all remains set-up.
@Zaslav
Changelog thread is here:
http://forum.xda-developers.com/showthread.php?t=709650&highlight=changelog
Click to expand...
Click to collapse
Great thanks for the help bro. Have a good one!
hey guys so has anyone with a debranded rogers x10a gotten an update this way yet? cuz mine is still saying up to date >_< I have the generic R1FB001 brazil fw from when I debranded...do you think I should rebrand and if so..how? _-_'
Thanks!!
help!! my one is vodafone nz version.i am trying to update it today through US with official process and at the end it says update fail! (please unplug and check your battery level first then try again) but then i found i can power it up but can't get into the system,just stucked after "sony-erricon". what happen??
xchaotiKittenx said:
hey guys so has anyone with a debranded rogers x10a gotten an update this way yet? cuz mine is still saying up to date >_< I have the generic R1FB001 brazil fw from when I debranded...do you think I should rebrand and if so..how? _-_'
Thanks!!
Click to expand...
Click to collapse
I swapped my firmware from the R1FB brazillian to the R1FA014 Argentinian and then SEUS recognized an upgrade available.
Great update. Its like a new phone. Love the fade effects. Much faster and the battery is awesome. 5 hours with wifi on and I'm at 91%. Normally id be around 70%. Thanks SE.
Thanks! uabtodd that worked =D just finished charging, i'm excited to see the battery difference =D
uabtodd said:
I swapped my firmware from the R1FB brazillian to the R1FA014 Argentinian and then SEUS recognized an upgrade available.
Click to expand...
Click to collapse
Thanks for that. I went from AR firmware to BR. Then switched back to Rogers for the update. Ill debrand again using AR then
Battery life is definitely better, though I wish I was getting the kind of life others seem to get. before the update, I would take phone off charger at about 6am and by lunch time would be at 20%, have to charge it up at work just to make sure it would make it home before dieing. Today, after update, I took it off charger at 6am and i just now plugged it up to charge at 5% (9:30 pm). At least now it makes it through the day without a midday recharge.
I'm pissed, I did the update, everything went fine. Everything was normal. However, the software was telling me that there was another update available, right after I updated. So I let it run again. Turns out that second update, whatever it was, did a hard reset to my phone and I lost everything... Software now tells me my phone is up to date, thanks a**hole!
I'm gonna call Rogers telling them i'm pissed and I'll have to use half of my monthly's allowed date to reinstall everything because of their update.. I only have 150mb on my data plan, no wifi at home (wifi modem/router died 2 weeks ago) I'll see if they do something for me...
You should use the Sony Sync every few days and back up all your important stuff to their free online storage....I always do just in case
Wow just bricked my phone doing this.
When I used SEUS it downloaded the thing, then as it was installing it gave an error and canceled
Any help?
Going to call SE tomorrow
I'm sorry for making this thread but i can't seem to find what im troubled for. And im pretty much a NOOB regarding this thing.. so please be understanding.. i have a samsung s4 sgh-i337 running mf3 4.2.2 (rooted) lately charging it took a lot of hours it took me 8 hours just to charge it from 5% to 100% i already closed all the background apps, wifi off, screen off, but still the same, so i think it must be the operating system i don't know if i just done something wrong or what, so I'm thinking to update my phone to the latest version (Kitkat) using samsung kies is it okay? because im rooted right now wouldn't it brick my phone? and does updating my phone correct or replace all the settings that i done wrong or deleted before? which is probably the cause of the slow charging? i really have no idea.. really noob here.. or is there any better way to resolve this? i hope someone can help me, and if there is links regarding answers to my question i would be happy if anyone could post it here.. thanks in advance..
Are you using the original charger? Does it charge faster if the device is off?
Sent from my Nexus 7 using XDA Premium 4 mobile app
cloverbits said:
I'm sorry for making this thread but i can't seem to find what im troubled for. And im pretty much a NOOB regarding this thing.. so please be understanding.. i have a samsung s4 sgh-i337 running mf3 4.2.2 (rooted) lately charging it took a lot of hours it took me 8 hours just to charge it from 5% to 100% i already closed all the background apps, wifi off, screen off, but still the same, so i think it must be the operating system i don't know if i just done something wrong or what, so I'm thinking to update my phone to the latest version (Kitkat) using samsung kies is it okay? because im rooted right now wouldn't it brick my phone? and does updating my phone correct or replace all the settings that i done wrong or deleted before? which is probably the cause of the slow charging? i really have no idea.. really noob here.. or is there any better way to resolve this? i hope someone can help me, and if there is links regarding answers to my question i would be happy if anyone could post it here.. thanks in advance..
Click to expand...
Click to collapse
Are you using the wall charger or the usb one? There's a big difference in charging rates of the two. If you want the official OTA update to Kit Kat 4.4.2, then you must be unrooted & all aps & files as original stock. Best & safest way is to Odin back to stock. Search Mf3 tar files on XDA.
http://forum.xda-developers.com/showthread.php?t=2616221
Red_81 said:
Are you using the original charger? Does it charge faster if the device is off?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i'm using the original charger, and i'm sure that the charger is not at fault because i tried it on my wife's phone and it worked great. i tried charging while the phone is off but still it really charge really slow..
John The Rhino said:
Are you using the wall charger or the usb one? There's a big difference in charging rates of the two. If you want the official OTA update to Kit Kat 4.4.2, then you must be unrooted & all aps & files as original stock. Best & safest way is to Odin back to stock. Search Mf3 tar files on XDA.
http://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
i'm using the wall charger, at first it works really fine, then i noticed that it was charging slow, at first i thought that was normal, but now it is really slow. when i try to use it while charging it the battery drops rather than to increase because it is charging.. and btw thanks for the tip regarding updating to Kitkat i was about to try it using kies that could end up bad hehe. but is it wise to use stock? i have read other threads about using other roms. i don't know if i should use it too..
cloverbits said:
i'm using the wall charger, at first it works really fine, then i noticed that it was charging slow, at first i thought that was normal, but now it is really slow. when i try to use it while charging it the battery drops rather than to increase because it is charging.. and btw thanks for the tip regarding updating to Kitkat i was about to try it using kies that could end up bad hehe. but is it wise to use stock? i have read other threads about using other roms. i don't know if i should use it too..
Click to expand...
Click to collapse
I had to replace a charger that did exactly what yours is doing. New one is perfect. Difference is like night & day. Perhaps your battery is going? Go to an At&t store and have your phone & charger checked. The usual suspect for such problems is the charger. Start there. Be sure to read the guide before going all the way up to Kit Kat. Depends on what you want. if I were you I wouldn't update beyond MK2, which gives you 30+ JellyBean 4.3 roms & almost over 1/2 a dozen Kit Kat 4.4.2 roms.
I was updating some apps from the playstore and decided to check my voice mail by holding the 1 key in the dialer, but then my phone rebooted. Now, it won't boot past the TMO screen no matter what I do. I've tried wiping cache in recovery, and everything but a factory reset because I have a pin/fingerprint set up. I've heard that it will lock you out of your phone for 3 days if you factory reset from MM for security reasons, hence why I haven't done it. I can't find the firmware to sideload for the T-Mobile variant, can someone shed some light on this issue? It's rather annoying to have it softbrick for no reason, and not have the firmware to fix it. If someone has the firmware that would be great, or if they know how to fix it.
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
t12icky0 said:
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
Click to expand...
Click to collapse
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Good luck
t12icky0 said:
Good luck
Click to expand...
Click to collapse
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
PracticallyGeek said:
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
Click to expand...
Click to collapse
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
Did you do anything specific to flash? I'm trying to flash it but it fails
luisrcastillo said:
Did you do anything specific to flash? I'm trying to flash it but it fails
Click to expand...
Click to collapse
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Pilz said:
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
luisrcastillo said:
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
Click to expand...
Click to collapse
Hopefully it works for you, I just downloaded the latest one I could find and flashed away. It seems to be working fine now despite the first boot taking a while
Sent from my Nexus 6P using XDA Labs
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
This happened to a lot of s6edge+ users in the beginning.
Still no idea what was causing it. Updates seen to have cleared it, however, every s6edge+ reboots/freezes at launch one in a while.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
where is this firmware you speak off
PracticallyGeek said:
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
Click to expand...
Click to collapse
Yes no matter what I did it would not boot pas the T-Mobile screen.
kappatau808 said:
where is this firmware you speak off
Click to expand...
Click to collapse
In the T-Mobile S7E subforum
Sent from my Nexus 6P using XDA Labs
Pilz said:
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Click to expand...
Click to collapse
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Cst79 said:
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Click to expand...
Click to collapse
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Pilz said:
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Cst79 said:
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Click to expand...
Click to collapse
I know this is a little off topic:
Motorola didn't make it easy due to their lack of pogo pins (even though most people don't like them). I'm not sure how it would fry a USB port, but anything can happen. I plugged my 6P into my Surface Pro 4's dock via an A-C cable and it windows said it was trying to pull to much current and shut off the port until I rebooted. Things happen for better or worse, but I prefer AW over Tizen due to the long term support, despite liking Samsung's rotating bezel.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
can you send a link where you found that tmobile firmware? I'm having the same issue of not being able to go past the white t-mobile screen
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
https://forum.xda-developers.com/showthread.php?t=3549458
Sent from my SM-G935V using Tapatalk
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
xjman said:
Outside of rooting to flash custom Roms is there an official way to downgrade. Nougat is junk. Both of my phone's will not hold a charge more than a couple hours and have issues waking up from sleep, and a myriad of other issues I have with the update.
If not I'll have to smash these and hope for a non updated model upon replacement.
Click to expand...
Click to collapse
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
xjman said:
Yeah resetting the phones was my first step. They do it without any other app installed.
I'm just going to have to mess with Odin until my driver's accept the phone. It's been ages since I've had to mess with it, and it js just frustrating
Click to expand...
Click to collapse
Did you yet Princes Odin?
Sent from my SM-G935V using Tapatalk
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
xjman said:
What? I haven't messed with it since Saturday. I'll update when I get a chance. Today was the first nice day since a storm wed that downed a bunch of junk in my yard, and damaged the roof to my barn.
I likely could have bad drivers or the wrong version of Odin. I've not used Odin since the days of the Samsung moment.
Click to expand...
Click to collapse
Try Princes Odin* sorry, autocorrect messed me up.
I have it here https://mega.nz/#!CwQhVCqb!yq_p3ZsUB8kXTSxlhK8XFG6MZRhx7cH3XzSiw36_wc0
Try it with the 4APK1 Firmware. Hope this works.
Sent from my SM-G935V using Tapatalk
Well my problem as escalated on one phone. Now any time I plug it in to charge it tells me moisture detected. Never been wet, never been damp.
Yeah I think I'm just going to move on to different phones. I'm not a fan of the bugs I've encountered on both, and they don't inspire confidence in longer term ownership. Thanks for the help folks.
And now the second phone has the same issue.
There is no way this is hardware related. Is anyone else having issues with theirs. I find it extremely hard to believe two phones having identical issues after an update is coincidence.
Standard OTA update to BQA6 with no problems.
xjman said:
Yeah I saw that, I've yet to get Odin to recognize my phone. I guess I'm going to have to try another PC.
Do any of those have the update function killed?
Click to expand...
Click to collapse
norbarb said:
I think problem is with some app you have. Check this first then try to downgrade. Or try clean install by downgrading to APK1 and OTA to BQA6.
If you have problem with phone not recognised by PC, maybe you have problem with hardware it self. Go and exchange. Nougat for me holds battery about 25% longer.
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Anytime I had an Odin issue it was because of USB drivers. I uninstalled all USB drivers from that device the (complex way) and then everything worked properly. It would seem if I switched USB ports it would work again, then not long after that I would run out of USB ports. I would have to uninstall the drivers manually and reinstall them.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Capt_JuMbO said:
Hey XDA,
Am a new user and i need some advice on the new Andriod O.
In the past I had the Andriod 7.1.1 and my got the BLOD. I sent the phone back to and got another one with Andriod 7.0.
I never upgraded the version because i didnt know if it was safe and now seeing that Andriod O is out. Am just wondering if its safe to upgrade?
Am considering to unlock the Bootloader and USB Debugging just in the event something goes wrong i guess i can always install a new ROM or something.
As i really dont want to be hurt again
Any advice for a newbie?
Thanks in advance.
Click to expand...
Click to collapse
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
DEVILOPS 007 said:
The android version isn't what causes the BLOD but a degraded battery is what causes it. It is completely safe to update to O.
Click to expand...
Click to collapse
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Capt_JuMbO said:
Okay when i called Hauwei support they told me it was a problem with 7.1.1 thats why i never updated.
So does that mean that the BLOD can come back? Or was it due to an inferior battery used on some devices ?
Click to expand...
Click to collapse
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
DEVILOPS 007 said:
It depends on how well you look after your battery. This issue is mostly present on the Nexus 6p as AFAIK but it can happen on any device. Just try to look after your battery by charging to the max of 80% and try not to go under 30% too often. What Huawei told you assuming you understood them correctly was BS and likely a way for them to put the blame on Google and not their hardware. Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
I guess what Hauwei was saying was BS but google didnt offer any help just said to contact them.
I try honestly try to look after the battery, i normally let it charge to 100% at night and take it off before i sleep. I dont leave it on the charger ever or longer than i need. Then charge it again around 20-15% back to full.
If i was to charging at 30% to 80%, i dont think would give me alot of time and would have to charge more often. Wouldn't that harm the battery more?
DEVILOPS 007 said:
Degraded batteries cause bootloops. If you already had the issue once then it will likely come back so you should definitely change the battery if you can't get Huawei to send you a new one.
Click to expand...
Click to collapse
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Capt_JuMbO said:
This is the second phone they sent me, so it doesnt have any more warranty. Am hopeful it can last and would have to replace anything. :fingers-crossed: Are there any sources for good battery replacement ?
Click to expand...
Click to collapse
Your first thought was the correct one. Start by unlocking your bootloader and then update to 8.0 and enjoy your phone. If/when you ever have a battery issue there are plenty of places to have it replaced at a reasonable price. Android software version was never the cause (or cure) to a bootlooping phone, so you got some bad information there.