Related
Hi, I'm sorry if this has been asked before, basically a few weeks ago I was having problems with my Tab 2 p3110, it just wasn't running right. At around the same time I ordered an EZCAST hdmi device for my tv.
Well, I used Odin and cwm and taught myself how to upgrade to kitkat withCM11 nightlies, great stuff, fixed the issues I was having.
Then my tv dongle arrived, the one feature I wanted to use more than anything was screen mirror/AirPlay. No you can imagine my dismay when I couldn't even find the option in cm11, I found cast screen but it wouldn't work.
So, having tried several nightlies hoping the problem would be fixed I settled on reinstalling the stock 4.2.2 rom following the instructions on here. It bricked my tab 2 but I managed to get it going again and reinstalled the stock rom after several days of trying.
All this to find the screen mirror option was not available on the stock rom!! I can't figure out why but thought, maybe, an upgrade was needed, so I headed to the update tab to be told that my device was modified, updates are not available!
To be honest I'm ready to throw it in the lake behind my house I'm that frustrated, does anyone have any suggestions on getting screen mirroring working?
http://live.samsung-updates.com/index.php?device=GT-P3110
Here... get the clean firmware here. It will give a pure system that won't trip the modification check.
It will also give you the factory recovery system.
Look up the p311x PIT file and when in odin pick the size that matches your tablet.
If it hangs at boot try doing a factory reset from recovery.
That's what worked for me to allow me to check updates.
I can't say that this will fix screen mirror, since I've never used it or seen the option on my p3113
Sent from my SGH-T999 using Tapatalk
Thanks for that. I can't find my model number on the list, The british one is close and as thats where I live i think i'll give that a go.
Thanks again for your help
Didn't work, still saying that the device has been modified and in download mode shows "count 1"
Any other ideas?
Triangle away?
Sent from my SGH-T999 using Tapatalk
Hey, I use my tablet with the Samsung Smart View ap.
You must have the right samsung tv for it to work and it's not perfect, but it is a nice feature. I stopped updating my tab because this is the most important feature for me.
I rooted my device and have the same issue as you, that's how I came across this thread.
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
I accidentaly flashed the edge version of twrp to my regular s6, 920r4. Now my touchscreen is reversed along the xaxis. When I dial *#2663#, nothing happens, only a dialtone goes on. Any suggestions?
Reflash regular S6 5.1.1 stock ROM via odin.
I did that, still no fix. Then I did a full reset, no fix.
Bring your S6 back to Samsung for repair.
roydok said:
Bring your S6 back to Samsung for repair.
Click to expand...
Click to collapse
Obviously my knox is tripped after flashing TWRP, would samsung be able to fix this anyway?
I hope so...
In other related threads, members were able to use the "secret codes" to update the TSP firmware. Could I perhaps install say the firmware for the 920F, then access the secret codes on that firmware, and in that process update the TSP firmware?
Flash this S6 regular S920R4 5.1.1 stock ROM instead of G920F:
http://www.sammobile.com/firmwares/download/48614/G920R4TYU2BOF7_G920R4USC2BOF7_USC/
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
This did not do anything for me. Could i just use the right one instead and all should go well? or there be another solution?
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
I finally got this issue fixed after almost half a year. I updated the firmware to a newer version, using the software update on the phone. My issue is finally fixed. I think that perhaps the several months new software update was different enough to require a complete changing of the recovery software.
Or at least something like that!
No longer will I be using my old s4, running liquidsmooth, that restarts 3-4 times a day. With a shattered screen at that!
Resurrecting the Thread
lagvoid said:
Posting this for future reference for anyone that comes across this issue. The instructions below resolved my reversed issue.
@ScottBroker - If that happens again, you will not need to exchange your device. In the dialer, input *#2663# and select the "TSP FW update (General)". In order to do this, you would have to actually press "TSP FW update (Internal Storage)" since your horizontal touch is reversed.
Click to expand...
Click to collapse
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
wolkowicz said:
Hi I have got same problem. but afters tiping *#2663# nothing hapend. What can I do?
Click to expand...
Click to collapse
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
After rebooting my phone couple of times it works. Thanks!!!
Ishmael89 said:
A year after OP, I've ran into the same issue as the OP.
I accidentally flashed an edge kernal (I think, might've just been an incorrect baseband) on my flat S6 (920t). Tried things from flashing correct kernals to wiping to Odin restoring stock firmware. Nothing worked, then I found this and my problem was resolved in 2.4 seconds. I laughed at myself for this one :silly:
(Note: I had a TWRP backup, but didn't try restoring because it was from a previous firmware and I'm not sure it would've worked, which is why I searched for other solutions...and found this one!)
Click to expand...
Click to collapse
Ishmael89 said:
Which model do you have? The dialer menus might be specific to the model/carrier, I'm not certain about that though.
Click to expand...
Click to collapse
wolkowicz said:
After rebooting my phone couple of times it works. Thanks!!!
Click to expand...
Click to collapse
No problem, glad it worked out and you can use your phone regularly now!
As I have found multiple threads for the same issue, I figured I would post the info in a few of them so if anyone else come looking for the issue and fix - they can get right to the howto instead of digging through multiple threads like I did. More info about the issue was found on the following link/s - https://1024kb.co.nz/galaxy-s6-reversed-touchscreen/ & https://forum.xda-developers.com/showpost.php?p=62289392&postcount=9
You DO not have to flash any stock roms or other versions of twrp to fix this, as it will NOT fix the issue, as near as I can tell something corrupted or changed the setting somewhere on the hidden section of the phone's firmware. All you need to do is access a hidden engineers menu, click on a button and your done.
The hidden adjustment setting is accessible through keypad *#2336# (reverse-entered as #*2114*) (you have to do this as the touchscreen is still reversed so you are unable to enter *#2336# normally). Once the task completed I then was able to press the back key and have it function as normal which confirmed the fix.
Hello there,
Please forgive me if i posted this thread on the wrong place.
-I would've not posted a thread here unless this got serious, so i own a Samsung Galaxy S6, it's 1 year old phone, when i first got it, i used it normally like everyone else and had no problem with it, but my curiosity got me to root the phone, i still did not get any problem with it until i chose to add a ROM. I used NNE 5.1 S8 port and it was working well until it got my phone broken somehow.
-My phone started acting really strange after 2 months of activity of that new ROM, my phone just started restarting randomly and it got me worried, i thought it's an application problem so i first just factory reset it. It seemed it was not the problem on an application, so i chose to change my firmware to a stock one. I searched up recently on the newest firmware for S6 and i found out it's: XEF (France) , PDA (AP): G920FXXU6ERC1 and CSC : G920FOXA6ERC1 on 2018-03-22. I Downloaded 4 files: BL,AP,CP,CSC , and i found out about PIT on one of the posts in this forum (Filename: SM-G920F-ZEROFLTE_EUR_OPEN.pit).
-Before i flashed with Odin, i wiped System, Data, Cache and Dalvrik Cache. The firmware worked well but after 1 hour it started doing the same thing but now differently. It happend to me only 1 time that it froze up on an application, but i think that is just an app problem. The main problem is that when i lock my screen, i cannot unlock it anymore, it just freezes there until it restarts after a short period of time. After the restart, it just keeps going, restarts, asks for pin, restarts and so on.
I tried removing the sim card and putting it back in, did not work.
I tried Safe mode, still same.
Model of phone: SM-G920F
Current firmware: XEF (G920FXXU6ERC1)
Android version: Nougat (7.0)
If you can help me, or you know something about this problem, please repost here, i would be really grateful since this is my only phone
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
lenovot said:
Ininstall twrp backup everything most important efs partition.
Install samsung switch and pray that it asks you to do an update. If not try to flash a diferent version of nougat for example November security patch and try again with samsung switch
Click to expand...
Click to collapse
How could samsung switch possibly help?
I did flash it with different versions already, but no luck :/.
I've been praying a lot for this lately but it is not working lol
Please Bump this!
try doing this.
1) go here: https://updato.com/
2) choose download 2 roms. 1 nougat and another marshmallow (to my knowledge, stock roms are one file. no more splits and unless otherwise stated... no need for pit)
3) first flash nougat using oden
4) try the phone for a few some time.
if after a set amount of time, phone works fancy and no issues present then it's solved.
if not... install marshmallow. then try again.
if all this fails then...
install nougat. as soon as possible afterwards install twrp.
boot into twrp and just leave it there. my twrp locks after a while and screen goes dark until user interaction (just like it's supposed to)
if the same thing happens then its a hardware issue... probably... (i have had my main board fail... kinda similar not similar issue... hope you dont have the same issue and that its just software related)
good luck.
In my case every time there was an update available it would download the whole firmware and by doing so you would get the most fresh and updated version. Also it updates every partition to match
S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!