yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] ThatDude24:
For a newbie, is this the best/easiest way to go about the whole root thing.It seems like it. Once i get a confirmation, im gonna go head and follow this.
[T-Mobile Samsung Galaxy S 4] RGD622:
I just did this, and it worked. I installed twrp 2.5.0.0 .tar, and I am in the recovery menu. First try, no issues.
[T-Mobile Samsung Galaxy S 4] jbdan:
Thanks for all the work on this OP (and cohorts). Simply done in 10 minutes on my new MDL GS4.

---------- Post added at 01:12 PM ---------- Previous post was at 12:40 PM ----------

Any clear advantage to running your kernel matt? I'm on MDL all the way around (I assume or am I on a mdb kernel after rooting the OTA?)?

I see that you explain and I quote ""non-SetUID restricted kernel"

Being able to have root on the latest firmware."

I have root and am on the latest firmware correct....or am I missing something (likely :p)
[T-Mobile Samsung Galaxy S 4] mattlgroff:
My kernel uses the MDL defconfig and ramdisk, so it might be "slightly" better than MDB. I haven't had a problem using my kernel as a daily driver, but there doesn't seem to be anything that couldn't be explained by the placebo affect.
[T-Mobile Samsung Galaxy S 4] Dazlan:
This helped tremendously! Thanks to Matt as well for getting this set up. :)
[T-Mobile Samsung Galaxy S 4] KennyG123:
Thread stuck
[T-Mobile Samsung Galaxy S 4] mattlgroff:
Rooting with any method breaks OTA updating. You would need to use triangle away and an official firmware tar.md5 to restore them, I'd imagine.
[T-Mobile Samsung Galaxy S 4] omf05:
Something I've noticed.

Whenever I flash this root file and I turn my brightness down on a black screen I see a reddish color instead of a pitch black. This makes it hard to watch any videos that have dark scenes. Once I restored back to stock my blacks where pitch black again and videos looked well.
[T-Mobile Samsung Galaxy S 4] freecbc3:
i cant get this to work either.
[T-Mobile Samsung Galaxy S 4] Piippes:
Hey guys, I have read guides and the forums after purchasing the S4 on Monday. And stupid as I was I updated with OTA before applying root...

Anyhow I have some question i hope I could get som answers to, and in advance i apologize for my noobnes:

- What im wondering here is what is the difference between this method and the motochopper method? I apologize in advance if its a stupid question.

- Is there a step by step guide video, maybe of this method? If so I can't find it. All the videos are pre-OTA.

- Can you do this guide with mac OSX? Can't seem to find Odin for OSX...

Some information: I have GT-I9505, International device I think you call it. So theres no Sprint, Verizon, AT&T and Tmobile in my country.

Thanks in advance!
[T-Mobile Samsung Galaxy S 4] madamuz:
Galaxy

buen aporte, lo voy a probar, muchas gracias
[T-Mobile Samsung Galaxy S 4] cbbplanet:
Does it matter which TAR file we should use? the stock TAR or UVUAMDL Official TAR?
[T-Mobile Samsung Galaxy S 4] sahussa9:
Worked like a charm first try no problem! Thank you.
[T-Mobile Samsung Galaxy S 4] krazy2o6:
I can't seem to get it to work either. Followed all the steps and when its starts to process It says "E://can't verify signature" than it finishes "rooting" and reboots. But the phone doesn't seem to be rooted
[T-Mobile Samsung Galaxy S 4] bigsammoe:
ditto on not being rooted.. getting the same RED when flashing zip
[T-Mobile Samsung Galaxy S 4] Razzzzer:
Verified this works on phone purchased May 15th with the OTA update.

I had to do the "hold volume up while odin" trick in order to get the custom recovery, other than that it worked just fine.
[T-Mobile Samsung Galaxy S 4] krazy2o6:
Issue fixed. Needed to do the battery pull trick
[T-Mobile Samsung Galaxy S 4] mattlgroff:
You need to flash custom recovery with Odin. Follow the instructions exactly or it won't stick when you flash it.

Running Root.zip through Stock Recovery leads to Signature Verification fail.
[T-Mobile Samsung Galaxy S 4] driodman98:
Does not work for me. I cant get Odin to see my phone. I done it on a PC, Mac with Parallels, Mac with straight bootcamp and with Hiemdell on Mac. Still will not see my phone. I have tried all kinds of drivers. Any suggestions?
[T-Mobile Samsung Galaxy S 4] Salt.King:
+1 ...did the same method two days ago, worked perfectly. ODIN'ed TWRP, phone rooted - with no issue at all

I began at full-on stock with the MDL OTA, which I kept postponing for several days; until my finger accidentally hit START on the update screen while reaching for the Home button to get out of it. :eek:

---------- Post added at 05:59 PM ---------- Previous post was at 05:51 PM ----------

Settings>About Device>Build Number (tap 5 times) for Development Mode?
[T-Mobile Samsung Galaxy S 4] seawolf823:
What do you mean by this^^^

What am I supposed to do after pulling the battery? I'm a little confused. Thanks for any help
[T-Mobile Samsung Galaxy S 4] Razzzzer:
in the thread they talked about it...

providing you have the drivers already (kies) you start odin. put phone in download mode and connect

navigate to the custom recovery file and (what i did) right before i hit the load button i held the upvolume button so that the phone (when odin reboots it) goes straight into the recovery.

then i reboot the phone (select not to over-write) and i can get to the recovery okay...
[T-Mobile Samsung Galaxy S 4] matthewdavis:
Only addition is to install this kernel after all is done. This will allow root and workaround the SUID restrictions.
[T-Mobile Samsung Galaxy S 4] ispot:
Thank you

Again, I made myself look stupid :)
[T-Mobile Samsung Galaxy S 4] kioshi:
followed the steps in OP but when i go to flash the root file it says in the command lines that signature couldnt be verified??

And when i install titanium back up it says root cannot be verified, etc.

Not new to rooting but this is my first samsung device rooting minus Galaxy nexus.

Thanks You
[T-Mobile Samsung Galaxy S 4] 92drls:
nutshell- "there is no SU binary installed, and SuperSU cannot install it".

Well I've been trying for a couple days now to avoid asking this question and searching throughout both of the "how to root" threads but still cant get this fixed.

I have flashed the UID fix kernel, the original .tar file, used motochopper etc etc.

As of now I stand with the kernel saying its from Apr 26 so it should be pre OTA, but whenever I try to get into SU it says "there is no SU binary installed, and SuperSU cannot install it".

Where can I go from here? I've tried installed the superuser zip in recovery but no dice.

Thanks for the help in advance.
[T-Mobile Samsung Galaxy S 4] XxKINGxX2580:
Thanks! this was really helpful.
[T-Mobile Samsung Galaxy S 4] Bowmanspeer:
I have a similar problem. I get this same error and I cannot boot into any kind of recovery. I hold the power and vol-up button. When the Samsung with blue writing comes up I let go then the device boots normally. If I continue to hold buttons it won't do anything after initial Samsung and blue lettering. I could hold it for 5 minutes and it won't boot. As soon as I let go it will boot normally. I initially used ODIN installing OUDHS. Got the stock recovery (from what someones screenshot said). It was so small I couldn't read it. I went back to ODIN and installed the TWRP tar. Now I can't get into any kind of recovery though the phone does say it is modified.

What I will do from here is use ODIN to return to stock following the thread http://xdaforums.com/showthread.php?t=2258628 From there I should be able to start over now that some of the "bugs" have been ironed out, well-- and the fact that I have read the whole thread now. :p

But I wonder if hitting the factory reset would do the trick? Don't have anything to lose...
[T-Mobile Samsung Galaxy S 4] 92drls:
Actually once the blue "recovery booting" writing shows up release the power key but keep holding the volume key until the android guy pops up, that's if you have flashed a recovery.
[T-Mobile Samsung Galaxy S 4] b12ando:
Thanks for posting this simple to follow tutorial! It really helped :)
[T-Mobile Samsung Galaxy S 4] IronWolve:
I had the latest OTA MDL version update. Using the OUDHS recovery it would keep erroring out when I tried to install any zip file.

I switched to CWM and no problems flashing ROOT_M919UVUAMDL.

So I'm rooted, thanks!
[T-Mobile Samsung Galaxy S 4] rtwrobert10:
Excited

I don't yet have an S4 but I plan on doing this right when I get it! Thanks :)
[T-Mobile Samsung Galaxy S 4] ivesdotkom:
this worked great! thank you so much.
[T-Mobile Samsung Galaxy S 4] PseudoChris:
e: signature verification failed issue (resolved)

With auto-reboot ticked, I was unable to root the device successfully.

As explained in the instructions,

UNCHECKING 'auto-reboot', then removing the battery after the flash is complete does allow the Custom Recovery to "stick".

Thanks to OP. I just can't stand not being able to remove bloatware. <3 Devs <3 Root <3 XDA :)
[T-Mobile Samsung Galaxy S 4] vedhed21:
Flashed stock through Odin then root. But now what?

Sorry if this has been covered, though I haven't seen it here or on the Dev page. I'm now rooted and I have TWRP running but is says the baseband and build are different when I go to settings > about. So do I now go back to Odin and flash the updated version or will that cause me to lose root. Again, I hope I haven't jumped the gun by asking. Been reading forums and rooting for about 3 hours now so I'm probably a bit short on patience. Any help would be appreciated.

Update... Looks like I have more issues. WiFi doesn't work and it won't mount my SD card. I can try another, but I should probably get some sleep. HMM... it says TWRP is taking up 5g of my storage space too. I will now ram my head against the wall repeatedly.
[T-Mobile Samsung Galaxy S 4] Bowmanspeer:
Oh the simple little things...

Root checker now says, "Congratulations! You have ROOT access!" Thank you! Button hit!

Edit: Thought I'd mention, that I don't have any wifi issues after a full day. :highfive:
[T-Mobile Samsung Galaxy S 4] kioshi:
flashing CloclworksMod touch recovery worked for me when trying to flash root file.

Rooted the Dad's S4! Thanks!
[T-Mobile Samsung Galaxy S 4] bigsammoe:
unchecking auto reboot and battery pull was the ticket! i feel dumb and shoulda read more.. ah well hopefully someone else laughs at me!
[Nexus S Q&A, Help & Troubleshooting] DizturbedOne:
When I used CWM Touch 6.0.1.0 it ended up bricking my device permanently by flashing over old data repeatedly and eventually corrupting the internal MMC. No one on this forum could figure out (or just didn't bother to help me) how to fix the corrupted partitions once it had happened. When you try to format or erase anything via this recovery, it doesn't seem to actually work, although it will act as if it did. I would suggest staying away from CWM altogether on this device. Other versions have been known to not work well with other Samsung devices also, such as 6.0.1.2 on the Galaxy Tab 2.

The inability to actually format causes you to install "dirty" ROM's over each other whenever you install a ROM. You have no recourse but to use a different recovery to actually wipe any partitions you may need to wipe. My advice? Use a different recovery in the first place, and stay AWAY from CWM for this device.

In short, CWM Touch corrupted the internal memory chip on this phone after several wipes that did not actually work. Although I can install various recoveries via fastboot (the NAND is fine), the main memory partition is corrupt and will not allow me to install anything on it.

That was in November btw. I spent almost 6 months trying to fix it now... Guess I'm just stuck without a smartphone until I upgrade... IN 14 MONTHS. :crying:
[Nexus S Q&A, Help & Troubleshooting] polobunny:
The Nexus S has shown slightly high NAND failure rates lately, mostly because it's getting old I believe.

I wouldn't blame CWM, that's pulling it... I have personally used it for 2 years straight and all was fine. Others have had similar experiences too and never got any issue whatsoever.

Not dissimilar to the power button failure conspiracies if you ask me.
[Nexus S Q&A, Help & Troubleshooting] ttakacs:
The same thing happened to me, I believe -- my file system became corrupted -- but not because of CWM, which I have never used on the phone.
[HTC One X+] matt4541:
I'm pretty sure I loaded a kernel incorrectly and now all I can get to is the Bootloader and Recovery. I am to the point of just flashing the RUU back to stock but I have never done this and wanted to know if that erased the sd card. I have backups on the sd card but the computer will no longer recognize the phone so I can't get to my backup files.
[HTC One X+] tmknight:
SD should remain safe with stock flash; though it is curious that you can get into boot loader but you can't access the phone via ADB or even Fastboot?
[Galaxy S III Q&A, Help & Troubleshooting] VinciusG:
Anyone can tell me if is it necessary to update the i9300 bootloader? Does it help with SDS? Does it Show a message like Yellow Triangles or something like that with custom recoveries if I update it? (Android System Info says that I've got I9300XBLH1 version)

Thanks in advance
[Galaxy S III Q&A, Help & Troubleshooting] wangdaning:
There is no known benefit of the bootloader in regards to sds. If you update you will get a red triangle if you use custom recovery or kernel.
[Galaxy S III Q&A, Help & Troubleshooting] VinciusG:
Thanks, I'll stick with mine so!
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
This is very outdated information.

The bootloader is what provides download mode. Download mode has a kernel, ergo if you want to use download mode, you'd better be on a 4.1.2 bootloader.

OP read the "[important] sds - are you covered?" Sticky thread in general
[Galaxy S III Q&A, Help & Troubleshooting] wangdaning:
Very true, I really think the danger there is minimal though. I guess it depends on how often you use download mode though. I normally use wanam's roms, which are flashed in recovery. I only use download mode in my failed attempts to get to an older bootloader:o
[Galaxy S III Q&A, Help & Troubleshooting] danarama:
Personally, being able to reset the flash counter permanently is much more important to me.

The problem with download mode is that you use it to flash (or write to NAND) so the use of download mode is extremely risky since all it does, is write, which is what triggers SDS.

I'm very happy not to use download mode though, i dont need it for any reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] osmxgohan:
I can install roms for sprint forum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
what model number is your S3? i've seen I9300's on telcel. if this is what you have as well, you should be in the i9300 forums. cheers
[G2 and Desire Z Q&A, Help & Troubleshooting] demkantor:
haha, i doubt ill be in germany any time soon... but i will be in greece in a month or so...

well it sounds like youre trying all the right things and it possibly is a hardware fault. but being you rooted 3 years ago you dont have true radio s-off, as it wasnt around.

if it were me, i would unroot, then follow the gfree method to downgrade and root via gfree, this will fully wipe out all partitions (except efs) and then flash a tried and true rom like cm7, hopefully all will be well at this point... if not, hardware...
[G2 and Desire Z Q&A, Help & Troubleshooting] _RaZziel_:
Thank you for your advice. I did as you told me and went through the pain to reinstall stock Froyo as well as stock recovery and hboot. I also had s-on (at leats that's what hboot and gfree_verify said). Then I went to reroot it again, this time using gfree1.0 (which was definitely not what I used last time).

But unfortunately WiFi did not work neither with stock Froyo nor after rerooting and running CM7. Bluetooth still worked fine in every case... Log still says the exact same thing.

There is just two things left that might be worth a try, but it's a long shot. Could it be a problem with some data on the efs-partition that is messed up? As far as I understand it that is where android stores important information about IMEI, MAC-adress an the like. But I really do not know how to restore this partition even if it were the cause. Or could it be a problem with the RIL since that is what communicates with the radio? But I also do not know how to restore this if it were the cause (but it's just said that matching the RIL might just improve performance).

What's your opinion about this? Do you think that a look at the phone's insides might yield any results/certainty?
[G2 and Desire Z Q&A, Help & Troubleshooting] demkantor:
Unfortunetly if you never made a backup of your efs partition there is no way to restore this, you can back it up now, wipe it, restore and see if that helps but I doubt it.

Ril is matched when you downgraded so that's not it. Trutfully my best guess is hardware, sorry
[G2 and Desire Z Q&A, Help & Troubleshooting] _RaZziel_:
Unfortunately, I never made a backup of my /efs. I also tried wiping it, but no change.

The only sad thing is, that there is no adequate replacement...

I still don't get why BT is working and WiFi is not while both use the same chip, but that will stay a mystery forever unresolved.

Is there any way to close this tread? Somehow I don't see any.
[G2 and Desire Z Q&A, Help & Troubleshooting] Android_Monsters:
Mine does what you are describing, but it's cause my gf dropped it

---------- Post added at 01:10 AM ---------- Previous post was at 01:08 AM ----------

And disconnected the wireless "modem"

The drop was pretty severe, however. I needed a whole new battery cover
[G2 and Desire Z Q&A, Help & Troubleshooting] coderzs:
op did you solved error ?
[G2 and Desire Z Q&A, Help & Troubleshooting] _RaZziel_:
Nope, I could not solve the issue and I did not disassemble my phone and risk being left without one. So far, my mobile data plan has been sufficient and for large data, I access the internet via a USB-cable. I will get a new phone though when I am less busy at work.

Sent from my HTC Vision
[General Questions and Answers] jimmy191990:
I really wanted the S4 so I placed an order with Sprint. Now looking at my bill which is over $200 for two lines, Im not going to pay that much because its less then $100 with Straight-Talk and its just as good.

So here is my question... If I order a AT&T Micro Sim card and put it in the Galaxy S4 will it work? I will consider rooting the S4 and unlocking it. If there is any possible way please let me know. The Galaxy S4 takes a Micro sim so im thinking there has to be a way. I will try anything so please share any and all information. Thanks for the help
[General Questions and Answers] jimmy191990:
Really

Funny this is suppose to be one of the biggest programmer /developer site yet I cant ever seem to get an answer. Waste of time
[One (M7) Q&A, Help & Troubleshooting] runwaypimp:
Is anyone else having issues with 5.0 GHz WiFi connections?

I have a Netgear D6300 WiFi 802.11ac Dual Band Router, which worked fine on 5 GHz band with the HTC One X but the new HTC One struggles to stay connected & forces me to connect to the 2.4 GHz band which is stable.

It seems to struggle with distance. Short distances. In the same room as the router it is fine but in all my other rooms its terrible & reconnects or times out.

Again, the HTC One X was happy under the same conditions.
[One (M7) Q&A, Help & Troubleshooting] alphaod:
I have the Asus RT-AC66U, and I don't have any connection issues. In fact I find in many cases the One has better reception compared to that on my other devices.
[One (M7) Q&A, Help & Troubleshooting] jalati:
I'm having the same issue with my d6300 and HTC one. Might try and downgrade to see if that works
[One (M7) Q&A, Help & Troubleshooting] shadowboy23:
I have a D6300 as well and no problems here. I also have a Billion 7800VDOX and have no problems either.
[One (M7) Q&A, Help & Troubleshooting] jalati:
Which HTC one do you have? I'm thinking my Telstra firmware is bugged
[One (M7) Q&A, Help & Troubleshooting] kenned88:
I have the same problem just with a D-Link Dir-825 running openwrt. 2.4GHz runs fine but it can't connect to my 5GHz
[One (M7) Q&A, Help & Troubleshooting] jalati:
Still no good connecting my HTC One to my netgear d6300. tried downgrading the router, changed from Telstra to ARHD 11.0 and no dice. The weired thing was that whilst on CM nightlies it would connect with no problem. Im also on my second HTC One and neither connect.
[One (M7) Q&A, Help & Troubleshooting] godfirst:
Have you tried restarting the router. I have the same router and don't have that issue. Only issue I run into from time to time is, I'll be connected, but no Internet connection. Turn wifi on and off on the phone fixes it.
[One (M7) Q&A, Help & Troubleshooting] sparklyflea:
I have the Asus RT66 (not AC version) and connect fine with stock HTC One on the 5mhz band. I did have to uniquely name the 5mhz band or it would connect 2.4.
[One (M7) Q&A, Help & Troubleshooting] jalati:
new firmware for router came out a few days ago and fixed problem! i believe the version is .30 from .24
[One (M7) Q&A, Help & Troubleshooting] fmedrano1977:
Yeah, I have that same router and also experience connection issues. It can be connected to the Internet then I lose connection. Switching to the other band fixes it, then that one does the same.

Sent from my Nexus 7
[One (M7) Q&A, Help & Troubleshooting] the show stopper:
Try enabling support for wifi N connection with a hack or something since it could be disabled by the carrier. Viper One rom has that option. You could also try going to wifi---> settings-----> advanced and turn on best wi-fi performance and changing wi-fi frequency band to auto.
[AT&T HTC One (M7)] droidiac13:
I unlocked my bootloader last night ave everything went well. However, now that I'm unlocked, adb doesn't recognize my phone unless I go into fastboot. To answer the obvious, yes debugging is checked, the drivers are installed and the usb ports are good. Anyone have this issue?
[AT&T HTC One (M7)] gunnyman:
Got either another computer or other Android device you can test on? There's nothing about unlock that should change the ability for adb to work.
[AT&T HTC One (M7)] droidiac13:
I hear ya. Not sure what happened. Tried it on two computers now and it doesn't recognize my device unless I'm in fastboot. Thanks Gunny!
[AT&T HTC One (M7)] gunnyman:
that's some weird stuff man

I assume your dev edition works fine?
[AT&T HTC One (M7)] droidiac13:
I'll tell you in a few once I open charge it up. It was just replaced today.
[Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting] karven:
Hi,

I hope, i didnt posted on the wrong place, but my problem is the next:

have a Archos 80 G9 250GB, and when i turn on the tablet appears a white screen but doesnt appear Archos logo,

tried come up with recovery mode, but happens the same white screen (white screen = have a bright white light from screen),

connected to computer recognizes hard drive but doesnt let me access him, since im losing options, im not sure if is possible to fix

via adb on computer and maybe repair it.

Thank you.

EDIT: Ok, afterwards it was the cable from volum buttons that was disconnected and tablet works but still have a white screen on tablet despite that over hdmi is working and touch screen too the screen on tablet just show a bright white color. If someone can know a possible fix for this please post.
[MDA, XDA, 1010 General] ramram:
This device is for my friend look what happened to it cracked screen and cover : :evil:
[MDA, XDA, 1010 General] ramram:
:cry:
[MDA, XDA, 1010 General] ramram:
Haven't I mention this device is 4 days old......Sad but true!!!!!!!!
[MDA, XDA, 1010 General] aceangel:
Ouch what happened exactly?
[MDA, XDA, 1010 General] ramram:
Simply went straight to the floor..it was horrible I saw it and couldn't do anything about it.