I need some help.
I'm trying to get a 7.1.2 build of Android running on my SM-G530T. (Preferrably, the most stable and functional build that currently exists.) So here's what I've done so far:
I unlocked the bootloader, I think?
Rooted the phone using CF-Auto-Root
Installed the TWRP official app.
Put the fortuna3g custom recovery on it, using the TWRP app
I used the TWRP app to boot into recovery mode, and that's when my problems started.
Sometimes it bootloops, sometimes it gets to the recovery page. If it gets to the recovery page, there's no touch response. I can still control the phone via CMD in windows. Any suggestions?
-Bludude4
this forums not letting me post links and its pissing me off. how do i post videos?
Doesn't the T model use the gprimelte recovery file rather than fortuna3g? I kept coming across the fortuna3g while looking for the twrp .tar file for the grandprime 530T. I used this link to flash the twrp recovery with Odin and had no issues.
dl dot twrp dot me slash gprimelte
Use Odin to flash TWRP from the official website. "dl <dot> twrp <dot> me <slash> gprimelte"Your device's codename is "gprimelte" The versions 530T, 530T1 and 530W have it too. I encountered no issues whatsoever. My device is a 530W.
1. Put phone to download mode (power+home+vol.down) then Volume up to confirm
2. Open odin then connect your phone to your computer. Odin should output an "added!" message.
3. Add the twrp .tar file to AP slot then click start.
4. Disconnect phone from PC after the process is done. It should reboot automatically.
Hope this helps!
droidity said:
Use Odin to flash TWRP from the official website. "dl <dot> twrp <dot> me <slash> gprimelte"Your device's codename is "gprimelte" The versions 530T, 530T1 and 530W have it too. I encountered no issues whatsoever. My device is a 530W.
1. Put phone to download mode (power+home+vol.down) then Volume up to confirm
2. Open odin then connect your phone to your computer. Odin should output an "added!" message.
3. Add the twrp .tar file to AP slot then click start.
4. Disconnect phone from PC after the process is done. It should reboot automatically.
Hope this helps!
Click to expand...
Click to collapse
Yeah, I was toying with the auto-selector in TWRP and it kept pointing me to the fortuna3g, and i eventually decided to use that over the gprimelte one, after being torn over which one to use. I guess I should've posted a question asking that first before I tried to flash. So I just have to repeat the procedure using gprimelte?
yes, using the gprimelte worked on my 530T
NECRO:
Haha, put the phone on the shelf for a year and 9 months, just spent 5 hours trying to figure out how to get my buddy back into his J2 core after he forgot the new unlock password he set on it. After getting a little frustrated at not being able to find a custom recovery for it by myself, I thought to myself "I wonder if I can take another crack at getting my Grand Prime working again." So I installed the latest version of Odin on my PC, put the Grand Prime in download mode, and slapped the gprimelte TWRP on there, it was booted in 20 under 20 seconds. XD
Now I just need to figure out how to get my friend's lock screen password off of his phone without losing his data...
Related
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.
just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method
Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.
^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!
Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.
this is my second time to try rooting my phone after i failed and gave up a year ago.
i have got itchy fingers for a new phone but nothing is grabbing me, so i'd like to try and root this and use it for longer.
i have tried various methods with no luck.
my phone is a note 4, bought from the three network in ireland in may 2015 and is unlocked by three.
model number - SM-N910F
android version - 6.0.1
security patch level - 1 march 2017
baseband version - N910FXXS1DQA2
kernel version - 3.10.40-9117724 [email protected] #1
build number - MMB29M.N910FXXS1DQC6
i apologise if i am missing a thread with my answer....and will be very grateful for any help.
I hope this helps:
https://forum.xda-developers.com/note-4/general/root-note-4-sm-n910c-t2977948
thanks.
following this - http://rootmygalaxy.net/install-twrp-root-samsung-galaxy-note-4-android-6-0-1-marshmallow/
stuck on...after flashing TWRP recovery using ODIN, and rebooting using vol up, power and home...it just boots into the old recovery every time
got it. sorted now
dougm1970 said:
thanks.
following this - http://rootmygalaxy.net/install-twrp-root-samsung-galaxy-note-4-android-6-0-1-marshmallow/
stuck on...after flashing TWRP recovery using ODIN, and rebooting using vol up, power and home...it just boots into the old recovery every time
Click to expand...
Click to collapse
When you flash twrp. Untick auto reboot. Let it flash, till it is complete. Unplug. Pull battery. Put back in. Then immediately reboot into recovery by holding pwr+vol up+home
Plus use the new Twrp
https://twrp.me/devices/samsunggalaxynote4qualcomm.html
Where are the non add files to download!!
I can't seem to access the correct root, unlocker, and recovery file needed to root my Samsung
aaron74 said:
When you flash twrp. Untick auto reboot. Let it flash, till it is complete. Unplug. Pull battery. Put back in. Then immediately reboot into recovery by holding pwr+vol up+home
Plus use the new Twrp
https://twrp.me/devices/samsunggalaxynote4qualcomm.html
Click to expand...
Click to collapse
Kaybabe4 said:
I can't seem to access the correct root, unlocker, and recovery file needed to root my Samsung
Click to expand...
Click to collapse
I don't understand "non add files"
How to root:
Download Odin here!
Download TWRP here for Note4 model trlte!
Download SuperSU zip files here!
Use Pc to install Odin and use Odin to install TWRP.
Then copy Supersu to phones SD card. And use TWRP to install it.
All done!
Use Google or search XDA. There are multiple links that show how to use with more detail.
This is my post basically backing up files for the Galaxy Note 10.1 GT-N8013 "p4noterf" so we don't lose them later.
Restore factory fimeware
If you have crashed out your Galaxy Note 10.1 GT-N8013 and need to restore it try the following
1. First make sure you can enter download mode: Power + Vol. Down and then Vol. Up to continue (Google if unclear)
2. Download the latest factory firmware (N8013UEUCOI1_N8013XARCOI1_XAR) here:
https://mega.nz/#F!UdFwWLyL!006TWe3MPyK-9yeAJlH7AQ
3. We need it unzipped so unzip it.
4. Download Odin such as Odin 3.13.1 here: https://mega.nz/#!wZ9H1ArK!TLiWdY9YUKNzVpnVXuqzJz4rtA86XysGlmFfdWl5LvE
5. Unzip Odin and click it to start it up. It's the file named Odin3 v3.13.1 (or Odin3 v3.13.1.exe)
6. With your tablet in download mode plug it into your computer, it should show up in Odin
(If it won't connect to PC try another USB port or install the drivers: https://mega.nz/#!lFMVDbSC!j_sMAjcXneHSPkqgOysc382dqVzNB82QP5T_Huet8YA )
7. Load the unzipped firmware into the AP slot and press start
Install CWM Recovery and Root:
Follow the second root method here:
https://forum.xda-developers.com/showthread.php?t=1831152
---> which leads to here: http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
Backup of files from this method: https://mega.nz/#F!5c8lHSLR!540QzdGl4z1kknFNYlmNDg
Install TWRP
1. Through Google Play store Install TWRP app and either select your device, download files and flash firmware in the app or continue at step 2 after installing.
2. You can direct download latest versoin to your sdcard (Download folder will do): https://dl.twrp.me/n801x/
Backup of latest at the time of this writing was ===> https://mega.nz/#F!EYlXCQhB!fTx37McGKNCWXkumldtHLA
3. Inside the TWRP app select the file you downloaded
4. Flash firmware
You can now use TWRP to install a custom rom if you wish, I used CM 13.1
https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
Note:
I had to use this gapps to get my keyboard to work during setup!!!
https://mega.nz/#!Id1VXK7T!3VfvcdmyDzofaAmEBlhpgArxBmtJVW43wq55bEMEPgw
1. On the WiFi screen in the bottom corner there's a little keyboard symbol, touch it to open option.
2. Move slider to On position
Thanks, was looking for just this thing
Yas
Thank you for this! Made sure to save those files while I still can. Was able to restore, root and install Lineage OS 14.1 on this old Note 10.1 I inherited. Truly amazing to jump from Jellybean straight to Nougat when Samsung couldn't have cared less to update this tablet.
Cm 14.1 sidesync 4.7 on samsung gt-n8013 not working
Does anyone have any luck getting the Sidesync to work with Wifi Direct from the Samsung Note 10.1 Gt-N8013 Android 7.1 to the Android 8.1 Samsung S8 Phone. Trying to Get the Mirror Feature to Remote Control the Phone on the Tablet Screen
Can install sidesync and click to run .. app screen opens but than crashes with error message about not being able to mirror. Seems something not communicating with Wifi or hardware on tablet incompadability..??
Firmware V1.0
Your post has nothing to do with this topic .
see your identical post moved to Q&A
When I download the firmware using Odin, where does it get saved? I can't find the file with TWRP when I am ready to flash the firmware.
Odin does not download firmware.
You download firmware .
Odin is an installer for stock firmware tar files .
TWRP installs custom rom zips .
BrettApple said:
Thank you for this! Made sure to save those files while I still can. Was able to restore, root and install Lineage OS 14.1 on this old Note 10.1 I inherited. Truly amazing to jump from Jellybean straight to Nougat when Samsung couldn't have cared less to update this tablet.
Click to expand...
Click to collapse
Not sure if you'll see this but how did this go? I have the n8013 (2013) model and would really like to update it past Jelly Bean. My biggest concern is the S Pen and S Notes still working as well as they do now. Is yours still up and running? Thanks!
SPen etc dont really work on non Samsung firmware .
Suggest a search for alternative spen on play store etc .
Install CWM Recovery and Root:
Follow the second root method here:
https://forum.xda-developers.com/showthread.php?t=1831152
---> which leads to here: http://rootgalaxynote.com/galaxy-no...t-galaxy-note-10-1-easiest-methodcwmmethod-2/
Backup of files from this method: https://mega.nz/#F!5c8lHSLR!540QzdGl4z1kknFNYlmNDg
Click to expand...
Click to collapse
I'm trying to fix a bricked Note 10.1 (stuck on a bootloop and can't even access Recovery Mode, TeamWin logo appears and then tablet resets) but everything you linked there is already gone.
marianito10 said:
I'm trying to fix a bricked Note 10.1 (stuck on a bootloop and can't even access Recovery Mode, TeamWin logo appears and then tablet resets) but everything you linked there is already gone.
Click to expand...
Click to collapse
I managed to solve same problem by flashing TWRP recovery using heimdall
How to flash recovery using Linux and Heimdall? (SOLVED)
Hi. Decided to try to give some new life to this old thing. But when I install the TWRP thing and shut it down it immediately boots up and overwrites the TWRT. I know the instructions says to let go of the buttons "very fast", but I've been...
forum.xda-developers.com
michael.pihlblad said:
I managed to solve same problem by flashing TWRP recovery using heimdall
How to flash recovery using Linux and Heimdall? (SOLVED)
Hi. Decided to try to give some new life to this old thing. But when I install the TWRP thing and shut it down it immediately boots up and overwrites the TWRT. I know the instructions says to let go of the buttons "very fast", but I've been...
forum.xda-developers.com
Click to expand...
Click to collapse
Ok, I extracted the PIT file from my tablet with Heimdall (like it was suggested in the readme), then I flashed TWRP Recovery and same result... Bootloop, and when trying to access Recovery Mode the TeamWin logo shows up for a second and the tablet reboots. Also tried flashing a stock rom, PhilZ Touch recovery, and still both Odin and Heimdall always say it was "succesful" but the result is always the same, nothing changes.
It's just weird to me how the TeamWin logo still shows up even after I flash the stock rom. I read somewhere that the oldest stock rom for my device might work, but I can't find a link anywhere for it except here, where it's Premium Only...
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.
there are some instructions how to install twrp or lineage on nnthe samsung galaxy a20e. it took me a while to manage it, for one part because it seems sometime i did not do everything exactly like it was described (old fault of mine...) sometimes i found some explication in another instruction.
this is why i post my experiences, to encourage those who also struggle with problems, don't hesitate, sometimes it only takes a bit longer, but also because some things i still don't understand, maybe somebody can explain me what happened..
naturally, firsty of all i first had to install twrp. so i searched for instructions and found some, including liks to download the twrp.tar for my model. some of them i was able to flash by odin, but when i then restarted the phone it only showed a black screen with some pink in the middle, with some fantasy i could read a slight samsung or samsung a20 in it. this happened when i tried to restart in recovery to flas disable-dm-verity, also when i tried to restart direct to system. with all the attempts i got very experienced in flashin back stock rom...
then i found a working recover after restart to recovery i got my twrp screen and was able to flash the no-dm-verity or magisk.
so next i tried to flash the lineage (unofficial lineage 17.zip) but always got the message invalid zip format. tried to unzip and zip again but no way. so i thought i might get lucky with adb sideload, entered the twrp advanced and clicked adb sideload, the screen told me starting adb sideload but the phone could not be detected by the computer. the computer detected it when switched on or in fastboot, so it seems the sideload did not really start.
so i searched the interenet for roms because i really wanted to get rid of google and a million of apps in the stock that i don't need. i found the links to andyyans gsi and several other zips.
as i was not used to the gsi installation i thought i better stick on what i know and tried to install another zip. but most of the time i got the invalid zip message or the zip is for another phone although i downloaded it for the a20e. but then twrp accepted the crdroid.zip (eureka) i downloaded, i was very happy, after the instalation was finished i restarted the phone and the screen went black, turned off and it seemed not pressing to download, to recovery or to start changed anything. i also tried with pressing vol up, vol down and conecting with computer but also no downloadmode started. so i pressed very long always several buttons and after a while the phone vibrated by pressing long vol down and power, but no screen. after it vibrated sometimes like this i turned to vol up and power, it vibrated again and finally twrp started. although the phopne was fully charged when i started the process, it now had only 8% battery.
so i charged the phone again, flashed the stock rom and twrp to try again to find a solution. at this time i also found an instruction that explained why after flashing twrp the system can't recognize the folders (downloads, music... ) and only gives them combinations of letters and ciffers, i have to decrypt it in twrp, wipe, format data, yes and this problem is solved. i don't know it happens always and who made the instructions to flash twrp thought this is common knowledge but in the first innstructions i read it was not mentioned.
i tried again to flash zips and now got a funny eroor message from twrp, unable to zip, this zip is for a20 but this phone is a a10. i tried another zip, the installation started and in the text i could see that it was for a10... so somehow twrp was sure to live on na a10, how could this be??? i thought maybe the twrp was for the a10 (it was a 3.4.x), so i again downloaded a tar directly from the page of twrp for the a20. but when flashed this twrp (3.5.x) and tried to restart to recovery (or to system) the phone was still in downloadmode and refused the custom rom. i had to flash back to stock, then flash again the twrp3.4 that thought my device is a a10, then i could flash the new twrp3.5 i was sure it was from the original site and for my device. i don't know the 3.4 was patched, i got the downloadlink from one how-to-site, but i did not read anything that it was patched...
but after testing all the zips that did not work, and also with the new twrp i was not able to sideload i decided it is time to learn how to handle the xz. so i extracted first the lineage 18, installed it by clicking install image (after wiping) but again the phone turned black and i had to press a while to get twrp restarted and the battery again was nearly down.
the same process worked with the lineage 17, so this is what is now innstalled. both where the correct ab versions, i checked before with treble info what version i need.
so, can anybody explain me
-what happened with my battery when the phone turned to apparently death?
-why could twrp think my phone is a a10, would a twrp for a10 work on my phone?
-is it possible that the sideload feature does not work on this phone?
¡¡¡and many thanks to all those who upload roms and instructions so people like me can make their phones a bit more like they want them!!!
The first time I flashed my A20e (SM-A202F) had the same problems with finding the right TWRP. I cannot answer your questions, but I can tell you what I do.
Beforhand: unloock the bootloader. Upgrade to the latest Samsung firmware. Download AndyYan's 18.1 LineageOS GSI arm64_bvS. Thought arm64_bvS-vndklite can work as well, I found that bvS has less bugs.
After installing the Samsung drivers and the adb stuff on a PC with Windows, I install Odin and flash with Odin the attached TWRP (AP), while phone is in Download mode.
I then go to recovery (TWRP) and if the folders and files are encrypted, I format, then yes. I wipe 4 things: dalvik, catche, system and data.
I then move the GSI image file inside the zip (not the zip) by drag and drop on my PC. Then in TWRP I click install, select image, not zip, select system and flash. Then I reboot to system.
I never had any problems with this installation process. The bvS has a bug with the Lineage music app, but simply install a local music app, such as Musicolet or AIMP from the Aurora Store (from F-droid).
On the camera side I haven't seen any app that significantly improves photo quality. My recommendation would be FreeDcam from F-droid. Use it on special occasions, as it tends to heat the phone.