I have read a lot about rooting prior to the new firmware. But I just got a new Sprint S5 yesterday, and it comes with firmware NK4 (4.4.4) I tried to odin flash the firmware from NE5 (from June 2014), and that boot me into a boot loop. So i had to Flash back to the NK4 (Nov.2014). This phone has NEVER been rooted. there is NO recovery flashed either.
Are there any suggestions or walkthroughs?
Here are the firmwares available from Sprint.
2014 November = NK4
2014 June = NE5
2014 April = ND2
2014 April = NCB
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
m20120 said:
CF Autoroot works but will trip the Knox counter. If you do not care about that then that is the easiest way to go. There is a walkthrough here.
Towelroot was an option on the earlier firmware (kernel) and would not trip Knox. There are ways to use Towelroot if you are on the latest kernel but it requires flashing to old kernel using Odin, running towelroot, and reloading the current kernel. There is a thread on this process here somewhere but I don't have a link. I used CF Autoroot and tripped knox the day I bought my S5.
Click to expand...
Click to collapse
I also forgot to mention that cf autoroot just boots be up to the Sprint boot up, and then hangs!!! So cf root doesnt seem to be an option on 4.4.4 NK4.
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Towel root will work, here are the steps and the kernels you will need.
1. Download and install towel root, but do not run.
2. Use odin to install NE5 kernel below, remember to unzip it first.
3. Boot phone and just hit ok or close to all the errors that will pop up because you have the wrong kernel installed.
4. Run towel root.
5. Use odin to install the NK4 kernel below.
6. After reboot, download supersu from the play store, then udpate binaries, answer yes to the disable knox prompt.
7. Profit!!! Use Galaxy Tools to unlock hotspot, or xposed framework and Wanum to customize phone.
What's the difference between the firmware and kernels?
Stuck
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
My baseband is nk4
xSpaceGhost said:
What's the difference between the firmware and kernels?
Click to expand...
Click to collapse
Firmware is the modem, kernel, etc. Not what you need to use towel root. All you need is the kernel to get towel root to work. If you flash the whole firmware you won't get towel root to work and your phone may not even boot.
banccalif said:
You need to flash the kernel that matches your baseband, you can find the tar and flashable versions here
http://forum.xda-developers.com/showthread.php?p=57469564
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
Click to expand...
Click to collapse
dewrust said:
i tried using cf auto root with odin (i dont care about warranty)
cant get phone to boot past trying to auto boot into recovery
RECOVERY BOOTING....
RECOVERY IS NOT SEADROID ENFORCING
Set Warranty Bit : recovery
at this point i would be happy just to get it to boot
Click to expand...
Click to collapse
First i put supersu as a zip on my sd card, thenI had to install custom recovery through odin and then installed supersu via recovery and this worked fine.
Can you post the super SU file. I did the same method but had to install supersu from the playstore.
http://forum.xda-developers.com/showthread.php?p=23427715
Here's the link to chainfires stable version. In the OP scroll done to the link for the zip file under the play store versions
I am on nk4 (4.4.4) firmware and baseband. I rooted using this method. 1. Went to download mode and unchceck auto reboot and time. 2. Odin flash 6.26.6 philz recovery. 3. Then unplugged and entered recovery (made a backup) 4. Copied superSU to phone. 5. Rooted and rebooted. 6. Rebooted and installed superSU and disabled Knox. Check with root checker. (Happy face)
glad it worked.
jpgranger said:
Yeah.....after NK4, you can almost forget Towelroot. There is a method in Q&A but doesn't seem 100% for some that I've spoken with. It takes a delicate hand and will probably only work on certain phones. And although CF-AutoRoot should work, you're gonna trip Knox no matter what. You may as well trip through Odin with PhilZ Recovery or the latest TWRP. Then flash the SuperSU.zip like the old ways of the S3.
And I know every Sprint store is different, but most reps know that we are root our phones.
Click to expand...
Click to collapse
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
travanx said:
I think I have one of these phones. Just got it on the 17th and was on NK4. Just tried towelroot after using ODIN to NE5, with and without string 1337 0 1 7380 4 0, and couldn't make it rain. At this point all I want is to be able to tether the phone. I guess I am eventually going to trip knox so why wait?
Click to expand...
Click to collapse
You should be able to use the galaxy tools app to get tethering, not sure if it requires root or not. If that doesn't work and you don't care about trippin knox you can re-download ne5 and follow these steps below to get root & custom recovery
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Can't I just use auto chainfire to root and recovery from Nk4?
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.
Can't I just use auto chainfire to root and recovery from Nk4?<br />
<br />
The only reason I was looking at a custom rom would be battery life, but wow the S5 is destroying my S4 on battery. Still might give MOAR rom a go if Lollipop isn't being pushed out by Sprint anytime soon.<br/>
See post 14 above those steps work and then use galaxy tools for hot spot. Worked great for me. Chainfires c.f. root did not work
banccalif said:
1. flash ne5 full tar with odin
2. download towel root, install and run to gain root (Make it rain)
3. Install supersu from play store
4. Install flashify from play store, grant root access
5. Download recovery IMG (Make sure it's IMG and not tar or zip) twrp here >> http://techerrata.com/browse/twrp2/klte
6. Open flashify for root users and select recovery image, navigate to twrp or philz custom recovery you downloaded and flash within the app
7. Open supersu and follow steps to update binaries, phone will boot to recovery and complete the update then reboot automatically
8. Enjoy your rooted device
Then you can either flash a Hotspot mod compatible with your baseband or switch to custom rom that has it enabled natively like MOAR ROM
Click to expand...
Click to collapse
.
Ended up using the oneclick NE5 from here, http://forum.xda-developers.com/showthread.php?t=2787760, knox says 0x0. Made it rain, still 0x0. And then odin 3.09 for philz recovery, still 0x0. As soon as I went into recovery it triggered 0x1 but not before. In case anyone new to the phone, like myself, cares what step triggers knox.
Related
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Nocturnal86 said:
Just flashed the factory Rom and got everything set up. I flashed TWRP then tried to flash the latest SuperSu to get root and it installed it but when I went to open it it would say that I don't have any binaries installed and I can't uninstall SuperSU either. I tried to install CWM Recovery and refresh it through there but I still have the same issues... :/ What am I doing wrong or how can I get my phone rooted properly? Thanks for any help!
Click to expand...
Click to collapse
You need to flash a kernel that is permissive and then flash SuperSU there are a few in the forums if you search you shall find them
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
aalaap said:
Instead of a permissive kernel, simply use Chainfire's AutoRoot, which will flash a more secure kernel and SuperSU automatically. You don't even need TWRP for this. http://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip
Go to http://autoroot.chainfire.eu/ to get AutoRoot for other devices.
Click to expand...
Click to collapse
So I flash this in ADB? Is the secure kernel the same as stock? and if I were to flash a customer kernel like FK would I lose root? Sorry for all the questions just trying to clarify some stuff so I'm not completely ignorant to what I'm doing lol
There's a batch file that does it. You run it in the bootloader, not ADB.
FK has a Lollipop compatible kernel, but try and root stock first. Then flash FK's Lollipop version (it's different) and run CF AutoRoot again. Just to be sure things are working. Personally, I'm going to use stock for a while, understand the performance and then try FK or EX or whatever, so I'll be able to tell the difference.
Hello Everybody.
I have finally successfully rooted Note 3 N9005 on Android 5.0 Dev Base (DB) only, without tripping knox. The Dev base (DB) is made or compiled by Alexander on OB6 (the latest firmware). It has Multi-CSC feature and hence you will not have to worry about the CSC feature being a reason for holding you back from Rooting Note 3 N9005.
Disclaimer: I am not responsible if you mess up any of the steps and neither am I responsible for anyone bricking their phone. I have personally tested this step 3 times over to confirm its validity.
UPDATE: We have finally been able to root all LOLLIPOP without dev base. The new guide is on its way. All your data can remain, you will be able to root without having to worry about losing your DATA.
UPDATE: Here is the link to my ROM, you can replace this rom with Alexander's Dev Base in the Instruction Steps and all will be fine.
:: MEGA DOWNLOAD ::
:: DROPBOX DOWNLOAD ::
UPDATE: Added updated Links for Alexander DevBase, Bootloader and CP File.
NOTE: KNOX apps have been disabled by default by Alexander himself. Thank you Alexander.
NOTE: Moderators please move this thread to the right section. Also, please note, I will be giving credits to the original Devs for the rom and the root methods which I used common sense and made them work. All these changes will be released in the final Guide. In a few hours the whole guide with the complete step-by-step procedure will be uploaded here.
NOTE: I have written this guide on my own and have not copied anything from anywhere except the rooting process provided by W0lfDroid. If required, I will remove it and replace it with the link to the page to make it easier. But, in my opinion my steps are simpler
Things you will need.
Precautionary step: Make a backup of your PIT File just in case. You might need it though I had no need for it and its simply taking up a few KBs of Space on my PC
1). Official Stock 4.4.2 Firmware. (Grab it via Sammobile).
2). N9005XXUGBOEA_DevBase_alexndr.zip (Grab it HERE).
3). ODin v3.09. (Grab it HERE).
4). Mobile ODin Pro. (Buy it and support Chainfire).
5). SuperSU 2.46 APK. (Grab it from Google Playstore).
6). Towel Root APK v3 Offline. (Grab it HERE)
6). Device drivers. (My suggestion would be to just install Kies 2 and Kies 3).
7). ADB should be set up and accessible via CMD.
8). Root Kernel
9). Stock Kernel: NF4, NG1, NG2, NH1, NI4, NJ1, NJ2, ZTFUNJ1, NK1
10). Bootloader File (OEA – Latest as of now).
11). CP File (OD3 – Latest as of now).
Credits:
The Root Kernel and Stock Kernels are all credited to W0lfDroid.
SuperSU, Mobile ODIN Pro 4.20 are credited to Chainfire.
DevBase Rom, Bootloader File, CP File are credited to Alexander.
Towel Root is credited to Geohot.
Instructions:
Part 1: Downgrade 5.0 >> 4.4.2 (Skip this if you have 4.4.2 and move over to Part 2).
Procedure:
1). Run ODin v3.09 as Administrator.
2). Unzip the stock rom zip package that you downloaded for 4.4.2 and you will get a ".TAR.MD5" file. That is the one that you require.
3). Attach your phone in “Download Mode”. To enter this mode, turn off your phone. Press and hold POWER + MENU (Home Button) + Volume Down keys. Then a confirmation dialogue will pop up and ask you to continue to enter the mode by pressing the Volume UP key.
4). Click on AP and select the “.TAR.MD5” file extracted.
5). Make sure only "Autoreboot" and "F.Reset Time" are "checked".
6). Flash the Firmware by clicking "Start".
7). Once flashed, let your phone reboot. Should take about 10-15 mins.
NOTE: If your phone doesn't boot up after a considerable amount of time. Turn it off. Pull out the battery. Re-insert the battery and boot your phone into “Recovery Mode” by holding the Power + Menu (Home Button) + Volume UP keys. Wipe your data and cache partitions.
8). Setup your phone but better not connect it to Google/Samsung/Dropbox or any other accounts because you are going to get those wiped again.
Part 2: Rooting Note 3 on 4.4.2 (Skip this is you have a Rooted 4.4.2 phone and move over to Part 3).
Procedure:
Before starting this find your kernel version and build number, the last 3 letters/digits matter such as NG1 or NH1, etc.
Install SUPERSU 2.46 APK
1). Run Odin v3.09 and connect your phone in “Download Mode”
2). Click AP on the ODin screen and navigate and select the file Root Kernel.
3). “Auto-reboot” and “F.Reset Time” are selected and click “Start”.
4). Let it flash and reboot.
5). Install Towel Root v3 Offline APK.
6). Open the Towel Root APK now and tap “Make it rain”.
7). Install SuperSU from Playstore.
8). Update the SU Binary and Disable KNOX.
9). Reboot your phone.
10). Now flash the Stock Kernel, Follow the same steps 1 – 4 but just replace the Root Kernel with the Stock Kernel to allow you to have full functionality as Wi-Fi gets disabled with the root Kernel.
Part 3: Upgrading to Android 5.0 Lollipop Dev Base Alexander OEA.
Procedure:
1). Install Mobile ODIN Pro 4.20
2). Move the N9005XXUGBOEA_DevBase_alexndr.zip to your Internal SD Card.
3). Run Mobile ODIN Pro and choose the option OTA/Zip Update.
4). Select the N9005XXUGBOEA_DevBase_alexndr.zip file.
5). Uncheck (untick) the “Everroot” Option.
6). Flash Firmware. If it asks to verify the checksum let it, if it does not then don’t worry.
7). Let Mobile ODIN Pro do it’s thing.
8). The Aroma Installer will pop up. Leave every option as-is. The only extra options we have to select are “Wipe Data” and “Update Stock Recovery”.
9). Let it install.
10). Uncheck (untick) the “Reboot Device” option.
11). If your phone reboots, then let it start up and then DO NOT set up your phone, just hold the power button and turn it off.
12). Enter “Download Mode”.
13). Run ODin v3.09 and click on BL and select the OEA Bootloader File and click on CP and select the OD3 CP File.
14). Make sure Auto-reboot is not checked.
15). Now, hold down the power key and turn off your phone.
16). Boot into “Recovery Mode” by holding the POWER + MENU (HOME BUTTON) + VOLUME UP keys. You will see a msg at the bottom Applying Multi-csc which is essential to prevent your phone from entering boot-loop or crashing after the Samsung LOGO.
17). “Wipe Data/Factory Reset” and “Wipe Cache Partition”.
18). Reboot your phone and set it up. But DO NOT install any app, my opinion or suggestion is not to connect your google account just yet.
19). After the phone has booted, open play store and connect your GMAIL Account and install Root Checker from Playstore.
20). Do not open any app and do not install anything.
21). Turn off your phone and wait for 2 – 5 mins.
22). Turn it back on and open Root Checker and grant it SU permission.
23). Then open SuperSU, update the binary if asked and set it up as you like.
24). Have fun, you now have a Rooted Lollipop 5.0 Phone on the latest Build Number OEAwithout Tripping KNOX
Updated and Maintained as of 19th June 2015.
Consider buying me a couple of beers for my contribution
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
I think my team has been able to come up with the solution.
patate331 said:
Nice job! I was waiting for this to update my note 3 to use new kernels. Is it possible to compile the same thing for n900w8, NB7 ? http://www.sammobile.com/firmwares/download/26653/N900W8VLUCNB7_N900W8OYACNB7_BMC/
Thanks a lot
Click to expand...
Click to collapse
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
XxXKINGMAKXxX said:
We are trying to figure this out. If we can get this kind of rom for any phone then we will have better luck getting all lollipop phones rooted. Also I'm in the process of getting the official stock firmware installed on top of this to allow us to have official kernel installed to. But I might just flash the original kernel to avoid the hassle and check it out
Click to expand...
Click to collapse
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
patate331 said:
Nice! Sounds very good. If I understand everything about your developpement, we will be able to root it but not to flash custom rom without tripping. Is that right?
Click to expand...
Click to collapse
Well yes. Flashing a stock rom with pre-root seems like the only case right now.
Sounds good enough for me! Awesome what you guys did, keep up the good work!
UPDATE
All variants (possibly) root knox 0x0
Thanks. worked like a charm. Just 1 suggestion. After point (14). Make sure Auto-reboot is not checked.) you can add "start odin flash" to avoid confusion. IMHO.
Yes very true. I will add it.
Also please note that I have tripped my knox in the learning process and will not continue any new guides regarding knox 0x0.
I'm quite satisfied and will now move forward towards hardcore development of Custom ROMS or development of stock ROMS with addition to more development of apps.
Check for new updates regarding new development apps that I am working on. I hope these apps become a game changer
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
sword_fish89 said:
thnks a ton KINGMAK.
Hey is there a way to saferoot stock Lollipop ROM rather than using the dev based one? Will u post a guide on that regardless of the post u added recently that u wont write guides on knox 0x0, since ur Knox is tripped I am eagerly waiting for that guide frnd.
Also, how to enable knox apps, container and all that on this dev based ROM? Is that possible?
If not, will I be able to use Knox apps, container in future? I suppose that a stock ROM should be flashed to get that. Is that?
Click to expand...
Click to collapse
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
XxXKINGMAKXxX said:
Yes it is possible. The dev_base is not entirely different from the Stock ROM. You would need to use the same procedure but the only change that would be required is the flashing of the Stock Based ROM.
I can make a rom with KNOX apps enabled but the root in the system will always remove/disable the KNOX apps since knox tries to reset the root.
Since the very beginning of KNOX system, the security is lost when you root your device. KNOX cannot be used and I doubt anyone will ever try to make them work.
Sincerely,
KINGMAK
Click to expand...
Click to collapse
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
sword_fish89 said:
So that means should I add Stock rom from sammy (BOB6.zip) in Mobile Odin pro as mentioned in step 4. of part 3 instead of N9005XXUGBOB6_DevBase_alexndr.zip file?
If so, do i need to flash BOB6's bootloader and modem again via desktop Odin? Plz clarify..
Click to expand...
Click to collapse
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
erevoz said:
if i already trip my knox 0x1 can it be changed to 0x0 with this method?sorry newbie question
Click to expand...
Click to collapse
No. This is to preserve 0x0. It won't change 0x1 to 0x0.
arvin2212 said:
Thank you. Followed your guide and managed to get Lollipop into my phone with root privileges. Flashed Xposed alpha via mobile odin and now my phone is stucked in a bootloop. Went to recovery to do a factory reset but it is still the same. What should I do to restore my phone?
Would it be fine following part 1 and 2 , although I am running the newest bootloader?
Click to expand...
Click to collapse
Flash the CP and Bootloader files. Then wipe your data and cache partitions am all should be fine.
Once the whole setup is complete and i wanted to debloat the rom, can i just install thru mop the dev base rom? Is it necessary to do the bl and cp again?
XxXKINGMAKXxX said:
Well you can flash the stock rom zip package of OB6 and it might b necessary to flash the bootloader too since it has been reported that if people don't flash the OB6 bootloader they end up with bootloop issues.
Click to expand...
Click to collapse
Thnx for the reply KingMak. But i hav few mre doubts.
1. Suppose if i use stock rom bob6.tar.md5 in mobile odin, how do we get that Rom rooted?
Should i tick everroot option and add supersu zip file and then flash to do that?
2. Does dev base (by alexndr) zip package include root installer? Is everroot option unticked for this reason?
3. Can we saferoot(knox 0x0) note 3 sm 9005 using the same method for s4 as posted by xda member Tyxerakias? Plz have a look>> forum.xda-developers.com/galaxy-s4/general/rooted-stock-lollipop-5-0-1-knox-0x0-t3061536
Samsung Galaxy Core Prime
Virgin Mobile
SM-G360P G360PVPU2AOH1
I have found a way to root this version of the device. Easy as pie.
1. Factory Reset your device.
2. After reboot, Power OFF device.
3. Boot into Download Mode
HOLD VOL ( - ) & POWER & HOME BUTTON
RELEASE HOME BUTTON when letters appear
PRESS VOL (+ ) to ACCEPT TERMS
4. Flash the CF-AUTO-ROOT.tar.md5 using the ODIN that is provided.
5. Reboot and let CF do it's thing (my device restarted maybe 3x)
When phone finally boots, you should be fully ROOTED. I updated SU, and installed a few Apps that require ROOT and everything is smooth. No Force Close, nothing.
Odin + CF-Auto-ROot:
http://www.mediafire.com/download/86y6nzbhms9fr7q/CF-Auto-Root.rar
If you need to completely reflash your device the 1GB+ file for ODIN is available.
Google is your friend.
Is there a working Custom Recovery for these? I believe the recovery is the same across all the variants,
here is one from the G360PVPU2AOH1 SM-G360P Model:
Recovery (stock)
http://www.mediafire.com/download/u44h4d02ss73w41/recovery.img
Boot Image (stock)
http://www.mediafire.com/download/3rdapre7dr4ia8r/boot.img
Hope this helps someone, I am attempting a TWRP 2.8.0.1 build for this, although I am not sure I know what I am doing.
these helped me a LOT but unfortunately i no longer have the files and my phone is currently a bit bricked du to some unrelated stuff, could you please update these links? email me if you do [email protected]
I used the s820l straight talk twrp 2.8.7....you can search developer Ardwill...my apologies i forgot the ending 2 numbers on his name....but search root deodex rom for your sm-g360p prevaile lte/ core and he has as have i on two prevail ltes booted thru odinbthe straight talk 820 s twrp port..flashes precompiled apos as well as zips to improve performance and even su....the rom has being rooted has a problem updating from settings but with twrp you can systemless root....pm me for both twrp and cfautoroot file...they are linked to my drive actually ....https://drive.google.com/file/d/0B9Nvxp8BpgclellYTmtEMnd1ZzQ/view?usp=drive_web...thats twrp found working by Ardwill all credits go to him as i never would of had a custom recovery....and cfautoroot is universal ...dwnld the file named after coreprime....thats the only coreprime that actually flash...possibly since the twrp will not format data.....ive done all i can to give my way of having twrp and root...both phones still work and never looped...twrp only needs root after its flashed...but ask Ardwill or better yet look up his thread on his stock deodexed and prerooted rom...i run it on my cracked one and its just fine ...but i only used twrp then cf autoroot after i flashed recovery via odin and accepted latest update....so props to chainfire for his cfautoroot working across all versions of this non existent variant of the Sm-g360p. Always perform a wipe via twrp before flashing ne thing..dalvick and cache only tho....have fun doing all the exploits that kitkat 4.4.4 has ....latest uodate past smg360pvpaoj2 will not flash xposed nor can you update firnware...so i woudnt run the stock basemodel past apj2 since all you get is a securiry patch update..also i believe twrp will format if you do it properly...i made the mistake not the dev who was ballsy enough to flash a twrp buikt fir a diffrent carrier.
Sent from my SM-J327P using Tapatalk
my bootloader isnt unlocked so i dont think i can flash twrp, i just installed the cf autoroot you posted last time and i cant find any other root for this device that actually works so if you could get that file for me that would rock
If ur root already theres no point
....i mean its not logical...what other root are u talking of?? Like a swich from supersu to another superuser.....i just ask
1. So u dont trash ur phones internals
2. What roots better than cf auto?? It comes with superuser.apk
3. One clicks are netorious for unreliability...why there are tools to clean them up anx install chainfires su binary over them...not vice versa for a reason...and Ardwills roms are prerooted with chainfire su...so u might wanna 4get about another root or w.e u were gettin ay
Sent from my SM-J327P using Tapatalk
If i have a different software version....... is that a problem? (Dont laugh me noob)
Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Now, I'm here to try to bring this same method to you guys! With the help of @jrkruse, here are the root instructions:
How it works:
These engineering firmwares are usually based on KitKat, and have their SELinux set to PERMISSIVE. This not only leaves the firmware very vulnerable to towelroot, but it also keeps SELinux from raining on our parade.
Thanks again to @jrkruse for the updated root instructions, and @mohammad.afaneh for the Safestrap!
Revised October 6, 2018.
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under "CID"
If the first two digits are "15," your bootloader is unlockable and you can install TWRP/AOSP ROMs.
If the first two digits are "11," your bootloader is not unlockable, but you can use rooted Lollipop ROMs that are based on TouchWiz (with the help of SafeStrap). You can also use non-rooted Marshmallow ROMs (based on TouchWiz) and flash mods with SafeStrap.
BACK UP YOUR STUFF NOW, YOUR STORAGE WILL BE WIPED!
If your eMMC CID starts with "15," start here:
1. Download and unzip this file: EMMC_15_Root_Bootloader_Unlock S5_QB2_PB1.zip
2. Reboot the phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the "COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5" firmware in the AP Slot
4. Flash and let the phone process the file. It will reboot twice and you should be dropped into Android within a minute and a half.
5. Copy the following files to your phone:
"RootS5" Folder and "EMMC_15_SafeStrap_QA1_6_0_1_MM_Bootloader_Unlock_AIO.zip",
and EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery choose install and select EMMC_15_SafeStrap_QB2_6_0_1_MM_Bootloader_Unlock_AIO.zip
13. Install the zip. The phone will power off. Reboot the phone to TWRP Recovery with Pwr+VolUp+Home
14. You will now have an Unlocked Bootloader and TWRP recovery Installed. Now whoose Wipe > Advanced Wipe. Select Dalvik Cache; Data; System; Cache, and swipe the swipe to wipe bar. When done, click the back button, click Install, and choose:
EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip
You're done! You will have stock rooted Marshmallow QB2 Build installed with an unlocked bootloader and custom recovery.
If your eMMC CID starts with "11," start here:
1. Download and unzip this file: EMMC_11_ Root S5_QB2_PB1.zip
2. Reboot Phone to Download Mode (Pwr +Vol Dwn+Home)
3. Use Odin 3.12 and load the COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot.
4. Flash and let the phone reboot. It will reboot to recovery and finish install then it will reboot and take about 20 seconds to boot.
5. Copy the following to the phone:
Root S5 Folder, EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip, EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip, and the TouchWiz ROM you want to install.
6. Use the File Manager (you can find it in the app drawer) to install Superuser.apk, Busybox.apk, tr_v2.apk, and SafeStrapKK.apk . Do not open anything yet.
7. Open towelroot and click "MAKE IT RAIN". It should tell you you have succeeded. Otherwise, reboot and try again.
8. Now open SuperSU and click "New User" to install it.
Once done, open SuperSU and update the SU binaries using the "NORMAL" method. It will tell you you need to reboot, but you can skip that. (If the Superuser install hangs for more than 5 minutes reboot phone and try to install it again.)
9. Now open the BusyBox app, grant SuperSU access and install BusyBox.
10. Now open SafeStrap, grant SuperSu access and click "install recovery". If the SafeStrap recovery fails to install, make sure BusyBox is installed by rerunning the BusyBox app (it will tell you if BusyBox is installed). If its not installed, click "install" again, reboot the phone, re-open SafeStrap and try to install recovery again
11. Once SafeStrap Recovery is installed click "reboot to SafeStrap Recovery".
12. Once in SafeStrap Recovery, choose what firmware you want to be on:
Lollipop 5.0 Firmware=EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip
Marsmhallow 6.0 Firmware=EMMC_11_QA1_6_0_1_MM_Firmware_Bootloaders.zip
13. Install the firmware zip, and then flash a TouchWiz Lollipop ROM. (Here is the latest stock rooted Lollipop Rom: VZW_BPB1_ODEX_DEODEX_V9.zip). You may want to download a copy of the latest SuperSu zip, and flash if installing a Lollipop ROM that is not rooted. Remember that you cannot root Marshmallow ROMs, so do not try and flash the SuperSu zip on a Marshmallow Rom (you will softbrick if you do).
14. After you install any Lollipop ROM, you may need to reinstall SafeStrap Recovery. Most of the time you don't have to and SafeStrap can be reached by flashing the KitKat Kernel in Download Mode with ODIN. But, in some cases, when flashing a ROM that flashes a system.img instead of a system folder, you may lose SafeStrap during install. This will be the case if you install the above ROM. You can reinstall it after the ROM is booted up. A Safestrap-G900V-4.04_LL_MM.apk is included that will flash a version of SafeStrap that will allow you to reboot to SafeStrap Recovery without flashing a KitKat kernel in Odin. Install BusyBox again from the BusyBox App in the RootS5 Folder. Install Safestrap-G900V-4.04_LL_MM.apk and make sure to grant SuperSU access. It may take a few seconds to prompt. If SafeStrap is not installed, click "Install Recovery". If Safestrap is still installed click on "Uninstall Recovery", close the app, and reopen it. It should say recovery is not installed. Now click on "Install Recovery". If this doesn't work, reboot the phone and try again. Once installed, you can just click reboot to SafeStrap from the SafeStrap app and you will reboot straight to SafeStrap. Remember to flash the appropriate Kernel when leaving SafeStrap!
Download and place these on your device:
LL_KERNEL_SS-FF_Flashable.zip, and
MM_KERNEL_SS-FF_Flashable.zip
If something goes wrong you can usually get back to SafeStrap by simply rebooting the phone to Download Mode and flashing NI2_stock_kernel.tar.md5. When the phone reboots, watch for the SafeStrap splash screen and enter SafeStrap.
WARNING: Do NOT change ANY boot options in SafeStrap. ROM slots cannot be used, so you must flash to the Stock ROM slot EVERY TIME OR YOU WILL SOFTBRICK. Some functions don't work in SafeStrap, like choosing an image file to flash directly. All image files must be flashed via zip file.
For CID11 users that have followed the above instructions and want to use Marshmallow:
QA1_MM_Firmware_With_QA1_Bootloader_CAUTION.zip=Marshmallow Firmware (use if flashing a MM TW ROM other than the one posted below). Just remember there is no root for Marshmallow ROMs, but having SafeStrap installed gives you the ability to do things like flash debloat Scripts, Mods, etc and the ability to go back to a rooted Lollipop ROM without going through the root process all over again. Simply flash the Lollipop ROM and EMMC_11_PB1_5_0_1_LL_Firmware_Bootloader.zip.
Here is a special ROM that includes SafeStrap, so you can flash a Marshmallow ROM and still be able to use SafeStrap to flash things. You will not have root but you can still access SafeStrap. VZW_QB2_STOCK_SAFESTRAP_ONLY_V1.zip More Instructions about this can be found HERE
When using a MM ROM, it is necessary to flash the KitKat Kernel with Odin to enter SafeStrap. When leaving SafeStrap, make sure to flash MM_KERNEL_SS-FF_Flashable.zip which is necessary to leave SafeStrap (This zip will be placed on storage automatically with the above ROM and you also download it in instructions above.) Just navigate to the .MM_KERNEL_SS-FF folder located on both Internal and External storage.
i'll odin my spare s5 to stock later if i get the chance and let you know if this works on my g900v.
The methods in post 1 are seriously outdated the easiest method to obtain unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
its uploading sorry it failed at 99 percent
jrkruse said:
its uploading sorry it failed at 99 percent
Click to expand...
Click to collapse
Thank you! very much appreciated
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
Its uploaded
jrkruse said:
Its uploaded
Click to expand...
Click to collapse
Downloading as we speak. I will let you know how everything goes!
tested on one of the spares I had kicking around
does what it says on the tin
!kickass
The apps are kind of hard to see in the App Drawer I installed View attachment Apex_Lancher.apk and it gets rid of that Info screen covering the Apps
The OP has been updated to reflect @jrkruse 's new instructions
AptLogic said:
The OP has been updated to reflect @jrkruse 's new instructions
Click to expand...
Click to collapse
I just cleaned them up a little I'll Pm you the changes
---------- Post added at 08:22 PM ---------- Previous post was at 07:32 PM ----------
jacob0298 said:
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...
Click to expand...
Click to collapse
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
jrkruse said:
This does not unlock bootloaders for CID11 people. There will probably never be a bootloader unlock for those people unless the Verizon S5 gets one from Samsung as it grows old and irrelevant.
Click to expand...
Click to collapse
Which, I should add, has about a 1 in 10,000,000 chance of occurring.
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used: (one linked in original thread)
http://org.downloadcenter.samsung.c...NG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
guitar1238751 said:
I was able to successfully flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_2572656_REV00_user_mid_noship_MULTI_CERT.tar.md5 in the AP Slot
After it rebooted to system , I am unable to get the phone to be recognized by windows. When I plug it in I hear the beep that it's plugged in charging, but I cannot find an option for file transfer on the phone itself. I tried a couple different Samsung drivers on Windows but to no avail. Does anyone know why this is happening or how I can get it to connect to the pc?
This was one of the drivers I used:
Click to expand...
Click to collapse
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
AptLogic said:
Try rebooting the phone and the PC. I've had that happen before and usually that fixes the problem.
Click to expand...
Click to collapse
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
guitar1238751 said:
Yup I've tried that a few times. I even went back to download mode, redid the process and booted back to system, still couldn't get it to connect.
Click to expand...
Click to collapse
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
AptLogic said:
That's peculiar... Have you tried another cord? Otherwise you'll have no choice but to take out the SD card and plug it into the PC manually.
Click to expand...
Click to collapse
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
guitar1238751 said:
I'll try it again with another cable and laptop. If it still doesn't work I'll copy it directly to the SD card. This is my friend's phone. I'm in class now so when I see him later I'll continue the steps and let you know what happens. Thanks
Click to expand...
Click to collapse
Happy to help
["QUOTE=AptLogic;71212479]Happy to help [/QUOTE]
if some one help me
i have Samsung Galaxy S5 ( DOCOMO Galaxy S5 sc-04f ) with marshmallow 6.0.1
i want to root my device with
cf auto root
but which thing is install first twrp or root
please guide me srep by step
thanks
MobileSTRixS said:
if some one help me
i have Samsung Galaxy S5 ( DOCOMO Galaxy S5 sc-04f ) with marshmallow 6.0.1
i want to root my device with
cf auto root
but which thing is install first twrp or root
please guide me srep by step
thanks
Click to expand...
Click to collapse
You can start with either one. If there is a CF autoroot or TWRP for your device then there should be instructions for how to do it in the thread where you get them from. Follow those instructions, it isn't rocket science.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Root and twrp
What should i do first
Root or twrp
Need help here
Sc-04f docomo
Uncheck Auto Reboot from options in odin
flash twrp
-phone won't reboot-
once done remove battery
put it back
press vol up + home + power
Help here
Ok
Then twrp install after i root
With odin or else
I have download file cf auto root from official website for my supported model number
But stil confuses about which thing i install first
Twrp
Or root
There are two types of root
Cf auto root and super su
Some youtube videos show me twrp install odin on download mode
Then install twrp custum recovery then install zip file of super su
But still confused about cf auto root file of my device
Is also available
Which thing i do first
With step by step
Plz guide me
You would install TWRP. boot the phone root it and then power off boot into recovery and flash SuperSu. I'm pretty sure this is how it's done I've not done it myself yet but I've been reading up on it alot can anyone confirm this?
MobileSTRixS said:
Ok
Then twrp install after i root
With odin or else
I have download file cf auto root from official website for my supported model number
But stil confuses about which thing i install first
Twrp
Or root
There are two types of root
Cf auto root and super su
Some youtube videos show me twrp install odin on download mode
Then install twrp custum recovery then install zip file of super su
But still confused about cf auto root file of my device
Is also available
Which thing i do first
With step by step
Plz guide me
Click to expand...
Click to collapse
Use twrp root method its safer
SuperSU.zip
---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------
Nickh90 said:
You would install TWRP. boot the phone root it and then power off boot into recovery and flash SuperSu. I'm pretty sure this is how it's done I've not done it myself yet but I've been reading up on it alot can anyone confirm this?
Click to expand...
Click to collapse
Flash twrp with Odin > boot into twrp directly > flash SuperSU
-Hope- said:
Use twrp root method its safer
SuperSU.zip
---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------
Flash twrp with Odin > boot into twrp directly > flash SuperSU
Click to expand...
Click to collapse
Yeah thanks. My wording and terminology was a bit off but I got the point.
if any one know or experience that root Samsung docomo galaxy s5 sc-04f with marshmallow 6.0.1
i also watch youtube about s5 root + twrp + xposed firmware
but still confused different method or old method save on youtube like lollipop
but my device have marshmallow 6.0.1
i want to root my phone
i visit cf auto root website
samsung SC-04F SC-04F SC-04F MSM8974 msm8974 MMB29M.SC04FOMU1XQH1 6.0.1
i also download twrp for my device and that file at my pc
https://twrp.me/devices/samsunggalaxys5qualcomm.html
but still confuse
i also install twrp because i need to install xposed firmware for my samsung device and the twrp is must
please guide me
i want to root my device and install twrp and xposed firmware
which thing install first second and third
please guide me step by step
#root
#twrp
#xposed firmware
need help here
please
MobileSTRixS said:
if any one know or experience that root Samsung docomo galaxy s5 sc-04f with marshmallow 6.0.1
i also watch youtube about s5 root + twrp + xposed firmware
but still confused different method or old method save on youtube like lollipop
but my device have marshmallow 6.0.1
i want to root my phone
i visit cf auto root website
samsung SC-04F SC-04F SC-04F MSM8974 msm8974 MMB29M.SC04FOMU1XQH1 6.0.1
i also download twrp for my device and that file at my pc
https://twrp.me/devices/samsunggalaxys5qualcomm.html
but still confuse
i also install twrp because i need to install xposed firmware for my samsung device and the twrp is must
please guide me
i want to root my device and install twrp and xposed firmware
which thing install first second and third
please guide me step by step
#root
#twrp
#xposed firmware
need help here
please
Click to expand...
Click to collapse
These things that you are mentioning have instructions in the places that you are finding/reading them. Try reading those instructions and doing what they say to do.
Installing TWRP and rooting have already been explained to you and you are still asking. Installing Xposed is just one more step. There are guides for how to do all of this everywhere. Try paying attention or you will regret it because you will destroy your device.
Are you even paying attention to what they are saying to you? Are you even trying to understand what you are reading in the threads and videos that explain how to install them?
You aren't asking "how to do it", you are wanting someone to do everything for you instead of using your own brain.
If your bootloader is locked then you can not flash TWRP, you will have to flash CF autoroot in Odin the same way that TWRP is flashed in Odin. The process is basically the same, only the file that is used is different.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hey everyone,
I can't root my device which is the same Galaxy S5 (SC-04F) the problem I am facing during the root is that when I try to flash TWRP from odin everything goes well but my phone doesn't detect the SIM instead I see "No sim | Insert Sim card" same goes with cf_auto root it doesn't detect the SIM card.
I really want to flash a custom rom Iam bored of the stock. Iam running the latest stock update 6.0.1 with August security patch level.
I have tried flashing the modem.bin by converting it into .tar file but no luck.
Any help will be appreciated...
Did you open the developer option and enable the usb debugging and oem ?
vachon18 said:
Did you open the developer option and enable the usb debugging and oem ?
Click to expand...
Click to collapse
They aren't having a problem flashing the device, they are having problems detecting SIM when it boots up after flashing.
Sent from my LGL84VL using Tapatalk