What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab
Related
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
I just ordered my sprint s7 edge. And have a few questions. i am looking for somthing up to date and not from march which seams to be most of the threads i find regarding this topic.
After browsing the S7 edge for Att, verizon, T-mobile and international it seams they all have root, roms and recoveries. What is so different about sprint?
Main things i want from my s7 (short of installing a slimmed down rom) is Full ad blocking (Not just in browser ad blocking) and titanium backup for freezing apps, backing up call log and SMS/MMS and the likes.
Any help would be great, thanks.
ch0de said:
I just ordered my sprint s7 edge. And have a few questions. i am looking for somthing up to date and not from march which seams to be most of the threads i find regarding this topic.
After browsing the S7 edge for Att, verizon, T-mobile and international it seams they all have root, roms and recoveries. What is so different about sprint?
Main things i want from my s7 (short of installing a slimmed down rom) is Full ad blocking (Not just in browser ad blocking) and titanium backup for freezing apps, backing up call log and SMS/MMS and the likes.
Any help would be great, thanks.
Click to expand...
Click to collapse
We first of all please take time and read up on the phone.
Basically there are various models of the phone but two processors.
The Qualcomm (US versions with T-Mobile, ATT, Spring and Verizon) all are Qualcomm. The Qualcomm phones (to include your Sprint phone) have locked bootloaders. What this means is that you cannot ODIN flash anything not signed by a carrier or by Samsung. It just won't install. If you do manage to acquire root and modify the system, the kernel will cause it to bootloop. Currently, we have an engineering kernel that allows root access and to boot the phone... but many to most people (to include my own experiences) report the phone to run sluggish (or lag), hot and with terrible battery life. Most I can ever get from my phone before rooting was about 20 hours. I get about half of that now. A lot of games are unplayable now and sometimes the phones just lock up and/or crash for no reason. A few have even reported waking up to see their phones stuck in a bootloop and had to flash the stock firmware and re-root just to fix it. So.... we're a long way from perfect regarding rooting.
Some things to research:
After rooting you'll notice a strange icon. That's the RCS icon. There are threads with instructions with how to remove it.
Look up Busybox on Rails to install busybox. You'll need that.
Lookup and install Flashfire from Playstore. You'll likely need that.
We don't have a custom recovery so Flashfire will be as close as you can get.
Just in case, download a copy of your firmware from Sammobile.com. You'll never know if you need to restore back to stock.
Also, check my signature for a guide from psouza4. That'll really help.
Remember that almost nothing that you can think of is original so I'm sure that almost anything that you can think to ask has been asked before. Search before posting.
Good luck!
Hi all,
Was recently in the 'States and broke my S8 - it's now the third mobile screen I've busted since Samsung brought in curved edges, never had any issues with the S2 or S5 - who ever thought tempering glass and curving it would be a good idea??
Anyway I had the opportunity to pickup a brand new Samsung Galaxy S8 Active and did a quick bit of research. I found the most compatible version with my carriers back home in AUS was the SM-G892A from AT&T. Picked up a brand new unlocked model, stupid me didn't connect it up to AT&T while I was there. I turned it on and played around with it on Wifi for the last few days of our trip and returned home to Melbourne.
Basically I now understand AT&T are a bunch of ***** and do not allow updates to be pushed even for unlocked devices overseas. Considering a lot of the updates are for security I'm very surprised by this.
Anyway so I've notcied a few tiny bugs here and there with apps/OS and figured updating my device/OS is the way to go and might resolve the issues. I guess the easiest way to get the info I need is to put the questions I have individually, as my mind tends to jump all over the place when I'm working a problem:
1. Is there any way to get my phone updated without rooting/flashing the phone?
2. If not, what is the best option for a S8 Active? Are there any firmware versions that will enable OTA updates so I don't need to keep flashing everytime new firmware is released? I have seen some posts about T-Mobile being able to be flashed over an AT&T model or even the G892U or maybe a custom firmware that allows this?
3. Will rooting/flashing interfere with any of the carrier settings etc? Don't want to upgrade it only to find it disables an LTE band or something?
4. I am an absolute noob at flashing, have never done it but am pretty tech savvy so if there is a step-by-step procedure I wil have no dramas following it. Saying that, I would rather not make the device worse than it is so I only want to follow tried & tested procedures if that makes sense, I don't want my device to be a lab-rat.
5. If there is no way to enable OTA internationally as per Question #2 when new firmware updates become available on XDA will flashing a new update delete personalisation/settings/files etc? Or will it retain them and update like a stock model performing a firmware upgrade would? If not, that would be a pain in the ass and time consuming to have to re-apply settings and reinstall apps every time and almost makes the idea of flashing unattractive.
6. I have baseband G892AUCU1AQG4 - taking into account Question #2 what is the best way to move forward? Considering Android 8.0 is available for the S8 Active and has been available for my model from AT&T since March 1st, 2018 apparently I'm hoping there might be some way to move towards that.
Hope someone might be able to help,
Thanks in advance
UPDATE 05/05/2019
Got some answers to my original questions...
1. Rooting/Flashing are different things - rooting allows custom firmware, flashing is the procedure to install custom or OEM firmware onto the device.
2. The best option for me I think is to just update to newer AT&T firmware so I get the updates and new software features as I'm not interested in custom firmware. I still do not know if it is possible to get OTA updates for this device directly from Samsung/Google.
3. As long as you are flashing from the same model firmware as in SM-G892A to SM-G892A should be no issues, however using SM-G892U might cause issues.
4. Once I wrapped my head around how baseband versions of firmware work and what is needed to get between bootloader versions flashing from SD Card or Odin (as I suspected) was very straightforward thanks to some of the guides out there. To make this easier for anyone facing the same issue I have written how I did this below.
5. Yes, flashing for AT&T will delete everything, it's an absolute PIA and that's why I will keep searching for a way to get OTA updates enabled if at all possible. However I believe Samsung SmartSwitch is pretty good for backing up and restoring so that might be a simple way forward.
6. See my latest post, I was 12 updates behind but able to skip 7 of them using my method.
I'm considering importing an S8 Active AT&T and have the same questions. How did you go?
secateurs said:
I'm considering importing an S8 Active AT&T and have the same questions. How did you go?
Click to expand...
Click to collapse
Sorry for the slow reply I've only just had the time to dive into this. Yes I have figured it out.
There are two ways, incrementally update by applying OTA updates via the SD card. However trying to find all of these can be a pain.
The other way you may have read about is to use Samsung's own 'Odin' flashing software.
Because I had the very first baseband version G892AUCU1AQG4 I was way behind. The fifth-last digit designates the bootloader version, you cannot jump from v1 to v3 for example. So what you can do is use a few OTA updates to jump you from v1 to the first v2, you can then use Odin to jump you all the way up and use another OTA to get you to the next bootloader version. Hope that makes sense?
So I was able to use x2 OTA updates to get from 1AQG4 to 1AQJ2, then I was able to do one more OTA to get from 1AQJ2-to-2AQK3. Now if I was to continue using the OTA method with the SD card, I would need to run the process x8 times. This presents 3 issues:
1. Time consuming, trying to find all the correct OTA updates.
2. Even when you do get all the correct OTA updates you then have to copy each on to the SD card waiting for the phone to update and then repeat the process.
3. Even if you can find a link for a required OTA update a lot of the links are dead.
However using Odin and the flash files I was able to skip these and go directly from 2AQK3 to 2BRF2, use one OTA update and then I was onto Bootloader v3 (which is the latest version). Here is how I compressed 12 updates do into 5, good luck..
1. 1AQG4-to-1AQJ2 OTA (SD CARD): dropbox.com/s/ikor71zt1ec0nyn/SS-G892AUCU1AQG4-to-S1AQJ2.zip?dl=0
2. 1AQJ2-to-2AQK3 OTA (SD CARD): dropbox.com/s/ott9fs9qunkvf9x/SS-G892AUCS1AQJ2-to-U2AQK3.zip?dl=0
3. 2AQK3-to-2BRF2 Odin Flash : androidfilehost.com/?fid=1322778262904016415
4. 2BRF2-to-3BRG1 OTA (SD CARD): androidfilehost.com/?fid=1322778262904016441
5. 3BRG1-to-3BRL1 Odin Flash: mega.nz/#!7M42VCAJ!-FKnhzwTZG0He1kb9FzHHaPX4Aanlnj4fpn0M61DzR4
Have the s8 active outside of America and desperately want to update it
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.
None2939 said:
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.
Click to expand...
Click to collapse
So you are on Bootloader v2 (5th character from the right). So you can skip straight to Step 3. Be warned all instructions below will result in all data on your device being wiped!
Using Odin to upgrade as directed on Step 3 & 5 or future upgrades (there is now v4 software appearing):
You need to download Odin (you don't need a modified/Comsy version).
You need to enable Developer Options on your Galaxy.
Once you have developer options you need to enable 'USB Debugging'.
You need to shutdown your Galaxy.
Connect your USB cabble to your PC.
Boot into Download mode by using the Power+Bixby+Volume Down combo. OR if that doesn't work Use the Power+Bixby+Volume Up and use the menu to get into Download Mode.
Open Odin on your PC, it should say 'Added' if it detects your Galaxy correctly. If it doesn't you may need to install some USB drivers (you can Google how to do this).
Once it says 'Added' you can add the files from Step 3 and flash but be warned it will wipe everything on your device.
For Step 4 OTA:
Very simply download the ZIP file and place the complete ZIP file on an SD Card (it should not be extracted must be complete ZIP archive). Place the SD Card in the Galaxy, power off and boot into Recovery Mode Power+Bixby+Volume Up. Then simply use the Volume Up/Down and Power keys to navigate through, 'Apply Update from SD Card', find your SD card and the ZIP file and allow the update to run.
(SOLVED)
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2
Hrafnblod said:
Hi,
Ive been searching around all week now trying to find a way to do the above, root my note 4 without a factory reset.
As far as i can gather, my bootloader is unlocked.
I suspect it has had somekind of non-t-mobile standard wizardry performed upon it prior to my ownership (2nd hand). The reason i think this (naive?) is as i understand it, these, in the UK, were locked to t-mobile sims new, however, mine can use any sim. also, since my ownership (couple years +), maybe 3 or 4 times it has randomly rebooted and gone into some kind of anti-"fiddling" mode stating something along the lines of "this phone has none genuine blah blah and is now locked. take it into a t-mobile shop to get fixed". A simple battery pull has "fixed" the issue each and every time.
Now, the actual main reason i want to root this, apart from the obvious other advantages, is to be able to perform a complete backup (including all the backup locked out apps). i have a few apps ive paid for, but have since been pulled from the play store, thus, should this phone die, i have no way of restoring them.
it seems that, the only way to backup these apps is to root the phone. i can only find ways in which to root my phone that involve a factory reset. hence im stuck in a catch 22.
According to posts i've read, fastboot doesn't work with my phone. I have been reticent to actually follow through with any method which may reset/factory wipe my phone (as, if i understand it correctly, changing the bootloader/recovery will?).
even though i have found apk's for some of these apps, they are only for the trial versions, and not what i have previously paid for. furthermore, some of these companies have either gone bust, or simply refuse to respond to my emails. losing their cache i can live with, losing the full apps i "can't".
i use a laptop with arch installed. i have occassional access to a windows10 pc.
please please tell me it is possible to root this phone without losing these apps. Or at the very least, a way of pulling/backing up these apps.
ive not found a browser that can see into the data\app folder. adb can see into the data\app folder and pull apps, but not the apps i want to backup which have been pulled from the play store that ive paid for.
phone details:
model sm-n910t
android 6.0.1
baseband n910tuvu2eqi2
kernel 3.10.40 - 9385989
[email protected]#1
build no mmb29m.n910tuvu2eqi2
Click to expand...
Click to collapse
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.
QuoPrimum said:
Have you tried Odin? Samsung phones don't use fastboot but have their own flashing tool.
Click to expand...
Click to collapse
I'm now rooted, cheers
I used ODIN on windows and CF_Auto Root.
I was just incredibly worried about getting a phone wipe/reset. I think, with having read through so many different guides and discussions, and having first tried to find a linux only solution, I'd ended up confusing myself. It just seemed that, when I thought I understood the process enough to actually physically start the rooting, all I could see was boot loop, bricking and factory reset issues in the guides.
Awesome forum.
Any apps you buy on the play store don't just disappear.
Check your actual purchase list for your Google account, it'll force a cached page.
Which is how I found out Activision pushed a (paid) mobile version of Zombies, removed it, then pushed the same game to the market which they continued to update.
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Flapjack said:
Hi everyone.
I just recently got a used S5e, mostly for the Dex capability. I am a consultant, so sometimes I'm in a location where I need a desktop, but don't always have room for my 15" laptop. I haven't had a Samsung device in years... preferring brands with easy root and a nearly limited skinning (currently, OnePlus devices... basically).
I had kind of resigned myself to not having root on this device, since it is a Samsung, so I was surprised when I came on here to see if anyone else was having the update problem, I found root threads. Currently, my device looks like it's on the May 2019 update (One UI 1.1, Android 9, Build PPR1.180610.011.T720XXU1ASED).
Still trying to resist rooting the device, especially since I saw the no-root debloat thread. But I would like to know how to get this stupid thing updated. From what I've read, it has to do with an XML file containing a Samsung URL that returns a 404 when queried manually. The software updater doesn't reflect that, though... and just says you're up-to-date.
So if I can root this and flash a debloated ROM, that would serve a few purposes. Otherwise, if there's a way to force an OTA (or find it and download it to the SD card), that would be fine, too.
Any advice.
Click to expand...
Click to collapse
If I'm understanding you right, you just want an OTA update applied? If that's the case, Frija is what you want to get the latest firmware for your device, and Odin will be your flasher. For stock rom flashes you don't even need an unlocked bootloader, much less root!
There are a ton of guides for Odin available, but still, if you have any questions please post!
Thanks for the reply!
I've used Odin quite a bit in the past, but I do know different situations need different files, so I'll probably do a quick refresher.
As for root, it definitely is a nice-to-have, mostly to remove bloatware, but if the debloat thread here works pretty good (and someone has info on just how much I can remove and keep Dex functionality), I would love to know that as well.
So, I am having a new problem. Using Frija, I downloaded the latest update. However, no matter what I do, I can't get a PC to recognize the tablet in download mode. It just says something about Windows not being able to recognize the device. In Device Manager, it says: "Device descriptor request failed". I've tried with and without the Samsung drivers, with three different USB cables, on two different PCs.
I'm worried that something is physically wrong with the USB port. That doesn't really make sense, though... as it charges fine, and shows up in Windows correctly once it's fully booted to Android.
**EDIT**
False alarm. I needed to press "up" again after getting into download mode and connecting the PC. So odd. It's updating now!