Develop Bugs

[EVERYTHING] Samsung Galaxy Attain 4G LTE

Hello guys!
This thread will be an expensive everything for the Galaxy Attain since it doesn't have it's forum so I'm going to make everything here.
I will be updating the thread with ROMS, RECOVERIES, GUIDES, ETC. but right now is too late and I want to sleep , will leave some.
GUIDES:
-Unbrick Galaxy Attain
ROMS:
THEMES:
KERNELS:
RECOVERIES:

Unbrick Galaxy Attain.
Please follow every step as wrote.​
With this guide you will bring your Attain back to life like I did with mine.​
NOW THE TIME HAS COME!, Follow the steps
Step 1. Files to download:
-Heimdall Suite: CLICK HERE TO DOWNLOAD
-GA Fix: CLICK HERE TO DOWNLOAD
Step 2. Heimdall Suite
Heimdall Suite is a suite made by Benjamin Dobell, so thanks to him we can have the Galaxy Attain back to life.
-Extract the Heimdall Suite wherever you want, but to make sure extract it in the main disk (C:\).
-After you have extracted it go into the folder of Heimdall Suite and open the Heimdall-fronted.exe (To make sure you have MS Visual C++ 2010)
--In case it gives error MSVCP100.DLL, download MS Visual C++ 2010 here: CLICK HERE TO DOWNLOAD
--Also make sure you have lastest Samsung USB Drivers, if you don't have it here is a link: CLICK HERE TO DOWNLOAD
Step 3. Preparing/Configuring Drivers
-In the folder of Heimdall Suite go to a folder named Drivers
-Attach USB to your Attain and put it into download mode. (without battery) *Volume Down + Power* then *Volume Up*
-After the computer recognizes it open zadig.exe
-Click on Options and click on List All Devices
-Go to the List and mow you should see "Samsung USB Composite Device" on the list.
-Click on Install Drivers
-Done.
Step 4. Attain Back to Life / Heimdall Suite
-Go back to Heimdall Folder and open heimdall-fronted
-Click on Browse and look for the AttainFix.tar.gz
-Click on Load/Customise.
-Click on Flash.
-Voila! (Done).
If you have any question or anything to ask, just feel free I'm here to help,
Special thanks to:
*MobilePlay
*DadCup
Also thanks to:
*Shabbypenguin
For their great support and all the files =D
If you like my work buy me a beer

Reserved again.

And once again reserved lol.

Last time reserved

Thanks for making this thread
Sent from my SCH-R920 using xda premium

ICS
Any movement on an ICS rom?

thanks

Samsung USB Drivers download is dead
Samsung USB Drivers download is dead . Please reupload again.

I've tried everything on here and a lot of other fixes too. I have had absolutely no luck
I believe my phone is soft bricked. It's booting by default into system recovery
Any help would be great

samsung Galaxy Attain 4g root
BrogiBear said:
I've tried everything on here and a lot of other fixes too. I have had absolutely no luck
I believe my phone is soft bricked. It's booting by default into system recovery
Any help would be great
Click to expand...
Click to collapse
Ok, This is no issue.
I have soft bricked the samsung Galaxy Attain 4g numerous times.
Lets confirm a few things. first, is this still an issue?
You used samsungs upgrade?
MPCS_R920_FG02_Simple_Download_Tool.exe
SIMPLE_R920_FG02_CL1163798.tar
You Need:
Odin 1.85.exe
Attain-4G.pit
Pre-Rooted.tar
I have them and can walk you through this. sorry, i could use help on attaching these apps/sw?
Thank You

I need help
I have two Attains. 1 is rooted and screwed. It says for "baseband: Unknown". Samsung simple upgrade doesn't recognize it and when I put it into recovery/download mode it say "ODIN" at the top. It won't come out of airplane mode. It has been rooted by the previous owner. I am trying to return it to it previous glory. I want to start fresh. The other is untouched. The factory ROM is still intact and the phone is fresh. How do I copy the factory data and restore the screwed phone.
Please, I am a noobi so let's play nice. I have rooted my admires previously. Both of them are fine. One I even updated and rooted with odin.
Any help would be appreciated.
Thanx in advance

u can use samsung kies to copy your. tar and. pit. from new phone and/OR other rom and then use oden to get the job done

Links fixed, also if anyone needs help please PM me and I will also post the solution I used here.

thax
thax

good
good work ..

Constant Restart
Having problems here. It only constantly reboots itself.
After I flash the phone, it restarts into recovery mode. The first time I simply selected Reboot, and the second time, after another flash, I wiped it and restored it to factory defaults.
Any help would be greatly appreciated!

can yo send me the file to unbrick my galaxy attain?
Hi bro, do you have the file to recover the galaxy attain?, because my phone is bricked and i need to repair it. Can you help me?

Request
Justrollen said:
u can use samsung kies to copy your. tar and. pit. from new phone and/OR other rom and then use oden to get the job done
Click to expand...
Click to collapse
Samsung ON5. G550T1 ROOTED ZIP available upon request

[HOW TO]Root the Tab Pro 8.4 and 10.1

Credit to @roustabout for providing @Chainfire with the stock recovery. And to @blulite for monitoring the CF thread for the release of CF Auto-Root.
NOTE #1: This procedure WILL trip the Knox flag.
NOTE #2: It is advisable that you do not connect your Tab Pro 8.4 to your computer until reaching Step 7.
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
Softpedia
Samsung's Website (you'll have to search a generic device, like Galaxy S4, in order to find the driver)
OR
Install Kies:
http://content.samsung.com/us/contents/aboutn/kiesIntro.do
STEP 2
Tab 8.4 Download CF Auto-Root (8.4)
Tab 10.1 Download CF Auto-Root (10.1)
STEP 3
Extract files to a folder on your desktop, open newly created folder, run Odin.
STEP 4
In Odin, for the Tab 8.4, choose "PDA" and select the file "CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5" (included in the CF Auto-Root zip)
For the Tab 10.1, choose "PDA" and select the file "CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5" (included in the CF Auto-Root zip)
STEP 5
Power off your Tab.
STEP 6
On your Tab, hold the Power and Volume Down buttons until you see a "Warning!!" screen with a large yellow triangle at the bottom. Press Volume Up to continue.
STEP 7
Connect your Tab to your computer using the supplied USB cable.
Your computer should now automatically install the appropriate drivers for use in the Tab's "Download Mode".
STEP 8
In Odin, verify that your Tab is connected to a COM port (yellow box with text "COM x" where "x" is a number)
STEP 9
In Odin, press "Start"
FINISHING UP
Upon a successful flash, Odin will display "PASS" and your Tab will reboot.
You can expect to have to disable Knox, and SuperUser should prompt you to do this.
Be sure to thank @Chainfire; he's an amazing contributor to all that is Android.

leatherneck6017 said:
Credit to @roustabout for providing @Chainfire with the stock recovery. And to @blulite for monitoring the CF thread for the release of CF Auto-Root.
NOTE: It is advisable that you do not connect your Tab Pro 8.4 to your computer until reaching Step 7.
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
http://forum.xda-developers.com/showthread.php?t=2038555
OR
Install Kies:
http://kies.samsung.com/
STEP 2
Download CF Auto-Root (link is at the bottom of the page)
STEP 3
Extract files to your desktop and run "Odin3-v1.85.exe"
STEP 4
In Odin, choose "PDA" and select "CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5" (it was included in the CF Auto-Root zip)
STEP 5
Power off your Tab.
STEP 6
On your Tab, hold the Power and Volume Down buttons until you see a "Warning!!" screen with a large yellow triangle at the bottom. Press Volume Up to continue.
STEP 7
Connect your Tab to your computer using the supplied USB cable.
Your computer should now automatically install the appropriate drivers for use in the Tab's "Download Mode".
STEP 8
In Odin, verify that your Tab is connected to a COM port (yellow box with text "COM x" where "x" is a number)
STEP 9
In Odin, press "Start"
FINISHING UP
Upon a successful flash, Odin will display "PASS" and your Tab will reboot.
You can expect to have to disable Knox, and SuperUser should prompt you to do this.
Be sure to thank @Chainfire; he's an amazing contributor to all that is Android.
Click to expand...
Click to collapse
The link on that thread for the usb drivers has been deleted, and the kies site isn't loading.

scottharris4 said:
The link on that thread for the usb drivers has been deleted, and the kies site isn't loading.
Click to expand...
Click to collapse
Thanks. Updated OP.

leatherneck6017 said:
Thanks. Updated OP.
Click to expand...
Click to collapse
Thanks, and does this delete anything on my device when I root like it did on the Nexus 7 and Nexus 4?

scottharris4 said:
Thanks, and does this delete anything on my device when I root like it did on the Nexus 7 and Nexus 4?
Click to expand...
Click to collapse
No.

leatherneck6017 said:
No.
Click to expand...
Click to collapse
Awesome. I'll have to try this soon, sometime when I have the time to fix it if I screw up somehow!

leatherneck6017 said:
.....
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
Click to expand...
Click to collapse
Erm.. latest Samsung USB Drivers are linked to on this very site...
SAMSUNG USB Drivers for Mobile Phones (x86 & x64) v1.5.33.0

SuperUser hasn't asked me to disable Knox. How do I do it manually?

Thanks for the detailed instructions for rooting. I do have a question as a newbie, if it's okay.
If I root my Tab Pro 8.4, can I still use Comixology and Zinio accounts? If yes, can I use the SD card as the main installation for Comixology and Zinio since I have lots of digital comics and magazines I would like to download.

Will this root work on the 10.1?
Sent from my SM-T520 using XDA Premium 4 mobile app

davidn11 said:
Thanks for the detailed instructions for rooting. I do have a question as a newbie, if it's okay.
If I root my Tab Pro 8.4, can I still use Comixology and Zinio accounts? If yes, can I use the SD card as the main installation for Comixology and Zinio since I have lots of digital comics and magazines I would like to download.
Click to expand...
Click to collapse
Rooting should have no effect on what non-root-requiring apps you can use. If the apps allow you to select a storage location, you should be able to use the SD after doing THIS.

scottharris4 said:
SuperUser hasn't asked me to disable Knox. How do I do it manually?
Click to expand...
Click to collapse
Open the SU app, it should prompt you then. If not, download SuperSU from the Play Store. It'll probably prompt you to update the binary as well.

http://true-android.blogspot.com/2014/02/how-to-root-samsung-galaxy-tab-pro-101.html
Sent from my SM-T520 using XDA Premium 4 mobile app

Thank You leatherneck6017 for pulling the rooting info together
Root was a breeze
Going with out a rooted device just seems so unnatural..

Worked like a charm on my 10.1 thanks for the instructions and as always huge thanks to Chainfire!!

Holy ****... I just got a bsod right in the middle of flashing with odin. Luckily it didn't brick or anything but I am not rooted after this. Will try again.
Edit: with the 8.4. Using a windows 7 machine.
Edit 2: well it bsod'ed a second time, i might try this on my windows 8.1 machine.

Encryption and stock firmware
So far so great over the last few days on my 8.4, thank you!
I tried to encrypt the device itself (not SD), had full password enabled, it reboots like it is going to start encrypting but never does. Another forum had some info that as of 4.3 this was happening on rooted devices (possibly knox related?) and you had to go back to stock everything to encrypt THEN root the device. No big deal, but I can't find a way to go back aside from a link to 4.4.2 firmware from nasirtech's blogspot which I don't really know if it's legit or not. Why can't we just download it from Samsung's website? I also tried KIES 3 and it says I'm running the latest firmware.
Downloading OTA gives "Your device has been modified. Software updates are not available" ok who cares, I'm planning to use CM whenever it's working anyway.
Aside from that the only other negative thing I've noticed since rooting was the KNOX WARRANTY VOID: 0x1 message on the custom download screen, but again, I don't care.
Really just curious if anyone has a workaround to the encryption thing, or if there's some better alternative anyway.

has anyone used this method with windows 8.1?

I have. Worked fine.
Sent from my SM-T320 using Tapatalk

qn1gJ1 said:
So far so great over the last few days on my 8.4, thank you!
I tried to encrypt the device itself (not SD), had full password enabled, it reboots like it is going to start encrypting but never does. Another forum had some info that as of 4.3 this was happening on rooted devices (possibly knox related?) and you had to go back to stock everything to encrypt THEN root the device. No big deal, but I can't find a way to go back aside from a link to 4.4.2 firmware from nasirtech's blogspot which I don't really know if it's legit or not. Why can't we just download it from Samsung's website? I also tried KIES 3 and it says I'm running the latest firmware.
Downloading OTA gives "Your device has been modified. Software updates are not available" ok who cares, I'm planning to use CM whenever it's working anyway.
Aside from that the only other negative thing I've noticed since rooting was the KNOX WARRANTY VOID: 0x1 message on the custom download screen, but again, I don't care.
Really just curious if anyone has a workaround to the encryption thing, or if there's some better alternative anyway.
Click to expand...
Click to collapse
That one on nasirtech's blogspot appears to be for Portugal. As far as I know, no one has posted a stock firmware for US models yet. Which makes me wonder...could it be extracted from Kies somehow?

Root method for Alcatel OneTouch Conquest 7046t

Looking for any information and help on rooting this device. Thanks in advance.

jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I managed to root this device today using king root. The first try failed. I ran it a second time and got it to work. I installed titanium backup which gave a warning that the superuser binary was functional but may cause problems. I installed supersu from the play store and tried to update the binary, which failed, even after a restart. Not sure what that means, perhaps someone more knowledgeable can tell me. I also installed other root apps, SD maid pro and rom toolbox pro, both of which seem to function as they should. I have yet to confirm root with a root checker but I intend to shortly. Hopefully this information will help with further development of this device.

The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
sosthenisRR

King root
King root version 4.5.0 works for Alcatel one touch conquest thank you very much. Titanium backup doesn't like the manager and anticipates problems and recommends superSU. I was unable to install the binary normally but haven't tried using the cwm or twerp option. Busybox 26 installed and I'm new to xda and will continue on the subject.

sosthenisRR said:
The above listed method works. I did it this morning by fluke. I just tried it thinking it wouldn't work but it did. I have lollipop v 5.0.2 and the kingrooy file I downloaded was from google searching "king root" without apk. Half way down you should see the 4.6 link.
Current version is 4.6x which works on most newer mid grade phones. Then I used kingroot to SuperSU files and setup which I got from Google. Can't remember link but search kingroot to supersu and it should be the first link. Run and reboot enter supersu and update binary. You ready to install root apps, debloat, and customize. Haven't found any customs kernel, ROMs, recovery, or anything so I will be working on that soon. Keep an eye out in the near future. Unregistered user until I finish posting.
Click to expand...
Click to collapse
Success! thank You

Yep, that method works great. I was looking for a.method to.root this device. The only difference was I used this link to switch from KingRoot to SuperSU
androidmtk.com/replace-kinguser-with-supersu
Thanks for the OP

Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?

Need stock rom!!
bmk072 said:
Does anyone have a link to the stock firmware and or the version of Ono Touch Upgrade for this device?
Click to expand...
Click to collapse
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work... netspoof said that i might have not given it superuser permissions ( which i did...when kingroot asked i clicked allow) and titanium backup pro said it failed to get root and that it recommends supersu....i installed superuser from chains sd and tried to update the binaries, but it failed......i notcied that in superuser it said that i had root and it said something about kinguser in superuser...so it bacame clear to me that i need to switch kinguser with superuser...or supersu like titanium backup and this thread suggested
so i followed the directions and found kingroot to supersu on google and let the app "supersu me" do its thing...
while supersume was uninstalling kingroot, and installing supersu....something popped up and asked me if i wanted to delete all the files associated with kingroot...i clicked yes....and thats what i think caused my phone to brick
when it said supersu was successfully installed, i went to the app and successfully updated the binaries...right....well it told me that i should reboot the phone because i just updated the binaries so i clicked the reboot now button that the app offered me and the phone went to reboot....but stayed at the alcatel onetouch screen and all i can access is the recovery mode....in recovery logs it says something about no such file or directory for dev/tty0 or soemthing. it said it again in something about the bootloader....
so i think what happened is when i told supersu me to delete all files associated with kingroot it went ahead and deleted a bootloader file or something....normally i would just reinstall the stock rom but this damn phone is so new there isnt one online anywhere
so anyways....can anyone tell me where to get the stock rom or how to unbrick my phone.....i want to just put the stockrom on an sd card and apply it as an update to restore whatever file that is missing and keeping it from booting up....i was thinking (since i happen to have a duplicate phone) that i could make a backup of the same exact phone in twrp and put it on the sd card, switch it to the bricked phone...recovery mode...apply update from phone storage...and bam...that shoulod work! right?
the only thing is....can you put twrp on this phone yet? there is really no development on it at all
so here are the questions i need answered
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
same thing here, except I can't boot into recovery or download. fflashcustom custom twrp from the aforementioned. still won't boot into recovery, hangs at the alacatel logo. what I did was hold down volume and power til it reboots 3&4 times, than it seems to boot back to a android. I even tried the factory restore and it wouldn't do that either. *shrug* imma hafta do more research and find out wtf. but ya, that should fix your sh*t. also. and haven't found the boost stock rom yet either. it's a custom rom, it's not actually lollipop.

Alcatel Onetouch Conquest 7046t rooting, etc.
jslow3 said:
Looking for any information and help on rooting this device. Thanks in advance.
Click to expand...
Click to collapse
I couldn't find the Alcatel Onetouch Conquest 7046t listed in the list of devices on this site at all, other than in a few posts. Maybe people don't think it's a worthy device to work on? Anyway, enough of that rant, what I would like to contribute here is that I tried using kingroot for my old Motorola xt912 which I had install Dirty Unicorns KitKat ROM on successfully, but lost root on. First it said it couldn't root it, then, after trying again, said it could. I started receiving alerts from Avast staying it has detected viruses, and it seemed to install it's own version of super user, when I already had the one by chain installed.. Which struck me as suspect activity and rose yet more red flags.
I also find it suspect that the users posting here on this thread seem to only be newbies.
Any thoughts or feedback is greatly appreciated. Thanks for reading.
P.S. .. And yes, I am interested in rooting this phone, debloating it, installing custom rooms, etc.

mistaweeks said:
my device is bricked! i have the alcatel onetouch conquest 7046t for boost mobile....i read this thread and decided to do exactly what everyone who posted on the thread said to do...i i got kingroot version 4.6, and it worked on the second try....but no root apps would work...
does anyone have a stock rom of this phone they could put in this thread?
can i get the stock rom straight from alcatel?
has anyone got twrp or cwm recovery onto this phone
i have never bricked a phone and not been able to fix it...i refuse this to be the one
Click to expand...
Click to collapse
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app

I'm not a newbie y
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....

mistaweeks said:
Ya I've been doin this for awhile and have an extensive list of phones I have rooted, debloated, installed custom roms on etc....and I have never had as much trouble with a device as I have with this phone....this pos phone isn't even on their site! I got another phone from boost (same one) And did the same root method....bricked it.....but I still have the one bricked phone....waiting for a stock ROM
Ya man........get a different phone.....
Click to expand...
Click to collapse
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Rusty they sent that phone to you special delivery from HELL! They're just testing you, bro. Lol
But seriously, I think if you could somehow get the scatter.txt for the demon (without having to risk rooting and bricking a good one), then it would be possible to use SP Flash to simply read back the ROM of a properly working phone (up to and including the recovery partition) then simply do a direct memory write onto any bricked device. Should wake it up immediately after the flash. The only exception would be if the custpack partition had something really stupid done to it...like someone messing with the buildprop.txt file! That would put it into a head-spinning bootloop.
So the key here for this demon is for someone on this thread to post the scatter.txt file PLUS a working stock ROM. Is there anyone out there who has already successfully rooted who can post a ROM? Or at least post the scatter.txt?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
i tried rooting the new alcatel the same exact way ( usb debugging was enabled both times) and ended up bricking it....i was doing this for my friend...we ended up just going to boost and telling them that there was a defect in the phone they gave him the day before and told them to give him the moto e ( which has so much developement on it its insane)
anyways my friend just gave me the other bricked alcatel one touch conquest and said that if i can fix it i can have it. so i no longer have a duplicate device to work with . can i even flash a stock rom with the original recovery ? im going to try to download the program from alcatels website like you said and see if that works
then if i get it working im going to get the program you were talking about where u said i can make a clockworkmod recovery for it....

CVAngelo said:
Rusty, it's possible that the reason your phone bricked is that it was not fully/properly rooted in the first place. So when SuperSu tried to Un-kingroot it, something went terribly wrong. By the way, had you remembered to turn Developer Options on and set USB Debugging on before running the KingRoot app?
Anyway, there are a couple of options to easily unbrick since you have an identical device.
Note that you can't unbrick by installing TWRP or CWM on your working device, then flashing the bricked device, UNLESS you already have the same custom recovery installed on the bricked device and can boot into that recovery. These recoveries do not provide their backups as a flashable zip, nor are they compatible with each other, which is why you need the identical custom recovery on the bricked phone.
Here is how you can unbrick your device. Go to Alcatel's website and download and install their Mobile Upgrade S software - you will find the link in the support tab for most of their models (or use Google to find it). This is the official Alcatel tool that you would use to flash their stock ROMs onto your bricked phone.
That's the easy method. But if you want a learning adventure, let's pull out your working device. Lol. Go ahead and root it with the King Root app. You may have to try several times to get it fully and properly rooted. Make sure you run a root checker app to confirm that it's rooted. Do not use the SuperSu Me utility yet.
Once you've confirmed it's rooted, install busybox. I prefer the Busy Box X app from Rob Nedi over Stericson's.
Ok, so now we want to install the MTK Droid Tools on your computer. On your phone, make sure USB Debugging is still on. Now connect your phone to the computer and let the drivers for the phone automatically install. Once the drivers are installed, run MTK Droid. It should automatically detect your phone. Next select the Blocks Map button. Then save the scatter.txt file it gives you. Make a folder somewhere because you're going to next use SP Flash Tool to backup the ROM from your phone.
Use Google and XDA to learn how to use MTK Droid and SPF. Here's a helpful link:
http://freaktab.com/forum/mtk-based-devices/mtk-phones/13919-some-useful-tools-for-mtk-phones
Once you've installed SPF on your computer and created the ROM_0 readback of your ROM, go back to MTK Droid Tools and let it break the ROM_0 down into all the partitions that are contained in the ROM. You do this on the root.backup.recovery tab of MTK Droid. Select the "To Process File ROM From Flash Tool". Note that during this process, the Tool will give you the option to create the ClowWorkMod recovery for your phone!
Once the ROM partition files are created by MTK Droid, place them in that folder you created. At this point, you can use SPF to flash the stock ROM to your bricked phone. This will unbrick your phone.
(There's an even simpler way to unbrick your phone with SPF. Instead of backing up the entire ROM of your working phone with SPF and then processing that ROM woth MTK Droid, in this case, you will just READBACK the ROM up to the recovery partition and no further. Then do a direct MEMORY WRITE of that partial ROM to your bricked phone. This will unbrick it. But this approach will not allow you to create the CWM recovery.)
Finally, once you've unbricked your phone, you can install either the Flashify or Rashr app on your phone, and use that to flash the CWM recovery image you just made with MTK Droid onto your phone's recovery partition. I usually also flash the boot_patched boot image, which was also created by MTK Droid, to the boot/kernel partition.
Long post, but I wasn't sure if you were up to an adventure. Please note that there is always a risk that you brick your working device if you make a dumb mistake along the way. It's going to be really hard to brick your working phone because you're pretty much just reading from it and not writing anything to it except when you are rooting it....but just be careful. You've been warned. Lol. But I suspect that like me, a bricked device is just a learning challenge. So enjoy.
Don't forget to thank me!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods

mistaweeks said:
strike the alcatel mobile upgrade S off the list of possibilities...
first of all.... the alcatel onetouch conquest 7046t is not even listed in supported devices, and when i downloaded/ installed mobile upgrade to my windows computer it said " pick your device " and it wasdnt listed in the dropdown menu there either
i still tried selecting the 7047 , because it was closest to 7046, and tried to run the program and it just said it was scaning my device for an ungodly amount of time
so im looking for other methods
Click to expand...
Click to collapse
Uh oh! I think I see the problem here. The Conquest runs a QUALCOMM chip! All along, I've been running with the assumption that this Alcatel was running the MTK chipset. Everything I've described here is thus for naught! Those tools, like SPF and MTK Droid, only work with phones that use the MTK platform. They will not even recognize the Conquest.
My sincere apologies, but I don't even know what tools would even work with this sucker. Oh my God... I'm beside myself with embarrassment...I can't believe I made such a serious mistake.
Sent from my Nexus 7 using XDA Free mobile app

Root Alcatel conquest 7046t
Kingroot rooted mine

can the phone work with GSM sim card. i have one piece which is locked i guess coz am overseas and it doesn't work says invalid simcard

Mcrome1018 said:
Kingroot rooted mine
Click to expand...
Click to collapse
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app

CVAngelo said:
Did you get full root with KingRoot? Do your root apps actually work properly? Please confirm as others have reported that the root with KingRoot did not function properly or with all root apps.
Another question several people have is where to get the flashable stock firmware for this phone?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Mine all works, ad away, root browser etc no clue for firmware though

[Guide] [Patched Images] ROOT / UNROOT - CN or WW Firmware (28/08)

So, Now that we are through converting the firmware of the devices, Let's move to root access.
As usual, I'll keep it as noob friendly as possible. Your suggestions are always welcome to improve the thread.
Please note that Root level access voids your warranty, Opens your system for vulnerabilities, security exploits, Banking and financial apps stop working and even can cause system instability.
Only proceed if you're very clear about what you're doing and only if you really need it.
How it works out
* Root level access is when you need access to internal areas of the file system which you cannot access as an end user.
* By having root access you can mod many things like ad block on hosts level, bootanimations, ringtones, Titanium Backup and even a clean debloat.
* To obtain root level access on ROG II what's required is to extract the Boot Image (Boot.img) from the firmware package and patch it using magisk.
* Then the Patched Image file will be flashed to the device via Fastboot replacing the stock Boot image on the device
* Since the patched boot image is not official, You must unlock the bootloader before attempting any of the below steps. Failure to follow this step will brick your device.
* If you later change your mind, and you need to unroot - You can simply download the stock image and flash it via Fastboot.
* Boot image can be patched using the magisk manager app if you want to do it by your own, However for the rest of us I have already patched and uploaded the files on the second post
* Stock Boot images are 90MB+ while Patched boot images are around 50MB. This is absolutely normal for some unknown reason.
* As long as you're rooted a few apps that detect root like banking apps, GooglePay will not work. You can try to use Magisk Hide, but some of the apps are not that dumb anymore.
Prerequisites
* Bootloader Unlocked (This is a Must)
* PC with working Fastboot (Guide to Setup)
* Device Drivers Installed and Identified (Google ADB USB Drivers)
* Latest Magisk Manager APK from this thread.
Instructions
* Download the appropriate file from the second post depending on whether you need to root or unroot.
* Move the file to C: Drive, or a place where you can start a command prompt from (Command Prompt -> Hit Windows Key + R (Run Dialog Box) and Press enter)
* Connect your phone using the USB Port on the Side (Black Coloured one) - Connecting the bottom charging port will not work
* Type Fastboot devices to verify whether the device is connected or not. If connected - You will see "Fastboot <Device Serial Number>"
* To flash the Boot image of your choice execute the below command from the folder you have your downloaded boot image saved
Code:
fastboot flash boot boot.img
A message will show transferring file, Patching boot_A and it will come back to a prompt.
* After this step, you can type fastboot reboot to boot to system.
* It is not important to wipe / factory reset the device after a boot image flash.
Patched. Now What?
* If you just obtained root access, Now you can install Magisk Manager downloaded from This thread.
* Connect the device to internet and open Magisk Manager - It will download some necessary files and it will ask for a reboot. Follow the action and reboot the device.
* Upon Reboot, You can open Magisk Manager and check for Root access status. If it shows Installed - You're done
* You can try Magisk Hide to hide apps detecting root
* You can try a few new modules in the Magisk Downloads section (Since we do not have TWRP yet, Be careful on this step) - A wrong module can cause a bootloop.
Thank you and Good Luck!
Last but not the least;
Would you like to Help Me back?

File Downloads
* Only download the file you need, Do not download multiple files as they all have the same name.
If you want to Root your device - Download the Patched Boot Image,
If you already have root and needs to go back to - Download the Stock Boot Image
WW - INTERNATIONAL ROM USERS
Current Version - WW_ZS660KL_16.0622.1906.19_M3.13.33.20-ASUS_1.1.93
DOWNLOAD STOCK BOOT IMAGE - DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
-----------------------------------------------------------------------------------------------------
CN - Chinese Tencent Games ROM USERS
Current Version - CN_ZS660KL_16.0621.1906.24_M3.13.33.19-ASUS_1.1.102
DOWNLOAD STOCK BOOT IMAGE - DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
Thank you and Good Luck!
Would you like to Help Me back?

1. How do you un-do this process and go back to stock?
2. Has anyone done this yet? Please share your experiences.
Thank you

Swarai said:
1. How do you un-do this process and go back to stock?
2. Has anyone done this yet? Please share your experiences.
Thank you
Click to expand...
Click to collapse
1. Flashing Stock Boot Image takes you back to stock. Then relocking the boot-loader takes you back to factory state.

JazonX said:
File Downloads
* Only download the file you need, Do not download multiple files as they all have the same name.
If you want to Root your device - Download the Patched Boot Image,
If you already have root and needs to go back to - Download the Stock Boot Image
WW - INTERNATIONAL ROM USERS
Current Version - WW_ZS660KL_16.0622.1906.19_M3.13.33.20-ASUS_1.1.93
DOWNLOAD STOCK BOOT IMAGE - DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
-----------------------------------------------------------------------------------------------------
CN - Chinese Tencent Games ROM USERS
Current Version - CN_ZS660KL_16.0621.1906.24_M3.13.33.19-ASUS_1.1.102
DOWNLOAD STOCK BOOT IMAGE - DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
DOWNLOAD PATCHED (ROOTED) BOOT IMAGE - LINK 1 (MEGA)
Thank you and Good Luck!
Would you like to Help Me back?
Click to expand...
Click to collapse
apparently If you switch to the WW ROM, try to install root, wifi will be disabled. Is there a way around this? Thanks

Swarai said:
apparently If you switch to the WW ROM, try to install root, wifi will be disabled. Is there a way around this? Thanks
Click to expand...
Click to collapse
I have switched to WW, with Root.
No issues with WIFI here.

I am really lost. I got my ROG Phone II 3 days ago (Tencent Version - but already flashed to WW) but I can't find any solution to root my phone. I have no idea how to extract the boot.img although I have read hundreds of posts on how to do this. I was on IOS for the last 10 years so I'm trying to root for the first time in my life and I would really appreciate any help I could get with how to get the boot.img out of the firmware. Bootlocker is unlocked, fastboot works like a breeze and the PC shows the phone in fastboot mode, so at least no problem there. Thanks in advance, any information and help is more than welcome!

Arcadiz said:
I am really lost. I got my ROG Phone II 3 days ago (Tencent Version - but already flashed to WW) but I can't find any solution to root my phone. I have no idea how to extract the boot.img although I have read hundreds of posts on how to do this. I was on IOS for the last 10 years so I'm trying to root for the first time in my life and I would really appreciate any help I could get with how to get the boot.img out of the firmware. Bootlocker is unlocked, fastboot works like a breeze and the PC shows the phone in fastboot mode, so at least no problem there. Thanks in advance, any information and help is more than welcome!
Click to expand...
Click to collapse
I recommend just flashing the boot image in the post and installing magisk, then you won't have to worry about extract the boot image yourself

Alright, it seems I have gone blind as I really did not see the boot.img posted here. Shame on me!
Everything worked fine, phone is rooted now! Thank for the help and ofc for the great tutorial here!

haha soo... i unrooted cause I needed to factory reset. caused a bootloop where it would only boot into recovery. Anyone else experienced this? Tried to factory reset and it did nothing so now going to try to reflash WW rom
****EDIT***
I am an idiot. Read the OP. Download stock image and flash -.-

Hello there, can someone explain how to show navigation bar button (back and multi windows button) on CN os?

Quick question,
If I decide later to unroot does the device go back to normality like nothing ever happen? Or there is going to be always a recorded trace of the root activation? Do you get back warranty, banking apps and all that? thanks

issues when charging in the switch off mode
Hello
Thanks For the guide
I also faced a problem that bothered me after root everything perfect except this issue .
the issues when i switched off the rog phone 2 and plugged into the charging cable ; the charging logo appears and freezes “Stuck“ and I can’t switch on the phone But when I press the Volume_down_button+power_button , The phone is restarted and back to normal.
Any solution ?

Will this patched image work on new version? WW_ZS660KL_16.0622.1907.33_M3.13.33.26
because it's for WW_ZS660KL_16.0622.1906.19_M3.13.33.20-ASUS_1.1.93?

What are the benefits of rooting the ASUS ROG Phone 2?
Just to change the rom from CN to WW?
Wondering if there are any benefit in rooting the Global Edition model.
Sent from my iPad using Tapatalk

MCube74 said:
What are the benefits of rooting the ASUS ROG Phone 2?
Just to change the rom from CN to WW?
Wondering if there are any benefit in rooting the Global Edition model.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
There is only a benefit if you see root as a benefit (apps, super user access, capabilities etc...)

If you want to root with enable wifi add Line:mtts10550
Swarai said:
apparently If you switch to the WW ROM, try to install root, wifi will be disabled. Is there a way around this? Thanks
Click to expand...
Click to collapse
If you want to root with enable wifi add Line:mtts10550

Swarai said:
There is only a benefit if you see root as a benefit (apps, super user access, capabilities etc...)
Click to expand...
Click to collapse
Will root void the warranty?
Can we unroot easily?
Sent from my SM-G9750 using Tapatalk

mtts10550 said:
If you want to root with enable wifi add Line:mtts10550
Click to expand...
Click to collapse
Thanks, but I found out that I was flashing the wrong image.
---------- Post added at 10:41 AM ---------- Previous post was at 10:28 AM ----------
MCube74 said:
Will root void the warranty?
Can we unroot easily?
Click to expand...
Click to collapse
1. Yes
2. Yes
1. Reset the entire phone
2. flash stock stock image
3. Then re-lock bootloader
4. Instructions in this link -
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042

MCube74 said:
Will root void the warranty?
Can we unroot easily?
Click to expand...
Click to collapse
-If you root, your warranty will be void!
-Can you root and unroot without losing warranty?, It depends!. The service center can detect easly if you have flashed a raw rom or unlocked the bootloader, but it will depend on the service center if they would let it slide or not depending on the type of damage. They can overlook it if the damage is simply software but if it's more than that they can prove you or someone has altered the phone software.
The logic behind my reasoning is simple, currently flashing the raw rom of the phone stops OTA updates meaning after flashing the raw rom your device doesn't go back to the way it was intended to be or the way it should behave, which implicates that the system has been altered.

Samsung Galaxy Tab Pro 10.1 (SM-T525) TWRP installation Error

Problem: Unable to install TWRP via ODIN. I try to flash the device with the twrp-3.1.1-0-picassowifi.img.tar using ODIN, I get the following errors during the boot recovery step Home+VolUP+Power:
Could not do normal boot.
ODIN Mode
Product name: SM-T525
Current binary: Custom
System status: Custom
Knox Kernel Lock: 0x0
Knox warranty VOID: 0x1
Qualcomm Secureboot: Enabled (CSB)
AP SWREV: S1, T1, R1, A1, P1
Write protection: Enable
UDC Start
I am able to reinstall KitKat back to its original state using ODIN each time which helps alot.
The tablet was in the following state prior to the TWRP installation:
I did a factory reset back to original Kitkat version 4.4.2
Samsung account: No
Google account: Yes
Installation Preparation Steps
Downloaded following files:
LineageOS 14.1,
open_gapps-arm-7.1-nano-20201223
ODIN v3.14.4
Samsung USB Drivers v1.7.31.0
Auto-Root-picassolte-picassoltexx-smt525
twrp-3.1.1-0-picassowifi.img.tar
Installation Steps:
Tested if recovery mode is working prior to installing twrp: Done Successful
Installed USB drivers on your PC
USB Debugging was enabled on device by pressing build number 7 times in settings
Developer options: Activated USB Debugging
Disabled bootloader: not done (not sure how to do it and if it is required)
Rooted device via ODIN: Done successfully (Auto Reboot and F. Reset Time flags checked)
Disabled KNOX via SuperSU
Tested if recovery mode is still working after root: Done Successful
Installed TWRP image via ODIN: Status PASS (Auto Reboot flag unchecked, F. Reset Time flag checked)
Booted into TWRP Recovery using HOME+ Vol UP + Power button
The last step is where the error occurs and TWRP recovery mode did not start.
I tried multiple versions of TWRP, but all attempts failed.
I installed TWRP via play store on the tablet and selected the .img file for my device via the TWRP tool. Although the tool was able to flash the device (stated that the flash was successful within the tool), when I try to enter device recovery mode, I get the same error: Could not do normal boot.
Any idea what could be wrong? Am I missing a step, permission issue?
I would appreciate any hint
thx
Sal

Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.

bmwdroid said:
Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.
Click to expand...
Click to collapse
There are 2 types of T525, wifi and lte. I have the wifi version.

Sal60 said:
There are 2 types of T525, wifi and lte. I have the wifi version.
Click to expand...
Click to collapse
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?

bmwdroid said:
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?
Click to expand...
Click to collapse
Thanks for the help. Before I reached out to you, I tried my best to gather all the info to upgrade to LineageOS. Rooting the device was one of the steps. I got the file for t525. I did not think about wifi or LTE. I see now that it makes a big difference.....thx. I'm rather new to the rooting and upgrading a device approach.
Strange, I doubled checked the package. It doesn't say anywhere about LTE - only wifi. But I checked the imei on imei.info and noticed that it is a LTE model. I bought the tab in 2014 and I guess I bought the lte model. This explains alot.
I will try the lte version of twrp.
thx again

I tried the lte version of twrp and I was able to enter into recovery mode. Thanks for the excellent tip.
I guess I need to do more homework on twrp and the whole process. I also got lucky on using the right root file. Because I almost made a huge mistake with rooting, I think I need to take a step back and do more research. I want to make sure that I have a complete image of my tablet just in case I take a wrong turn. I believe twrp is the right tool to do that. Any suggestions on the steps which I need to do?
Initially when I first started to gather all the info and dowloaded the files, I also downloaded lineage-14.1-20201218-UNOFFICIAL-n2awifi.zip. It appears that this file is also for the wifi model. Is there a difference between wifi and lte for lineageos 14.1?

@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.

bmwdroid said:
@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.
Click to expand...
Click to collapse
Awsome, I backed up everything. I will need to do more research on the right ROM. Using the wifi version I downloaded of the Samsung Galaxy Tab Pro 10.1 is probably not the best way to go.
I see that LineageOS.org does not support my tab as of now and CyanogenMod no longer exist. Do you know of any other projects which might support my tablet?

@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.

bmwdroid said:
@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.
Click to expand...
Click to collapse
Thanks anyway

Sal60 said:
Thanks anyway
Click to expand...
Click to collapse
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button

bmwdroid said:
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button
Click to expand...
Click to collapse
@bmwdroid: thanks for the link. I will review the url. I completely understand the risk part. I rarely use my very expensive tab anymore because it is so old and more or less useless. Most apps do not work anymore. Samsung stopped updating the tab shortly after it was released.
Sorry about not hitting the like button.
I will update the post with the results after I do some research on the file.
Thanks.

@Sal60 I condemn Samsung for their update strategy as well.
That's why I will never ever again by a new device from them.
All my stuff is older than four years and on custom ROMs either on Nougat or even Q.
I bought them only after searching here for active devolopers.

@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com

bmwdroid said:
@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Click to expand...
Click to collapse
@bmwdroid I just seen this newly created ROM as well...thx. I checked both URLs. It seems a little complex. My only concern is understanding the technical side of the installations. I guess I have my work cut out for me.