Hello, I have tried every root on the internet for my samsung galaxy s3 spring android 4.3 and I have the cwm installed and working, and I can flash without the error that you cannot mount the sdcard. I have tried every root and it still says that my phone is not rooted, through root checker and supersu also says that it is not rooted. Please, help! I've used the instructions at www . epiccm . org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I am very frustrated with this, and am about to give up. Please help.
Thanks.
-1998golfer
When i open supersu (i donwloaded it from the app store) it says:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!"
Try flashing THIS in Recovery.
Try the repository for a odin one click @ http://rwilco12.com/
prboy1969 said:
Try flashing THIS in Recovery.
Click to expand...
Click to collapse
Nope. Didn't work =/ Still says I do not have root access in root checker.
still not working
Drennan said:
Try the repository for a odin one click @
Click to expand...
Click to collapse
I can't find what you're talking about but I tried all of the superuser flashable zips (supersu, superuser, and MIUI. None of them worked. They said updating android when I booted, but it still doesn't show as root. It tells me no su is installed and then KNOX comes up telling me that it tried to access a secure area.
Please help
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
How do i disable knox. I've stopped all the processes and even (tried to) delete all the files pertaining to it. i dont have permission to do so. I tried terminal emulator and it doesnt let me do it.... i type su and it tells me i dont have permission. ive tried flashing zips that claim to disable knox and they dont work.
Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
I tried installing superuser.apk using that explorer and it installed. it doesnt ask about knox nor does it mention it... Nothing people suggest seems to help =/
Please... Anyone know what to do?
1998golfer said:
Please... Anyone know what to do?
Click to expand...
Click to collapse
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.
Mr. Struck said:
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.
Click to expand...
Click to collapse
Didn't work
1998golfer said:
Didn't work
Click to expand...
Click to collapse
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk
Mr. Struck said:
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Cwm - the version for new s3's
1998golfer said:
Cwm - the version for new s3's
Click to expand...
Click to collapse
I would highly recommend switching to Philz Touch recovery, then starting over with flashing the most recent SuperSU zip. Once you boot back into system, open the SuperSU app, choose yes when it asks if you want to disable Knox, and then let it update the binaries for you via the TWRP/CWM option.
This is the repository thanks to @rwilco12, http://rwilco12.com/ in case if the above option doesn't work. Odin down to a rooted jb, then flash a recovery I use Philz Touch (cwm based) and it works flawless, then choose a ROM. Also able to restore cwm or twrp. Be sure to clean install ROMs and always nandroid.
Good luck. I also recommend using philz. Although this process can be frustrating at times, these members @xda are amazing and will get where you need to be. Again, good luck.
Jessooca said:
These guys are definitely leading you in the right path.
From stock on the latest update. I used CF Auto-Root for the Sprint S3 by chainfire in Odin.... uncheck everything.... then after it's flashed take out your battery and boot into recovery and flash the latest supersu zip file then reboot after it reboots open Supersu and it should ask you if you'd like it to disable Knox.
This is what I did it worked for me with no issues
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?
1998golfer said:
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?
Click to expand...
Click to collapse
Yes, Odin rooted MK3. Use the Knox Removal in this post after Odining a custom recovery-http://forum.xda-developers.com/showthread.php?p=47812894
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I do,
Download stock rooted deodexed ram from this site, also download knox app remover, also download wifi fix.
Load TWRP 2.6.3.0 Recovery. Flash that using odin.
Reboot to recovery (TWRP)
Having the stock ram on the SD card or the internal storage .. install it than before rebooting install knox app remover and wifi fix and boot..
Make sure than to update the supersu and all should be good.
I hope this helps.
Related
Hey guys,
i'm new here and i hope, that you can help me with my problem!
I've tried to root my Samsung I9192 S4 Mini DuoS, which is 4.2.2 and XXUBNB1.
I flashed the Custom Recovery (recovery-clockwork-6.0.4.5-serranoltexx.tar.md5) via Odin and after that, I've installed the S4Mini_RootKit_v2.zip via CWM Recovery.
SuperSU is installed, but if I check my root permisson, the message is, that i havent any root rights, although I installed the S4Mini_RootKit_v2.zip.
I can't understand it! I know that KNOX is the problem, and i dont know how to remove it. I've tried a lot of methods, like remove the KNOX files via ES Explorer, but it doesn't work! :crying:
My question: How can I root my Samsung I9192 S4 Mini DuoS with Android 4.2.2 and Built XXUBNB1?
Can I flash the Custom Kernel called "Amestris Kernel V2 for Samsung Galaxy S4 mini Duos (GT-I9192)" which is based of
MK4 on my I9192 with NB1?
THANK YOU!
AND SORRY FOR MY BAD ENGLISH
Follow this guide http://forum.xda-developers.com/showthread.php?t=2494435
Powered by CM11 - M6 snapshot
R_a_z_v_a_n said:
Follow this guide http://forum.xda-developers.com/showthread.php?t=2494435
Powered by CM11 - M6 snapshot
Click to expand...
Click to collapse
Thank You!
I follow the steps but i havent got any root permisson, although SuperSU is installed.
What can I do? Can i install the Amestris Kernel V2 for GT-I9192 via Odin (based on MK4) on my I9192
with NB1 ? KNOX is the problem, I Can't unistall it. But this Custom Kernel can deactivate it...
007lou said:
Hey guys,
i'm new here and i hope, that you can help me with my problem!
I've tried to root my Samsung I9192 S4 Mini DuoS, which is 4.2.2 and XXUBNB1.
I flashed the Custom Recovery (recovery-clockwork-6.0.4.5-serranoltexx.tar.md5) via Odin and after that, I've installed the S4Mini_RootKit_v2.zip via CWM Recovery.
SuperSU is installed, but if I check my root permisson, the message is, that i havent any root rights, although I installed the S4Mini_RootKit_v2.zip.
Click to expand...
Click to collapse
Neither I could achieve root on I9192UBUAMH1 doing the arco method. Also Saferoot failed.
I then flashed PhilZ Touch CWM Advanced Edition, reflashed stock ROM, boot into Recovery and select "PhilZ Sttings" --> "Re-root System (SuperSU)"
That did the job for me.
aguaz said:
Neither I could achieve root on I9192UBUAMH1 doing the arco method. Also Saferoot failed.
I then flashed PhilZ Touch CWM Advanced Edition, reflashed stock ROM, boot into Recovery and select "PhilZ Sttings" --> "Re-root System (SuperSU)"
That did the job for me.
Click to expand...
Click to collapse
did you re-flashed your Stockrom in the Custom Recovery or via Odin?
Can I flash the PhilZ Touch CWM Recovery over my Clockwork-recovery and do "Re-Root system", without reflash stock rom????
007lou said:
did you re-flashed your Stockrom in the Custom Recovery or via Odin?
Click to expand...
Click to collapse
I flashed system.img.ext4 (extracted from Stock firmware) with heimdall after I had wiped the ROM with PhilZ Touch CWM.
I think you should be able to achieve the same with Odin instead of heimdall.
007lou said:
Can I flash the PhilZ Touch CWM Recovery over my Clockwork-recovery and do "Re-Root system", without reflash stock rom????
Click to expand...
Click to collapse
Yes, it might work w/o re-flashing system. In my case I just wanted to make sure there were no leftovers from my previous attempts with arco/saferoot.
Here is a quick summary of all attempts I did:
- arco recovery --> works
- arco root --> fails
- saferoot --> fails
- PhilZ touch --> works
- clean ROM with PhilZ touch --> works
- re-flash Stock ROM (only system.img.ext4) --> works
- re-root with PhilZ touch --> works
aguaz said:
I flashed system.img.ext4 (extracted from Stock firmware) with heimdall after I had wiped the ROM with PhilZ Touch CWM.
I think you should be able to achieve the same with Odin instead of heimdall.
Yes, it might work w/o re-flashing system. In my case I just wanted to make sure there were no leftovers from my previous attempts with arco/saferoot.
Here is a quick summary of all attempts I did:
- arco recovery --> works
- arco root --> fails
- saferoot --> fails
- PhilZ touch --> works
- clean ROM with PhilZ touch --> works
- re-flash Stock ROM (only system.img.ext4) --> works
- re-root with PhilZ touch --> works
Click to expand...
Click to collapse
THANK YOU SO MUCH!
I will try it out today, but I have still a little question:
Does the PhilZ touch Recovery root my phone without any Zip file, i mean automaticly???? And does it works (with KNOX and with 4.2.2)?
Use saferoot,
But I the Knox notifications was preventing root access just force close all knox related apps on applications manager then open supersu, worked for me,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you have cwm recovery you have all you need
Solution 1) mount system and use aroma file manager to delete all the Knox related apps then reboot and update supersu,
Solution 2) You could also flash a rom cleaner script to delete all bloatware including Knox stuff reboot and update super su
Sent from my GT-I9192 using Tapatalk
007lou said:
I will try it out today, but I have still a little question:
Does the PhilZ touch Recovery root my phone without any Zip file
Click to expand...
Click to collapse
Yes, the re-root option of Philz CWM did that in my case. At least so I was able to run 'su' when in adb shell. You might have to install SuperSU additionally for running Android root apps.
I'm not on Knox, so I'm not of much help there. As far as I understood though, it doesn't prevent you from any rooting but will set a flag when you flash any custom firmware. By applying the arco root I guess you've triggered that flag already though. As fburgos said the Saferoot way should not trigger that flag, but it failed to run on my device.
007lou said:
THANK YOU SO MUCH!
Click to expand...
Click to collapse
Don't say that, just hit the "Thanks" button
aguaz said:
Yes, the re-root option of Philz CWM did that in my case. At least so I was able to run 'su' when in adb shell. You might have to install SuperSU additionally for running Android root apps.
I'm not on Knox, so I'm not of much help there. As far as I understood though, it doesn't prevent you from any rooting but will set a flag when you flash any custom firmware. By applying the arco root I guess you've triggered that flag already though. As fburgos said the Saferoot way should not trigger that flag, but it failed to run on my device.
Don't say that, just hit the "Thanks" button
Click to expand...
Click to collapse
I have a new problem, my Phone doesn' have Connection of mobile Data, so i can't use Internet outside (wifi works). I have checked the APN but its all right. The phone accepts the sim card, but i cant use the mobile data
What can I do?
Dear All,
I tired to root my devise Samsung GT-I9192 build I9192XXUBNB1 but I couldn't I tried Odin and Kingo from PC. I want only to root my phone not to install any custom rom
[Q] Rooted SPH-L710 with ODIN & CF-Auto-Root, Root Checker shows NOT rooted. HELP?!
I have had my Sprint Samsung Galaxy S3 for about a year now, and finally decided to give root access a try on the phone. I followed all of the step-by-steps tutorial, that Chainfire posted on his ([SPH-L710] CF-Auto-Root) thread, and have run into an issue. ODIN shows that the rooting procedure has passed, and the red android dude popped up, and the phone rebooted. Anytime I turn on my device, I immediately receive the notification that "unfortunately, SuperSU has stopped working". And running the app "root checker" returns the message "sorry! this device does not have proper root access". I went into download mode, and the flash counter shows that I have 1 custom rom/binary, whatever its called, and that my phone has the custom rom/binary status. I did some researching on the forums and threads, and it would seem that there's no clear cut way to fix this issue; given my phone's specific state. I don't want to brick my phone, so I need an experts solution! Thanks a million in advance!
If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery
Reply
thenexusgeneration said:
If you want to leave root alone, you can reflash stock 4.4.2 is in Odin. But if you want to try to fix root you can flash a custom recovery is in Odin so you can flash an update to superuser using the custom recovery
Click to expand...
Click to collapse
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.
Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Have you tried this:
Go to the Google play store and find supersu. It should give you the option to "update" (versus "install")
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
All it says is" open". That's the only option on the Google play store.
Jayhawker69 said:
I would like the keep the phone rooted (which it has an issue with)....so as for fixing the root, by flashing a custom recovery....where do I find the custom recovery, and how exactly do I do this in ODIN, to specifically update superuser?
**NOTE: I downloaded a different superuser app on the google play store, (which will obviously not be saved/stored to system/app, like chainfire's SuperSU app is) and when I opened the Superuser app, it returns a message "SuperSU binary is out of date". I'm not sure what this means exactly, but maybe it might mean something to you, haha.
Click to expand...
Click to collapse
If you're looking for;
Odin
http://odindownload.com/
Philz
http://d-h.st/users/philz_touch/?fld_id=25216#files
SuperSU (zip)
http://download.chainfire.eu/396/SuperSU/
But as suggested try opening supersu first. Mine would fc, so I just flashed the supersu file above, from philz recovery.
I would also suggest Uninstall in the other su app. They never played well together (for me)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Jessooca said:
Open it and if prompted select normal if it asks Normal or twrp/recovery
Click to expand...
Click to collapse
Any time I try to open it, it force closes with the message "unfortunately, SuperSU has stopped."
Reply
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck
If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Thanks a million!!
roirraW "edor" ehT said:
If you're ND8 or NDC bootloader, the only completely working custom recovery is the very latest Philz Touch Recovery.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett
Jessooca said:
restart your computer and redownload odin
Everytime I try to flash the twrp recovery, windows error reports pops up and says "ODIN communicator has stopped working and needs to close." I have noooo idea. Why is it doing this! I have the worst luck
Click to expand...
Click to collapse
[/QUOTE]
Thanks for your help as well, much appreciated.
You're welcome and cheers right back from Columbus, Ohio. ☺
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
I need help toooo!
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.
thank you!
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:
Kalen_Christian said:
thank you! that worked like a charm. however, i really wanted some free tethering, but it looks like kitkat won't allow FoxFi to do it! a pop up comes through about subscribing to the service. I installed SlimKat, and I hate it. It's fast and I can do the free tethering, but it's so ugly. I want to go back to my rooted kitkat. What should I do?
I don't think i made a correct back up. i thought i did, but i guess i didn't.
I'm downloading the official ROM for my SPH-L710 right now.
How can I return to a normal rooted kitkat?:good:
Click to expand...
Click to collapse
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You might want to check in philz for any backups. If you have 1 it's easy to reinstall. If not, then you would have to flash your stock tar in Odin. Then, flash philz and then root. The more you do it the easier it gets. But, make sure that you are not downgrading by trying to flash an older stock tar. Downgrading your boot loader will cause a hard brick...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks
**proper way to fix your problem!!**
Kalen_Christian said:
i've been having the same issue! thank you for working it out. i really want to complete the root, but im having trouble.
I'm very new to this stuff and I don't understand some of the instrutions.
could someone made make a clear cut instruction on how to do this?
I have an SPH-L710
I used Odin with CF- Auto Root.
When I try to open SuperSU, I get, "Unfortunately, Supersu has stopped." and I can't update it in Play. Just like OP.
I'm unfamiliar with recoveries and how to install them. I have the latest philz touch and SuperSu Zips on my computer ready to go. I have odin 3.07.
If Jessooca could make a clear cut instruction that would be awesome. Or anyone really..I just need some help.
Oh, and my computer won't recognize my phone. It did for a moment, but It hasn't been working for the past hour.
Click to expand...
Click to collapse
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**
Kalen_Christian said:
I checked Philz out very thoroughly and I don't think I did it correctly. So, I have to put a fresh 4.4.2 on. When I do want to creat a backup for recovery, What app should I use? Also, What are the main apps for superusers? I don't want to download a bunch of stuff I don't really need.
Thanks
Click to expand...
Click to collapse
You would use philz recovery to make your backup. My apps that use root would be things like titanium backup, clean master, busy box. By going to the playstore and doing a search for root, you'll find apps that don't need root access but perform better when they have it...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Check this out !!!!
Jayhawker69 said:
Ok, first off....no offense to the poster 'Jessooca', but the steps she has posted to solve your issue are in part, slightly incorrect and misguiding. The following steps are *EXACTLY* how you should proceed, in order to fix the problem/issue you are having (the EXACT same issue I dealt with for the past two days) :
Step One:
IF you haven't done so already, download the Samsung Galaxy S3 USB drivers from the following link. This should solve your connectivity problem. Following the link below, scroll down just a little bit, and click on the downloads tab located just to the right of the 'Manuals' tab. Click on the blue box that says "EXE", and this should get the proper driver downloaded for your Sprint Samsung Galaxy S3. And obviously, install the downloaded driver after it completes the download.
Link:
http://www.samsung.com/us/support/owners/product/SPH-L710MBBSPR?CID=AFL-hq-mul-0813-11000279#
Step Two:
I know that you have stated that you have already downloaded the 'Philz Touch Recovery'.zip file....but there is a chance you may not have downloaded the proper file for your specific and exact handset. So, here is the link for 'Philz Touch Recovery' that you should download and use for this process. It should be a direct link for the download file. I'll post a second link that you should only use as an alternative, in the event that the first link does not work. IF the first link didn't work, then make sure you download the most recently uploaded version of the Philz touch recovery from the alternative link; should be Sun, July 6th...and also be sure to click on the download link (there's two separate links) titled "philz_touch_6.48.4-d2lte.tar.md5"...as it will be much easier to work with than the .zip file.
Link One:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
Alternative Link:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Step Three:
Now that we have the proper 'Philz Touch Recovery' file downloaded, you will need to download a different version of ODIN, as the 3.07 version you have will not suit our needs for this procedure. The link for the proper version of ODIN you will need is posted directly below. Download, extract it, and put the extracted folder somewhere on your computer that is handy or easy to find later. I'd suggest making a folder on your desktop from the very start of this procedure, and name it 'SPH-L710 Root Files', or w/e works best for you. Save all the files, or move all of the files you might have already downloaded at this point into that folder. Always nice to be organized and shizzz.
Link:
http://forum.xda-developers.com/attachment.php?attachmentid=581913
Step Four:
Alright, were getting closer to being done with this whole ordeal. Follow the link I have posted below, for the proper instructions on how to flash 'Philz Touch Recovery' in Odin to your device (the version of Odin we just downloaded from step three...obvi). Reading the instructions, you'll notice that it mentions that auto-reboot into recovery mode may not work properly after the file is flashed in Odin. This actually happened to myself....and seeing as how we have had the exact same problem with rooting our phones, I would suggest from the start, to uncheck the auto reboot option in Odin, and then manually boot into recovery mode after Odin successfully flashes the file to your phone. If you take my advice, and follow what I just said, your phone will still be in download mode after Odin flashes the file...assuming Odin says that the file successfully flashed ("PASS!"). From here, you will unplug your phone from your USB cord.....and now we will boot into the recovery file/mode we just flashed. To do this, HOLD down in this order: the Volume Up button + the Home key + the Power Button....continue to hold all 3 of these buttons down until the phone enters into recovery mode...you will be able to tell when you are in recovery.
Link:
http://forum.xda-developers.com/showpost.php?p=39433857&postcount=4
Step Five:
Ok, so hopefully if you did everything right to this point, and some other unforeseen issue has not arisen, you should be in Philz Touch Recovery Mode. Click on "PhilZ Settings" or "Advanced" , I can't remember for sure which one it is....but I'm almost positive it's in "PhilZ Settings"...click that option first. Within this settings menu, click on the option titled "Re-root" and click yes to proceed. After this is done, go back to the main menu and click on the "Reboot system/device" option on the very top.
Step Six:
Your phone should now boot up normally into your phones operating system/shell. Go to the Google Play store and search for and download an app called "Root Checker". Open the Root Checker app and click on the verify button. If everything worked properly, and if baby raptor Jesus loves you, the Root Checker will return the result that your phone has been properly rooted and you have root access/privileges. Now, go back to Google Play Store and download the "SuperSU" app....if it isn't already still on your phone (I had to re-download it). Open SuperSU from your apps menu/drawer and it might ask you to update the SuperSU binaries...mine did....and click on the normal method option, instead of the recommended option for HTC devices. SuperSU should update binary and your problems should all be melted away like butter by now.
** THIS IS THE EXACT SOLUTION(S) I TOOK TO FIX OUR SAME PROBLEM. I CAN'T GUARANTEE IT WILL WORK THE SAME FOR YOU, FOR WHATEVER REASON OR CIRCUMSTANCE THAT MIGHT BE. GOOD LUCK, YOU'LL DO GREAT KID :laugh::good:**
Click to expand...
Click to collapse
WILL TRY TO BE BRIEF....maybe...
ONLY did the whole QUOTE for the fact this works on newer formats 4.4.x.... (for now)...
IMO, this SHOULD out in the main thread or something.
Seems that just trying to use Chainfire Auto root does not work on 4.4.x...HOWEVER THIS does honestly work right the first time!!! Do need to add that I have tried Auto w/Odin (3.09/3.07/an 1.85) so many times it Nuckin' Futz....
OK, have been in same boat and working extremely hard and long on this issue (rooting SGS3 on 4.4.2) for the past week or so! I do really mean work on this issue. Have read an researched tons ...Starting w/4.3 to 4.4.x, as well as what is coming down the darn pike on this matter. Look up what Mr. Chainfire has posted in the last month... might get folks thinking twice on that new phone purchase, not just the cost, but what they end up with.
Anyway, I want to thank you....
Seems to me, the main thing that has kept me from rooting was this little tid-bit>>> "After it says "PASS" unplug and go right into RECOVERY from this point, (meaning from download mode right to recovery)"....as well as Once in Phliz recovery> RE_ROOT, then boot into system
Truly hope this helps others with there SGS3 (l710)
Thanks Again.
P.S.
reason for the red>So hopefully others on stock 4.4.x, can see 1 honest easy way to root
Jayhawker69 said:
roirraW "edor" ehT....THANKS A MILLION!! I have successfully in ODIN, flashed Philz Touch Recovery onto my S3. I booted into recovery, went in Philz settings, and clicked on the "re-root" option. I rebooted the device into the main system/shell, ran root checker to verify root status.....AND VOILA! ROOT STATUS GRANTED, BISH! I downloaded SuperSU from the play store, and everything seems to be running like butter. Consider this thread CLOSED!
Cheers from Lawrence, Kansas!,
-Brett
Click to expand...
Click to collapse
These steps worked! Thank you both very much!
Hi all,
I can't install busybox on B512. I download it from market and when I open it, it did't show anything like the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(http://imgur.com/QT0Rzl1)
Help me plz
notwo said:
Hi all,
I can't install busybox on B512. I download it from market and when I open it, it did't show anything like the picture.
(http://imgur.com/QT0Rzl1)
Help me plz
Click to expand...
Click to collapse
Root with TWRP will add the busybox
install it http://forum.xda-developers.com/showthread.php?t=2709353
and for root follow this at the end https://www.youtube.com/watch?v=3dBSVlCxYlg
Reboot and update supersu
If your phone is already rooted maybe TWRP don't show you the supersu messagei don't tried with a rooted device but on unrooted device it's work perfectly. So if you need a unrooted device you can just return to stock recovery and reflash the B512 firmware
Skyllery said:
Root with TWRP will add the busybox
install it http://forum.xda-developers.com/showthread.php?t=2709353
and for root follow this at the end https://www.youtube.com/watch?v=3dBSVlCxYlg
Reboot and update supersu
If your phone is already rooted maybe TWRP don't show you the supersu messagei don't tried with a rooted device but on unrooted device it's work perfectly. So if you need a unrooted device you can just return to stock recovery and reflash the B512 firmware
Click to expand...
Click to collapse
Hi,
I'm pretty sure my phone is rooted with supersu and already installed TWRP.
and also Busybox got the root access.....
my problem is I can't install busybox (either smart install or normal install)..
I can only install busybox apk from market..
any idea how to install it.
My phone is on B512.
notwo said:
Hi,
I'm pretty sure my phone is rooted with supersu and already installed TWRP.
and also Busybox got the root access.....
my problem is I can't install busybox (either smart install or normal install)..
I can only install busybox apk from market..
any idea how to install it.
My phone is on B512.
Click to expand...
Click to collapse
When you root with TWRP, TWRP install busybox automatically
Skyllery said:
When you root with TWRP, TWRP install busybox automatically
Click to expand...
Click to collapse
I root with UPDATE-SuperSU-v2.02.zip via TWRP recovery
and also i already bought Busybox pro from market.
is there anyway to install it?
Thanks anyway
notwo said:
I root with UPDATE-SuperSU-v2.02.zip via TWRP recovery
and also i already bought Busybox pro from market.
is there anyway to install it?
Thanks anyway
Click to expand...
Click to collapse
I know only two ways to install busybox ..
1. Root with TWRP
2. Root with RootGenius
But separately i don't know i didn't tried becuse when i was under B125 i tried to install busybox with busybox installer and it fail (soft brick) ..
Maybe try this http://forum.xda-developers.com/showthread.php?t=1929852
Skyllery said:
I know only two ways to install busybox ..
1. Root with TWRP
2. Root with RootGenius
But separately i don't know i didn't tried becuse when i was under B125 i tried to install busybox with busybox installer and it fail (soft brick) ..
Maybe try this http://forum.xda-developers.com/showthread.php?t=1929852
Click to expand...
Click to collapse
First of all, thanks for ur helps, man..
I flashed busybox from http://forum.xda-developers.com/showthread.php?t=1929852...
but when i opened 2lines for viber which needs busybox, it said that busybox doesn't seem to be installed.
any idea?
notwo said:
First of all, thanks for ur helps, man..
I flashed busybox from http://forum.xda-developers.com/showthread.php?t=1929852...
but when i opened 2lines for viber which needs busybox, it said that busybox doesn't seem to be installed.
any idea?
Click to expand...
Click to collapse
Try wipe cache and dalvik-cache throught TWRP or retry maybe
Skyllery said:
Try wipe cache and dalvik-cache throught TWRP or retry maybe
Click to expand...
Click to collapse
already tried... and also flash again & wipe again..
still can't install
Help me plz
Thanks
notwo said:
already tried... and also flash again & wipe again..
still can't install
Help me plz
Thanks
Click to expand...
Click to collapse
I have nothing more .. try to reroot with rootgenius
or reflash B512 and root with Rootgenius or TWRP
Skyllery said:
I have nothing more .. try to reroot with rootgenius
or reflash B512 and root with Rootgenius or TWRP
Click to expand...
Click to collapse
Buddy,
I tried reflash B512 and root with TWRP..
but still can't install Busybox... I also tried to install busybox installer from playstore but when I open tat, it automatically closed by itself.
any option???
Thanks
notwo said:
Buddy,
I tried reflash B512 and root with TWRP..
but still can't install Busybox... I also tried to install busybox installer from playstore but when I open tat, it automatically closed by itself.
any option???
Thanks
Click to expand...
Click to collapse
TWRP install busybox when you root your phone normally ...
Try Rootgenius ... when your root with it, it install Kinguser (like SuperSu) and with it my application never told me to install busybox. They are also other methods http://forum.xda-developers.com/showthread.php?t=2390491 maybe install the busybox too.
Or try through adb to install it manually
TWRP recovery 3.0 zenwatch
How to install Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master
acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.
Ups , i fix this today ...
Sorry
hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!
Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)
itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).
Boooooo moto 360. It's sooo damn big.
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github
Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.
I need a link to the stock recovery.IMG file
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess
aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk
imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!
Will the same method work on pj1 ?