just got my shiny s4...been using jailbroken iphone forever,anything i should know before starting following the root guide in Original Android Development? Thanks!
You should wait for stock images to be uploaded at a later point. Currently if you soft brick there is no fix until factory images are provided Sure, the guide is quite simple, but if a problem occurs you will have wish you waited. Just my 2 cents. Especially with you being new to android I would take it easy to start off.
Oh and make sure you read. Read. A. Lot. It will help you understand a lot of things and help you self diagnose and fix things when you read troubles others are having with a given issue. You will be surprised how much knowledge you can gain by just casually keeping track of various forum activity. Best of luck. Can't wait to get my S4 in the morning
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
Mike on XDA said:
You should wait for stock images to be uploaded at a later point. Currently if you soft brick there is no fix until factory images are provided Sure, the guide is quite simple, but if a problem occurs you will have wish you waited. Just my 2 cents. Especially with you being new to android I would take it easy to start off.
Oh and make sure you read. Read. A. Lot. It will help you understand a lot of things and help you self diagnose and fix things when you read troubles others are having with a given issue. You will be surprised how much knowledge you can gain by just casually keeping track of various forum activity. Best of luck. Can't wait to get my S4 in the morning
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
Click to expand...
Click to collapse
Yes do exactly as mike says above!! u dont wanna brick this sick phone...
Mike on XDA said:
You should wait for stock images to be uploaded at a later point. Currently if you soft brick there is no fix until factory images are provided Sure, the guide is quite simple, but if a problem occurs you will have wish you waited. Just my 2 cents. Especially with you being new to android I would take it easy to start off.
Oh and make sure you read. Read. A. Lot. It will help you understand a lot of things and help you self diagnose and fix things when you read troubles others are having with a given issue. You will be surprised how much knowledge you can gain by just casually keeping track of various forum activity. Best of luck. Can't wait to get my S4 in the morning
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
Click to expand...
Click to collapse
I think it could be fix for soft brick. If we can get to download mode we can try using samsung kies to restore software. I was doing this on my skyrocket and S3. Just not sure is you can do it if bootloader is lock. If someone with soft brick phone want to try link is in my signature.
norbarb said:
I think it could be fix for soft brick. If we can get to download mode we can try using samsung kies to restore software. I was doing this on my skyrocket and S3. Just not sure is you can do it if bootloader is lock. If someone with soft brick phone want to try link is in my signature.
Click to expand...
Click to collapse
If you look at the few things we have in the dev section now it explicitly says there is no stock image and thus no fix for soft brick at the moment. If someone is soft bricked at the moment and is willing to try your solution then great because you very well could be on to something, but I just want to inform the user of the risk currently being taken
-------------------------------------------------
Sent from my Skyrocket i727 running Slim Bean
-----------Nexus 7 running AOKP M1-----------
Related
Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
gedster314 said:
I've ran many versions of the stunner rom without issues. I find it hard to believe you are bricked.
Describe your situation. If the display turns on, you are not bricked. Have you tried connecting to a PC and see if Odin can see your phone?
Click to expand...
Click to collapse
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
octavian90 said:
Uninformed fail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Your right. Why don't you just give the guy razor blades and sleeping tablets even before he explains his issue.
Yes I'm new to the Note but I have brought back many phones back from the "BRICK".
Nothing works, I can't boot into download or recovery
Any ICS kernel based on the leaks seems to carry a danger of permanent damage to the eMMC.
So far the only safe Samsung ICS kernels seem to be those based on the I9100 update4 source base.
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Check the end of stunner thread... Send it to mobile video review for jtag
Sent from my GT-N7000 using Tapatalk 2
every time i consider bumping to a Custom ICS I see a thread like this or some issue that is a showstopper for me.
I'm glad I haven't yet had ICS.
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
sutekidane said:
I'm also in the same boat as you. I flashed it and it turned into a brick thinking it was the battery being drained. Plugged the phone in and the the phone didn't respond so I knew something went really wrong. Then the bricked news followed on the thread. There is pretty much nothing we can do right now but to send it out to get a JTAG, which is not a guaranteed fix either according to some folks in the thread. The very last resort is to replace the mainboard.
Click to expand...
Click to collapse
don't lower your hopes down, I've seen countless and numerous times of Bricked Notes being revived and restored thru JTAG. This process is the much low level process you can get of restoring your Note into it's normal process. I don't see why your Note can't be restored if it's done thru JTAG.
(Not unless you have a broken ICs or chipsets already, which contitutes a hardware failure and that's the time you may have to replace it.)
JTAG is trusted already and proven to restore almost all bricked Notes.
Just from my own experiences..
Cheers
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
MrSlippyFist said:
sorry to hear that guys i was very reluctant to switch from stunner 5 to any other version....im staying with 5 until it gets stable.....i heard about the bricking earlier today....thats ****ed ...i know they figured it out already...and lp5 is part of the problem as well....good luck
Click to expand...
Click to collapse
Just installed 1 4.26... I would recommend you to try it...its on another level than beta 5 ...very smooth n stable
Sent from my GT-N7000 using xda premium
thebz1 said:
Hi everyone, I was one of the people who bricked their phone by flashing the ICS Stunner Rom. I thought it would nice if there was a place where we could discuss how to go about solving this. I'm aware that we'll probably just have to send our phones in for repair but I thought it would be best to look at all the options first.
Click to expand...
Click to collapse
try to use jig bro maybe it will solve the gnote
Oh no...not another CWM touch recovery-esque fiasco. I thought we were over that? And, damn that sucks dude. I've been in your exact shoes. This is my second phone, and I currently use Stunner as my daily driver...so I'm a bit worried now!
androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
so why aren't the other roms running lp5 bricking the phone?
androidindian said:
Its not coz of stunner from... its coz of lp5 kernel with a malfunctioned recovery during system partition format... so please change your title
No it's a specific problème of stunner... It happens...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Envoyé depuis mon GT-N7000 avec Tapatalk
thebz1 said:
Well what would you recommend I do from here though? I want to get this fixed as soon as possible.
Click to expand...
Click to collapse
do you have a JIG or the tools to create one by yourself ? this seems your only solution for now, anyway does your phone enter to boot animation or it just doesn't flick ?!
there isnt much any of us who had our phones bricked can do about, and yes it was a version of ics stunner that did the damage, i have a feeling its gonna be a motherboard replacement
Hello folks I just bought the 32gb TF300T at Best Buy tonight. Got the price match via the "Office Max" ad for $349.99 plus tax...
Anyhow some questions.
I have rooted, rom'd, themed, ect... the heck out of my DroidX and am generally very comfortable mucking around in that territory but I'm reading various threads here and about concerning the permanent bricking of the TF300 if a person does something wrong. I'm used to being able to SBF & restore the DroidX if something goes amiss and bring the 'brick' alive again. That being said, I'm a bit squeemish at the moment to do any modifications with the TF300 but of course will be itching to nontheless... Mainly would like to definitely Root-Unlock(?)-Flash Roms. Any suggestions or particular threads to point me to concerning this? I've done a little looking around but there seems to be multiple methods discussed for even rooting and I'm a little uncertain on where to begin realizing this is likely a bit different than the DroidX.
Any recommendations as to "Must Have" apps and/or do most apps that work on the DroidX for example, still work on this tablet?
My uses will be for both work and play. A lot of web surfing, email, and media.
Any and all tips are appreciated! Thanks
Once you unlock the bootloader you should be good to go. Just make sure you follow directions and read up before you do anything new. Also just so you know once you unlock you cannot go back to locked and you will not get updates from asus. Currently I'm just going with it locked and rooted and I'm happy. Ics is so good already plus there aren't too many rooms out yet. Give it time though and once they start to roll out and I get sick of stock ill start flashing. I'm also holding out so that if anything goes wrong my warranty is still valid and I can get it replaced.
Sent from my ASUS Transformer Pad TF300T using xda premium
Howdy!
First off, nice buy, I do so enjoy my TF300T, and I'm sure you will as well.
As you prolly know from the cheaper price, Asus also used cheaper parts to build their tablets. Make sure the screen is free of defects, so you can return it for a new one if something goes wrong. It's a beautiful tablet as long as your luck is up and you don't brick it by mistake. My advice: wait a week or two. If you're happy, go ahead and visit this thread ( http://forum.xda-developers.com/showthread.php?t=1669827) for a cyanogenmod 9 port. The Nightlies are stable, I'm using it right now, but there are still issues with GPS and Sound, which will be fixed with time and patience.
You can root (if you haven't updated past .17 and don't want to install CM9 yet) easy by using sparkyroot at: http://forum.xda-developers.com/showthread.php?t=1526487 ))) But if you have, do some research, and you'll find what you"re looking for.
If you do, here's something to help you along: http://www.android.gs/update-asus-t...anogenmod-9-android-4-0-4-ice-cream-sandwich/
There's more, but you have to search for it! Google is your friend.
------------------------------------
If I've helped you, please don't forget to thank me!
TDinsmoor said:
As you prolly know from the cheaper price, Asus also used cheaper parts to build their tablets. Make sure the screen is free of defects, so you can return it for a new one if something goes wrong.
Click to expand...
Click to collapse
I second this completely. I'm on my third tablet. The first one had a dead pixel, and the second had a hardware defect where the touchscreen went crazy if I applied any amount of pressure to the left edge of the tablet. The second one took me a few days to figure out what exactly was happening.
Thanks for the replies! I did actually take that update from Asus last night after powering it up.
My Kernel version is 2.6.39.4
Wonder if I can even root now at this moment?
Thinking of holding out for now regarding unlocking as I would sooner keep it within warranty at this time plus it doesn't seem like there are any real perks in unlocking currently if the Roms & Kernels out now are still young in development.
I would like to root though if I haven't screwed up by already taking the update so I can run TB, ect...
Thanks again guys. I'm sure there will be many questions to come!
Yer very welcome.
I do recommend the updated build.prop, it's low-profile, but helps with things such as battery life and other optimization. You need root, however.
TDinsmoor said:
Yer very welcome.
I do recommend the updated build.prop, it's low-profile, but helps with things such as battery life and other optimization. You need root, however.
Click to expand...
Click to collapse
Thanks! I did get my root very easily per this thread: http://forum.xda-developers.com/showthread.php?t=1689193
The thing is I tried to get the CWR via:
3. If you have root and need CWM recovery.
Why? Nandroid backups and restores. Debrick. Flexibility. Numerous other reasons. ( but no OTA)
- Step 1. Run the tool "1-Click Transformer Root.bat"
- Step 2. You'll be presented with a menu. Choose option (3)
- You'll have CWM Recovery
Click to expand...
Click to collapse
And was unable to as option #3 is simply "Quit" :silly:
I'm wondering if one needs to be "Unlocked" to obtain CWM recovery?
Anyhoo, yea, could you point me to this updated "build.prop" discussion and method for obtaining? Anything in particular to be cautious of when doing it?
Thanks!
lazer9 said:
Thanks! I did get my root very easily per this thread: http://forum.xda-developers.com/showthread.php?t=1689193
The thing is I tried to get the CWR via:
And was unable to as option #3 is simply "Quit" :silly:
I'm wondering if one needs to be "Unlocked" to obtain CWM recovery?
Anyhoo, yea, could you point me to this updated "build.prop" discussion and method for obtaining? Anything in particular to be cautious of when doing it?
Thanks!
Click to expand...
Click to collapse
You need to be unlocked for CWM. In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
jgaf said:
You need to be unlocked for CWM. In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
Click to expand...
Click to collapse
Thanks for that info. I'll read up on the process now so I will have a good grip on it if/when one becomes available for the current firmware.
jgaf said:
....In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
Click to expand...
Click to collapse
Wait... From that thread: Post #261 http://forum.xda-developers.com/showpost.php?p=27666040&postcount=261
It seems there are actually two for the latest firmware or am I reading something wrong?
Edit: Disregard the above. I just realized those are for the WW version and not US. If I'm understanding correctly... Whew, so much to be careful about.
So it now seems clear that OTA will NOT come for the very nice Google IO version of this device, I recently learned that the rooted versions will handle DRM material from Google play,,(correct?) so I think I'm ready to take the plunge,,
Any advice and step by step instructions? Is there a good JB version (if I'm going to do it might as well go all the way?)
Have not rooted the thing at all, so a bit nervous,, I have installed early ADB's on other devices.. so I get generally how the process should go,, but of course the 10.1 is different and the GIO one is even different from all the rest.
Direction/advice and cautions appreciated.. I love the device and don't want a brick in it's place..
And yes I have both the Nexus 7 and Galaxy Nexus from this year's GIO...
Thanks in advance!:fingers-crossed:
You need to make use of the search feature here. Lots of great info on rooting and flashing.
The Google I/O version is a different build and doesn't get any updates pushed to it by Samsung.
Thanks but...
BretonGirl said:
You need to make use of the search feature here. Lots of great info on rooting and flashing.
The Google I/O version is a different build and doesn't get any updates pushed to it by Samsung.
Click to expand...
Click to collapse
Yes I have been searching diligently but as you note the GIO tab is "different" so it is not clear which run and which are eligible solutions.
I see from the views that a number are interested in this question but from searching I don't see great solutions..
It seems that the JB versions are not fully baked.
The ICS versions each seem to have issues and it is not clear which if any are running smoothly on the GIO version.
Hence my attempt by asking the question, to gain some authoritative clarity!
The google io version is the same just is fully unlocked by default. Samsung has indeed pushed more then 1 update to this device in the past. Doesn't seem like they will further. It is NOT 100% GOOGLE on this tab... Not sure why everyone thinks so. Anyways, anything that runs on the retail versions will run on the io just make sure u don't flash a new bootloader keep the one u already have. Use Odin to flash a custom recovery then use that recovery to flash a CUSTOM Rom. I'm running cm10 with very few problems
Sent from my PG86100 using xda premium
Thanks! That helps!
That will help a lot.. The clarity on how the GIO version fits in is the main thing that was confusing me.
Now I have a path to follow.. I think.. The CM10 looks very tempting with JB from what I have been reading here,, I take it the only somewhat real issue is the front camera?
xTONEx said:
The google io version is the same just is fully unlocked by default. Samsung has indeed pushed more then 1 update to this device in the past. Doesn't seem like they will further. It is NOT 100% GOOGLE on this tab... Not sure why everyone thinks so. Anyways, anything that runs on the retail versions will run on the io just make sure u don't flash a new bootloader keep the one u already have. Use Odin to flash a custom recovery then use that recovery to flash a CUSTOM Rom. I'm running cm10 with very few problems
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Sorry but need pointers..
A quick scan and I could not locate the Odin recovery instructions or software, and can you clarify that you mean the CM10 rom, not sure if you are implying something more by specifying CUSTOM Rom?
Anything I need to know about Not replacing the bootloader?
I'm assuming that I can ignore instructions relating to rooting/unlocking? Since it is a GIO device?
Do i need to do anything special to keep apps/access to app store, Google provided apps Gmail etc or does CM10 have all the basics??
Sorry to be so basic...Just don't want to end up with a shiny brick!
xTONEx said:
The google io version is the same just is fully unlocked by default. Samsung has indeed pushed more then 1 update to this device in the past. Doesn't seem like they will further. It is NOT 100% GOOGLE on this tab... Not sure why everyone thinks so. Anyways, anything that runs on the retail versions will run on the io just make sure u don't flash a new bootloader keep the one u already have. Use Odin to flash a custom recovery then use that recovery to flash a CUSTOM Rom. I'm running cm10 with very few problems
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
dartdog said:
A quick scan and I could not locate the Odin recovery instructions or software, and can you clarify that you mean the CM10 rom, not sure if you are implying something more by specifying CUSTOM Rom?
Anything I need to know about Not replacing the bootloader?
I'm assuming that I can ignore instructions relating to rooting/unlocking? Since it is a GIO device?
Do i need to do anything special to keep apps/access to app store, Google provided apps Gmail etc or does CM10 have all the basics??
Sorry to be so basic...Just don't want to end up with a shiny brick!
Click to expand...
Click to collapse
Google is your friend. You'll find ODIN and instructions on how to use it easily.
I believe you have to flash or install the Google Framwork apk separately. I'm sure the CM10 folks have a sticky or FAQ to help.
Read as much as you can about the process before doing it!
Found this on Odin on Android Authority
this appears to answer some of my questions at least where to find Odin
http://www.androidauthority.com/gal...kmod-recovery-5-5-0-4-custom-recovery-102580/
But of course I want to go to CM10 so I need to think how that modifies things...
BretonGirl said:
Google is your friend. You'll find ODIN and instructions on how to use it easily.
I believe you have to flash or install the Google Framwork apk separately. I'm sure the CM10 folks have a sticky or FAQ to help.
Read as much as you can about the process before doing it!
Click to expand...
Click to collapse
I'm honestly not sure where to post this, I found it on another forum (and that post was made about three hours ago). In any case, Samsung appears to have open sourced the stock firmware and kernel for Straight Talk's version of the Galaxy S II.
If you go to http://opensource.samsung.com/ and search of the model number - SGH-S959G - it's the only thing that comes up. The download appears to be just what it says, the uncompiled source code.
I've been looking for stock ever since I bought this phone and since I'm not exactly green when it comes to Linux and using a terminal, I'm tempted to give a crack at compiling this myself. Anybody have any experience with this? It can't be too hard...right? :silly:
(source: http://androidarea51.com/modifications/straight-talk-s2-sgh-s959g-source-code/msg8830/)
IndigoAK said:
I'm honestly not sure where to post this, I found it on another forum (and that post was made about three hours ago). In any case, Samsung appears to have open sourced the stock firmware and kernel for Straight Talk's version of the Galaxy S II.
If you go to http://opensource.samsung.com/ and search of the model number - SGH-S959G - it's the only thing that comes up. The download appears to be just what it says, the uncompiled source code.
I've been looking for stock ever since I bought this phone and since I'm not exactly green when it comes to Linux and using a terminal, I'm tempted to give a crack at compiling this myself. Anybody have any experience with this? It can't be too hard...right? :silly:
Click to expand...
Click to collapse
You won't get the stock firmware by compiling the kernel, mate. Why do you want stock when you already have stock (original) firmware? If you're looking for unbranded, you're unlikely to find it as you have a carrier specific phone.
Force Close said:
You won't get the stock firmware by compiling the kernel, mate. Why do you want stock when you already have stock (original) firmware? If you're looking for unbranded, you're unlikely to find it as you have a carrier specific phone.
Click to expand...
Click to collapse
I'm aware of how this source code works!
IndigoAK I am the one that posted the link on AA51. The file appears to be in tar.gz format like what is used for install through odin. I have not tested it, as I am not a developer, or in need of flashing to factory firmware at this time. I posted it as I seen many people looking for it. I believe it is needed to be able to safely start making modifications for this phone, CWM, Root, custom ROMs, ect., and being able to flash back to stock if something goes wrong. Hopefully with the information out there now it will jump start development.
Edit: After further research the source code files are used to create the firmware, and these cannot be installed through Odin. Feel free to correct me if I'm still wrong.
mr-cook said:
IndigoAK I am the one that posted the link on AA51. The file appears to be in tar.gz format like what is used for install through odin. I have not tested it, as I am not a developer, or in need of flashing to factory firmware at this time. I posted it as I seen many people looking for it. I believe it is needed to be able to safely start making modifications for this phone, CWM, Root, custom ROMs, ect., and being able to flash back to stock if something goes wrong. Hopefully with the information out there now it will jump start development.
Click to expand...
Click to collapse
I probably should have linked to your post. I apologize.
I just thought that posting it here on XDA might get it seen by more people who might know how to put this to use.
Hopefully somebody does put it to use. Due to the way that Straight Talked has gimped this phone, it's going to take the community to really make it worth the price they're charging for it.
I tried to link to the original post on android area 51, but as a new member I am not allowed, yet. I am just trying to get information out there, so thank you for posting it here (as I just now joined). The phone is fairly new and under advertised, but hopefully these posts will stir interest.
I was looking under the battery cover and noticed the FCC id for this phone (SGH-S959G) is A3L SGH I777. Now for everyone smarter than I. Does this mean that the phone is an i777, and would all the mods and ROMs ect. be directly compatible. Also its android 2.3.6. Version s959g UDLG1. Kernel 2.6.35.7. Any thoughts, educated opinions would be appreciated. Thanks.
Sent from my Galaxy Precedent using Tapatalk 2
mr-cook said:
I was looking under the battery cover and noticed the FCC id for this phone (SGH-S959G) is A3L SGH I777. Now for everyone smarter than I. Does this mean that the phone is an i777, and would all the mods and ROMs ect. be directly compatible. Also its android 2.3.6. Version s959g UDLG1. Kernel 2.6.35.7. Any thoughts, educated opinions would be appreciated. Thanks.
Sent from my Galaxy Precedent using Tapatalk 2
Click to expand...
Click to collapse
No.
Everything needs to be modified. The I777 rooting method works for this device, but nobody has been able to get past that as far as I'm aware. I've lost count of the number of times I've had to double reboot my phone trying to install every custom recovery image (and searching around suggests this is the case for a lot of other people) I can get my hands on and I've kept a pretty close eye on custom firmware sites - none of them have added support for this device (probably because you can't install a custom recovery image yet).
Guys I have the same problem, I tried to root my Straight Talk Galaxy SII using the AT&T root but CWM doesn't install and the root breaks the Wifi, Contacts save option, several apps like YouTube. I cannot revert back to the stock ROM due to this issue and I really could use the help.. I'm surprised that DEV teams haven't done much on the phone considering for 45 dollars a month you get really fast 7mb/s speed.
I'm willing to do whatever I can to contribute to a way of finally getting this awesome phone off of a sucky stock rom.
Thanks everyone!
I was just curious if it could be fully flashed to stock i777 GB. As it appears to be the exact same hardware. Completely start over making it the at&t i777.
Sent from my SGH-S959G using Tapatalk 2
mr-cook said:
I was just curious if it could be fully flashed to stock i777 GB. As it appears to be the exact same hardware. Completely start over making it the at&t i777.
Sent from my SGH-S959G using Tapatalk 2
Click to expand...
Click to collapse
No. I tried this.
Also, if your WiFi doesn't work, you probably used the Zedomax kernal. Search XDA for Entropy's kernel and use that instead.
LOOKIN. For Fully Rooted .. Samsung Galaxy s2. Sgh-s959g From Straight Talk. FLASHED a kernel dat when loading. Tells me its a sgh-i9100 ... has a ... ! ...triangle under it...and when I check the info on bout phone. It says sgh-i777.. any links for the best FULLY ROOTED kernels GB?.. PS. Willing to do testing with this phone from straight talk. But has. Att kernel.. one from. Entropy! !! Thanks 
Hi I just got a new sprint Galaxy s4. I had a Samsung infuse 4g that I rooted and unlocked (which btw was hard to do for a newb way back then) but I never flashed a rom. To be honest I was afraid that I would destroy the phone. They are not cheap. I still have the infuse, so I guess I could practice flashing roms on that one but is it basically the same process? I just really really do not want to destroy my beautiful phone. Is it risky to flash ROMS or put other stuff in the phone? Thanks for the advice. This is an awesome site.
*Anything* you flash to your phone carries a risk (however minute) that it'll brick the device. The root method may be different, but for the most part ROM flashing is the same across any Android device.
IMPORTANT: Check your device model, since there are two variants of the Sprint S4 out there (SPH-L720 and SPH-L720T). The 720T doesn't work with all ROMs, and (last I checked) you lose the Spark connectivity, but 1x/3G/LTE will still work. I have one of the old models before Sprint started rolling out Spark, so I haven't really been keeping up with that part of it.
emeralds5668 said:
Hi I just got a new sprint Galaxy s4. I had a Samsung infuse 4g that I rooted and unlocked (which btw was hard to do for a newb way back then) but I never flashed a rom. To be honest I was afraid that I would destroy the phone. They are not cheap. I still have the infuse, so I guess I could practice flashing roms on that one but is it basically the same process? I just really really do not want to destroy my beautiful phone. Is it risky to flash ROMS or put other stuff in the phone? Thanks for the advice. This is an awesome site.
Click to expand...
Click to collapse
once you get the rooting done here is a great place to start looking for ROM's
http://forum.xda-developers.com/showthread.php?t=2303917
cyberweasal said:
once you get the rooting done here is a great place to start looking for ROM's
http://forum.xda-developers.com/showthread.php?t=2303917
Click to expand...
Click to collapse
thanks for replying. I posted a question on the rooting thread regarding the s4. I was wondering about rooting it with my
Android version. I believe it's the latest but was not sure. Do you know if it's relatively safe to try that or are there issues like boot loops? Maybe I should leave well enough alone because I doubt I could fix a brick. These are really nice phones...thanks for your help
emeralds5668 said:
thanks for replying. I posted a question on the rooting thread regarding the s4. I was wondering about rooting it with my
Android version. I believe it's the latest but was not sure. Do you know if it's relatively safe to try that or are there issues like boot loops? Maybe I should leave well enough alone because I doubt I could fix a brick. These are really nice phones...thanks for your help
Click to expand...
Click to collapse
i had no problems. that being said. make sure you also have a stock rom down loaded on the phone or on a pc to fall back on, that way if you do boot loop you can just flash that. also once rooted make a backup!
you can root without doing a new rom or even choose a rom thats mostly stock with minimal changes its up to you how deep you go.
first thing if first once you root if you have KNOX you WILL flag the knox warranty count by 1 and that is not reversible yet.
good luck