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
Related
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
My dumb ass just got a galaxy s3. Also have my note but mixed up the roms and put a s3 room on my note. Hard bricked it now. I ordered the Jtag service hopefully it can help.
They will fix it. Sorry.
Lol that sucks
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
aragoona said:
My dumb ass just got a galaxy s3. Also have my note but mixed up the roms and put a s3 room on my note. Hard bricked it now. I ordered the Jtag service hopefully it can help.
Click to expand...
Click to collapse
At least you admit you're dumb... lol jk. Hope it gets fixed.
Sent from my SAMSUNG-SGH-I717 using xda premium
Good luck man jtag will fix it. I am thinking about selling my note and buying gs3 , seeing as tho u have both do u think its a good idea or bad idea?
Sent from my SAMSUNG-SGH-I717 using Xparent SkyBlue Tapatalk 2
Return it for warranty and get a new one. I hard brick mine by accidentally flashing a kernel from the international note. Return it and said that the phone no longer turn on, and i think it was a hardware defect.
Sent from my SAMSUNG-SGH-I717 using xda premium
Save your money. I know of several people including myself that have tried this service. I got mine sent back to me as repaired but indeed was not. They did however apologize for the mix up. I just wouldn't do it again. My opinion folks. Please prove me wrong...
Sent from my SAMSUNG-SGH-I717 using xda premium
I did the same thing, and Telus just issued me a new phone after waiting for it to be shipped to that specific Telus store, this is only the case if its within the first 30 days of purchase.
Good luck, hope you get it sortted out, and if yours is a Canadian GN, let me know what you did, as I want to try a root again. Possibly.. ت
Model: SGH-I717D
Version: 4.0.4
Kernel: 3.0.8-perf
The process is quite easy ...
The key is reading for comprehension, and a good PC environment .
If you have those, you'll be rooted and done.
Here's the Canadian root info ...g
http://forum.xda-developers.com/showthread.php?t=1775263
XDA is no longer worth my time.
TimOster said:
You say it's bricked, but can you get into download mode?
Some say bricked when they can...you can recover from Kies IF you can get into download mode.
Click to expand...
Click to collapse
Or Odin ...
Strongly recommended ....g
I have an infuse with the wrong boot loaders on it that does get into download mode but i can't even get any computer to acknowledge it is even hooked up. So are you sure about this?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
screh172 said:
I have an infuse with the wrong boot loaders on it that does get into download mode but i can't even get any computer to acknowledge it is even hooked up. So are you sure about this?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Download mode would indicate that the device is able to connect, as the USB drivers, or at least a portion of them, are contained in the download mode program.
But if the data is corrupted or missing, due to software or hardware issues, then the process would fail.
So you get "no " COM " detection at all ??
If not ...it's a JTAG fix most likely ....g
update
I should be getting back my note any day. Hopefully it is fixed since the order status says complete. I want to sell the note and get a tmobile one.
aragoona said:
I should be getting back my note any day. Hopefully it is fixed since the order status says complete. I want to sell the note and get a tmobile one.
Click to expand...
Click to collapse
Let us know when it comes back if you would please ....g
gregsarg said:
Download mode would indicate that the device is able to connect, as the USB drivers, or at least a portion of them, are contained in the download mode program.
But if the data is corrupted or missing, due to software or hardware issues, then the process would fail.
So you get "no " COM " detection at all ??
If not ...it's a JTAG fix most likely ....g
Click to expand...
Click to collapse
i agree that if you can get into download mode, then youre good. if the pc doesnt see it, then its most likely a driver issue. even if you have "a" driver specifically for it, there may be a different one that you would need for it to be seen in download mode. Hard brick is when the phone wont turn on or its just black and there is no download mode and no recovery mode. download mode is where its at! dont mean to get off topic.........Let us know how the jtag goes!
fixed
Got back the phone and it was restored to stock. My unlock is still there. Great service with fast turnaround.
Excellent !!
could you place a "SOLVED" in your thread title ?
that will help others to find information faster..
Thank you !!....g
aragoona said:
Got back the phone and it was restored to stock. My unlock is still there. Great service with fast turnaround.
Click to expand...
Click to collapse
Wow, that's great. I stand corrected. Glad it worked out for you. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
aragoona said:
My dumb ass just got a galaxy s3. Also have my note but mixed up the roms and put a s3 room on my note. Hard bricked it now. I ordered the Jtag service hopefully it can help.
Click to expand...
Click to collapse
I used their services a few month ago and yes the phone was return restore to stock - also very fast turn around.
Okay, Im an ass so I say that up front. I flashed a bad kernel and I hardbricked my 5 day old galaxy s3 fro Tmobile. I took it to the local repair place that does JTAG repairs, which btw, does not work on the weekends. according to them the JTAG'ing takes 40 hours which I think is more because I kept calling and seeing if the phone was showing any signs of life. Anyone know how long the actual JTAG procedure actually takes cause 40 hours seems like a long time to me. Even after they said there was no guarantee that it would work and bring my phone back from the dead.
I am not new to rooting or flashing roms and kernels and things of that nature. So for the record I did not read first about bad kernels floating about so again Im an ass.
First mistake was flashing anything from this forum, this is for the international version ONLY.
Secondly a jtag should bring it back to life.
I'm not sure of the timeframe but 40 hours seems like a lot of time to do anything.
Sent from my GT-I9300 using xda premium
barbie1215 said:
Okay, Im an ass so I say that up front. I flashed a bad kernel and I hardbricked my 5 day old galaxy s3 fro Tmobile. I took it to the local repair place that does JTAG repairs, which btw, does not work on the weekends. according to them the JTAG'ing takes 40 hours which I think is more because I kept calling and seeing if the phone was showing any signs of life. Anyone know how long the actual JTAG procedure actually takes cause 40 hours seems like a long time to me. Even after they said there was no guarantee that it would work and bring my phone back from the dead.
I am not new to rooting or flashing roms and kernels and things of that nature. So for the record I did not read first about bad kernels floating about so again Im an ass.
Click to expand...
Click to collapse
Could you describe how exactly you hardbricked your phone? As far as I know hardbricking is pretty much impossible on the s3 and probably extremely rare (this is the first case I've heard about it).
Sent from my GT-I9300 using Tapatalk 2
Whoosh13 said:
Could you describe how exactly you hardbricked your phone? As far as I know hardbricking is pretty much impossible on the s3 and probably extremely rare (this is the first case I've heard about it).
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Flashing a kernel for the international version on a US version will send you on the road to brick town.
Sent from my GT-I9300 using xda premium
nodstuff said:
Flashing a kernel for the international version on a US version will send you on the road to brick town.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Ah sorry my bad, I read it again and saw its the T-Mobile version
Sent from my GT-I9300 using Tapatalk 2
Well..on youtube you can see how the jig works and it doen't take that long.
Sent from my GT-I9300 using xda premium
A kernel won't hardbrick a phone. If you flash a correct kernel it should boot. A way to brick it is to flash a wrong firmware from here. Cause the first thing being flashed on a firmware with odin is bootloader. Then you will have an expensive paperweight.
Sent from my GT-I9300 using xda premium
afaik s3 has separate kernel and recovery where flashing a kernel dosent touch the recovery , so practically it should not be hard bricked
If I were you I would approach to XDA forum first! where all the " DO DOES " happen!
are you 100% sure its bricked?
I dont really know about it, but from my experience bootloader flash and emmc bug are the only ways to hardbrick S3, flashing wrong kernel should make your phone unbootable, but shouldnt do a **** to your download mode (if flashed right, put under pda in odin), however if you put it under bootloader box, than it might flashed kernel on bootloader partition which deffinatly makes hard brick.
Sent from my GT-I9300 using xda app-developers app
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Phone is already at the servicecenter as you can read... So those questions do not add anything.
JTAG doesn't take 40 hours btw, takes a lot less.
Sent from my GT-I9300 using xda app-developers app
Ok, what I don't really undertand how all people got the idea that he's speaking about the US version. Yes, he said he got it from t-mobile, but if you buy in germany from t-mobile you'll get the international version also.
L
Why he or she doesn't give us the answer?
Really weird guy.
NEXUS 7
I bet its not hard bricked, it would just be soft bricked, if the correct firmware is flashed it shud be back to life...
Sent from my GT-I9300 using xda app-developers app
9Lukas5 said:
Ok, what I don't really undertand how all people got the idea that he's speaking about the US version. Yes, he said he got it from t-mobile, but if you buy in germany from t-mobile you'll get the international version also.
L
Click to expand...
Click to collapse
Because if you do some research and look at the persons other post on xda it is in the T-Mobile galaxy SII section.
Sent from my GT-I9300 using xda premium
I tried
sebarkh said:
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Click to expand...
Click to collapse
I tried the three combo until my fingers went numb I tried so many cables and computers and then I was like this thing isnt doing ANYTHING no vibration NOTHING. The JTAG didnt take the first time around so now they are still "trying" according to them ofcourse. I tried ODIN but it did not recognize my phone so that was no good. I tried everything I knew to try and that why I finally caved and gave it to the JTAG guys.
barbie1215 said:
I tried the three combo until my fingers went numb I tried so many cables and computers and then I was like this thing isnt doing ANYTHING no vibration NOTHING. The JTAG didnt take the first time around so now they are still "trying" according to them ofcourse. I tried ODIN but it did not recognize my phone so that was no good. I tried everything I knew to try and that why I finally caved and gave it to the JTAG guys.
Click to expand...
Click to collapse
Since its 5 days old have u tried warranty replacement?
help!
sebarkh said:
Can you enter download mode with 3 button combination?
Sent from my Galaxy SIII
Click to expand...
Click to collapse
this happened to my phone. and yes i can enter odin but idk what to flash!
I mean graveyard & doornail dead!
I know I read several had the big problem that I have now.
Seems like there were a fair amount of bricks. Our close calls anyway on many devices.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Why this particular weekend?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
sholsten said:
I know I read several had the big problem that I have now.
Click to expand...
Click to collapse
How did you brick your phone
sent from my lovely phone....hmmm wait its a tablet...waaa i dont really know.....im PARANOID NoW!
baudilus said:
Why this particular weekend?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I've been scratching my head on this all weekend.
King71st, I flashed Liquid JB on it and used Flap's kernel and it didn't work so good yesterday.
All the bricks I've seen is using the wrong rom for the device. There are many variants to most phones and they use a rom for the variant they
don't have
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
All the bricks I've seen is using the wrong rom for the device. There are many variants to most phones and they use a rom for the variant they
don't have
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Yes, but why so many on THIS weekend. I think a wrong ROM was accidentally posted as an i717 or something.
I bricked an i727 with a rom thru goo manager which I'm sure was not posted correctly. Will never use it or rom manager again. I Don't trust them.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
I bricked an i727 with a rom thru goo manager which I'm sure was not posted correctly. Will never use it or rom manager again. I Don't trust them.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
I liked it for named backups, but flashing CWM just to use the app is scary when you dont see your specific device listed.
sholsten said:
Yes, but why so many on THIS weekend. I think a wrong ROM was accidentally posted as an i717 or something.
Click to expand...
Click to collapse
I believe this to be true, I've flawed a ton of sh!t that was for another phone but in our forums. My 3 notes have proved un brick able in my hands (knock on wood).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
LittleRedDot said:
I believe this to be true, I've flawed a ton of sh!t that was for another phone but in our forums. My 3 notes have proved un brick able in my hands (knock on wood).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Mine had been unbreakable from when I bought it in June till yesterday.
sholsten said:
Mine had been unbreakable from when I bought it in June till yesterday.
Click to expand...
Click to collapse
How did you fix yours? Tried flashing abyssnote and liquidsmooth and it wont turn on. Torch blinks when you hold lock for about a minute.
I may have worded that wrong. I haven''t fixed mine. I meant it has been good since I bought it til I put Liquid JB on it Saturday afternoon. Mine is dead as dead can be.
any help fixingmine would be appreciated. searched but nada. desperately googling at the moment
scjsean said:
any help fixingmine would be appreciated. searched but nada. desperately googling at the moment
Click to expand...
Click to collapse
I'm just like you, but I believe Samsung is our only hope
scjsean said:
How did you fix yours? Tried flashing abyssnote and liquidsmooth and it wont turn on. Torch blinks when you hold lock for about a minute.
Click to expand...
Click to collapse
you flashed stuff for the Note 2; THAT is why you now have a brick
sholsten said:
I'm just like you, but I believe Samsung is our only hope
Click to expand...
Click to collapse
No jtag is your only hope.. Sending a brick into Samsung is fraud. You claim all responsibility when you give your phone root access, not to mention installing a 3rd party operating system.
True there are ways to revert everything to stock so that you can return it, but these are for people with legitimate hardware defects not to be abused by someone who can't man up and admit they made a mistake.
Ffs
STOP CONDONING FRAUD ON THIS FORUM!!!
THE REASON COMPANIES WANT TO LOCK DOWN DEVICES AND MAKE US NOT ABLE TO TO MODIFY ANYTHING IS THAT EXACT REASON.
TAKE RESPONSIBILITY FOR YOUR OWN MISTAKES AND STOP RUINING IT FOR THE PEOPLE THAT KNOW WHAT THEY ARE DOING!!
XDA does not condone Fraud in any way, shape or form. If you broke it and somehow pull the wool over their eyes, don't post it here.
We all take these risks when we flash the ROMs/Kernels/Mods. In doing so, we also should take the responsibilities as well.
I am still trying to figure out why "This weekend" as well as the relevance of this thread.
If you were me, what would you do in this situation? I had to get a replacement Note 2 and the replacement thankfully came with the VRALJB software installed. I deferred the update to L4 for 5 days.
Would you just root and unlock the bootloader now the easy way, or take the L4 update and do it the harder way? Would either way be beneficial or does it not really matter?
Thanks!
Go ahead and unlock/root. You don't have to do anything further if you don't want to and you never know how difficult it would be to unlock in the future.
When I purchased mine outright it had the older software. I used the jailbreak method and that worked like a charm.
Sent from my SCH-I605 using xda app-developers app
Either way. Just do it on the current software and save a step. Same end result.
Sent from my SCH-I605 using xda premium
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
kintwofan said:
As others said doesn't matter. Once you flash aROM you could just flash the LL4 radio and it would be the same as the OTA.
So I guess Odin didn't fix your last one?
Sent from the dark on a Note 2
Click to expand...
Click to collapse
im guessing it had a emmc failure that some have reported.
Well if you were me you wouldnt think about it and just root when I got my phone I didnt even sign into google first I skipped all that and was rooted within half an hour of owning my phone...Lol so root away mang
mine came with the ota last Saturday night, i waited til Monday to root just because I've always had htc phones, had to get familiar with touchwiz. took me 10mins to root after i couldn't take all the bloatware anymore
sent from my rooted SAMSUNG GALAXY NOTE 2...
droidstyle said:
im guessing it had a emmc failure that some have reported.
Click to expand...
Click to collapse
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
WizeGuyDezignz said:
Yeah guys, odin didn't fix it. I consider myself somewhat of a veteran with phones, rooting, etc. This time it stumped the hell out of me. Absolutely nothing that I did worked.
I want to thank you all for the help, info, etc. I will be back in business soon!
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
kintwofan said:
Ya man I've seen you around, I think from the s3 also. I knew you actually knew what you were doing that's why it was so strange Odin didn't fix it. Guess with this beast of a phone we get beast of bugs
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Yup, I had the S3 for a while and was over there. Yeah man, I was chatting to the developer of the Jedi ROM and I sent him the meta folder of the ROM that I flashed for beta testing and he saw some problems. He said it was touching some partitions that it shouldn't be touching.
Anyhow, I guess I learned the hard way to be careful of testing ROMs from devs that I don't really recognize.
Time to root this bad boy and get back in business lol.
Sent from my SCH-I605 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
kintwofan said:
Good idea. I thought with that failure it went black with no signs of life, but haven't read up on it. It was a strange that Odin of stock didn't fix it for him.... That's usually a guarantee unbrick
Sent from the dark on a Note 2
Click to expand...
Click to collapse
normally yes...i was just throwing that out there. something was corrupted since recovery was borked.