Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance
Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.
Tbnitz said:
Hello hoglak
I have a 920I and was also having the same problem.
I solved the problem flashing the latest version of the rom from SamMobile site.
After flashing the rom your TWRP should work.
Click to expand...
Click to collapse
Can you tell me which specific rom you tried i downloaded latest I can find for Aus rom but still having the same issue. Any chance give a step by step guide on what you did exactly.
Thanks in advance
I just used the New Zealand firmware.
I am from Brazil and with the orginal rom the same thing happened, im flashed the generic one and worked.
This one seems to be the general rom to Australia
http://www.sammobile.com/firmwares/database/SM-G920I/XSA/
But i used the zto version from Brazil
hoglak said:
Hi Guys,
I've got an S6 Australian SM-G920i version. Done the root option and done the twrp recover flash in odin however i keep getting stuck at Samsung Logo. Tried root first and then flash twrp that didn't work, tried twrp first then tried to boot to recovery to root from twrp and still no go. teamwin says it compaitible with SM-G920i version tried TWRP 2.8.6.0 and TWRP 2.8.6.2 still no go.
Please help if any of you know of a work around.
Thanks in advance
Click to expand...
Click to collapse
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.
d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.
Click to expand...
Click to collapse
I'll give this a go tonight hopefully it will work.
Thanks mate
d2d2d2d2 said:
I had the same problem. The latest firmware for unbranded (XSA) Australia on sammobile is AOC4. I had success with using the Singapore unbranded (XSP) firmware AOD1.
Flash AOD1 with Odin then you have stock everything. You should be able to flash TWRP 2.8.6.2 with Odin and boot successfully into Custom recovery.
You can either take two options from here.
Flash CF-Root and "just root" the stock ROM - Boot into Download (again) and then flash the CF Root.
Flash a ROM or a Mod which has Root included. - My first success was Wiping with stock recovery, flashing AOD1 clean with Odin, then flashing WanamMod on top of it as it included root.
Aussie G920i.
Hope this helps.[/QUO
Thanks mate that worked perfectly.
Click to expand...
Click to collapse
Hi
So, i'm going to root my S6 and flash a custom rom, got 1 question:
Reading the CF-AutoRoot page, it mentions something about battery drain because of wakelocks after rooting, and that i need to flash an update zip file to fix it.
Do i still need to do that after rooting ? Or has it been already fixed and thus i can just root and flash the rom i want ?
Thanks <3
No one?
CF-auto root doesn't work on firmware 5.1.1 you will have to flash unikernel found here http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395 using Odin then flash https://dl.twrp.me/zeroflte/ custom recovery using flashify (found in the playstore) and you will be rooted with a custom recovery and ready to flash a custom rom
You can try this
http://androiding.how/how-to-root-galaxy-s6-on-android-5-1-1-all-variants/
I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:
Hi Guys.
I've reached a state of confusion reading about OTA-updates, TWRP and root. My question question is this:
I installed TWRP, flashed the verity opt encryption kernel and rooted my G930F. Everything works and all is good. But with the new Chainfire AUTO-ROOT (is it X.72?) OTA-updates has been disabled.
I'm confused about the reason for this. Does this mean that I risk bricking my phone if I at some point in timez deside to flash stock rom via ODIN? Or will this just replace TWRP with original recovery and overwrite root?
Sorry for my noob-mind. I'm new to Samsung devices.
Best regards.
If you flash stock rom via Odin TWRP will be deleted and stock recovery will be installed. You will also lose root privileges. Make sure you have a backup before flashing stock via Odin. Once restored stock rom via odin follow same steps you took the first time you rooted your phone.
Leeum said:
If you flash stock rom via Odin TWRP will be deleted and stock recovery will be installed. You will also lose root privileges. Make sure you have a backup before flashing stock via Odin. Once restored stock rom via odin follow same steps you took the first time you rooted your phone.
Click to expand...
Click to collapse
Thanks alot!
Hi, as the title says im looking for a way to keep TWRP while i install the newest stock room for my specific version of the S7 Edge.
I already downloaded the 2GB zip file from sammobile, but that files are made for the Odin installer, and if i install it trough Odin i am guessing TWRP will go away.
tl;dr: Im looking for a way to have MAGISK hence TWRP and newest stock for my specific version of the S7 Edge
lazykpox said:
Hi, as the title says im looking for a way to keep TWRP while i install the newest stock room for my specific version of the S7 Edge.
I already downloaded the 2GB zip file from sammobile, but that files are made for the Odin installer, and if i install it trough Odin i am guessing TWRP will go away.
tl;dr: Im looking for a way to have MAGISK hence TWRP and newest stock for my specific version of the S7 Edge
Click to expand...
Click to collapse
The only way you're going to flash any kind of stock firmware while keeping TWRP is if someone has conveeted your stock firmware into a flashable.zip that can be flashed in TWRP. If there is not a flashable .zip available, you wont be able to do what you're trying to do.
The only other way to flash stock firmware is to use Odin or mobile Odin and they will both remove root and TWRP.
Typically, Samsung devices that are rooted and have TWRP can only update the stock firmware via Odin, mobile Odin, Kies or SmartSwitch. This removes root and TWRP which means those users have to root their device again and flash TWRP again.
Sent from my LGL84VL using Tapatalk