Root method failing every time - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Im using this method
http://forum.xda-developers.com/showthread.php?t=2252248
I have all the drivers installed and run the bat file. The script finishes and installs superuser, but I'm not rooted. I've updated superuser and checked on root checker. Not sure what to do. The bat script also says "failed"
Any ideas?
http://i.imgur.com/UfLkJVk.png

What firmware are you on? If its mf3 I'd suggest using the kingo method.
Sent from my SGH-I337 using xda app-developers app

CollegeProfesor said:
Im using this method
http://forum.xda-developers.com/showthread.php?t=2252248
I have all the drivers installed and run the bat file. The script finishes and installs superuser, but I'm not rooted. I've updated superuser and checked on root checker. Not sure what to do. The bat script also says "failed"
Any ideas?
http://i.imgur.com/UfLkJVk.png
Click to expand...
Click to collapse
You can try Kingo Android Root 1.0.8 version
http://forum.xda-developers.com/showthread.php?t=2473747

If MF3 its just as easy to format "any " micro sd card to exFAT and enter three commands in a terminal emulator. Search for the card reader root method.easy
Sent from my SAMSUNG-SGH-I337 using xda premium

jball said:
If MF3 its just as easy to format "any " micro sd card to exFAT and enter three commands in a terminal emulator. Search for the card reader root method.easy
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
+1
http://forum.xda-developers.com/showthread.php?t=2387577
OP, we have no idea what firmware you are on.

Related

[RESOLVED] Stubborn security on MT4G. Will not Temp-Root.

I was able to root my MT4G with ease using VisionARY r14. My friend purchased a MT4G shortly after and I was trying to root it for him, I used several methods and no luck on any of them.
I've tried using:
1. Visionary temp root>attempt perm root
2. Visionary temp root>terminal (sh root.sh)
3. Visionary temp root>terminal (/data/local/wpx.ko)
From what I understand #2 & #3 basically are the same. So going back to the problem, on MY phone (I don't recall if I used #1 or #2), I rooted with no issues. On his phone, the root is not sticking, every time I go into the bootloader on his S=on still. Nothing stands out or is out of the ordinary, and I would think it would have rooted just fine, the scripts ran via terminal emu and looked okay and all.
Something else I've noticed is when I install CWM Recovery via ROM Manager, after temp root from Visionary the install of CWM Recovery itself was fine, though after going into bootloader and trying to access recovery or booting into recovery from ROM Manager, it doesn't go into recovery, I get the cell with red triangle and "!" on it. I'm assuming that this is a result of it being unrooted still? Anyone else run into a stubborn MT4G like this? I've attached 2 pictures for visual aid of the phone's bootloader screen and about screen below.
Any suggestions or help is greatly appreciated, I've been trying to root it for over a week now and no luck.
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
grankin01 said:
Ok guys, first of all Scotty2 gets all the credit for the program R&D. I used my device as a test bed and have tried a couple different kernels (Gr8Gorilla's O/C Kernel and the stock kernel).
Now for the boring stuff ...
This is a very invasive way of rooting your device but the benefit is TRUE S=Off and root privileges throughout the system. As such, you do this at your own risk and if you brick your device neither Scotty2 nor myself are responsible, YOU ARE!!! Do this at your own risk!!!
This is not for the faint of heart and if you have any reservations about doing things like this do not do it.
This process will do three things for your device. I will explain them here:
1. It will set up Super CID on your device allowing you to flash any carriers rom (not just tmobile). Giving you more freedom with your choice of software. The software still needs to be device specific to the glacier for compatability reasons though. Like vodafone glacier roms etc.
2. It will subsidy unlock your device. In other words, it will SIMUNLOCK your phone allowing you to use an AT&T sim card and so on in your device without needing the unlock code from HTC.
3. Most important of all it will turn the RADIO S=Off. This is the ultimate S=Off because the radio is what controls the security flag in the first place. Once you turn it off here it is off everywhere and will allow you pure unadulterated access to your device.
This process will not change your bootloader (unless your on 0.86.0000 and you follow the optional steps).
Now, you may be asking "Why do this? I already have root from your other guide and it has given me r/w access to system and recovery. I thought this meant we had permanent S=Off." This is only partially true. We have had an engineering bootloader and "Label" s=off not radio s=off. When you turn the security off in radio it is off permanently no matter what hboot you have installed engineering or otherwise. However, it is optional but you can still copy the engineering hboot over and it will allow you to flash whatever you like without (as much) fear of bricking your device.
This guide assumes you know how to use ADB. If you do not there are guides all over XDA to show you how. There is even a really good one in this forum. Also here is a video on how to setup adb discovered by topgun303: http://www.youtube.com/watch?v=1UF5w1dKe2U
*NOTE*
For some reason this process can bork your recovery. If you notice after following the steps below that in order to reboot from recovery you have to uninstall/reinstall the battery and hit the power button, just install/reinstall clockwork recovery through Rom Manager in the android market and it will fix your problem.
CONFIRMED: Guide does work for pre-OTA devices!!! Thanks xanz!
Here we go:
If you are already permarooted per the other guide just follow the first 11 steps.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60 New version of gfree with more options! See below.
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory.
2. Plug your device into your computer.
3. Now open explorer and hold down shift at same time you right mouse click on your SDK tools directory (platform-tools if you have the R8 version of the SDK). Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root. (If you were already permarooted w/s=off ignore this step.)
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
New features in gfree.
gfree usage:
gfree [-h|-?|--help] [-v|--version] [-s|--secu_flag on|off]
-h | -? | --help: display this message
-v | --version: display program version
-s | --secu_flag on|off: turn secu_flag on or off
-c | --cid <CID>: set the CID to the 8-char long CID
-S | --sim_unlock: remove the SIMLOCK
With the new features you can turn off one thing at a time. You can also turn security back on and set the CID back to stock if you wish. To turn simlock back on you still have to follow the revert procedures on this page as the information that is patched to turn the lock off is encrypted and we can't write back to it other than restoring the entire image.
So, if you wanted to leave simlock on but turn security off and set super CID the command would be "./gfree --secu_flag off --cid 11111111" + enter. The -f switch after ./gfree that is now in the above step (./gfree -f) just tells gfree to patch everything.
11. Wait for the program to finish and then reboot into HBoot to see if S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked.
If you already had hboot 0.85.2007 you can check it through the hboot menu. It gives you an option for "system info" in the hboot menu. Highlight it and hit power. It should say CID = 11111111 or something like that. If it does your golden.
Congratulations!
12. If this is the first time you have rooted your device you will need to run visionary again (temproot w/set system r/w after root checked and then attempt permroot) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to.
[Optional] Steps to flash engineering bootloader.
1. Restart your phone and plug it back into your computer.
2. Download this file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
3. Copy the file to your SDK tools directory.
4. Open a command prompt again and cd into your SDK tools directoty (platform-tools if your on the new R8 SDK).
5. Type "adb push hboot_dhd.nb0 /data/local" and hit enter.
6. Now open terminal on your device and type "su" and enter to gain root priviliges.
7. Type "cd /data/local" and enter.
8. Now type "dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18" and hit enter.
9. You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah.
10. Now restart the device into hboot and check if your bootloader version is 0.85.2007. That is what you want to see.
Congratulations, you now have a TRUE root and engineering bootloader on your shiny MT4G!!!
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA Premium App
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
I second this, gfree works great
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
powduh09 said:
I can't see the pics you posted, but I had this issue myself, for me the answer was to find a stock recovery pre ota update and force it, then I ran visionary and terminal with sh root.sh or whatever... Hope this helps... Just try to find an image of pre ota stock rom and go from there... There is a good forum here with a walkthrough to do this... Post results please, would like to know if this was your issue...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I see. So just get a pre ota stock rom and Visionary would be the simplest way then? But would the pre ota stock ROM also include the < 86.0000 botloader?
ZuluNexus said:
Hey I ran into the same problem, with that 86.0000 boatloader u must use the gfree chmod777 process its because its after the ota update
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ZuluNexus said:
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
ziggy34 said:
I second this, gfree works great
Click to expand...
Click to collapse
Thumbs up
powduh09 said:
This would explain why I had to flash the pre ota stock image before I could root using the sh root.sh.... I am sure the chmod777 would have worked also...
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Which method did you use to flash the pre ota image?
And thanks everyone for the quick replies!
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
powduh09 said:
When I flahed pre ota I found the forum on here for it. Just placed the file on my sd card and named it PD15IMG and booted phone to hboot, it found update and went from there
Sent from rooted Royal Glacier using XDA app
Click to expand...
Click to collapse
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Rainbowbright081 said:
I am having a problem getting the gfree files to move where they need to be and sry guys, unsure of ow to use sdk, im need the dummy dummy guide anyone? Ive been researching for days lol
Click to expand...
Click to collapse
You need a root explorer.
*Root can be accomplished without SDK.
Sent from my Glacier running CM7 RC2 via XDA app.
YOu can try using mt4groot.zip google it
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
lilazngoku8 said:
YOu can try using mt4groot.zip google it
Click to expand...
Click to collapse
It's in the second link I posted. Safer than Googling.
Rainbowbright081 said:
I managed to get it done right with adb, s=off perm, running cm7 with honeycomb. Quite awesome!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Running CM7 with Honeycomb? I am mistaken? You mean the honeycomb theme?
Sent from my Glacier running CM7 RC2 via XDA app.
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Rainbowbright081 said:
Sry yes running the honeycomb theme
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Lol cool, I was going to say, 3.0??!! ; )
gordonzhao said:
Awesome, what is hoped for! Thanks!
Sent from my HTC Glacier using XDA App
EDIT!!
RESOLVED!
Unfortunately the method of just using the PD15IMG did not work because the bootloader recognized it as an older image and wouldn't update it. I came across this thread and successfully rooted!! =]
http://forum.xda-developers.com/showthread.php?t=995549
I improvised a bit and did not use "Androzip" I had "Adao File Manager" already installed on my friends phone. Basically.
Credit goes to the OP of the posts!! But here's the link to the gfree the OP is referring to. http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
This is just a laid out variant of the ./gfree method. It'll work but it's been around since the dawn of the Glacier. It's nothing special .

[Q] Need Help/advice

I used this method to try and root the xformer......... all worked good until I tried to push the Superuser apk it did not push. Upon trying again, it said it was a read only file
Any suggestions?>
It is a 4/23/11 build I was using BLobV5
http://androidroot.mobi/asus-eee-pad-transformer-tf101-root-cwm-recovery/
Thanks
Do "adb remount" then try again.
Sent from my HTC Vision using XDA Premium App
well Got the superuser but still does not allow titanium backup to access root, I have busybox downloaded, and downloaded rom manager ad rebooted a couple of times
???? repush superuser ?

Chainfire 3D On A500

Hei!
I've just installed Chainfire 3D on my Iconia last night and when I try to install the driver, it show me this error:
CF3D driver
ERROR
Could not write to /system
I'm on root and I don't have any recovery installed
Thanks
Did it ask you to allow root access to the app? Sounds like it did not get proper root access. When all else fails, reinstall.
Sent from my ADR6425LVW using xda premium
mygraine said:
Did it ask you to allow root access to the app? Sounds like it did not get proper root access. When all else fails, reinstall.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes, the app ask for root access and I gave him, of course. Let's try to reinstall
[EDIT]= it's the same! It says me that error..
giovandrea said:
Yes, the app ask for root access and I gave him, of course. Let's try to reinstall
[EDIT]= it's the same! It says me that error..
Click to expand...
Click to collapse
A lesson. Root and /System RW are not the same thing.
You need to open your file manager, (ESFile Explorer, Root Explorer, etc), and set your /System to RW
Then install the app again.
MD

[Q] "Your device has been modified. Software updates not available" Unrooted

[Q] "Your device has been modified. Software updates not available" Unrooted
Hi,
I rooted my device with Odin/CF autoroot (still on stock rom)
I now want to get the official update. I've unrooted by using the 'Permanently Unroot' within Super SU. I've cleared the cache partition in recovery. I do not have an SD card.
It still says modified and won't update. Can anyone offer assistance?
Did you delete busybox from /system/app?
jd1639 said:
Did you delete busybox from /system/app?
Click to expand...
Click to collapse
I did not. Where can I find this? Under 'My Files' I can't see system. Also, is this safe?
jblz said:
I did not. Where can I find this? Under 'My Files' I can't see system. Also, is this safe?
Click to expand...
Click to collapse
The problem is going to be you have to be rooted to delete it. It is safe and should have been removed before you unrooted.
jd1639 said:
The problem is going to be you have to be rooted to delete it. It is safe and should have been removed before you unrooted.
Click to expand...
Click to collapse
Rerooted in the same way. Ensured I am rooted (even downloaded Root checker). Navigated to system/app but there is no busybox there :/
jblz said:
Rerooted in the same way. Ensured I am rooted (even downloaded Root checker). Navigated to system/app but there is no busybox there :/
Click to expand...
Click to collapse
Look in the /xbin directory
http://forum.xda-developers.com/showthread.php?p=45301834
jd1639 said:
Look in the /xbin directory
http://forum.xda-developers.com/showthread.php?p=45301834
Click to expand...
Click to collapse
Sorry for being such a pain in the ass but under system/xbin I only have
daemonsu
daemonsu-old
dexdump
su
Nothing busybox related.
I've done a full search using ES File Explorer of my local files - 0 results found for busybox.
This may or may not have anything to do with the update issue but it's worth a try. Sometimes the damensu-old file will remain in xbin after unroot. Next time before unrooting uninstall any play store update to the supersu app then unroot from settings in supersu. After you unroot use es file explorer to confirm that the only file left in xbin is dexdump. Then try the ota update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Delete all but dexdump.
Sent from my SAMSUNG-SGH-1337 using XDA Premium 4 mobile app
muniz_ri said:
This may or may not have anything to do with the update issue but it's worth a try. Sometimes the damensu-old file will remain in xbin after unroot. Next time before unrooting uninstall any play store update to the supersu app then unroot from settings in supersu. After you unroot use es file explorer to confirm that the only file left in xbin is dexdump. Then try the ota update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Completed all of these steps. Still saying 'Custom' :/
Sounds like you need to reroot then use triangle away, then use those steps.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Sounds like you need to reroot then use triangle away, then use those steps.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Reading that thread it seems it may not even help. I may just flash back to stock if possible..
I bought the I9505 from Amazon.co.uk - can you please point me in the right direction to what firmware I need?
Google, my friend.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

ROOTED can't delete files off sd-ext

Was hoping someone could shine some light on my situation
Rooted using the towel root app
Verified root through a play store root checker
Superuser works fine
I use xplore file manager changed settings in the file manager for a rooted device, so i dont think it's the file manager.
so i'm wondering do i need to set permissions somewhere I haven't already
Or does this have to do with the locked bootloader?
Fyi: if i connect my phone to my computer I can delete the files through the computer but it doesn't allow me to directly on my phone.
Search "sdfix kitkat" on the play store. Try that and reboot
Sent from my SM-G900V using XDA Premium 4 mobile app
joeyrey said:
Search "sdfix kitkat" on the play store. Try that and reboot
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man

Categories

Resources