Related
ok so i was running SH 3.9.1 and decided to go back to stock so i odined back to jfd and then tried to update with kies and now my phone will not even turn on anyone have any clue on what i need to do or if there is anything i can do
a)did you flash gingerbread bootloaders? If you so and you didn't flash back the froyo bootloaders before using keis your probally f***** up your phone. Need a jtag
b)if you didn't flash any bootloaders just call tmobile and tell them keis f***ed up your phone
c)you could just lie to tmobile and tell them keis f***ed up your phone
seconded... (holds up blank phone)
same issues here, odined JFD, all was working fine, went to update via Kies, and it completed, rebooted, and did not come up after waiting over a half hour
no lights, can't get to download or recovery modes..
Yes you need a jtag, I recently had the same problem. PM connexion2005 and he can hook you up for $50.
Sent from my Nexus S using XDA App
cannonbomb said:
Yes you need a jtag, I recently had the same problem. PM connexion2005 and he can hook you up for $50.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thanks I just contacted him.
Well luckily I was able to get a replacement phone. But thank you to everyone that helped.
pathbas said:
Well luckily I was able to get a replacement phone. But thank you to everyone that helped.
Click to expand...
Click to collapse
Kies has a history of causing bricks FYI.
Sent from my GT-I9000 using XDA Premium App
lol yeah i see that now and funny thing is i was actually coming from your rom EB.
The "Kies" effed up my phone has got to be the #1 over used excuse. Probably used more often then it actually does, but IT DOES! so its easy to get by with. I'd have to imagine in this situation its bootloader related. People should honestly fess up when they bork up their own device and pay the fee to get it jtaged. Just my 2cents.
As the old Chinese proverb goes:
"You break, You buy!"
I agree with you on that and it probably was my fault it messed up but im also broke otherwise i would of gone that route
one of these days there gonna catch on
Wow..... you guys.... bootloaders for vibrant are backward compatible..... even still.... you could have built a custom jig for $1.19, some scotch tape, and an old car charger. read the stickies yo.... I've had bad bootloader flashes at least 20 times now with odin and my cheap little jig has me back in dl mode in seconds.
Majin_X said:
Wow..... you guys.... bootloaders for vibrant are backward compatible..... even still.... you could have built a custom jig for $1.19, some scotch tape, and an old car charger. read the stickies yo.... I've had bad bootloader flashes at least 20 times now with odin and my cheap little jig has me back in dl mode in seconds.
Click to expand...
Click to collapse
I might try that next time but I just got my new phone in now so time to root again and try a different rom or go back to the old one not sure yet.
Majin, you have not had a bad bootloader flash yet. You will know when you do and that jig won't help...
Sent from my GT-I9100 using XDA Premium App
So your saying there is something worse than the "phone-pc!" Sign? Honestly I thought that was as far as it would go. I mean..... what's worse than "fail" while flashing boot loaders?
Sent from my GT-I9000 using XDA Premium App
Majin_X said:
So your saying there is something worse than the "phone-pc!" Sign? Honestly I thought that was as far as it would go. I mean..... what's worse than "fail" while flashing boot loaders?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Oh yea there is definitely a worse step than that screen. It's called NOTHING. Literally your phone is worthless at that point without a good JTAG technician. I see it over 100 times a month... . Not trying to be a smarty just letting you know that there are scenarios in which the JIG is worthless and you will need someone to JTAG there phone. Please remember me if it happens to you as I can fix that although I would never wish it upon you...
pathbas said:
I agree with you on that and it probably was my fault it messed up but im also broke otherwise i would of gone that route
Click to expand...
Click to collapse
Here that! College is to damn expensive! Better be worth it in the end.... Because this life of poverty sucks
so i tried to unzip a file with a backup assistant apk on it. when i boot into my phone with cyanogen cm7, im getting constant popup messages like adw.launcer and rom manager and android market etc has stopped expectedly. please try again. the only option i get is to click okay. i can't do anything else. is there a way to whipe my phone? i can't even boot into clockwork recovery because i can't get past my lock screen. any help would be amazing. thanks
Pull the battery. Boot into hboot by holding volume down plus power Untill the bootloader screen appears. Select recovery. Restore backup/reflash ROM.
Sent from my HTC Thunderbolt
just figured it out before you posted that - im an idiot. thank you.
ElectroFetish said:
just figured it out before you posted that - im an idiot. thank you.
Click to expand...
Click to collapse
It's all good. Stuff happens and I've never met anyone who has never had a duhh moment. lol
Sent from my HTC Thunderbolt
If your phone is bricked, go buy a new one. By definition, a bricked phone cannot be fixed. But then again, I suspect you don't know what "bricked" means.
mike.s said:
If your phone is bricked, go buy a new one. By definition, a bricked phone cannot be fixed. But then again, I suspect you don't know what "bricked" means.
Click to expand...
Click to collapse
Job well done on a post that contributed nothing and was just an attempt to make someone feel stupid.
Sent from my HTC Thunderbolt
JBO1018 said:
Job well done on a post that contributed nothing and was just an attempt to make someone feel stupid.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Truly bricked phones won't make it past the boot animation.
He needs to stop freaking out and follow instructions.
This is a PERFECT example of why people should NOT root until they know what they're doing.
Sent from my Synergized Thunderbolt via XDA Premium App
Ok so i restored my stock backup because i needed to do a fresh install of unnamed. now when i turn the phone off it comes right back on and when i try to go into recovery it just continues booting up. what have i done and what do i need to do?
Even with phone on you can press and hold power and both volume up and down. Keep holding it and it will boot you into recovery.
Sent from my páhhōniē
there is no need to go to stock to do a new rom flash
The problem is fixed but now i face a new dilemma. When i go to turn the phone off it comes right back on. Even with a hard shut down. Also happens when i pull the battery and put it back in. It will turn on again by it self. I am on unnamed 1.3.1 with the blue monkey theme. Any ideas?
what if maybe your power button is tweaked?
I guess warranty wouldnt cover it because I'm rooted?
Sent from my SAMSUNG-SGH-I777 using xda premium
MWilkenson said:
I guess warranty wouldnt cover it because I'm rooted?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
If you revert the root using entropy rom and a jig you can return it for warranty work undetected.
Sent from my SAMSUNG-SGH-I777 using xda premium
k4zyn said:
If you revert the root using entropy rom and a jig you can return it for warranty work undetected.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Alright thanks. Ill look into it. me being an android noob is not helping the situation lol.
Sent from my SAMSUNG-SGH-I777 using xda premium
MWilkenson said:
Alright thanks. Ill look into it. me being an android noob is not helping the situation lol.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
+1
True
jk
Be still true
Sent from my páhhōniē
Ok I'm honestly baffled here. My battery life has been terrible. Here's what has been done recently. two days ago I restored my stock back up and flashed unnamed 1.3.1. Noticed my battery was dying very quickly. So I went into cwm. Wiped data, cache and davik cache and reflashed unnamed 1.3.1. My battery is dying no exaggeration about 10% every 40-50 minutes. In addition to all this...my phone wont stay turned off. It turns it self on after about 2 seconds. Ugh please help me.
Sent from my SAMSUNG-SGH-I777 using xda premium
Wow. That's pretty rough. I say go back to 100% stock and see how it goes. If it still is dropping that fast your battery may be bad.
Sent from my páhhōniē
The phone screen turning back on so often says "rogue app" to me.
I really appreciate the replys. I'm going to take one more day and see how it goes...if its still not working right ill be buying a USB jig and learning how to get back to stock.
Sent from my SAMSUNG-SGH-I777 using xda premium
gr8hairy1 said:
Wow. That's pretty rough. I say go back to 100% stock and see how it goes. If it still is dropping that fast your battery may be bad.
Sent from my páhhōniē
Click to expand...
Click to collapse
Also when you say go back to 100% stock...do you mean like restore my stock back up? Or am i going back to 100% stock unrooted? Or what? I've seen a couple threads, I'm just confused so I apologize. If you could guide me in the right direction I would appreciate it.
Sent from my SAMSUNG-SGH-I777 using xda premium
MWilkenson said:
Also when you say go back to 100% stock...do you mean like restore my stock back up? Or am i going back to 100% stock unrooted? Or what? I've seen a couple threads, I'm just confused so I apologize. If you could guide me in the right direction I would appreciate it.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Use Entropy512's return/unbrick to stock package. Or I have an Odin3 OneClick Downloader of his package is you prefer. It's a little easier. See the link in my signature.
There is no such thing as a backup of 100% stock. To make a working nandroid backup, you need to already have a custom kernel installed.
creepyncrawly said:
Use Entropy512's return/unbrick to stock package. Or I have an Odin3 OneClick Downloader of his package is you prefer. It's a little easier. See the link in my signature.
There is no such thing as a backup of 100% stock. To make a working nandroid backup, you need to already have a custom kernel installed.
Click to expand...
Click to collapse
Thank you so much. I will check it out when I get home. So after I do that I'll still be rooted? Or do I need to root again before I flash a rom again? I promise im almost out of noob questions.
And I might try getting a new battery to fix the other problem. I'd hate to have to send my phone in for warranty
EDIT: ok i just looked at your link with odin 3. say i use the one without root. i would essentially be bone stock out of the box correct? and from there i could just start over, use the guide on how to root, etc.?
Sent from my SAMSUNG-SGH-I777 using xda premium
MWilkenson said:
EDIT: ok i just looked at your link with odin 3. say i use the one without root. i would essentially be bone stock out of the box correct? and from there i could just start over, use the guide on how to root, etc.?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
The only difference between the two packages is one will give you root while the other will not. If you go with the one with root you will be 100% stock aside from root. I only recommend going 100% because then you'll know it won't be any rogue apps draining the battery or issues from a custom rom. If you get the expected battery life stock rom has then you'll know the battery is good. If it's lower than what is usually is for stock rom most at&t stores will replace the battery on the spot for you.
So no benefit of going with the package without root unless you're taking it back to at&t.
Sent from my páhhōniē
ok i just went back to stock + root. about to flash the unnamed rom again. I cannot express how appreciative i am for everyones help and for being patient with me. im slowing learning as much as i can. thanks everyone!
Pay it forward
Sent from my páhhōniē
indeed i will sir.
although i do have another question..sorry. Ok so when i first rooted i became acustom to CWM and flashing unnamed rom themes in that. After i used odin3 one click it gives me the android system recovery 3e and ive never seen it before. can i still flash unnamed through this or do i do something different?
edit: ha nevermind i found it http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
sorry.
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know much about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Sorry but looks like its gone. Have seen a few ppl able to recover with mskips fix but only if theyre able to turn phone on.
DeathGrind said:
Hello all, I was walking my friend through rooting his phone over Google talk. He rooted all went well a few days later he wanted to Rom it. He made a mistake and flashed the international omega Rom on his US ATT samsungi747. His phone is now dead. No way to get into recovery or download mode. Just dead. Bricked. What can I do to help him? As I am partially responsible cause I was helping him. I did not know about the Rom he was flashing.
I was reading about a possible fix with a jig but can not find a jig for.the Samsung i747.
Please any and all advice would be greatly appreciated.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
A compatible jig may be your only solution if you can't get into download mode manually. A jig would force the phone into download mode, once in download mode you'd be able to flash the stock AT&T firmware through Odin.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
DakiX said:
In the blacked Screen try flash with Odin.
Sent from my Hybrid Note using Tapatalk 2
Click to expand...
Click to collapse
he's in oregon and I'm in california. I think he is freaking out. But he did say ODin was not recognizing the device.
ADB? ^^
Sent from my Hybrid Note using Tapatalk 2
Error 1. Not reading
Error2. Wrong section... not reading
If he cant get cwm or screen to show something who knows what he did...fix: there is none get another device and read before u do stupid stuff.... u can't expect us to fix lack of reading or not knowing what ur flashing....
im on my phone. expect terrible typos.
DeathGrind said:
oh no. Its his first android phone. He only had it about a week. I can't believe this. I feel so bad for him.
Thanks for the reply
I have been looking for a jig that is compatible with the att samsung galaxy s3 sgh-i747 and had no luck. Do they exist?
Click to expand...
Click to collapse
A jig is a jig the one I bought for my captivate works 100% on gs3, get the jig put into phone if don't boot into download mode, hold down power button with jig still in if that don't work ur screwed .... your better off trying make ur own jig ( YouTube it ) cause if the phone runs out of battery and won't charge then u have another issue...
---------- Post added at 12:38 AM ---------- Previous post was at 12:27 AM ----------
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Just cause "we " can't turn it on don't mean they eventually can't ..
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Moh_Jay said:
Btw you maybe able to save your friend
http://forum.xda-developers.com/showthread.php?t=1743757
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Moh_Jay said:
Has anyone ever tried just returning it and saying it randomly died? If they can't turn it on then there's no way to tell it's rooted
Only joking
"All this knowledge is giving me a major brainer!"
Click to expand...
Click to collapse
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Some people actually have there phones just stop working. Happened to my friend that had a Samsung galaxy nexus, stock unrooted. Just died. There was nothing I could do to fix it.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
Thanks man! I ordered him one. Hopefully it will work. He's also going to make one tomorrow.
A huge thank you to all the people that provided helpful information and friendly advice.
I was actually expecting more ridicule, but it was minimal. . I know we messed up, but I never knew you could "brick" a phone from flashing a Rom.
Anyway thanks again guys! I will keep you posted on if the jig works or not.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
If you didnt know a rom could brick a phone you shouldnt be flashing period. Theres always ALWAYS bold letters that says this may brick your phone an or we are not responsible if this breaks your phone... no one with there first android should be flashing till they know android smoothly... *sigh*
Usually 90% of the time your always able to get into recovery mode. From what I've read this only happens when flashing the omega Rom. People make mistakes.
I've rooted and rom'd 100s of phones, and never not been able to get back to recovery.
Sent from my ADR6400L using Tapatalk 2
SiNJiN76 said:
The morning I was picking up my phone...a dude walks in and says that his phone doesn't turn on anymore after having it a week. I thought to myself..."he flashed an international ROM...what a douche".
Click to expand...
Click to collapse
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
jcbofkc said:
The good and bad of brand new phone on the market. Some people do not like reading and want to be handed the solution.
Noobs....read.....read...read some more....go to bed....get up...read some more...have cookies for snack time....read some more... and then read some more... and for the love of GOD....read some more before flashing anything!
I mean that in the nicest way, becasue I have questions on a semi-regular basis also.
Click to expand...
Click to collapse
If ppl read things 95% of there questions would be answered. The other 5% could be found by google
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
DeathGrind said:
I understand telling him to read. And he did so for about a week. He succesfully used odin to root his phone. A few days later he said he wanted to Rom, and asked me how to do a proper back up with titanium backup. I ran him through the backup procedure.
I mean I totally thought that if he made it through the rooting procedure that he was good to go. Rom'ing has always been to me something fairly easy, and if something went haywire, just boot to recovery.
I've had people ask for help that flashed an incomplete or corrupted download, but have always been able to at least power the phone on, or at the very least have it recongnized in adb.
I have been reading and googling about a fix, but information seems minimal on this current circumstance. So I reached out to the community for advice.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Personally i wait a bit to root rom a brand new phone... however ive never had a issue untill i fried my gs mesmerize so im a lil hesitant
Yeah, this is the first serious issue I have ran into in almost 3 years of mod'ing android phones.
Sent from my ADR6400L using Tapatalk 2
I was running Scotts CleanRom 4.25 on my s3 and flashed Saberkernel.13.4 and it bricked my sg3.. will not boot into recovery.. the kernal works on my note 2.. but just thought I would post to prevent others from making same mistake. I done the battery pull. and can only get a red light to come on , on the top left of the device. Even tried a second battery I have from wife's s3.. same thing.. and it is not recognized with usb chord either. Had to ship it back to Samsung...
ronschuck said:
I was running Scotts CleanRom 4.25 on my s3 and flashed Saberkernel.13.4 and it bricked my sg3.. will not boot into recovery.. the kernal works on my note 2.. but just thought I would post to prevent others from making same mistake. I done the battery pull. and can only get a red light to come on , on the top left of the device. Even tried a second battery I have from wife's s3.. same thing.. and it is not recognized with usb chord either. Had to ship it back to Samsung...
Click to expand...
Click to collapse
Aaaaand that's why you don't flash anything that's not made specifically for your phone, unless you know it's compatible. Sorry for your loss though. Can you get into download mode? Guess it's too late now, if you already sent it back, but I'm sure you tried to Odin back to stock..
Sent from my Inverted Beans ROM @ 240 DPI
sleevasteve said:
Aaaaand that's why you don't flash anything that's not made specifically for your phone, unless you know it's compatible. Sorry for your loss though. Can you get into download mode? Guess it's too late now, if you already sent it back, but I'm sure you tried to Odin back to stock..
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
yes.. i tried Odin several times.. I could never get the phone to show up on my pc.. reinstalled drivers. rebooted..couldnt get into download mode for anything.. after a day of trying everything.. I said.. OK... I quit... good thing is .. it was my backup phone that I flash with as a hobby.. still have my note 2..
ronschuck said:
yes.. i tried Odin several times.. I could never get the phone to show up on my pc.. reinstalled drivers. rebooted..couldnt get into download mode for anything.. after a day of trying everything.. I said.. OK... I quit... good thing is .. it was my backup phone that I flash with as a hobby.. still have my note 2..
Click to expand...
Click to collapse
Kinda like me I still use my S3 as a backup phone for streaming music on Wi-Fi/hotspot, playing games, hooking it up to my tv, and flashing ROM's when I get an itch, and don't feel like changing my current Note setup. I really like the Galaxy Mod ROM for the S3 mainly because it has Multiwindow, which I can no longer live without!
Sent from my Inverted Beans ROM @ 240 DPI
So, you flashed a Note 2 kernel that is for an Exynos SoC to the SGS3, which is a Qualcomm SoC? I'm not sure why anyone would even think to try this in the first place, so I'm not sure why you felt the need to warn everyone. Also, this is exactly the reason VZW locks the bootloader, because people do things like this and then get warranty replacements.
As for fixing it, you should be able to, but you likely need a USB jig to force it into download mode, then a full Odin tar plus a PIT file so you can re-partition properly.
Exactly what imnuts said. People sending their phones back for warranty replacement due to mistakes THEY made themselves is exactly why verizon is locking bootloaders and why rooting voids your warranty. If people took responsibility for their own actions, the rest of us wouldn't have to pay for the consequences.
Should change the title to I bricked my phone by flashing a kernel that was not made for my phone. The kernel did not brick your phone you did by making a really bad decision.
This thread is bad and you should feel bad, too.
Sent from my Galaxy Nexus using xda app-developers app
This may be the most ridiculous thread I've seen in a long time. But only the fact instead of paying for his mistake he thinks some how is Samsung responsibly, but how completely ridiculous he was to knowingly flash a note 2 kernel on a s3.
op why do you think there are different sub forums for phones and even carriers. You're probably one of the people who flashed an international ROM too. ...Then sent your hard bricked phone in for warranty
Sent from my SCH-I605 using Tapatalk 2
<Facepalm>
Sent from my Galaxy Note II
I can't even comprehend how you failed this hard. I feel sorry for the dead phone.
Sent From My Galaxy Note 2
This gave me a good healthy laugh. Thanks OP :thumbup::beer:
sent from my Note 2
And this is why most people should not be allowed to root and ROM phones....
Sent from my SCH-I605 using xda app-developers app
What the hell? Everyone did my job for me??
Late to the party today, twice!
Sent from my SCH-I605 using Tapatalk 2
so you guys get all high and mighty and tell the guy he screwed up. I think he knows. cut the guy some slack. we've all made mistakes flashing. some bigger than others. he knows what he did wrong. no need to be complete jerks. this is why xda sucks now.
Sent from my SCH-I605 using xda app-developers app
fearjego said:
so you guys get all high and mighty and tell the guy he screwed up. I think he knows. cut the guy some slack. we've all made mistakes flashing. some bigger than others. he knows what he did wrong. no need to be complete jerks. this is why xda sucks now.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Uh forgetting to check MD5 can be more than just screwing up. Do that with an HTC hboot that is corrupt and no soft brick for you!
Sent from my SCH-I605 using xda app-developers app
nosympathy said:
Uh forgetting to check MD5 can be more than just screwing up. Do that with an HTC hboot that is corrupt and no soft brick for you!
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Well true and I guess doing it with a radio on my note would be pretty bad to.
Sent from my SCH-I605 using Tapatalk 2
Instead of criticizing, just help the person. We all make mistakes. Just find the Odin stock zip of your device. Here's a fix: http://forum.xda-developers.com/showthread.php?t=2065470
kintwofan said:
Screwing up is forgetting to check the md5 and soft briking. Flashing a kernel made for a different phone ON PURPOSE then, instead of paying for it himself, decides it's somehow Samsung fault. Oh and then posting here like it's the kernels fault is ignorance!
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Lol you realize he sent the phone back 6 mos ago?
AJ Bryant said:
Instead of criticizing, just help the person. We all make mistakes. Just find the Odin stock zip of your device. Here's a fix: http://forum.xda-developers.com/showthread.php?t=2065470
Click to expand...
Click to collapse
Sent from my SCH-I605 using Tapatalk 4