Develop Bugs

[Q] Phone Will Not Boot / Bricked

Hi there...
So I have a slight issue. I've been away from the XDA community for a while now, and anyways, I came back and wanted to upgrade into the latest Fresh 3.5.0.1 Rom. So I downloaded it, new radios, and new pri pack, and put it on and went to work. Now that I'm here at work, I flashed 3.5, the new radios, and the new pri. Rebooted (I think I probably should have rebooted after flashing the rom, before loading up the others :-\). I got the wonderful green error arrow thing. I've had this happen before when flashing roms, so I pulled the battery, waited a few minutes, then put it back in. Pushed the power button, and now I have a brick. It won't power up at all.
So I need help, as I've never had a brick before and I'm stuck here at work, working on my mac laptop. Any advice on how to get the phone to start into recovery so I can nandroid backup would be wonderful.
Edit: I was upgrading from Fresh Evo 3.3.0.1. According to Fresh, I should have been able to flash this rom over my old version. :-\
Edit2: Realized that General wasn't a good place for my to ask my question, so I brought it over here.

Are you positive the battery didn't get super drained? Regardless, if possible, keep it on a charger in the meantime.

teh roxxorz said:
Are you positive the battery didn't get super drained? Regardless, if possible, keep it on a charger in the meantime.
Click to expand...
Click to collapse
My battery was around 95%.

Alright, and what is this about a green error arrow? Try removing the battery for a few minutes, again and see if it powers up. Keep it on a charger.

After it wouldn't turn on, I pulled the battery for about 5 minutes, then put it back in--nothing. It's sitting on the charger atm; I might stop in at the Sprint Store during my lunch break and see if they can replace it without me getting hit with the 100$ deductible from Asurion :-\

Well, keep it on the charger. By any chance, anyone else in the office that has an Evo where you can test the battery to make sure it didn't magically die on you?
If not, try putting the battery back in and holding the power for an extended time...like a minute. I have heard that to work on occasion.

The green arrow was downloading the radio img. I think your pretty much bricked when u pulled the battery u caused it to stop downloading the img. Dors it by any chance enter bootloader if not itsbricked

lcorona056248 said:
The green arrow was downloading the radio img. I think your pretty much bricked when u pulled the battery u caused it to stop downloading the img. Dors it by any chance enter bootloader if not itsbricked
Click to expand...
Click to collapse
Oh my...if he did pull during the radio download, most definitely bricked, unfortunately.

lcorona056248 said:
The green arrow was downloading the radio img. I think your pretty much bricked when u pulled the battery u caused it to stop downloading the img. Dors it by any chance enter bootloader if not itsbricked
Click to expand...
Click to collapse
DOH! Yea then it's bricked. It doesn't boot at all.
I'm going to try to pull the battery and press power to see if that might not help some way.
>.<
This is what I get for trying to do this stuff while at work

misterneums said:
DOH! Yea then it's bricked. It doesn't boot at all.
I'm going to try to pull the battery and press power to see if that might not help some way.
>.<
This is what I get for trying to do this stuff while at work
Click to expand...
Click to collapse
Nothing good happens at work...your mac got jealous of what it could never be.
But unfortunately, you're bricked. When you go see Sprint, don't tell 'em you were rooted..blah blah...say that your installed the latest OTA and its suddenly not responding.

teh roxxorz said:
Nothing good happens at work...your mac got jealous of what it could never be.
But unfortunately, you're bricked. When you go see Sprint, don't tell 'em you were rooted..blah blah...say that your installed the latest OTA and its suddenly not responding.
Click to expand...
Click to collapse
Right. Yea hopefully my boss will let me out for my lunch in about 45 minutes and then I'm going to head to the sprint store and see if I can get a phone headed this way asap. Thanks for all your help!
Random Question: Do you think they'll let me keep the mSD card if I tell them that I have a bunch of private information on it that I wouldn't want getting into the wrong hands? And secondly, if anyone has gotten refurbed units--do they send them with SD's equipped, or will I get to keep my old one?

misterneums said:
DOH! Yea then it's bricked. It doesn't boot at all.
I'm going to try to pull the battery and press power to see if that might not help some way.
>.<
This is what I get for trying to do this stuff while at work
Click to expand...
Click to collapse
Yup, you're definitely bricked. That green arrow meant it was writing the radio image, and a battery pull during htat process almost gaurantees a brick. That sucks man. Before you go to Sprint, I would highly suggest you clear your sd card, either completely, or just ensure that there are no ROMS, flashable zips, or anything that will give the Sprint tech a clue that you've been rooted and flashing stuff. I've read where a phone was bricked and wouldnt turn on, so the Sprint guy wouldn't have known he was rooted, but he looked at the SD card, and saw ROMS, kernels, and other things that indicated the guy was rooted before. The tech was a jerk and wouldn't work on the phone and red flagged the account. Guy with broken phone = screwed. So yea, either remove your card before you, clear your card before you go, or remove all root/flash related zips and files from your card. Good luck man.

misterneums said:
Right. Yea hopefully my boss will let me out for my lunch in about 45 minutes and then I'm going to head to the sprint store and see if I can get a phone headed this way asap. Thanks for all your help!
Random Question: Do you think they'll let me keep the mSD card if I tell them that I have a bunch of private information on it that I wouldn't want getting into the wrong hands? And secondly, if anyone has gotten refurbed units--do they send them with SD's equipped, or will I get to keep my old one?
Click to expand...
Click to collapse
Well if they are able to swap it right there, they should let you keep your sdcard, and they can keep the other one. And they would have to give you the phone as a "complete" unit, so it should come with an sdcard, and if so, you can keep it as an extra.
Also, just in case, take the sdcard out now and copy it to the mac, and remove all you "rooting" files, roms, kernels, ect and place back on the sdcard; in case they don't let you keep it...but they should.

teh roxxorz said:
Well if they are able to swap it right there, they should let you keep your sdcard, and they can keep the other one. And they would have to give you the phone as a "complete" unit, so it should come with an sdcard, and if so, you can keep it as an extra.
Also, just in case, take the sdcard out now and copy it to the mac, and remove all you "rooting" files, roms, kernels, ect and place back on the sdcard; in case they don't let you keep it...but they should.
Click to expand...
Click to collapse
Yea I pretty much deleted everything. Never know which files might look not good to have on there. My store isn't a full blown Sprint Store--I don't think they have any real smart tech people, but it never hurts to be safe. I'm still going to ask for the card regardless.
Thanks for your help everyone--I can't click thanks anymore today--apparently I'm limited to 5 per day!

misterneums said:
Yea I pretty much deleted everything. Never know which files might look not good to have on there. My store isn't a full blown Sprint Store--I don't think they have any real smart tech people, but it never hurts to be safe. I'm still going to ask for the card regardless.
Thanks for your help everyone--I can't click thanks anymore today--apparently I'm limited to 5 per day!
Click to expand...
Click to collapse
True enough, but they should let you keep it. No troubles, just glad we got the heart of the issue resolved.

teh roxxorz said:
True enough, but they should let you keep it. No troubles, just glad we got the heart of the issue resolved.
Click to expand...
Click to collapse
The heart of the issue: My Stupidity

misterneums said:
The heart of the issue: My Stupidity
Click to expand...
Click to collapse
Well, we all make mistake,s but its important that we learn from them.

Good luck man! Hopefully sprint will give you a refurbished evo
Sent from my PC36100 using XDA Premium App

Update
Update:
So I received an express ordered replacement on Friday. I'm was super excited until I saw the screen. There is a thumbnail sized bright spot. I'm assuming that the phone I got was a refurb, but this makes slightly angry. Now I have to go to a repair center and probably get a screen swapped out or get a new phone ordered in. Worst part about it: it's a 45 minute drive to nearest repair shop. NO wait, I lied, the actual worst part about it is the fact that I can't root until I can get it fixed
Random question: I had been away from XDA scene for awhile. It looks like CM7 is looking pretty snazzy now with 4G functionality. Is there any downside at all anymore? Before it was because there was no 4g and no HDMI. Any thoughts are appreciated.

Take your sdcard out and then tell them you just downloaded the latest ota and I have had one refurb with card and one without either way KEEP Your sdcard
Sent from my SPH-P100 using XDA App

Reboot problem, need help

Ok, i did a search but not much help.
i have been having reboot problems but i normally take the batt out and let it sit for a while and it boots back up.... reason why i have to pull the batt is because the reboots dont stop.
i was using the phone and it started to reboot... but now no matter how long i let it sit it wont boot back up... just reboot.
i did flash a splash screen using pc36img and it does work but thats it.. it reboots..
im going to try and let the phone "rest" for a couple of hours but i have a feeling that wont help this time.
anything else you guys can think off?
it wont boot into recovery either.. it did when i pull the SD card but i dont think the card it bad, since i took it off and placed it in my pc to add the new splash screen.
i was reading some threads and some people said they had hardware problems that where causing the reboots so this may be the case with me as well.
ideas?

Need more info... which ROM? Which radios? How's your signal? Etc

Vinchenzop said:
Need more info... which ROM? Which radios? How's your signal? Etc
Click to expand...
Click to collapse
well, i have been using the latest Miui with the latest radio update with PRI etc.
i have been having the reboot problem for a little while but like i said, i can normal solve it by pulling the battery and after a few minutes turning the phone back on.
no matter the rom, it still this did.
today we where having problems with the signal... we are getting 4g updates
but, i think think that would cause the phone not to boot up.
i could be wrong of course

Seeing as it doesn't appear to be a specific ROM issue, it could be a hardware issue, such as a bad memory block, which if that's the case, obviously there is little advice besides take it to Sprint and try to get a replacement phone.
But if that is the only solution, I'd advise you to wait until a root method for the latest ota is available because your replacement phone would come with the latest, unrooted firmware and you'd be stuck without root. So if dealing with the reboot issues is possible ( though I'm sure frustrating) I'd hold out for the potential root method to be released.

i was putting up with the reboots since i am planning on getting the evo 3d. but i need a phone. i havent touched it for a while so i hope that somehow helps lol but if not i plan on going to the sprint store tom morning as soon as the open.. i have an hour cause i have to be on base at 10:00 and i dont want to be without a phone all day.
hope they can give me a replacement and i dont have to wait for one to be shipped.
this sucks
the thing that kinda worries me is that they know i root my phones, hell i have shown them a few things as well as the Evo with it 1st came out.. i ordered by phone and they didnt have the phone till later.
anyways..
thanks for the help.. it has to be hardware related, dont think it can be anything else.

it it just booted but as soon as it got up and running it rebooted again... damn it

Well. Got a new out of the box evo. They didn't have any at the warehouse.
So here I am with a stock evo. Boo lol but no reboot problem, so I'm happy.
Sent from my PC36100 using Tapatalk

[Q] Horray! I bricked my epic...

Ok, so like...two days ago, I followed qbkings video on how to root & clockworkmod an epic with EI22, well it worked. I got recovery working A ok and played around with some roms and stuff. They all worked for the most part, but after rebooting my phone, the SAMSUNG loading screen wouldnt fade away, realizing it had been soft bricked. I tried recoveries but they didnt work. tried tutorial after tutorial after tutoria, but no luck. When trying the Odin unroot method It'd always be stuck on like a factory. file, and keep getting the phone - ! - computer error afterwards. Ive tried looking around the forums and such, but no go. I really need help with this.

You didn't look to hard. There have been 5 threads like this in the last 2 weeks. Go to the stickies, top of development and follow post 1 of How to restore a semi-bricked Epic.
Sent from my SPH-D700 using XDA App

Uh yeah, that was one of the first posts I tried. Never worked for me. Followed exactly step by step and repeated the process five times, but ive been constantly getting stuck on factoryfs.rfs

oh ****, now it wont even turn on. tried charger usb, nothing! no indicator or anything. damn. am I screwed?

I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid

Try pulling the battery and sd card, let sit for an hour with usb unplugged, then connect to usb cable with odin running and try to boot into download mode.
If it goes, pop the battery in and load up ei22 or another odinable tar along with the recovery in qbkings videos. Make sure only reboot is checked in odin.
If not, go back and try every step in the sticky. I doubt that you have a problem that has not been experienced already.
Sent by my CleanGB Epic using XDA App

So you tried buying and using a better cable? And tried with both the battery and sd card out using only the computer as a power source like the thread in Development said to do?

b16flybye said:
I think you were better off leaving your phone alone. If following instructions is difficult, than that should have been your first clue. Id post a link to help you, but you have already read and tried it, and even that didn't work........time for you to buy an iphone I guess.
Sent from cyandroid
Click to expand...
Click to collapse
That's a bit flamish.

shane6374 said:
That's a bit flamish.
Click to expand...
Click to collapse
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk

azyouthinkeyeiz said:
Sometimes the truth hurts.
I tend to agree with that sentiment, nothing against you OP, but there are some that gravitate to technology and feel at home, and then there are some that gravitate and lack the necessary skills for something like this.
This is a very straight-forward task, especially with all of qbking's hard work in making those very easy to follow videos, and other's time typing out tutorials, so I really fail to see how most have so much trouble making it work. Maybe they belong in the latter analysis.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
We all started somewhere on this, and I bet most people didn't have success right away. I know I didn't on either platform I've worked on. I'm just sick of the n00b flaming around here. These people might be the ones who's roms or kernels you running in a year. Just show some respect.
Sent from shane6374's Epic via Tapatalk

Youll have to find one of them jigs to get you back into download mode I assume usually time heals all mistakes though if your inpatient id look up how to make an odin(download) reset jig ( I think its called that). I think there a thread about that lying around here somewhere...
Sent from my OG Epic

Yeah, not trying to knock on you too hard, but qbkings videos should be all you need for successfully rooting and flashing. He works hard on them and is very clear with instructions.
Sent from cyandroid

Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.

Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.

With the soft brick you might have been able to save it. It happened to my brothers phone and what I did to fix it was wipe everything, factory reset
Then flash stock rom. Wipe everything again
Then flash stock kernel
Wipe everything again
Then it was perfect.
If you had already been flashing roms.and such then your problem wasn't following directions.
You just might have flashed a rom without a supported kernal. Causing bootloop
As far as where you are now.. maybe tell then you dropped it and it never turned back on?
I don't think they can ever find out you rooted it if it never turns on again lol
Sent from my PG86100 using XDA App

Jbluna said:
Yup, Ive tried different cables,ports, no battery, battery but got nothing. I thoroughly read through the entire post and tried what was suggested and got nothing. Phone wont turn on or do anything. I'm thinking that i'm screwed. I have been thinking about getting a replacement epic for a while, cause some time ago I actually accidentally dropped it from my desk and this happened to it http://imgur.com/ZBlNn still worked fine, so I didn't really bother thinking about replacing it, but now I'm guessing that I have to. If I do end up requesting for a replacement, any tips/fore warnings about what I should say when I talk to the guys over at sprint before i end up mumbling like an idiot.
Click to expand...
Click to collapse
Don't use the broken screen as the reason or they will charge you around $100. Just try and make sure you get across the point that its the faulty phone (even if it isn't) and make sure you have an accurate believable story on how it got bricked. If you mention anything about messing with root or anything similar they won't replace it.

True. But on another note you can't say much. Only other thing I can think of is saying maybe you tried updating the device and it died
Sent from my PG86100 using XDA App

Seriously you ignored the odin mode jig? it jumps you back into download mode and you should be able to odin back to eco5........ Ill find a how to for ya.
Its all over a simple google search and you can find a usb jig for about 8 bucks.
Sent from my OG Epic

I just unbricked my wife's EPIC with this: http://forum.xda-developers.com/showthread.php?t=1052813
thanks dyehya for the howto tutorial!

Jus tell them you took it off charge this morning and it wouldn't come on.
Did you try the mythological magic button? The pin hole behind the cover next to the camera lens?

[Q] Bricked SGS2?

So... I was trying to port a skyrocket ROM to our device with CM9.1.0 as the base. I just flashed it on my device. Flash went fine. I thought it would be fine... However, when I hit reboot, nothing. Black screen. I don't know what happened. It doesn't seem to be responding to any commands. I'm trying a ton of things. I can't figure out anything... Somebody, answers please? Can I do anything? A jig maybe? Really hope this isn't the end for my SGS2...
Edit - Tmobiles generously sending me a new one for 5$.

DinoSoup said:
So... I was trying to port a skyrocket ROM to our device with CM9.1.0 as the base. I just flashed it on my device. Flash went fine. I thought it would be fine... However, when I hit reboot, nothing. Black screen. I don't know what happened. It doesn't seem to be responding to any commands. I'm trying a ton of things. I can't figure out anything... Somebody, answers please? Can I do anything? A jig maybe? Really hope this isn't the end for my SGS2...
Edit - Tmobiles generously sending me a new one for 5$.
Click to expand...
Click to collapse
I'm thinking you may have jumped the gun a little on the "getting a new phone from Tmobile"
I'm sure you've tried taking th ebattery out and holding the volume buttons with the power button and trying to get into recovery or download mode?
Also the Jog in my opinion would have helped as a last resort, XDA is filled with so much usefull info that it would prob have been better to get the phone working on your own so you can see why it happened.
I'm willing to bet it just got stuck on some kind of boot loop....But since your getting a new phone I'm sure your going to be nervous rooting the new one....Nothing learned

NhCarDealer said:
I'm thinking you may have jumped the gun a little on the "getting a new phone from Tmobile"
I'm sure you've tried taking th ebattery out and holding the volume buttons with the power button and trying to get into recovery or download mode?
Also the Jog in my opinion would have helped as a last resort, XDA is filled with so much usefull info that it would prob have been better to get the phone working on your own so you can see why it happened.
I'm willing to bet it just got stuck on some kind of boot loop....But since your getting a new phone I'm sure your going to be nervous rooting the new one....Nothing learned
Click to expand...
Click to collapse
Turns out, I had technically flashed a Skyrocket ROM (my port). Nothing can be done about that... Lesson learned: Don't port from skyrocket's stock ROMs.

S3 SDS?

I've read a lot about SDS and there seems to be no general consensus on the symptoms of it. Some people say they can enter recovery/dl/etc but the phone crashes all the time. Others say that their phone doesn't turn on at all and won't charge.
Here is my issue with my S3.
I just recently installed 4.3 pacman rom. I got everything set up and everything was going great. I tried to flash ACID MOD 7.0/DevilKernel, and they both failed, so I rebooted back into the system and the phone just shut off.
If I take the battery out and hook it up to a charger, the LED will light up. However, if I plug it in with the battery already inside of it, the LED does not turn on. Also, if I hook up the phone to my computer, it'll make a sound like it is trying to mount the device, but it'll make a stutter sound like it failed. It doesn't do this automatically, it only does it if I try to enter recovery/download mode/or turn the phone on.
I'm not sure if the phone is completely dead, or bricked, or what is going on? Or if anyone has any other suggestions - other than changing the battery, which I did do, lol.

Sounds bricked. What model is you s3 btw? And can you post links to everything you've flashed?
SDS doesn't affect our S3's, it was only the international model that had this issue, and I believe it was only on the original firmware.
Sent from my SCH-I535 using Tapatalk 4

http://forum.xda-developers.com/showthread.php?t=2015525
latest nightly
+ 4.3 gapps. it booted fine from gapps.
http://forum.xda-developers.com/showpost.php?p=38599629&postcount=1005
acid mod v7
2802 + 2805 for sammy devices
http://forum.xda-developers.com/showthread.php?t=2240832
devil kernel
prior to flashing pac i installed 2.6.3 twrp because the 2.5.x i was on did not work. i booted in, flashed pac, got everything set up. after restoring the apps and whatnot, i went back to twrp to install acid + devil kernel. they both failed, so i just rebooted from there and it never turned back on. i just assumed the battery was dead, charged my bat in my external charger, and yeah, never turned on since then.
any way to do this without jtag? i'm not at home right now to do something like that and am out of the country, so im a bit unsure how hard it'd be to get those supplies.
i was able to go to a samsung a/s place, but they would only send back to america. i don't think it is worth paying 200+ when this phone is probably only worth 400 or so out of the box, brand new, maybe even less.
i just assumed it was SDS because the symptoms seemed spot on, but it was really weird. i've never had any issues like this flashing roms and it wont' even go to the boot logo. if i plug it in, it makes it seem like it is trying to mount, but there are no vibrations or anything like that on the phone.
thanks for all the help doc, like always.

Thanks for providing the links! Makes it so much easier to help when we don't have to search for everything!
I'm afraid you have bricked your device. I don't know about the Acid mods compatibility with our device, so it may be part of the problem, but that kernel is for the international S3 (I9300/9305). (I'm assuming you have the T999 btw). Never flash anything for the international models, you're nearly guaranteed to brick the phone!
But there's hope! Verify your model number by looking under the battery. Then check out KAsp3rd's unbrick thread in the development section. It should be towards the top.
Give that a shot and say a prayer! It won't fix all bricks, it depends on what was overwritten, but there's a good chance it'll fix yours!
In the future, it's best to stay out of the international models forum altogether! The devices are very different and you take a huge risk when using anything you find there!
Good luck!
Sent from my SCH-I535 using Tapatalk 4

Thanks Doc. I don't think it'll be fixed unless someone in that thread wants to try to flash that devil kernel and see if they can unbrick it w/o jtag. I followed those instructions to a T, and no dice. Although, I can't really tell if my battery is charged right now. I don't have my external charger on me. I will try again tomorrow, but I really doubt it at this point.

Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4

DocHoliday77 said:
Really? Maybe give it another try with a different SD if possible. I saw the posts there and there's no reason I can see that it wouldn't fix when aboot got overwritten.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, it is really weird.
After some toying with it I figured out that it only tries to mount the device when connected to the computer IF and only IF my phone is connected to the computer with no battery. It didn't do this before, which is odd. Even if I take out the SD card it still does this now. Before it would fail to make any sound, and now it tries to install the driver. But then it says it fails to install the driver for it, which is the bricked one, the SUBS DWLND or whatever.
I tried following Kasp3rd's advice to hold the button down longer, and I held it down for a whole five minutes with no luck.
I will try another SD when I get the chance, right now I only have a 64gb with no avail to back it up. The SD card is super old though, you are right Doc. It is from my OG droid, but really I haven't had a need for SD cards since I was on an iPhone after my droid and since the S3 is mine, but i'm not using it, I never really bought a nice SD card for it.
I'm going to run to the store in a bit to get one though and hopefully that will make a difference?

May have missed the part about it being 64GB before. Could be the age, but also those 64's have given lots of folks some problems in the past. Seems the S3 can be a bit finicky with those.
Sent from my SCH-I535 using Tapatalk 4