Database Info

BEST Guide for Returning to Stock ! (Add to guide thread?)

Here are the directions and files used to fix this problem (do not type any of the "quotation marks"):
1. Download the .zip file from here: http://www.megaupload.com/?d=YUYEMJNM
and put it on the root of your sdcard. (Do not unzip the file). Then rename it to PD15IMG.zip .
2. Download the miscnew file to your computer (uploaded as attachment to this post). Unzip it and place the miscnew.img file that was in the zip onto the root of your sdcard. You can delete the .zip file after you do this.
3. Boot your phone up like normal and connect your phone to your computer.
4. Make sure your sdcard is NOT mounted (but make sure those 2 files were copied to your sdcard).
5. Go into adb and type "adb shell"
6. Then type, "su"
7. Then type, "dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17"
8. Once this is done after about 5 seconds, turn your phone off and unplug from the computer.
9. Once the phone is off, hold down the volume-down key and the power button until you arrive at the bootloader. Once there, the phone should automatically start checking that .zip file you downloaded to the root of your sdcard. After its done checking, it will ask you if you want to continue, and just follow the prompt to say "yes" and YOU'RE DONE!
This guide was made by travisjames and was just put into my own words. His guide was a derivative of Apache14's OTA and Radio downgrade guide for the T-Mobile G2.
Also, thanks to Clarknick27 for tipping me off on how to get back into my phone after it was unbootable.
***Please click "thanks" if this helped you!

Ignore/Wrong thread...

two questions-
if i used gfree, do i need to undo gfree 1st? (you make no mention of rooting techniques, and if this undoes all those or not)
second, my phone, about a month ago, lost data connectivity on the usb port-- in other words, it charges fine, but i can not get any computer to pick it up any more to transfer files are use adb, which is a royal pain. -- can i use terminal emulator to accomplish your commands, or am I SOL ?
thanks

Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.

thanks jack,
would the syntax be exactly the same as above via term em?

Yes, just skip the "adb shell" command.

Is this to undo 2.3.4 GB update and take it back to 2.2.1?

How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App

andrewp3481 said:
How do I undo gfree? And if I just run the pg15img will I keep root? I need a way to return to stock but rooted.
Sent from my Incredible 2 using XDA App
Click to expand...
Click to collapse
First question, Here is the thread you need to undo gfree (get s-on) http://forum.xda-developers.com/showthread.php?t=858996 (about half way down OP)
Second question, no you will not keep root
witch stock rom do you want rooted, stock 2.3.4 can not be rooted right now

So... to summarize, this would be to revert back to Android 2.3.4, sense 3.5 STOCK, without root, eng. hboot, or s=off.
In other words, if you purchased a MT4G now, or received a replacement MT4G with 2.3.4.... Following these steps will give you this new gingerbread stock state (approximately).
Please confirm. Thanks!

can i use this steps with terminal emulator on my phone instead of adb?

unciviilized said:
can i use this steps with terminal emulator on my phone instead of adb?
Click to expand...
Click to collapse
Yes...check the 3rd and 4th post of this thread....

Just curious, so if I flash this ROM in recovery, will I lose root, s-off, etc.?
What I'm trying to do is flash the phone to the MT4G stock rom (which I assume this is), use gfree to sim unlock it, then revert back to my nandroid backup, so I wanna make sure this will not interfere with my root access before I proceed to flashing it. Thanks in advance to whoever answers me~!

ronin178 said:
Yes...check the 3rd and 4th post of this thread....
Click to expand...
Click to collapse
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?

unciviilized said:
ok so when im on emulator i do "s" and it says permission denied,
then i got to command prompt and it says adb shell is not recognized as and internal or external command. Any suggestions?
Click to expand...
Click to collapse
You don't need to type adb shell because you are on terminal emulator.
Just type su to gain superuser access.
Then type dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
Make sure you have the file miscnew.img in the root of your sd card.

Absolutely Perfect
I have looked and looked all over both XDA and the Interent in general. I was trying to restore my Glacier (MyTouch 4g) from stock 2.3.4 to stock 2.2. NOTHING worked. It got to the point that I didn't even remember everything that I tried. I followed this guide to the T. PERFECT!!! I am now back to having my phone exactly how I left the Tmo store with it.
I CANNOT THANK YOU ENOUGH!!

Great work in helping people out that don't understand. And making it a less strenious process
Sent from my HTC Glacier using xda premium

Jack_R1 said:
Yes, you need to undo Gfree.
Yes, you can run the commands from Terminal Emulator.
Added to Wiki.
Click to expand...
Click to collapse
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!

socal88 said:
Sorry, a complete noob to "gfree". I'm a new convert to GSM as I was with SPrint CDMA for 10 years until a couple weeks ago. I've rooted Samsing phones but never an HTC.
Anyways, I just purchased a MyTouch that had been rooted and loaded with Virtuous ROM. It's for my wife and she wants it back to stock. I tried all your directions exactly but still will not work. I'm assuming it's this "gfree" issue. I followed the link to the other thread but it's not clear on exactly what I need to do in my situation.
When I run the bootloader, it says bad or no such image... I have confirmed I have PD15IMG.zip and miscnew.img in the sdcard root directory.
Can someone please show me in simplified terms. Thanks!
Click to expand...
Click to collapse
If you are new to this rooting stuffs, i suggest don't go with methods, that have potential to brick your phone.
Just do this simple method, Follow the link in my signature, you will see a Rooted version of the stock 2.3.4 rom.
Just flash the Rom through your recovery.........no big deal.......easy way to get the stock feel.....
Follow the instructions carefully.........Happy Flashing........

Thanks for the great help. One more question -- How do I turn "quick boot" off?

[Q] Got S-Off but Recovery failed to install

Ok, I ran Revolutionary, got the mod to flash to get root, but when I hit Recovery on the boot screen I get some sort of lockup that requires a battery pull to recover from.
I've installed a terminal emulator, and have the root mod from Revolutionary on /mnt/SDCard. Is there some way I can run this from the terminal emulator on my phone?
I have ADB installed on my PC but I'm having some issues with that as well and would prefer to run anything directly from a terminal on my phone if possible.
BTW the phone boots back into a usable state with no issues*. I have S-Off, just don't have root.
*Well, with no issues that it didn't have before I ran Revolutionary.

Are you sure your superuser zip flashed correctly? When you go into terminal emulator and type su and hit enter does superuser ask for permissions? If it says permission denied then your root didn't work. If it does work then follow these steps:
unclespoon said:
If you're already rooted with s-off and want to update your recovery, but are like me and don't have access from work to ADB or don't know how to use it, here's how you can update to the 4.0.0.9 recovery:
1. Download Recovery 4.0.0.9 from Modaco's website
2. Using Root Explorer, find the file in your downloads folder on the sdcard.
3. Paste the recovery img file into your phone's /data/local folder.
4. In terminal emulator, first type "su" and then type "'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21" and let it transfer the recovery file.
Simple as that!
Click to expand...
Click to collapse
Make sure the file ends in .img and not .txt or whatever it is that people keep running into. And make SURE the text is verbatim (without quotes obviously) or you'll run into errors. If it tries to capitalize a letter on you, pull out the hardware keyboard and make sure it's lowercase. If it doesn't let you input a special character, use the soft keyboard.

I appreciate the reply.
I'm quite certain that superuser didn't flash at all. The Recovery didn't install correctly, and hangs when I try to use it.
So what I want/need to do (unless someone has a better idea) is flash the MoDaCo recovery somehow. I tried to manually copy it to the correct block, but I do NOT have root.
Or manually flash the super user mod. I have a terminal emulator on my phone and can enter commands there, the super user mod is on /mnt/SDCard/.
I've also found this thread, which I intend to try to do later on after I've had more than 3 hrs of sleep in the past 24.

Yes, that's a great thread. Follow those instructions. If I were you I'd assume nothing has worked thus far and try starting over from scratch

I used the thread in the dev section the one labeled for dummies. worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1286324

unclespoon said:
Yes, that's a great thread. Follow those instructions. If I were you I'd assume nothing has worked thus far and try starting over from scratch
Click to expand...
Click to collapse
That fixed it. I had issues with ADB so I had to uninstall that and reinstall it. Then I ran Revolutionary and got S-Off for real. Installing MoDaCo clockwork mod went like clockwork.
I'm now running UndeadK9's AOSP Gone Wild on Sense. I'm thinking I like some of the Sense widgets better, so I'll be reflashing his other ROM soon.
Now I just need to figure out how to do a batch restore in Titanium Backup and I'll be golden.

Have to buy full or use a cracked version if their is one.
Sent from my Crack Injected Doubleshot using xda premium

Droidmoder said:
Have to buy full or use a cracked version if their is one.
Sent from my Crack Injected Doubleshot using xda premium
Click to expand...
Click to collapse
I bought the full version of both Titanium Backup and Root Explorer.

Tb explains itself. Great app can also freeze updates and such so you won't be bothered by them.
Root explorer can fix premissions which is good and also various other things.
Two very good buys .
Sent from my Crack Injected Doubleshot using xda premium

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

New Root Method for AT&T Samsung Galaxy S 4 (OTA MF3 + Safe update to MK2)

HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR or 7-zip).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here.
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Stopping AT&T Auto Software Update
Since AT&T just rolled out the new update (4.3), I add this short guide on how to stop it before it becomes late! Note that these steps require root, so you should follow the rooting steps first.
Download and install "App Quarantine ROOT/FREEZE" from Play Store.
Open the app and go to settings by tapping on the wrench icon at the top right of the screen.
Uncheck the "Hide system services" option.
Go back to the app and select "AT&T Software update".
Tap on the lock icon on the top right of the screen.
It may ask you to enable the USB debugging.
Feel safe from AT&T's new attack
How to get MK2 without losing root
I have tested this approach and it worked for myself. You should consider the risk of losing the root access and follow these steps on your on risk:
Root your MF3 phone using the approach described earlier in this post.
Stop AT&T from pushing the update as described above.
Install Super SU Pro. Note that this is not a free app and it is an add-on for Super SU.
Run Super SU. Go to Settings and check the "Survival Mode". If you don't have this option, probably you don't have the Pro version.
Disable your guard against the AT&T update by enabling "AT&T Software update".
Let the device update itself and hope for the best.
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***

MF3

Can't wait to try it...
Sent from my SAMSUNG-SGH-I337 using xda premium

I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Billsfan99 said:
I get permission denied. In terminal emulator I type
CD /mnt/extSdCard
./pwn
Then it says permission denied
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Same here

Nick James said:
Same here
Click to expand...
Click to collapse
Sorry guys. I missed one step. You should format the external SD card to exFAT. Windows supports it.

Question
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.

ddslee said:
Does this mean that we can flash Google Edition rom on the MF3 AT&T S4?
Or do we have to wait until more exploits are discovered?
I was rocking GE rom until I went back to the stock Samsung ROM to SIM unlock my phone.
I got screwed by the OTA MF3 and have been following this forum everyday for a new root method.
Click to expand...
Click to collapse
This only allows you to root your device. No method to use custom ROM has been found yet.

So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?

Nick James said:
So my phone WAS rooted, stock ROM.
I installed the OTA update on accident.
Ran the new exploit
Installed SuperSU
It asked me if I wanted to update the binary, I told it "Continue" and it comes back with "failed"
I suspect this is because of my previous root?
Click to expand...
Click to collapse
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.

jortex said:
No need to install anything yourself. Uninstall everything and run SuperSU. Let it update itself. If that doesn't work, a reboot may help.
Also try to make sure that you have root.
Click to expand...
Click to collapse
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?

Nick James said:
I never had SuperSU installed though.
You're talking about this, https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Right?
Click to expand...
Click to collapse
Yes. It is being installed by the script.sh. You just need to update it. That's it.

jortex said:
Yes. It is being installed by the script.sh. You just need to update it. That's it.
Click to expand...
Click to collapse
I'm not following you. What do you mean I just need to update it? The script never installed it. I had t download it from the market and once I did that it asked me, upon opening it for the first time, "The SU binary needs to be updated. Continue?" and when I hit Continue it then says "If you have a custome recovery like TWRP or CWM, that can be used to (try to) install the SU binary. this is recommended for HTC devices. How would you like to install the SU binary? Normal or TWRP/CWM
I've tried both options with no luck.

When I run the exploit, it also says my device isnt supported but stays it obtained root?

Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
Mine said the same thing. I just kept going and typed the ./script.sh and thats it.

Nick James said:
When I run the exploit, it also says my device isnt supported but stays it obtained root?
Click to expand...
Click to collapse
That's fine. It tries several exploits. The first one does not apply to your device (SG4), but the last one does.
UPDATE: You already "obtained root". Look at the prompt which is changed from $ to #. As wahbob suggested, continue running script.sh. This file installs SuperSU for you. Then you can run it without explicitly getting it from Play Store.

jortex said:
This only allows you to root your device. No method to use custom ROM have been found yet.
Click to expand...
Click to collapse
Ahhh Thanks for the root though!

Thanks! Just tried it and I have Root again

thanks for this

Sorry for the noob question but when I run the cd/mnt/extsdcard command I get a "not found". Does anybody know what I'm doing wrong?

May Update Help?

Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?

Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly

Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...

Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!

I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.

Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?

Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one

pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it

Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!

pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.

exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).

Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome

Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding​ it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.