I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
AAANNNDDDYYY said:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.
I bought this in New Zealand from Spark. I assume it is locked?
Is the bootloader locked?
I couldnt find the matching build on Chainfire, Can this particular model be rooted?
Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.
I can't even find the original stock rom.
Is rooting not similar to jailbreaking in the way it is done?
My specs:
Model: SM-G920I
Android: 5.0.2
Build: LRX22G.G920IDVU1AOD1
Thank you in advance.
Click to expand...
Click to collapse
I have the SM-G920I and it's rooted.
Rooting the G920I is apparently not as straightforward as others but still possible.
I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.
Details when I get back from work, or some kind soul decides to help.
There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
AAANNNDDDYYY said:
Thanks, is it better to reset the s6 before rooting? For a clean root?
And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
Click to expand...
Click to collapse
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.
It is unlikely Spark firmwares have locked bootloaders.
So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.
Use the USB cable that come with your phone and make sure you have the drivers installed.
Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.
Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.
For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
AAANNNDDDYYY said:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.
This tutorial the way to go?
youtube.com/watch?v=BW5P8zqkFpY
Click to expand...
Click to collapse
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
AAANNNDDDYYY said:
Yes the G920I listed on Chainfires site is for the AOC6 build, but I am on the AOD1 build.
Another thing, should i factory reset before rooting?
Click to expand...
Click to collapse
Nah, don't bother. The process will retain all your settings and data too.
So just confirm that i can root my g920I with build AOD1 with this meathod?
---------- Post added at 05:45 PM ---------- Previous post was at 05:33 PM ----------
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So just confirm that i can root my g920I with build AOD1 with this meathod?
d0ce said:
What the chap did in that video was exactly what my original plan was to root and install TWRP. Where I got stuck is the TWRP recovery hung so I couldn't flash SuperSU. Good run down of the basics of flashing with Odin though.
What I did after the recovery got stuck was return to download mode and flash CF-Root again through Odin (same process as in the video). The one for the 920I didn't actually work (boot loop), the 920F CF-Root worked fine though. Probably has something to do with these CF-Roots having been build on a older firmware as you noted in your OP. Then, once you have root, you can flash a custom recovery (such as TWRP) through Flashify (available on Play Store).
It certainly can be confusing with all the trial and error reported in these forums, this is largely because the devices are new. The Devs' will iron out the bugs in due course making the process much simpler. You could wait a few weeks and check back, or grab yourself a stock Spark firmware and have a crack. Flashing this trough Odin will return you to stock provided you can get your phone to download mode. No responsibility from my end.
Another thing, you will lose OTA updates. You will find newer firmwares here as they get released, to update its as simple as flashing them through Odin.
Click to expand...
Click to collapse
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
s3ct0r said:
So were you able to install TWRP?
CF Root works for me with 920I version, but flashing TWRP forces it not to boot past the Samsung Logo.
Likewise with flashing a custom kernel also forces it not to boot past the Samsung Logo
Im on the C4 Australia build.. thinking about trying to flash a later 920I build to see if it'll help
Click to expand...
Click to collapse
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Kjc99 said:
Did someone figure this out? I have the Sm-920i and I get stuck at the Samsung splash screen after flashing twrp! So I have to Odin the cf-auto-root... I've tried flashify also... It won't work... Stuck @ Galaxy S6 screen what gives is it the SM-920I OR ME? I have had many Galaxy phones in the past but this one is pissing me off
Click to expand...
Click to collapse
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
s3ct0r said:
Yeah flash the New Zealand 1D firmware and TWRP will work perfectly. But note that to get root, you will have to use cf-auto-root for the 920G Model
Best of luck
Click to expand...
Click to collapse
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Kjc99 said:
How come it has to be the New Zealand? I'm trying to backup my carriers crappy baked rom just in case I need to return... Is there anyway to back it up without a custom recovery but rooted? Because if I flash the new Zealand before making a backup and have to return they will see I have messed with the phone because they put a boot animation
Click to expand...
Click to collapse
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
My carrier is GCI wireless in Alaska, USA... No way to download there firmware...also is twrp it? No more cwm or philz recovery?
Sorry forgot to add current firmware pic
s3ct0r said:
Doesn't have to be the New Zealand one, I just used it since I'm in Australia. Any 920I firmware should work just make sure it's at least 1D. I only tried those firmwares, and always had success
Click to expand...
Click to collapse
Cool thanks for the info!
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Kjc99 said:
Update thank you @s3ct0r...worked on the 1st try.... Now I'm working on the deep sleep issue...
Click to expand...
Click to collapse
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
s3ct0r said:
Flash the ktoonsez Kernel, or the flashable zip from the Cf-AutoRoot topic
Click to expand...
Click to collapse
Is ktoonsez a stable kernel, I remember using it on my S4 but skipped it last year on my S5 because it had to many tweaks... Can I use it with a stock rom? Alliance?
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Hi
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I would invite you to post your request in the below forum as our team mates there should be able to help you:
AT&T Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Click to expand...
Click to collapse
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hi,
iam glad this place still exits
I've got a S6 (SM-G920F), more or less a testing-device (poor Batterie^^) . It was on Android 7 Stock, may not updated for 6month+, not 100% sure . Was my first mistake, i don't know any more details...
First i tried a few old stock from sammobile (Android 5.1.1 etc.) and tried to flash with odin. As you may guess it didnt work. I thought "Stocks - should be easy " and there are many outdated guides who tell this. I searched for the error messages (onscreen) and found hints that this problems could be caused by Bootloader who deny downgrading, may also for good reasons. I didnt read any deeper, as i found this Guide here: https://forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
Followed this Guide with https://www.sammobile.com/firmwares/galaxy-s6/SM-G920F/DBT/download/G920FXXU2COH2/54694/ as "Source". I worked with the engineering bootloader and the told parts from the Stock. RecoveryMode was broken, but systems seems boot fine and no obvious Errors or Problems. A good guide for that goal, but no guide can teach me whats going up in detail. I want to understand a little bit more, and not searching for a "from any to ANY guide"
Actually iam trying to get on 6.0.1 Stock, but this guide doesnt work for me with a few stock-roms, not booting.
Flashing complete stocks with odin still fails. Flashing dont start or fail at hidden.img.
I came to this page with my first xda, later flashed a lot with my Galaxys...S2-S4, also custom roms- but stayed on stock at some point. So i should have basic knowledge, but i realize its outdated and there a few new "stummbling blocks" etc. Therefore i decided to get more in detail and ask here, before trial and error with other ways (like flashing with recovery)may leads to a brick. Not founded deeper informations myself. In the past i knew which parts a rom/firmware could have and their functions and whats possible with it.
Somebody here with time to help? Where can i find infos which bootloader i got, which others i may can flash (on what way) and which one is working with which Rom^^ Hope that the device wasnt on newest BL, and i still have the choice. Is the Kernel or other parts important as long as iam only trying to jump between stocks?
I backuped efs-partition with TWRP and stored the backup folder on PC, is that enogh to be prevent IMEI lost?
Hints or Links could be enough in some cases.
Thanks for reading and your work
Mattezh said:
Hints or Links could be enough in some cases.
Thanks for reading and your work
Click to expand...
Click to collapse
G920f is international version, so compatible with all roms. Frankly speaking, flashing is basically same as s2 etc. If you're on nougat, then nougat bootloader.
Idk why u want to go to Marshmallow, but some guys managed to flash a Marshmallow custom rom directly from nougat. It's called xtrestolite. It has no support whatsoever. https://forum.xda-developers.com/ga...xtrestolite-deodexed-mod-edition-1-0-t3094423
For TWRP & ROOT, follow the steps in this video https://youtu.be/BV1ELmu8T0I & that's it.
DO NOT USE supersu. USE & flash latest Magisk v15.0+ (stable) from here https://forum.xda-developers.com/app...80cb6-t3618589 Download latest Magisk Manager as well
So the steps are:
From the links in the video, download the specific twrp for g920f. This one: https://eu.dl.twrp.me/zeroflte/twrp-...roflte.img.tar The first file.
Install the Samsung drivers from the link in the video on your pc.
Download & extract Odin.exe.(link in video. Use the same version)
Enable usb debugging on your phone.
Put your phone to download mode
Start odin. Follow the steps in the video to install twrp
When install is complete, immediately reboot to twrp to flash latest Magisk. Wipe Dalvik.
Reboot. Install latest Magisk Manager
Check status in the Magisk Manager.
Done.
If not rooted, flash magisk.zip again in twrp
SuperSu gave problems to some users. Magisk was successfully installed in the first shot!
Nougat roms I'd suggest to flash. They're in S6 unified forum:
MiPa rom, A8 2016 v2, OdexLite v4.1
Try the Nougat roms I've mentioned since you're already on Nougat.
BTW Don't flash any kernels. Stay with those which came with the roms