I've just got myself a new phone, the Samsung GALAXY core LTE a few weeks ago and now I'm wanting to root it so I can customize it even more than it already is and while it runs android 4.4.2 and it's an awesome phone, Kingo Root doesn't seem to be able to connect with it.
The model number is SM-G386W
Any suggestions?
I am interested in knowing how to do this as well
Galaxy Core LTE is basically the Galaxy Avant (tmobile) with different branding. The Galaxy Avant has a chainfire root. Submit the recovery image for your firmware to the main chainfire thread (search for it) and chainfire should be able to provide a odin flashable file. Keep in mind your bootloader must be unlocked.
do you know how to unlock this phone? thanks
Can root SM-G386W same way as SM-G386T
I took the plunge and tried the Chainfire Autoroot method provided for the SM-G386T on my Canadian SM-G386W (Koodo variant) and it rooted fine. I have verified root and removed system apps with 3C Toolbox via the Xposed framework. Thus, it is clearly good to go root-wise. The instructions are here:
http://forum.xda-developers.com/showpost.php?p=54768458&postcount=1
Warning: this method will trip your Knox counter to 0x1 as Chainfire warns. So, if that concerns you do not use this method.
jcurtis said:
I took the plunge and tried the Chainfire Autoroot method provided for the SM-G386T on my Canadian SM-G386W (Koodo variant) and it rooted fine. I have verified root and removed system apps with 3C Toolbox via the Xposed framework. Thus, it is clearly good to go root-wise. The instructions are here:
http://forum.xda-developers.com/showpost.php?p=54768458&postcount=1
Warning: this method will trip your Knox counter to 0x1 as Chainfire warns. So, if that concerns you do not use this method.
Click to expand...
Click to collapse
i'd like to root my canadian SM-G386W too, but i have a concern:
In the thread you cite they say somewhere that the rooting script flashes recovery.img from
T-mobile sm-g386t, which would prohibit future updates if flashed to sm-g386w phone....
Sorry for my ignorance, but is there a way to fetch recovery.img from my sm-g386w phone?
in order to binary compare it at least with the one from existing root kit,
or better yet, to submit it to chainfire for a kit specificallydesigned for sm-g386w..
Download the Odin tar.md5 from sammobile and extract. I would do it myself but I don't have > 10 posts and can't post on the request thread...
Sent from my SM-G386W using XDA Free mobile app
johpan said:
Download the Odin tar.md5 from sammobile and extract. I would do it myself but I don't have > 10 posts and can't post on the request thread...
Sent from my SM-G386W using XDA Free mobile app
Click to expand...
Click to collapse
Thank you.. i will try.. i do not have 10 posts either, but i guess
it is not difficult to get them...
In the mean time, here is what i found:
https://twitter.com/srsroot/status/540567541576650752
#SRSRoot: samsung SM-G386W (Build: KOT49H.G386WVLU1ANI1) #Android 4.4.2 Now Supported for #Root at http://www.SRSRoot.com
Do you know guys if this SRSroot is a reliable root provider?
J.Tichi said:
Do you know guys if this SRSroot is a reliable root provider?
Click to expand...
Click to collapse
I tried SRSroot. pretty sure there just garbage. reboots the phone a couple times, claims to succeed. then Root checker says "not rooted" and when you try to undo root with SRSroot it also says device is not rooted unroot failed
we just really need someone to convert the G386 stuff over for the G386W. there the same damn phone. it just seems no one wants to touch the G386W because its only carried by Wind Mobile Canada. no love for the Canadians i see.
heres what happens.
SRS does this:
---= SRS One-Click-Root v4.7 =---
6:57:57 PM - Starting ADB Server..
6:58:02 PM - Manufacturer: samsung
6:58:02 PM - Model: SM-G386W
6:58:02 PM - Android Version: 4.4.2
6:58:02 PM - Build ID: KOT49H.G386WVLU1ANH7
6:58:02 PM - Board ID: MSM8226
6:58:03 PM - Chipset Platform: msm8226
6:58:03 PM - Getting OffSets.. : 0x8003 0x8005 (False)
6:58:03 PM - Query Server for Best Method.. Found Rootkit: 4
----= Start Rooting Process.. Please Wait =----
6:58:06 PM [+] Testing exploit: root4 (please wait..)
6:58:09 PM [+] Device Reboot #1 (Wait till it's started)
6:59:34 PM [+] Device Reboot #2 (Wait till it's started)
7:00:48 PM [+] Remounting /system Filesystem as R/W..
7:00:49 PM [+] Installing SU Binary...
7:00:49 PM [+] Installing SuperUser APK...
7:00:49 PM [+] Remounting /system Filesystem as R/O..
7:00:55 PM [+] Rooting Complete !
Then Rootcheck does as shown in the attachment.
then unrooting says:
---= SRS One-Click-Root v4.7 =---
7:11:01 PM - Starting ADB Server..
7:11:06 PM - Manufacturer: samsung
7:11:06 PM - Model: SM-G386W
7:11:06 PM - Android Version: 4.4.2
7:11:07 PM - Build ID: KOT49H.G386WVLU1ANH7
7:11:07 PM - Board ID: MSM8226
7:11:07 PM - Chipset Platform: msm8226
7:11:07 PM - Getting OffSets.. : 0x8003 0x8005 (False)
[x] Device is not rooted, UnRooting not needed.
johpan said:
Download the Odin tar.md5 from sammobile and extract. I would do it myself but I don't have > 10 posts and can't post on the request thread...
Sent from my SM-G386W using XDA Free mobile app
Click to expand...
Click to collapse
Hey, folks, I still do not get it.. successfully connected my device in the download mode to odin 3.07 (taken from the chainfire root package for SM-G386T),
and my device is visible there (windows 7 downloaded correct drivers automatically in the process).
in "Odin" I do see the options to flash the files ONTO the phone (as explained in the Avant root thread cited above ),
but I do not see any options to download any images FROM cellphone TO the computer!
How do you get recovery.img FROM cellphone to the computer?
My undersanding is that chaifire requires this file recovery.img from SM-G386W in order to make root toolkit for canadian version...
thank you for your suggestions...
J.Tichi said:
How do you get recovery.img FROM cellphone to the computer?
My undersanding is that chaifire requires this file recovery.img from SM-G386W in order to make root toolkit for canadian version...
Click to expand...
Click to collapse
Once you download the tar.md5, you can unzip using 7z or other extraction tool and it'll be in the extracted files.
johpan said:
Once you download the tar.md5, you can unzip using 7z or other extraction tool and it'll be in the extracted files.
Click to expand...
Click to collapse
Ah! thank you..
I've got the recovery.img from the G386WVLU1ANI1 Kooodo/Telus firmware for SM-G386W dated 2014 Sept 3 from here:
http://www.sammobile.com/firmwares/download/35905/G386WVLU1ANI1_G386WOYA1ANI1_KDO.zip/
and now since I have more than 10 messages I'm going to post a request in the
CF-Auto-Root thread here:
http://forum.xda-developers.com/showthread.php?t=1980683
Hopefully a few fellow Canadians are gonna benefit from that too
N.B. Still i'm curious what can I use to extract the firmware images directly from my Samsung phone.
---------- Post added at 12:33 PM ---------- Previous post was at 12:16 PM ----------
UPD. Ouuups. Got an error while uploading recovery.img:
Your file of 9.61 MB bytes exceeds the forum's limit of 8.00 MB for this filetype.
Predictably, zipping it does not help much to reduce its size..
Folks, will you kindly join my request here
http://forum.xda-developers.com/showthread.php?t=1980683&page=78#post58282353
so that chainfire might kindly consider downloading recovery.img for SM-G386W from sammobile
http://www.sammobile.com/firmwares/download/35905/G386WVLU1ANI1_G386WOYA1ANI1_KDO.zip/
Hi Big_BadAss,
I appreciate if you could help me on this. Thank you.
Do you think that your rooting method will work for this phone (my friend's):
It's with Virgin/Bell and Notice it's auto-updated to 4.4.4.
SM G386W 4.4.4
G386WVLU1ANJ1
KERNEL 3.4.0-2988301
<<<<<<<<<<<<<<<<<<<<<<<
BIG_BADASS said:
Hello friends,
I successfully rooted SM-G386W with SM-G386T method. You may get Odin and the tar.md5 file for SM-G386T here:
http://download.chainfire.eu/480/CF...oot-afyonltetmo-afyonltetmo-smg386t.zip(CLICK THE VERY BOTTOM LINK TO DOWNLOAD)
Refer to the following links on full VISUAL aided instructions:
https://www.youtube.com/watch?v=dy-cD5_7aLo
http://androidxda.com/root-samsung-galaxy-avant-sm-g386t
Best of luck!
Best regards,
BIG_BADASS
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
Hello all,
I successfully rooted SM-G386W with SM-G386T method. Get Odin and the tar.md5 file for SM-G386T here:
http://download.chainfire.eu/480/CF...Auto-Root-afyonltetmo-afyonltetmo-smg386t.zip (CLICK THE VERY BOTTOM LINK TO DOWNLOAD)
Refer to the following links on full VISUAL aided instructions:
https://www.youtube.com/watch?v=dy-cD5_7aLo
http://androidxda.com/root-samsung-galaxy-avant-sm-g386t
Best of luck!
Best regards,
BIG_BADASS
Click to expand...
Click to collapse
BIG_BADASS said:
I successfully rooted SM-G386W with SM-G386T method. You may get Odin and the tar.md5 file for SM-G386T here:
http://download.chainfire.eu/480/CF...oot-afyonltetmo-afyonltetmo-smg386t.zip(CLICK THE VERY BOTTOM LINK TO DOWNLOAD)
Refer to the following links on full VISUAL aided instructions:
https://www.youtube.com/watch?v=dy-cD5_7aLo
http://androidxda.com/root-samsung-galaxy-avant-sm-g386t
Best of luck!
Best regards,
BIG_BADASS
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
Hello all,
I successfully rooted SM-G386W with SM-G386T method. Get Odin and the tar.md5 file for SM-G386T here:
http://download.chainfire.eu/480/CF...Auto-Root-afyonltetmo-afyonltetmo-smg386t.zip (CLICK THE VERY BOTTOM LINK TO DOWNLOAD)
Refer to the following links on full VISUAL aided instructions:
https://www.youtube.com/watch?v=dy-cD5_7aLo
http://androidxda.com/root-samsung-galaxy-avant-sm-g386t
Best of luck!
Click to expand...
Click to collapse
I confirm. It works!.. All that stuff about recovery.img I was talking about above is not important.
After rooting, odin just flashes back the ORIGINAL recovery.img.
Glad to finally have rooted phone. It is mostly important in order to fix SD card permissions.
Greetings!
---------- Post added at 08:12 PM ---------- Previous post was at 08:02 PM ----------
J.Tichi said:
After rooting, odin just flashes back the ORIGINAL recovery.img.
Click to expand...
Click to collapse
N.B.
No, I was wrong actually.. it indeed flashes the recovery from SM-G386T (t-mobile) , as stated above in the thread,
but who cares...
it works, and it is rooted, and those stupid SD card permission restrictions are gone!
---------- Post added at 08:17 PM ---------- Previous post was at 08:12 PM ----------
BIG_BADASS said:
Hello Sintoo,
It should work, as long as your hardware is the same, or similar. Rooting the devices installs custom firmware, which is unique to each device (and similar devices), regardless of the software installed.
I didn't get the 4.4.4 update. I get an error message saying that an unauthorized firmware has been installed onto the device, whenever I tried to auto-update. So I un-rooted the device to see if the update is available. I do not get the error message anymore, but there is no indication of a software update either.
Best regards,
BIG_BADASS
Click to expand...
Click to collapse
How exactly did you unroot? just flashed stock firmware from sammobile using odin? or some other way (without hard reset) is possible too?
thanks!
Koodo SM-G386W (same as mine) did not have any update up to today....
BIG_BADASS said:
There's a "full unroot" option in the SuperSU settings. Then reboot your phone and to be on the safe side, use Samsung Kies to install the original firmware for your device. All you must enter is the model number and serial number. It will identify the original firmware and install it for you.
Click to expand...
Click to collapse
Hm.. interesting, thank you... However, did you also observe that SuperSU full-unroot restores original recovery partition ( that from SM-G386W Koodo, ending with .. ANI1 )?
E.g. now, after rooting, when I boot into recovery (by holding Volume-Up/Home/Power buttons)
I can see that the recovery partition is now from t-mobile SM-G386T (ending with ..ANG6),
while the rest of the firmware is from Koodo SM-G386 (..ANI1 ), as you can see from the android settings/ about device.
Can you tell pls whether the recovery partition is back to ... ANI1 after you did full-unroot via SuperSU?
thank you!
N.B. I have Kies3, but I do not see any place to t enter is the model number and serial number... Which Kies are u using?
BIG_BADASS said:
I didn't keep track of the recovery partition after the SuperSU uninstall, but after I have re-installed the original firmware, it's back to ...ANJ1 Bell Canada firmware
In Samsung kies 2.6 or 3: Tools> Firmware Upgrade and Initialisation.
After that, the program will guide you for the next steps
Click to expand...
Click to collapse
Thank you!
Hm.. "Curiouser and curiouser!" (C)
How does SuperSU know what exactly is the original recovery partition for your particular phone, in order to restore it?
Or ... are you describing the situation after you also refreshed your phone via Kies?
My situation now (after rooting) is the following:
- t-mobile SM-G386T branded recovery partition (..ANG6 ending) is showing when boot into recovery,
- while the rest of the firmware is still the original SM-G386W Koodo (..ANI1 ending).
- OTA update attempts now fail telling me that i have an unauthorized firmware,
- while Kies tells me that everything is OK and ..ANI1 firmware is the latest one...
So, Kies apparently ignores recovery partition change, which may be good, since it might rewrite all, if a 4.4.4 or 5.xxx update is available..
N.B. It seems no 4.4.4 update to SM-G386W is available so far, mention of it on page 2 is a mistake...
Bell users-Android 5.0 Lollipop update
SM-G386W Android 5.0 Lollipop update available for Bell Mobility clients. 4G LTE network access is stronger.
BIG_BADASS said:
SM-G386W Android 5.0 Lollipop update available for Bell Mobility clients. 4G LTE network access is stronger.
Click to expand...
Click to collapse
Bell's site still says its on 4.4.2
BIG_BADASS said:
SM-G386W Android 5.0 Lollipop update available for Bell Mobility clients. 4G LTE network access is stronger.
Click to expand...
Click to collapse
Can you provide a link or screenshot of this? This is what I personally really want to do to my g386w is get android 5 on it.
I rooted a Fido and rogers version of this phone both using the cf auto root above and the twrp from that phone no problems
HI EVERYONE. my moto g got struck in 'warning bootloader screen' while trying to downgrade from 5.0.1 gpe to 4.4.4 kitkat. and
i am a noob in rooting.so i need help.i can go to fastboot mode.i followed a youtube video moto- unlock,restore video. i did not know that i will run into problems when trying to downgrade from lollipop. so if someone can guide me.pls help
pranavesh1202 said:
HI EVERYONE. my moto g got struck in 'warning bootloader screen' while trying to downgrade from 5.0.1 gpe to 4.4.4 kitkat. and
i am a noob in rooting.so i need help.i can go to fastboot mode.i followed a youtube video moto- unlock,restore video. i did not know that i will run into problems when trying to downgrade from lollipop. so if someone can guide me.pls help
Click to expand...
Click to collapse
i am in the same predicament, someone, anyone, please
Hi, please say the process you used to downgrade. Did you use motoboot? Gpt? Did you go to 4.4.4 gpe? It's necessary to know this stuff in order to help you. It's most probably fixable.
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
And by the way, that warning screen is called the boot logo
---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------
And if you're able to upgrade back to 5.0.1 gpe, i can tell you how to downgrade. Disclaimer: I'm not responsible for anything that happens from listening to my advice.
first of all, it would be quite helpful to know which version of moto g are you using, are you using the dual sim type? if yes, and you just want your moto g up and running, this this guide might be useful.
i've had unsuccessfull downgrade from lollipop to kitkat, probably since the partition is not the same. If the non-locking method doesn't work, you can always try to lock the device again per the instruction on that guide, and this time, with relocking the bootloader, this has saved my skin more than i would like to count.
tzzeri said:
Hi, please say the process you used to downgrade. Did you use motoboot? Gpt? Did you go to 4.4.4 gpe? It's necessary to know this stuff in order to help you. It's most probably fixable.
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
And by the way, that warning screen is called the boot logo
---------- Post added at 12:30 AM ---------- Previous post was at 12:25 AM ----------
And if you're able to upgrade back to 5.0.1 gpe, i can tell you how to downgrade. Disclaimer: I'm not responsible for anything that happens from listening to my advice.
Click to expand...
Click to collapse
I am using xt1032 us retail.the method I used is this YouTube video (link).I can got to 5.0.1 gpe and I want to relock my boot loader because I cracked my screen yesterday in a hurry and service center in here does not accept gpe phone. So help.
I converted my xt1032 from retail to GPE. To go back, I was able to flash back to retail using fastboot commands. Make sure you flash gtp.bin and skip motoboot.img.
pranavesh1202 said:
I am using xt1032 us retail.the method I used is this YouTube video (link).I can got to 5.0.1 gpe and I want to relock my boot loader because I cracked my screen yesterday in a hurry and service center in here does not accept gpe phone. So help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=57840897
I personally used the method in the 2nd post. Just be careful, no one's taking responsibility for a bricked phone in the process.
And you might want to flash stock logo.bin before locking bootloader in case locking doesn't help.
Sent from my Moto G using XDA Free mobile app
I have a samsung galaxy s6 with smg920f on the back. Since bought, I didn't get android marshmallow and clicking the update manually button doesn't do anything, it doesn't work and neither does it say 'no updates are available'. When trying to update via odin, the update failed saying that the model number was smg920p instead of smg920f as found on the back of the phone.
Smg920f is unlocked version of sprint, and as I'm not in the US, it will not push the update and installing firmware for sprint will not work on my carrier. It seems that the phone will not receive any update. What should be done and is there any way to update it?
Have you tried using SmartSwitch to update?
Using smartswitch also cannot update it. How can the device say its smg920p if on the back is smg920f?
Which Firmware do you try to flash via Odin? I mean which exact Model number and CSC
---------- Post added at 08:37 PM ---------- Previous post was at 08:34 PM ----------
And also this thread belongs in the q'n'a section.
I tried to flash the smg920f firmware but ut failed. Using phone info app, it said it's a smg920c instead
I rooted my J7 earlier today. After a few hours, I needed to reboot and I am getting an FRB Locked (Custom binar blocked by FRB lock) error. I can't seem to get rid of it.
I tried factory reset from the "maintenance" menu, but it didn't work. Using Odin to reflash is failing also.
Every solution I've found has assumed that I can boot into the OS - which I can't do.
I'm totally stuck. I'm hoping that someone here can help! TIA
you forgot to tick the oem unlock box in developper options
its ok you can fix it and root your phone but you will lose your personal files
THE FIX:
1/ power off the phone
2/ reboot to download mode by pressing volume down and power button and home button
3/flash stock rom of your phone model after downloading it
if you dont know how to flash stock rom search youtube or in google
the stock rom must be
sm 610m variant and your country build number
*if you want the root unlock the oem lock in developper option
*The developper options is unlocked when you press your phones build number 4 times
*The build number is in settings /about phone /software info
Reflash the stock rom
---------- Post added at 01:42 PM ---------- Previous post was at 01:39 PM ----------
Flash it using samsung odin tool in the computer
---------- Post added at 01:47 PM ---------- Previous post was at 01:42 PM ----------
Go to the samfirmware.com type (device name and model number) next download the latest firmware of your device
And odin tool
---------- Post added at 01:57 PM ---------- Previous post was at 01:47 PM ----------
This video help you
I just purchased this S7 from "Amazon Renewed" with a 90-day warranty and 2 yrs of insurance. It was sold as a "Verzion S7", and it has the "Verizion√" logo on the back. But the model shown in Software Information says G930U (not G930V), and the firmware is G930UUESACSI1. Also, it has no Verizon Bloatware; it's squeaky clean.
What do I have here..? Is it the Verizon hardware, but flashed with the unlocked firmware..?
Can this be rooted..? (that's where I was headed with this)
Also, the bootloader seems to be R16NW, which I see on S8 & S9 too..? I guess the bootloader version can vary widely across many models..? (I didn't know that until just now).
that seems like it
spinjector said:
I just purchased this S7 from "Amazon Renewed" with a 90-day warranty and 2 yrs of insurance. It was sold as a "Verzion S7", and it has the "Verizion√" logo on the back. But the model shown in Software Information says G930U (not G930V), and the firmware is G930UUESACSI1. Also, it has no Verizon Bloatware; it's squeaky clean.
What do I have here..? Is it the Verizon hardware, but flashed with the unlocked firmware..?
Can this be rooted..? (that's where I was headed with this)
Your bootloader version is "A" which is #10. If you look in the Verizon S7 thread you'll see how to root nouget/Oreo firmware. There is a link to the eng-boot you need posted bear the end of the thread. You just need to follow the op to root. Hopefully the SI1 firmware is still rootable.
Click to expand...
Click to collapse
Drunkpilot said:
Your bootloader version is "A" which is #10. If you look in the Verizon S7 thread you'll see how to root nouget/Oreo firmware. There is a link to the eng-boot you need posted bear the end of the thread. You just need to follow the op to root. Hopefully the SI1 firmware is still rootable.
Click to expand...
Click to collapse
Thank you. Could you reply with a link to the correct thread? I did start reading one with 11 pages, but after 6 Pages my eyes fell out of my head. I'm not even sure I was reading the correct one.
spinjector said:
Thank you. Could you reply with a link to the correct thread? I did start reading one with 11 pages, but after 6 Pages my eyes fell out of my head. I'm not even sure I was reading the correct one.
Click to expand...
Click to collapse
There are a lot more pages in this one: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Drunkpilot said:
There are a lot more pages in this one: https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Click to expand...
Click to collapse
Holy cow, that thread is huge. I think that's going to take me a while, lol.
I also bought one of the cheap Verizon S7s from ebay. It's running the same 930U Oreo firmware and is fast and clean.
I really want root and so I have been looking for an engineering boot that I can use to enable it, however the highest version I can find is v9 and I need v10.
Does anyone have the v10 eng boot image?
---------- Post added at 07:32 AM ---------- Previous post was at 07:30 AM ----------
Quote:
Originally Posted by billa
This root should run on any bootloader A/10 firmware version (the unbranded "U" version is preferred), what's important is to follow the steps carefully and do not skip anything.
First, always start with a factory reset in order to avoid any further issues. Enable ADB Debugging and run this script before anything, in order to avoid the constant re-booting and OTA updates after flashing the eng-boot.
Samsung_Security+OTA_Disabler_(BillA_v2018-04-01).BAT
https://androidfilehost.com/?fid=674106145207486974
Second, flash the eng-boot and let it sit there for about 30 minutes without touching the phone, then again enable ADB Debugging .
Samsung_G930x_QC_UVEACSF1_v8.0.0_Eng_Boot_Root_v20 19-06-04.TAR
ro.bootimage.build.fingerprint=samsung/heroqlteuc/heroqlteatt:8.0.0/R16NW/G930AUCEACSF1:eng/test-keys
https://androidfilehost.com/?fid=1899786940962594014
Samsung_G935x_QC_UVEACSF1_v8.0.0_Eng_Boot_Root_v20 19-06-04.TAR
ro.bootimage.build.fingerprint=samsung/hero2qlteuc/hero2qlteatt:8.0.0/R16NW/G935AUCEACSF1:eng/test-keys
https://androidfilehost.com/?fid=1899786940962594015
Third, run the https://www.androidfilehost.com/?fid...63190603904440 file and follow the instructions in the OP.
This has not worked for me so far, but I will try again.
---------- Post added at 08:07 AM ---------- Previous post was at 07:32 AM ----------
Success!
I'm using linux so I extracted the engineering boot.img file from the archive and flashed it. After that I was able to remount all the system partitions RW via ADB and then I could install root!
The engineering boot image is noticeably slower than the stock one so the next step will be to try and replace just the stock boot image to get the faster kernel back again.