*Newbie* Samsung Galaxy Tab 3 SM-T217A - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I have an old Samsung Galaxy Tab 3 SM-T217A (S3..?) I got from ATT 10 years ago maybe and it's still in perfect condition. I'd like to root it and update the OS from 4.2.2 to 4.4.2... I have the ODIN and Samsung drivers. Can anyone provide further instruction on where to find a stable OS. I only want to use for Tiny CAM Pro...

Your device is Tab 3 7.0",
There seems to be unofficial build or Resurrection Remix Oreo, so far seems there's no bugs.
Try it:
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-resurrection-remix-n-v5-8-0-t3507947
It's easy, 1st flash TWRP via Odin, then get into recovery, do a simple wipe, flash ROM ( & GApps if you want), then reboot.

Mohamedkam000 said:
Your device is Tab 3 7.0",
There seems to be unofficial build or Resurrection Remix Oreo, so far seems there's no bugs.
Try it:
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-resurrection-remix-n-v5-8-0-t3507947
It's easy, 1st flash TWRP via Odin, then get into recovery, do a simple wipe, flash ROM ( & GApps if you want), then reboot.
Click to expand...
Click to collapse
This seems to be for sprint variant

Related

Problems with TWRP/CyanogenMod 12.1 - Motorola MotoG 2nd Gen XT1068

Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use

i9305 stuck on boot logo

Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then

[Solved] Rom setup blocked, Tab S2, T813 blocked!

Hi dear developers,
I just got my new Galaxy Tab S2, T813. Updated it to Nougat, firmware T813XXU2BQD1_T813OXA2BQD1_DBT. I rooted it via Chainfire's autoroot and worked perfectly fine. I installed the latest TWRP (twrp-3.1.1-1-gts210vewifi), advance wiped in twrp (like tens of times before with Galaxy S5, Galaxy S7, Redmi 4, ZUK Z2, Xiaomi Mi 5s, LG G2 etc.). I flashed Lineage 14.1 (Lineage-14.1-20170516-nightly-gts210vewifi) but when I rebooted the phone Lineage setup would not start. I went back and advance wiped again and installed an older Lineage version but again the same. I advance wiped again and installed Omni (Omni-7.1.2-20170521-gts210vewifi-weekly), but here again setup would not start. I reformatted the data in twrp and reinstalled Lineage 14.1 but again the same. So I went back and flashed via Odin3_v3.12.3 the stock firmware (for Germany) T813XXU2BQD1_T813OXA2BQD1_DBT. Odin command was pass and i though everything was fine. When the original firmware rebooted i have the same problem, the setup would not start and starting apps would crash. I entered recovery (of course stock recovery because twrp has been wiped by odin), but it says "no command".
Smart Switch would not support my device although it actually should.
I tried to flash via odin also on my second PC but again the same problem. Both PCs are running Windows 10.
I never faced something like this before. And after hours of search I found nothing. Please help me solve my problem so that i can install at least one firmware (no matter which one: Stock, Lineage, Omni etc.).
When you flashed lineageOS or omni rom, did you also flash gapps?
musashiken said:
When you flashed lineageOS or omni rom, did you also flash gapps?
Click to expand...
Click to collapse
First time flash:
+ clean advanced wipe
+ lineage
+ gapps (ARM64, Android 7.1, Pico)
+ addonSU
other times flash:
+ clean advanced wipe
+ lineage
or
+ clean advanced wipe
+ omni
I believe either flashing Chainfire Autoroot file or flashing TWRP might have caused the problem and might have deleted something or maybe i deleted something during first time wipe via twrp.
Is there a patch or aboot or something to flash via Odin prior to flashing the stock firmware to correct the problem with stock rom setup blockade?
Ok, I'm not sure what went wrong with how you did stuff but let's not use Chainfire's autoroot again. The best way to root is to do it manually.
Anyway, firstly you should be able to go back to stock samsung firmware by using Odin and flashing the full tar file. I'm not sure why that is not working for you as that's the only way to reset and fix your tablet.
Please check how to flash the full firmware via Odin again.
- ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Once you are able to load a fresh samsung firmware, then come back again. I'll see if I can guide you through the TWRP and rooting process again.
musashiken said:
ensure you downloaded the correct nougat firmware file. Latest LineageOS should require the EU version of the nougat firmware. I think it is T813XXU2BQD3. Not the firmware you used.
Click to expand...
Click to collapse
Thanks fo the tip with the new version of firmware. I installed the firmware ...QD3 via Odin...
Closed per OP request

[JazzROM] [Stock Firmware Base] Samsung Galaxy Tab S2/SM-T713 Nougat 7.0

JazzROM For Samsung Galaxy Tab S2/SM-T713 Nougat 7.0
A custom ROM based on official firmware Samsung Galaxy Tab S2/SM-T713 Nougat 7.0 (XAR- USA version)
[Deodexed, Deknoxed, Rooted, Internal Encryption off, Init.d, Su.d, etc..etc..all good stuff you will find in pretty much every good custom ROMs..]
Nobody is allowed to take stuff from my rom without asking me! Thank you.
A fair warning before you jump on and flash this ROM: Installing this Rom will void warranty. Installing TWRP will trip knox to 0x1! Secure folder will be unusable.
Prerequisites / What you need:
1 - No brainier that flashing custom ROMs requires a custom recovery, we use TWRP 3.1.0-1 - look here @ashyx thread download for your device.
2 - If you are still on official firmware and never rooted, maybe it is time to get into custom recovery! - so get that one going..have question about TWRP, please ask @ashyx thread, not here.
3 - Now that you have fully working TWRP installed, it is good time to do full nandroid backup and save that to your microSD card and your computer (in case all goes wrong, you can restore it)
4 - Keep in mind that we developer always assume you know what you are doing since you are here and interested flashing custom ROMs!
5- Remember that do not set read-only mode system in TWRP
6- Are we good up to this point? if yes, then proceed to installation step!
Installation:
-- Of course, do full nandroid backup!!!!!, dont blame ROM developer if something goes awfully wrong..so do full backup!!
1 - Then, first download JazzROM-SM-T713.NOUGAT.7.0.DEODEX.V1.zip copy it to your tablet's internal sdcard or microSD card.
2 - Reboot in to TWRP, and do Data Format [Wipe]/[FormatData], type "yes", and once it done, go back to main screen
3 - In TWRP main screen, -->Wipe-->Advanced Wipe, and check only; "System", "Data", "Cache", and "Dalvik/Art cache" - do NOT select any other options!, once it done, go back to main screen.
4- In TWRP main screen, select Install, and Select Storage where you saved JazzROM-SM-T713.NOUGAT.7.0.DEODEX.V1.zip in first step above, and select "JazzROM-SM-T713.NOUGAT.7.0.DEODEX.V1.zip" then swipe to confirm flash and wait until it finishes...
5- Reboot to System, don't be alarmed, you may get couple boot-loops (for me it happened 2 times) with SuperSU-v2.82, this is normal.
6- Now, while your tablet is rebooting, go get coffee or read a short book or watch something, it is going to take several minutes (5 to 15 min.)
7- Once reboots, go thru the setup of tablet as you normally do.
8- If all goes fine, you should be running stock base deodexed Nougat 7.0 ROM!
Download Links:
====>DOWNLOAD: JazzROM-SM-T713 V1.0
reserved
just in case
Nice, will try it.
Looking forward to test this as soon as I get a soft bricked Tab S2 that I will try to resuscitate.
Don't pass the bootlogo
Same here, stuck on bootlogo.
Due to complaints about boot logo freeze i haven't tried to test the rom yet. Any feedback from the developer?
RIP OP
JazzROM saved the day
My Galaxy Tab S2 SM-713 Nougat developed a FRP
---------- Post added at 07:36 PM ---------- Previous post was at 07:26 PM ----------
My Galaxy Tab S2 SM-713 Nougat developed a FRP block after rooting which bricked it. I wanted to reflash the original rom but unfortunately I never copied the id number from the tablet
After lots of searching, I found this "generic" JazzRom and downloaded the zip file which I then converted to a tar.md5 file. I then used ODIN to flash my tablet (fortunately the upload mode wasn't bricked).
Flashing proceeded normally and when done, the tablet booted fairly quickly back and everything looked as if it never was bricked.
I know I should probably do a full factory reset ad restore all my apps from my backup but everything is working so smoothly so I'll do that tomorrow.
Thanks for the excellent job.
cannot open the androidfilehost
My Samsung Tab S2 (8.0) SM-T713 Running 7.0 downgrade to 6.0.1
Hi guys! Newbie here.
Just want to ask if it is possible to downgrade my tablet that is running on OS 7.0 to Stock rom or on atleast OS 6.0?
The OS 7.0 was updated using OTA and it really drains my battery just want to roll back again on the stock or on the previous version.
Please help.
Thank you so much.
Help ROM samsung tab s2 8.0 32gb SM-T713
Hi, I need your help.
I would like a free rom for my tablet samsung tab s2 8.0 SM-T713 2015.
I've already put several rom's but none worked.
I need your help urgently, please.
Thanks

Cannot flash Oreo roms

Hi , I am able to flash nougat roms such as aosp extended ,but cannot flash oreo roms like the ones by daniel_hk . There are no errors while flashing , but the ROMs are not getting flashed . This started to happen suddenly from last month when I tried to flash clean stock rom s433 through twrp which gave an error . I am however able to restore a twrp backup of omni oreo rom . As I said the issue started since a month back . Any ideas ? I am asking this as I want to flash lineage os 15 .
Can you check if your downloads (rom .zip) are corrupted. Have you tried any other rom apart from lineageos. Also before installing the rom you need to wipe everything except internal storage/sdcard/otg. Then install rom/gapps/supersu. Also I would take suggest the Lineage OS 15.1 Rom for the k3 note (I've used it) as the rom is prone to crashes and plus camera and bluetooth dont work. Flash Resurrection Remix as it is stable and everything works in it except some minor things.

Categories

Resources