Related
To get to the point, people DON'T UPDATE YOUR VIBRANTS and T-MOBILE HANDLES THE ISSUE HORRIBLY! Obviously this is not a universal problem, but if you do happen to be one of the lucky ones that bricks their phone with the update there is no saving it (at least with the help of T-mobile).
I just got off of the phone with tech support and they were less than helpful. After the regular punching in numbers, talking to two different people, and trying to re-boots that everyone with half a brain have tried, they informed me that they would replace the phone but I had to PAY for shipping. While I realize this is a normal policy when it comes to random malfunctions, which may or may not have been the users fault, this is absolutely ridiculous when the problem is 100% their fault. Seriously, T-mobile ships a top of the line phone that has some major flaws and inactivated software (media hub), then breaks the phone with it's official update, and somehow this is MY responsibility to pay to get fixed? The rep even asked if I at this point wanted to add insurance so next time I wouldn't have to pay for shipping and if I wanted to pay extra for expedited shipping! They were trying to make an add-on sale while fixing an issue THEY caused!
That's not even the end of it, because I was so irritated they sent me to a "loyalty specialist" (who sounded like a used car salesman). He rambled on about how he would waive the shipping fee (he made it sound like he just saved my first born child). I told him I appreciated that but it didn't fix the fact that T-Mobile was not handling the issue well. When a large number of phones break from an issue originating from the provider they should either 1) have re-furbished phones (or even set aside new phones if necessary) to replace these broken phones as they come up or 2) offer free over night shipping of the replacement phone. He told me that these options were too expensive for T-Mobile, and that if I like I could sign up for either of their two insurance plans, as they would allow me to do an in-store replacement (he later noted that one of them was only available within the first 14 days of owning the phone...). I couldn't believe they were trying to another add-on sale! The best part being, I later called around to all my local T-Mobile owned stores and none of them have the Vibrant available for in-store replacement (and never have).
So the Cliff-Notes of my rant:
1) DON'T UPDATE YOUR VIBRANT
2) If you did brick your phone, make sure to complain and they should refund the ridiculous shipping charge
3) If you don't own a Vibrant and are thinking about it consider the following (Don't let it stop you, just consider it):
- Still on 2.1, when Nexus One has been on 2.2 for months (and the Galaxy S 2.2 official ROM has been leaked so it does exist in some form.) => Meaning updates are super scarce and extremely late.
- T-Mobile is selling a good phone with many flaws, and their first attempt to fix it bricked many phones (do a google search I am not the only one).
- While it may be better than other companies, T-Mobiles customer service is FAR from flawless
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors.
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Had the same problem but this is a pretty fix using Odin.
If you install an update from an OTA T-Mobile should be held responsible
I don't know about you guys but when you have been a customer for 10+ years, T-Mobile will pretty much suck your balls.
Either way, if you guys rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Yeah why warranty the phone when you can just ODIN and fix it yourself? Do a xda search. If you're gonna use xda to complain at least use it to solve your own problems as well. Unless your phone is hardware locked it is 100 % fixable.
Sent from my SGH-T959 using XDA App
starkiller86 said:
I hate when people mess with their phones then get angry at a company for "breaking" their phone. Im running stock rom with root and also got bricked, but, I manned up and knew I was in the wrong and accepted what happened. I didn't put the blame on TMo, because completely untouched vibrants that I was aware of had no issues with this OTA. If you added functionality to it after the fact that it wasn't originally on there before when you initially purchased it; then its YOUR fault that it bricked, NOT T-mobiles. Take some responsibility and stop crying.
Click to expand...
Click to collapse
P.S. My phone was completely stock (so please don't mention how I did this with a lag fix, etc.). I waited at least 15 mins before I pulled the battery, before which I had noted the T-Mobile sound starting without the animation (seems like a timing issue or something). And finally, I realize this is a duplicate post to many others but I want people to find this info (not be at the bottom of a really long thread) to get the word out how T-Mobile deals with their errors
Did you not read that part?
I bricked two stock Vibrants with the update. The second one failed during Mini-Kies update and was hardware locked.
It is a known issue according to the Tech guy that I spoke to while getting my replacement.
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
No, no.
This happened to me, I had a rooted phone I had uninstalled the inflight internet, etc on it and hadn't overclocked or anything like that. Phone kills itself. I went to the tmo store and they only make you pay for shipping if you take the overnight option.
PROTIP - DON'T ASK FOR EXTRA SPEEDY SHIPPING AND THEY'LL PAY FOR IT.
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
watcher64 said:
I guess this is just an example of "store your pictures on the external SD card"
Then if you brick it you can still get your pictures back ....
Click to expand...
Click to collapse
Word. That's one of the first things I did when I got the phone and was playing with the features. Switched it from phone storage to memory card.
Sorry to hear you lost photos.
Protip: Pay the damn overnight shipping fee...it'll be deducted from your bill (flex pay) which makes it free: )
Sent from my SGH-T959 using XDA App
Here is the business side
If I am T mobile every time some person has a problem and I offered free shipping, the Every moron would be shipping the device back for Any problem. Way way costly, so that is not going to happen. If you Really believe the phone is factory defective then, pay the shipping and move on. If you messed with it at all then the burden to resolve is yours and be honest about that. Remember the reason people are in here is to customize the phone and improve it. Like the XDA mantra sez.......... It is not just the result... but the journey....
Like one of the other posts stated:
If you rooted it, then that takes the fault from T-Mobile to you. You changed the phone. The update was designed for a pristine un-edited Samsung Vibrant, if you changed anything in the system by rooting or flashing it is your fault for changing the equation. T-Mobile is NOT at fault for your actions.
Gr8gorilla said:
First phone wouldn't power on after failure, second phone was hardware locked so un-fixable.
Click to expand...
Click to collapse
There is a hardware lock fix now, you really should flash that before you do anything else. Yeah, you run the risk of bricking with the hardware unlock, but it's probably a safer bet than flashing away.
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
If you Odin it with the JI6 update, you might still be able to get a working system out of it. Worth a shot to see if you can get it without having to flash to stock first (which will wipe).
With all the time you spent with tech support, you could have found the thread that delineates how to fix your phone and update through odin. Its very easy and, frankly why be on a developers forum when you are not willing to tinker around a bit.
Sent from my SGH-T959 using XDA App
dechire said:
so i guess we are just SOL for the data on the phone? I just lost an entire vacation of pictures. I had not had a chance to root this phone either. this is ****ing awesome.
Click to expand...
Click to collapse
As long as the phone still powers on you can still use ADB Pull and save the data from the /sdcard folder. This update isn't a totally bricking the phone (at least it didn't mine) just making the display and inputs not work. To quote Billy Crystal: "He's only MOSTLY dead"
Odin was really simple to reflash the stock ROM and then I was able to do a nandroid restore from there.
The T-Mobile OTA update left my phone only booting to the vibrant screen, but it was a pretty simple fix with Odin. The hardest part was getting the proper drivers installed in windows!
Mini kies wouldnt even let me update,so I rooted and flashed bionix 1.8,works great.**** tmo.
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
mr2t32 said:
Fyi to the people with hardware lock. I did the update on my gf's phone which was hardware locked and it failed. The phone would only boot to the vibrant screen. The good news is the ota update unlocks the hardware because her phone is able to get into recovery and download mode even thought the update failed. The point is don't worry if ota fail on you because you can just use odin to fix it since it unlocks the download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If the update even gets that far...
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Don't be heartbroken just yet. This just happened to a friend of mine with his Note. I'm sending him your way. He's working today so I doubt he can get to you right away but I'm pretty sure he has the answer you need.
Sent from my SAMSUNG-SGH-I717 using xda premium
Have you tried accessing the phone with odin to see if it shows up there?
did you install CWM prior to flashing? try the three button combo to boot into recovery
did you backup prior to flashing ICS?
erikistehsex said:
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Click to expand...
Click to collapse
Some ROMs can damage the device's onboard flash. Surprisingly the Note is one of the few devices that you can actually physically break by flashing the wrong ROM.
erikistehsex said:
Hey guys, first post, first real major issue I've encountered well rooting a phablet.
I have a ATT galaxy note, yesterday I rooted it and installed the Saurom ROM, everything was a breeze, I decided to try out ICS, I accidentally installed Criskelo onto the device before finding out it wasn't okay for the ATT note.
It hung on installing the rom itself and so I removed the battery imagining I could just revert to Saurom til I found a new ICS rom. But after I interuppted the ROM from installing, I get NO POWER! No download mode, nothing whatsoever on the screen =[ I'm ultra sad, best solution I find for the note is possibly a USB jig but I don't know if it will bring me back from this...
ANY HELP IS GREATLY APPRECIATED! I'm sitting here with a bricked note and a broken heart.
Click to expand...
Click to collapse
You may need to contact mobile tech videos and get jtag unbricking service.
A bad flash happened to me in my first week of owning the phone so I was under the 30 day return policy with AT&T. I told them I was updating apps in the market, it got super hot, shut off, and would not power up.
They couldn't get it to turn on either, for obvious reasons, and they exchanged it no further questions asked. Hopefully your still in the return period.
Sent from my Icey G-Note Beast with XDA Premium 0_o
I done the same thing..odin should pick it up kust flash att recovery
Sent from my SAMSUNG-SGH-I717 using XDA
I'm sorry to say you probably have a hard brick on your hands. There's more info in this thread. I did the same thing myself. studacris's answer is the only option, you'll need to send it to someone who can do a JTAG repair on it, or you need to hope it's under warranty and send it back to AT&T and tell them that it just plain broke.
All notes are under warranty from Samsung still. They are for a year of purchase date. note has not been out a year.
Normally when I've had a a phone brick on me or a friends phone when out of the 30 day period, I would call 611 and have them send me a phone and when I received the new one I would mail the bricked one. It wasn't a big issue since the phones have manufacture warranties. Now they opened a device support center near buy and you can go and get a new one that same day.
Sent from my SAMSUNG-SGH-I717 using XDA
question for the OP's question, Samsung has that flash counter on the phone, I'm assuming with a bad flash like this it doesn't go up. But does it? And it if does, would Samsung be able to tell what happened? I know Samsung has a hard stance on flashers. To OP, I did the same thing, and I resorted to getting the JTAG thing done, the few places I've came across won't charge unless they can fix it. And they only charge like $50.
I tried jtag. Waste of money. They could not save my phone, plus they charged me $30 for looking at it.
Not to mention I lost out on my shipping.
Sent from my SAMSUNG-SGH-I717 using xda premium
The last resort is to try a Jig to force download mode. If that fails, you are done. You can look on your PC in the Device Manager. In there it will show you an "state" when you connect the device trying to get into Download Mode. Google that state. I am guessing you are getting the bad one which at this time is a device exchange.
Hi There,
I did search around and didn't find a specific answer to this, I did see someone was looking to modify some binary values but no confirmation if it worked. Anyways I have successfully used many roms on my phone and tablet but last night after using CWM and the rom flashed successfully I rebooted the device and then nothing. Blank screen. Nothing happens when I charge. Used the wife's battery fully charged to see if it would help. Tried three-button boot method. All nothing. It's just dead.
Now I'm guessing I must have missed a step somewhere and fully take responsibility for what happened, and would pay for a repair - but can Samsung even repair a device in this state? I talked to an agent on the phone last night and openly told them what happened and asked how much it would be to repair and he said he couldn't give me any information without sending the device in. This is my mistake to get my phone in this state so I don't want to sneak my way into a warranty replacement. Is it worth the wait as Samsung can fix this, or should I just buy a new phone?
Cheers and any information is much appreciated.
www.mobiletechvideos.com
They can repair bricked phones for a very reasonable cost. Samsung may see it and void your warranty. I'd go with Mobiletech. I've heard they do great work on bricked phones.
The above advice is good, assuming your device is truely hard bricked.
However, from your description, it's hard to figure how you bricked it. A true brick usually happens when an attempt to flash a bootloader partition gets interrupted in the middle. There are possibly other ways, but it's not very easy, actually. So, is there absolutely no sign of life? Nothing you can do will even get a flicker of light on the screen? You cannot enter download mode, or recovery mode. You have tried all of these? No point in spending $50 on a jtag repair if you can recover the phone yourself.
I would also be interested in a complete description of the steps that led up to the problem.
I'm a little embarrassed to post this but don't want to waste anyone's time. It is totally bricked but I know why.
I just noticed I downloaded a rom from the i777 forum, and my device is a i727.
Oooops! Guess I'm learning a valuable $50 (plus shipping) lesson.
Thanks for the help, my phone is off Mobile Tech.
Still might not be hard bricked. Mine did this a few weeks ago for no reason. Had been running fine then wouldn't boot one day. Wouldn't boot at all. Could not get into recovery.Nothing. Only thing that worked was connecting through Odin. Had to then flash original Gingerbread. Phone then booted fine. I have since rooted again and I'm now dual-booting SHOstock and Rootbox. Try Odin first.
SPatMobile said:
I'm a little embarrassed to post this but don't want to waste anyone's time. It is totally bricked but I know why.
I just noticed I downloaded a rom from the i777 forum, and my device is a i727.
Oooops! Guess I'm learning a valuable $50 (plus shipping) lesson.
Thanks for the help, my phone is off Mobile Tech.
Click to expand...
Click to collapse
I don't really know much about the I727 architecture, but I seriously doubt if your device is hard bricked. You should still be able to get into download mode via the normal procedure (maybe, or if not with a usb jig) for your phone, and then flash a good I727 rom, I believe. There are no bootloaders or partition information, or param files in any of the I777 roms, as far as I know, so there's really not much of anything that can do serious damage.
Try getting in to download mode by With your phone off and unplugged. Enter download mode by pressing and holding the power and volume down buttons and plugging in the USB cable before the lights blink. I don't know it will work on i727 but worth a try..GL
This is a good thread to help you read all you can....
http://forum.xda-developers.com/showthread.php?t=1652398
creepyncrawly said:
I don't really know much about the I727 architecture, but I seriously doubt if your device is hard bricked. You should still be able to get into download mode via the normal procedure (maybe, or if not with a usb jig) for your phone, and then flash a good I727 rom, I believe. There are no bootloaders or partition information, or param files in any of the I777 roms, as far as I know, so there's really not much of anything that can do serious damage.
Click to expand...
Click to collapse
Interesting. Well I suppose it is possible I had a legitamite hardware failure completely unrelated to the software issues. I did some searching around for hardware failures instead and found some very similar cases to this.
Exactly what happened. I downloaded the wrong rom, rebooted in cwm, wiped, then flashed the rom. It went successfully and I rebooted from cwm then during boot right after the samsung logo all the lights went off and the screen went black. I left it like this for about 45 mins to an hour and had dinner just in case it was still doing something. The battery was fully charged at the time I started the procedure, and I have tried using the wife's battery to make sure mine wasn't dead. My battery also functions without issues in her phone. I had done this successfully multiple times on my phone before and tablet, and successfully flashed two or three different roms on my wifes phone last night.
I tried every suggestion mentioned, and followed the guide as well. There is no glimar of life. If this is hardware I might be wasting my money with Mobile Tech but I suppose we'll know for sure soon. Phone is shipping off today.
Have you tried a jig?
Sent from my SGH-I777 using xda app-developers app
you're doing the right choice, mobile tech is your best bet
OP got his answer. And his device is an i727. Let's let this one die before we attract trolls
Sent from my SGH-I777 using Tapatalk 2
Ya good idea
Sent from my SAMSUNG-SGH-I777 using XDA
In case anyone was interested it looks like the device was a hardware failure.
"Unfortunately, I was not able to repair your device. The device's onboard EMMC controller was in a non-responsive state. It is advised to try out warranty replacement if possible or to search for a parts device and use it's mainboard for the swap."
*edit - I tried to use the thanks meter for everyone, but thanks for all the help!
Never was really a samsung fan until I got my i777. Blackjack? wth was that? Browsing with opera was off the hook though so the phone grew on me. Now I tried simply flashing a different i777 kernal because ICS constantly freezes and the phone bricks? Sent it to Mobile Tech Videos.... EMMC is in non responsive state for me too wtf Samsung? Had my nexus one twice as long and flashed twice as many times and its still rockin. Now will definitely think twice before going Sammy.
paulfrankie said:
Never was really a samsung fan until I got my i777. Blackjack? wth was that? Browsing with opera was off the hook though so the phone grew on me. Now I tried simply flashing a different i777 kernal because ICS constantly freezes and the phone bricks? Sent it to Mobile Tech Videos.... EMMC is in non responsive state for me too wtf Samsung? Had my nexus one twice as long and flashed twice as many times and its still rockin. Now will definitely think twice before going Sammy.
Click to expand...
Click to collapse
Did you wipe in ICS's stock recovery before flashing that different kernel? Because there's a well known brickbug with the I777's stock ICS kernel, where if you use it to do anything before you flash custom kernels, it'll mess up your EMMC and brick your phone. If this is what happened to you, I would suggest you do more reading before flashing anything again; different phones operate differently, and even if you're a pro at flashing stuff on a galaxy nexus that doesn't mean squat when it comes to flashing an I777. I don't mean to be harsh or offend you, I just want you to know that reading more is always a good idea, and that there's a chance that it wasn't Samsung's fault you wound up with a bricked device.
He could always try the jig to kick it into download mode. Read up about it. It may save you some money.
HTC = Hate The Consumer
Mobile tech will fix ya but in all seriousness, phones are way different from model to model. As previously stated. Read a lot before doing anything. may Atrix is way different than this phone,.
Sent from my SGH-I777 using Tapatalk 2
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Based on the information we're currently provided with, I think it'd be safe to say you're screwed for now. Why you would even try to root a device that doesn't currently have any rooting methods is beyond me. You should definitely read up before you try anything you're not sure of.
The only other option you'd have at this point is taking the phone into Verizon, showing them the screen and telling them that this is how it has looked since it came out of the box. Although it's a lie, and you bricked it out of your own neglect, the reps can't really turn you away.
Can you return it?
Sent from my SCH-I605 using xda premium
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
MedicMillan said:
I did some research, and nobody had any negative things to say about the rooting process, especially with all the videos and forums on it. I searched for how to root the Samsung note 2, versus the model number, which is different for different carriers.
Click to expand...
Click to collapse
Every carrier is different. You must be new here.
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
You will need to wait until the boot loader is unlocked to flash a rom, only way I can think of.
MedicMillan said:
I am new. I have rooted phones before, but never had this problem. Would it be an option to install a custom rom like Cyanogen until there is a public release of the stock firmware?
Click to expand...
Click to collapse
At this point in time, you can't flash anything, you can't root, and there are no recovery images to return to stock with. You either have to wait it out, or try to exchange it at Verizon.
You can exchange, they will not know the difference
Sent from my SCH-I605 using Tapatalk 2
Just take it to Verizon play dumb and get it replaced. It's within the 14 days so it will be swapped on the spot. They wont/don't care what's wrong with it.
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
DaRkL3AD3R said:
The suggestion of just return it to the store, they won't notice, is a really **** move and I'm not saying that in defense of Verizon. I'm saying it that it is things like that that in the end cause more harm to the end user than good. They up costs and add charges, create obscene policies, etc. It may not negatively impact you immediately, but when multiple people do this all over the country it adds up.
Click to expand...
Click to collapse
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
MedicMillan said:
Great. I, like a dumbass, decided to try and root my new phone without a backup plan. I have had no luck using the XDA video, and now I'm stuck with the "Please select recovery mode in Kies" screen. Kies doesn't recognize it, and I have no way to restore the stock ROM. Is my only option to wait until a stock firmware ROM is released, like it was for sprint?
Click to expand...
Click to collapse
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
bork.it.consulting said:
Check the development section. There is a leaked ODIN .tar file that you can flash. It is a prerelease, but at least you will have a functioning phone until a proper root/unlock solution is found.
Click to expand...
Click to collapse
This Odin file fails. It will not flash. Someone was trying to flash it last night with the same screen you are on.
just odin the stock image in the dev section and you will be back up and running...do not I repeat do not anybody try any root methods for the other gn2 variants!
http://samsung-updates.com/device/?id=SCH-I605
if it fails then your screwed until the latest odin image is release, which im sure wont be too long.
Nit3mare said:
I have to say I agree 100%. If people just used common sense, or read up a bit, situations like these could be entirely avoided.
Click to expand...
Click to collapse
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Check out this link for a fixed brick....
http://forum.xda-developers.com/showthread.php?p=34862234#post34862234
mrlaigle said:
I'm not saying that everyone should go flash happy, attempt to root without knowing what they are doing destroy their phones and take them back to Verizon then rinse and repeat the process. But there have to be a few that are a tempting to get root for everyone else there is bound to be some hard bricks. Should they be out 700, and that's kinda harsh.
Click to expand...
Click to collapse
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Nit3mare said:
But with a little reading in the correct forum, people could avoid owning a $700 paperweight. It's really not that difficult, and any issues that arise from lack of research are due to their own ignorance. I can't feel sympathy for anyone who flashes blindly.
Click to expand...
Click to collapse
I'm not disagreeing with you. If you do not know what you are doing or if this is your first time you shouldn't be attempting to root an un rooted device. But there will always be those guinea pigs...
Sent from my SCH-I605 using Tapatalk 2
This is exactly the reason why everyone else who follows commense is punished with locked bootloader.
iwhenever i bootup my phone turns into colors then turns white and my computer wont recognize it. i am running blackstar x and am rooted. if anyone can help me i'd appreciate it. oh and i cant go into recovery but can access odin.
So just flash a rom with odin.
rangercaptain said:
So just flash a rom with odin.
Click to expand...
Click to collapse
Agreed....
and once the new image is pushed over to the device, you will need to boot once, then reboot into recovery and wipe all caches and data.
Otherwise, you will have dirty flashed, and you will have stability issues....g
I've never used odin I am reading up on it now as far as I can tell you can't flash zip files so do you know any good roms I can use for my galaxy note?
izdabombest1 said:
I've never used odin I am reading up on it now as far as I can tell you can't flash zip files so do you know any good roms I can use for my galaxy note?
Click to expand...
Click to collapse
Odin is used to push stock image files...
And they can be found in the super thread, at the top of the general section.
concentrate on getting a stock build running properly first, then we can worry about custom builds later.
Edit:
This is the thread, and inside will be the file you need:
Read carefully, and take your time on this...g
http://forum.xda-developers.com/showthread.php?t=1506330
gregsarg said:
Odin is used to push stock image files...
And they can be found in the super thread, at the top of the general section.
concentrate on getting a stock build running properly first, then we can worry about custom builds later.
Edit:
This is the thread, and inside will be the file you need:
Read carefully, and take your time on this...g
http://forum.xda-developers.com/showthread.php?t=1506330
Click to expand...
Click to collapse
well I ran loading and it came up with firmware upgrade in encounter in issue please select recovery mode in kies and try again so I will do the next I guess. but I can never get kies and the phone to connect.
can't get kies and phone to connect and i followed all the steps. what gives?
update: after 16 hours with kies decided to give odin one more shot on a different computer. she's back up and running! now to decide with what rom to go with. LOL. thanx guys for the help.
Kies is a fickle pig. Sometimes you're using the wrong cable or usb port.
rangercaptain said:
Kies is a fickle pig. Sometimes you're using the wrong cable or usb port.
Click to expand...
Click to collapse
wow this is unbelievable when it went to reboot and never came back on and it makes the Microsoft Windows keep asking you need to format a disk in drive D before you can use it so itslight turning itself on in 3 seconds in 3 to 4 second intervals. then the computer started loading drivers for a Qualcomm CDMA technologies MSM now where would that come from?
evidently from what i have gathered through many hours of reading and studying, i have hard-bricked my device. like i reported in previous post my computer will recognize it in short intervals. it continues to attempt to download drivers for Qualcomm CDMA.....but disconnects before finishing installing. one time ofter unplugging it left an icon that read.....oh i forget but i immediately looked it up and all reports from xda says that means a hard brick. called service provider and they are sending out new one but what happens when they recieve it and see that it has been rooted? i would really like to keep trying to save the phone i have. any suggestions?
If you are using files from our section, you must have the SGH-I717 device.
You mentioned CDMA. And although present in the chipset, this version of the note is a GSM device, and runs on the following networks respectively.
AT&T, BELL, ROGERS, TELUS, STRAIGHTALK, and carriers in far eastern countries....
Please link us the information on the Odin file you used to repair the device.
It appears you may have inadvertently pushed the wrong image. Perhaps for the N7000 ???
If that's the case, then the device will be hard bricked, and can be repaired using a JTAG repair service.
After you post the rom information, we will know for sure.
A general search for JTAG information will link you to several threads that talk about the service.
I'm sorry you are in this predicament, but for $50 U.S. dollars the device can be repaired.
I do not condone sending the device back under warranty, as it technically is not a defect, and is not the fault of Samsung or the carrier.
Good luck to you Sir.....g
gregsarg said:
If you are using files from our section, you must have the SGH-I717 device.
You mentioned CDMA. And although present in the chipset, this version of the note is a GSM device, and runs on the following networks respectively.
AT&T, BELL, ROGERS, TELUS, STRAIGHTALK, and carriers in far eastern countries....
Please link us the information on the Odin file you used to repair the device.
It appears you may have inadvertently pushed the wrong image. Perhaps for the N7000 ???
If that's the case, then the device will be hard bricked, and can be repaired using a JTAG repair service.
After you post the rom information, we will know for sure.
A general search for JTAG information will link you to several threads that talk about the service.
I'm sorry you are in this predicament, but for $50 U.S. dollars the device can be repaired.
I do not condone sending the device back under warranty, as it technically is not a defect, and is not the fault of Samsung or the carrier.
Good luck to you Sir.....g
Click to expand...
Click to collapse
first off I would like to say thank you for all of your guys help.how do I send a link from the Odeon file that I used?and I am pretty positive that it is hard brick.I do not want to be dishonest in I want to resolve this on my own.oops I mean with your help of course.
Simply copy/paste the link into your next reply.
then we can see the source for the file.....g
okay i took your advice and sent the replacement back. your right if i can't spend $50 to save my $600 phone i shouldn't start on this road. however as thorough as i usually am i am not very organized. i started installing upgrades and little modifications for my friends and family as a little hobby. then other people started asking me for this and that, so i would help them. so, i have downloaded a LOT of things to my computer (ROM's, MOD's,, etc.) for different android phones and from different forums (now i only use software from xda) and i rarely delete or uninstall anything. needless to say my computer started to look like a teenagers bedroom. i have now started to organize things so i can get a better grip on what i'm doing so i can take this more serious. with that being said i can't remember exactly what file i used to flash with Odin. is there some kind of log that is automatically kept by Odin?.....i have decided to try to use a phone jig to get my phone to at least turn on. is that a wise move? i am studying all there is available on the ins and outs of phone jigs. if that fails i will send off to be JTAG'd. if there is any advise or info that you feel i could use please send my way. thank you.
oh one more thing i do not own any windows phone software or cdma software, but i was connected to my friends nokia lumia 822 hot spot when i flashed my phone. and that's when it went dead and popped up as a cdma devise. could that have anything to do with it? sounds farfetched but so does alot of things that we are capable of doing nowadays.
The jig doesn't work for the note 1, so it's off to the JTAG guy.
ouch! can u plz send me a link i cant seem to find any. thank you.
www.mobiletechvideos.com
izdabombest1 said:
okay i took your advice and sent the replacement back. your right if i can't spend $50 to save my $600 phone i shouldn't start on this road. however as thorough as i usually am i am not very organized. i started installing upgrades and little modifications for my friends and family as a little hobby. then other people started asking me for this and that, so i would help them. so, i have downloaded a LOT of things to my computer (ROM's, MOD's,, etc.) for different android phones and from different forums (now i only use software from xda) and i rarely delete or uninstall anything. needless to say my computer started to look like a teenagers bedroom. i have now started to organize things so i can get a better grip on what i'm doing so i can take this more serious. with that being said i can't remember exactly what file i used to flash with Odin. is there some kind of log that is automatically kept by Odin?.....i have decided to try to use a phone jig to get my phone to at least turn on. is that a wise move? i am studying all there is available on the ins and outs of phone jigs. if that fails i will send off to be JTAG'd. if there is any advise or info that you feel i could use please send my way. thank you.
oh one more thing i do not own any windows phone software or cdma software, but i was connected to my friends nokia lumia 822 hot spot when i flashed my phone. and that's when it went dead and popped up as a cdma devise. could that have anything to do with it? sounds farfetched but so does alot of things that we are capable of doing nowadays.
Click to expand...
Click to collapse
A clean and reliable PC environment is at least as important as the proper files.
Maintenance is king on any file structure...
And while I feel badly that your device was damaged, I applaud your choice in sending back the replacement device.
People forget that when these phone manufacturers take back damaged product under warranty, they increase the price of new devices to maintain the same profit margin.
We pay at the register for others mistakes.
Again, thank you for your honesty, and integrity in this matter.
And don't worry, the device will return quickly, and will run like new.
We are always willing to assist users here through the lessons we have learned, and it becomes much more gratifying when we know the caliber of the user we help.
You have earned high marks for your choices today, and stand with the most reputable Members of XDA ....IMHO
Should you need anything upon the return of your device, consider it done ...g
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app