Hello.
I read almost everything but still not able to use SuperSU.
Updating from market give me the error of no binary installed.
I tried to flash it but then i dont see it at all.
I have upgraded my N7100 to official stock 4.4.2 through Kies.
I am using Philz recovery and Dr.Ketan multi tool.
Is there something i missing ?
When i upgraded to 4.3 everything went fine.
majoragi said:
I am using Philz recovery and Dr.Ketan multi tool.
Click to expand...
Click to collapse
Try TWRP
'cause in the Phantom Rom thread, many people experience problems when using other recoveries. It's worth a shot, although I do not guarantee it.
majoragi said:
Hello.
I read almost everything but still not able to use SuperSU.
Updating from market give me the error of no binary installed.
I tried to flash it but then i dont see it at all.
I have upgraded my N7100 to official stock 4.4.2 through Kies.
I am using Philz recovery and Dr.Ketan multi tool.
Is there something i missing ?
When i upgraded to 4.3 everything went fine.
Click to expand...
Click to collapse
I had a similar situation. Resolved it by using CF autoroot, flashed via PC Odin. Follow Chainfire's process as per the link below, then update SuperSU via playstore. I had to repeat the process a few times, before it "stuck".:laugh: Its working fine now and it has survived a factory reset as well, so I am happy.:good: Thanks to Chainfire.
http://forum.xda-developers.com/showthread.php?t=1933542
Fianlly worked.
I tried the same in a internet cafe couple days ago with no result.
I did it today at home and worked.
I think my Note2 have personality and wants only my computer for these kind of stuff.
Anyway after the CF-autoroot i install SuperSU and then i flashed again Philz recovery cause i like it more.
Then i run Dr Ketatn's multitool (not for the root option) and everything works perfect.
Related
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
rezaasl2000 said:
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
Click to expand...
Click to collapse
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
hednik said:
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
Click to expand...
Click to collapse
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
rezaasl2000 said:
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
Click to expand...
Click to collapse
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
hednik said:
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
rezaasl2000 said:
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
Click to expand...
Click to collapse
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
rezaasl2000 said:
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
Click to expand...
Click to collapse
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
hednik said:
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
Click to expand...
Click to collapse
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
rezaasl2000 said:
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
Click to expand...
Click to collapse
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
hednik said:
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So, I finally figured it out. I used the samsung galaxy s3 toolkit to install the stock firmware and then I updated it on the phone. Next, I went back to the toolkit and installed the most recent version of CWM on it and everything just worked beautifully. I have LiquidSmooth installed and it works just great.
thank you for the help hendik.
:good:
hey guys. lurker turned new poster here at XDA. a friend of mine turned me on to this a while back when he introduced me to the world of rooting. I've recently bought a Galaxy S III (SGH-i747), and I've been trying to root it using mskip's unified toolkit (http://forum.xda-developers.com/showthread.php?t=1979290). I got it rooted once, but eventually bricked it when trying to get 4.4 on it, and had to reinstall the stock 4.1.1 rom on it and lost the root in the process.
I'm completely new to all this, and I'm still trying to figure it out. I've been searching as much as I can and reading a lot, but I'm not sure if there's something I'm missing here. when I try to root it lately using the toolkit, it gets stuck in the process after I exit Odin, and will never progress.
before when the root was actually in place, I tried to install a custom OS after doing a full wipe of the system, and it never would install. I tried it with TWRP and CWM, and there was no success with either of them. the one peculiar thing, however, is that I could never get it to install with the "ALLINONE" option. when I got it to work that once, I had to install it each individually.
is there some sort of guide out there that would make this easier for me to get 4.4 on the phone? or will someone be able to help me through the process?
thank you for your time!
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
hachikid said:
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
Click to expand...
Click to collapse
I used this when I first rooted my I747. http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My Bell s3 was on 4.1.2. I rooted by installing a rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Do not flash a 4.1.1 or 4.1.2 rom if you have a bootloader from 4.3.
when I got the phone, it had 4.1.2 on it. when I bricked it, I flashed a stock 4.1.1 ROM on it, and that's what I've been using as my base ROM.
Boomer1605: I'll try that when I get home.
anyone else know what is up with the place I get stuck at during the toolkit way?
My Bell s3 was on 4.1.2 when I got it. SInce I needed to unlock it and didn't want to pay, I installed the stock Bell 4.1.1 firmware from here: http://www.sammobile.com/.
After using the menu option to unlock the phone and confirm that it was unlocked, I flashed the pre-rooted Bell s3 4.1.2 rom.
Everything worked perfectly, no errors or issues at all.
Cool! Can I find a pre-rooted 4.1.1 AT&T rom on that site? I can't really look at that link cause I'm currently at work.
Pre-rooted roms are here: http://forum.xda-developers.com/showthread.php?t=1739426
I was able to install Root Explorer on my pre-rooted ROM and delete a tonne of Samsung apps.
I was able to install a pre-rooted version of 4.1.1, and I did a system/data/cache/dalvik wipe from the TWRP screen, but when I tried to install both Liquid Smooth and Omni Rom, it failed. I even restarted and didn't wipe, and it still failed. not sure where to go from here... :/
tativle coast
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
hachikid said:
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
Click to expand...
Click to collapse
Awesome! Congratulations. For future reference, TWRP also had tar images for use with Odin.
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
xysterztia said:
I dropped Illusion and went full unrooted stock for the OTA to 4.3, which was not as awesome as I hoped it would be. So back to root and a custom rom!! Rooted MK4 with ease using kingoroot, used SuperSU to drop KNOX. I think after these steps is where my issues begin. Use goomanager to install twrp, and finally use billard412's wicked awesome "Back to UNROOTED Stock with Auto Flash Count Reset" to get back to MC2 in order to flash a custom rom. I have gotten stuck in a boot loop twice doing this and resolved both with the awesome forums here! The problem was both ROM's i went to (Dirty Unicorns and Smasher X) worked awesomely except for no mobile service on either.
So do I need to go back to MC2 in order to flash a custom ROM or can I go straight from rooted / custom recovery MK4 into a custom ROM. Or is there another flaw in my mechanics? I have seen a bunch of comments on using CWM instead of TWRP, is that my issue? Does CWM work in a similar fashion as TWRP? (I have only ever used TWRP) Thanks for any assistance, and fingers crossed there is not an unseen by me thread on this exact issue!
Click to expand...
Click to collapse
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
cashdude1971 said:
Hey I think I am having a similar issue. I had to root back to stock MC2, take my phone to Sprint, have them reset it. Now I am on MK4 4.3 unrooted. When I tried to root, I got a Samsung message saying that there was an unauthorized app (SU) trying to run and prompted me to update Samsung security policy. What can I do to be rooted again so I can install custom ROMs again. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2539227 <-- install SuperSU from play store and then google search Kingo Root, dl kingo root, run kingo root, enable USB debugging, connect, and follow on screen instructions!
Also that unauthorizing app is KNOX and big thanks should go to lorjay589 for posting work around. Also you should read his thread and understand all dangers and voidednous that now potentially comes with rooting.
That was the problem! I wish I would have tried before posting! My issue was either using TWRP or downgrading to MC2, I just tried again using CWM and root on MK4. Dirty Unicorns loaded perfectly and data is running!
Thanks for the tip, that helped me out also
I have T-Mobile SM-N900T with N900TUVUCNB4 Latest firmware 4.4.2 it came with the phone.
I have tried to install and root this phone many times. And every time it goes into recovery it boot loops. No matter what I have tried. I have tried CF-Root for the Kitkat, I have installed Recovery from TWRP 2.7, via Odin. Every time I says it updates but just goes to recovery and loops. I know that it has already tripped the Knox Warranty it now says 0x1.
Maybe if there is a Rooted 4.4.2 rom that can be put on via odin that might work. I have not found one. Or if anyone can give me directions on how to install any of the roms for this phone via odin it would be helpful as well.
I would like to root due to I need to remove allot of the bloatware on the phone its really full of apps that I will never use.
arielb27 said:
I have T-Mobile SM-N900T with N900TUVUCNB4 Latest firmware 4.4.2 it came with the phone.
I have tried to install and root this phone many times. And every time it goes into recovery it boot loops. No matter what I have tried. I have tried CF-Root for the Kitkat, I have installed Recovery from TWRP 2.7, via Odin. Every time I says it updates but just goes to recovery and loops. I know that it has already tripped the Knox Warranty it now says 0x1.
Maybe if there is a Rooted 4.4.2 rom that can be put on via odin that might work. I have not found one. Or if anyone can give me directions on how to install any of the roms for this phone via odin it would be helpful as well.
I would like to root due to I need to remove allot of the bloatware on the phone its really full of apps that I will never use.
Click to expand...
Click to collapse
Read the cf auto root thread.ur answer is in the few last pages
TWEAKED N3
BACARDILIMON said:
Read the cf auto root thread.ur answer is in the few last pages
TWEAKED N3
Click to expand...
Click to collapse
I have gone through those steps. It always comes up with same thing in the recovery says RECOVERY something about enforced smsrecovery it goes too fast. But it does not work.
arielb27 said:
I have gone through those steps. It always comes up with same thing in the recovery says RECOVERY something about enforced smsrecovery it goes too fast. But it does not work.
Click to expand...
Click to collapse
I am for sure that you did not use cf autoroot for the euro phone. I am willing to bet that you might also be trying the wrong recovery. Only 2 exist for the 4.4.2 boot loader.
TWEAKED N3
I was having the exact same problem you are having right now, and BACARDICIMON helped me out of it. I downloaded the original 4.2.2 firmware from sammobile.com and then used odin 3.9 and flashed that. It started working perfectly afterwards.
I had used cf-auto-root to root my note 2 running build number KOT49H.I317MVLUDNH2 (koodo 4.4.2 stock). Worked great no issues, after root I used flashify to install twrp-2.8.7.0-t0lteatt.img.
My issue is recently I noticed an update from koodo (KOT49H.I317MVLUDNH3). Using kies I installed this update, which caused the phone to loose its root. I tried using cf-auto-root to root the phone again but no supersu.
Can anyone point me to a root method that will work with the new update? Notice the difference is the 3 at the end of the build, the os version remains 4.4.2.
Thanks in advance
You could just flash supersu via Odin or TWRP and you'll have it back again...
Also....2.8.7.0 is a bit buggy atm...so 2.8.6.0 may be a better choice...g
gregsarg said:
You could just flash supersu via Odin or TWRP and you'll have it back again...
Also....2.8.7.0 is a bit buggy atm...so 2.8.6.0 may be a better choice...g
Click to expand...
Click to collapse
i did exactly as you said. and it worrked!
gregsarg said:
You could just flash supersu via Odin or TWRP and you'll have it back again...
Also....2.8.7.0 is a bit buggy atm...so 2.8.6.0 may be a better choice...g
Click to expand...
Click to collapse
how do you flash supersu ?
I tried to root my galaxy note 2 using odin 3.10.7 and it was successful but after checking "about device" at the very bottom it says my phone is official which it is not, it was rooted successfully so I don't know why it is saying that. Also, supersu was not installed immediately after rebooting from odin, I had to manually download supersu from the play store. When I open up supersu, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
What can I do ? thanks
Flash twrp to the note 2 via Odin. Then flash supersu.zip from twrp.