I had lag and touch sensitivity issues and I upgraded my white note4 dash cam from 4.4.4 to 6.0.1. Factory reset fixed it. I am going to set my white note4 up as close to daily driver as possible and run with it a few days before I upgrade my black note4. In the meantime anything to report? I haven't run into issues. How is reception? Does it still connect to hspa+ when LTE signal is fine or low? Still have 5.1.1 bug where outgoing calls couldn't be made occasionally but receive was fine until reboot?
Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.
+1 for fully functional when flashed properly. My process:
1. Backup
2. Backup your internal data to sd or USB
3. Reboot into recovery, wipe everything (internal and data included)
4. Reboot into download mode
5. Flash with Odin
Optional root:
6. Flash TWRP .tar in Odin. (The best way to get TWRP to stick is to flash it before the ROM boots for the first time. Takes practice and timing, but will save you a headache. )
7. Flash latest seamless root from chainfire in TWRP recovery
Sent from my SM-N910T3 using XDA-Developers mobile app
DeeXii said:
Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.
Click to expand...
Click to collapse
Not experiencing problems. Just trying to find any majors bugs that might hold me off for awhile. Haven't tested with a sim card yet. Just my note4 with a dashcam. Every thing apparently seems fine. Totally stock though. Going to flash TWRP and root of course. Then xposed a week down the road. Need ad blocker and swap back and recent buttons. The I'm going to mod s pen to left side of note for us lefties. Sike! But do wonder if Samsung will ever appease the lefties.
Sent from my SM-N910T using XDA-Developers mobile app
thefanum said:
Optional root:
6. Flash TWRP .tar in Odin. (The best way to get TWRP to stick is to flash it before the ROM boots for the first time. Takes practice and timing, but will save you a headache. )
Click to expand...
Click to collapse
For someone relatively new to the Samsung way (but not flashing in general), what's the best procedure for this particular step?
SteveRiley said:
For someone relatively new to the Samsung way (but not flashing in general), what's the best procedure for this particular step?
Click to expand...
Click to collapse
Guessing from off top of my head but untick reboot after flash. Flash TWRP when Odin finishes rom. This upsets me. Lol. I just factory reset again and setting up my phone. Waiting for apps to DL so I can flash TWRP and root. Ugh. I guess I'll update later or by Friday at least or maybe somebody else will.
My phone is laggy. Did a full wipe as per OP, then flashed stock rom.
SD card tap here to transfer media files
I have a constant notification "SD card tap here to transfer media files." on my Note 4 replaced recently with the T3 version, now that I have done the OTA upgrade to 6.0.1 Marshmallow. Everything else works well. The Galaxy S7 forum has threads on this issue dating back to April 2016 anyway. Is nobody else seeing this on the Note 4? I have a 64 Gig Samsung microSDXC UHS-1 Card. Perhaps this is just cosmetic? Restarting doesn't fix it. Unmounting and remounting from Settings > Storage doesn't fix it. No surprise that taking the card out after power down does eliminate the notification. Replacing the card and restarting brings the notification back.
Saw SD card notification once but not again even after many restarts.
Sent from my SM-N910T using Tapatalk
Everything is fine for me. I've noticed Lego Star Wars The Complete Saga runs way better on 6.0.1 than it did on 5.1.1. I did a factory reset after the upgrade and haven't had a problem yet.
Stuck in 4g mode, unable to recognize finger print unlock and the transfer media filed bug.
How do u fix the screen rotation on marshmallow? Doesnt work.
DeeXii said:
Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.
Click to expand...
Click to collapse
Does OTA not install the update the same as ODIN? I'm dont care for root at the moment as I have in the past.
In the first flash from 5.1.1 to 6.0.1 my phone stalled at the tmobile splash. I just did a factory reset and wiped it down a couple times and it booted up just fine. Been up and running for almost a full 24 hours now and no probles to report. I just installed my gear vr files and ill see how netflix and the theater run.
monkeyass408 said:
How do u fix the screen rotation on marshmallow? Doesnt work.
Click to expand...
Click to collapse
See this post from DeeXii:
http://forum.xda-developers.com/showthread.php?p=67537758
Sent from my SM-N910T using Tapatalk
Has anyone tried secret mode in the Samsung browser? I can't get the fingerprint or password lock on it. In 5.1.1 I could have it so that it needs a fingerprint or password to go into secret mode. I don't see the option to do it now on 6.0.1. I checked on the playstore to see if I have the latest version and I do. It's also not in privacy in settings for the browser.
Waiting on a few more replies before I flash it. Perfect weekend to do it
Sent from my SM-N910T using Tapatalk
Does the phone still show LTE in notification bar when it's available? or does it just show 4G/3G/2G now? I only ask because I am not sure if that's all that's displayed now because all I show is the 4/3/2.
Thanks
can someone on marshmallow please test out the built in video calling? for me it keeps saying preparing display image...
lol laugh out loud .... f-ing tmobile took so much time trying to implement that feature in the dialer and it still fails
monkeyass408 said:
How do u fix the screen rotation on marshmallow? Doesnt work.
Click to expand...
Click to collapse
Did you freeze or uninstall any apps with Titanium Backup?
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
ElCid43 said:
Does the phone still show LTE in notification bar when it's available? or does it just show 4G/3G/2G now? I only ask because I am not sure if that's all that's displayed now because all I show is the 4/3/2.
Thanks
Click to expand...
Click to collapse
The Cell signal icons and behavior are the same as LP.
Related
Hi all.. Firstly, so sorry about the generic title.. but as you will see, i have quite a few questions and I wasn't sure what to put.. or even if this needs to be in a different section.. sorry mods..
Anyway, here we go.. (advanced warning.. im not a complete idiot.. but not far off. so go gently)
HTC one sim free from phones4u in the UK.
im on android 4.1.2
software 1.28.401.7
htc sdk api level 5.12
The story so far:
Ive rooted my HTC one as I need to have rSAP working on it for my car (Audi). Also, I found the stock bluetooth stack didn't seem to work with my car either so i installed bluetooth phonebook app v 1.1.4.. this all seems to work well. I used rSAP v2.3.2
Now, I carried out all the above myself with lots of reading and to be perfectly honest, lots of trial and error installing it all. I didn't find it easy and for the life of me, I can't remember the steps.
The issue i have:
1. I keep getting a notification for an OTA update for my phone. I have tried to run it once.. but it did not install. I'm assuming because my phone is rooted. I force stop it, but it comes back every time i reboot.
2. I've noticed any app that requires root access is failing. (not all the time, some of the time) and if I go into SU it tells me the binary files need to be updated. I have two options. Run "normal" or "TWRP/CWM" neither of them work.
If i pick normal. It says installing, then reboots and is basically the same. The other option boots me into the recovery but I can't see any update to be applied.
UPDATE: I have now resolved this. I simply downloaded the latest zip file for SU.. booted into recovery and ran the zip update from there and it worked..
Now, you super clever lot probably think this is fun to mess around with.. but us, dare i say it, older peeps just really want to be able to press a button and it works.. (i know iphone.. but give me some credibility).
What I'd like to achieve:
1. I've ordered an OTG cable and drive today (be here tomorrow) with a view of taking an off device back up of my current data / app setiings etc. I assume this is easy to do?
2. I'd like to unroot and update the phone to the latest updates via the OTA service
3. I'd really like to get the rSAP/Bluetooth working with very little fuss
4. Put all my email accounts data etc back to where it was.
How to do achieve my request:
Over to you guys... just please for my own sanity.. and anyone else that reads this in the future.. make it easy.. just remember.. I'm not R2D2...:laugh:
Thanks so much.......... i will personally thank each and every useful reply..
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
2. No need to unroot for OTA
3. Not too sure about this one
4. OTA won't wipe anything unless it specifically says so.
ArmedandDangerous said:
If you're rooted, I'm guessing you're using a custom recovery? The OTA won't install if you have a custom recovery installed.
Click to expand...
Click to collapse
Yes correct, I have the TWRP, I believe.
1. Yes, no issues there, but unrooted devices can only r/rw on FAT32 devices, and if your drive is NTFS, you need an app that requires root.
Click to expand...
Click to collapse
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
2. No need to unroot for OTA
Click to expand...
Click to collapse
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
uktivo said:
Yes correct, I have the TWRP, I believe.
OK.. so I should be good to go with NTFS format drive. Is this as simple as I think, i.e. plug in the OTG cable and drive and go into the recovery and backup from there?
I'm a bit confused with this reply, as I don't seem to be able to complete the OTA update becasue I have custom recovery.. Do I need to remove custom recovery then apply the OTA update? If you could just expand on this please? i.e if i need to remove custom recovery, how do i do it?
Thanks
Click to expand...
Click to collapse
Hey,
Because you are rooted, you will not be able to install otas. They may notify you they exist, but you can't install them.
How do you get rid of them?
Well you're on a stock Rom. That Rom will receive otas from your service provider. You can install a custom Rom. It's fun! it gets rid of the notification but that's only like 2% of any advantage you can have from a custom Rom. Plus that ota that's trying to come to your phone is most likely already on a custom Rom, as the devs get leaks and port them way before regular users receive them. You could give it s try?
No idea about the first post.. loving the Audi part though haha!
Sent from my HTC One
ArmedandDangerous said:
How do you get rid of them?
Click to expand...
Click to collapse
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
uktivo said:
Pull down the banner from the top of the phone. Click and hold the notification for the update, click app, then pick to force close it. It then goes away until you next re-boot.
Click to expand...
Click to collapse
Think you're quoting the wrong person
As I said in my earlier post, you can still receive OTAs and apply them even if you are rooted. The part that makes it fail is the custom recovery. You should be able to find the correct stock recovery from one of the threads here on XDA, or if you have ever received an OTA before on your device, the OTA zip file should still be in your internal SD.
Flash the stock recovery over TWRP (make sure to do a nandroid/backup first) and apply the OTA. You will probably lose root, but just root it again the usual way.
Then you can flash a custom recovery, root, etc etc all over again.
About the USB OTG, I believe TWRP always saves the nandroid backups internally, but you can always transfer them off to a USB device through USB OTG if you want. I don't think it natively supports reading from USB OTG while in recovery.
Why have it so complicating?
Hi,
what I don't understand is why your Audi is not recognising your phone properly? I stream music at home via BT to an APT-X receiver plugged into my stereo, and using quite often rental cars of all makes, I simply connect it, punch the PIN into my fone and the One phonebook is available.
Now, as you are already rooted, and of course unlocked, just download and flash a Custom ROM. They are rooted, and some are based on 4.2.2 and work very well.
No need to fuss about with what you are about to do!
Don't forget to backup imortant stuff you want to keep on your SD card, simply copy it over to your computer for future reference. JB 4.2.2 is organising the SD card structure differently, so you copy stuff back to SDcard/0/
Custom ROMs are featuring the latest updates anyway very quickly, so there really is no need whatsoever to wait for an OTA (which you should never ever attempt to flash when rooted/S-off-ed)
Looking forward to see what you are telling me about the Audi BT connection trouble. I never had any!
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..of course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk 4 Beta
uktivo said:
Audi..bless them, use a strange protocol. The stock Bluetooth stack will connect but will not transfer the contact information. It can be fixed once root is gained. In all honesty Audi really need to look at this problem. My car is an A7 about 5 months old now but I think they may have addressed it on the latest builds..If course, I won't get the upgrade for free will I...
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah, to much Iphones stuff around! hehehe
Try maybe with the Custom ROM in my signature. It worked very well with the Ford Kuga I had last week, music as well as contacts.
Just read up a bit on the different SD card managment google implemented with the multi user stuff.
And I have to say: Audi A7 ???? Nice motor!
Yes , it's a lovely car.. Thanks.. Also; thanks for the info. I will investigate roms..
Sent from my HTC One using Tapatalk 4 Beta
Hi all, Sorry I've been away working for the last few weeks so I've not had chance to do any of the above.
I was hoping I could get some easy to follow (trust me, it has to be easy at my age) instructions on the best way to achieve what I want to do. If the step by step instructions could include links ot the downloads i need, that would be fantastic.
Re-cap on what I want to acheive:
My phone right now:
The phone was purchased from Phoes4u (UK) as a sim free unit. I currently have an O2 sim inserted
Android 4.1.2, HTC sense 5, Software 1.28.401.7
HTC SDK API level 5.12
Kernel 3.4.10-gddcfb8croot
When i boot into recovery it tells me:
M7-UL PVT SHIP S_ON RH
HBOOT-1.44.0000
I have added rSAP v2.3.3 to the phone in order for my car to have access. http://www.android-rsap.com/compatibility.html
I have one exchange email, some movies, and basically thats it.
----------------------------------------------------------------------------------------------------------------------------------
I would like to update to the latest Jelly Bean and ensure I keep rSAP for my car. If there is a way to back up all my data and movies and simply press a button to re-install it, data, settings for email etc that would be fantastic.
Please help if you can.....
thanks.
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:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?
dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.
Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk
Hi!
Last week I got a S2 TM-810X Retail-Tablet (9.7, Wifi, 16GB).
This tablet is for shops or so and the Retail Mode starts the Tablet after a time between 3 minutes and 3 hours (you can select it) automaticly and reset all preferences, delete all files, pictures, installed apps and any kind of user changes.
So I want to remove this firmware and first step was to try to root with Odin.
I tried rooting with all of this files.
t810_5.1.1_boot.tar
t810_cf-autoroot_5.1.1.tar
t810_twrp_LL_5.0.2.tar
twrp_2.8.7.1_LL_5.1.1_t810.tar
I had success with "t810_cf-autoroot_5.1.1.tar". I see "SuperSU"-App on my tablet now.
But if I start this app I got an error -> "SuperSU stopped".
What do you mean: Is the tablet really rooted? And what is the best way to remove the "Samsung Retail Mode"-Firmware?
BTW: I had no success with the other tree files. I got an "PASS!" in Odin indeed, but after the tablet autostarted it goes directly to the main screen and not in a screen like I got after cf-autoroot ( see at imgur.com/a/hwzMS )
Sincerly Andy
A few ideas:
http://www.naldotech.com/how-to-disable-exit-galaxy-s5-demo-live-unit-retail-mode/
This suggests changing the retail mode settings to enable factory resets and allow for odin-flashing a standard rom
http://forum.xda-developers.com/tab-s2/general/stock-collection-sm-t810-stock-odin-t3204373
That + factory reset should eliminate retail mode and have a rom that is supported by autoroot. Do you really have a 16gb model or is it 32gb?
schrimmschramm said:
Hi!
Last week I got a S2 TM-810X Retail-Tablet (9.7, Wifi, 16GB).
This tablet is for shops or so and the Retail Mode starts the Tablet after a time between 3 minutes and 3 hours (you can select it) automaticly and reset all preferences, delete all files, pictures, installed apps and any kind of user changes.
So I want to remove this firmware and first step was to try to root with Odin.
I tried rooting with all of this files.
t810_5.1.1_boot.tar
t810_cf-autoroot_5.1.1.tar
t810_twrp_LL_5.0.2.tar
twrp_2.8.7.1_LL_5.1.1_t810.tar
I had success with "t810_cf-autoroot_5.1.1.tar". I see "SuperSU"-App on my tablet now.
But if I start this app I got an error -> "SuperSU stopped".
What do you mean: Is the tablet really rooted? And what is the best way to remove the "Samsung Retail Mode"-Firmware?
BTW: I had no success with the other tree files. I got an "PASS!" in Odin indeed, but after the tablet autostarted it goes directly to the main screen and not in a screen like I got after cf-autoroot ( see at imgur.com/a/hwzMS )
Sincerly Andy
Click to expand...
Click to collapse
All you need do is ensure reactivation lock is disabled. Factory reset then flash the stock firmware.
rp3 said:
A few ideas:
http://www.naldotech.com/how-to-disable-exit-galaxy-s5-demo-live-unit-retail-mode/
This suggests changing the retail mode settings to enable factory resets and allow for odin-flashing a standard rom
Click to expand...
Click to collapse
I tried this. All the codes are working but after rebooting the retail mode is enabled again.
http://forum.xda-developers.com/tab-s2/general/stock-collection-sm-t810-stock-odin-t3204373
That + factory reset should eliminate retail mode and have a rom that is supported by autoroot. Do you really have a 16gb model or is it 32gb?
Click to expand...
Click to collapse
Tablet has 16gb.
After a lot of attempts I can boot in TWRP
But SuperSU is stopping furthermore, when I start it.
Thanks for stock-firmware-URL. I will try it.
Does anyone knows the difference between a XAR and DBT?
Sincerly
Andy
ashyx said:
All you need do is ensure reactivation lock is disabled. Factory reset then flash the stock firmware.
Click to expand...
Click to collapse
I will try it again!
Thank you very much!
Yeah! New Firmware installed!
Thank you so much you both
some more questions
Android 5.1.1 runs now on my S2 One little issue: if I install now "t810_cf-autoroot_5.1.1.tar" with Odin I run in a bootloop. Maybe there is another way to install SuperSU?
After installing "Phone Info Samsung" I can see the tablet has no IMEI. Is this normal because the tablet has no LTE or is the reason for the missing IMEI that the tablet is a retail model?
I can't open the sd card slot. When I tried to stick a needle in this small hole on the right side of the tablet nothing happens.
Maybe someone with a "normal" S2 can tell me if there is a little trick to open this slot? If not I think the reason too is that I have a retail model.
Did you install firmware for the t815 and the custom kernel?
I installed the firmware for 5.1.1.
After that I installed cf_autoroot 5.1.1
Oh, now i read that i have to install your kernel too. sorry, i will try it now.
All is fine now!
Thank you again!
schrimmschramm said:
Android 5.1.1 runs now on my S2 One little issue: if I install now "t810_cf-autoroot_5.1.1.tar" with Odin I run in a bootloop. Maybe there is another way to install SuperSU?
After installing "Phone Info Samsung" I can see the tablet has no IMEI. Is this normal because the tablet has no LTE or is the reason for the missing IMEI that the tablet is a retail model?
I can't open the sd card slot. When I tried to stick a needle in this small hole on the right side of the tablet nothing happens.
Maybe someone with a "normal" S2 can tell me if there is a little trick to open this slot? If not I think the reason too is that I have a retail model.
Click to expand...
Click to collapse
I have the same model (SM-T810X) and i can open the sd-card slot. press down fairly hard to open the slot.
i have a question for you. Did evreything went well with the software ? I am thinking of rooting myself but i am a bit afraid of causing more dammage then good.
sikkie81 said:
I have the same model (SM-T810X) and i can open the sd-card slot. press down fairly hard to open the slot.
i have a question for you. Did evreything went well with the software ? I am thinking of rooting myself but i am a bit afraid of causing more dammage then good.
Click to expand...
Click to collapse
Flashing anything is always a risk even Stock firmware however considering literally thousands have already done this success is more likely than failure.
I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627