Related
This thread is for people that want a faster and more reliable method to get root/custom recovery and viper and Xposed plus debloating your device and not having to go through countless other threads to find files
I am not held responsible if you miss read and screw up your phone<----extremely hard to do with this method but if anything does happen either load your backup you make or just plug in your phone to kies and firmware update your phone it will bring your phone to stock firmware no root no custom recovery then you can restart
(sm-g903F and Canadian variants are also know as the Samsung galaxy s5 neo)<------ I know there different variants but this is for SM-G903F and Canadian variants ONLY
I will have all the file you need for everything you need
if its not a dropbox link it will be a play store link
ROOT
https://www.dropbox.com/s/pz8x0wj4f6okjdg/CF-Auto-Root-s5neolte-s5neoltexx-smg903f.zip?dl=0
make sure you have ------>(OEM UNLOCKED)<------MOST IMPORTANT,unknown sources, USB debugging all enabled or you will go into a bootloop or soft-brick
flash this with ODIN everything should work fine
TWRP RECOVERY
as of right now that I know of the neo does not have a working CWM recovery soo TWRP will have to do
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
(when in the app look for this name Samsung Galaxy S5 Neo Exynos flash that one in the app and you should be good)
Viper4Android 5.1.1(audio mod)
(all of these are flashed in recovery EXCEPT for the presets you put those in the viper4android folder for presets that is created after you install the app it should be in your sdcard directory near the bottom)
please flash V4A2.3.4.0 then policy fix you should then be able to install the audio driver (use super high quality<----the best sound ) inside the viper app. then go to the settings tab and update the app.....
if when you install the new version viper stops working and there is no sound or it asks you to install the driver again please go and re-flash the policy fix then go install the driver
(viper4android 5.1.1)
https://www.dropbox.com/s/1grrl3yhghc8o2n/V4A2.3.4.0_Lollipop.zip?dl=0
im pretty sure this is the right policy file what it does is allows stuff like xposed framework and viper to run with SELinux set to enforcing
if you guys have problems just comments and ill fix anything
(policy fix)
https://www.dropbox.com/s/1pj5u0g5k7db6n7/ViPER4Android-supolicy.zip?dl=0
(Viper profiles)
https://www.dropbox.com/s/shfdoqvq1ioiejq/eXtremeBeats%20Viper%20Presets%20v1.0.zip?dl=0
XPOSED
(make sure you have ran the policy fix from the viper4android)
this is for stock or close to stock roms only!!!!!!
1.Install Xposed Installer App
Xposed installer App
2.Make a backup not needed but always helpful
3.Copy the Xposed file and the uninstaller to your sdcard
xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip (XPOSED FRAMEWORK FILE)
EXPOSED UNISTALLER FILE
4. Flash "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip"<---- Xposed FrameWork File) through TWRP recovery this is the one for our SM-G903F and Canadian variants that are running 5.1.1
if anyone has ARM64 system on 5.1.1 or 6.0.0 orrrrrr this phone with 6.0.0 contact me and ill put thoses files up as well
- ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
- ARM64 means the devices that are running arm64 operating system (Galaxy S6, Note5 and all their variants...)
- SDK22 means Android Lollipop 5.1.x
- SDK23 means Android Marshmallow 6.0.x
DEBLOATING&Disable annoying "Check battery cover"
for debloating just download this and flash with recovery and bam!!!!! done :good:
for Disable annoying "Check battery cover
just go into rom toolbox or anyapp that you can see system app and freeze or disable this apk "Popupuireceiver.apk"
Credits
Chainfire for root
twrp for recovery
wanam for xposed
ViPER's Audio founded by ViPER520.
Co-founded by ZhuHang.
CN. vipersaudio.com / EN. facebook.com/vipersaudio
Copyright (C) 2006-2016 vipercn.com / vipersaudio.com
FOR THE AMAZING VIPER4ANDROID
Nice which apps or data's will be all debloated by this file
LetMeShow said:
Nice which apps or data's will be all debloated by this file
Click to expand...
Click to collapse
ill have to get back to you on that I have the list but I may be merging with another thread soooo ill keep updated
I'll possibly will be merging with another thread but all this info is working
(make sure you have ------>(OEM UNLOCKED)<------MOST IMPORTANT) meaning I have to have an unlocked phone?
@adbpusher123: Thread merged. If anything needs to be changed, tell me
Thanks.
RE: Galaxy S5 Neo SM-G903W help question
[SIZE="7" said:
XPOSED[/SIZE]
(make sure you have ran the policy fix from the viper4android)
this is for stock or close to stock roms only!!!!!!
1.Install Xposed Installer App
2.Make a backup not needed but always helpful
3.Copy the Xposed file and the uninstaller to your sdcard
4. Flash "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip"<---- Xposed FrameWork File) through TWRP recovery this is the one for our SM-G903F and Canadian variants that are running 5.1.1
if anyone has ARM64 system on 5.1.1 or 6.0.0 orrrrrr this phone with 6.0.0 contact me and ill put thoses files up as well
- ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)
- ARM64 means the devices that are running arm64 operating system (Galaxy S6, Note5 and all their variants...)
- SDK22 means Android Lollipop 5.1.x
- SDK23 means Android Marshmallow 6.0.x
Click to expand...
Click to collapse
Hi I was going to try to install Xposed on a Samsung Galaxy S5 Neo Canadian variant (SM-g903W).
I'm currently rooted running marshmallow 6.0.1 with TWRP installed.
If I'm correct you have a specific installer for the marshmallow set up? please let me know.
Thanks
Are there any current roms available for the 903w (canadian version)?? Also can other 903neo roms be applied to it?
SH-G903W FRP - cannot get past verification
Hi I have a Samsung Galaxy 5 Neo Rogers Canada I cant seem to get past the FRP. I have tried to bypass it using an OTG Cable on a USB drive with the .APK to bypass. My issue is , when I connect the USB the drop down menu on the phone does not appear. I am assuming this is because the phone has the latest software installed onto it since the patch in Jan 2015. In order for me to install another version of OS i need to be able to turn on USB Debugging and Dev or I may soft brick the phone ? correct ?
in other videos online once the usb OTG cabel is connected a popdown menu lets you install the apk. I cannot get that menu to pop down.
So I am guessing my best bet would to be to revert to a version before the patch. Which I am having a hell of a time finding. I am very unsure If i can even load another OS without being able activate the Debug or Dev.
Can anyone help ? Im not sure what else to do.
also i appologive if this post is in the wrong directory
[email protected]
---------- Post added at 06:02 AM ---------- Previous post was at 05:46 AM ----------
I also just tried SlideSync and it looked very promising. Again, no pop up window when connected. Getting very frustrated. lol. please help.
gunsum said:
Hi I have a Samsung Galaxy 5 Neo Rogers Canada I cant seem to get past the FRP. I have tried to bypass it using an OTG Cable on a USB drive with the .APK to bypass. My issue is , when I connect the USB the drop down menu on the phone does not appear. I am assuming this is because the phone has the latest software installed onto it since the patch in Jan 2015. In order for me to install another version of OS i need to be able to turn on USB Debugging and Dev or I may soft brick the phone ? correct ?
in other videos online once the usb OTG cabel is connected a popdown menu lets you install the apk. I cannot get that menu to pop down.
So I am guessing my best bet would to be to revert to a version before the patch. Which I am having a hell of a time finding. I am very unsure If i can even load another OS without being able activate the Debug or Dev.
Can anyone help ? Im not sure what else to do.
also i appologive if this post is in the wrong directory
[email protected]
Click to expand...
Click to collapse
I just did my S5 Neo SM-G903W.
Follow the instructions for the 2nd option: 2. Bypass any Samsung Galaxy Google Account Verification without OTG
Once you've done that you have to make sure when using Odin that auto reboot is "unchecked" or it will boot into the oem recovery and not TWRP.
So once Odin gives you a successful pass, close it. Turn your phone off by pressing both volume keys + home + power key and it will shut off in a few seconds.
Then boot into TWRP by holding the Vol up key + home + power
However, there are no custom roms for the Neo, and the ones for the S5 (900 series) won't work; I tried.
Got it!
Thanks for your reply man I didn't think I was going to get any help on this. I actually did end up figuring this out I used a USB drive that had a light in it this way I could tell when the disc was being read I was simply being too impatient and not letting the disc read. I waited a few moments sure enough the menu popped up so I could go into settings using the APK. So all-in-all I did learn my lesson to be more patient , also to use a drive that had a light inside of it. However after I did get into the phone and put a SIM card in it said not registered on network.
Glad you got it working.
I have my S5Neo rooted by using SuperSU once I got TWRP installed.
So there's no custom roms which kinda sux, but at least with a rooted phone you can install great rooted apps: enhance the sound with Viper4 FX etc etc
And there is the bloatware remover.
Lot's of other great stuff on xda.
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
DJRenegade88 said:
I have searched a lot on the web and xda but cannot find any solutions. As far as I know I have correctly installed the Xposed framework using TWRP but when rebooting I get stuck on the Samsung logo screen and have to recover to fix. I have tried various versions of the framework and always get the same issue.
Android version - 5.0.2
Installed ROM (stock or custom ROM) - Stock ROM (Would install custom if it helps but cant decide which one yet)
Names of the file you tried to flash - I tried 3 - xposed-v67-sdk21-arm.zip, xposed-v72-sdk21-arm.zip, xposed-v86-sdk21-arm.zip
Error messages - none, but gets stuck at the samsung logo on boot
I really wanted to install the custom ROM Acheron, but dont think its compatible with my device so if anyone can recommend a good custom ROM I am all ears
Click to expand...
Click to collapse
https://mega.nz/#!yMQ0ABIb!X_FrC0Uds2By-liblHEa9TTdy5v0wWIb76Jxr2JzKRo try this
Sent from my SM-A9100 using Tapatalk
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Nergal di Cuthah said:
Not sure I'd blindly follow a mega-upload...but maybe I'm paranoid. @DJRenegade88 I know you say you searched the web, but it sounds like you're trying to use the official xPosed. There's a huge red sign stating that if you try that on Samsung you will boot loop. For Android 5'0.x you need arter's xPosed
http://forum.xda-developers.com/showthread.php?t=3113463
If you update to 5.1 or 6 you'll need to get the Wanam version instead (I'd link, but don't wish to confuse you as you have 5.0.x (sdk21)
Click to expand...
Click to collapse
yea I was trying the official and I have seen that red text about samsung bootloops lol, dunno how I missed that the first time, thanks for the clarification. Is there a specific version I should download? I see he lists a few, I am guessing the most recent (xposed-v75-sdk21-arm-arter97-snapdragon.zip) is the correct one?
The number "75" "86" etc is the version number so everything you typed is correct 21 arter arm but you want whatever is the highest, with one caveat: if there is an 86 a few modules will not work (in short they will be forbidden from running by xPosed for bad coding); I'm guessing quite a few of the 5'0'x specific modules may get caught by this. If you find a module you can't live without that doesn't work (and gives a very specific, noticeable error in the xPosed log) you might want to stick with 85
Doesn't work
It took 5 minutes to boot and now it's optimizing all my apps. I don't think it works.
I have an MTCD Joying head unit, and i've struggled from day 1 to get TT Go working on it.
I have a paid subscription and it is my preferred GPS software, so I was determined to get it working.
I tried many different ROMs but they were either buggy or unstable or just didn't let me install tomtom, or I could get a solid stable ROM but couldn't install Xposed etc.
As you probably might know, the problem usually lies with the huge serial number that these Chinese units have.
Anyway, without further ado, I will detail the process I used to make it all work properly using the latest stock firmware and some Xposed hacks.
I've ended up with a nice stable system, it's fast, it boots up in 14 seconds and I don't have any issues with bluetooth or laggyness or TT saying it can't connect etc.
Please make sure you use the EXACT versions that I used otherwise it might not work ( I had to try many permutations of different software to get this far ) .
I'm working from the latest Joying ROM dated 27th September please note it's an MTCD image, do NOT flash this if you have MTCB./MTCC.
So install the latest ROM dated 27th September, you can find it in post number 416 here
http://forum.xda-developers.com/and...-factory-firmware-rk3188-mtcd-t3366561/page42
Once installed you need to root the image.
Go into factory settings, and put in the code *#hct#root# you should get back the message "ADB ROOT"
Once ADB rooted, install KingoRoot
Once rooted, go and install SuperSU from the play store but don't run it. Just install.
After that, download and run SuperSu-Me v6.7 and let it run and reboot.
After reboot, run super su and let it update the binary
After that, download Flashfire app from play store
Press the + button in flashfire and choose ZIP option and flash xposed-v86-sdk22-arm-custom-build-by-dsa-20160715.zip
Unit restarts
after restart, install xposed installer
after installing xposed installer, find and download mtcservice-2.28.apk
open mtcservice and select advanced options > serial number
set a 12 digit serial number of your own choosing
open xposed, choose modules , tick the checkbox for mtcservice
reboot
install TT go from APK
bingo. Job done.
I'm sorry I can't actually post links to xda-developers yet but I can make a .zip file and upload it with all the files required in it if anyone needs it but someone else will have to link to it for me.
Cheers best of luck.
Cool! Will try. Please make a zip with all files if you can.
https://mega.nz/#!oB4FTZyJ!91wAORXxNh8Ukg8kwI_MJLXhhy0eCBWMNkBuQhv8DhQ
link has everything EXCEPT for:
kingoroot (all the online storage places say it has a virus in it .. I got it from https://root-apk.kingoapp.com/kingoroot-download.htm .. download at your own risk.
tomtom apk , again google for the APK i'm using the latest one tomtom GPS navigation traffic 1.12 since i have a subscription, and it's a fremium app anyway i think it's fair for me to download the APK
also would like to point out that the dmcu.zip and dupdated.zip is the stock firmware and ROM for a Joying MTCD unit.
do not flash these if you don't know what you are doing or don't have an MTCD unit and dont flash dmcu.zip unless you also have a joying unit..
good luck let me know how it goes for you.
Wow finally a solution! I tried almost everything. This finally worked. Thanks for the great step by step guide!!!
Hi Lordxenu,
I have an Erisin ES3015V and want to install Tomtom, because like you, I ever loved it.
However, my unit is an Android 5.1.1 with 1024x600, and think Tomtom is not able to install into units with a display larger than 800x600. Is yours 1024x600 one or not? This is important for me, because I've tried to install from Play Store but it refuses to do so, and I don't exactly why: 1024x600? Serial number as you stated?
Before getting mad trying to install, I want to have things as clear as possible.
Regards!!!
Hi
Yes my unit is a 1024x600.
I could not install from play store either. Either due to serial number or due to it not recognising what device you have.
But installing via my guide above works. Mine is also 5.1.1
Hi,
thanks a lot for your description.
I think this would be a solution for my 4046GD.
I have
MCU-Version:
MTCD_KGL_V1.75.2
Aug 9 2916 09:18:18
Android 5.1.1
Kernel:
3.0.101+
[email protected] #66
Thu Aug 4 20:46:10 CEST 2016
Build-Number:
rk3188-userdebug 08082016.10:58:46
Will this also work on this device?
Hi Dobhi
Yes. It should work. Your unit is MTCD and 5.1.1
You can probably try it on your existing image without having to flash a new one as long as its stable and fast.
Otherwise flash the provided image (assuming your units screen is in 1024x600 if not find the same image for your resolution
Let me know how it goes for you.
Hey Lordxenu,
thanks for the fast reply.
I have to say that i'm a complete noob depending on android devices...
Yes the resolution is 1024x600.
But I still have some questions...
I downloaded you zip and i think the "dupdate.img" is the image file to install, am i correct?
I found a little how to doc from Malaysk image and i think will getting it done.
you wrote:
-Once installed you need to root the image.
-Go into factory settings, and put in the code *#hct#root# you should get back the message "ADB ROOT"
--> Will there be a terminal or something like this, in the factory settings of the new image??
-Once ADB rooted, install KingoRoot
-Once rooted, go and install SuperSU from the play store but don't run it. Just install.
-After that, download and run SuperSu-Me v6.7 and let it run and reboot.
-After reboot, run super su and let it update the binary
-After that, download Flashfire app from play store
--> All fine here
-Press the + button in flashfire and choose ZIP option and flash xposed-v86-sdk22-arm-custom-build-by-dsa-20160715.zip
-->Where can i find this zip? ---> Update: got it meanwhile.
-Unit restarts
-after restart, install xposed installer
--> New: Will this Installer be the by the exposed.zip?
-after installing xposed installer, find and download mtcservice-2.28.apk
--> Where i can find this...i googled it but sadly there where no clear hits
Update: I found the mtcservice-2.36D.apk, but as you said...its not the same as you mentioned.
-open mtcservice and select advanced options > serial number
-set a 12 digit serial number of your own choosing
-open xposed, choose modules , tick the checkbox for mtcservice
-reboot
-install TT go from APK
thanks for your help!!
I'm a little nervous about this...I will not kill my new toy
bg
Dohbi
Hi
Will try to answer your question.
Yes. dupdated.img is the actual android image to flash. Do NOT flash the dmcu.img because you do not have a Joying branded unit. So ONLY flash dupdated.img
-> Will there be a terminal or something like this, in the factory settings of the new image??
No. There's no terminal to use (if you really want you could install one) but doing the ADB root is done via the "factory" app.
When you start the factory app it asks you for a PIN code. This is where you type in *#hct#root# and press OK. No terminal needed.
>Where can i find this zip?
It's in the ZIP file I provided.
--> Where i can find this...i googled it but sadly there where no clear hits
Again, it's in the ZIP.
As long as your unit really is MTCD then you can't really brick it using my instructions.
If at the worst you somehow totally screwed the unit, you would just flash it again using the same or another image.
Usually you can also just choose the "wipe /data" option in the recovery menu and you will be back to having a fresh image installed etc.
There are lots of guides / tips etc on how to flash these units on the XDA developers forum so you can just have a read but to be honest, you don't need to know anything about it before you do it. I didn't
Hey Lordnexu,
i think there was a little hickup at the zip download.
i downloaded it again...now i have all files!
I will do this update tomorrow and keep you informed!
Thanks for your support!
bg
Tobias
Sadly there is a problem with super-sume... it stucks in "Stage 6 cleanup"
I wait almost 30 minutes but sadly nothing happens...
do you have any ideas?
Breaking News.
I have no idea how...
but it works.
I simply skip the Super-Sume Cleaning, and do all the rest...
Now my TT is running perfectly, with one little issue....the navigation voice is very silent an i don't get it louder.
Again...Thanks for your support!
Or you could just run Malaysk's 5.1.1 for MTCD and make it easy.
http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
Not sure why supersume stuck. It did take a while on mine and appear to freeze but eventually continued.
Did you do it on your stock ROM or on the ROM from my zip ? But I'm happy it now worked for you.
And yeah .. the Malaysk ROM ... well as I said in the original post... these ROMs were super buggy for me. Things like bluetooth not working properly, freezing up, slow, boot loops when enabling modules in Xposed... so I gave up after trying 5 different Malaysk ROMs.
If you look in the ROM threads for MTCD literally everyone says the stock ROMs are faster. If Malaysk ROM works for you then great, it didn't for me.
>If you look in the ROM threads for MTCD literally everyone says the stock ROMs are faster. If Malaysk ROM works for you then great, it didn't for me.
There was a rough patch there when Xposed was first being ported to 5.1.1, but it is all working now, and there are in fact several people making their own builds for MTCD 5.1.1 ROMs now which are fast and stable and much more streamlined than any stock roms now.
We have even developed a tool that you can use to build your OWN rom and chose what options you want in it for MTCD.
You might want to check them out again.
Ok, I made all installation step by step but TT GO still get no connection. I use an 1024x600 MTCD headunit with the small da_anton beta3 rom (already rooted) and all is looking fine, even the 12 digit serial number.
I tried some different GO versions but everytime I get the "can't establish connection" message back. Any ideas ? What apk have been used ?
The id changing did not work for me.
Only xprivacy, a xposed framework modul, did it..
At start of tomtom some pop ups appears.
Allow all, block only identity.
Good luck.
Getapped and getalked with 6603
ok, thanks, will try this later.
I also tried the Xposed ID changer were you "could" change the serial, but no luck at all.
makes2068 said:
The id changing did not work for me.
Only xprivacy, a xposed framework modul, did it..
At start of tomtom some pop ups appears.
Allow all, block only identity.
Good luck.
Getapped and getalked with 6603
Click to expand...
Click to collapse
can you do a screen of permission?i tried but tomtom doesn't work
This thread is how I have managed to upgrade a Samsung S5 with Android 6.01 to LineageOS 16 with a Mac laptop running Sierra, in an attempt to keep on using it with my car infortaintment system.
First of all it's important to leave very clear 2 things:
ALL THIS INSTRUCTIONS APPLY TO A SAMSUNG S5 SM-G900F kltexx device. I don't know how it will work in any other device . This is what has worked for me and I'm sharing this with you all just hoping that will be useful for someone else.
YOU ARE THE SOLE RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE.
So let's get started.
Prepare your system:
You must have the Samsung USB drivers installed (I used the latest ones from Samsung - https://developer.samsung.com/mobile/android-usb-driver.html).
You need to allow your device to debug it using the USB. Instructions here: https://androidcure.com/enable-usb-debugging-samsung-galaxy-s5/
You need to install adb in your computer. The easiest way to do it is this one: https://www.cyanogenmods.org/minimal-adb-and-fastboot-windows/ although another option would be to install Android SDK platform tools, but thats much heavier (https://developer.android.com/studio/releases/platform-tools). Usually the first option is enough.
You need to ensure that your Samsung will always trust your computer. So connect your Samsung with your computer and when it asks if your computer can be trusted, make sure that you click on the checkbox with the option "Always".
ODIN:
You need to install a Recovery System in your device and for that you will need ODIN which is a tool created by Samsung to flash files to Samsung devices. It has a version for Mac which has worked for me. Go to this site to learn how to use it and to download it: https://macmetric.com/odin-for-mac/ or you can right jump to this site (https://forum.xda-developers.com/devdb/project/dl/?id=20803) to just download the version that worked for me.
ROOT : (Optional)
By default your device has the bootloader unlocked. This was something that drove me crazy as I couldn't find anywhere to show me if it was. I ended up rooting my device to confirm that it was unlocked and also to confirm the real name of my device. So it's almost 100% certain that your Samsung S5 has the bootloader unlocked, but in case you want to confirm it, as I did, follow the instructions from this thread https://forum.xda-developers.com/showthread.php?t=2696537.
Basically, I ended up on this page, CF-Auto-Root homepage
http://autoroot.chainfire.eu/ downloading the file to root my device from there and flashing it with JOdin. Keep in mind that you might think that your device is version klte and there are at least 5 klte: kltedx, kltexx, kltezh, klteduosxx and kltejv. Mine ended up being kltexx
In my case I followed the process described in that thread and tried to root my device with the file for kltedx and it didn't wok out. Then I tried again with the file for kltexx and it worked. That's how I discovered that mine was kltexx.
TWRP :
You need to install a custom recovery system to your Samsung S5 device to be able to flash the LineageOS ROM. This site has the instructions that I followed to install it: https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
It is extremely important to highlight that the latest version of TWRP didn't work for me. I installed the latest one and everything seemed to be OK but it was not. I couldn't flash any ROM with it. I ended up discovering that for my case, the best option was to install an older version. To be more precise, version 3.0.2.2 (https://eu.dl.twrp.me/klte/twrp-3.0.2-2-klte.img.tar.html).
To make sure that you have been able to install TWRP do the following. There are 3 ways to boot your Samsung S5: Normal boot, Download mode (ODIN) and Recovery mode. We need to start up on recovery Mode and see a screen menu similar to the one we've seen in the previous thread (https://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/).
To do so, start the device on Recovery mode:
For the Normal mode you just click the Power Up key and wait. No magic here.
For the Download mode you have to switch off your device and then click at the same time the Power Up key, the Volumen Down key and Home key. It comes with the standard installation, so no magic here either.
Home Key
For the Recovery mode, you have to switch off your device and then click at the same time Power Up key, Volumen Up key and Home key. After a couple of seconds, the screen will say at the top "Recovery option..." and you should be able to see the touch screen menu of TWRP.
Flashing LineageOS 16 :
This is suppose to be an easy step but it ended up being very complicated because my device name was not properly being exposed by my device. So I ended up modifying the installation script to ensure it didn't matter.
So, you have to download not only the LineageOS version but also some other packages like Google apps, that are not installed and that you will need, and also the rooting package, which is always handy.
So the instructions and the links to download the packages are here. You might go there, read them and download all the packages: https://wiki.lineageos.org/devices/klte/install under the section Installing from Recovery....
Once you have all the packages ready to install, before you follow their instructions, you will have to do some hacking that you will find here explained here: http://www.lineageosdownloads.com/fix-error-7-lineage-os/ under section METHOD 1: UPDATER SCRIPT HACK TO FIX ERROR 7.
Basically, what I did was to edit the zip file using vim editor from the command line. You type "vim lineage-16.0-20200726-nightly-klte-signed.zip" (being lineage-16.0-20200726-nightly-klte-signed.zipand the name of the lineageOS image) and then go to "META-INF/com/google/android/updater-script" and then edit the file removing all the lines where it has any reference to the device name which are usually the first lines of the script containing the getprop(...) lines of code. To remove them, just click "dd" and they will be removed. Once they are removed, click on "Esc". Then type ":wq", it will go back to the previous screen, and then click ":q" and taht will be it, you have the package ready to be installed.
Now follow the instructions that you read previously and you should be able to have your Samsung S5 updated to LineageOS 16.
And now comes the part that I haven't resolved yet. How to install Mirrorlink in this device. So far I have managed to get several version of the Driverlink APK from Samsung but I'm not able to install them because when I try to do it using adb in root mode, I get the following message: "Package com.sec.android.automotive.drivelink has no signatures that match those in shared user android.uid.phone; ignoring!".
I know it has something to do with the signatures of LineageOS and that I need to sign the APK file with the LineageOS ROM signatures, but so far I haven't been able to find how to do it.
So I'll keep on trying and posting my discoveries here. Anyway, if anyone is willing to help me, it will be very welcome!!
I really hope that this helps others to take back from the closet their forgotten Samsung S5 and put it back to work.
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
guroth said:
I dont think it would help even if u did manage to install mirrorlink as samsung did drop support for mirrorlink.
Mirrorlink needs a new security certificate from samsung every month, and last certificate works until 2020-07-31
Click to expand...
Click to collapse
I'm still working on it. Anyway, the certificate is not a problem. Once I have mirrorlink working, I will install some applications that will install the certificate (like RockScout - "https://play.google.com/store/apps/details?id=com.carconnectivity.mlmediaplayer&hl=en_US") or LG Mirrorlink. And with them I will use other apps to take control of the screen like for example Full Mirror for Mirrorlink - "https://play.google.com/store/apps/details?id=full.mirrorlink&hl=en_US"
The main challenge is to be able to create the connection between the cellphone and the car.
There is a button "Translation" in notification bar in LOS, that is a mirrorlink by itself if I do understand this correctly. But klte SM-G900F on LOS 17.1 and lentislte SM-G906S on LOS 16.0 doesn't discover a mirrorlink device that is working properly with Samsung A50 on stock ROM (Anydata device, Windows 10 PC). One day I have managed to establish a mirrorlink connection between A50 (it was a transmittor) and SM-G900F (receiver) via some (can't recall it's name) app. But still I haven't managed to use S5 as a transmittor for mirrorlink...
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
bardell3600 said:
Problems & Solutions: Installing Lineage on a SM-T713, Samsung Galaxy Tab S2 8”
There are many sites offing Step-by-Step guides.
I used
https://wiki.lineageos.org/devices/gts28vewifi/install and/or
https://forum.xda-developers.com/nexus-7-2013/development/rom-lineageos-16-0-t3903286
(SEE BELOW for what’s missing from the instructions)
I have a 2016 Samsung Galaxy Tab S2 8.0 that seemed to be on its last legs. After all, it is the 4th quarter of 2020 as I write this. The current version of Android is 10. This poor old, much loved, tablet runs either Android 5, 6 or 7. Ancient, right!
I upgraded to Lineage 16.0 (17.0 was still “unofficial” in late summer 2020) – Android 9. All I can say is WOW!! A whole new tablet, or at least that is the way it behaves.
The process took me two days. It should have been about 2 hours. I’m writing this to save others those 46 hours of frustration.
I absolutely hate it when those that create the “How to” guides assume …
Don’t get me wrong I greatly appreciate and respect the intent and effort involved. Heck I’m doing a “how to” myself right now! But skipping info because “everyone” knows or because of an “assumed configuration” is unfortunate and causes major frustrations for others.
So things that didn’t work for me installing Lineage 16.0 on my Samsung Galaxy Tab S2 , SM-T713 region XAR.
Things they DON’T tell you:
• Let us start right at the end of that last sentence “region XAR.”
Look at any list of regions Samsung Firmware is released for that you can find. Canada is listed, United Kingdom is listed. Is USA, United States, or America listed? Nope! Somehow we are supposed to know that “Cellular south” is the correct firmware to use?
• The Tab S2 needs to have the Android Nougat 7.0 firmware. That makes sense. But would you presume that the latest 2019 Samsung Update, T713XXS2BSG1_T713XAR2BSB1, would not work?
It turns out that the latest (as of this writing) Lineage, lineage-16.0-20200928-nightly-gts28vewifi, requires a SPECIFIC Samsung Firmware Update -> T713XXU2BRB2_T713XAR2BRB2, dated March of 2018.
Repeated Error 7 from TWRP: Unzip the Lineage file. Look in META-INF\com\google\android and open the updater-script with notepad (Notepad++ is even better) find the “Target:” statement. It will tell you which Samsung firmware update the Lineage was built for.
• Odin won’t recognize the Tab S2:
and/or
Heimdall returns ERROR: “Failed to access device. libusb error: -12”:
Samsung firmware update requires Odin. Changing recovery to TWRP uses Heimdall. It appears these two Flash Softwares use different Windows 10 Drivers to communicate with the SM-T713
o After using Heimdall (and zadig-2.4.exe to install its drivers) you need to use SAMSUNG_USB_Driver_for_Mobile_Phones.exe to reinstall the Samsung Drivers if you want to use Odin3
o After using Odin3 and the required Samsung Drivers you need to use zadig-2.4.exe to reinstall the drivers used by Heimdall
• Tab S2 stuck on Samsung at boot after Samsung firmware upgrade:
Use recovery or TWRP, either one, to Wipe the Cache Partition
NOTE: I didn’t fix this boot loop issue after Flashing T713XXU2BRB2 and TWRP installed lineage-16.0-20200928 just fine . And lineage booted up A-OK.
There are things I haven’t told you that aren’t in the instructions either:
When you boot into stock recovery you’ll get “no instruction” – just wait it out
Flashing Lineage from your MicroCD is much easier than “adb sideload”
Odin takes a long time to load the Samsung Firmware before you can proceed
If Odin3 fails or especially partially fails, just do it again from the beginning
Boot into Recovery – Home + Power + Volume Up works best
Download mode - Home + Power + Volume Up works best
If you screw something up and can’t shut down – Power + Volume Down
Then IMMEDIATELY at black screen Home + Power + Volume Up – you can power off from there
Before Lineage install in TWRP
Wipe – Format
Wipe – Advanced - Cache & System
(Some instructions wipe more, DON’T)
If the Lineage install fails, you’ll have no OS and will need to reinstall a Samsung Firmware via Odin3
And more I’m sure
Click to expand...
Click to collapse
Thanks for this,
I am looking to breath some life into my wife's S2 8.0. Where did you get the March 18 firmware? I looked on Sam Mobile and I cannot download it as I am not a premium member. Her tablet is already on the July 2019 version which is what I downloaded this morning just to have on hand ( I am also in Canada)
**Update - I found a link to the firmware you mentioned and downloaded it**
Do you mind sharing the link to the download? thanx
RJC_68 said:
**Update - I found a link to the firmware you mentioned and downloaded it**
Click to expand...
Click to collapse
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
pas7771 said:
Hello there, do you mind sharing where you downloaded the right firmware?
Thanks a lot
Click to expand...
Click to collapse
It may have been this site
Galaxy Firmware - Samsung Galaxy Tab S2 8.0 (SM-T713)
Samsung Galaxy Tab S2 8.0 Android tablet. Announced Jul 2015. Features 8.0″ Super AMOLED display, Exynos 5433 chipset, 8 MP primary camera, 2.1 MP front camera, 4000 mAh battery, 64 GB storage, 3 GB RAM.
galaxyfirmware.com
We have sold all our android devices and gone back to Apple so I cannot be 100% sure.
Hope this helps