yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] oakley470:
Does anyone know if ti possible to unroot and remove the custom firmware notification if we need to on the developer device? I want to root but want to make sure i can get it back just in case. I assume follow the same steps as for the standard s4 but i am not sure if a stock firmware is currently available for the developer device?
[Verizon Samsung Galaxy S 4] :
Yes man, my droid 1 is still rocking eclair because I refuse to run any ota.
[Verizon Samsung Galaxy S 4] wtherrell:
Just applies to current GS4 situation concerning keeping root & custom recoveries. Sorry about your Droid 1 situation but that is why with this phone, once we have custom recovery & can rom it, most of us wish to keep it that way. :)?

Perhaps I was a bit harsh. Sorry.

Hope we can still be friends
[Verizon Samsung Galaxy S 4] Stevez48:
Got my Developer edition phone yesterday. Still a little unclear on what to do to root, I guess I will try Moto Chopper, and then install custom recovery via goo manager or can it be done via Odin?

Also, about making an image file of stock. How do I go about doing that so I can get it back to the way it was when I got it, just in case it needs to go back or anything... I would be happy to share it once I figure out how to do it.

Thanks.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Motochopper didn't work for me. Read through this thread: http://xdaforums.com/showthread.php?t=2346979

It gives a better way to root, I think. Wish I had seen it before I did mine an overwrote the stock dev kernel, LOL!

Someone else will have to help with the stock img file stuff.
[Verizon Samsung Galaxy S 4] wtherrell:
OK, I feel lice a dunce right now. I can't get a download of Odin. Links on the site don't seem to work or I get spammed with pop-ups wanting to add all kinds of other "free" stuff & can never get to what I want. Searching for Odin in the search box on the forum stays gray for several minutes then comes up empty. Tried SourceForge but the latest I could find there was 1.87. I am clueless atm, and out of time for the day.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Try this link: http://www.andromint.com/download-odin-latest-version/

The scroll to the bottom and look for Download 1 / Download 2. It's version 3.07.
[Verizon Samsung Galaxy S 4] locofocos:
This worked fine for me. Using 3.07 in this package- http://xdaforums.com/showthread.php?t=2189539
[Verizon Samsung Galaxy S 4] feffrey:
dang it the code isn't working any more :(
[Verizon Samsung Galaxy S 4] wtherrell:
Kaiya_FL, locosfocos and others, thanks guys. Once I got the 3.07 Odin, installing philzTouch CWR was a breeze. Then used that to flash Chainfire's SuperSU and , voilà, root! Made a nandroid backup but could not get it to go onto ext SD card. Probably just an overlooked setting somewhere.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Awesome! :good:

I had to use the phone to reformat mine before I could save my nandroid backup to it. You may want to try that and see if it works.
[Verizon Samsung Galaxy S 4] HowardZ:
I don't own a developer edition s4, but I have experience with a HTC Rezound with factory unlocked bootloader.

On the pc, use adb and fastboot commands.

If the bootloader isn't unlocked, type

Fastboot oem unlock

Get the recovery as a img file for our s4, and then

Fastboot flash recovery filename.img

If you don't want to install the recovery, just to use it one time,

Fastboot boot filename.img

So, these commands are from my memory, so it wouldn't hurt to look them up.

Then for rooting, download the latest supersu.zip file onto the SDcard and flash it using the custom recovery.

Regards

Howard

Edit: Silly Me!!! I can't seem to get the S4 phone into FASTBOOT mode. Looks like we can not use Fastboot commands with the S4?
[Verizon Samsung Galaxy S 4] tithefug:
Nope. They use "Download" mode. So, you must use ODIN to flash anything. That was my first try was attempt. Didn't work.
[Verizon Samsung Galaxy S 4] Kaiya_FL:
And that then explains why I could see the device with the 'adb devices' command but not with 'fastboot devices'. Guess it's time to get friendly with ODIN :cool:
[Verizon Samsung Galaxy S 4] Firemedic:
Got Samsung to honor the discount!!

Hello All,

I was waiting until I got my Developers edition in hand before I posted this. I like the others used the Discount code that Samsung had provided to get 25% off of the GS4 developer. Like everyone else my order was cancelled before it was shipped. Feeling this was not quite legal since the coupon code worked and I was quoted a specific price for the phone I decided to pursue it.

First I talked to the CSR, Bumped it to the supervisor then to the manager at the distribution center. The phone number is on the order. I ran into a roadblock each time. They kept telling me it was a glitch and I kept telling them that is not my problem, I was quoted a price and I expect them to honor it. I then wrote a very long email detailing everything, the quotes, the discount code. How I felt they were wrong and on the border of bait and switch. I also said that if I went into any electronics store and they quoted me a price, They would have to honor it. I also said that I would contact the FTC, BBB, Attorney General and the local consumer reporters. Then I sent the email to every possible email address I could find for Samsung, President, Support, Sales, Their PR firm, Facebook, Twitter etc.

Got a call back from the manager the next day telling that they would honor the discount. Samsung corporate set up a special discount code for me and I was able to order the phone for that price. Just as a note, the distribution center is not actually Samsung it is lectronics.com.

Just got my phone and at an unbelievable price. It also took me very little effort to convince them they were in the wrong.

Go for it..and good luck!
[Verizon Samsung Galaxy S 4] HowardZ:
OK,

I did a little reading, out of curiosity.

First one gets the img file for the custom recovery you want to use.

Then you convert the img file into a Odin flashable file.

See here: xdaforums.com/showthread.php?t=2281287

Then flash the custom recovery using Odin.

Download supersu, boot the custom recovery, flash the supersu zip file using custom recovery.

http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
[Verizon Samsung Galaxy S 4] Kaiya_FL:
That's awesome! I can't even get them to refund the shipping on an order that never even left the warehouse and that THEY cancelled.
[Verizon Samsung Galaxy S 4] NoSauce:
It's a win for the people.

This is great. Good for you. I feel like this is a small win for the people. All these large companies put these highly unnecessary blocks in the customer service and compartmentalize CS from billing, etc on purpose to make people's live's unnecessarily stressful. I have to do some meditation/mind control before I call any CS department to prepare me from the repeated transfers and repeating what happened and explanations, etc. Even still, I feel like clubbing some baby seals afterwards.

I think putting things in writing helped. A lawyer told me that it's harder to ignore if it's on the record, in writing. Do you mind sharing a little more detail as to who you ended up writing and who ended up getting back to you? I need to write ATT for some highly absurd BS. Clearly, I'm looking to switch to Verizon.

Thanks ahead of time.
[Verizon Samsung Galaxy S 4] r4ph:
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.

Steps from my win8 laptop were...

Install samsung drivers,

get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)

dl and push your superuser zip to the sdcard or external sdcard

dl odin 3.07 and extract to pc

dl and make tar.md5 of your favorite recovery. ( i personally like cwm )

Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power

Start odin.exe

uncheck auto-reboot

click pda button, select the recovery file.md5

press start and let it finish, only takes a few secs...

once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.

Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.

reboot your phone and done.

good idea to make a backup while ur in recovery :)

If someone has hosting, i can send the files needed.

-r4ph
[Verizon Samsung Galaxy S 4] tithefug:
Thanks for the reply! I'll add this to the OP.

Also, do you get the "Samsung | Custom" boot logo when you turn the device on?
[Verizon Samsung Galaxy S 4] r4ph:
yep sure do... has a little lock that is unlocked icon.
[Verizon Samsung Galaxy S 4] tithefug:
Okay. Great. That's what I was expecting, but if it didn't, I might have tried to find the original images and go this route.

Thanks again.
[Verizon Samsung Galaxy S 4] r4ph:
Also, one side note...

I had to try a few different superuser apps...

This one finally worked when i flashed it in CWM.

CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu

Filename: UPDATE-SuperSU-v1.51.zip

The others would install, but not allow the binaries to work correctly. Tried a bunch to get the others working from the market etc.. This is the only one that seems to work.

I can now use titanium back-up, and get the su prompt normally.
[Verizon Samsung Galaxy S 4] rmanaka:
Thanks for your information! Some of us are trying to get rooted without modifying the recovery image so that we can get a stock recovery package for the Development Edition phone.

It sounds like you can get full "su" and if you can can you run

dd if=/dev/block/mmcblk0p22 of=/storage/extSdCard/boot.img

in terminal emulator (or ADB ) so that we can get a stock boot.img?

Thanks!
[Verizon Samsung Galaxy S 4] r4ph:
EDIT:

Found that mmcblk0p22 is actually fota, and 20 is boot. Adjusted the file and string below. </Edit>

root@android:/ # dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/boot.img

dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/boot.img

20480+0 records in

20480+0 records out

10485760 bytes transferred in 0.500 secs (20971520 bytes/sec)

file attached.
[Verizon Samsung Galaxy S 4] stang5litre:
What is the best method to get full root?

Hello sorry if this is in the wrong spot I have been looking through the threads to try and find the right thread. Please don't smack me :( . What currently is the best method to get full root? The one click method? or Going through the whole process. My phone will be here in like 2 hours so just want to make sure I do it right. I will post what build it is also as I know the me7 build can't be unlocked fully. It should come with MDK. Thanks for any and all help in advance. Have experience in rooting but it was with HTC's. :o
[Verizon Samsung Galaxy S 4] tithefug:
No smacking needed. A little while ago, I had updated the OP with a link to a post in this thread. That should be all you need to acquire root, as well as a custom recovery.

Good luck!
[Verizon Samsung Galaxy S 4] asharad:
This thread is for the Developer Edition. Is that the phone you purchased?
[Verizon Samsung Galaxy S 4] stang5litre:
Smacking may be needed not dev edition

Hey thanks for your quick responses no I have the reg 16gb white frost edition. For some reason I have a hard time finding the right thread in XDA thats why i was saying sorry from the start. :( embarrassed..... I downloaded the one click method. But not sure which route to take as this is my first Samsung dealing with Odin. Used to HTC rooting. I know pretty much the same process with out Odin. Just don't want to brick my phone so I wanted to ask questions and get the right method. Thanks in advance
[Verizon Samsung Galaxy S 4] sparky697:
I think it's gonna depend on what carrier and build number your phone is on. MDK can be unlocked and ME7 cannot.

Look in "about phone" for build. That's for verizon anyway.
[Verizon Samsung Galaxy S 4] asharad:
Hey, no problem. I just don't want you to follow directions for the Dev Edition on your device. It's a sure way to cause problems.
[Verizon Samsung Galaxy S 4] Bait-Fish:
CAUTION

The memory block #22 you extracted is actually FOTA. If someone dd's it back to mmcblk0p22, no harm. BUT, if someone downloads it and pushes it to the actual location, 20, that's bad news. I suggest you rename the file to FOTA or pull it altogether.

Honest mistake. I did something similar going from information posted in the Need Help of Someone with Dev Edition S4 thread. I pulled the files, not wanting the possibility to brick someone.

The actual locations are here and SamuriHL posted a more foolproof method here.

Edit: Links added
[Verizon Samsung Galaxy S 4] r4ph:
you're right... did an ls -la in that dir... and it shows this:

root@android:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 1970-01-08 10:02 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-08 10:02 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-08 10:02 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-08 10:02 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-08 10:02 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-08 10:02 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-08 10:02 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-08 10:02 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-08 10:02 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-08 10:02 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-08 10:02 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-08 10:02 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-08 10:02 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-08 10:02 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-08 10:02 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-08 10:02 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-08 10:02 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-08 10:02 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-08 10:02 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-08 10:02 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-08 10:02 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-08 10:02 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-08 10:02 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-08 10:02 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-08 10:02 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-08 10:02 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-08 10:02 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-08 10:02 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-08 10:02 userdata -> /dev/block/mmcblk0p29

Adjusting the file, and attaching it here.
[Verizon Samsung Galaxy S 4] stang5litre:
Baseban+ Build#

Hello thanks for everyone's kind responses. :) I just got the phone and the Baseband is I545VRUAMDK Build# JDQ39.1545VRUAMDK.

I turned it on just to get that and cut it back off with no sim in it. Again thanks for all help in advance and sorry for not finding the right forum. I hope this is fully rootable as I have 2 now my wife does not care about root so took hers. What would be my best method to fully root? The one click tool? or going through the steps?. Again sorry for wrong forum and thanks to everyone here who has answered and helped me. :o (not dev addition) Ref 16gb Frost white
[Verizon Samsung Galaxy S 4] rmanaka:
One click worked fine for me when I rooted a MDK phone before I got the Development Edition. Did wife's phone that way as well to freeze the OTA update process.
[Verizon Samsung Galaxy S 4] asharad:
This is where you want to be:

http://xdaforums.com/showthread.php?t=2290798&highlight=search+this+forum
[Verizon Samsung Galaxy S 4] stang5litre:
Thanks!!

Thanks will try that. I can do either method and feel comfortable but if I can use the tool .. y not makes it faster. Thanks for pointing me in the right direction. :)

---------- Post added at 03:17 PM ---------- Previous post was at 03:12 PM ----------

Thanks for your guidance in finding one of the right threads. :) Just didn't get anyone to answer on that side. And was just wondering if there was a preferred method over the other. Thanks again and I won't post in the wrong section hopefully anymore. Used to Infected.com forums way easier to navigate to the right thread and no one gets upset if u ask a question. Santod always helped out great Dev!!
[Verizon Samsung Galaxy S 4] asharad:
Lol, I'm not upset, just trying to help you out. ;)
[Verizon Samsung Galaxy S 4] stang5litre:
Thanks!

I wanted to say thanks for all your help and sorry for wrong posting. I wasn't saying you were upset per say just some people. I got it rooted successfully but I can't get the OTA Push to stop. I see they say to freeze it with titanium backup but I have the free version. Is there a way to get past this like delete those files or rename them? Or do I pretty much have to buy titanium backup?

Again thanks for all your help it has been much appreciated, and won't be forgotten. :)
[Verizon Samsung Galaxy S 4] Kaiya_FL:
If you get a file explorer like Root Explorer, you can rename the sdm.apk to sdm.apk.bak and it should stop it.
[Verizon Samsung Galaxy S 4] stang5litre:
Root Explorer

I actually have that app.... I must be losing my mind. Thanks for all your help as you have been very helpful. I also downloaded rom tool box which can freeze for free. But I am curious where these files are to rename as I would like to do that. Checked under system. No luck finding them (this was on internal memory not sd) , Checked under android and platform as well. Thanks again for taking so much time to really answer my questions each time. :good:
[Verizon Samsung Galaxy S 4] old&slow:
/system/app/
[Verizon Samsung Galaxy S 4] stang5litre:
Very helpful xda member

Your the man. Thanks so much for all your help. You have been so helpful. Worked like a charm. :laugh::good::good: I found them now and renamed them. All is well. Rooted and OTA no longer pushing. Thanks for getting me up to speed.
[Verizon Samsung Galaxy S 4] old&slow:
No problem...glad to help :)
[Verizon Samsung Galaxy S 4] Kaiya_FL:
Glad you got the info you needed :good: Darn work got in the way and I couldn't reply :laugh:
[Verizon Samsung Galaxy S 4] benjis226:
can you send me the needee files please im running win 7

Hi are you able to send me the files please if its easier my email address is benji.shakespeare1990@gmail.com and also does it unlock your phone? Ive got the uk s4 version mate
[Verizon Samsung Galaxy S 4] sparky697:
This thread is for the Verizon Developer Edition. I'm not sure what version you have but if you're in the UK I'm guessing it's not the same one. Maybe the international version?
[Verizon Samsung Galaxy S 4] lortay78:
So I have read through this thread, and I think I'm ready to roll when my developer edition shows up. Sounds to me like I just follow the steps in the amended OP and use Caboomi's recovery img2tar odin-maker to make my custom recovery file into what I need. But I do have a question. So, given that the original build required loki recovery, and now we have this safestrap method for the ME7 build, I'm wondering which version of TWRP I should use. I don't see why I should need loki with this phone. I'm guessing I will try the most recent version, as I think I could continue to try others if it doesn't work. I don't mind CWM either.

I don't know if my dev edition will have updated software from what came on the ones you guys got, but I don't see why it would matter. Just wondering what you all are using for recoveries mostly. Thanks. I'm excited to get a developer edition phone. I'm guessing that is all I will buy going forward unless hell freezes over and Verizon gets another Nexus.
[Verizon Samsung Galaxy S 4] playaprez35:
Working Recoveries???

I was wondering if anyone knew of a functioning custom recovery, that allows you to flash Roms??? I have a VZW S4 Developer Edition, but I can't flash custom roms. I just bought it about a month ago, and it came with the MJ7 software version. I was able to flash SuperSU, but being stock rooted is kind of useless to me. Mainly because I hate all the bloat that slows the phone down, plus I'm a little limited when it comes to functionality. So until I am able to flash a rom, I'm stuck using my S3. Which leaves me with an expensive paper weight...

Please Help!!!
[Verizon Samsung Galaxy S 4] Mistertac:
I've seen guys with dev s4's throw the non Loki version of say...philz recovery on there phones using Odin u believe with no problem... As far as what ROMs you have available I'm not really sure but I've definitely seen threads on here regarding your phone and what options you have.

You should really be using it lol no reason it should be sitting around like that.

Check this thread out and see what they have to say...if you haven't already

http://xdaforums.com/showthread.php?t=2346979
[Verizon Samsung Galaxy S 4] jpcalhoun:
I have a Dev S4 also. I've used PHilz custom recoveries when I first got the phone but had some problems with that recovery and certain ROMS. I suggest you use TWRP 2.5.0.2. That recovery seems to be the "gold standard" for the S4. New versions may work, but i've never heard of anyone having an issue with 2.5.0.2. You can find a .tar or a zip version. I flashed the zip version in PHilz recovery and it replaced Philz with TWRP without issue. Go here for the zip version: :http://d-h.st/gLS
[Verizon Samsung Galaxy S 4] playaprez35:
Thank you both for the info. I truly appreciate it, and I'll let you know how it goes.

@

Mistertac

don't laugh at me lol. I'm smart/capable, but I'm still kind of a noob when it comes to all of this. I'm also very particular for some reason, but thanks again!
[Verizon Samsung Galaxy S 4] Mistertac:
Oh hey I wasn't laughing at you promise. We've all been there. There's a lot of information to digest here on XDA. You're in the right place and I'm happy to answer any questions I can. Theres people on here that know far more than I do.

Good luck!!!
[Verizon Samsung Galaxy S 4] playaprez35:
Hey, It's all good, I was just kidding. I'm just hoping that I'm in one of those situations where: I missed something so simple that, I'll tap myself on the head once I figure it out. Besides sometimes it's good to be able to laugh at yourself. Plus I know that if there is anyone who can help me, it's going to be here.

So far I'm not having any luck, but I gave up that "I can do it all, on my own" attitude a long time ago. I like being surrounded by intelligent minds, it helps make me smarter.... Vice Versa. Anyway thanks for pointing me in the right direction, I appreciate your time.
[Verizon Samsung Galaxy S 4] cawaller:
I'm not new to rooting and flashing on other phones. I have done Motorola OG, and Droid Max, then HTC's Rezound and Incredible. But have never done anything with a Samsung product. So I'm a complete newbie to Samsung and don't know the terminology. I have downloaded and extracted Odin. I have ADB setup. I don't know what is meant by "dl and push your superuser zip to the sdcard" or how. Same with "dl and make tar.md5 of your favorite recovery". Does anyone have a site that explains the "how to" for these? Or a "how to root Samsung for dummies" site?
[Verizon Samsung Galaxy S 4] Mistertac:
Do you have a Dev Edition S4?,

Sent from my SCH-I545 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S 4] cawaller:
Yes. I have the Verizon S4 Developer Edition
[Verizon Samsung Galaxy S 4] Mistertac:
My fault. I'll let one of these Dev S4 guys lead the way then. I'm on an MDK S4. Sorry to waste space here lol

Sent from my SCH-I545 using Xparent Blue Tapatalk 2
[Verizon Samsung Galaxy S 4] wtherrell:
http://xdaforums.com/showthread.php?t=2346979

Have you read through that thread?

All I did on my Dev edition was to download a recovery to my PC and push it to my phone using Odin. Then downloaded Chainfire's SuperSU +root to my phone and flashed that using the recovery. Just make sure you get the right version of the recovery for your phone and carrier.