Database Users

[Q] Risky to root?

I've just receieved my Galaxy S (Swedish if that affects anything). How big is the risk of bricking when trying to root?
I've had the phone for 1 hour and dont want to make it to a papper weight already

Before you do anything. See if the phone can go in download mode. Hold volume down+ home and power button when phone is off. Let go off power button then home and vol down. If your phone can do that then its all good. Rooting phone is rather safe and i have not heard of anyone. Bricking from rooting. But you might need download and upgrade mode if something goes wrong. There's heaps of rooting methods too. Have fun.
typed with bloodied fingers on a Apple Newton 2100. Hail Fuhrer Jobs!

Not sure if I'm doing it wrong but the phone just boots as normal.

if your worried about breaking your phone does Dl ryanza lag fix do the root and do the lag fix it will be Alot fast and rooted

it's safe to root
but risky to do any other soft of hacks to make the devices faster

I primarily want to change country for Market and change the filesystem so it will be faster. Maybe unlocking SIM too. I'm not interested in changing ROM or anything like that.
Where do I start?

use this instead
AppBrain App Market
link here http://forum.xda-developers.com/showthread.php?t=765081
djr83 said:
I primarily want to change country for Market and change the filesystem so it will be faster. Maybe unlocking SIM too. I'm not interested in changing ROM or anything like that.
Where do I start?
Click to expand...
Click to collapse

I really cant get into download/update mode. Is it safe to root if I use adb?

yes rooting is safe
only put the update.zip file on the internal sd card
reboot to recovery mode using ADB or any other method
and select the file update.zip

AllGamer said:
yes rooting is safe
only put the update.zip file on the internal sd card
reboot to recovery mode using ADB or any other method
and select the file update.zip
Click to expand...
Click to collapse
I'm in the same situation. My Recovery/Download mode is deactivated and my phone is so slow sometimes that it's frustrating to use.
I want to root and apply RZA lag fix
I'm wondering has anyone here ever "bricked" their phone by just rooting and having to recovery it using recovery/download mode?
I have to make sure that it's almost impossible to brick the phone while rooting because I would have to send the phone to Hong Kong because I bought the phone there and I'm currently in Canada.
Thanks

AllGamer said:
yes rooting is safe
only put the update.zip file on the internal sd card
reboot to recovery mode using ADB or any other method
and select the file update.zip
Click to expand...
Click to collapse
Ok, think I'm gonna test it. Where do I get update.zip?

there are many listed in the development section
specially the topic about "easy root your phone"

AllGamer said:
there are many listed in the development section
specially the topic about "easy root your phone"
Click to expand...
Click to collapse
Is http://forum.xda-developers.com/showthread.php?t=728754 the one you mean?
I'm also really interested in lagfix (http://forum.xda-developers.com/showthread.php?t=724251), is this safe to do when I cant access download mode?

not safe to do with you not have download mode
many people have done it and died (sent back to samsung for repair) because of that
yet there are more people that have done it and enjoyed the new speed
so my recomendation, don't do it
go exchange your phone, and get one that has working 3 buttons before you do the lag fix
or just wait a few more days for FROYO 2.2
and if it dies with legit official froyo for public release, then its under warranty....
but yeah that will still suck, it will still mean like at least 5+ weeks without a phone to use.

AllGamer said:
not safe to do with you not have download mode
many people have done it and died (sent back to samsung for repair) because of that
yet there are more people that have done it and enjoyed the new speed
so my recomendation, don't do it
go exchange your phone, and get one that has working 3 buttons before you do the lag fix
or just wait a few more days for FROYO 2.2
and if it dies with legit official froyo for public release, then its under warranty....
but yeah that will still suck, it will still mean like at least 5+ weeks without a phone to use.
Click to expand...
Click to collapse
Why would it matter if 2.2 is released? I'm not interested in flashing 2.2, I just want to do lagfix. If it dies because of the lagfix I guess an official 2.2 wont help me?
Is it even possible to get a new with working 3 buttons? I guess all the new ones have the download mode locked? And I'm not even sure I would be allowed to exchange it since it's really not anything wrong with the one I have.

they are mixed batches, even in new ones
you can get working 3 button and not working 3 button on the same shipment

Soft brick installing GingerbreadlatinIME.zip

I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:

to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.

tenbeau said:
I just tried flashing the Gingerbreadime.zip and followed the directions to the letter and I experienced my first soft brick. The phone went into a boot loop at the mytouch screen. Luckily I was able to go into Recovery and restored the backup I had made after rooting and turning s=off. It appears to have restored okay as I still have root etc. Does anyone have any idea how or why this happened ? This zip was posted in Droid-Life and was advertised as good for all android 2.2 devices. I have never used adb but have it set up on my phone so I guess I had better get more familiar with it. I have flashed my Vibrant numerous times using Odin and Rom manager but I don't believe that there is a similar program for the Mt4g (Odin that is) I guess I have been spoiled by my Vibrant as it seems to have more options to recover with and are easier to use from what I can tell. I do love this MT4g though It is probably the best all around phone I have ever owned. Any and all info and help is greatly appreciated.:
Click to expand...
Click to collapse
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.

bobsbbq said:
to my knowledge there has been no gingerbread port for our device yet. Your lucky you didn't brick your device.
Click to expand...
Click to collapse
yes I a sure am. I trusted the Dorid-Life site and should not have. Thanks for the swift response...

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.

Please post questions in Q&A section.

I did the same thing. I flashed the .zip file from droid life forum and got a success message when I installed it through recovery and mine never bootlooped. I didn't get the gingerbread keyboard but it didn't bootloop either
Sent from my HTC Glacier using XDA App

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
I think you mean bootloader? You only have 1 recovery. If you flashed clockwork you no longer have stock recovery. Vol Down + Pwr gets you to bootloader or SPL where it shows S=off.

I did not flash the zip (sounds like an overkill to flash a zip for new KB). I ADB pushed both files and got a FC on multi-touch KB... oh well, I like HTC_IME better anyway

tenbeau said:
I sure intend to and I should have got on this forum before I even attempted to flash it. Right now everything seems fine except I cannot get into recovery only clockworkimode recovery. I am holding down the volume down button and pressing the power button at the same time and the device just reboots. Any ideas and what could be causing that? I am embarassed to say that my ignorance that pushed me to flash that zip is probably at the root of it. Any steps that I can take to enable me to get into stock recovery to check and make sure S=off?
Edit: Just pulled battery and sim card and than put them back in and the device went into stock recovery and s=off so I hope that all is okay and I did not create some ghosts that will show up when I attempt to flash a rom later on.
Click to expand...
Click to collapse
make sure fastboot is checked off otherwise you cant get into the bootloader. to make sure it is off go to: menu, settings, applications and uncheck fastboot. you're good to go then. to get into recovery, you can do it thru bootloader or by opening up rom manager and clicking on the "reboot to recovery" option

setzer715 said:
There are people experiencing the same thing in the Nexus forum. Personally I would stay away from anything that is not specifically built for this phone as its a completely different OS than Vanilla or Moto Droid or etc. etc.
Click to expand...
Click to collapse
the website was not specific enough. the port at the current moment is for motorola droid devices. they should have been more specific instead of saying any rooted 2.2 android phone. even if you do get it on your phone, its only going to force close every time you try and type something. thats what happened to me, so after about 24 hours i said **** it and removed it. swype in my opinion is better anyway. im trying to port the g2 swype to our phone so we can have a swype with a mic on the keyboard. oddly, ours didnt come with one.

Most ridiculous issue ever - please advise.

Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!

Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.

Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<

Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom

Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.

Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.

Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.

Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.

Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.

So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.

Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App

Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.

chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App

chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.

Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...

Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!

Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...

t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App

t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.

I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.

Problem after using goomanager

I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?

Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.

ok thanks for the help

cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012

Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.

If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.

I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.

~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct

Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.

cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?

Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.

Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read

Hard bricked GS4 i337, PLEASE HELP.

Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...

dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
In these situations its best to provide as much information as possible. What was your Baseband? MDL? MF3? if you have no idea what any of this means....then you shouldn't be trying to flash anything on your phone, atleast not until after doing a ton of research. Your best bet is to try and get it into download mode and ODIN back to a stock image. If you can't get into download mode then unfortunately there isn't much you can do. You can try going to a best buy and see if they can flash it for you. You should know that if you're on MF3 you CANNOT flash a custom recovery other than SafeStrap. Hope some if this helps.

This phone is super special with special needs.if you can get it into DL mode than SEARCH for the Odin files that are floating around here.this phone will teach you how to read again
Sent from my ATT S4 MF3 using Tapatalk

If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3

nash2000 said:
If the phone is new like you said, its a good chance the model is MF3. The custom recovery you installed doesnt work for that model which more than likely cased or helped cause your issue. If you dont know the model and your phone won't turn on...the model number is listed on the box (assuming you still have it).
The TC mentioned he can't obtain DL mode so I'm not sure how the using odin will help him since it won't recognize his phone. I'd try best buy and go from there. If you try to have it warrentied while pleading the "I dont know what happened" card to your carrier...just be warned, if they replace it and find out it was rooted or messed with than they will charge your account the full retail cost. I've had many phones replace via manufacturers warranty and that is the first thing they tell me. It can even be an issue if the screen has a tiny scratch. Hope it works out.
brought to you by my not so sexy GS4 MF3
Click to expand...
Click to collapse
He he can't turn it on best buy isn't going to help either. No one will be able to tell it's rooted either. Just take it back to where you got it and tell them it won't turn on. If it does turn on then you can Odin it.

dotkong said:
Hey guys.
Tonight I rooted my phone with the hopes of everything going smooth, it didn't. It was a nightmare rooting the phone itself.
I was trying to install TWRP recovery through Goomanager but that didn't work so I did it through fast boot and terminal emulator with the commands.
After it was done I rebooted my phone and it just went to a black screen with the blue notification light. Then the phone turned off. I can't turn it on at all nor can I get it to go into download mode.
I recently just got this phone, one week ago to be exact, as an early Christmas present and I haven't really even been able to enjoy the phone because I've had the flu. I just now recovered from it and this happens.
I am in a insanely bad situation.
Is there anything at all I can do? Please help me...
Click to expand...
Click to collapse
Pull the battery and wait a minute. Then replace it and see if you can use the correct key combo to get into recovery. If you fix it or get it replaced I suggest you do a lot of reading and learning before doing anything else. Good luck.

Bricked Galaxy S4
I've been there my self. The best and fastest thing to do now is go on the Wed and look up mobiletechvideo .
The guys are great. The turn around is fast.

Thread cleaned and closed.
XDA does not condone fraud in any form.