Boot into TWRP after updating to version 3.1.1 SM-T210 - Galaxy Tab 3 Q&A, Help & Troubleshooting

Hi Everyone,
I have a Galaxy Tab 3 (SM-T210 / lt02ltespr) which I am ultimately trying to get Zoom running on.
I have been trying to install LineageOS version 16 which won't install as version 3.0 of TWRP is too old. I have tried various ways of updating TWRP to version 3.1.1 none of which have allowed me to load into TWRP to install LineageOS (holding Power + Home + Volume Up). I've tried installing through the TWRP app and also installing it via TWRP 3.0 to the recovery partition in boot mode but in both cases I've not managed to get back into TWRP after a power off and holding Power + Home + Volume Up. I have tried Using Odin (both Version 3.04 and version 3.14 to install the latest version of TWRP for the device downloaded from their website but Odin crashes during the MD5 check so that route has never been successful for me.
If there is another way of installing LineageOS from within the main os after updating TWRP that would be amazing or some way of getting the TWRP file I have on my PC not to crash either version of Odin during the MD5 check that would also be great.
Thanks for your help.

Related

[Q] CWM recovery bootloop and can't get out

The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!
re: boot loop/recovery/rom manager
Jakman85 said:
The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!
Click to expand...
Click to collapse
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
Odin flash the cf-autoroot first.
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Once you are done doing the above you will no longer have bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Also philz touch recovery is not fully compatible with these newer firmwares and roms.
Good luck!
Misterjunky said:
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Odin flash the cf-autoroot first.
Once you are done you will no longer have any bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Good luck!
Click to expand...
Click to collapse
Here is the problem: I cannot get into download mode. I have held volume up+home+power and any combination of buttons and it just keeps trying to boot into a broken recovery. I have also plugged it into my computer and it doesnt communicate to it at all (makes sense, since it never boots into anything). I need to be able to reset my bootloader or force the bootloader into download mode.
Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.
PanchoPlanet said:
Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.
Click to expand...
Click to collapse
I have been trying that all evening! I have been looking up JTAG services and JIGs. I read your comment and said "It can't hurt to give it another go"... and BAM!!! Download Mode! After the 50th time!!! WOOT! Thanks guys!
This is what the Android community is all about.
Your welcome.
Pp.

Help: Can#t install gapps with twrp 2.8.6.0.

##Hi i'm using an Galaxy Tab 3 Wifi! I Installed CM 12.1 via TWRP 2.8.6.0 like witten in developmet section in the forum. -> Houdini -->gapps will not work --> error: your recovery is missing the xz binary.
After that i realized that my trwp is not the latest and so I installed (by odin) the latest twrp. But it's not working (Pressing power+Volume up has no results) then i installd the old twrp 2860 and there I am.
What am I doing wrong. Why is the latest twrp not working?
elramon said:
##Hi i'm using an Galaxy Tab 3 Wifi! I Installed CM 12.1 via TWRP 2.8.6.0 like witten in developmet section in the forum. -> Houdini -->gapps will not work --> error: your recovery is missing the xz binary.
After that i realized that my trwp is not the latest and so I installed (by odin) the latest twrp. But it's not working (Pressing power+Volume up has no results) then i installd the old twrp 2860 and there I am.
What am I doing wrong. Why is the latest twrp not working?
Click to expand...
Click to collapse
SOLVED.... funny I reinstalled TWRP v2.8.7.1. and pressed Power+Volume up just for 2 sec. --> And it worked --> maybe my fault was pressing it too long
Funny wit the latest twrp i was able to insatall gapps

TWRP+ROOT for Marshmallow 6.0.1 S6 G9208 (Taiwan Version)

So its been a long time since we wait for root on our S6 Taiwan Version Latest version 6.0.1
Today I flashed my phone to the latest official version of Taiwan 6.0.1 G9208ZTU2DPD1, flashed the TWRP then via TWRP flashed SUPERSU and finally got root. I just got these from a chinese site apk.tw
So first we should download on our pc :
1-The latest official rom for taiwan from this direct link or from sammobile.com
HTML:
https://drive.google.com/file/d/0B15wMPEgxdTjR1dsY1VWTEZYWHM/view
2-Odin
3-TWRP
HTML:
https://drive.google.com/file/d/0B15wMPEgxdTjZ09RSElKUEJOOWc/view
Now we must follow these steps to
Flash the official Marshmallow
-Extract (unzip) the firmware file
-Open Odin
-Add the firmware file to AP
-Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
-Connect phone and wait until you get a blue sign in Odin
-Make sure re-partition is NOT ticked
-Click start and after it finishes wait till it reboots to Marshmallow
After it boots up download the latest SuperSu from Chainfire
HTML:
https://download.chainfire.eu/960/SuperSU/BETA-SuperSU-v2.72-20160510112018.zip
Go back to Download Mode (pressing and holding Home + Power + Volume Down buttons)
Now we flash the TWRP
-Open Odin
-Add the TWRP file to AP
-Click start and wait till it reboots
To get root rights we do those final steps
Turn off the phone
Press and hold Home + Power + Volume Up buttons to enter recovery
Since its chinese in the first screen you just need to slide
After you slide go to Download
Select BETA-SuperSU-v2.72-20160510112018.zip
Slide it again
And touch the button to the right to reboot
Once ur phone boots up u should be rooted
any question feel free to ask
It would be nice if our developers can manage to give us a english twrp theme or even better a official twrp for our phone, anyway we thank them
Cheers
Thank you ,
how to set selinux selinux permissive ?
Unable to get TWRP running
I have a chinese version SM-G9208 (never buy android in China since it doesn't come with any google services or apps).
Previously, I was able to root and install gapps. Unfortunately something happened a month ago and it was bootlooping.
I have been able to reinstall the official Android 6.0.1 using Smart Switch.
I have succeeded in rooting but have not been able to get TWRP install. I want to flash gapps.
I have tried using Odin and the files from TWRP website, I have tried the offical TWRP app and the TWRP manager app, and various versions of TWRP for zeroflte such as twrp-3.0.2 to twrp-2.8.6.
Using I get the recovery is not SEAndroind enforcing or I get caught in a bootloop. Once i saw the TWRP recovery screen but the screen was frozen.
I have read as many forum entries as I can to find a solution.
It looks like TWRP is the most likely candidate to be able to flash gapps. How can I get twrp to work? Is there an alternative to get gapps installed, most of the "installer" apks I have tried to not work.
Any have any success at this?
I should mention, the taiwan ROM does not work for Chinese phones as expected

Urgent Help Needed Flashing CM13 On a GT-I9195 LTE

Hi people.
I'm in the process of flashing my friend's Samsung Galaxy S4 Mini LTE.
Here's some details:
TWRP version: 2.6.3.0 (The one some dude here made himself)
ROM: cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-serranoltexx
SuperSU installed
Rooted using CM AUTO ROOT
Used Odin 3.09 to install TWRP
Everything is working fine but i'm having an issue flashing GAPPS.
9195 has a Krait 300 - which is an ARM processor so i downloaded the ARM 6.0 Micro package from OpenGapps.
Wiped all partitions, queued up the ROM and GAPPS in TWRP and flashed.
The process goes by fast and smooth, but the phone doesn't boot up after that.
The first time it took 25 or so minutes to boot up and ALL the GAPPS crashed after that.
What should i do?
I tried the following alternatives as well:
Bliss-v6.3-serranoltexx-UNOFFICIAL-20160521-1003
Slim_mini_gapps.BETA.6.0.build.0.x-20160516-2250
benzo-gapps-M-20151011-signed-chroma-r3
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
noppy22 said:
@Helhound0
That's an old recovery. I would update it with TWRP 3.0.2-1 from HERE, reboot to recovery, and then wipe /system, /data, /cache, and dalvik/art cache, then flash rom and gapps and reboot.
Click to expand...
Click to collapse
This worked!
I thought the old TWRP version was the only version compatible with the SGS4Mini.
I'm a Newb sure, but fairly sure this isn't my fault....
Hello, I have spent the past 2 days working on this flash you've stated as well and I can't understand for the life of me what I am doing wrong. You mentioned that TWRP may not have supported the mini but it seems that it does - odin just isn't installing it right? I am hoping people on here have already hashed this out on both ODIN and TWRP for this device and after spending 24 hours figuring this out i'm wondering if it's just some stupid thing i'm doing wrong. I've put the full stuff below which you may largely be able to ignore but what i need to figure out is how to install TWRP 3.0 or higher on my device, and how to keep ODIN from crashing. Can you help?
1. where I started and my goal:
My homestay mother in New Zealand who works for the tech firm Datacom provided me with a Galaxy S4 mini (GT-I9195 spark edition) that she had left over because she got a new phone for her work. I had a galaxy note 2 running default controls due to its setup on KNOXED up verizon, so i thought this was a good opportunity to switch to cyanogen since i've used the service before (someone else went through all this trouble for me and I am eternally grateful). So I am trying to install Cyanogen mod 13 with GAPPS package nano on to it.​
2. The file repretoires and guides I used:
TWRP 2.8.1 (originally) and it's accompanied manager
Trying to upgrade to TWRP 3.0.2.0 or 3.1.0
GAPPS arm 6.0 mini/nano/pico (I've tried all three)
Odin 3.12.3 with requisite drivers (shows blue on status bar)
Default Bootloader for Android devices
CMD ADB systems with requisite drivers
CyanogenMod 13 (cm-13.0-20160820-ZNH5YAO0J7) (currently installed and working san-GAPPs)
3. What I've done Start to current:
starting with the phone locked, unrooted, and factory resets not working (company KNOX settings)
Installed Kingroot, superSU, RootChecker, TWRP manager and official ap, P-uninstall = Obtained Root
Attained root on the phone, deleted all KNOX and KGNT protection. = obtained unlocked sim/recovery loader
Installed TWRP 2.8.6 (any more recent installs failed as I will explain below in problems) Attempted to flash it = read success
Failed to boot into TWRP recovery - provided default recovery instead.
downloaded and installed ODIN. Used default boot loader and attempted to install TWRP directly through ODIN = Works
placed CM13 zip file and GAPPS 6.0 - ARMS Nano on SD card.
Created recovery on SD card
Wiped cash, devalk cache, and internal storage = clean partition
Installed BOTH CM13 and GAPPs 6.0 as zip files using TWRP 2.8.6 = worked
rebooted system into new OS
OS got stuck in boot cycle due to GAPPs package. after some googling i found out that Gapps requires TWRP 3.02 or higher (but i couldn't get those to download onto my phone at all. [here enlies the ROOT of my problem - you're allowed to kill me now]
Returned to TWRP and installed JUST CM13 on the device = works great! just no GAPPs! and no ability to download apps
Used Odin, TWRP manager, the official TWRP app, and CMD ADB sideloader to attempt to install all 3.0 and higher TWRP files = all of them failed
now I cannot access a bootloader at all, but can access my OS just fine. It refuses to accept any TWRP bootloaders but without them i cannot install GAPPS
4. Where I am Currently & Problems I'm running in to:
Right now CM13 is on and stable for my device. My Recovery loader is refusing to come up AT ALL. Attempting to install both .img and .tar files of TWRP read as succeeding in the apps but don't come up.
ODIN can't load anything on the device. Either it keeps freezing and crashing any time I touch it or when it does go through the device still can't bring up TWRP. Even when flashing 2.8.6 which originally worked as a recovery file it fails as well. I can't get back to TWRP working at all.
ADB sideloading just results in <waiting for device>. I am clearly using "fastboot" instead of ADB during the point in which i am flashing the recovery file on to it.
5. What I need Help with:
I need to know why TWRP is freezing any time i attempt to install it regardless of version and how to get it properly installed
if someone could point me to a reason odin freezes regardless of what options I tick on or off, file I upload, or whatever i'd love to know
I see 2 ways out of my predicament and i'm not sure which one I should spend more time on: 1) get TWRP 2.8.6 to work again and then find an older GAPP partition to load on to it. or 2) Get TWRP 3.0 or greater to work on it, and then use current GAPP packages. which would be best?

[SM-P607] TWRP install issue (recovery boot loop)

Hi all, looking for some help here.
I picked up a pair of P607's to install Lineage on.
1. I flashed (via ODIN) the latest Samsung factory build from Sam Mobile (Now running 5.1.1).
2. Grabbed the latest TWRP tar file (twrp-3.1.1-0-lt03ltexx.img.tar)
3. Flashed TWRP via ODIN (AP button, selected the twrp tar, unchecked auto-reboot)
4. Held power button and turned off.
5. Powered back on and Held the [home - vol up - pwr] to boot into recovery to check TWRP.... and..... Recovery Boot Loop.
Odly enough, if I get it back into download mode and just boot it normally, it will boot fine back into the OS (stock rom, not lineage yet)
I can recover back to the factory by re-flashing the stock rom again, so it's recoverable.
I've tried with two different 3.1 TWRP versions now, twrp-3.1.0-0-lt03ltexx.img.tar and twrp-3.1.1-0-lt03ltexx.img.tar, both do the same thing.
Any ideas on this one?
There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?
how did you get out of the boot loop? i cant seem to get back in to download mode
XnoteX said:
how did you get out of the boot loop? i cant seem to get back in to download mode
Click to expand...
Click to collapse
Today I got the same bootloop problem.
Impossible to enter the Download-Mode.
I removed carefully the Backcover and disconnect the battery plug for some seconds.
On the next start I´m holding down Vol- and entered Download Mode.
With Odin I flashed TWRP 3.0.2.0 (same version like before) and its working again without loosing the installed programs.
I think you can also wait until the battery is empty .....
Hope it helps a bit to recover a great tablet.
sillysuliman said:
There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?
Click to expand...
Click to collapse
Most ROMs here install fine with 3.0.2. That's what I am using on my 607T.

Categories

Resources