Hi,
I have a P3113.
I want to be able to receive the OTA updates from Samsung, but their OTA update process invokes a reboot into their stock recovery to complete the update. So, if I replace the stock recovery, the official OTA updates wont be able to complete.
But the only way I have seen to "root" a stock ROM was to first replace the stock recovery with CWM recovery, which is need to install a Zip file that does the actual root.
But, once I replace the stock recovery, I will no longer be able to do official OTA updates because they require a stock recovery.
So, what can I do to have a stock ROM and Recovery on my tab, but also be rooted?
If you have the mobile odin pro (paid) and managed to flash stock firmware (the updated one) that you downloaded from www.samfirmware.com (register first) then you will be able to retain root after flashing if you checked the everroot option in mobile odin pro
Or receive the latest firmware via kies then you could root it afterwards ( root the updated firmware)
Or flash the updated firmware from samfirmware via odin pc 1.85 and then root again as usual
As i know no flashable zip to flash to give you the stock recovery
I suggest update via pc odin and forgetting about update via kies
If anytime you want to use kies for update, you could flash first stock firmware via pc odin then update or flash the updated firmware directly then root
Sent from my GT-P5100 using xda app-developers app
Mohamedselim said:
If you have the mobile odin pro (paid) and managed to flash stock firmware (the updated one) that you downloaded from www.samfirmware.com (register first) then you will be able to retain root after flashing if you checked the everroot option in mobile odin pro
Or receive the latest firmware via kies then you could root it afterwards ( root the updated firmware)
Or flash the updated firmware from samfirmware via odin pc 1.85 and then root again as usual
As i know no flashable zip to flash to give you the stock recovery
I suggest update via pc odin and forgetting about update via kies
If anytime you want to use kies for update, you could flash first stock firmware via pc odin then update or flash the updated firmware directly then root
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info - very helpful.
So am I correct in my understanding here, I can flash stock with mobile Odin, keep my root have stock recovery and then be able to get ota updates without a problem (or use kies to get the update, either way is fine by me).
If I am correct I love you all more and more everyday I come here
Just trying to confirm my understanding
Mohamedselim said:
If you have the mobile odin pro (paid) and managed to flash stock firmware (the updated one) that you downloaded from www.samfirmware.com (register first) then you will be able to retain root after flashing if you checked the everroot option in mobile odin pro
Or receive the latest firmware via kies then you could root it afterwards ( root the updated firmware)
Or flash the updated firmware from samfirmware via odin pc 1.85 and then root again as usual
As i know no flashable zip to flash to give you the stock recovery
I suggest update via pc odin and forgetting about update via kies
If anytime you want to use kies for update, you could flash first stock firmware via pc odin then update or flash the updated firmware directly then root
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
So this is kind of a bump since I am trying to understand if I am correct here. I am still new to all this and want to learn things.
If I use Mobile Odin Pro to flash stock firmware with EverRoot on my P3113, then I can still receive normal updates either via OTA or Kies (which is preferred?). This will keep stock recovery, for the updates, and preserve my root so I can enjoy the benefits.
Does this plan run the risk of bricking on updating? Due to the fact that it is rooted, I thought you can NOT do a regular update (or was that just because of CWM being the recovery?).
What happens when Jelly Bean goes to roll out, will this brick the device since it is a whole new OS? Will this break root and I will need to re-root?
Just trying to understand everything before I make a decision on how I proceed with my device from here. I have never used Mobile Odin, and this is my first rooted device, so I apologize for my questions, but how else will I learn?
Thanks for your time, and your help, and as I said I love you all more and more each time I come around here, since I usually learn something new
Root link
hi can someone post the root link for download?
Hat Trick said:
hi can someone post the root link for download?
Click to expand...
Click to collapse
Sorry guys it's right there in development.
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:
Hey there,
I have a nasty problem with my Samsung S7 G930F.
Rooting went fine, wiped everything to get access to the internal storage for backup. Now I need the German version of Vodafone ROM to use Wifi Calling which is really essential for me.
However I only get this ROM at Sammobile which must be flashed via Odin then. When I flash the ROM everything I did before gets lost, TWRP gets overwritten by a Android Recovery.
If I reinstall TWRP now, the wipe - which is necessary for backup or Xposed - is gone.
Everytime I try to install the ROM everything is replaced, even if I put in HOME_CSC file at CSC in Odin.
I really need this special ROM, however it is pretty important to get access to backup and Xposed.
Is there any way to preserve my TWRP status AND installing the new ROM? Or maybe there is a way to convert the Odin tar files to a zip which can be flashed in recovery?
Thank you so much!
Anyone have the odin of the latest factory rom or a zip for twrp? Of course the phone knows there is one there but the naughty owner of the phone isn't stock......
you can get the latest stock samsung (any model) ROM on updato.com (no restrictions, no accounts, totally free), however, the google apps will need to update themselves.
Does it have to be done through Odin or can it be done through twrp?
sent from my Samsung wonder device
.zip : TWRP
.tar.md5 : Odin
EDIT: that's not actually true. but, updato.com ROMs are flashable via rocovery such as TWRP.
Sitting right here.
http://forum.xda-developers.com/galaxy-j7/how-to/firmware-update-t-mobile-j7-2016-sm-t3506092
Hey Guys,
So in early January when the s8+ Oreo update got leaked I followed the guide to install it on my device. However, I noticed when I go to download mode it shows up as the SM-G955U and my device is SM-G955W. When I tried download the stock firmware and flashing it in firmware it fails in ODIN. So my question is how would I revert back to the stock firmware and ROM that came with my device, I've tried many different zip files for the stock ROM thinking it might have been corrupt but it does not work.
Edit: here's the tutorial I followed to flash Oreo on my device initially
https://www.xda-developers.com/install-android-oreo-galaxy-s8-snapdragon/
Thanks!
Try the patched version of Odin 3.13.1:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
I did the same thing and used this to get it back to SM-G955W. This version has support for .lz4 files, which is used in the Oreo ROMS.
Grospolina said:
Try the patched version of Odin 3.13.1:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
I did the same thing and used this to get it back to SM-G955W. This version has support for .lz4 files, which is used in the Oreo ROMS.
Click to expand...
Click to collapse
DO you mind linking the ROM you downloaded for it ??