Related
Bluetooth in my XperiaV was broken by the upgrade to 4.3, which I have performed using PC Companion.
It tries to turn on for a few seconds and turns off.
Have you experienced that kind bluetooth behaviour and found solution, which you could share with me?
I would be thankful.
EDIT:
FM tuner does not start too. It seems there is problem with a driver for IC responsible for BT and FM.
Did you ever figure this out? Mine isn't working. On Xperia T LT30A version
link1227 said:
Did you ever figure this out?
Click to expand...
Click to collapse
No. At first I have waited for some help from here. Later I have found an information about ROM upgrade for LT25i and LT30a, which is apparently on it's way [here], so I have decided to wait for the new ROM. I expect it will solve this and maaany other bugs introduced by the recent upgrade.
As to the other bugs, to list a few:
- FM tuner does not work,
- there are spontaneous restarts,
- Skype crashes instead of starting.
Interestingly it happen once that after one of the spontaneous restarts BT started to work, but WiFi has stopped. I was able to turn on/off BT, connect to BT headset and use it. As Wi-Fi is more important to me I have tried to make it work once again and when I eventually managed to do so BT stopped to work. So far I wasn't able to make it work once again.
If the timespan between ROM certification and availability for the newest ROM will be the same as it was for the current one, then it would mean we should get it within one week from now. I hope it will fix all the bugs.
I actually figured it out.
Using root explorer, go to data and rename the usf folder to usf1. Reboot the phone and the nfc should do an update.
Bluetooth works well on my phone and my wife's phone as well (two different lt25i which were upgraded from stock 4.1.2 to stock 4.3).
I see many complains about bluetooth, wi-fi, battery drain, volume bar, etc and I can assure you that none of the two lt25i phones suffer from that.
The only bugs we have noticed are:
- the camera video recording autofocus buzz noise and some low-light inability to focus
- gps may sometimes reboot the phone
- ocasional (and rare) reboots
Battery drain is similar to 4.1.2 and we are not even using Stamina.
(FYI, if you turn off Google location services you'll notice the difference)
Our radio works well too.
Maybe you have flashed a ROM which does not tune FM frequencies acording to your geography ?
I believe that many "bugs" reported are due to incorrect flashing.
My 50 cents...
arturiu said:
Bluetooth works well on my phone and my wife's phone as well (two different lt25i which were upgraded from stock 4.1.2 to stock 4.3).
I see many complains about bluetooth, wi-fi, battery drain, volume bar, etc and I can assure you that none of the two lt25i phones suffer from that.
The only bugs we have noticed are:
- the camera video recording autofocus buzz noise and some low-light inability to focus
- gps may sometimes reboot the phone
- ocasional (and rare) reboots
Battery drain is similar to 4.1.2 and we are not even using Stamina.
(FYI, if you turn off Google location services you'll notice the difference)
Our radio works well too.
Maybe you have flashed a ROM which does not tune FM frequencies acording to your geography ?
I believe that many "bugs" reported are due to incorrect flashing.
My 50 cents...
Click to expand...
Click to collapse
What about 100% charge bug? (At 100% phone shut down-->no alarm at morning for example).
Did you notice this bug into your XV?
I noticed that on stock branded rom (official via seus).
No BT issues at all btw.
Sent from my SK17i using xda app-developers app
link1227 said:
Using root explorer, go to data and rename the usf folder to usf1.
Click to expand...
Click to collapse
Is there a way to root 4.3 stock ROM with locked bootloader?
przemhb said:
Is there a way to root 4.3 stock ROM with locked bootloader?
Click to expand...
Click to collapse
The only way I know of doing it, is downgrading to an old 4.1.2 rom and rooting, and then upgrading back.
I unlocked my bootloader because it was much easier
link1227 said:
The only way I know of doing it, is downgrading to an old 4.1.2 rom and rooting, and then upgrading back.
Click to expand...
Click to collapse
My 4.1.2 was rooted before the upgrade to 4.3. Upgrade has broken root.
przemhb said:
My 4.1.2 was rooted before the upgrade to 4.3. Upgrade has broken root.
Click to expand...
Click to collapse
You should still have cwm recovery. Boot into it by hitting volume down at the sony screen until it vibrates. Then install the root supersu package
link1227 said:
You should still have cwm recovery. Boot into it by hitting volume down at the sony screen until it vibrates. Then install the root supersu package
Click to expand...
Click to collapse
Now I regret, I haven't installed CWM.
Is it possible flashing latest upgrade didn't succeed due to lack of free space on data partition? When it has finished there was only about 90MB left.
On the one hand it changes only system partition, but on the other it may use data partition for some temp data (although should use cache first place).
I hope that upcoming update will fix the bug. If it won't be the case, then I guess I will have to reflash ROM.
Does repair procedure of the PC Companion leave data partition intact?
alfanumerica said:
What about 100% charge bug? (At 100% phone shut down-->no alarm at morning for example).
Did you notice this bug into your XV?
I noticed that on stock branded rom (official via seus).
No BT issues at all btw.
Sent from my SK17i using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I forgot to mention that "bug".
No, both my phone and my wife's charge properly up to 100%
Not an issue here...
That's why I'm surprised with so many of these "bugs", while I have two phones at home that work (almost) perfectly.
And with 4.1.2 it was the same story. People complaining about so many things, and I could see bothof our phones with no such issues.
I only had an issue with SD card corruption, which seemed to be related with overheating and bad contact in the card slot.
I had .145 firmware and my wife had .140 (we're now both on 4.3 stock) and the upgrade even kept all our settings.
FYI, my phone was rooted but locked BL (I just installed a couple of tweaks).
My wife's was not even rooted.
I think that if we use the phone as close as factory settings, life will be easier.
Anyway, I'm always looking for potential tweaks to improve my experience, and because of that I'm waiting for a root exploit that doesn't require unlocking BL or flashing code that doesn't come directly from Sony servers.
przemhb said:
Now I regret, I haven't installed CWM.
Is it possible flashing latest upgrade didn't succeed due to lack of free space on data partition? When it has finished there was only about 90MB left.
On the one hand it changes only system partition, but on the other it may use data partition for some temp data (although should use cache first place).
I hope that upcoming update will fix the bug. If it won't be the case, then I guess I will have to reflash ROM.
Does repair procedure of the PC Companion leave data partition intact?
Click to expand...
Click to collapse
I have no idea. Have you tried unlocking your boot loader?
link1227 said:
I have no idea. Have you tried unlocking your boot loader?
Click to expand...
Click to collapse
I'd rather leave it locked, as I don't need to flash custom ROMs. At least at the moment. So far KitKat based CM is not stable, stock KitKat is "under investigation" and stock 4.3 update, probably bug fixing release, is about to be available.
przemhb said:
stock 4.3 update, probably bug fixing release, is about to be available.
Click to expand...
Click to collapse
As the mentioned update (.199) has fixed only NFC issue and not BT and FM ones, I have decided to give PC Companion's "repair" a try.
To put it short - it did the trick. BT and FM radio are working fine now.
Apparently something must have gone wrong, when I upgraded from 4.1 to the 4.3 (.0.295) and there was free space shortage.
As I had not root I have used stock backup and restore app. It managed to backup and restore all apps installed from the Google Play (with data).
The only thing I am missing right now is a root.
I have not decided to unlock the bootloader to make rooting possible, because I do not want to loose NFC capability, my data (some sources claim even SD card contents would be deleted), Bravia Engine etc.
przemhb said:
As the mentioned update (.199) has fixed only NFC issue and not BT and FM ones, I have decided to give PC Companion's "repair" a try.
To put it short - it did the trick. BT and FM radio are working fine now.
Apparently something must have gone wrong, when I upgraded from 4.1 to the 4.3 (.0.295) and there was free space shortage.
As I had not root I have used stock backup and restore app. It managed to backup and restore all apps installed from the Google Play (with data).
The only thing I am missing right now is a root.
I have not decided to unlock the bootloader to make rooting possible, because I do not want to loose NFC capability, my data (some sources claim even SD card contents would be deleted), Bravia Engine etc.
Click to expand...
Click to collapse
For most of the so-called "bugs" that these forums report, a simple PC Companion repair would do the trick.
This is the Sony recommended way to overcome issues during flash process.
You will end up with a stock rom, no root/UBL, but your drm keys will be back (important for Bravia Engine, ...).
From my experience, too much hacking = messy device.
Personally, I'll root my lt25i 4.3 device based on an exploit for locked boot loaders when it is found.
Until then... using stock with almost no bugs at all.
And so does my wife, which also has an lt25i with stock 4.3.
The only relevant bugs we found on 9.2.A.0.295 (yep, still waiting for latest ota update to be available :-/:
- camera background noise and slow focus issue
- gps random reboots
Hello,
Is there any one using the ATT GS5 on Tmobile network (obviously Tmobile SIM) with wifi calling working ? (Please..please.. I know ATT does not have wifi calling, But if you use a Tmobile Rom with Tmobile sim, you expect to have it working) !!
If yes, would you please share which ROM you are using ? Also if there is a trick to make it wok please share it?
Thanks
no luck so far
This is not a solution, I just wanted to report what I have tried so far.
I have a G900A with a t-mobile SIM card. I called TMO to make sure wifi calling was enabled on my line. I used towelroot + safestrap to install the t-mobile Alliance rom (B4), as well as the latest stock TMO rom. So far, wifi calling does not work. It is always stuck on "Enabling" in the calling options menu. VoLTE doesn't work either, but I wasn't expecting it to. My guess is that there is something in the TMO baseband that makes these things work and that ATT phones don't have.
Any hints and ideas would me much appreciated!
No solution yet...
Guillaume2x said:
This is not a solution, I just wanted to report what I have tried so far.
Any hints and ideas would me much appreciated!
Click to expand...
Click to collapse
JJ here,
I tried this ROM - [ROM] G900TUVU1BNH5 ported from TMobile, rooted, deodexed, no knox, Download Booster
... everything works, nice and smooth, but the Wifi Calling is stuck "Enabling"...
Same boat.
My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?
chronichemp said:
My att s5 is unlocked and on the tmobile network. Your telling me i can flash the tmobile stock rom? And everything will be working properly, except wifi calling?
Click to expand...
Click to collapse
Yes. In particular, Mobile Hotspot will work.
Guillaume2x said:
Yes. In particular, Mobile Hotspot will work.
Click to expand...
Click to collapse
Will everything else work properly? I mainly need the t mobile stock rom to enable mobile hotspot, I have an ATT phone and do not wish to trip efuse. Thanks
does anyone know if the same issue will happen with the international version?
On a similar topic, my dad has a AT&T Samsung Galaxy S5 which was sold in Malaysia. And I found out that his phone was not able to hotspot. I have downloaded the official firmware of Samsung Galaxy S5 for Malaysia and was going to use Odin to flash the firmware into his phone. Does that work and not brick the phone? The phone seems to be unlocked as it can be used here except the firmware and the phone is AT&T barnded. Any advise? Thanks
Sent from my iPad using Tapatalk
It all works!
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume
Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks
Guillaume2x said:
Guys, I have some great news. Both wifi calling AND VoLTE now work on my SM-G900A on the T-mobile network. Here is what I did:
I installed the latest ATT firmware (OA1), released earlier this February. OTA update did not work, so I had to flash the original firmware (ANCE) via Odin, and then flash the two subsequent updates using update.zip on the SD Card. This will remove safestrap and root, but fear not.
Once my phone had AO1 installed, I used this tutorial to root the phone again. It invonves temporarily flashing an earlier (ND3) kernel, using TowelRoot, and then reflashing the OA1 kernel
With my OA1 rooted, I installed safestrap. Make sure you install busybox first.
With safestrap, I installed the T-mobile Alliance Rom (build B4).
Seconds after booting, both Wifi Calling and Voice over LTE work!
Enjoy!
Guillaume
Click to expand...
Click to collapse
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?
Geek007W said:
Thanks as this is great news for us G900A users on TMO! Question though: After 0A1 installed/backedup and Alliance installed, did you use safestrap [TWRP] to restore your data from 0A1 install?
Click to expand...
Click to collapse
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
Jojososo said:
Hi Guillaume,
Have you tried just installing the stock T-mobile 5.0 firmware on a Att GS5 ?
I have my GS5 in ND3 rooted and I'm on Tmobile, but the procedure you have seems really long...
I really need wifi calling as I'm travelling a lot and it allows to call my wife when I'm back in France.
Thanks
Click to expand...
Click to collapse
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Guillaume2x said:
Actually no; I had been using the t-mo alliance rom using safestrap for a long time (just with the old ATT modem and kernel), so I just restored the data associated with that.
Some more info after a day of tests:
You can also install the 5th build of Alliance Rom, it works too
The camera sometimes glitches a bit; toggling HDR on/off fixes it
Except for the camera glitch I'm pretty happy with it!
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
Agree with the last expletive.
I did install in alliance B4 in slot 1 of Safestrap and both wi-fi tether and calling worked well. However, my G900A would not reboot or shutdown (dark screen) without a battery pull. After power up...worked?!?!
Did you install as "Stock" or in a slot?
Also have a G870A (Active). Do you know of anyone attempting the 0A1 method and Alliance Rom with the s5 Active?
I might to try to create a flashable zip from the latest t-mobile lollipop release, keeping only the /system files, and see how that goes. This is really a shot in the dark, hoping that the 4.4.4 modem and kernel from ATT somehow work well enough with the t-mobile lollipop rom. Damn you locked bootloader!
Click to expand...
Click to collapse
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?
Geek007W said:
Did you install as "Stock" or in a slot?
Click to expand...
Click to collapse
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
---------- Post added at 06:15 PM ---------- Previous post was at 06:11 PM ----------
Jojososo said:
What would happen if I odin a Stock T-mobile firmware and let T-mobile update it ?
Will it update the Baseband etc ?
Click to expand...
Click to collapse
You can't do that, the bootloader is locked.
Guillaume2x said:
You can't do that, the bootloader is locked.
Click to expand...
Click to collapse
Okay thanks,
So I started the steps, I've Odin the original firmware and factory reset on but my baseband stayed ND3...
Tried the OTA update hoping that it would work, but as expected it did not.
So I guess I'm at step 1 of your step one.
Then you said you pushed the update via sd card, where did you find the updates ?
Then I'll do the other steps!
Baby steps by baby steps, F... it's been a long time since I rooted my ipod 1st gen to crack my ps3!
Jojososo said:
Okay thanks,
Then you said you pushed the update via sd card, where did you find the updates ?
!
Click to expand...
Click to collapse
They are in the post that I linked to, under the troubleshooting section. If you want to keep your user data, use adb sideload instead of recovery
Guillaume2x said:
I only use the stock slot.
B4 seems a bit more than stable than B5 for some reason. I get some signal issues with B5, and the fingerprint scanner sometimes fails. (It works when I first install B4, use it for a while, and then upgrade to B5. But if I do a /data wipe on B5, these issues appear. I have no idea why).
Click to expand...
Click to collapse
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.
Geek007W said:
OK. Installed in stock slot but ROM behaved much differently.
1. Wifi sms/mms work both send/receive but erratically.
2. Outgoing calls connect then immediately drop with local "cancelled" within a few milli-secs with a partial ring at the far end.
3. Can't receive calls at all. TMO network thinks I'm offline even though can receive a text.
3. Phone App GUI stutters when making a call.
4. Camera is basically not usable.
Where there any special steps you took to get this working installed in the stock slot? Has your install remained stable? Thanks in advance.
Click to expand...
Click to collapse
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.
Guillaume2x said:
My phone is still working flawlessly. What your are describing is what happened to me during the short period I reverted to the NG3 kernel in order to use Towelroot. Did you make sure to reflash the OA1 kernel once you were rooted? (before installing safestrap and, within safestrap, installing the Alliance Rom). I have found Alliance B4 to be more stable, so you could try that. Finally, a factory reset (wipe option in safestrap). Beyond that, you could try the whole thing again: flash the "downgrade to NCE" rom, which will remove safestrap and clean everything up; and take the tutorial from there.
Click to expand...
Click to collapse
Thanks again Guillaume,
Was running OA1 prior to Alliance B3, so just wiped Dalvik and Cache again, rebooted and left phone for the night. By next morning all was well except for the camera HDR issue. Once toggled it is OK until closed and reopened. Haven't had the time to look into whether there are Alliance B4 options which may affect this.
Have run it a few days and have had zero issues with Wi-Fi calling or tethering or apps: a very smooth experience.
Thanks again for your contribution. Also muniz_ri will find a bottle of wine on the doorstep soon. :highfive:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.
goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)
Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.
I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).
Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
gj13 said:
I have been experiencing a rather annoying bug on my S6. After unlocking the screen, sometimes the status bar will not pull down. This happens about 1/5 unlocks. I have to lock the screen again and then unlock for it to work again. Since the status bar is usually the first thing I use after unlocking, this becomes a real pain. I was hoping that the recent update would fix this, but it's still happening.
Is anyone else experiencing this issue? I couldn't find anything on the forums or Google.
Click to expand...
Click to collapse
Could you please provide additional information about your phone, such as the Base and or ROM?
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Rayman360 said:
Could you please provide additional information about your phone, such as the Base and or ROM?
Click to expand...
Click to collapse
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
Rayman360 said:
Maybe try going into Recovery mode and clearing cache, that may resolve it.
Click to expand...
Click to collapse
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
gj13 said:
Baseband: G920AUCU1AOCE
ROM: Stock unrooted (G920AUCU1AOE2)
No recovery, but the cache was cleared after I installed the G920AUCU1AOE2 update.
Click to expand...
Click to collapse
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
That doesn't explain why it was happening when I was on the version that it shipped with. They matched at that point. Good suggestion though.
Rayman360 said:
There is the issue right there, your base needs to be G920AUCU1AOE2, your on the older firmware but using the newer ROM. Use Odin to return to stock G920AUCU1AOCE, then do the OTA update from AT&T again. FYI The new PingPong Root still works on the new OTA, if you decide to go that route.
Return to Stock - http://forum.xda-developers.com/att-galaxy-s6/development/5-16-stock-odin-tar-g920aucu1aoce-t3110182
Click to expand...
Click to collapse
I just updated the baseband to match the software. I'll report back after I use it a bit to see if it happens again. It just happened after I posted that. Ugh x.x
Looks like I'm going to have to factory reset. I was hoping more people would at least vote on the poll -.-
Wireless charging possible cause
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
gj13 said:
It seems like this issue only happens if you use wireless charging. I did a factory reset on the phone and used it for a couple weeks with AC charging and I did not have this issue. As soon as I tried wireless charging again, the issue came right back.
Click to expand...
Click to collapse
I strictly use wireless charging, so your blanket statement only applies to you. Never had an issue with three different charging pads.
Sent from my SAMSUNG-SM-G920A using Tapatalk
When I first got this Blu R1 HD Prime version I was able to remove the ads and such by using the SP tool and directions here: https://forum.xda-developers.com/r1-hd/development/blu-r1-hd-remove-amazon-ads-ota-updates-t3427303. It is currently on 6.5. I have never updated it since then because I did not want to deal with ads again. Now I am having issues with it not wanting to connect to any mobile data (wifi is fine though and the sim card works in another phone) I figured an update might not hurt things. So with all that said, what is the best way to get the phone updated without bringing the ads back and not losing any data/apps?
kameleon25 said:
When I first got this Blu R1 HD Prime version I was able to remove the ads and such by using the SP tool and directions here: https://forum.xda-developers.com/r1-hd/development/blu-r1-hd-remove-amazon-ads-ota-updates-t3427303. It is currently on 6.5. I have never updated it since then because I did not want to deal with ads again. Now I am having issues with it not wanting to connect to any mobile data (wifi is fine though and the sim card works in another phone) I figured an update might not hurt things. So with all that said, what is the best way to get the phone updated without bringing the ads back and not losing any data/apps?
Click to expand...
Click to collapse
Not knowing what is causing the data connection problems, it is not positive making update will help, but worth a shot.
I have posted updates that can be installed without being forced back into the ads system.
Will need to install TWRP recovery to install them.
Rooting the system is not needed to remove ads with twrp installed, if you do not want to have room rooted.
Since you are on 6.5 and not 6.6 you can use spft to flash recovery, or you can also use the dirty-cow method "tool" to unlock bootloader and then install recovery with fastboot(built into the tool )
If you don't have recovery then my opinion is use this to get recovery installed
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
Then use twrp to install one of these ROMs (recommend v21)
https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672
in my case two amzn 8.7 will show that it recognize sim, but no service, would need root to try and change IMEI, probably these phones are from a batch reported lost or stolen, but to be blacklist even in my country, a bit farfetched.
Gizmosis350k said:
in my case two amzn 8.7 will show that it recognize sim, but no service, would need root to try and change IMEI, probably these phones are from a batch reported lost or stolen, but to be blacklist even in my country, a bit farfetched.
Click to expand...
Click to collapse
could just be an APN setting needs set to your carrier number/ settings.
Rebooting about a dozen times seems to have fixed it. I double checked the APN and everything but nothing worked. It just started working again. However I do still want to update it just to make sure it has more recent bug fixes. Thanks all.