Related
Hello, my first post, I searched everywhere all the morning so I choose to register and make the question...
I have here a Samsung Nexus S rooted. Apparetly without any system on it (don't know why).
This is my first android smarthphone, so I'm not a noob on linux sistems but a completly noob regarding Android.
So I followed a wrong tutorial and I rooted the smartphone before copying the custom roms on SD.
I used superboot to grant root permission, it worked and rebooted but nothing happened after the login screen (google+unlocked icon).
No probs, but now I can't access to the SD card to put the roms and the lang pack.
And the phone is completely useless.
I tried with "download mode" but the phone don't connect with the computer via usb (and for me it's difficult to comprehend how to make the download mode, the normal way don't work always and I find a way with Idontknow which combination).
When I start the phone I have the normal Google+unlocked icon but it stucks there.
Recovery mode doesn't have "mount/unmount" text. Only
reboot system
apply update from /sdcard (actually the dir is empty)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
I only need to put that files on the phone to start the upgrading to custom rom...
(I don't have windows pc at home, only linux, I can use XP at office btw)
Any way to install a rom via fastboot?
I'm trying to but...
/fastboot-linux update update-cm-7.0.3-NS-signed.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Remember that the Nexus S does not have an SD Card slot so that's why it says empty directory. Also, as a correction for you, it's called Superuser not Superboot.
Theonew said:
Remember that the Nexus S does not have an SD Card slot so that's why it says empty directory. Also, as a correction for you, it's called Superuser not Superboot.
Click to expand...
Click to collapse
Yeah, I knew that, that was the problem...
Superboot is a script to obtain superuser rights.
Btw I solved by downloading a recovered boot image and installed with fastboot.
I have tried to root my TF doing it the way trippmcnealy say and to no success. I would get the android with gears turning then it would turn into an exclamation point and after a bit boot normally.
Anyone has the same issue? If not and you successfully rooted, feed back would be great. Oh when I got it, I updated without thinking.
Build# HTK75.US_epad-8.6.5.21
Any help would be great appreciated.
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Brand New said:
You can't root a b90 on .21, you have to downgrade to .19 and root with razor claw.
Click to expand...
Click to collapse
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
CobraBytez said:
Is there a method that you are aware of at this point in time that allows you to downgrade from .21? If so could you provide a link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=20799328
baseballfanz said:
http://forum.xda-developers.com/showthread.php?p=20799328
Click to expand...
Click to collapse
Already tried that multiple times and it didn't work.
felix8787 said:
Already tried that multiple times and it didn't work.
Click to expand...
Click to collapse
Double check your file to make sure it's not filename.zip.zip if your PC is set to hide known extension and you rename it to filename.zip you're gonna get the extra .zip behind it.
Also it seems like the 2nd method by trippmcnealy getting better results for peoples
Did that too. I caught the .zip.zip and changed it. Still nada. Will try again. Another thing, from the external sd card, you take the file and copy and paste to filemanager and not in a folder correct? Cause I wasn't putting it in a folder and just added to the filemanager.
Yes it has to be on the root of the sd card, don't put it in any folder.
It will scan the sd card but not scan inside any folder.
Seems like you need two files on the external sd card and two files on the internal sd card as per trippmcnealy's method
So I leave the USB hooked up also as it's recovering? Will try now but with the US .13 first then update to WW .19.
No you don't need the USB connected.
Also after you downloaded the file you did unzip to get
WW_epad-user-8.6.6.19.zip out of the zip file correct?
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
felix8787 said:
Pasted onto root of internal..........powered down......volume down/power then up when prompted...nothing.
Click to expand...
Click to collapse
you pasting one or two files to the internal sd card?
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
felix8787 said:
2, EP101_SDUPDATE and the WW_epad-user-8.6.6.19, still getting the yellow triangle with the exclamation point.
Click to expand...
Click to collapse
You can try this to see, someone said they changed the WW to US and it worked for them. Outside of that I'm not sure what else you can do.
Thats exactly what I was getting ready to do....let you know how it goes.
Quick update, nothing, I did notice that when I do a recovery it says something about recovering kernel and not update?
wait a min...........well, this is what it tells me.
System Update
The update package is not compatible with your current software, please check your software version and version number in Settings and try the correct update package.
System is restored to previous configuration.
After you download the file, did you extract the file within or are you using the file as is?
I transfer both files without extracting anything. Going to try and do the US.13.
Well that didn't work, looks like I will have to wait for a fix, thanks for you time and help!
HI Guys
so here is the thing , everything was working fine, until i flashed ICS the stock rom with CWM, right after flashing my pc was unable to recognize my Transformer as a USB device.
Every time i connect it my transformer freezes for a few seconds and then nothing happens, and on my computer screen it doesn't even recognize a new USB drive.
I tried to connect it to two different computers and the same thing happens which means the problem is with my transformer
Afterwards i Flashed Revolver rom but i still have the same issue
Any one had the same problem? any possible fix for this problem
Edit: Charging Works fine
Thanks
Update: Strangely when i tried to connect the USB when i am on the recovery menu the computer was able to recognize my transformer, ADB was installed but not the MTP so the problem is not a cable or computer problem something much be wrong
I used ViprerMod to root my transformer and i am using Rogue CWM
Thanks
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?p=19093950
Slight hi-jack but I have a question about this.
I updated OTA from scratch (meaning a full and complete wipe). I plugged my tablet into my PC and it downloaded all the drivers. Great!.
I have my Titanium backup folder on the Internal (for some unknown reason why I did that) and I want to put it on my External. I plug the tablet into my PC and the media device icon pulls up. I click on it and both drives pull up and I can open them. Now I want to take my Titanium folder from the internal and put it on the external with just drag and drop. So I drag and drop, only when I click on the folder in the external (tried it to a temp folder on my PC desktop too) it shows as empty. I have USB debugging on and MTP is checked. I have also been able to transfer pix, .zips and other misc files over while inside the tablet with Root Explorer, it is just that the Titanium folder will not cross over for some reason.
Ideas? I did the OTA so not sure that flashable bootloader.zip will work. I am just missing something and I can't figure out what it is. I know they did away with Mass Storage mode with HC and not ICS. How can I get it over there?
Woodrube said:
Ideas? I did the OTA so not sure that flashable bootloader.zip will work. I am just missing something and I can't figure out what it is. I know they did away with Mass Storage mode with HC and not ICS. How can I get it over there?
Click to expand...
Click to collapse
Back then I use to use Root Explorer and copy the whole folder over to external sd card. Now TB have the option to backup directly to external sd card.
Ya, but my dumba$$ pulled a copy of my TB from my phone with all my backups (PowerAmp, Jango Music, At-Bat,...) and installed it on the external when I first got the tablet and then copied it over to the internal (because I didn't know there was such a threat of losing internal on this tablet) once I got a new external I wanted to move it back.
I know that in TB you can set the backup destination to wherever you want it to be, but this is an existing backup folder that I am wanting to move. Wonder if I can put it in my dropbox (900mb- but can be trimmed down for some apps that I know don't work and general cleaning house) and pick it back up to my PC and then transfer it over to external?
Edit:: I used Root Explorer to try and copy it over and let it run all night and when I woke up it was still cycling the icon in the center of the screen, 6hrs later.
baseballfanz said:
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?t=1514658
Click to expand...
Click to collapse
Thank you very much for your advise , But Doesn't that mean that i will go back to stock rom and i won't be able to use the benifits of the revolver rom?
One other thing i should mention is that i already tried flashing this stock rom once before i flashed revolver rom and i had the exact same problem
i mean first flashed ICS CWM flashable >> USB not recognized
Then i tried with the ICS revolver rom >> Same thing USB not recognized by the computer
All what happens is that my Transformer freezes for a few seconds and nothing shows up on my computer
It sucks not being able to connect your device to the computer i mean it is kind of a deal breaker
Any ideas?
Bogda2 said:
Thank you very much for your advise , But Doesn't that mean that i will go back to stock rom and i won't be able to use the benifits of the revolver rom?
One other thing i should mention is that i already tried flashing this stock rom once before i flashed revolver rom and i had the exact same problem
i mean first flashed ICS CWM flashable >> USB not recognized
Then i tried with the ICS revolver rom >> Same thing USB not recognized by the computer
All what happens is that my Transformer freezes for a few seconds and nothing shows up on my computer
It sucks not being able to connect your device to the computer i mean it is kind of a deal breaker
Any ideas?
Click to expand...
Click to collapse
I apologize, didn't see the part that you're on Revolver.
Did you wipe going from one ROM to the next?
baseballfanz said:
Just flash this update on top of your ROM
http://forum.xda-developers.com/showthread.php?t=1514658
Click to expand...
Click to collapse
hi. i can't use MTP on my transformer too. I flashed the CWM flashable ICS ROM (Option B)that was in your link about two days ago. was just wondering if there's a new version and if I flash from that, it'll work?
yuhenyo said:
hi. i can't use MTP on my transformer too. I flashed the CWM flashable ICS ROM (Option B)that was in your link about two days ago. was just wondering if there's a new version and if I flash from that, it'll work?
Click to expand...
Click to collapse
Flash the upgrade link he linked to above for your version. Should clear it up.
Solved:
After Updating to the Latest revolver Rom 1.3.1
Everything Went Back to normal , USB is recognized by the computer
I think this update solved the Issue
According to Gnufabio's Latest Changelog:
Added bootloader to solve usb problems for some people
Dont really know what the Bootloader is but Probably this is what was missing
baseballfanz Thank you very much it is not the first time you've helped me
Cheers
jasonwuzthere said:
Flash the upgrade link he linked to above for your version. Should clear it up.
Click to expand...
Click to collapse
by update, do you mean option A? or is it still the option B?
yuhenyo said:
by update, do you mean option A? or is it still the option B?
Click to expand...
Click to collapse
Just go here and flash the correct update ROM for you're region
http://forum.xda-developers.com/showthread.php?p=19093950
After flashing ICS thru OTA, not able to sunc with Asus, PC recognizes the device, but not able to change from MTP
Any ideia ?
Asus Sync reinstaled, with XP
All credit goes to original posters- this information was compiled from a few different threads to make things easier.
Info came from the following threads:
http://forum.xda-developers.com/showthread.php?t=1803090
http://forum.xda-developers.com/showthread.php?t=1492887
** As always, this has risks. You could brick your device. Do this at your sole discretion. This worked just fine for me, but it might not work for everyone.
** What this does is replace TWRP with the stock recovery, enabling OTA updates to be applied again. It does NOT re-lock your bootloader. It also overwrites your /system image and build.prop with the original .22 image, which should enable the .26 update to be successful.
** This did NOT overwrite any of my settings or apps- that may not always be the case. It's best to expect that this will result in a factory reset, even though in my experience it didn't. Better to be prepared and pleasantly surprised.
** This assumes you installed TWRP or another recovery and need to revert to Stock recovery. Although I'd recommend running the full process anyway, as this ensures you have a fully stock /system partition, build.prop, etc. You can try skipping to step 10 if you're still on stock recovery.
1: Run a TWRP and/or Titanium backup, just in case. Grab everything including recovery if using TWRP.
1a: To be on the safe side, make sure you don't have any other update zips at the root of your external SD or internal storage.
2: Download the appropriate 9.4.5.22 file for your device from here:
3: Extract files from within zip
4: Extract files again from the extracted zip
5: Copy extracted "blob" file to root of folder of the removable Micro SD card or some other folder
6: Through ADB shell or Terminal Emulator, run the following: (May take from 5 to 20 minutes)
Code:
su
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
If copying the "blob" file to the SD card in the keyboard dock, use: dd if=/Removable/SD/blob of=/dev/block/mmcblk0p4
If copying it to the internal memory, use: dd if=/sdcard/blob of=/dev/block/mmcblk0p4
7: Reboot only if the following is displayed (exact numbers may be different):
Code:
1068769+1 records in
1068769+1 records out
547210197 bytes transferred in 153.991 secs (3553520 bytes/sec)
Update process will automatically launch
8: Once booted up, root device by using debugfs root here
9: Do not make any other changes to build.prop or the /system directory
10: Download the appropriate dlpkgfile. The US version of the update can be downloaded here. I'll add any others as they are posted.
11: Use root explorer to copy "dlpkgfile" into /cache/ directory. Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Code:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
12: Create the file called "command" under /cache/recovery/ directory.
13: Write this statement in the file /cache/recovery/command
Code:
--update_package=/cache/dlpkgfile
14: Finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down". The update process should start... wait for it to complete. (This will take a little while, as the dalvik-cache will be rebuilt and your camera firmware will be updated. Once it completes, you should have the updated firmware installed on your tablet
15: Once the update is complete and you're at your home screen, you'll need to re-root. Just follow step 8 again.
16: Once rooted again, you can reinstall TWRP according to the original instructions, or just leave stock recovery on for now to avoid having to do this again once the next OTA comes out.
thanks for taking the risk and trying all this out. i just ran through all the steps and it worked perfectly. (i also had TWRP)
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Headcase_Fargone said:
Really stupid question incoming, skip this post if you're in a cranky mood...
How can I tell if I'm running TWRP? I used the unlock tool from Asus then the debugfs root method from another thread in this sub. When I boot into recovery I get a red exclamation point over my surgery table android. It just says something along the lines of Android recovery, so I assume that's stock.
Click to expand...
Click to collapse
Yeah, it sounds like you're on standard recovery, and maybe there's an update file on your SD card or in cache that's failing.
If you follow the OP, it should enable you to update if you haven't yet. It'll pretty much do everything back to default .22 except relocking the bootloader.
Oh, as an afterthought, make sure you don't have any other update zips at the root of your external SD or internal storage, just to be safe.
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
rsbuffalo said:
followed all steps and seems to work. However, in the last step after I created the command file with root explorer, I booted into stock recovery and recovery screen is now just blinking with the Android icon. This does not seem correct! Any suggestions?
Click to expand...
Click to collapse
How do you mean blinking? Does the android icon have a red triangle?
i think he may have missed the part where he needs to hit volume up after volume down.
Thanks eoh7678! I did have some update zips at root sdcard that seemed to be causing an issue. I deleted the files and uninstalled busybox. Then I redid the command file. Update was successful!!! About tablet now shows IML74K.US_epad-9.4.5.26-20120720.
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
newellj79 said:
Nice work. I was not aware you could go back to stock recovery. I may give this a go. I'm really blown away that somebody hasn't released a flashable zip that is custom stock ready yet.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually have one mostly ready to go, according to what I've read, but to be honest, I've only ever made update zips for samsung or HTC phones. I've never tried this whole blob thing. TBH, I'm scared to death to try flashing my own creation.
Thank you for posting the howto (you saved me from having to write my method) I did everything from my TF700 using terminal and remote explorer to get recovery reverted and .26 OTA installed.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
I haven't tried the manual update with this one, as I received it OTA before this one was posted, but it erased my su. Happily RootKeeper preserved it.
newellj79 said:
I'm curious about why to root between installing .22 and upgrading to .26? Does the root method not work on .26? If you root before upgrading to .26 does it retain root natively or do you need to use voodoo root keeper?
Click to expand...
Click to collapse
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
eoh7678 said:
For me, at least, restoring .22 from the blob removed su. Probably rootkeeper would have solved, but honestly, I figured the safest bet was just to reroot between to make it easier and less prone to problems.
Click to expand...
Click to collapse
Kewl. Just curious. Almost done.
Edit... worked great. Thanks!
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
cctaylor410 said:
Having an issue.... Once i move dlpkgfile to cache, make the command file, and reboot to recovery i just get the android with the red triangle. Also once it reboots and i check the cache folder the command file is gone. So at the moment im stuck on 22
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
DroidEris1981 said:
I was having the same problem. My issue was when I downloaded the dlpkgfile a .bin extension was added to the file name. Make sure there is no extension on the filename.
Click to expand...
Click to collapse
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
cctaylor410 said:
Im mildly retarded cause the file was 0kb lol. Re-downloading and trying again
EDIT: every copy method i try dlpkgfile ends up as 0kb, not sure what is going on. Using root explorer and terminal fail.
Sent from my unlocked and rooted TF700T using the XDA Premium App
Click to expand...
Click to collapse
I used ES File Explorer (make sure to check the options in settings to tell it you have a rooted phone) to do everything (including creating the file) and it worked great. ES File Explorer is *awesome* - check it out.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
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?