Hi! I'm using an AOSP rom in my I337m. I want to use the Kit Kat 4.4.2 picture whrn my phone starts instead of the Samsung Galaxy S4 that is the default. Any Help?
Sorry I can't be of help here but be VERY CAREFUL with it. I tried to change that splash screen on my less than week old S4 back when it first came out. I hard bricked it and had to send it for JTAG at MobileTechVideos. I really liked making them on my ATT S3 and thought I had it figured out when I first got my S4. Flashed it and was bricked.
It wasn't a FULL hard brick as I was able to get into download mode but not recovery. BUT even though I was able to get into download mode and flash the stock .md5 files back then it would NOT do anything other than the blue led light up and the phone vibrate constantly. It would never get past that point.
So point is I haven't tried it a second time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
on the S4 that image is built into the bootloader. so no. it cannot be changed
TRusselo said:
on the S4 that image is built into the bootloader. so no. it cannot be changed
Click to expand...
Click to collapse
True, but 1337m's (Canadian s4) are not bootloader locked like their American counterparts
Sent from my GT-I9505 using Tapatalk
[Facepalm]
locked/unlocked bootloaders has nothing to do with being able to modify the bootloader itself.
I have a 337m. I am canadian. I am a developer. I am a retired moderator.
if it were really that easy they would have modified the 337m bootloader to work on the 337 long time ago,.
My bad
Sent from my GT-I9505 using Tapatalk
That's a bummer, I was hoping it would be a simple dd command.
Sent from my SGH-I337M using XDA Premium 4 mobile app
Related
I have a ATT I337 and a dream, to install a rom that turns my phone into a Pure Google Edition S4 that thinks its true Pure Google Edition S4 (OTA updates straight from the big G and all)
Is this possible? I have been waiting on this dream and holding off installing other ROMs but just realized it could be a pipe dream.
What do you guys think?
Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
http://forum.xda-developers.com/showthread.php?t=2341376
Sent from my SAMSUNG-SGH-I337 using xda premium
Been watching that but it seems to be more of a Rom that acts like the PGE S4?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
You install the Google edition ROM and you will have your dreams come true. Running it right now and its truly glorious.
Sent from my SGH-I337 using xda app-developers app
cwhittl said:
Been watching that but it seems to be more of a Rom that acts like the PGE S4?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
That Rom is ripped right from the Google edition. Has someone who has been using nexus devices for the past two years, I can assure you, it's pretty much stock. About the only thing we might miss out on is ota updates working properly. Might be a few days behind for the devs to adapt them. I don't see it as an issue as Google seems to be slowing down it's updates schedule
Sent from my SGH-I337 using xda app-developers app
Ok .. if I'm reading this right .. I know exactly what cwhittl is asking for in which people are not understanding .. and he is looking for the same thing as I am.
We're NOT looking for a ripped ROM that we have to have a custom recovery on in order to get on our phones. All other Google Edition phones going back to the original Nexus phones and images that are applied to the phone using ADB commands, thus not needing to be rooted, custom recoveries etc.
Now that its been announced that Google will not be holding/creating the images for the HTC One or SGS4 GE .. it will be up to the OEM to create these images .. Samsung has already posted the source code for this phone on there Samsung Open Source website .. but where can we get the build (not rip) image that is currently on the SGS4 GE (img, tar, tgz, md5 etc etc) .. that can be installed either by ADB or ODIN.
All the different versions that are up here either in the AT&T SGS4 thread or the original GT-i9505 thread are working off a ripped version and all have issues (yes, I have been reading most of them) . and I'm sure the actual SGS4 GE does not have all these issues that people are reporting from the rips.
Hence .. the reason for requesting a ORIGINAL build, not rip.
LordGeek said:
Ok .. if I'm reading this right .. I know exactly what cwhittl is asking for in which people are not understanding .. and he is looking for the same thing as I am.
We're NOT looking for a ripped ROM that we have to have a custom recovery on in order to get on our phones. All other Google Edition phones going back to the original Nexus phones and images that are applied to the phone using ADB commands, thus not needing to be rooted, custom recoveries etc.
Now that its been announced that Google will not be holding/creating the images for the HTC One or SGS4 GE .. it will be up to the OEM to create these images .. Samsung has already posted the source code for this phone on there Samsung Open Source website .. but where can we get the build (not rip) image that is currently on the SGS4 GE (img, tar, tgz, md5 etc etc) .. that can be installed either by ADB or ODIN.
All the different versions that are up here either in the AT&T SGS4 thread or the original GT-i9505 thread are working off a ripped version and all have issues (yes, I have been reading most of them) . and I'm sure the actual SGS4 GE does not have all these issues that people are reporting from the rips.
Hence .. the reason for requesting a ORIGINAL build, not rip.
Click to expand...
Click to collapse
So what your saying is that you want the phone to be partitioned exactly as the Google version ? Well sir we have a locked boot loader I337 to turn a device into an entirely different model and be stock is impossible ... you should just buy the model you need .. and the definition of rip here means they took the original build and provided it in a flashable package ..
Even if we had the tar file for the Google edition and pit files we can't flash it because of locked bootlader not to mention it will also erase imei because it would flash a different baseband... and the repartition erases baseband too ...
Sent from my GT-I9505G using xda premium
LordGeek said:
Ok .. if I'm reading this right .. I know exactly what cwhittl is asking for in which people are not understanding .. and he is looking for the same thing as I am.
We're NOT looking for a ripped ROM that we have to have a custom recovery on in order to get on our phones. All other Google Edition phones going back to the original Nexus phones and images that are applied to the phone using ADB commands, thus not needing to be rooted, custom recoveries etc.
Now that its been announced that Google will not be holding/creating the images for the HTC One or SGS4 GE .. it will be up to the OEM to create these images .. Samsung has already posted the source code for this phone on there Samsung Open Source website .. but where can we get the build (not rip) image that is currently on the SGS4 GE (img, tar, tgz, md5 etc etc) .. that can be installed either by ADB or ODIN.
All the different versions that are up here either in the AT&T SGS4 thread or the original GT-i9505 thread are working off a ripped version and all have issues (yes, I have been reading most of them) . and I'm sure the actual SGS4 GE does not have all these issues that people are reporting from the rips.
Hence .. the reason for requesting a ORIGINAL build, not rip.
Click to expand...
Click to collapse
I don't believe we well ever have that. The nexus line uses fastboot to flash the images when the bootloader is unlocked.
The Google edition is not fully open sourced nor will it, Samsung holds key components for some of the drivers as closed source, hence why Samsung will be releasing the updates, Google is just mirroring them and working with them to make the os stock. If you want the true open source experience, get a nexus. The Google edition Rom is the closet thing we will ever get to it on this model of phone.
Has someone who had been using nexus devices for the past few years, I'll give up that little bit of control to get stock on a powerful hardware like the s4. Google edition will hold me over until fall of 2014 when I'll upgrade to that nexus device.
Yes, I miss fastboot, Odin is such a pain in comparison
Edit, I just wanted to add that as of this moment, I'm not experiencing any issues at all. Everything works as intended
sent from my i377m Google edition
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
LTE issues as well as other things
I just flashed the stock google edition rom 4.2.2 on my at&t galaxy s4. I installed the rom, then flashed the kt kernal, and then loki-doki. However when I turn on my device I get only a H instead of LTE. also I was youtubing videos of people who installed this and their about phone screen looks different from mine. Mine still indicates that it is a SGH-i337 while others show gt-i9505G when flashed onto an AT&T s4. Im new to all this stuff please help! ive attached a screen shot of what my screen currently looks like.
I have an Canadian SGH-I337m Galaxy S4. I have installed the TWRP recovery and Google Edition 4.3 rom on it. Today I have received an OTA software update notification for a small 16 Mb update. However, when I tried to install it, phone rebooted in TWRP recovery menu and nothing was installed.
I got very excited about it but i guess it is not possible to install these OTA?
cloud628 said:
I just flashed the stock google edition rom 4.2.2 on my at&t galaxy s4. I installed the rom, then flashed the kt kernal, and then loki-doki. However when I turn on my device I get only a H instead of LTE. also I was youtubing videos of people who installed this and their about phone screen looks different from mine. Mine still indicates that it is a SGH-i337 while others show gt-i9505G when flashed onto an AT&T s4. Im new to all this stuff please help! ive attached a screen shot of what my screen currently looks like.
Click to expand...
Click to collapse
You need to set your APNs correctly.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So I flashed the tmobile wicked rom v4 for samsung galaxy s4 onto my at&t s4 with ktoonsev kt touch wiz kernel 6-23-2013. Everything seems ok but when I hit the power but for the screen to go asleep or what it is, it looks like a tv turning off like on a aosp rom. Is this normal or should this not be like this? And can I get awesome beats equalizer on this stock rom aswell?
Sent from my SGH-M919 using xda app-developers app
KT kernel 6/23 has a few bugs on a couple roms, not naming them either, roll back to the 6/10 version, should fix the problem. been there done that.
Oh yeah, do forget to wipe dalvik, and cache before you flash, but I should have to tell you right? You know that.
Good luck.
Your welcome
brandonsbailey.101392 said:
So I flashed the tmobile wicked rom v4 for samsung galaxy s4 onto my at&t s4 with ktoonsev kt touch wiz kernel 6-23-2013. Everything seems ok but when I hit the power but for the screen to go asleep or what it is, it looks like a tv turning off like on a aosp rom. Is this normal or should this not be like this? And can I get awesome beats equalizer on this stock rom aswell?
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Yes the crt off is normal. It's part of Wicked v4.
Sent from my SGH-M919 using xda premium
are you able to see your EXT flash drive?
I did the same thing as far as loading this rom onto my att 4.2.2 MDB baseband. I loaded KT kernal 8-20-2013. Im still having difficulties getting LTE support. All I get is 4G thats it....I changed the mobile network and still no luck. I did install loki-doki as well. Im very new to this so if anyone could help it would be greatly appreciated. ..thanks guys
never mind got it fixed
Brick or soft brick
i tried running wicked through my gs4 i337nc1 ad now it is in boot loop, battery charging does not seem to be working and i cant get into download mode. Screwed royally or simply screwed am I?............
I rooted my galaxy s4, OTA MF3 updated, I accidently installed Chainfire 3d and tapped 'install CF3D driver', and instantly the device reboots and stuck at at&t logo. i tried latest stock firmware to flash with Odin 3.07, but it says
<NAND write start>
<FAIL(Auth)>
.
also did factory reset but it stuck at the at&t logo every time.
what should i do!!
I sent my device to MobileTechVideos for JTAG brick repair and ROM/root upgrade.
do you think they can fix it with JTAG?
Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store then install the drivers through the app. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Way too coincidental...
http://forum.xda-developers.com/showthread.php?t=2419863
If it's not you, please read that thread so we don't have to keep cluttering the board up with the same stuff over and over again. Any help you will find for your issue has been posted in that thread.
If it is you, I hope you are banned for multiple accounts.
OH NO
graydiggy said:
Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
it can't be fixed ANYWAY? by the way, why do you think the Odin doesn't work? i want to know why my device can't be fixed. explain to me please, why can't it be fixed and what is the problem that make it unable to fix.
You are on MF3. Thee is no custom recovery on MF3. There is no ODIN flashable MF3 ROMs, there is no MF3 on Kies.
If you would read the stickies and most MF3 related threads, you would know that there is no way to come back from messing up on MF3.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Nope i'm not that guy
graydiggy said:
Please tell me this isn't the same guy from a few days ago with a different username.
If not. You did not accidentally install it! You have to click install and accept in the play store then install the drivers through the app. You intentionally installed it but you were too busy NOT reading anything that says that it is only compatible on specific hardware. Now you are screwed and have no way to fix it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you mean the guy who posted same problem few days ago?
Yep... Created multiple threads on it too.. scott14719 posted a link.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
.
graydiggy said:
You are on MF3. Thee is no custom recovery on MF3. There is no ODIN flashable MF3 ROMs, there is no MF3 on Kies.
If you would read the stickies and most MF3 related threads, you would know that there is no way to come back from messing up on MF3.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I installed Clockworkmod recovery and did the factory reset. isn't Clockworkmod recovery a custom recovery? so that means, i have to collect 400 dollars and switch the mainboard at at&t or should i wait until odin flashable MF3 comes out? i just bought galaxy s4 a week ago.
anyway i'll find my way to solve this even if that means i have to switch mainboard. thanks for replying.
If you are truly on MF3,you would not be able to install CWM.
It means that you have a $650 paperweight for the time being until you
A: Get it replaced
B: Get a new motherboard
C: learn ADB and can fix it with that
D: Try a J-Tag repair
E: Wait until the bootloader gets unlocked. If it is even possible.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
If you are truly on MF3,you would not be able to install CWM.
It means that you have a $650 paperweight for the time being until you
A: Get it replaced
B: Get a new motherboard
C: learn ADB and can fix it with that
D: Try a J-Tag repair
E: Wait until the bootloader gets unlocked. If it is even possible.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A: Yep
B: Would be better off getting another phone. I'm not sure if the NV memory is located on the Motherboard or not?
C: ADB might not be able to connect if he can't get the phone booted.
D: So far JTAG is a no-go on MF3.
C: Yep, but hopefully Samsung will release the full MF3 firmware (hopefully through KIES as well) that will be able to reflash the firmware to the phone.
I would say replace it or be screwed until MF3 firmware drops.
Noooooooooooo
scott14719 said:
A: Yep
B: Would be better off getting another phone. I'm not sure if the NV memory is located on the Motherboard or not?
C: ADB might not be able to connect if he can't get the phone booted.
D: So far JTAG is a no-go on MF3.
C: Yep, but hopefully Samsung will release the full MF3 firmware (hopefully through KIES as well) that will be able to reflash the firmware to the phone.
I would say replace it or be screwed until MF3 firmware drops.
Click to expand...
Click to collapse
Why did AT&T updated to MF3!!!!!!!!!! do if MF3 comes out, does that mean i can flash that with Odin?
i should say MF3 stands for Mother+F word times 3. anyway thanks for replying.
I sent my device for JTAG yesterday. they might not fix it
ryujeff said:
Why did AT&T updated to MF3!!!!!!!!!! do if MF3 comes out, does that mean i can flash that with Odin?
i should say MF3 stands for Mother+F word times 3. anyway thanks for replying.
I sent my device for JTAG yesterday. they might not fix it
Click to expand...
Click to collapse
I'm sure AT&T views MF3 as a complete success. It's just the people interested in customizing and modding their phones (XDA minded people) that hate it.
When Samsung releases the full MF3 firmware, you should be able to use ODIN to flash back to stock. However, no one will know for sure until it is released. It has been a while since the MF3 OTA started to roll out, so if Samsung is going to release the full MF3 firmware, it should be soon.
As far as JTAG goes, I haven't seen a successful flash yet. I think the JTAG people are waiting for the firmware release as well.
I thought J-Tag works for flashing MF3 but doesn't work for downgrade. It doesn't work for both?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
scott14719 said:
I'm sure AT&T views MF3 as a complete success. It's just the people interested in customizing and modding their phones (XDA minded people) that hate it.
When Samsung releases the full MF3 firmware, you should be able to use ODIN to flash back to stock. However, no one will know for sure until it is released. It has been a while since the MF3 OTA started to roll out, so if Samsung is going to release the full MF3 firmware, it should be soon.
As far as JTAG goes, I haven't seen a successful flash yet. I think the JTAG people are waiting for the firmware release as well.
Click to expand...
Click to collapse
Yay! thank you so much for at least giving me hope to fix my device. i was very experienced developer of galaxy a, you may never heard of galaxy a. it was released only in Korea. i thought galaxy s4 might be similar to galaxy a. i should've studied more. in Korea, we used to make custom roms flashable by Odin. XDA doesn't seem to have roms that are flashable with Odin. i used to make my own roms. please could you help me fixing my phone when MF3 releases? i don't know a lot about galaxy s4. again, thank you.
XDA is full of ODIN flashable Stuff. MF3 is just locked tight. We are working on some stuff to make it better for now until there is a bootloader unlock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
XDA is full of ODIN flashable Stuff. MF3 is just locked tight. We are working on some stuff to make it better for now until there is a bootloader unlock.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't know that! thanks!
graydiggy said:
I thought J-Tag works for flashing MF3 but doesn't work for downgrade. It doesn't work for both?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is from the thread when Aou was trying to JTAG his device...
well i finally got in touch with mobile tech and got a refund/explanation of our problem it seems the qfuse being blown is the main reason this is happening..
Unfortunately, we were not able to repair your device. The device's onboard EMMC controller was in a non-responsive state. It is advised to try out warranty replacement if possible or to search for a parts device and use it's mainboard for the swap.
The blown fuse is the reason JTAG (or ODIN / KIES) for that matter) can not revert the device to a previous firmware.
Once the full MF3 firmware is available, it will probably be possible to restore the device via JTAG to MF3, but as we know, the MF3 firmware is not yet available. Therefore, it can not be done (yet). And once / if it is released, there is no guarantee it will work until it is tried.
The quote from Mobile Tech above mentions swapping mainboards, but I don't think it will work due to the NV memory I mentioned before (but maybe it can?).
Anyway, the key seems to be wait until the full MF3 firmware is released or wait until / if the bootloader is unlocked. I think the firmware is the better bet and it isn't guaranteed.
Switching out motherboards should be no issue. All that is being done is dropping it into the back of the screen, plugging in some flex cables, slap it back together and booting it up. I know why we can't downgrade, just didn't realize that a full system dump of MF3 was not enough for J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
ryujeff said:
Didn't know that! thanks!
Click to expand...
Click to collapse
Well, be careful. The SGH-I337 (AT&T S4) has a locked bootloader, so only official firmware (signed by Samsung's encrypted key) can be flashed via ODIN. To complicate things, the MF3 update (which you have) made the previous firmwares unflashable via ODIN. Phones that did not update to MF3 (still on MDB or MDL firmware) have the ability to flash Custom recoveries and Roms because of an exploit called "LOKI". LOKI was patched when the MF3 OTA was released. So any phone on MF3 can not flash recoveries or ROMs at this point. ODIN is basically useless for the time being.
I highly suggest you read the "pinned" threads in the "general" and Q & A sections. Alsor ead the threads that have "MF3" in the titles. This will give you a good understanding of what your options are if / when you can repair your phone. There is a method being developed that would allow several custom Roms to exist on the phone (MF3), but it hasn't been tested or released yet. The thread about it is in the "general" section as well. However, again, it will do you no good unless you get your phone repaired / replaced.
---------- Post added at 12:14 AM ---------- Previous post was at 12:09 AM ----------
graydiggy said:
Switching out motherboards should be no issue. All that is being done is dropping it into the back of the screen, plugging in some flex cables, slap it back together and booting it up. I know why we can't downgrade, just didn't realize that a full system dump of MF3 was not enough for J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I realize the physical action of switching motherboards isn't an issue, I was just wondering if it would do any good? If the NV memory remains in another area of the circuitry, or other memory remains that still has a part of the MF3 bootloader structure intact, switching the motherboard by itself won't do any good. If all structures of the MF3 bootloader are included on the motherboard, maybe it would work.
Also, last I knew, bootloaders can't be pulled via system dump. They have to be obtained via official firmware release. In the case of MF3, the bootloader parts from the OTA can't be combined with a system dump from a post OTA MF3 device because of signing issues. It just doesn't work. It's been tried. I know there are a couple of MF3 Tar balls floating around but they are only good for parting out. Aou has tried a bunch of this stuff. Honestly, I do not know 100% of the technical reasons why it won't work. I have a pretty good understanding but that is it. Truly, the MF3 Bootloader is the problem and until the full, official, MF3 firmware is released from Samsung (or a signing key is released / leaked) I don't see much happening in the area of repairing / restoring bricked MF3 devices.
It shouldn't remain. The only other parts that are separate from the motherboard and screen assembly. Are the charging port assembly/flex,the camera, the softkeys/home button assembly and the back housing that just holds antennas. None of that should have anything on it that would hold any residual MF3 data. Even if something did, it would have to hold the whole update to possibly do any kind of damage in eras of installation and blowing the Qfuse. If it did not and it blew the fuse without updating, it would instantly render the device useless if the motherboard had MDL on it.
All data is stored in the motherboard.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
So I could not get the phone to root (super user binary issue) and I installed that SetUID kernal and now my phone will not boot. Can someone please guide me to a fix. Thanks
Set uid kernel? What are you talking about? The sprint gs4 doesn't gave a kernel like that.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Set uid kernel? What are you talking about? The sprint gs4 doesn't gave a kernel like that.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Crap I just realized that it is a T-mobile thing. Am I completely screwed now?...should have following my rule and read twice downloaded once.
If you did flash a kernel with that name, it would explain your boot problems.
Flash one for the Sprint S4 and all will be good.
Sent from my SPH-L720 using Tapatalk
frostedunit said:
If you did flash a kernel with that name, it would explain your boot problems.
Flash one for the Sprint S4 and all will be good.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
OK I am currently downloading the 1.4gig SPR-L720VPUEMK2-20131212171424.zip file and will Odin that onto my phone. It is still about 40min from finish so if there is something smaller then I could try that in the mean time. Thanks for the Info and assurance that I maybe alright.
engelstine said:
OK I am currently downloading the 1.4gig SPR-L720VPUEMK2-20131212171424.zip file and will Odin that onto my phone. It is still about 40min from finish so if there is something smaller then I could try that in the mean time. Thanks for the Info and assurance that I maybe alright.
Click to expand...
Click to collapse
Any of the appropriate kernels from the original development section will get you up and running. You'll just have to pick one for whatever rom you were one (4.3, 4.4, tw, aosp, etc)
Sent from my SPH-L720 using Tapatalk
frostedunit said:
Any of the appropriate kernels from the original development section will get you up and running. You'll just have to pick one for whatever rom you were one (4.3, 4.4, tw, aosp, etc)
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok well so next development....I odin the SPR-L720VPUEMK2-20131212171424 from samsungs website. Now I get the Galaxy Initial screen, it flashes and then nothing. advise lol
factory reset through stock recovery. This will wipe the whole phone. pics music etc. see if this helps.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
factory reset through stock recovery. This will wipe the whole phone. pics music etc. see if this helps.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
How do I get into stock recovery? Tried up, mid, power. Just flashes the galaxy screen and turns off.
Ok so found out that I can get into recov with power plugged in. So battery is low. But now did fact reset and still galaxy screen the now just blue led black screen
ok so I am back running. installed mk2_stock02 from Dev page. Was able to get CWM booting and loaded the ROM from there. My next question, probably has been answered but this is where my problem started before. When I go to open the SuperSU I get an error saying there is no SU Binary installed....and then closes.
Install super su from market
Sent from my SPH-L720 using Tapatalk
alright Im back in action. used CF-auto root and away we went. Now I have successfully rooted my gear also. Thanks for the Help guys I really appreciate it.
How do you go about changing the splash screen on the S4? I came from an HTC One which achieved it through fastboot but to my understanding AT&T's S4 doesn't have fastboot.
P.S I'm not talking about boot animations since a lot of people get them confused lol.
Deleted
Sent from my Nexus 5 using XDA Free mobile app
Kendosis said:
How do you go about changing the splash screen on the S4? I came from an HTC One which achieved it through fastboot but to my understanding AT&T's S4 doesn't have fastboot.
P.S I'm not talking about boot animations since a lot of people get them confused lol.
Click to expand...
Click to collapse
I don't believe you can. I had an HTC before this and a custom splash, but the splash on this one is probably integrated into the bootloader (so it changes with the custom flag).
Sent from my SGH-I337 running BlackBox 3.0
DeadlySin9 said:
I don't believe you can. I had an HTC before this and a custom splash, but the splash on this one is probably integrated into the bootloader (so it changes with the custom flag).
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
Aww that sucks at&t really has this device on lock, thanks though probably gonna end up sending back the S4 and try something else.