Related
I've been rooting and working with custom roms for a long time (couple of years at least). I started with WinMo, and since I got my Evo the day they came out, I've been doing it in Android. I can also use ADB, and can typically recover from pretty much any problem on my Evo. (not claiming to be an expert) HOWEVER...
A couple days ago I loaded the latest Fresh ROM on my phone, and ran out the door while it was loading. Got in my car, the Evo started to reboot after applying the ROM, and zzzZZZIP! The thing went dead. And I mean REAL DEAD. The led which usually shows the charge level as not lit. I pulled the battery and tried to turn it on after replacing it. No go. Nothing when holding down vol while pressing power... nothing. When I got home I tried a wall charger, still no light, no boot, no drive with !, nothing. When the wife got home, tried her Evo's battery... same kind of nothing. USB connection to PC gives no adb access, no fastboot access,... you guessed it, nothing.
Sprint doesn't replace it if you didn't buy the warranty. Called HTC, of course they'll happily replace it, as long as it wasn't rooted. So I have a two part question.
Firstly, because I want my Evo back NOW! No, two days ago! LOL Is there a way to fix it?
Second, if I send it in, is there a way for them to know I rooted it?
Your help would be greatly appreciated.
Have you tried a different battery? That one may be fried. Just a suggestion.
Sent from my PC36100 using XDA App
fdb8231 said:
Have you tried a different battery? That one may be fried. Just a suggestion.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks for the quick response! Yep, tried that. I thought maybe I had one of the USB port issues that didn't allow me to charge the phone, but alas, my wife's fully charged battery couldn't boot it (or do anything), and my battery worked fine in her Evo.
I also disassembled the phone to check solder connections both on the battery connector and the usb port... both looked totally fine.
Well, if you pay insurance on it you could always accidentally lose it and report it lost or stolen.... that's what I would do, but that's just me....
___________________________________
Yup.... The ones yoe momma told ya about.... Bad Seed Customs!!
Yeah, I'll weigh my options. I think I'll send it to HTC first. I really don't think they can read the internal memory in this condition. I think it is probably fried. It is too late for the Sprint TPE (warranty), but but I might be able to finagle a squaretrade warranty. It will take time though. I thought about having a friend list it in eBay as a buy it now for what a new one costs, buy it from him (he give me my money back), and wait whatever period squaretrade requires, and file a claim. They're great, and I should have bought a squaretrade warranty from day 1. I've had it on the two phones prior and had to use it on one of them. They're easy to deal with and cheaper than any other options. Plus, its more flexible since they don't replace the phone, they issue you a refund for it (which would give me the option of switching phones, not that I would).
mrsato said:
I've been rooting and working with custom roms for a long time (couple of years at least). I started with WinMo, and since I got my Evo the day they came out, I've been doing it in Android. I can also use ADB, and can typically recover from pretty much any problem on my Evo. (not claiming to be an expert) HOWEVER...
A couple days ago I loaded the latest Fresh ROM on my phone, and ran out the door while it was loading. Got in my car, the Evo started to reboot after applying the ROM, and zzzZZZIP! The thing went dead. And I mean REAL DEAD. The led which usually shows the charge level as not lit. I pulled the battery and tried to turn it on after replacing it. No go. Nothing when holding down vol while pressing power... nothing. When I got home I tried a wall charger, still no light, no boot, no drive with !, nothing. When the wife got home, tried her Evo's battery... same kind of nothing. USB connection to PC gives no adb access, no fastboot access,... you guessed it, nothing.
Sprint doesn't replace it if you didn't buy the warranty. Called HTC, of course they'll happily replace it, as long as it wasn't rooted. So I have a two part question.
Firstly, because I want my Evo back NOW! No, two days ago! LOL Is there a way to fix it?
Second, if I send it in, is there a way for them to know I rooted it?
Your help would be greatly appreciated.
Click to expand...
Click to collapse
Are you certain the battery isn't fried? Also, make sure the SD card is fully seated and secure. With the battery OUT, connect your EVO to it's power supply and then reinsert the battery. Sometimes, after doing so, you will see the LED light up. If not, try again. If it still does not, try getting to the Hboot screen by pressing the down volume button while also pressing the power button.
I am pretty sure I tried that. I pulled battery while plugged in, put battery back, no difference. The first thing I thought was that it was a bad battery connection, because the phone has never worked with the battery out, but plugged in. The battery MUST be in to work. So I disassembled it to check the battery and USB connection solder points, and they look fine.
I called a reputable mobile phone tech and he said he has seen this a few times with rooted Android devices. He said he doesn't think they will be able to read the internal memory, or probably won't go through the effort it would require to (pull the internal memory out and put it in a reader).
Just pull all your root files off the SD card cause that is a dead give away that it is rooted.
Sent from my PC36100 using XDA App
Insurance
Going through HTC is going to be a waste of time. Their turn around time is 30 days... And thats if they dont discover the rooting and therefore actually replace it.
Your best bet is sucking it up and paying the $100 deductible for Asurion insurance... If you order on their website www.phoneclaim.com they will overnight for free. However I have heard of it being back-ordered, in which case you will either wait, or be one of the lucky guys who gets a brand new one.
In regards to them seeing your internal memory, I would say its 50/50. They can recover that sort of stuff, but at the same time, HTC is way more lenient with rooting/mods than other manufacturers.
Good luck
toddlmr said:
Just pull all your root files off the SD card cause that is a dead give away that it is rooted.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
As it turns out, when you send your phone to HTC, you have to pull your battery cover, battery, microSD card, and any other "accessories" you have off, and keep them. They only want the phone without any of these items. I asked the guy, "you don't want me to ship the batter OR even the cover with the phone, but separate?" He said, "no, they are yours to keep. if you send them to us, they will not be returned." LOL! If they replace the phone, I'll have spare parts! Yaaay! I left my screen protector on it, in case they can fix it, they won't scratch it. Love my Evo y'all!
Yah the same exact thing happened to me when i first got my evo (the first day it came out). Absolutely no sign of life, but got it through best buy and just went back with no insurance or anything and she gave me another one on the spot.
Yeah if it won't even power, they won't bother. You are straight unless by some miracle they actually get it working.
TEP is a godsend.
I'm supremely surprised no one has popped in to say "WRONG SECTION AMAGADWTFBBQ!"
sekigah84 said:
I'm supremely surprised no one has popped in to say "WRONG SECTION AMAGADWTFBBQ!"
Click to expand...
Click to collapse
That would be so barbaric and elementary - so many capitals and so much hostility!
To the OP:
Wrong section, jackhole.
It will probably cost you $35 without the insurance. If one store doesn't work, try another.
Yeah, just smash it on the floor and claim a new one
$100.00 ..thats it.
Where to post this?
I had a feeling this was the wrong place to post this, but not sure where else to do it. General maybe?
SORRY! ;-P
I wouldn't have a problem if an admin moved it to the right place.
Do did you make a decision to send it in?
teh roxxorz said:
Do did you make a decision to send it in?
Click to expand...
Click to collapse
Yeah, with fingers and toes crossed.
Well, I don't think they'll find out. Cuz I'm in engineering, and they could try to overvolt the phone [in an attempt to turn it on] but too much a risk of frying the circuits. Also no sdcard so they can't see your files...and way too much work to disassemble...so I think you're good.
Thanks man, that really is reassuring. I'm kind of on pins and needles over this. I can't afford ANYTHING, much less to buy another phone (I was laid off Jan 1).
I've been desperately trying to learn to program in Java, for Android. Both should provide me with more flexibility financially. I'd rather work as a contractor than FTE any day, but sysadmin type work is hard to find these days. I didn't expect to enjoy programming as much as I am, which is a pleasant surprise. Java isn't so hard. ;-)
I hope to get my Evo replaced under warranty. Then I hope to get more income by the time the new Evo 3D comes out! Not to sideline this thread, but what do you guys think of that thing? I'm also wondering if the new Evo View 4G would work as a phone replacement, just using Google Voice to replace cell service. Most new cars have bluetooth built in, and otherwise can use a bt headset (even stereo headphone type), so you never have to hold it to your head anyway.
Sorry, I guess I spaced posting my results. The did not know out had been rooted. They just replaced the motherboard and sent out back.
Unfortunately, they downgraded me from hw version 003 to 002. There were also two soft key lights out and I sent it back. Even though I complained about the version difference they still put another v2 in it. I called US public relations and came close to getting a hwy v3 board in but in the end it didn't happen. All they really care is that they made the device work.
Moral of the story is, if your Evo is dead-dead, send it to htc, and now you know what to expect.
I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?
So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.
I hope that you have the warranty from the carrier!
gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.
!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....
ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk
android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.
volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.
Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch
Forum Noob here, I was using my Galaxy S3 (Wind) and all of a sudden the screen went black and it turned off. Something similar had happened a couple hours before and the phone wouldn't turn on through the power button so I simply took out the battery and put it back in and it worked. Then when it happened for a second time I tried the same thing but to no avail the phone stayed dead.
So far I've tried:
Using another GS3 Stock Battery
Tried getting into download and recovery mode
Tried charging it (I do know that the battery is charging since I checked it on another phone. The red light is not on but it turns on when I take out the battery and then plug it in. After 20-30 seconds of battery insertion the red light goes away and is completely unresponsive all that time)
Tried Keeping the battery out of the phone for a couple of hours (Suggested by a friend)
Also Tried connecting it to a pc, and it only connects when I keep the battery out. When it finally connects it tries to install drivers for "QHSUSB_DLOAD" but fails.
I have no idea what's happening to my phone and I would like to get it fixed as soon as possible. After some searches I've narrowed down to either a Hard Brick or a Sudden Death Syndrome but it doesn't completely match with all the characteristics of either problem. I greatly appreciate any help and I would like to know what exactly the problem is and what my best viable option.
Thank you.
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Don't know why, but it's bricked. But you mentioned it started working at one point when you put the battery in. So if you take it out, then put it back, does the phone automatically try to turn on by itself?
Qhsusb is a definite indicator of a brick, but if your power button is faulty it may have caused the brick by rebooting over and over without ever fully booting up. Basically causing corruption somewhere.
There's a debrick thread stickied in development, but if the button is also faulty it may not help for long.
Sudden death is only describing a problem the international models had after release. Doesn't apply to ours in that way.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
TheSoldierDude said:
Yeah, when you put the battery back in it doesn't do anything. Also I don't think the power button is faulty I mean it's been working fine for the last year didn't really give me any problems.
Click to expand...
Click to collapse
Only reason I suspect the power button is you mentioned you couldn't get it to turn on using the button, but removing/replacing the battery worked. And it can work perfectly and then fail out of nowhere. So goes when you have plastic parts! But lots of people have had issues with this button recently.
Wasn't trying to convince you that was the problem, just letting you know it's a potential culprit.
But if you think it's ok, then try to use KAsp3rd's debrick thread and see if that gets you going again.
Sent from my SGH-T999 using Tapatalk
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
ssingh0247 said:
If it's completely dead then it's most likely hard bricked. My phone just got hard bricked so you will need to buy a JIG of Ebay. If it's not that then try reflashing your ROM or re rooting it. If none of that works then just take your phone in too wherever you bought it from and have them fix it. Oh a JIG is a small USB that will re write it and force it into download mode.
Click to expand...
Click to collapse
Since they are seeing the QHUSB_DLOAD (which is technically a hard brick) a simple USB jig wouldn't work, however they can attempt to use my recovery method. It's at no cost and just takes some time and reading.
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Remove and reinsert battery. If it turns on by itself, you are probably right about the button.
Sent from my SGH-T999N using Tapatalk
You're Right I believe
tomy1986.nt said:
Your phone in stock rom ? If stock rom that is suddenly dead mean bad emmc on the logic board with my experience.
Click to expand...
Click to collapse
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Nope
P06o said:
When you attempt to restart your phone, does anything come up at all? I've been having issues over the past week, culminating in a device that won't charge, and won't complete a boot sequence. I get as far as the Samsung splash screen (and occasionally the first snippet of the ROM's splash screen) and then....a black screen and a quick buzz. Then the whole process repeats. In my case, I believe it's the power button.
Click to expand...
Click to collapse
Nothing happens at all.. its completely dead, simply a paper weight.. a very bad one of sorts
TheSoldierDude said:
I went to a Samsung service center and they told me the motherboard had to be replaced.. I did some searching and found this http://forum.xda-developers.com/showthread.php?t=2178484
I've come to the conclusion that it was indeed a bad emmc (Yes, I was using stock ROM).. Any thoughts?
Click to expand...
Click to collapse
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Thank you
Perseus71 said:
If it indeed is a Bad EMC then it should be In Warranty Repair as Samsung does offer that. If you didn't have Insurance that is.
Click to expand...
Click to collapse
Nope.. xD 3 months off warranty, and yes I got it repaired from Samsung.. Motherboard was replaced, $300.. :|
Thanks to everyone helping out though
I can't believe I didn't know about these forums before :good:
Samsung Galaxy S3 died-black screen
my s3 gone black,its not getting turned on.there was red light(indicator) for some time before i tried to restart but when i tried to switch on. it's completly died,i am not getting any display.i have purchased in UK, unlocked using it now in India.some guys told me it would because of motherboard issue (if i replace motherboard it in India will it work normal,is there any possibility?)how to fix it?please give me some solutions.
screen not working
Hi all. In my s3 the red light is flashing fast. Also the screen is black but it works. Also the phone works and I can receive phone calls. Every few minutes the screen turns on for a sec and goes off again. I can feel the vibration when I touch the screen. Pkease help me.
Thanks
hard bricked
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
syben7 said:
same issue, totally dead, short red light when connecting usb be, tried this http://forum.xda-developers.com/showthread.php?t=2439367 but nothing happens when holding power button, any possible help?
Click to expand...
Click to collapse
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Answered in the other thread. Just fyi, its best to only ask your question once, in one thread. It gets messy and confusing when different things are mentioned/attempted in different threads for the same issue.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
yea, sry about that, was actually trying to get 10 posts in so that i could go post in the dev thread concerning this, gonna check out the method you sent, thanks a ton man!
STUCK
Well my s3 (us cellular r530u), has no boot but has a red led without the battery. Is there a debricking procedure? And if so..where can i find a debrick file.
There is for us. But you need to be in Sprints forums. Theres nothing for your device here, and I dont know what they have over there. Good luck though!
Sent from my SGH-T999 using Tapatalk
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Top5a said:
The best part about spending 30 minutes typing a post is having your browser crash. Anyway, if you have any further questions because this is going to be a bit brief, let me know.
My background: Fairly well-versed in Android, custom ROMs, flashing, rooting, doing development work on Android, reading directions, decent google-fu and RTFMing. But I really need help on this one. The phone in question is my primary phone, which I actually like to keep as stock because I don't want anything mucking up on it. It's 20 months old (daily usage), running stock 4.1.1, which was rooted about 17 months ago with cf autoroot, which I needed for development purposes. For the past 10 months, I have been using an extended aftermarket battery, because when traveling and thusly using navigation, gtranslate, lots of messaging, and whatnot with a bright screen whilst outdoors, I was tired of having my phone leave me without a communications device at 8pm.
Recent changes to phone: Several weeks ago, before another bout of traveling, I did my usual *#197328640# perso256 disable (one of the reasons that I like keeping my phone at 4.1.1), and voila -- carrier unlock.
What happened: Things were going swimmingly for a few weeks, when one day, I was out and about, typing something into google translate, and the screen just went black. It was early midday, and the phone was at 90% battery (extended battery life ftmfw). Every now and then, when doing serious multitasking (and, mind you, since the early days of owning this phone, as well as through the entire life of my GS1, which still works, by the way), my GS3 would occasionally reboot of its own accord. I thought nothing of this, except it just being a hallmark of samsung phones, and a minor inconvenience, at worst. This time, however, it failed to power back on. I removed the battery, held in power button in an attempt to discharge any residual power, and put the battery back in. Nothing. Panic. No ssung logo, no vibration, no lights, nothing. Just the black screen staring back at me. There was no moisture, and no trauma to the phone... nothing, save for a ridiculous sinking sensation.
Symptoms: Phone completely unresponsive. I tried a charged stock GS3 battery, and the symptoms are the same. If I plug the phone in without a battery, the led lights up red for a time, and that's it. Even though I haven't modded this phone at all, with the exception of the rooting almost 2 years ago, I tried everything I could think of and read online. vol up + power + home. vol down + power + home. Leaving the battery out for a while. So much reading through these forums and some others online. When I plug it in in windows (even though I primarily use linux), I get the QHSUSB_DLOAD problem, so I do not think it is a problem with the power button? Or maybe the power button can be permanently depressed or something that would cause this? Anyway, I've installed QHSUSB_DLOAD windows drivers, but don't want to start flashing things until I know there isn't another longshot option to get this to work. I even loaded up linux and ran pblclear, which allegedly attempts to knock HTC phones out of being stuck in QHSUSB_DLOAD mode. Didn't work, but figured it was worth a shot, and seemed relatively harmless.
Why I don't even know if it's SDS: The reason I'm asking this is because I'm completely at a loss. SDS appears to affect i9000s after 150-200 days, OR when people incorrectly flash a ROM, or something happens during flashing or modification. My phone is an ATT i747 has been fully operative for 600+ days, and I haven't done any flashing, rooting, whathaveyou in nearly two years (and it was just that simple autoroot that I ran once).
What I'm wondering: I really want to get this phone working, because of hundreds of images, notes, data, etc. that I have accrued over the past few years. Most of my videos and larger files were on my sd card, but literally hundreds of memories and works in progress that I would do insane things for were saved to the phone. I'm an idiot for not backing it up, but I wasn't doing anything to the phone, so wasn't expecting such a catastrophe. Will JTAG work? What about a debricking microsd image? Most of the ones I can find are for 4.1.2 or 4.1.3 -- are there any for 4.1.1? I'm nearly certain 4.1.1 is my version, because IICR 4.1.2 and 4.1.3 don't even have the perso256 disable menu, and it's why I had not upgraded to them. It seems like the microsd rewrites would wipe the contents, and then I would have to quickly attempt a recovery on the data? Or have there been any cases with similar failures that are something else dying on the board? To be perfectly honest, if it appears to be an issue with the board, it's not beyond my ability to perform BGA rework and remove the emmc entirely, and transplant it onto a new board, but I would ///really/// like to avoid that.
Thanks for reading... :angel:
Edit:
Additional information: I forgot to mention that I have found pages such as this samsung-galaxy-s3-sgh-i747-i747m-repair-dead-boot-1755452 [I'm afraid you'll have to google it because I can't post links if you want to look TT^TT] which have files that say, for example, "Samsung SGH-I747 Repair Boot Supported" if using JTAG. So, if there aren't suggestions about how I can fix my phone with an sdcard unbrick, or something else, does anyone know whether or not doing a boot repair will unbrick a phone without wiping the ROM itself? Thanks again~~
Click to expand...
Click to collapse
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
thorur said:
same thing just happened to my 20 month old att s3.i unlocked the bootloader and flashed a twrp recovery.the phone was on 4.1.1 and rooted.
now just a lifeless phone
Click to expand...
Click to collapse
Did it die closely after the unlocking/flashing? Or a long time after? Or was the unlocking/flashing an attempt to save the phone? Ever get it fixed? I'm so anxious!
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I never heard of qualcomm chips doing this. There is a app called emmc brickbug check on the market though it won't be of much use to you now.....but it allows you to check the mem. Controller chip and check if its a "sane chip" and allows you to probe the memory for any bad sectors.....its really quite a nice app
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
Well, thanks for the input! Makes me feel a better hopefully the emmc isn't completely fried. I just really want my files, and am continually irritated at myself for having been so stupid to not make backups.. although I have phones from 10+ years ago that have never completely died in such an unexpected manner. It's quite the agonizing wait for a JTAG programmer to come in the mail. If I can manage to get it to boot from SD, which I haven't been able to do so far, do you think it's logical for me to simply reflash the bootloader/CWM, then attempt boot? It shouldn't erase files, right?
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
You can try a bootloader and recovery flash which might yield results.....and the plus side of that is that it won't wipe the memory unless you format the /data partition or you do a full Odin restore with ROM kernel and everything
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I've also searched everywhere for a debrick image for 4.1.1 AT&T... anyone know where I can get one? All I can find are ones for 4.1.3 =\
EXACT same problem here, let me know if you find anything
(Btw, my phone also had the "power button stuck down" issue, but your phone will vibrate when you put the battery in if this is the issue.)
If I'm not mistaken you will be able to Odin to 4.1.1 while using the 4.3 SD card debrick (again this is just guessing)
Sent from my ATT Samsung Galaxy SIII using TapaTalk
I've tried the SD card debricks for 4.3, and still nothing happens. Yea, I also don't get vibrate. As a long shot, I actually installed the qualcomm drivers and ran the qdload.sh script to attempt to send a signal which kicks the phone out of that mode (works on some... I want to say, HTC, phones), but, yea, I think the emmc just failed somehow. I'm hoping that the failure is just in the bootloader segment, and that by jtag reflashing the bootloader area, I should be able to boot. Either that, or even if one of the memory sectors died, hopefully it's not the one with my data partition. I still can't believe this ! Out of all the electronics I've ever used, aside from a hard drive or two, I've never had something like a phone just kick the bucket with no warning. gha !
Also, thanks for all the tips and stuff, guys and gals. Tell me if you figure out anything, and I'll let you know if I get it fixed with jtag.
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
OK plz let us know how it goes! I don't want to sound rude but your phone would be the only snapdragon I have ever seen fail....and I've been using snapdragons since the s1 on a HTC wildfire s
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ZOMG SO RUDE > haha, j/k ;P Yea, no problem, dude/dudette! I know how it feels reading threads with no followup... I'm actually surprised that people have come out of the proverbial woodwork mentioning having similar problems to me ! It really sucks spending inordinate amounts of time reading threads and not arriving at a definitive conclusion... so, yea, I especially want to let people know if there is a fix, and/or how I did it.
So, with regard to what you said about the snapdragons not failing... yea. This is rekking my mind, tbh, because I've just never had a device insta-fail on me like this (aside from some old computer hard drives that were server backed up, but yea that's essentially par for the course on that medium [yay for S.M.A.R.T.]). Especially a device that I'd only had for less than 2 years, and though my GS3 has heavy usage, I treat it very well (no drops, water, etc.)... so, yea.
Also, a minority of people with whom I have spoken via the æther have also experienced similar emmc failures on i747s, as well ! Which I was not expecting. It's still insane, though, to believe that, out of such a small percentage of phones that could potentially experience SDS, and then which ones actually do experience it... and then to not even have an i9000 and /still/ experience it on an i747... I feel as though I've won the lotto. Except ****ty.
I'm waiting on parts to come in, then surgery will commence.
Did you try going into download mode? If you can so that then the phone is fine. Another thing is try reflashing stock Odin which will erase msgs and stuff but not music or pics unless u tick "repartition".
Sent from my SGH-I747M using Tapatalk
Open serial port...OK
Connecting to the RIFF Box...OK
Firmware Version: 1.37, JTAG Manager Version: 1.56
Selected Resurrector: [Samsung I747 V1.0.5095.46594]
Connecting to the dead body...OK
Detected dead body ID: 0xhexhereisOK[redacted] - CORRECT!
Set I/O Voltage reads as 1.81V, TCK Frequency is 1 MHz
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Detected an Initialized FLASH1 Chip, ID: 0x0015/0x0100 (000000, 0x000400000000 Bytes = 16.00 GB)
Detected an Initialized FLASH2 Chip, ID: 0x0015/0x0100 (000000, 0x000000080000 Bytes = 0.50 MB)
No Resurrection Data is available for the eMMC Chip with Capacity = 16.00GB
WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Flashing the dead body...
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: DCC Loader has reported Error Code = 0x51 (0x000000). Trying to recover...OK
ERROR: Stopped due to multiple communication errors. Terminating at 0x0003AB3FBE00
Had to reduce the speed to that 2MHz/1MHz to get communication to work. So, 0x51 is a DCC power failure problem... but it is able to detect the initialized chips. So.. not really sure how to proceed at this point. I haven't checked the signal quality on my NRST line, which apparently can cause problems. Some people have increased the voltage from 1.8 to say 1.9, but doing something like that requires me to actually make my own resurrection file, which I haven't had the time to do yet.
Anyone seen a problem with something like this before?
The 000000 is somewhat unsettling, as the chip is apparently supposed to report some ID#? Although, the failures that I'm getting don't seem to be the typical ones that happen when the emmc becomes completely toasted.
Oh, yea... I can't seem to figure out wth is up with --> WARNING!!! Using Resurrection Data for the eMMC Chip with Capacity = 14,68GB
Like..... ??? I think I'm using the most up to date resurrector?!
EDIT: Dumping out the entire contents of the emmc (haven't had errors so far, but it will take a while at 1 MHz), into a bin file (this avoids the bad sectors in the bootloader).
Does anyone know what to do with the resultant *.bin file? I think that if I got another surrogate GS3, I'd be able to write that onto the phone, essentially cloning my dead phone. I'd like to avoid having to do that, though -- does anyone know how to write one of DCC bin jtag file dumps into a readable file system?
i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!
noobbrokes3 said:
i got a samsung gs3 yesterday, i loved everything but battery life, lastnight i used George Holtz's "towel root" and rooted my phone, added super user and rom toolbox, upgraded my recovery to clockwork mod basic, and proceded to flash to "flashingdroid version 2.2" it went thru everything and installed the rom, when it tried to reboot, it went black... now it does nothing, computer tries to recognize it, abut i cant get it to download mode, and i cant get it into recovery mode... it does not show charge picture when plugged in and if i take the battery out, plug it in, then insert the battery i get a red light... PLEASE HELP!!!!!!!
Click to expand...
Click to collapse
What model is your phone? You flashed a i9300 ROM, this is the sub-forum for the i747.
its the i747, i before looking today never knew there were more than 1 model of the GS3, is it possible to fix it?
This may help:
http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
This may help:
http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/
noobbrokes3 said:
my problem is my phone does NOT vibrate when power button is pressed, it isnt doing ANYTHING at ALL, the red charging light only comes on when battery is left out and the phone is plugged in, light turns off after a minute or so of the battery being installed, to me it seems like less rom flash related, and more failure in the board, but im not good at this stuff so im probably wrong, i bought a verizon one (i535) for 50 bucks (pretty banged up touchscreen is cracked in several places i got it without a back cover,but it works,) to get me by but i miss my 4g on straight talk =( i wish i had just left it alone, it was clean just 1 crack in the touch screen wires ans such for lcdanddigitizer got cut by accient while trying to modify midframe for verizon board, i sure as hell cant afford the att version for a while 150-260 for a decent i747, is it possible that a JTAG service would be able to bring it to life or even one of those dongles to force recovery?
Click to expand...
Click to collapse
Flashing an i9300 rom is guaranteed to hard brick the device and cause exactly what you described. If you follow the instructions in the thread linked in an above post it probably has a 90% chance of fixing it.
I am 99% certain it is not a hardware failure. Others have done the exact same thing and were able to fix it by using the instructions in that thread.
audit13 said:
It could be a board failure but it happened right after you flashed the ROM which leads me to believe it is software related.
A dongle is not going to help since the phone won't even power up. A jtag service would be your best and quickest option. You should try and find a shop that will guarantee to revive the phone or you pay nothing.
This might help with your current phone: http://www.xda-developers.com/android/how-to-make-your-verizon-galaxy-s-iii-a-world-phone/
Click to expand...
Click to collapse
i found one on ebay, full refund short of a 5 dollar shipping cost for return shipping, once i have money that i can spend ill sure as hell be giving it a shot
Or you can attempt to fix it for free.....but I suppose that is up to you.
DocHoliday77 said:
Or you can attempt to fix it for free.....but I suppose that is up to you.
Click to expand...
Click to collapse
either way its gonna cost me a little cash, i dont have a 16 gig sd card, forgive me for being so noob but the sd card trick CAN work for my case?? i know for a fact i cant do anythingto my phone right now as it wont even power on, but if you BELIEVE it will work ill gove it a try
Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.
DocHoliday77 said:
Unless you updated with the kk ota, you are probably on 4.3 firmware. I cannot guarantee it will work, but I believe the chances are pretty good that it will.
Just remember, if it doesn't work, dont give up on the first try. Many have had to run through the process several times before it would actually boot up again.
The only other tip I can think to give is to make sure you buy a decent sd card. It doesn't have to be top of the line, but there are tons of fake ones out there that would be less likely to work. If you can, try to buy one from an authorized dealer for whatever brand you are considering. This greatly reduces the chance of getting a bad card.
Click to expand...
Click to collapse
4.0.x was the last firmware, i never got to update it. i bought a PNY 16gb microSD HC class 4, it was 25 bucks at the local drug store, i was hoping for a class 6 - 10 but i believe it is a good quality card, maybe you would know better?
I won't lie, I am not a big fan of PNY, but as long as its the real thing, I think it should work. Class 6 or better is recommended, but it has worked on class 4 cards too. At this point, the only thing left to do is give it a shot. Good luck!