SU Problem - Galaxy S III Q&A, Help & Troubleshooting

Whenever i try to reboot through CWM or flash something, an error always pops up informing me that my root access is possibly lost. It then asks if i want to fix it. I can either say "No" or say "Yes - Fix Root (/system/xbin/su)"
I have tried both options and have discovered that i cant flash anything. I have also checked and i have cobfirmed that /system/xbin/su is in fact on my phone. I dont know what to do. Also, my phone is an AT&T Galaxy S3 i-747 rooted with towelroot, stock ROM, stock kernel(which I hope to change right after this).

EddyTeddy01 said:
Whenever i try to reboot through CWM or flash something, an error always pops up informing me that my root access is possibly lost. It then asks if i want to fix it. I can either say "No" or say "Yes - Fix Root (/system/xbin/su)"
I have tried both options and have discovered that i cant flash anything. I have also checked and i have cobfirmed that /system/xbin/su is in fact on my phone. I dont know what to do. Also, my phone is an AT&T Galaxy S3 i-747 rooted with towelroot, stock ROM, stock kernel(which I hope to change right after this).
Click to expand...
Click to collapse
You need to post your question here >> http://forum.xda-developers.com/galaxy-s3-att <<

Hi there maybe you should rather try using twrp recovery(more features) and to try and fix your root look at the bottom of this page http://forum.xda-developers.com/asc...d-add-want-t2843511/post54729790#post54729790 (rooting is mostly universal)Bin4ry will probably work best with a samsung device also try the supersu flashable file

Related

[Q] Need to revert to stock

Apologies but i am out of my depth and need some support. I have a Galaxy S3 and decided to root it as I can't resist looking for useful tweaks. I rooted it fine but only then realised that our good friends at Sky had barred me from using Sky Go. This was more important to me than the tweaks so I followed some web instructions on unrooting. Again, this seems to have been successful as tests and trying to use root apps fail. If I try to re-unroot, I am told that I am not rooted but here's the rub, Sky still says I am rooted!. As a last resort, I decided to do a factory re-set and before loading anything else, load Sky Go to see if the problem was solved.
As the restore began, I noticed a screen that I think was something to do with TWRP - I noticed that the words WIN.... were in the title and here was a recovery message. The screen was made up of blue graphics. The reset continued but without anything else loaded, Sky Go still said I was rooted. I can only assume that at some point during the root and un-root, the ROM was flashed with this other tool and it is this that is being detected by Sky Go. Am I right?
So, I would really appreciate some assistance as to how to get back to un-rooted stock ROM with no extras!
Any help gratefully received!
Thanks
Maybe just use something like this:
https://play.google.com/store/apps/details?id=com.marutian.quickunroot
that's probably the solution for an app that doesn't work on a rooted device (I have the same issue with a local dutch tv provider app, solved with the mentioned app)
The other option (since removing SU from your current rom kinda failed) is flashing a new ROM with TWRP, just find a zip file for a ROM without SU/root
prulleman said:
Maybe just use something like this:
https://play.google.com/store/apps/details?id=com.marutian.quickunroot
that's probably the solution for an app that doesn't work on a rooted device (I have the same issue with a local dutch tv provider app, solved with the mentioned app)
The other option (since removing SU from your current rom kinda failed) is flashing a new ROM with TWRP, just find a zip file for a ROM without SU/root
Click to expand...
Click to collapse
Thanks - The Quick Unroot option doesn't work as it can't find an SU binary file - 'spose it's because it's not rooted!
I flashed a new ROM (using ODIN) but I think that the recovery screen mentioned before and which appears at the strt of the re-set has also been added to the ROM and is the only thing I can think of that's causing this.
More suggestions please!

[Q] Problems getting root access at galaxy s4 mini

Hi, first i appriciate ure help and the work here is amazing. i wanted to put the question directly to the right threat but i couldnt (no 10 messages).
i have rooted my galaxy s4 as explained in http://forum.xda-developers.com/showthread.php?t=2364980.
i did everything exactly as mentioned from step 1 to 9 and it all worked.
When i started my phone, also as mentioned, the knox-file told me that phone has security issues... (i thought "nice, now its definitaly rooted"). SuperSU asked me if it shall block the knox, i said yes and the messages stopped.
To make it sure, i downloaded "root checker", the app asked for permission at superSU, i gave it, then message from phone that permission is given, but then nothing happened. Same for Titanium Backup. When i wanted to set permissions directly at superSU, it said that binary file needs an update. What i did was to update superSU via google play as mentioned in many forums, but still same problem. i also downloaded super user, the app said no root permission.
-> i rooted the phone already 3 times following exactly the instrucions at thread from above, every time the same problem.
I read a lot in forums, my conclusion to the problem is that i still dont have my phone rooted.
- What do you think??
- Has anyone any idea what i can do to get my phone rooted?
- Is there a possibility to unroot the phone? because now i always get questions about permissions, but it makes no difference what i press bec it doesnt work.
penqrockt said:
Hi, first i appriciate ure help and the work here is amazing. i wanted to put the question directly to the right threat but i couldnt (no 10 messages).
i have rooted my galaxy s4 as explained in http://forum.xda-developers.com/showthread.php?t=2364980.
i did everything exactly as mentioned from step 1 to 9 and it all worked.
When i started my phone, also as mentioned, the knox-file told me that phone has security issues... (i thought "nice, now its definitaly rooted"). SuperSU asked me if it shall block the knox, i said yes and the messages stopped.
To make it sure, i downloaded "root checker", the app asked for permission at superSU, i gave it, then message from phone that permission is given, but then nothing happened. Same for Titanium Backup. When i wanted to set permissions directly at superSU, it said that binary file needs an update. What i did was to update superSU via google play as mentioned in many forums, but still same problem. i also downloaded super user, the app said no root permission.
-> i rooted the phone already 3 times following exactly the instrucions at thread from above, every time the same problem.
I read a lot in forums, my conclusion to the problem is that i still dont have my phone rooted.
- What do you think??
- Has anyone any idea what i can do to get my phone rooted?
- Is there a possibility to unroot the phone? because now i always get questions about permissions, but it makes no difference what i press bec it doesnt work.
Click to expand...
Click to collapse
Try flashing this in CWM recovery:
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
Hope this helps!
Try flashing this in CWM recovery
Click to expand...
Click to collapse
It might be kind of a noobie question but i still ask it
I followed the instructions from the thread mentioned earlier, but when i go in recovery mode with the button combo i have the "normal" recovery from android and not the CWM. do i need to flash the CWM to my phone like mentioned for example here at method A?
Another thing: Do you think that my phone is rooted and i just got problems because of the SuperSU binary file?
penqrockt said:
It might be kind of a noobie question but i still ask it
I followed the instructions from the thread mentioned earlier, but when i go in recovery mode with the button combo i have the "normal" recovery from android and not the CWM. do i need to flash the CWM to my phone like mentioned for example here at method A?
Another thing: Do you think that my phone is rooted and i just got problems because of the SuperSU binary file?
Click to expand...
Click to collapse
Place the Update-SuperSUv1.86.zip (I gave you a link for it in previous post) on your sd card then repeat steps 2-7 from this thread:
http://forum.xda-developers.com/showthread.php?t=2364980
Once you are booted into CWM recovery flash the Update-SuperSUv1.86.zip file and reboot. Now go open SuperSU it should ask if you want to disable knox. Say yes and then try root checker.
If you do not have Su binary on the phone then you are not rooted.
There is a file in the phone that reflashes the stock recovery on every boot, you would need to remove it to keep CWM.
Please let me know if this works for you, good luck!

ROOT BOUNTY FOR SGH-527 with 4.4.2 KitKat Update

Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version

New to rooting, cant flash the firmware

Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
white5pirit said:
Hi guys. Im not going to lie, im a noob when it comes to rooting, so I turned here to ask for help. Now, let me explain my whole issue. Lets start with, i cant unlock my bootloader. I also cant get into flash mode on flashtool which would allow me to downgrade, and and then root my phone from there. So yeah, I cant do anything honestly. I would love it if someone would be kind enough to help me with a step by step instruction guide, or even live assistance?. I already google'd for about 2-3 hours now, and can't find anything. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Mention 'EveryThing' about your phone. You can Take a screenshot of 'About Phone' and post it here.
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
white5pirit said:
Thanks for the reply!
I have attached a screenshot of what the window looks like.
"prntscr DOT com/8ffqdz" Sorry for the link, but I wasnt able to post it through the img tag.
Oh I also forgot to mention, just this morning I could root my phone with Kingo Root, but reading some negative stuff about it, I would still like to root it with the standard, old method of flashing etc, and I can't do some things I could on standard root.
Click to expand...
Click to collapse
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
hitman-xda said:
Well, it's Xperia M2.
Let me clear that,
There are two types of Rooting methods available.
1. Permanent root
(Root access is available for ever, untill you unroot manually)
2. Temporary root
(Root access is gone, when you restart phone)
So, if you have successfully rooted your phone with Kingo Root, you no need to flash rooted kernel or firmware (its same with already root access available).
After rooting, you must have seen a app SuperSU or SuperUser or anyother that manages root permissions requested by apps that needs root (you need to grant permissions to let app work). If you do not see such any app, download it from play store.
I usually suggest Xperia users to root their devices with TowelRoot app. It is smart and simple and it does not contain any preloaded app for permissions (that means you can switch with SuperSU or Superuser)
Also, what things you could not do? let me know. I'll help you out
Regards,
hitman-xda
Click to expand...
Click to collapse
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
white5pirit said:
Again, thanks for the reply. Yup, I saw the SuperUser app, and the problems I have might not be phone breaking and such, but I would like to be able to do things like, change permissions of certain folders, which i cant do with the Kingo root, as it somehow denies the access to the folder, even tho I allowed root browser/es file manager root access. Overall, i think the problem is with the permission system Kingo has. I'd also like to mention that i would love to install Cyanogenmod on my device, but I will look into that myself @edit: Also, I would prefer to have a premanent root, instead of the towelroot and such.
Click to expand...
Click to collapse
You could just press the 'thumbs up' instead writing 'thanks' everytime.
Well, why do you want to change the permissions of the folders? You could mess-up your device if you change permissions for the root folders.
The problem looks strange. If you have rooted successfully and GRANTED permissions for ES file explorer through SuperUser, you should not get any problem changing permissions. Check in SuperUser app that you see ES file explorer.
Also try using other explorer app. I use 'Solid Explorer' and its great.
If you have temporarily rooted your device as I mentioned in above post, try using TowelRoot app for rooting your device permanently and manually download SuperSU.
If you want to use CyanogenMod (it'll be pre-rooted) you need to carry below steps;
1. Unlock your Bootloader
(Wipes everything)
2. Install recovery.
3. Take stock ROM backup.
4. Flash ROM.zip
5. Flash GApps (optional)
6. Wipe cache+dalvic+factory reset
7. Reboot
Regards,
hitman-xda
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
white5pirit said:
Problem is that my bootloader can't be unlocked. I guess there is literally no way in which i can unlock it then?
Click to expand...
Click to collapse
If your bootloader status says
'unlock bootloader allowed = NO'
Then you can't flash anything on your phone. Almost every ROM needs an unlocked bootloader. There will be some ROMs that can be flashed over locked bootloader but they will be stock based.
EDIT: You have a good Luck, you can flash recovery on Locked bootloader
http://forum.xda-developers.com/xperia-m2/development/d2303-clockworkmod-6-0-4-6-t3011821
If you flash recovery successfully, that means you can flash ROM
Check below link for ROMs Available;
http://forum.xda-developers.com/xperia-m2/development
Regards,
hitman-xda
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
white5pirit said:
Yup, my bootloader says it can't be unlocked. Anyways, i tried the link yo usent me, but it comes up with an error, saying "device not found". I went into recovery mode on my phone, but i assume it might be the adb driver issue? I will try to reinstall it, and get back to you.
@edit: I reinstalled the ADB drivers, and now CWM is stuck on "daemon succesfully started", but it will not do anything else. Any clue as to what could I do to fix this? @edit2: Actually, disregard what i said. It still comes up as" Device not found"
Click to expand...
Click to collapse
It can be a drivers issue. Install PC companion and connect your phone, let PCC install essential drivers and after that follow the same steps for installing recovery.
If you post any screenshot, that would be better.
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
white5pirit said:
Mkay, it worked now after i reinstalled the device in Sony PC companion. Heres a screenshot of what the CWM cmd window looks like: "prntscr DOT com/8fth1u". I assume this is good? So, all i have to do now is just download Cyanogen Mod and flash it, right?
Click to expand...
Click to collapse
Yup! Everything looks good. Just try to enter into recovery before downloading CM.
1.Switch off your phone and wait for 10 sec
2. switch on
3. When you see LED, try pressing either of vol buttons.
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
es0tericcha0s said:
Hate to rain on the parade, but CM and CM based roms don't work with locked bootloaders for that phone, despite having CWM. It should say in the title of the thread whether it'll work with locked bootloaders.
Click to expand...
Click to collapse
Yeah you are right! Purely CM doesn't work on locked bootloader. But there must be any ROM available that is based on CM or even other ROMs that has some CM features.
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
es0tericcha0s said:
I went through a few threads in that forum, Omni, CM, PAC, etc and all mentioned needing unlocked bootloader. Best bet is a good stock rom and Xposed to enable other features.
Click to expand...
Click to collapse
Z4 experience looks great ;
http://forum.xda-developers.com/xperia-m2/development/rom-z4-experience-locked-unlocked-bl-t3079811
Your xposed idea is great. Plus there must be GravityBox

Need help with root for Galaxy SM-J320VPP / android 6.0.1

i know this is a newer phone but i'm still pretty surprised i haven't been able to find anyone that's rooted it yet. i've been all over the internet it seems. this is the :
Samsung Galaxy J3(6)
SM-J320VPP
Android 6.0.1 Marshamllow
Verizon pre-paid plan/network
i see lots of videos and guides for other j320f or j320p (close but no cigar) and nothing works. what i've tried so far:
- Dev mode enabled, USB debugging and OEM unlocked.
- any/all 1 click root apps. none worked, and i'd like to avoid these anyway unless you know it works 100% for my version. at this point i'll try anything.
- recovery / flash superSU. only i haven't even gotten past flashing a recovery. i've tried several different versions of Odin with several different versions of recovery .tar's and for each combination i've tried Odin simply fails. big red FAIL button in upper left corner. sadness. this seems like what i need help with. i have SuperSU downloaded so if i can just get a custom recovery working for my phone i'm hoping it's a simple process from there of booting into the custom recovery and then installing the SuperSU. presto.
is there no hope? is there no tested, confirmed working recovery that i can flash to my phone using Odin? i've tried Odins 3.07, 3.09, and 3.11.1. various custom recovery .tars but the only one i know for sure is the J2 version official from TWRP's website (yes i know it says J2 but someone on another thread said it's similar enough to someone ELSE's model "j320f" or something so i gave it a shot) the other recovery .tars i tried are suspect since they had generic names "recovery.tar" and were downloaded from links provided in many different "guides" that i've googled.
internet, you have failed me. thus do i issue this challenge to all those mighty phone hackers of the land. come forth and slay the evil giant that is my phone's ludicrous security (seriosuly how is this even a thing still in 2016. my phone can do so much more, so much better but for these shenanigans).
thanks so much in advance!
EDIT: not sure about the bootloader. i may be a complete idiot. yes. ok. i'm onto something. gonna post this anyway for any other poor soul that has this version phone, but i think Odin's probably failing because the bootloader is still locked. and Samsung doesn't make this easy like motorola or HTC. T_T. once more into the fray! i'll see if i can't track down a method for unlocking the bootloader on my phone. should i return victorious i'll go ahead and share my steps with the rest of the class.
EDIT2: there is no waking from this nightmare. i dig and dig and dig and can find no root. *sigh*
-- i've got android studio installed. and the java SDK platform-tools which contains the adb.exe, fastboot.exe, etc.
-- something i should explain here: in all these guides whenever there's a step that requires the phone to be connected to the PC, it simply says to, you know...connect your phone. but MY phone by default only uses the cable for battery charging. i have to (on my phone) swipe down from the top, select the "connected for charging" message bringing up "Use USB For" options, then select "Transferring media files" option. THEN my phone shows up both in my windows explorer and displays as a device when i run "adb devices".
--when i run "adb reboot bootloader" this does the same thing as holding down pwr/home/vol down - phone boots up into a blue (teal?) background with a large down arrow in center, below that it says "downloading...do not turn off target". in the upper left are several lines of system font style text:
ODIN MODE
PRODUCT NAME: SM-J320VPP
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF*
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1*
SECURE DOWNLOAD: ENABLE
*the R's above may be A's or vice versa...hard to read font. sorry
--but as soon as i've rebooted into this mode, my phone disappears from adb devices' list of devices attached. regardless when i run the "fastboot oem unlock" command from the adb shell on my PC at this point i get the infamous "waiting for any device" message and then, of course, nothing....forever. i've also installed PDAnet but i think it's hitting the same road block where my phone is only using the cable for battery charging and i can't toggle that option from ODIN MODE. there's also a "USB Configuration" choice under development options on the phone that has the same options as "Use USB for" but this doesn't stick when booting into ODIN MODE. sadness. i need to retire my brain thoughts at this point. will post TL;DR. you're a saint of geeks if you've made it through my WoT to here.
EDIT3: just an observation - the only thing (so far) that will detect my phone in ODIN MODE is ODIN itself. is there a way to use ODIN to unlock the bootloader?
TL;DR: i think odin is failing when attempting to flash because of locked bootloader. need help with unlocking bootloader first? phone defaults to use USB cable for charging only so i CAN change that to MTP while phone is on normal and then run "adb reboot bootloader" but then phone vanishes from adb devices list once it reboots (and cable is then only charging). thus, cannot run "adb fastboot oem unlock" cuz it hangs displaying "waiting for any device" -- can i unlock the bootloader on this phone? or did i buy a phone that's IMPOSSIBLE TO ROOT!?!?
I have the same problem! I need to root it to install the Patch to change from CDMA to GSM! Because I tried without root and it tells me "E: Signature verification failed"
Thanks
Still nothing?
This is starting to look hopeless
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
News?
There is nowbody that had been rooted his J3 Verizon yet?? We need help with this trouble!
In this forum (http://forum.xda-developers.com/android/help/galaxy-j3-sm-j320vpp-configuring-cdma-t3414049) Sergio said:
" try root with this root is only for Snapdragon 410 MSM8916
http://forum.gsmhosting.com/vbb/f723...t1994-1946985/ "
The J320VPP has a "1.2 GHz, Quad-Core". There is no place that sais it's a "Qualcomm Snapdragon 410 Msm:8916" processor. You think this suggestion could work?
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Whusky said:
I think I've managed to get the recovery.img with KIES... However flashing the image I've extracted doesn't work but if anyone is ready to help me port a recovery I might try !
Click to expand...
Click to collapse
im gonna try and do a reflash with kies and grab that file myself, ill work a bit on it because i love this phone but no basic root is driving me insane. if you can beat me to posting tell me how you got the file, otherwise ill post here once i find out. I'm not a top of the line developer but i can work my way around and try my best since nobody else is offering to help.
wish me luck.
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
well turns out verizon locks the flashing with signature verfication. so unless verizon changes or root is found for marshmellow there will be zero possible root for this phone.
NerdmastaX said:
sorry for the double post but got the files via the verizon software assistant no problem. it ended up in C:\Users\YOURNAME\AppData\Roaming\Verizon_AR\SM-J320VPP_J320VPPVRU1APC3_FACTORY for me, and even decrypted and unzipped itself for me, now we just need to mod a custom thingy into those files and we can work towards rooting. so as i sit here and watch my phone finish flashing back to factory i will look into how we can mod the recovery. if someone is capable of doing it faster i can upload the files very quickly as its only 1.4 gb
Click to expand...
Click to collapse
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Sparko612 said:
Hi I'm currently rooted with TWRP 3.0.2 recovery and mabey this might help http://forum.xda-developers.com/general/help/samsung-galaxy-j3-sm-j320fn-how-to-root-t3369511
Click to expand...
Click to collapse
verizon blocks flashing of modified recoveries. so unless someone finds a root exploit for marshmallow we will have no luck.
Has the kingroot method worked for root on your device ??
NerdmastaX said:
we need the stock recovery.img to be able to mod it and flash it through odin. the recovery for the verizon version does not match so odin wont allow it. i asked on sammobile and they said verizon only releases ota on the device. so idk what to do. perhaps someone with knowledge on this will help.
so far what ive figured out our situation is:
we need root to get root.
more specifically we need root to pull the recovery and then mod that recovery with twrp and use twrp to gain root. The root methods that worked for the other variant SM-J320P dont appear to work for ours, probably due to having android 6.0.1
till we get root we are stuck. the rest is easyish
Click to expand...
Click to collapse
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
MetAJFA said:
Hi to all, im new here and i am having the exact same problem! You say that there has to be a root specifically for the 6.0.. So i found that in the Chainfire page they have this https://download.chainfire.eu/986/CF-Root/CF-Auto-Root/CF-Auto-Root-j3lteusc-j3lteusc-smj320r4.zip already (i dont know if i can post links, so if i cant, sorry), it is marshmallow but the model is J320R4, so i was wondering if this could be the solution. i'll be waiting here for a response, i seriously love this phone :c
Click to expand...
Click to collapse
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
an twrp is already available for j320p u can try to root your device using it
es0tericcha0s said:
No, this is not the solution. When using a utlity like CF Auto Root, it must be specific to your model / carrier. Trying to install that will do 1 of 2 things.
1) Just fail in Odin
or
2) Soft brick your device
Since VZW doesn't bother to put out the full firmware files to reflash the device, it's not worth attempting without having the backup plan of the original firmware to flash via Odin.
Click to expand...
Click to collapse
Understood, thank very much you for clearing that out. Since all this is pretty much a kick in the butt, do you think there will be some kind of solution to this or should we just lose hope? :/
can Someone here help me with this.
someone wrote:
I have the same problem, I already got 4G LTE data with the correct APN and also I change to lte/gsm with the help of a network app and with commands in adb shell :
pm clear com.android.providers.telephony
settings put global preferred_network_mode 9
settings put global preferred_network_mode1 9
settings put global preferred_network_mode2 9
Click to expand...
Click to collapse
but i dont know how to initiate this adb mode in the phone. anyone?
anyone fix ?
i have few units J320VPP same problem .. searching for service .
That's a Verizon device with a locked bootloader, you cannot try twrp or modified files meant for 320f or other models on this one.
Sent from my SM-N920G using Tapatalk
So has anyone found any luck with this device? It's driving me crazy not having root

Categories

Resources