Database Users

[Q] Best procedure for flashing Optimized CM12.1 on to the UK GT-I9505 (JFLTEXX)?

I successfully flashed CM11 on to my LG G Pad 8.3 without issue so I've done this before (but most of the downloads had Batch files to automate things) but want to still be sure of the procedure.
My I9505 was recently upgraded OTA to Android 5.0.1 along with Samsung's TouchWiz. Hopefully this won't complicate matters.
Is this the best/recommended procedure? -
Root: What's the best/recommended method to Root my S4?
Backup Stock Recovery: Using Flashify on Google Play.
Install Recovery: Is TWRP Recovery v2.8.7.0 the best Recovery to use?
The Optimized CM12.1 thread recommends TWRP 2.8.7.0 but the download doesn't contain a batch file to run?
Reboot to TWRP --> Backup my existing ROM image then choose the Wipe option
Install the Optimized CM12.1 ROM then GAPPS from SD Card
Related questions about the Optimized CM12.1 ROM and GAPPS please:
Wouldn't a regular CM12.1 Nightly for the I9505 be better than the Optimized CM12.1 ROM? The Optimized CM12.1 ROM looks to be older (2015-06-16), or am I splitting hairs over a few days? Thanks
The Optimized CM12.1 thread offers a link to download GAPPS for Lolilpop 5.1. Is this better to use than the one in the GAPPS for Lollipop 5.1 here (ARM download): http://wiki.cyanogenmod.org/w/Google_Apps
Thanks a lot in advance for your help.

Is the TWRP Manager on Google Play the best/recommended way to install TWRP 2.8.7.0? -
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager
Thanks again.

Regarding your steps...
1, 2: Cyanogenmod is pre-rooted, and the stock recovery images are readily available, thus these steps waste time.
3. Yes.
4. Yes. You'll use Odin to flash the recovery, thus no batch file.
5, 6: Yes.
As to your other questions...
1. You need to decide which you want more. Is having a more current build more important than the optimizations? Regardless of the final choice both install in essentially the same fashion.
2. The GApps in the thread is more up-to-date than the official download.
Finally, TWRP Manager stopped working properly some time ago and really isn't necessary. Download the image from the Optimized CM12.1 thread and install it using Odin.

Strephon Alkhalikoi said:
1, 2: Cyanogenmod is pre-rooted
Click to expand...
Click to collapse
Firstly thanks for the detailed reply.
I remember that from installing CM on my tablet but presumably you still need to Root the S4 to be able to install CM?
Strephon Alkhalikoi said:
4. Yes. You'll use Odin to flash the recovery, thus no batch file.
Click to expand...
Click to collapse
A few more questions please:
1. So when you run Odin it will ask for the location of the TWRP Recovery v2.8.7.0 folder?
2. Is this the best place to get Odin? - http://odindownload.com/
3. That link says I need "ADB & FASTBOOT TOOLS", where do I get these for the S4?
Strephon Alkhalikoi said:
2. The GApps in the thread is more up-to-date than the official download.
Click to expand...
Click to collapse
Oh great thanks. I noticed it was a smaller download. Is there much missing from it over the official one?
Thanks again Strephon.

1, 2: No. You only need to flash the recovery through Odin to be able to install Cyanogenmod.
2. I believe the apps that all can be downloaded from the Play Store are missing, which is a good thing.
4: You need to input the location of TWRP on your hard drive. Search on XDA for the most current version of Odin (3.10.6) and ignore that site's comment about ADB & Fastboot Tools. Simply download Samsung's drivers off their website and install them. As an alternative, you can install Kies, but make sure Kies isn't running when you run Odin.

Strephon Alkhalikoi said:
4: You need to input the location of TWRP on your hard drive. Search on XDA for the most current version of Odin (3.10.6) and ignore that site's comment about ADB & Fastboot Tools. Simply download Samsung's drivers off their website and install them. As an alternative, you can install Kies, but make sure Kies isn't running when you run Odin.
Click to expand...
Click to collapse
Great. Thanks for the further help. I'm nearly there, just a few more questions please:
Do I need to enable USB Debugging?
Running Odin and it's unclear what to do next? I presume these instructions under "Odin Install Method (No Root Required)" are correct? - https://twrp.me/devices/samsunggalaxys4internationalqualcomm.html
Those instructions say to press the PDA button, there is no PDA button. Do I press the AP button instead?
In Odin options is it safe to leave "F. Reset Time ticked"? It looks like it is.
The TWRP 2.8.7.0 in the Optimized CM12.1 thread only offers a ZIP file and the link here only offers an IMG file: https://dl.twrp.me/jfltexx/. But it looks like Odin needs a TAR file. Any ideas?
I presume this (Micro) GAPPS is as good to install as the GAPPS link in the Optimized CM12.1 thread (it's newer, just want to be sure it's compatible)? - http://opengapps.org/
Finally, is it a good idea/recommended to convert to F2FS?
Googling and it's unclear if I want "F. Reset Time" ticked or I should be converting to "F2FS", so I thought I should be sure first. Great I already have Kies installed.
Thanks again. I'm pretty close to installing CM12.1 now.

It won't hurt, but in download mode it shouldn't be needed.
Yes.
The instructions assumed an older version of Odin. Press the AP button.
If Odin fires up with it enabled by default, I'd leave it as is.
Grab the 2.8.7.0 TAR from https://dl.twrp.me/jfltexx/ and install it through Odin. Afterward, you can change over to the F2FS-compatible version using the upgrade instructions given on the twrp.me install page.
It should be compatible, but you may have better luck using the version in the thread.
F2FS is totally optional. I personally don't use it.

Thanks for the quick reply again. There is no 2.8.7.0 TAR file in that link, just a 2.8.6.0 TAR file .
* I presume I should install 2.8.6.0 TAR then install the 2.8.7.0 IMG file on top from inside TWRP?
* OR better yet install 2.8.6.0 TAR using Odin then install 2.8.7.0-F2FS ZIP from inside the TWRP 2.8.6.0 Recovery itself? I presume I use the same Install option I do to install CM2.1 itself?

I didn't look carefully at the page. Sorry. But yes, you can grab the 2.8.6.0.tar, install it, then install either of the 2.8.7.0 images afterward in TWRP.

Thanks Strephon Alkhalikoi. I finally got around to doing this last night and it went without a hitch. I got a pit error using Odin but a quick Google said to plug the USB cable direct into the PC.

Flashing on 935F

Hi all.
I have the 935F International on it's way to me, delivering in the next day or so
By all accounts the 935F is already unlocked. To prepare, I have already downloaded Odin 3.11.1, CF's root file, TWRP twrp-3.0.2-2-hero2lte tar, and a custom ROM and bootloader/modem files.
I'm not a noob to flashing, just newish to Samsung.
What is the best way to start? Boot into stock, enable bootloader unlock on developer options, run Odin and flash TWRP, then CF's root file? Also, I want to run unencrypted - format data using advanced wipe 'yes' method?
The ROM states it sets root on installation. Do I then need to flash CF's root file?
Further, how are bootloader/modem tar files flashed? Is it as simple as selecting BL for bootloader, although I don't see anything for the modem??
Finally, what is the actual order of all this? I'm thinking: TWRP first, Format internal data second, CF root third, ROM flash from TWRP fourth, reboot to download mode from TWRP and then flash modem/bootloader last. Then reboot all together to set the phone up?
Thanks and any help is appreciated

1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM

dynospectrum said:
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
Click to expand...
Click to collapse
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:

If you're not new to rooting and custom roms, pretty much all you need is to unlock OEM in Dev Options in Settings, Restart the device and hold Vol Down+Home+Power to get into Download Mode and press Up at the blue screen. Plug in your USB to your phone and run the tool on your PC.
Once Rooted, its business as usual. You don't need a guide to install TWRP, just install the Flashify app and let it do it for you, and then have no-verity-opt-encrypt.zip handy to flash. I know no-verity-opt-encrypt.zip is essential if you flash TWRP through ODIN, but not 100% sure if you should if you flashed TWRP through Flashify, I always flash no-verity-opt-encrypt.zip regardless so I unno.
Also if you find yourself in a semi-bricked situation where you can't figure out your problem, as long as you have Download Mode, you'll always have a way to get back to a working device. Samsung Smart Switch for Windows has an Emergency Mode that will revert your device back to Factory Conditions.

peteri8706 said:
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
Click to expand...
Click to collapse
I've been doing things this way since day 1 with no problems. My advice would be to do it the same way. I can assure you a solid install ;]
Yes, firmware is bootloader & modem. Great thread for this is here http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065

Starting the root, recovery and custom ROM procedure from KitKat (D80220d-HKG-XX)

I've read pretty much every source I can find on getting a custom ROM up on my LG G2, which I haven't even rooted in the past 2 and a half years. My warranty ran out a while back and I'm getting a bit bored with stock now, and I want to start flashing, but the last time I did this was with my old HTC Desire HD.
As you can see I'm on 20d on my LG G2. It's a Hong Kong version for some reason, lol. What I considered doing was the following: update to the latest Lollipop official ROM using the LG Flash Tool (it gives me an available update to 30d); root using the rooting app, install a recovery with AutoRec Lollipop, flash a thermal recovery from the installed recovery (very scared of my phone overheating, I'm even considering putting it on a large, fast-running fan while doing anything, read too much about the phone overheating and making the screen yellow); back up my phone's IMEI data; use the recovery to install a brand new (I'm hoping a Marshmallow) ROM. I also understood that I need to flash a bootstack to change my bootloader to a KitKat, because it can be "fooled" using the BUMP thing. Is that correct? Do I even have to update my phone to Lollipop in this case? Also, how likely is it to overheat while doing all of these procedures?
Thanks in advance!

Sorry for the necroing my old thread, but I have yet to do anything with my phone. I am also still on KK. I saw that I can start rooting and install TWRP from it straight away. After that I need to flash a bootstack, right? How likely is it that I can brick myself? By that I mean what could get mixed up to get a brick while flashing. Also, has anyone had overheating issues while doing root, recovery installation and flashing things (newer TWRP, bootstacks, new ROM)?

Hi, i can understand your situation as i was in same till today, g2 with stock kitkat.
i finally installed cm13 after rooting it and the phone feels fresh.
you have understood most things right and ready now.
you dont need to upgrade to lollipop if youdont want to, you can start from kitkat itself.
few things i can tell you to begin here,
Root your G2,
for kitkat i found few good methods. Either do it via ioRoot using pc. or you can use towelroot or kingoroot apps to do it from phone itself. I used kingoroot since i didnt have a system with me. You can find these apps by searching at google, jst tyoe kingoroot. At first i was skeptical but it worked nice.
after root, you download autorec app, this is to install a custom recovery(twrp) for kitkat. you just have to install the app and run it and press install recovery/twrp and it'll do the rest.
after you have twrp installed, you need to upgrade it to latest version. For that download blastgator's twrp for your model and flash it through your recovery.
oh and dont forget to learn, how to enter into recovery yourself, since each G2 model has different method.
once you have these things you can start flahing roms. Most of the instructions on how to flash certain rom with what bootloader and bootstack etc. is written in its own thread, so you can learn that from that rom's thread that you will flash.
but basically, you need kk bootloader and lp bootstack for cm13 and above. usually both these things come in one zip. (if not you check for hybrid bootstacks)
Just make sure you are downloading things For your Model, if you try to flash different models stuff into yours, itll brick.
The autorec app, blastgator's twrp and ioroot can be found in a sticky thread in G2 general section, along with many other files and guides in that thread, theres complete index in that thread of all thing for all g2 models .
here : http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178
also usually the phone doesnt heat up while flashing, just make sure your battery is more than 80% before you start and itll be ok. Even if it does a little, after a custom rom itll be fixed. I suggest you try cm13 for starters as your first custom rom.
hope this helps you :good:
Good Luck ::highfive:

Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...

hitmancho said:
Thank you very much, appreciate the vote of confidence, lol.
I've actually considered installing Resurrection Remix Marshmallow. In the thread they point to the hybrid bootstack I need to install. I am on a D802 phone, so I'll be downloading that boostack. Anything I should really know before flashing that particular stack, except that I need to run the latest recovery from blastagator? Can I boot back into my old stock KK installation before putting the new ROM and Gapps on my phone and wiping + flashing, or will the phone not be able to boot that old firmware with the new bootstack? Theoretically, can the phone still get bricked even if I'm using the latest recovery + the proper bootstack? I've read that the CM13 devs don't recommend flashing bootstacks but instead using the kdz flashing method to flash the latest Lollipop release...
Click to expand...
Click to collapse
to upgrade from kitkat you need lp or hybrid bootstacks. they have images (. img files) that are needed for your phone to function properly., like aboot, modem, radios etc. Hybrid bootstack contains aboot from kk and everyhing else from Lp. So when youll flash a bootstack, youll need to wipe everything, except internal storage(or external if you have one) , before you can flash it. that wipe will include, cache, dalvik cache, system, data. so basically all the old system stuff will be gone before you can flash this bootstack. i hope after reading that youll know that you cant access your old kk installation since itll be wiped, therell be nothing to boot to. if youll try, it will give you errors on lg logo.
understand it like this, to install new 21 inches tyres to your car, you need to upgrade the rims to hold a 21 inch tyre right? what will happen if you just put the 21' tyres on old 15' rim or old 15' tyres on new 21' rims?
the cm 13 devs dont recommend you to flash bootstacks because most of the models took the official lollipop update, which put everything in their phone to lolipop level. since there is no official marshmallow(MM) bootstack for our phone (because no official update), everyone developed ways to utilize lollipop bootstack to function on a custom MM Rom. Since most models are already on lollipop, theres no need to flash lollipop bootstack while flashing custom rom. That step is mostly for those who are still on stock or custom kitkat based rom. So they say to get official lollipop through kdz method, instead of flashing Lp bootstack before gettig their rom. But remember if a rom developer asks to install a bootstack for their rom, you should consider it if you dont have much knowledge about it, cause if you dont follow instructions, you can soft brick, in that case youll need hybrid bootstack.
see if you are using everyhing proper for your phone then your phone wont brick. only thing that can go wrong with that condition is your execution, your steps. As long as you dont make a mistake in these steps everything will go fine.
ill explain it what you should do.
1. first root your phone.
2. when done rooting, install "root checker" from google play. itll confirm if you have root or not.
3.Then you come back here and find autorec app from the link i gave you in my previous reply. download that, install the autorec app. and follow on screen instructions and itll install twrp recovery for you.
4. then come back here again, and find blastgator's twrp, from the same link in previous post. itll be the one whih says "twrp with f2fs". download it and remember where you put it.
5. turn off phone, boot into recovery (i hope you've learned by now how to get into recovery of your g2 model). Now youll be in recovery, hit install button there and find where you put that file, flash it, then reboot recovery, youll have new recovery after that. then you reboot into system.
now upto this point, you can play along in your kk, have fun with features, say last goodbyes and all lol. Because everything stock kk related will be gone, past this point, including all the apps you have installed.
[IMPORTANT] : after rooting and installing recovery, get bootstack zip, rom zip and gapps zip files downloaded and placed together in a folder on your phone, before you start with flashing bootstack. Because you wont be able to boot back into system after flashing just bootstack.
now you prepare for MM, boot into recovery, now since you are in kk, you need to install LP bootstack, and for that you need to wipe everything using your recovery's wipe feature.
6. in recovery, hit wipe, hit advanced, select cache, dalvik cache, system, data. [ Dont select internal storage otherwise all flashing files will be gone and youll be left with a brick.] and wipe.
7. Now hit the back button to go back to main recovery screen once wiping is finished. hit install, flash the bootstack zip.
8. now your phone has new bootloader but its still empty, like you got a body but no soul . so hit back button, hit install and flash the rom zip you downloaded.
9. now flash gApps same way.
10. once its done, just hit reboot system. no other steps needed.
11. be patient, first boot takes longer than normal boot.
12.enjoy MM :highfive:
you probably know these steps from all the reading but its for your reference, so you dont screw up at all and be safe from bricking.
you can get google apps from opengapps website. you need to get ARM-> 6.0 -> (your prefered ones) pico/nano/micro/etc.. pico has the least amount of gapps, all important ones are there in pico, then extra will increase as you go up from pico to stock. stock has all the gapps. size will also increase as you go up. so choose as you prefer.
now once you have a cm13 /MM based rom, you wont need to flash bootstacks for other roms from next time unless the developer instructs to do so.
good luck

@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent

andrew2432 said:
@MarshisnotMellow
Does the cwm mm come pre rooted? Or unrooted ready from whatever idiocy I'm ready for?
1.stock
2.root
3.autorec twrp
4.upgrade to blastagators 3.0.2-1> or a different version I'm missing? This one says blastas twrp bump
5.put cwm rom, bootloader, gapps <where to get gapps zip?> onto internal memory somewhere familiar to me
5.wipe all but internal memory
6.flash bootloader
7.flash rom
8.flash gapps
9.???
10.profit
Check my steps teacher? I'm gonna start it anyway when my phone hits 80+ percent
Click to expand...
Click to collapse
cwm is clockworkmod, its a custom recovery. i think you meant CM 13, mm rom.
yes, the Cyanogenmod team have placed root access into the rom, so once youll be finished wih installing cm 13 rom, you can just go to settings, Tap build number repeatedly until a message will show "congrats you are a developer now". that'll open developer options in main setting screen Go into that and youll see root access. turn it on. youll have root.
you can check in root checker app to confirm root access for confirmation. you wont need super su app in any of these roms anymore.
your steps :
stock
1. root
2.autorec (for installing twrp on your phone) for kitkat its on forums, for lollipop its in google play. just get the one for your model, search for autorec in google play.
- blastgator's twrp requires you to have any version of twrp beforehand in order to install his version.
3. download and save blastgator's latest twrp, when youll go to download his twrp, itll be written there which one's is the latest version, just download that one and flash it through recovery.
4. Yes place all files in your phone, you can get gapps from opengapps.org/
select arm- 6.0- whatever size you like(, pico is lightest contains all essential gapps, stock contains every gapps)
5. wipe yes.
6. flash bootstack
7. flash rom
8. flash gapps
9. once gapps done, just hit reboot system.
10. enjoy
yes go for it when you have more than 80% battery, this is to ensure that all flashing steps go through without any issue, you dont want your phone to run out of juice while flashing rom do you that could cause soft bricks. so always keep battery more before flashing.
[IMPORTANT] : remember to read instructions of the rom you're installing and adjust the steps as instructed in there.
Goodluck :highfive:

Awesome, I forgot to.flash gapps prior to something I just did, not sure if it will cause increased global warming or thermonuclear war...update soon
@MarshisnotMellow
Gapps installed!! No Internet connection on the d800 and something sinister has happened to my unlocked WiFi Hotspot so I'll have to check for play store capabilities later!! Thanks for the help!!

I decided to go with the latest 29.10.2016 nightly of CM13 for my first run on this phone. Everything went through, no one died, lol. I'm going to start installing and restoring stuff now, get Xposed on, like I have on my TF701T tablet and trick out my phone's appearance. Just a note - after you install new bootstacks your phone's MAC address will change, so if you have a WiFi network with a MAC filter you might want to add your new address.

[Guide] Rooting G800F on Marshmallow 6.0.1 + getting Xposed framework

UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.

weird enough all those files where already on my pc. i just wanted to know if it would work

it says no root

Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?

kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work

I also have 6.0.1 Germany DBT but this didn't root my s5 mini

Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk

Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.

Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.

kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.

Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me

Does this root trigger the knox counter?

Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works

i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you

Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.

Can someone help me? I did it like in the tutorial but it does not work. Thanks all

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?

Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.

thanks for answer. Now it work with Version 2.8.0

Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.

Updating Android on SM-T560

I got a brand new Samsung Tab E 9.6" (SM-T560). Shame on me, I didn't notice before it comes with Android 4.4.4
As many apps require newer OS, I'm wondering if I can upgrade it to Android 6.0.
Plase note:
1. I'm not an expert, so please explain me as easy as possible how to do it, if it can be done;
2. please tell me, in case,if it's 100% legal and/or if it can void warrant.
Thank you.

Samsung Tab E
Check again --- Just picked up the same thing this week at Walmart for $129.00 + $25 Google Play credits - it came with 7.1.1. - Take it back sounds like you got some real old stock..

They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.

Hello,
I'm searching forsuch an update, too. But It seems, that it was only released for USA and CA. But I'm from Germany. @xSLAYERx do you have a link to the ROM?

xSLAYERx said:
They do come with Android 4.4, however if you go to Samsungs web page you can find a crispy 7.1.1 image you can flash with Odin. Then if you wish you can unlock bootloader and flash a custom recovery like CWM or TWRP and then chainfires systemless root. Cheers! Upgrading to just 7.1.1 with Odin will not void your warranty, anything else that involves unlocking the bootloader will and is will trip samsungs knox security feature. If warranty is important only flash the 7.1.1 image using Odin.
Click to expand...
Click to collapse
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!

hurkagyurka123 said:
heya, could you please share a link of this 7.1.1 with me? or the image itself, I can't find it anywhere and I'm stuck with 4.4.4
thank you!
Click to expand...
Click to collapse
Hi, I was with the same problem, and I posted here in XDA, I'm from Brazil, i have the model SM-T560, and now i'm using nougt, from Lineageos 14.1, and this was only possible, because someone from Xda, gave me the following link:
http://www.gearappsnap.com/2018/03/14/how-to-install-android-nougat-on-the-galaxy-tab-e-sm-t561/
The rom is of the SM-T561 model, but also works on the SM-T560, read everything before doing anything. When installing TWRP, you can install the version of the SM-t560, which will not make any difference.
One more thing, I advise you to see some YouTube tutorials how to install TWRP. Just in case.

Thank You for your help!

hurkagyurka123 said:
Thank You for your help!
Click to expand...
Click to collapse
For nothing, follow step by step that will work perfectly. Except this will end your warranty, but it's the only way to install an update. If you need any help, just talk.

gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.

Um, did you follow step by step?
I followed what was written, and for me it worked normal, The boot.img file is to fit just the memory of the table because it had some problem with the rom, without installing it, has tablet that got locked in infinite loop. And the links were working normal for me.
Links that i download:
ROM: https://drive.google.com/file/d/1D0wrGM4XyZMo-t3ll4trvJ93Pl1KEZ1V/view
Boot.img: https://drive.google.com/file/d/1bqGmu4NTlEeKdsFPGjIY9lnPqujjazr4/view
softkeys: https://drive.google.com/file/d/1ddSB28g1xTd0J7sl8V6QmlPZA1aX77ot/view
Gaps: https://opengapps.org/
First the TWRP is installed, with the battery above 70%, then restarts the tablet.
Within the TWRP:
1) Wibe-> advanced wibe-> selects almost anything but not microSD and OTC. and Wibe.
2) Back to the home page-> Install-> select the external storage (the files must be saved on the SD card).
3) The first file to be installed is the rom.
4) Once installed, go back to the files and at the bottom of the page you will click install image and install boot.img.
5) After Boot.img is installed, switch back to Install Zip, and Install the Softkeys.
6) After installing the softkeys go back and install the Gaps. (I used the ARM-7.1-Pico) and restart the tablet.
In my case I did not install superSU. That's what I did. This rom has some flaws but better than Kitkat, that's what I think.

thE_29 said:
gearappsnap site is not really good made.. The download links behind text which look like a normal one and also that it says, flash boot.img only when the memory is wrong..
Well, CM14.1 did not work for me.. I had to flash boot.img before EVERYTHING else, then rebooted again to TWRP and THEN install cm14.1.
Click to expand...
Click to collapse
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560

63or63 said:
HEY!
download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow steps.
1-install TWRP 3.0.2-1 via odin
2- copy ALL files of .zip in one folder in storage (mem stick)
3- power off and then power on IN TWRP (vol + + home + power button)
4- make full wipes except externar storage
5- install zip (first choice lineage -14, then choice open gapps, next choice key.zip)
6- install img (choice boot.img)
7- WIPE (Dalvik, cache)
enjoy android 7.1 in your tab e T560
Click to expand...
Click to collapse
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.

marcelo010 said:
In reality you have to install boot.img and softkeys before, the reason is because they are modified for the T56X, otherwise install themselves after the gaps will give error when to use. At least it is what was written on the site, and so far I have been using no defect at all.
Click to expand...
Click to collapse
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.

63or63 said:
I do not think that is effective. if you come from 4.4.4 and install it before the lineage ROM (BASE 7.1 for example) it will be erased again because with the new base everything is overwritten.
Click to expand...
Click to collapse
Well that didnt work for me.. Was coming from Stock 4.4 ROM. Flashed the CM14.1 AND softkeys, but NOT the boot.img, because you cannot flash zip and img files at the same time. Then I booted it and it crashed 10-60secs after it booted. Sometimes it had a boot loop.
Then I tried CM 13 which worked fine and in a german board, someone wrote (based on the gearappsnap site) that the boot.img has to be the first thing to flash and even reboot into twrp again and then flash CM14.1 + softkeys + gapps.

If you could install it, that's what matters, in my case it worked the way it was on the site, there are some bug's, but it's a lot better than the stock rom, and I was already using a custom rom on the T560 before installing this LineageOS 14.1,and it was this link:
https://forum.xda-developers.com/galaxy-tab-e/development/rom-lightning-t3716039

Szia!
did the upgrade work for You For galaxy tab e?

Done this and it worked but.........
The tablet is really slow, not netflix compatible with this version, and so on....
I think I just might downgrade again

After I have tried step 3, it didnt open in twrp mode. My tab stucks in black screen with "Samsung galaxt tab e " text in background.Please let me know how to proceed.

[QUOTE = "63or63, Post: 78613279, Mitglied: 4438103"]
HI THERE!
Download this: https://mega.nz/#!yEpjCITA!9EA101hYDOajDwmBHKxSZhv3QkV-RI61MkLn0JYNRZY
unzip and install and follow the steps.
1-install TWRP 3.0.2-1 through odin
2- Copy ALL .zip files to a folder in memory (mem stick).
3- turn off and then turn on IN TWRP (vol + + home + power button)
4- Make full towels except for external storage
5- install zip (first choice line -14, then select open gaps, next choice key.zip)
6- install img (choose boot.img)
7- WIPE (Dalvik, Cache)
enjoy Android 7.1 in your Tab e T560
[/ZITAT]
1000 tanks BR
.

1000 x danke es hat funktioniert
Translation: 1000 x thank you it worked