Related
I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
How to Root a Samsung Focus Windows Phone
the_professor. said:
I have a samsung focus I look threw the forums can i cant find one for os version 7.10.7720.68, I want a rom that has multitasking if at all possible and custom text tones
Click to expand...
Click to collapse
First off, I am not the creator of any of the resources listed below. All thanks should go towards: Dark Forces Team, WindowsPhoneHacker, and the many others who created these tools. Be sure to thank everyone whose tool/website/ROM you used by buying them a drink. Also, I am not responsible for any damage/bricking/etc that may occur as you attempt to modify your phone.
To address the the absence of OS version 7.10.7720.68, I would like to note that OS version 7.10.7720.68 is the original Mango update provided by Microsoft. Since then, Microsoft has continually updated the OS with minor tweaks (think: service packs) for Windows Phone. Though Samsung (or AT&T or whoever) has not provided these minor updates OTA, ROM developers for the Samsung Focus can bake them into their ROMs. Thus, any ROM with a version number higher than 7720.68 will contain all of the features you request (and more). More information as to the features added/fixed in the OS updates are given at the following link.
(link 1)windowsphone.com/en-us/how-to/wp7/basics/update-history
Now, the easiest place to start the rooting process is by visiting WindowsPhoneHacker's YouTube channel. There is a tutorial available (see the following link) that walks you through the whole process. I strongly suggest you watch the video several times to get a good idea as to the process required. Be sure to like the YouTube video if you find it helpful (trust me, you will).
(link 2)youtu.be/0dSTahZY4mI
I also suggest reading the more detailed information provide by WindowsPhoneHacker (see link below). The link takes you to the "Jailbreak" portion of the website which gives useful information on how to root and install custom ROMs. Read the source and the referenced sources three times or more before you even think about rooting your device.
(link 3)windowsphonehacker.com/articles/the_complete_guide_to_jailbreaking_windows_phone_7_and_7.5-09-24-11
At this point, you should be ready to root. Give it a shot. Be patient, stay calm, and good luck!
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.
Hello xda community,
I would like to try my hands at building Lineage OS for the Galaxy Note 4 Duos. I was a little surprised that there seems to be not even an unofficial build for it (or cyanogenmod for that matter). Is there some technical reason why it hasn't been attempted yet that is specific to the Duos?
Otherwise, I'd be happy if someone could point me in the right direction. Maybe someone who already did it for a different model could post a basic guide since I have no experience yet in this area.
Speaking of it, my current level of experience is that I have rooted and flashed roms on android phones a few dozen times, and developed a handful of apps for android. So hopefully it's not too far outside of my skill-level.
Thank you in advance.
You can take a look at Note 4 General section, a new thread was made on how to build LinageOS for the Note 4 N910F/N910G. N9100 will not support 2nd sim if im not wrong, you need a dev who want to work on this project
Try this:
https://drive.google.com/open?id=0By...llGSnVyVDVfRlE
I downloaded this from the Chinese website. The latest build is 29 April. Donno why. Give it a try.
Thank you very much, I'll give it a try when I get to it.
Btw. the url is incomplete, I'm trying the original thread.
Did it work for you? (the April 29 build )
akshayarajdayal said:
Did it work for you? (the April 29 build )
Click to expand...
Click to collapse
Kind of. Fingerprint and HDR camera don't work, which was expected, but for some reason phone calls don't work for me, I can call and receive, but there is no sound on either end. Otherwise everything seemed fine and the phone performed relatively well.
twrp-3.2.0-0-trlteduos official build release candidate!
twrp-3.2.0-0-trlteduos.img
twrp-3.2.0-0-trlteduos.tar
I've finally managed to build it from a pure omni device tree borrowed heavily from _mone's trlte twrp device tree. Chinese variant users: please test it as thoroughly as you can, including backing up and restoring with and without encryption. If it works, _mone will push it for official support.
ripee said:
twrp-3.2.0-0-trlteduos official build release candidate!
twrp-3.2.0-0-trlteduos.img
twrp-3.2.0-0-trlteduos.tar
I've finally managed to build it from a pure omni device tree borrowed heavily from _mone's trlte twrp device tree. Chinese variant users: please test it as thoroughly as you can, including backing up and restoring with and without encryption. If it works, _mone will push it for official support.
Click to expand...
Click to collapse
The links are broken
I just bought an S5E, and having owned two previous Samsung devices, I expected a fair amount of bloat, but not nearly the amount I discovered. It makes my previous two Samsungs look downright slender. Particularly loathsome, in my view, is the way SS has hijacked Find My Mobile and Google Messages, the latter of which, as a Google Fi customer, I have to use for SMS.
Hence, I am going to root, and cleanse this otherwise delightful device with the fire of 1000 suns. I have rooted Android devices before, but it's been a while, and my memory hasn't improved with age, so I have several questions, some about rooting in general, and some specific to this device. I should add that, while I am not opposed to performance gains and newer versions of Android and suchlike, my only pressing concern is to de-Samsungize the bejeebers out of this thing. Other than that, something like a stock version of Android and an otherwise low-maintenance tablet will make me very happy. So, here goes:
I have the PewPewk method bookmarked, and believe I have one or two others using various combinations of ADB and Magisk and suchlike bookmarked. I imagine I can handle them, but they look complicated. Are any of the apparently simpler approaches found here effective, sufficient to achieve my goals, and unlikely to brick me?
What are the advantages of Custom Android Recoveries relative to the stock Android, and if they add much in the way of complications, can I live without them?
Do I need a custom ROM, and more specifically, do I need one to give me non-Samsungized versions of Find My Mobile and Google Messages? At a minimum, I need the garden-variety version of Google Messages so I can text like a normal person, not a Samsung zombie.
Again, I don't really need tweaks for performance or new versions of Android, but I do need to get bug fixes and security patches with a minimum of fuss. How do I find that minimal sweet spot?
If the answers to one or more of these question are that yes, I need a custom recovery and/or ROM - I suspect this will be the case - then can anyone recommend good candidates that will get me the outcomes I'm looking for without perplexing me too greatly and making me want to cuss?
Can anyone identify the questions which I should be asking, but which didn't occur to me, and then pose them and answer them?
I'm confident that I'm in the right forum to get the answers I need, so all advice will be greatly appreciated.
smilejack1 said:
I just bought an S5E, and having owned two previous Samsung devices, I expected a fair amount of bloat, but not nearly the amount I discovered. It makes my previous two Samsungs look downright slender. Particularly loathsome, in my view, is the way SS has hijacked Find My Mobile and Google Messages, the latter of which, as a Google Fi customer, I have to use for SMS.
Hence, I am going to root, and cleanse this otherwise delightful device with the fire of 1000 suns. I have rooted Android devices before, but it's been a while, and my memory hasn't improved with age, so I have several questions, some about rooting in general, and some specific to this device. I should add that, while I am not opposed to performance gains and newer versions of Android and suchlike, my only pressing concern is to de-Samsungize the bejeebers out of this thing. Other than that, something like a stock version of Android and an otherwise low-maintenance tablet will make me very happy. So, here goes:
I have the PewPewk method bookmarked, and believe I have one or two others using various combinations of ADB and Magisk and suchlike bookmarked. I imagine I can handle them, but they look complicated. Are any of the apparently simpler approaches found here effective, sufficient to achieve my goals, and unlikely to brick me?
What are the advantages of Custom Android Recoveries relative to the stock Android, and if they add much in the way of complications, can I live without them?
Do I need a custom ROM, and more specifically, do I need one to give me non-Samsungized versions of Find My Mobile and Google Messages? At a minimum, I need the garden-variety version of Google Messages so I can text like a normal person, not a Samsung zombie.
Again, I don't really need tweaks for performance or new versions of Android, but I do need to get bug fixes and security patches with a minimum of fuss. How do I find that minimal sweet spot?
If the answers to one or more of these question are that yes, I need a custom recovery and/or ROM - I suspect this will be the case - then can anyone recommend good candidates that will get me the outcomes I'm looking for without perplexing me too greatly and making me want to cuss?
Can anyone identify the questions which I should be asking, but which didn't occur to me, and then pose them and answer them?
I'm confident that I'm in the right forum to get the answers I need, so all advice will be greatly appreciated.
Click to expand...
Click to collapse
Hello there
Your questions are really deep, maybe that is why no answers so far
I'm not an expert at all, so I can't give you comprehensive answers. But I rooted Tab S5e successfully (on stock ROM) and I've read a lot about modifying it, so I can share just few hints.
I wouldn't bother of any other rooting method than Magisk. However, this tab isn't as easy to root as most of the other devices... By far the best and comprehensive guide to root the stock ROM is here:
Galaxy Tab S5e (SM-T720) - Root Instructions (Release 1.0) | XDA Developers Forums (xda-developers.com)
If you follow it closely, you shouldn't have problems. I did it and can confirm it's working fine.
I haven't used custom ROM on this device, but there are some available, especially LineageOS from the recognized developer and one of the LineageOS team member. You can take a look on those threads:
[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1 | XDA Developers Forums (xda-developers.com)
[ROM][UNOFFICIAL][gts4lvwifi][11] LineageOS 18.1 | XDA Developers Forums (xda-developers.com)
In order to flash custom ROM you need custom recovery. There is TWRP available:
Samsung Galaxy Tab S5e WiFi (twrp.me)
Again, I did not try to flash it, I've heard it's tricky, so you need to dig dipper inside those threads and articles.
Alternatively, there is a method to debloat stock ROM without root. It is described in this thread:
[Guide] Samsung Galaxy Tab S5e Debloat Without Root-Info | XDA Developers Forums (xda-developers.com)
Hope it helps!
Thank you for your input. By the time you offered it, I had plunged ahead with the rooting method you suggested. Overall, it went well, but I'm having a few issues with the tablet since getting Lineage 17.1 installed.
I have made a new post requesting help with those issues, which can be found here. If you can offer any advice thereupon, I would be greatly appreciative, and if not, thank you for your efforts above.