Related
I recently received Acer Iconia A500 with stock 4.0.3 ROM (unrooted). I'd like to have root, flash recovery (prefer TWRP-like recoveries) and custom ROM (OmniROM 5.1.1 to get apps like MS Office/Word which 4.0.3 does not support). I've done a lot of background research on this matter but I'm really lost. There seem to be so many different methods of achieving this and none of them are written so that an unexperienced person (and I flash recoveries and custom ROMs many times a week to my Samsung phones) could completely understand what they do. There seem to be other problems as well such as dead links to installation files or executables that are problematic in Win8/10 environments (giving errors like 'install .NET 2.0 framework').
So here's what I currently understand. I get that I first need to root the A500 and that many rooting methods also unlock the bootloader (those are not familiar to me) and add an older recovery which then can be used to flash a newer recovery (with which I can flash ROM and GAPPS zips). I'vet got my ACER CPUID (used ES Explorer app to find it) and my SBK. I've copied zips and MD5s of OmniROM 5.1.1 V11 ROM, its GAPPS and TWRP based recovery REV2.0 beta4 to a MicroSD card which is inside the A500. I've got USB Debugging (and unknown sources) on.
Could someone please give me a good step-by-step guide with working links which describes how can I get from the current state of A500 (stock 4.0.3, unrooted, factory reset made) to the point where I can start flashing zips of recoveries and ROMs (which I know how to do)? I realize that this is an older device but for someone who has spent many hours within the last few days browsing XDA, Tegraforums and other places for information, there seem to be many A500-owners who still in 2015 are doing their first rooting and flashing experiments.
Please help!
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
rampart51 said:
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
Click to expand...
Click to collapse
you folks are all TEGRA OWNERS right? You should definitely check there instead...
Sent from my SM-G900V using Tapatalk
You can follow this which i wrote in other forum:
For basic step, follow if you are coming from stock. Make sure you flash all as mentioned in below forum
http://forum.tegraowners.com/viewtopic.php?f=9&t=363
In that forum, step2,
you can use Touchrecovery mentioned there or from: http://forum.tegraowners.com/viewtopic.php?f=8&t=1490
Also, for latest ROM, use the rom from first post of this forum.
Make sure you have Root access on tab, as well as you check MD5 sum for all file you flush it on the source from where you flush it. Usually, you put your files on microSD so check MD5 sum on MicroSD file.. (if you don't know how to, google it)
Basically, it is boiling down to below steps:
1. you need to root your device.
2. go to your existing recovery and install TWRP recovery. (http://forum.tegraowners.com/viewtopic.php?f=8&t=1490)
3. Once you install, go back to new recovery
4. tap on Partition Format
5. Tap on Storage. (Screen has only one big button)
6. Select Data from left side.
7. Select f2fs from right side.
This will format all your existing data. You will lose everything that you have.
8. Do same for Cache.
9. Reboot back in recovery to make sure that both partitions are formatted as intended.
10. Go back to main menu in recovery
11. Install ROM
12. Install GAAP.
13. Reboot.
14. Thank Thor.
Click to expand...
Click to collapse
I managed to get a Vista laptop so I've been able to get pass the compatibility issues with my Win10 PCs. However, I'm still a little unsure what to do. Could someone please clarify this for me? Can I use the quoted guide to get my A500 4.0.3 unrooted tablet rooted and with a recovery I can use to flash TouchRecovery, OmniROM and GAPPS zips? More specifically, does Step 1 work with 4.0.3 unrooted:
I wanted to write a consolidated tutorial for people on the latest/unrooted 3.2.1 OTA and how to flash it to rooted Jelly Bean ROM. If you follow step 1, it actually installs an old version of Touch Recovery for you, so you do not need to bother with Acer Recovery Installer. All links are derived from the FAQ stickied thread.
1. First you need to obtain root. Follow this guide to install a rooted 3.2.1 image.
[tab=30]All data will be lost. The 10 step guide is included as a PDF in the download:
[tab=30] http://forum.xda-developers.com/showthread.php?t=1307539
[tab=30]Confirm you have the Superuser app installed once completed.
Click to expand...
Click to collapse
I also found this piece of information from XDA:
Its an old thread used to upgrade you to rooted 3.2.1 -
It can also be used to downgrade/rollback/reset partition table - from ICS BUT there's a slight difference in the steps you need to take to do that...and alot of folks have come to grief here - so for the downgrade -
after running the "test.cmd" which checks the right drivers are installed correctly - run dotnetdetector.exe - follow the instructions UNTIL
You see a window asking you to connect your usb cable and that the EUU will check you "image versions" If you are downgrading DO NOT connect your cable!!!
This will "force" the "cannot detect your Iconia" window and then give instructions to put your tab into "manual apx mode" - once you have done that you can connect your cable - enter your cpuid - then you'll see the green status bar and the "update" will begin - it should take no longer than 10 minutes -
Click to expand...
Click to collapse
So which is it? Do I follow the 3.2.1 OTA method as is or do I take into consideration the alternative step to downgrade? Or does the method even work for A500 4.0.3 unrooted?
Sorry if this is the wrong section, basically my S5 (SM G900F) is stuck on Android 5.0, there is no updates for it OTA or on kies, so I went to sammobile to download the marshmallow update searched in my countries carrier, (Lebanon) but it seems there is only the 4.4.2 version. So I don't know what to do, I'm kinda new to all this so excuse my ignorance on the matter.
What if I downloaded the UK firmware? Does it matter at all?
Shadz01 said:
Sorry if this is the wrong section, basically my S5 (SM G900F) is stuck on Android 5.0, there is no updates for it OTA or on kies, so I went to sammobile to download the marshmallow update searched in my countries carrier, (Lebanon) but it seems there is only the 4.4.2 version. So I don't know what to do, I'm kinda new to all this so excuse my ignorance on the matter.
What if I downloaded the UK firmware? Does it matter at all?
Click to expand...
Click to collapse
If you don't really care whether it's Touchwiz or not, maybe try flashing TWRP via Odin and flashing a Lineage 14.1 ROM? (I don't take responsibility if you brick your phone, please follow this guide if you're new and proceed with caution.
Guide: https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin
Download link for Odin: https://odindownload.com/download/Odin3_v3.12.3.zip
Download Link for TWRP (G900F / KLTE): https://eu.dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
Official Lineage 14.1 Build Downloads : https://download.lineageos.org/klte
Open Google Apps Link: http://opengapps.org/ (Choose: ARM > 7.1 > Pico)
The reason I choose LOS 14.1 is because it's very stable and Nougat based. LOS 15.1 is not ready as a reliable daily yet.
(I repeat, I do not take responsibility if you try this and end up bricking your device.)
@Shadz01 it doesn't matter at all what country it says. Just grab the latest 6.0.1 from here and flash away.
CoreyOS said:
If you don't really care whether it's Touchwiz or not, maybe try flashing TWRP via Odin and flashing a Lineage 14.1 ROM? (I don't take responsibility if you brick your phone, please follow this guide if you're new and proceed with caution.
Guide: https://www.theandroidsoul.com/how-to-install-twrp-recovery-using-odin
Download link for Odin: https://odindownload.com/download/Odin3_v3.12.3.zip
Download Link for TWRP (G900F / KLTE): https://eu.dl.twrp.me/klte/twrp-3.2.1-0-klte.img.tar.html
Official Lineage 14.1 Build Downloads : https://download.lineageos.org/klte
Open Google Apps Link: http://opengapps.org/ (Choose: ARM > 7.1 > Pico)
The reason I choose LOS 14.1 is because it's very stable and Nougat based. LOS 15.1 is not ready as a reliable daily yet.
(I repeat, I do not take responsibility if you try this and end up bricking your device.)
Click to expand...
Click to collapse
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
koragg97 said:
@Shadz01 it doesn't matter at all what country it says. Just grab the latest 6.0.1 from here and flash away.
Click to expand...
Click to collapse
I already downloaded it from this thread, it doesn't state which country/carrier https://forum.xda-developers.com/ga...m-official-android-6-0-1-marshmallow-t3319376
Can you check if it's the right one? Thank you.
Shadz01 said:
What if I downloaded the UK firmware? Does it matter at all?
Click to expand...
Click to collapse
Yes, it matters. But not much.
The phone will work but you may lose language and APN settings at least.
Have a look at this ROM.
It's for SM-G900F, it's the most recent ROM for this phone, it's "stock-based" ROM and it contains LEB CSC code you need.
I'd install it without modification (root=noroot) for the first time.
Read several leading posts in the thread to learn how to deal with all that stuff.
bbsc said:
Yes, it matters. But not much.
The phone will work but you may lose language and APN settings at least.
Have a look at this ROM.
It's for SM-G900F, it's the most recent ROM for this phone, it's "stock-based" ROM and it contains LEB CSC code you need.
I'd install it without modification (root=noroot) for the first time.
Read several leading posts in the thread to learn how to deal with all that stuff.
Click to expand...
Click to collapse
If I want the one without the modification, no root, I change the name of the file to "G900Fxxx_DevBase_v4.x_noroot.zip" or "G900FXXU1CRA2_DevBase_v4.6_noroot.zip" ?
I install it with Odin no need for TWRP right?
Shadz01 said:
If I want the one without the modification, no root, I change the name of the file to "G900Fxxx_DevBase_v4.x_noroot.zip" or "G900FXXU1CRA2_DevBase_v4.6_noroot.zip" ?
I install it with Odin no need for TWRP right?
Click to expand...
Click to collapse
There's a small file options.prop inside the zip with the ROM.
Pull it out, modify and put into the root of phone's memory (have a look at the manual).
There are 2 lines only which can be modified:
root=noroot
CSC=LEB
Use Notepad++ or Notepad2 or some other text editor which can handle linux LF, not only Windows CR LF.
The ROM is installed from TWRP.
You'll need to flash TWRP, bootloader and modem (from Odin), then install the ROM.
Shadz01 said:
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
Click to expand...
Click to collapse
I don't mean to sound patronising but it's just common sense to have Samsung drivers installed when using your computer to communicate with your device. (I did not thoroughly check through this guide but only linked it as I followed this before when I first began flashing custom firmware/ROMs to my devices myself.
Also, the google apps link is to get Google play functionality on Lineage OS as it does not come with any Google functionality whatsoever when installed standalone. This adds Google Play Store and Google Play Services to the ROM. You can install Yalp store from F-Droid if you do not wish to install Google apps but please note if you do decide to go without Google apps, you will not have contacts sync so you will have to export and import your contacts manually using a vcard file.
Apps that are dependent on SafetyNet and GPlay Services such as Snapchat also do not work without flashing the Google apps.
Also I only suggested Pico OpenGapps as it only comes with the bare minimum functionality to get Google Play Services running. It's up to you then what you install.
No, you do not need to root your device to flash anything via TWRP.
TWRP is used to flash root tools such as SuperSU or Magisk, it is the control panel to your hardware pretty much.
So...
Flashing TWRP:
1, Install Samsung Smart Switch or USB drivers (If smart switch doesn't work try these:
http://developer.samsung.com/common/download/check.do?actId=698)
2, Download Odin and the TWRP image for your device (Links in my OP)
3, Turn your phone off, hold Power + Home + Volume Down to enter Download Mode. (Follow instructions given on screen once download mode is active)
4, Plug your phone in via a reliable USB port and cable
5, Run ODIN as Admin and tick the AP box and choose the TWRP .tar file by clicking on AP.
6, Click Start at the bottom of ODIN and wait for the recovery to be flashed.
7, Now as your device reboots, hold Power + Home + Volume Up to enter your newly flashed TWRP recovery.
Optional ** If successful, make a backup of your original firmware using the backup section in case you need to get back to it in future.
Installing the ROM:
1, Within TWRP, go to Wipe > Advanced Wipe and tick "Cache", Data" and "System". (You will lose all app settings if you haven't backed up)
2, Go to Mount > Mount USB Storage and plug into PC in order to copy the rom, gapps and other files to your internal storage.
3, Unmount storage, go to "Install" from the main menu and select the ROM and flash it. (Use "add more zips" option to select gapps and others)
4, Once all has installed reboot and fingers crossed you'll see the Lineage boot animation :good:
Like I said yesterday, I take no responsibility, just trying to help out.
Hope you get good results.
It's not all bad if you device won't boot if something goes wrong, you can always just flash the original firmware via ODIN which is provided by Sammobile. (Been there, bricked that, fixed that etc etc)
Keep me posted!
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Shadz01 said:
Are you sure about the guide you linked for installing TWRP? Nowhere does it say to install "samsung driver" which I have seen to be a step in many other tutorials.
Also, in step 3, when the guide says to enable OEM unlock does it mean the enable USB debugging? Because I can't find any checkbox for it in the developer option.
What is this Google Apps link? Is it the same as LOS (the link you provided at first) ?
Do I need to root my device to flash LineageOs via TWRP ? Because it's a custom ROM.
I've heard lineageos drain the battery, or at least is worse than the Stock ROM, also it makes the camera horrible because of improper drivers.
Thank you.
Click to expand...
Click to collapse
Forgot to mention, also Enable OEM Unlock I've noticed is only present in more recent devices. If you do not have that option and you have thoroughly checked it does not exist, you should not have to worry about it. (Please don't take that ass 100% gospel. I just noticed my Samsung J3 has it (2016 mid) and my S5 does not (2014 Flag)... Up to you, just do some digging but I don't have taht option and I have never been FRP locked... (Only on my J3 )
CoreyOS said:
I don't mean to sound patronising but it's just common sense to have Samsung drivers installed when using your computer to communicate with your device. (I did not thoroughly check through this guide but only linked it as I followed this before when I first began flashing custom firmware/ROMs to my devices myself.
Also, the google apps link is to get Google play functionality on Lineage OS as it does not come with any Google functionality whatsoever when installed standalone. This adds Google Play Store and Google Play Services to the ROM. You can install Yalp store from F-Droid if you do not wish to install Google apps but please note if you do decide to go without Google apps, you will not have contacts sync so you will have to export and import your contacts manually using a vcard file.
Apps that are dependent on SafetyNet and GPlay Services such as Snapchat also do not work without flashing the Google apps.
Also I only suggested Pico OpenGapps as it only comes with the bare minimum functionality to get Google Play Services running. It's up to you then what you install.
No, you do not need to root your device to flash anything via TWRP.
TWRP is used to flash root tools such as SuperSU or Magisk, it is the control panel to your hardware pretty much.
So...
Flashing TWRP:
1, Install Samsung Smart Switch or USB drivers (If smart switch doesn't work try these:
http://developer.samsung.com/common/download/check.do?actId=698)
2, Download Odin and the TWRP image for your device (Links in my OP)
3, Turn your phone off, hold Power + Home + Volume Down to enter Download Mode. (Follow instructions given on screen once download mode is active)
4, Plug your phone in via a reliable USB port and cable
5, Run ODIN as Admin and tick the AP box and choose the TWRP .tar file by clicking on AP.
6, Click Start at the bottom of ODIN and wait for the recovery to be flashed.
7, Now as your device reboots, hold Power + Home + Volume Up to enter your newly flashed TWRP recovery.
Optional ** If successful, make a backup of your original firmware using the backup section in case you need to get back to it in future.
Installing the ROM:
1, Within TWRP, go to Wipe > Advanced Wipe and tick "Cache", Data" and "System". (You will lose all app settings if you haven't backed up)
2, Go to Mount > Mount USB Storage and plug into PC in order to copy the rom, gapps and other files to your internal storage.
3, Unmount storage, go to "Install" from the main menu and select the ROM and flash it. (Use "add more zips" option to select gapps and others)
4, Once all has installed reboot and fingers crossed you'll see the Lineage boot animation :good:
Like I said yesterday, I take no responsibility, just trying to help out.
Hope you get good results.
It's not all bad if you device won't boot if something goes wrong, you can always just flash the original firmware via ODIN which is provided by Sammobile. (Been there, bricked that, fixed that etc etc)
Keep me posted!
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Forgot to mention, also Enable OEM Unlock I've noticed is only present in more recent devices. If you do not have that option and you have thoroughly checked it does not exist, you should not have to worry about it. (Please don't take that ass 100% gospel. I just noticed my Samsung J3 has it (2016 mid) and my S5 does not (2014 Flag)... Up to you, just do some digging but I don't have taht option and I have never been FRP locked... (Only on my J3 )
Click to expand...
Click to collapse
Thanks so much for your help, I installed TWRP with no problem. Does a nandroid backup include pictures and videos? Have you ever experienced with LOS battery drainage or worse than the stock ROM?
Shadz01 said:
Thanks so much for your help, I installed TWRP with no problem. Does a nandroid backup include pictures and videos? Have you ever experienced with LOS battery drainage or worse than the stock ROM?
Click to expand...
Click to collapse
No it's usually better as there's less services running and it's official and stable (still a Nighlty) but personally I can't use TW it's awful and LOS sh*ts all over stock.
A great way of saving battery like I do is running LOS without GAPPS. Or install AICP and enable the performance mode toggle in quick settings.
If you would like a link to AICP let me know, it's built from Lineage and is very smooth and optimized. (Make sure to enable force scrolling cache in AICP extras app).
And no problem, it's my hobby and I also love helping when I can.
EDIT: Your personal files will not be lost as long as you do not wipe internal and external storage (MicroSD)
For future, if you get to the stage where you change your data and cache partitions to F2FS make sure you copy your files to PC... For some reason it wipes internal storage when you format the data partition.
CoreyOS said:
No it's usually better as there's less services running and it's official and stable (still a Nighlty) but personally I can't use TW it's awful and LOS sh*ts all over stock.
A great way of saving battery like I do is running LOS without GAPPS. Or install AICP and enable the performance mode toggle in quick settings.
If you would like a link to AICP let me know, it's built from Lineage and is very smooth and optimized. (Make sure to enable force scrolling cache in AICP extras app).
And no problem, it's my hobby and I also love helping when I can.
EDIT: Your personal files will not be lost as long as you do not wipe internal and external storage (MicroSD)
For future, if you get to the stage where you change your data and cache partitions to F2FS make sure you copy your files to PC... For some reason it wipes internal storage when you format the data partition.
Click to expand...
Click to collapse
I already flashed LOS, very smooth, I like it, but the battery sucks. I lose 1 % every one and a half minute when I use my phone. Is this AICP a ROM or some mode? I never tried updating my modem and bootloader, would that help the battery? Or maybe installing a kernel manager?
Shadz01 said:
I already flashed LOS, very smooth, I like it, but the battery sucks. I lose 1 % every one and a half minute when I use my phone. Is this AICP a ROM or some mode? I never tried updating my modem and bootloader, would that help the battery? Or maybe installing a kernel manager?
Click to expand...
Click to collapse
Yes it's another rom. It uses Lineage 14.1 as a base but has its own tweaks.
I find what you're saying to be very true too but I can put up with that. I just cannot tolerate anything other than stock AOSP Android.
Try Greenify, I use it to hibernate Facebook and a few other apps that suck the life out of my phone...
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?
Hi All
Looking for a best tutorial to follow and the right one for my phone really don't want to brick it, obviously :/. as there seems to be a few versions for the S7
I have the following: S7 android 8.0.0 SM-G930F not sure what else I need to know! I'm in the UK so I assume UK phones come with Exynos cpu's
and as far as I am aware android 8 is Oreo! but when they say Stock Rom I assume they mean the same as what came with the phone the original rom?
if so is there an alternative stable rom without the crap included or is it just as simple to delete every thing you don't want now it's rooted! and does that mean if I reset the phone its back to normal with all the crap included! or is there a way to keep it rooted even after reset! and should anything be disabled I.e prepare the phone before attempting to root like any kind of auto encryption that needs disabling and just one more question
if at anytime the rooting process hangs for a ridiculous amount of time when should I throw in the towel! and what are the chances of retrieving the phone back to original state! or does a dirty shutdown brick it?.
I started the root process but failed at first hurdle!, followed instructions install Odin3_v3.13.1 but when I connected the phone nothing showed up in Odin? though I will have another go just to confirm I followed it correctly, I'll update this when it's done.
this was the tutorial I followed:
Easy 4 Newbie [Root Guide]SM-G930F, G935F, G930FD, G935FD (Samsung Galaxy S7 Edge)
Warning ! Please note that the official TWRP for Nougat on Galaxy S7/ S7 Edge is not available yet but based on my experience the Marshmallow version is working on Nougat. By installing a custom recovery on your S7 and S7 Edge and rooting it...
forum.xda-developers.com
I know alot of questions I would really appreciate any help and clarification on the above.
many thanks
Regards
Daz
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Mohamedkam000 said:
Look pal, rooting the phone is just like being an adult, it means you will get rid of Samsung's "Child Care".
Yes, UK models use Exynos chip, but you have to be sure, look at your baseband version, if it is G930FXXX, then you are good.
ROMs are in two shapes:
Stock-based: These are just like the one you are using, or other Samsung phones does, like Samsung Experience, One UI, TouchWiz. Maybe MIUI and FlymeOS will come into account, as there are ROMs based on them + Samsung's.
AOSP: These are pure Android ROMs, with few modifications to the core, but keeping the UI as close to the source as possible, Google & OnePlus phones come with a near-to-pure operating systems.
Changing a ROM is not risky, as long as you follow the instructions, without any unaccounted improvising.
Before you install a ROM, read the working and bug list, to make sure you are installing something you have an idea of.
You need to install TWRP recovery (or any other one you like), and format data, in order to be able to travel among ROMs and/or root your device.
Formatting is only required because the phone is forcibly encrypted, and TWRP can not decrypt it, at least not for this device.
Rooting is simply about flashing a 5-MB file, Magisk, then rebooting to system, no need to wipe data.
No need to do any additional steps, unless you are trying to hide root from some apps and/or pass SafetyNet.
Click to expand...
Click to collapse
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
CitizenSmith said:
Hi Mohamedkam000
Thanks for replying. I'm not confused about why I want to root the phone. I'm just trying to understand the inner workings and the risks as I'm not as clued up with phone OS's as I am windows. I don't care about warrantees or hiding the the fact it's rooted I just want a clean rooted phone free of big brother well inside at least I know you will never completely keep them out but making it hard is a start lol.
Thank you very much for all the above especially on clarifying about the roms and the reason TWRP formats due to encryption nice one
My Baseband version slightly different though it's G930FXXU8ETI3 not sure if having a U instead of a third X makes any difference!
and I posted wrong tutorial I'm actually following this one below again not sure if that matters.
Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )
Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1...
forum.xda-developers.com
Again many thanks for clarifying that lot up very informative and much appreciated.
Kind regards
Daz
Click to expand...
Click to collapse
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Mohamedkam000 said:
It doesn't matter which version of Android you are using, root is the same.
However, on stock ROMs, it might sometimes get rough, as you may end up with Wi-Fi not working (happened to me Q1 2020).
If you really want to learn how Android OS works, then rooting the stock ROM is not your way.
Try AOSP ROMs, preferably start with Oreo ones, you can root in 3 common way, LineageOS SU Add-on, Magisk, Super SU.
But before you tickle your phone, you have to make a backup of your current device, of every partition, EFS is the most important partition, so make sure it is safe.
Baseband version doesn't matter a lot, unless you're paranoid with updates, it is sorted alphabetically, each string on its own.
The phone is more similar to a linux machine than to a Windows PC.
Edit: To root stock ROM, you have to flash dm verity, so you don't end up encrypted again.
Click to expand...
Click to collapse
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
mooms said:
The first thing to do is to flash (install) TWRP, it's a custom recovery (think of it as a mini OS that can boot before Android), that will be the base for any of your future tinkering.
Here is the thread, read the FP carefully: [Recovery][Exynos] Official TWRP for Galaxy S7 (herolte)
Once TWRP installed, you can do many things:
Install addons like Magisk. Magisk is the tool you use to obtain root. Forget SuperSU, its outdated, and don't works in modern versions of Android.
Install a custom ROM (this subforum is the perfect place to find them).
Backup & restore an image of your current ROM (very useful).
Click to expand...
Click to collapse
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
CitizenSmith said:
Thanks again for clearing quite a few things up I thought rooting stock rom would have been far safer way forward wow how wrong was I! but I guess I am just trying to find any kind simile to windows in any way but as you pointed out again it's more like Linux which again I've only played around with ubuntu and mint for a short period so again not to up on Linux lol.
It's funny I was just reading up on AOSP ROMs then got your message. I see they have a stable but not complete! Android 10 not that I would consider it need as I need a stable OS so Oreo is fine for me.
I have backed up phone using Smart Switch on the PC I assume that copy's every thing that's needed, I reset the phone in anticipation all be it prematurely but at least it restored all my data so if anything that was a good test of the back up at least .
I will have look at some AOSP ROMs and see what's involved there, I'll check out their tutorial hopefully it will include the whole process including root.
I gather by your comment using a AOSP ROM you don't need to use dm-verity or will that still be needed!.
Click to expand...
Click to collapse
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Mohamedkam000 said:
AOSP ROMs are pure, you can't say they are not complete. They are complete, and what OEMs do, like Samsung and Xiaomi is just a customization that you can do, too.
It is preferred that when you take a backup, take it with TWRP, just to ensure you backed up phone's partitions, along with "EFS".
The root procedure on Android 6+ is done by patching the Kernel (boot.img), so unless you take backup of that, you cannot keep root.
There are stable custom ROMs, custom ROMs are meant for custom adjustments, however the stability depends on your phone, and the way you use it, you can compare AOSP vs. Stock and see the difference.
AOSP ROMs doesn't need dm verity, well, at least not if the developer did not mention the encryption part.
Click to expand...
Click to collapse
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
CitizenSmith said:
Some of the roms I have looked at mention external touch buttons at bottom of phone do not work or something else in the phone I'm just reading their comments.
I understand about the stock & custom rom's now that's not my problem at least not at the moment as I am miles away from choosing a rom! as I can't even get out the starting gate!. I can not get TWRP on my phone as the only way I can see to get it on a unrooted! phone is to use Odin but as I said Odin doesn't work at least not for me it does not see my phone. I would love to take a back up using twrp but that won't happen until I find a way to get TWRP on a unrooted phone. what crazy paradox is this!. you can't root phone without twrp installed and twrp won't install on a unrooted phone!. that makes perfect sense.
Click to expand...
Click to collapse
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
CitizenSmith said:
Thanks Mooms for the input
I tried to follow your links tutorial which he gives three options only one is any good to me and that was installing twrp using Odin but I'm having issues at every turn!. I can't even get Odin to recognise my phone it just wont pick it up I have Samsung driver installed and I have reinstalled many times I found an article claim to have a workaround but that was BS just selling some other app I even change the driver as described on there page,
7 Tips to Fix Odin Not Detecting Phone
Are you using Odin flash tool to flash your Samsung phone but it is not recognized by Odin? Here are 7 tips to fix Odin not detecting phone.
www.imyfone.com
.
but that did nothing so reinstall normal driver again.
feels like it's just not meant to be :/
Thanks again.
Click to expand...
Click to collapse
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Mohamedkam000 said:
Does your phone allow MTP communication? I mean can you transfer files when the phone is turned on?
Does the phone show any notification about a usb connection?
If not, then you have probably a bad USB cable, at least, or you have a hardware issue that can go as deep as a burned charging port.
If yes, then either your USB cable is not as fast as the phone requires, or you haven't installed the Samsung USB Drivers on your PC.
Unfortunately, you cannot root your device without PC, at least not since Lollipop.
Click to expand...
Click to collapse
Hi
Yes I can transfer files.
Yes phone asks to allow or block file transfer and it ohone shows up in Devices and Drives list and I can access the phone directory and shows up as Samsung s7 icon.
I will try another USB lead but the one I'm using is new and wasn't cheap but still a possibility I have had leads that weren't suitable for other things I was trying so it is worth a try.
Thanks
mooms said:
Which version of Odin are you using ?
Use this version (latest): Odin v3.14.4
Which version of the Samsung USB drivers are you using ?
Use this version (latest): https://developer.samsung.com/mobile/android-usb-driver.html
Click to expand...
Click to collapse
When I downloaded Odin this was latest one Odin3_v3.13.1 though I have doubts that one version update will fix this issue as I did not see many if any people having my issue so they all used Odin and I believe theirs are fine even with older versions! but as I said Mohamedkam it's worth a try I will down load that version and give it a try.
As for the Samsung usb driver I believe that is where I got mine
SAMSUNG_USB_Driver_for_Mobile_Phones no version visible under properties on file version 1.7.23.0.
The USB connection seems to be fine I have uninstalled then re-download and reinstalled a couple of times.
I can transfer files no problem it shows up as Galaxy S7 Icon with card and phone drive inside.
I'll update shortly thank you.
Update:
I just went to try new Odin and whilst checking my phone have seen I have Offical TWRP app installed? I have no clue as to how that's got in there! as Odin did not show phone so I could select nothing!.
In the phone I open app and if i select backup existing recovery it opens and Select Folder tab and under that Selected Folder: /sdcard Filename: Recovery .img and at the bottom of screen Root access required.
I just hope it's installed correctly!. it is showing in playstore my apps as well just to confirm. if this is now installed what should I do next Now not sure what tutorial to start following.
I am just going to try the new odin and see if it picks up the phone back soon.
OK Seem that it now shows up in the new Odin. at least I think it has! in the log window I see this: <ID:0/004> Added!!
I didn't see that before.
Would be grateful if you could tell me how to proceed from here!
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
mooms said:
Correct, you don't need he latst version of Odin or the Samsung drivers, bit it was just to be sure.
You need to be in download mode, but before, you must have checked OEM unlock & USB debug in developer options (mandatory).
I've written a tutorial with images here (in French):
Samsung Galaxy S7 (edge) - Mangez un Oreo! [Topic Unique] - Page : 487 - Téléphone Android - Technologies Mobiles - FORUM HardWare.fr
Click to expand...
Click to collapse
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
CitizenSmith said:
As I said the older version did not show any kind of data what's so ever and the phone was in download mode. phone displayed "Downloading" which I believe it says that even if it's not doing anything! so a tutorial explained. I think it must have installed the Official TWRP app even though phone did not show up in Odin everything was blank however when I installed the new version of Odin like you suggested it then showed up as <ID:0/004> Added!!. so your suggestion work thanks for that and I did enable OEM unlock & USB debug I did long time ago.
I would check out your tutorial but unfortunately I don't speak French and translating instructions is too risky but thank you for the offer but I'll carry on look around still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
CitizenSmith said:
still undecided on what custom rom to go for as I said some comments point out small issues and the developers also state certain things are not working so that is making it hard to consider one if you know what I mean.
Again Thank you for your input very much appreciated.
Click to expand...
Click to collapse
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Mohamedkam000 said:
Take a note that, when you flash TWRP, you have to boot immediately to the recovery, so as to enforce its existence, cause I remember they phone has an original recovery backed up somewhere, and gets triggered when you reboot directly to system instead of the unofficial binary.
I advise you to watch guides on YouTube, it's more .. understandable.
Click to expand...
Click to collapse
Yer I read that but I've ended up with TWRP installed and did not do that process because I was unaware it installed until it showed up.
As I said I'll just keep looking for now I know I'll find one that works for me from start to finish.
and I've been checking youtube but wouldn't want to use any links their providing but it may help familurise myself with the whole process if i watch enough of them.
Thanks again for your help.
mooms said:
I recommend to go with ALEXNDR ROM: zero bugs, everything works perfectly (it's based on stock ROM).
[ROM][G930F/FD][ALEXNDR] * U8EUE1 * DevBase v7.4 * Encryption support [Jul-10]
Important notes for Developers / Chefs !!! This ROM is NOT based on any other custom ROM. My work contains many original ideas and innovations that I introduced as the first in the ROM development (see "Changelist" in post #2). Of course, it...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi Mooms
I will check that out many thanks. I wonder if you could help me here. I am in the middle of the rooting process but have hit a snag. again!
I have now installed TWRP successfully then no-verity-opt-encrypt-3.1 all went fine and I'm at point of flashing Magisk but have an issue when I swipe to flash is gives me a error in red saying "invalid zip file format !"
I downloaded it from github here.
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
I click on "code" tab and then "download zip" and I placed that in a download folder on my sd card when I select it I get the above error any ideas as to why I am getting this am I downloaded the correct file?
thanks for any assistance you could give.
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Waiting for someone to shed some light in to this matter. I tried all the possible procedure I found on google, but no luck.
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
If your still interested in rooting this device go to @Austcool post it worked for me.
custom-sm-t380-sm-t385-boot
Edit: 2022 I have tested it it fully works as of this year!!!. 😁 disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk. to flash it simply open up settings enable developer options and enable OEM...
forum.xda-developers.com
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
Its Defex use my boot.img it's related to Samsungs new Defex anti root privileges security feature you must build the kernel from source; I already built Defex disabled kernel Prerooted with magisk.
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Sure I'll pull them from my device on pie.
Austcool said:
Sure I'll pull them from my device on pie.
Click to expand...
Click to collapse
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Austcool said:
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Click to expand...
Click to collapse
Thank you so much!!!
And sorry it wasn't your build it was zfk110's build https://forum.xda-developers.com/t/...android-9-bloatware-free-twrp-backup.4243589/
Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I am piggy backing too because you are someone recently (last week) were messing with this thing too...
I was given a SM-T380 and am trying to make it "useful"
So far I have had fine luck with both oreo and pie (using the build you mentioned T380DXS4CUD3 via twrp restore... and it is fine, but seems slower than I recalled 8.1 being...
Anyway, I have been flashing the v19.0 of magisk (and a v7.1 of magisk manager) and then flashed v21.4 (and v8.x of manager).
Anyway, if you install a newer magisk manager it will show the device as unrooted (N/A) but updating further seems like I would need to extract the boot.img from the twrp backup (which is above my head...) and patch it with newer magisk...
I am not sure that it's needed for what I will be using the tablet for.. but I haven't had luck with safetynet (using magiskhide props) so I am looking into other methods.
Anyway, I'm not sure if I sould go back to oreo 8.1 or not just because pie 9 seems sluggish in comparison..
Anyway, I am going to tinker with it in my spare time over the next few days, so if you want to connect about anything particular I am around.
-g
cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I root mine by just loading pie.tar from @Austcool post on odin. We have the same build no.