yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] saldebot:
This is how I rooted and flashed a Custom ROM to my S4

1. Go here and downloaded Original MDL firmware

2. Downloaded Wicked Rom and placed on SD Card

3. Placed S4 in Download Mode (vol up + Power ) and flashed official firmware via Odin 3.07

4. Let phone boot up and let sit for 2 minutes or so then powered off and entered download mode once again

5. I then opened Odin and unchecked auto reboot option and used openrecovery-twrp-2.5.0.2-jfltetmo.tar once Odin finished I unplugged it from the computer pulled battery and then manually entered into recovery (vol down + power).

6. In TWRP I did factory reset, then flashed Wicked Rom and rebooted. Now I was on ofiicial MDL firmware and MDL Baseband/Radio.

Almost all custom rom's already have root included in them.
[T-Mobile Samsung Galaxy S 4] Misterjunky:
re: rooting

If that's all there is to rooting the Official S4 MDL firmware then why do all those rooting instruction threads here tell everyone

that they need to download stuff like motochopper, SuperSU, MDB-SetUIDOff and CF-Root and I already forgot what else?

If all we need to do is copy a custom rom to sdcard, put the phone in download mode, open odin and uncheck auto-reboot,

flash stock official MDL firmware then remove the battery & put it back in the phone boot into download mode again and

Odin flash the "openrecovery-twrp-2.5.0.2-jfltetmo.tar " then reboot into twrp recovery and do a factory reset in twrp and

flash the custom rom on our sdcard in twrp.

If this method roots the phone properly then why don't we see these instructions instead all the other ones in these threads?

Your way seems to be a lot easier & straight forward, the same thing can be done in cwm recovery if we d/l the TAR version of it.

I wish I would have known this a long time ago, even with the good old Infuse, Captivate and the S3 phones which I had.

If your method of rooting works on the S4 I am almost sure that it would have also worked on these other phones I had too.

One of these days I am going to give your method a try because I never seen a post here in xda with this rooting method.

Thanks for the information.....
[T-Mobile Samsung Galaxy S 4] saldebot:
That is what I did. After reading all the problems with wifi after doing the method they recomend to remove that pesky file.

So I thought to myself:

I can odin recovery and then reboot right into it....

Wicked has deviant kernel included in it so I do not have to worry about the kernel giving me that problem.

Wicked has root baked in.

So I did it and have had 0 problems with wifi or any pesky message showing up.
[T-Mobile Samsung Galaxy S 4] Misterjunky:
re: wicked v3 kernel

I never did have wifi or any other issues after flashing wicked v3 and I always turn the wifi calliing on because I am usually at home.

The question I have now is let's say someone does not want to flash the wicked rom but instead wants to flash a custom rom

with stock kernel, then what happens? Would that file called "MDB-SetUIDOff" need to be cwm/twrp flashed?

If it needs to be flashed does that means that your method only works with most custom kernels I guess?
[T-Mobile Samsung Galaxy S 4] saldebot:
I would have to say yes, you would have to flash MDB-SetUIDOff. That is if you want the stock kernel, because in the stock kernel is where the problem is...
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
Just throwing this out there: my phone came with MDB, from which I rooted with motochopper, and used odin to flash TWRP... I've been using WickedV2 (which I THINK was MDL) with 100% root access and absolutely no problems. The only reason, ONLY reason I didn't use V3 was because Skype would force-close every time I tried to open it. Even using V3 which is definitely MDL I still had root access. Custom ROMs have all worked, and I've flashed quite a few of them from here and the 9505 section.

One thing though; under Settings->more->about->baseband still showed the MDB baseband and not MDL.

On that note, I decided to download the original Odin-flashable .tar and "upgrade" to MDL through Odin; my baseband still showed up as being MDB. Even after flashing the MDL fw/baseband/modem, it would still show up as MDB in both Kies and About phone. After a few flashes of the stock .tar, I finally got my baseband to show as MDL, cf-auto-rooted, and re-flashed TWRP and I'm back up and running same as before. Only difference I see is my baseband version.

Also, I'm pretty sure the stock MDL kernel wouldn't work with anything outside the stock(ish) TW ROMs out there. Things like Avatar, PAC, Slim, Omega, CM, etc would use their own kernel versions. From my understanding, root access is dependent on an exploit (or built into) whatever kernel/ROM you are currently running; not whether you were rooted before you installed the custom recovery.
[T-Mobile Samsung Galaxy S 4] saldebot:
Which means you are not completely on MDL. You have the firmware but not the baseband/radio.
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
I re-read that and decided to clarify. Edited the original.
[T-Mobile Samsung Galaxy S 4] Misterjunky:
re: skype

That's strange, I have Wicked v3 in my phone now and I use skype all the time and it works just fine.

It worked fine in Wicked v2 as well, I even tested video calling with it and it was excellent.

The first thing I did when I got my phone was upgrade the firmware to the MDL by downloading the full odin

flash firmware and then I rooted my phone and made a nandroid backup.

Then I flashed Wicked v2 and that worked perfectly and when wicked v3 came out I flashed that without any issues.

Each time I flash any rom, even if it's an update I always do full wipe which includes factory reset, I think that's why

I have not been having any problems or issues at all with any apps or wifi and data and no fc's.

My baseband shows MDL.
[T-Mobile Samsung Galaxy S 4] lordcheeto03:
I guess I was a bit winded in my response; the main idea I tried to put across was that I never updated to MDL and retained root on each ROM I flashed; both MDL and custom. Pretty sure that instead of using Odin to flash stock MDL I could have just flashed the modem/baseband and everything would have been just fine. I was able to fix the FC issue as well... it wasn't anything to do with me starting from MDB, it was just me being hard-headed because I didn't see the difference between TiBu's app only update.zip being flashed through recovery and using the batch restore feature and making sure to select app only.
[T-Mobile Samsung Galaxy S 4] JawjaBill:
Got a roadblock at this point. While booting phone would update to approx 15% and reboot. :(

Repeated step 3 with same result. :mad:

Searched XDA for any & everything on soft bricks & boot-loops. Went into stock recovery and did a Factory Reset which had the phone quivering at the pink & white block boot screen.

Went back into stock recovery, wiped caches, rebooted and SUCCESS! On to Step 4. :D

The fear was just about to set in.

Forgot to pull the battery. Didn't seem to matter but backed out of recovery and did it anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmpntl:
Can I port over the Samsung Camera & Gallery to a CM10.1 ROM? I hear there may be framework issues, etc...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d3athsd00r:
Can't happen. Requires the touchwiz framework.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmpntl:
That's unfortunate, as the HDR Function on Cm10.1 is not good--you basically need a tripod to get it to not be blurry.
[Verizon Samsung Galaxy Note II] webb7735:
My car charger doesn't charge my note 2 although it acts like it charging. How can I fix this issue.
[Verizon Samsung Galaxy Note II] BoostedB18C:
Car chargers work much slower than a wall charger because of the output of it. If you have the screen on, using gps, and listening to music at the same time it won't charge or it will actually drain.
[Verizon Samsung Galaxy Note II] SuperDuperPuddin:
charging problems

pp

Probably, the car charger is putting out just enough amps to activate charging mode, but not enough to charge with any discernable speed

I would look for a more reputable charger brand. I have found that cheapie chargers just don't perform well. Especially with the 2 amp requirement our devices need. A 1 amp verizon mobile charger with the micro usb factory attached and ment realistically for my wife's s3 1 amp requirement is adequate to provide a stable but long charge time for my note 2. Remember, some power distribution is lost simply in the usb connection between a cheap 1 amp charger and the usb cable plugged into it. Another useful addition for mobile charging would be an ac/dc inverter that allows your factory home 2 amp charger to plug into your vehicle. That would be reasonably clean 110 v ac to dc at 2 amp from your genuine samsung home charger. Better chance of getting the charging capacity you require. Also, don't forget to chech your usb cable. It may look fine, but could be stretched or damaged causing a bad charge connection. But definitely avoid cheap car chargers. Not only can they work sporadically, they may actually damage your phone.
[Verizon Samsung Galaxy Note II] webb7735:
MUOTE=BoostedB18C;42146532]Car chargers work much slower than a wall charger because of the output of it. If you have the screen on, using gps, and listening to music at the same time it won't charge or it will actually drain.[/QUOTE]

I have tried charging my phone with it turned off when its charging in my car i dont use it i just let it charge but it doesnt work. Its ok not a big deal i can charge it at home and get a good day and a half on a full charge. I was just wondering if there was a way to fix it.
[Verizon Samsung Galaxy Note II] webb7735:
Thanks for the info. I will try that.
[Verizon Samsung Galaxy Note II] BoostedB18C:
This, I just didn't feel like explaining it all. Also using an inverter can cause problems with strain on the electrical load of the vehicle though. If you have a big truck, they are safe to use. If you have a civic, I wouldn't use one.
[Verizon Samsung Galaxy Note II] SuperDuperPuddin:
charging problems

You are most welcome.
[Verizon Samsung Galaxy Note II] shangrila500:
I used one all the time when I had my Civic Si to power mine and a friends laptops when in town, we didn't have high speed at our houses and the provider wanted 50k to bring it, and I never experienced any issues with electrical strain. Im not saying it doesn't happen but with the newer vehicles it isn't that much of an issue.
[Verizon Samsung Galaxy Note II] webb7735:
Thanks for the info.
[Galaxy S II Q&A, Help & Troubleshooting] tempdroid:
I've currently installed NeatRom 4.7 Lite. Everything is fine except for the video mode of the standard camera app.

Camera mode is ok as well, but when switching to video mode, the zoom factor seems to change, everything is bigger and I'm unable to record a good video without moving backwards.

Please have a look at the attached screenshots.

Anyone else with this problem?

Anyone with a solution to this?

Thank you.
[Galaxy S II Q&A, Help & Troubleshooting] king_below_my_lord:
It's not a problem it happens because of the changes in resolution, in photo mode 8 megapixel capture is at resolution 3264x2448, and max resolution for video recording is 1920x1080.

Edit :If you don't want to step back you can reduce video recording resolution to like 640x480, but the recorded videos will not be good for watching in a big screen.
[Galaxy S II Q&A, Help & Troubleshooting] tempdroid:
Jelly Bean problem?

I was using CheckRom v6 before (Android 2.3.6) and never mentioned anything like this, screen detail was the same in camera and video mode.

Has this something to do with Jelly Bean or only with NeatRom?

Do you know any alternative video recording app?
[Galaxy S II Q&A, Help & Troubleshooting] king_below_my_lord:
Well in max resolution(full HD recording) any kind of zooming is not allowed but in lower resolution zooming is there, and I don't remember about gb, but this is common in all my Jellybean device's.

Edit ;So what I mean is since zooming is fixed it's kinda at max zoom, and I am using NeatRom with this device and other jb versions on other devices.
[Galaxy S II Q&A, Help & Troubleshooting] tempdroid:
Zoom Min Max

That was my point.

Zoom factor seems to be at max level, whereas it was at min level on GB.

But good to know, that this not a NeatRom failure.

Do you know of an alternative video recording app?
[Galaxy S II Q&A, Help & Troubleshooting] Paul Blake:
This is a trick used by samsung because we can record on 30fps it crops the image for achiving target fps u cant do anything ..... hardware limitation:mad:

Send from my SGS2 I9100 with HassanROM and latest DorimanX 8.xx kernel
[Galaxy S II Q&A, Help & Troubleshooting] king_below_my_lord:
I don't know any good ones that record video at full HD, I myself use Camera Zoom FX for multiple camera features, and for video recording they use the stock recorder, and as far as I know the stock video recorder app is referred to as the best, for your problem if you are willing to sacrifice full HD, reducing the resolution to the one just below(1280x720) is also pretty neat since we can play with zooming levels to our desire, I myself find it more comfortable to use.
[Galaxy S II Q&A, Help & Troubleshooting] tempdroid:
Answered...

:good:

Thank you for your answers. Maybe the resolution was set to 1280x720 on CheckROM v6 / Android 2.3.6, so I didn't notice such a difference.

Switched to 1280x720 and now it is ok.

I use Camera Zoom FX for a long time and agree, that it is the best photo solution.
[Micromax A110] samthechamp:
Hi everyone,

I was flashing suvi v9 through cwm and it was unsuccessful because of installation aborted status 7..when I rebooted my phone ,,it is showing invalid imei... However in factory mode ,it is showing imei...has anyone faced this prob?.. I have tried generating new mpob_001,zopo imei tool,mt6516.apk method ...plz help
[Micromax A110] devmgs:
Root your phone then use termunal emulator and give these command.

su

echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1

echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
[Nexus 4 Themes and Apps] raul.k:
Any app by which I can get the list of last used app and the time they were used on my nexus... ?
[Nexus 4 Themes and Apps] Mubz_C:
Try This it is more of a widget than an app though: https://play.google.com/store/apps/details?id=com.w8ds.recentapps&feature=search_result
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RawBrokerage:
I have the strangest feeling this has already been answered somewhere...but i've scoured the internet and havent found much of anything on the topic. I've read some mixed statements saying ppls sgs4 see's an external sd card formatted as exFAT, others say it isnt working for them. I've figured out a way to get the hardfloat Kali Linux ARM gui terminal working and all applications installed running in a chrooted environment...however the image size needs to be a minimum of 6gb to install all programs. I'd like to go with 8gb just to give it a little play. I have an SGH-I337 (AT&T) and am rooted, i've tried stock rom w/ stock kernel, stock rom w/ KTweaker kernel, said it supports exFAT but did not work. Also i've tried Cyanogenmod 10.1, but havent tried the KTweaker kernel w/ cyanogenmod yet. After formatting the 16gb microsd i have to exFAT and inserting it into the phone it states "Preparing SD Card"...and immediately says "SD Card is safe to remove". Anybody have any insight as to how i can get around this 4gb filesize limitation? Any input will be greatly appreciated. Thank you.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WoodburyMan:
Here's the deal.

All cards 32gb or less (SDHC cards) come formatted in Fat32.(Part of SDHC spec) This includes a file limit of 4gb max for a single file.

All cards 64gb or more (SDXC cards which the S4 supports) come preformatted in exFat (Part of SDXC spec). This does not have a 4gb file limitation.

The stock Samsung / AT&T Firmware supports exFat. (I bought a 64gb SDXD formatted with exFat and plugged it in and worked right away). Most recoveries do to. (TWRP does at least).

However, I flashed CM10.1 onto my S4. CM10.1 does _NOT_ support exFat. Initially I backed up and reformatted my card in Fat32. Angry with the 4gb file limitation (I have many 720p and 1080p movies over 4gb..) I actually took the microSD card out, used a adapter and hooked it up to a Linux system (Ubuntu 13.04 in my case) and used gParted to format the card to EXT4 filesystem. EXT4 is a filesystem most Linux machines use and support natively. This is actually the filesystem most newer Android device use for their internal SDCard / Data partitions! I popped the card back in, CM10.1 reads it perfectly! And I was able to copy files over 4gb to the device!

So its not a hardware thing since the S4 is SDXC compatible. Just formatting / partition time issue.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RawBrokerage:
I greatly appreciate the breakdown! :) However i do have a question, since the sgs4 supports exFAT, why does it not see it after i reformat my 16gb to exFAT? Is it because it is an SDHC and not an SDXC? Also, does the type of recovery you have installed alter what filesystem types are recognized?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WoodburyMan:
No problem!

As far as the spec goes, if it's formated in exFatand its SDHC it should still read it fine. Filesystem is just a filesystem. The spec just says what is used by default on cards.

One possible issue though, did you format your card in your phone? Sometimes the odd way these work the SD cards like to be formatted in the phones themselves. It worked formatting from a Computer for my ext4 case, however that does not work for all cards/phones/filesystems sometimes.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RawBrokerage:
I've tried formatting from phone, 3 different computers (one computer running Debian), cfdisk command line as well as gparted, also window's format utility. It seems though nothing is working :( however after going to Cyanogenmod 10.1 last night and formatting the external to ext4 the phone only displayed "Reading SD Card" then "SD Card is blank". It works perfectly fine whenever the phone formats it, it just doesnt like any other type of filesystem. It is a polariod sd card which gave me issues in the past. Hopefully i can get this resolved and post more on it. Probably just something small i'm missing :/

Anyways, thanks a million on the input!
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] igotroot:
Can you kindly link me/us to their (TWRP) posts verifying this?

Thanks
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] WoodburyMan:
As far as I know there aren't and posts saying it supports it but I've used TWRP with exFAT, Ext4, and FAT32 formatted ROMS.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] noirelion:
roms not reading 64gb sandisk sdcard

I have the 64gb sandisk ultra class 10 sdcard... and it flat out works in stock... even when I recover. But doesnt work atall using wicked rom and a couple others. ExFat is the reason... those roms dont support it...
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] ThePerson98:
You can use this kernel to get exFAT support on custom ROMs such as Cyanogenmod:

http://xdaforums.com/showthread.php?t=2292341
[Windows Mobile Development and Hacking General] mdodsworth:
I've managed to use the Extended_Rom and Config to restore an XDAII after hard reset.

Problem is that I need to add a registry entry for a control (from the config file)

I used the How to Make the extended ROM visible on your HTC Himalaya .cab

http://www.ppcw.net/?itemid=1638

can anyone explain how i would do something similar (simply?)

thanks
[Oppo Find 5] phonetechkid:
Hi I am new to Oppo find 5 and I was wondering what is the difference between x907 and x909 models. Also how do you check which one you have.
[Oppo Find 5] paperWastage:
x907 is the first phone released by Oppo a year ago(Oppo Finder) 4.3" screen http://www.gsmarena.com/oppo_find-5171.php (it's supposed to be "Finder" not "Find")

x909 is the latest phone (Oppo Find 5) with the 5" 1080p screen http://www.gsmarena.com/oppo_find_5-5161.php

some of the threads here talk about x907, because the mods moved it here....
[AT&T Samsung Galaxy S II SGH-I777] mmoroz:
Phone: Samsung SGH-I777, Android version 2.3.6, Baseband I777UCKK6, Kernel version 2.6.35.7, Build GINGERBREAD.UCKK6). As far as I remember, it's still the stock phone as I received it from AT&T.

I want to root it, get rid of the AT&T customizations, and upgrade it to a newer Android version. I am confused about the order in which I should do these things. Should I first upgrade OS, then root, then apply custom ROM, or should the order be different?

Thank you!

P.S. I am yet to do my research about the custom ROMs; but if anyone wants to recommend which Android version to upgrade to and/or which custom ROM to use, let me know! My main goals are to improve the GPS signal acquisition time, and maintain the overall phone stability.
[AT&T Samsung Galaxy S II SGH-I777] Butchr:
Before you upgrade anything run ExynosAbuse. It is by far the easiest way to root. Just be careful and read everything before you do anything. Do not patch the exploit only root. After you run the exploit follow the guides in the stickies to flash a kernel with CWM, and flash the ROM of your choosing.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Butchr's suggestion is exactly right if you want a custom rom like for instance SHOstock3.

If you would like to remain stock on the latest version but rooted, then flash UCLL6 stock plus root from the link in my signature. This is the latest official stock ICS 4.0.4, with root which will allow you to remove the AT&T bloat.
[AT&T Samsung Galaxy S II SGH-I777] votinh:
I would recommend you reading the very first link under creepy's signature.
[AT&T Samsung Galaxy S II SGH-I777] Eternalty:
Android 1.5 cupcake for sure...!

Sent from my CLEAN Note ll
[AT&T Samsung Galaxy S II SGH-I777] mmoroz:
Hmm I installed (using APK Installer) and ran Exynos Abuse 1.40. It said: "ERROR: It seems your device or firmware is not exploitable at all (hurrah!), this app can't do anything useful for you"

I double checked my phone, and all the specs I provided earlier are still the same. What am I doing wrong?
[AT&T Samsung Galaxy S II SGH-I777] Butchr:
Not sure. I used the exploit myself. The only difference I see between your phone and mind is that when I ran the exploit I was on 4.0.3. Very strange. If that isn't working for you I have seen quite a few people having success with the frameroot method though I have seen some saying that it was only a temporary root.
[AT&T Samsung Galaxy S II SGH-I777] mmoroz:
Do you think I can try approach 3) (with Odin3) on this page?

Edit: it worked perfectly, except now wifi doesn't work (I turn it on, it tries to connect, in a few seconds finds no networks, and turns itself off). I assume it will get fixed later in the process. I now have Android version: 2.3.4, Baseband: I777UCKH7, Kernel 2.6.35.7, Build GINGERBREAD.UCKH7.
[AT&T Samsung Galaxy S II SGH-I777] Butchr:
I believe you can get it sorted out as you continue. You seem to be doing a pretty good job of sorting out your issues. You can't go wrong following the links in Creepy's sig as long as you reed and comprehend what the instructions are telling you to do. You seem to have a pretty good grasp on things at this point. I believe you will sort your WiFi issue as you flash a kernel and then flash your rom. Happy flashing.
[AT&T Samsung Galaxy S II SGH-I777] creepyncrawly:
Flashing from 2.3.6 back to 2.3.4 always caused the wifi to fail. The fix is to perform a wipe data/factory reset in recovery. In fact, as you move forward you should know that anytime you change base, you need to perform a wipe data/factory reset, preferably before the flash.