Database Users

How to Root Tab (P7500) After ICS 4.0.4 Update

Flash recovery with odin
Copy SU file to Root of device and flash from recovery
Files and method found at link below;
http://galaxytabhacks.com/galaxy-tab-10-1-root/how-to-root-ics-on-galaxy-tab-10-1/

Hi guys,
I have a problem.
I used this guide as well as others, and always appeared to me to superuser icon but root checker and other apk me reported that the tablet does not have root.
sorry for my english I'm slovak

winco206 said:
Hi guys,
I have a problem.
I used this guide as well as others, and always appeared to me to superuser icon but root checker and other apk me reported that the tablet does not have root.
sorry for my english I'm slovak
Click to expand...
Click to collapse
Nazdar
Actually I have the same issue as winco, I had root before upgrade to ICS.
I used this guide, everything looked fine. I have installed CWM, I have Superuser app, but tablet does not seem to be rooted. Even when I press in CWM. "fix root" it does not help at all.
Does anyone know if there is an easy way to root it without connecting the PC method?
Many thanks

Hi all, some time has passed, does anyone know? To help 2 noobs. Many thanks
Sent from my GT-P7500 using Tapatalk HD

doktorko said:
Hi all, some time has passed, does anyone know? To help 2 noobs. Many thanks
Sent from my GT-P7500 using Tapatalk HD
Click to expand...
Click to collapse
Make it 3............same problem here

doktorko said:
Nazdar
Actually I have the same issue as winco, I had root before upgrade to ICS.
I used this guide, everything looked fine. I have installed CWM, I have Superuser app, but tablet does not seem to be rooted. Even when I press in CWM. "fix root" it does not help at all.
Does anyone know if there is an easy way to root it without connecting the PC method?
Many thanks
Click to expand...
Click to collapse
If you have CWM installed, then you need to get the superuser.zip onto the internal sdcard partition. You can download it using the tablet's browser, then use an file manager application to copy the downloaded zip into /sdcard.
Then boot into recovery and install it with "install zip from sdcard".

Defaults browser of Android 4.0.4 stock rom errors
when i turn internet in stock rom 4.0.4. it not work and put out.
who can explain to help me?

u know how to root SGT WIFI only with update 4.0.4 ?

root twrp not working
I'm a newbee with android so please appologize for stupid remakrs or questions.
I wanted to root my Samsung Galaxy Tab 10.1 with android 4.04 (Icecream I think) because I can't use my WD-elements external 2TB disk, not even with an external power supply. The disk is not recognized by the tablet, I only get a message 'High power device connected".
After some googling I saw that the S3C driver is missing. It seems that the tablet has to be rooted to be able to innstall such a driver.
I followed instructions from this thread, used Odin en then tried to reset my gt_p7500 by pressing start and volume down and then volume up.
The TWRP windows shows up but the screen is running like hell. So I cannot reach twrp to backup my old image and install the new image.
So my tablet is still not rooted.
Pleas advise me what to do.

Working method for me
scherpbierje said:
I'm a newbee with android so please appologize for stupid remakrs or questions.
I wanted to root my Samsung Galaxy Tab 10.1 with android 4.04 (Icecream I think) because I can't use my WD-elements external 2TB disk, not even with an external power supply. The disk is not recognized by the tablet, I only get a message 'High power device connected".
After some googling I saw that the S3C driver is missing. It seems that the tablet has to be rooted to be able to innstall such a driver.
I followed instructions from this thread, used Odin en then tried to reset my gt_p7500 by pressing start and volume down and then volume up.
The TWRP windows shows up but the screen is running like hell. So I cannot reach twrp to backup my old image and install the new image.
So my tablet is still not rooted.
Pleas advise me what to do.
Click to expand...
Click to collapse
I'm new to this too. Will try to help as much as I can since I've been able to successfully flash new ROM, TWRP etc., The process is as follows:
1. I found that the only TWRP recovery + ODIN combo that worked for me was the one packaged in this thread. Booted my tab into Download mode -> flashed TWRP with the ODIN (both from the package in the mentioned thread) -> Rebooted into recovery TWRP.
1a. From TWRP -> Wipe -> Cache, Dalvik Cache, Data.
2. Did 'adb push <rom_image.zip> /sdcard' (without quotes. need to have Android SDK installed in your PC with version 1.0.29 or above. Reason for version is to have 'sideload' functionality which I'll show how to use later).
3. Did 'adb push <gapps.zip> /sdcard' (same notes as in above bullet).
4. Selected "Install" option in TWRP -> Selected rom_image.zip from /sdcard location -> swiped to flash/installed the ROM (I used this ROM and find it to be the best so far and suits my liking).
5. Installed gapps in the same process as above for ROM.
6. Rebooted system.
Additionally, you could download TWRP flashable .zip file of TWRP 2.6.3.0 in order to get 'adb sideload' functionality. I found this to be a savior for me many a time.
:highfive:
Let me know how it goes. all the best flashing...

twrp is the problem!
baystallion said:
I'm new to this too. Will try to help as much as I can since I've been able to successfully flash new ROM, TWRP etc., The process is as follows:
1. I found that the only TWRP recovery + ODIN combo that worked for me was the one packaged in this thread. Booted my tab into Download mode -> flashed TWRP with the ODIN (both from the package in the mentioned thread) -> Rebooted into recovery TWRP.
1a. From TWRP -> Wipe -> Cache, Dalvik Cache, Data.
2. Did 'adb push <rom_image.zip> /sdcard' (without quotes. need to have Android SDK installed in your PC with version 1.0.29 or above. Reason for version is to have 'sideload' functionality which I'll show how to use later).
3. Did 'adb push <gapps.zip> /sdcard' (same notes as in above bullet).
4. Selected "Install" option in TWRP -> Selected rom_image.zip from /sdcard location -> swiped to flash/installed the ROM (I used this ROM and find it to be the best so far and suits my liking).
5. Installed gapps in the same process as above for ROM.
6. Rebooted system.
Additionally, you could download TWRP flashable .zip file of TWRP 2.6.3.0 in order to get 'adb sideload' functionality. I found this to be a savior for me many a time.
:highfive:
Let me know how it goes. all the best flashing...
Click to expand...
Click to collapse
The problem lies within TWRP. As I wrote: TWRP shows up but the screen is scrolling like hell. So I am not able to reach TWRP to wipe or anything at all.
so still no root I am sorry to say.

scherpbierje said:
The problem lies within TWRP. As I wrote: TWRP shows up but the screen is scrolling like hell. So I am not able to reach TWRP to wipe or anything at all.
so still no root I am sorry to say.
Click to expand...
Click to collapse
Oh ok . The version I had mentioned in my reply did not help?

Root lollipop on AT&T Note 3 without Safestrap!

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

Root, recovery and custom rom setup for Galaxy S5 (SM-G900I)

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.

Rooted, Custom Rom a huge fail

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

CF-Auto-ROOT, Odin success but phone appears to be unrooted.

Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker and I am now receiving a security notice about unauthorised actions.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:

ElronVonSexbot said:
Forewarning, I'm super novice at phones but am pretty good with computers (can program and such).
I recently tried to root my phone using CF-Auto-Root, I used odin and all appeared to be a success, I unplugged the phone from the pc and it went through a black screen white writing and a red android logo and did a few other things.
once rebooted there was an unusual blue screen and my phone came up with a message saying something wasn't recognised and I had to wipe all data and reset to factory.
once all this was done, my phone is showing as unrooted by SuperSU and Root Checker.
I have since "installed"(please advise me of a better word) TWRP and used no-Verity-opt.... but when installing Magisk I get an Error 1
I am not sure where to go from here. Please help/advise or tell me my post is in the wrong spot.:good:
Click to expand...
Click to collapse
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.

jaannnis said:
ONLY WORKS WHEN YOU HAVE TWRP INSTALLED (which you obviously have):
Either you download a recovery flashable SuperSu from here or a recovery flashable Magisk from here directly to your device.
Than you just boot to recovery(hold down volume up, bixby and power buttons while turned off) go to "Install" in TWRP and search for the file you just downloaded (usually /sdcard/Downloads/ or something) just wait till the flash process is done and reboot.
Click to expand...
Click to collapse
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.

ElronVonSexbot said:
During the flash process using the flashable Magisk I get an error:
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/download/Magisk-v16.0.zip' "
This is where I'm stuck, I don't how how to solve this error.
it says above the error
! boot image patched by other programs ' Referring to CF-Auto-Root which didn't work
So I guess my question is how do I restore my stock boot image after using CF in order to flash Magisk instead.
Click to expand...
Click to collapse
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img

jaannnis said:
AFAIK you have two options now:
Flash stock TouchWiz (plenty of tutorials on the forum) and install twrp afterwards, then install Magisk via TWRP
Flash custom rom like Renovate ICE or any other from the forum directly via TWRP. I believe all of them are (at least have the option to) pre-rooted with either Magisk or SuperSu
As your SuperSu doesn't recognize your root you can't unroot with it and (someone please correct me if im wrong) not even a full wipe does unroot/does anything with boot.img
Click to expand...
Click to collapse
Thanks, I was going to custom ROM eventually anyway so I may as well bite the bullet, and Renovate ICE seems to be the best out there, thanks for the advice.
I think you are right, it was my thought that because I used CF-Auto-ROOT no backup of the original/stock Boot.img was ever created giving me no point of return. god knows what actually went wrong with the root. I shouldn't have been lazy and avoided the TWRP step in the first place.
Again, thanks for the help, I am Downloading Renovate ICE now, only 1.5 hours to go, yay Australian internet.