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.
Related
IT CAN BE DONE
Here's how I did it. (And don't blame me if you brick the phone, etc., etc....)
PLEASE DO NOT ATTEMPT IF YOU DO NOT UNDERSTAND THESE NOTES! Read them thoroughly!
1. Install stock NC2 (Instructions are all over)
2. Root with towelroot.
3. Install latest SU from the play store and update binary (you know the drill, right?)
4. See Chainfire's site here. http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 Get FlashFire
5. Place the AT&T stock lollipop .tar file on your SD card. It is available in the note 3 forum.
6. Run FlashFire. Once it has done its thing, click on the + sign.
7. Click on flash firmware package and navigate to the stock .tar file.
8. FlashFire will analyze the file and you will see a screen with partitions checked. These are the partitions that FlashFire can write (AND ROOT)
9. Click the download sign at the top on the red bar.
10. Click on the check mark to Create New Archive (FlashFire will create a .tar.md5 file take note of where it is saved and COPY TO YOUR PC BEFORE you run FlashFire! You will need it!
11. Next you will see the screen with ACTIONS on a red bar. Scroll to the bottom and touch FLASH
12. FlashFire will now write the partitions that are checked. When it reboots the phone, IMMEDIATELY hold the volume down, home, and power button to enter download.
13. Go to your PC where you copied the archive (that .tar.md5 fike). Right click on the file and choose rename. Remove the .md5 from the file name or odin will likely give you an error.
14. Open odin and connect your phone. Place the .tar archive FlashFire created in the AP section and flash. It will write the partitions that FlashFire could not.
15. Reboot and enjoy rooted lollipop on your phone.
Hate that I still have to wipe data to get it to boot at all, but a minor gripe I suppose. Just hate having to reinstall my apps and set them back up. Thanks for sharing this, been waiting for something like this for a while!
Yeah but if you're already on rooted nc2, why not just flash the stock rooted lollipop rom?
Doesn't that process require using SafeStrap, where this process does not?
netracerx said:
Doesn't that process require using SafeStrap, where this process does not?
Click to expand...
Click to collapse
You can use flashfire...
Plus why go through all this hassle to reach the same result?
That's absolutely true. but think it is a matter of preference. I had some issues with Safestrap, but were it still supported for lollipop, I would probably still be there. I also had a soft brick when I attempted to do a backup, which supposedly still works by booting from the power screen. SO for those who would prefer a cleaner option, this might suit them better. Flashfire also has the potential to install other custom roms. I am still looking at that option.
swapavi said:
You can use flashfire...
Plus why go through all this hassle to reach the same result?
Click to expand...
Click to collapse
this is the first post i've seen for the N900A that advised using Flashfire, all other posts required using Safestrap (which i personally did not like the idea of using just because it wasn't actually updating the OS on the phone, but essentially tricking the phone into loading a different set of files much like multi-booting). if it were possible to use Flashfire with the rooted lollipop roms, i'm surprised none of the thread OPs updated their posts to reflect that.
FlashFire has only been out since April. It is Chainfire's successor for Mobile Odin. It takes a while for all of the phones to be tested. There are a couple of other users that have tested it. Just search the FlashFire forum for Note 3 and you can read the comments. At least one other has used it on the AT&T variant.
reboot into download mode
I just finished your method successfully. Thank you. I would like to add that there was an option to reboot into download mode after flashing with FlashFire. I didn't have to worry
about immediately holding vol. down . I think the version of FlashFire I used is a little newer. Anyway thanks again!
I will keep trying
Hi all,
I was able to go through all the steps but keep getting stuck on step 14. Odin fails at the very very end and never finishes. I have done the whole process 3 times over.
Questions:
1. When picking the .tar in step 7, I am selecting the largest file of lollipop. I believe it is an AP file about 2.2 Gigabytes. This is the right one to select in step 7??
2. On step 10 when it ask you to Create New Archive, do i check ALL the boxes?? Nothing is checked by default when i press the download sign in step 9.
Other than these two things, everything else seems to work nicely. I did also notice that when Flash Fire runs and writes the system, wipe is set to OFF. I figured it was like that on purpose but just saying.
Thanks in advance,
John :good:
Sorry for the delay. I have moved on to the S6, so been busy with it.
For step 7, choose whichever ROM you wish to use. The one you have should be fine.
With regards to the second question, Flashfire should check the files in step 8 that are needed for the archive. Are you using a stock rom for step 7? If not, it might be able to flash without a separate tar file.
Ok,
Yes it was stock and thanks for the tip i will give this a shot as soon as i can and see how it goes.
So this will work to Root the Note III on Lollipop?
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
fitzly said:
What exactly does Flashfire do in this case? Is it unlocking the bootlader, allowing for flashing a custom rom? Or is it only rooting Lollipop? I was looking at safestrap for running a custom rom on the AT&T Note 3, and someone mentioned in another thread that Flashfire was a better option for doing so, with no need for the multi-boot workaround. Thanks to anyone who can straighten me out on this, and if Flashfire doesn't allow for flashing a custom rom on the AT&T note 3, is there anything else out there that does?
I'm under the impression that the AT&T note 3 has a locked bootloader, which is my point of confusion.
Click to expand...
Click to collapse
Great Guide and find.
Flashfire has the power to bypass the security that would provent Odin from installing , for example a custom kernel, so be carefull with Flashfire, it installed a custom kernel on my phone and flagged Knox to a 1
Followed the steps in the 1st post...worked flawless! May I add its good to clear cache & delvic cache as well
Sent from my SAMSUNG-SM-N900A using Tapatalk
Excellent. I don't like Safestrap, so this was perfect... I didn't have to wipe my phone, and everything went perfectly the first time. One note, I did have to put my phone in Download Mode (as stated in the OP) after the reboot from Flashfire. Thanks so much to all who worked on this!
Update: The OC2 update happened pretty much immediately after I booted. The OTA update actually managed to complete, and I still have root.
I am currently on 4.3 MI9 version..
i rooted it with chainfire method root de la vega.
Now can i flash NC2 with odin and continue the thing ?
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Chocu1a said:
Can someone point me to the stock lollipop tar? I cannot for the life of me find it in any of these forums. Please & thank you.
Click to expand...
Click to collapse
look here, if you still have issues let me know
http://forum.xda-developers.com/showthread.php?t=2703006
yesterday i successfully rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
glennnall said:
yesterday i successfully
rooted my Tab 4 using CF Root matissewifi-matissewifizs-smt530 - then spent the entire remainder of the day trying to understand the difference between 'recovery mode' and 'ROM' and 'recovery' 'img', 'tar', 'zip' and 'nandroid' and backup and TWRP the app and TWRP the recovery and Rom Manager and Clockworkmod and why the apps don't want to download the roms I want and why my Tab 4 10.1 isn't listed in the TWRP devices so...
i attempted to install a recovery in about 50 different ways and got my Tab stuck in reboot loop about 50 times -
WHEN I DID get what i thought was TWRP (or GooIm-whatever) to download the correct recovery and reboot into the proper recovery mode i ALWAYS saw the usual recovery options: Reboot, something using ADP, something using external, Factory Reset, wipe cache, something using cache.
nothing related to TWRP or ANY custom recovery.
I'm not quite sure that all of the directions i can ever find about how to do this are written on the assumption that the user knows half of what's going on here. there are some of us who do NOT know what "Flash" means, and other terminology.
******* Can someone please tell me what i need to do to install ANY custom recovery so that I CAN create a Nandroid Backup?
I'm trying to install the new Magazine UX theme or whatever it is. (apparently this replaces the TouchWiz theme? Mine came with TouchWiz?)
Click to expand...
Click to collapse
Follow these instructions and you will have a custom recovery installed on your SM-T530. Yes I know the title of the post is root your tablet, but this is accomplished by installing a custom recovery. Nobody here is going to take much pity on you for not understanding the terminology, we all took it upon ourselves to learn it at some point or another, it just kind of comes with the territory. XDA University can be very helpful if you feel lost or overwhelmed
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
glennnall said:
thanks -
2 of the problems i encountered yesterday were:
Run Odin. Disable the "Auto-Reboot" and "Re-Partition" options... Auto Reboot and F-Reset options were grayed-out, unchangeable.
Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file... there IS no AP button, just the PDA button. everything else is grayed-out (i ran it as Admin)
not optimum conditions for new people who are TRYING to learn how this stuff works. (I'm a Web programmer and not incapable of grasping Android technology, assuming i'm reading from the correct 'literature'.) The link looks promising - but these hurdles need to be crossed first.
yesterday, CF Auto Root installed SuperSU already, so i don't know which of the following promising instructions to follow... can i just run these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
Click to expand...
Click to collapse
Yes this will install safely over your current configuration. PDA button is the correct option, on newer versions of Odin it is renamed AP, sorry. You should be using at least Odin 3.07
Since you're already rooted, you shouldn't have to worry about the auto reboot, but do install that newer version of superSU at some point, it's designed for lollipop, works better than old versions.
can I run this on top of my rooted Tab, or do i need to "unroot" it?
yesterday, CF Auto Root installed SuperSU already, so i don't know which of these following instructions to follow... can i just run all of these instructions on top of my rooted device and get the newer SuperSu, recovery etc?
sorry, reposted in my impatience. thanks for the help.
ok, great - worked as advertised.
SuperSU updated normal, reboot, now i'm sitting on "Samsung" ... hmmm...
Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?
Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp
AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes
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...
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.