Develop Bugs

[Q] Need help, I have a brick

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. :-\

Does anything happen when you try and power on? Ie does the phone vibrate and do anything at all? Also when you plug the phone on does the charging lite come on? I hate to say this but if you answer no to everything it looks like you may have a brick. But there is always hope.
I could be wrong but I think toy were suppose to boot the rom then flash the radios.

wrapkgb said:
Does anything happen when you try and power on? Ie does the phone vibrate and do anything at all? Also when you plug the phone on does the charging lite come on? I hate to say this but if you answer no to everything it looks like you may have a brick. But there is always hope.
I could be wrong but I think toy were suppose to boot the rom then flash the radios.
Click to expand...
Click to collapse
No light with charging, not even the most faint bit of vibrating other than my own pulse I do have insurance on the phone however through Asurion or however you spell it.
Also, I was going to delete this thread before you posted here, as I realized too late that this isn't the question forum

Wrong forum maybe, but its already here so its all good. With what you said I would have to say you in fact have a brick unfortunately. I would work on trying to get a replacement from asuron. Sucks man, radios can be dangerous if something goes wrong in the process of flashing them.

wrapkgb said:
Wrong forum maybe, but its already here so its all good. With what you said I would have to say you in fact have a brick unfortunately. I would work on trying to get a replacement from asuron. Sucks man, radios can be dangerous if something goes wrong in the process of flashing them.
Click to expand...
Click to collapse
I guess that's what I get for not being more active in the community >.>
Gonna check with Sprint during my lunch to see if they'll replace it for free as a defect ^.^
Sure would be nice not to have to pay that 100 dollar deductible.

Ya, unfortunately you probably pulled the battery while the radios were updating. Good thing you have insurance, because that Evo is done.

Why not take it to Sprint? Just say it stopped working. Make sure to delete any suspicious files from the SD card.

jxr94 said:
Ya, unfortunately you probably pulled the battery while the radios were updating. Good thing you have insurance, because that Evo is done.
Click to expand...
Click to collapse
I pulled the battery after I rebooted and it went to the green ! screen. :-\.

Wish the outcome was a little better!

[Q] CM 7.0.3 Random Reboots Even After Clean Install

I've racked my brain and searched the forums so I'm hoping someone has some insight here. Recently my phone has become unstable...I can't do too much in a single sitting without it rebooting. I've been on CM7 for a while now and had been trying the nightlies so I thought it was maybe that or just left over garbage from the upgrades so I decided to do a clean CM7 install yesterday (factory wipe). After I got through the setup and started to download gmail (1st non-stock app) from the market my inc rebooted. I flashed Chad's latest kernel thinking maybe it was a kernel issue...still reboots.
I then decided maybe it was the battery because at times I will get into a couple of reboots back to back and then the phone turns off and vibrates three or four times. But when I get the phone booted and check the battery temp it is maybe 98F which doesn't seem to be above average based on my forum readings. I then swapped batteries with my wife (unrooted inc) and we both launched plants vs. zombies and started playing. After maybe 10 min, I got my first reboot and then another a few minutes later so I just turned the phone off...she kept playing.
Now of course I have to point out my wife works for Verizon Wireless so I'm getting extra grief for rooting my phone and she is saying that is the cause since she never has reboots. Not that I want to prove my wife wrong, I really just want a phone I can do more than make phone calls on, but someone please tell me she isn't right. My reboots only seem to happen when I've had the screen on for a while...3 hour conference calls have no issues. Can you give me suggestions of things to try to help narrow down the issue? Thanks in advance!
Phone Info:
Baseband:2.15.00.07.28
Kernel: 2.6.37.6-incredikernel-gb-04192001
Mod Version: CyanogenMod-7.0.3-Inc
Build: GRI40

I get similar problems but it happens when i am watching youtube videos or playing games, or sometimes out of nowhere. Can't figure out and it is really annoying.

Copy sd to pc, reformat sd fat32, copy stuff back to sd. Helped a friend with hers.
Sent from my ADR6300 using XDA Premium App

Thanks I'll give that a try. I did try running the phone without a card at one point and it didn't help any.

AOSP Roms, like CM, interact with the sd on boot. Don't expect aosp roms to boot without sd.....
Sent from my ADR6300 using XDA Premium App

OK, performed the the SD format last night and just got around to running apps today. Again, I tried Plants vs Zombies and after about 20 mins the phone rebooted...I had been an hour long conference call before that. The phone rebooted and got to the startup screen and then rebooted again but at least this time it finished booting which is an improvement over before. Also, thanks for the tip about AOSP roms not booting without an SD card.
I did notice yesterday when it rebooted on me, after a couple of bootloops the screen then went black and the phone vibrated 5 times. I was only on a short phone call yesterday while in my car for 10 min.
On a side note, I haven't partitioned my SD card with an app partition but I was wondering if it is necessary for moving apps to the SD? I have moved several apps to SD so I want to make sure that isn't causing an issue either.

had the same problem myself, did a clean install which didn't help, finally reinstalled 7.0, all working fine now
Sent from my ADR6300 using XDA App

Snappyts said:
had the same problem myself, did a clean install which didn't help, finally reinstalled 7.0, all working fine now
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Thanks Snappy...I never really thought about reverting. I've give it a try later today and report back.

Alright, so last night I performed a factory wipe and installed CM 7.0. Everything went fine but as soon as the ROM loaded and I opened the market it rebooted on me. This morning I just performed another factory wipe and installed MIUI thinking maybe it might be a ROM issue, but I got the same results. As soon as I opened the market to start installing stuff it rebooted on me...I tried this twice and reboot each time the market opened. I guess next I'll try a sense rom, Skyraider maybe...I'll post back with the results.

Warranty replacement
I was having pretty much the same issue. I tried everything from countless forums for the last month and a half. Finally had to cave and get a warranty replacement. - just pointing out that it might be a hardware issue (my device ran hot w/o sd and stock OS)

If the problem is following you on multiple roms it sounds like its probably a hardware issue.
Sent from my ADR6300 using XDA App

I've bounced around between various forums/posts and I think I have to agree it is probably a hardware issue. Being that I'm out of warranty, my only alternative is to upgrade or buy another Inc. Given the small pricing difference, buying another Inc versus upgrading, the logical choice seems to upgrade.
So my upgrade choices that are currently available are Inc 2, Thunderbolt, or Revolution. Another option is wait for the Bionic to come out in a few months. Any suggestions? I'm personally leaning towards the Thunderbolt...
Thanks again everyone for your help.

Well if you need to update now, I'd say the thunderbolt is probably your best choice. If you can wait, the bionic, if unlocked, looks like quite a phone, but IMHO the galaxy s2 is the phone to beat.
Have you tried getting a replacement? I suppose if you got your phone when it first came out the one year warranty might be up but it never hurts to try.
Sent from my ADR6300 using XDA App

k_nivesout said:
Well if you need to update now, I'd say the thunderbolt is probably your best choice. If you can wait, the bionic, if unlocked, looks like quite a phone, but IMHO the galaxy s2 is the phone to beat.
Have you tried getting a replacement? I suppose if you got your phone when it first came out the one year warranty might be up but it never hurts to try.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I haven't tried, but we did get the phone when they first came out last year so we are a couple of months past the one year warranty. My wife looked it up though and since we are available for an upgrade at this point the likely scenario is VZW pushing me to a new device rather than replacing my dying one.
I agree, the Galaxy S2 does look nice but since my wife works for VZW I'm kind of stuck with them.
I'm tempted to limp along until the Bionic comes out to see what it has to offer. As long as I can make calls I'll be ok...I guess Plants vs. Zombies will have to wait.

The GS2 is coming to Verizon. Not exactly sure when, there was a rumor that it'll be next month but I don't know how for sure that is.
Sent from my ADR6300 using XDA App

k_nivesout said:
The GS2 is coming to Verizon. Not exactly sure when, there was a rumor that it'll be next month but I don't know how for sure that is.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I had to go refresh my memory on the exact GS2 specs, then I had to wipe the drool from my mouth. I haven't heard of Verizon getting it within the next couple of months so now I'm even more bummed.
I guess it will kind of depend on how long my phone holds out. The random reboots and shutdowns can be annoying and have become all too frequent if I do anything more than make a phone call...sometimes even then it shuts down.

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

I bricked it was my fault....

So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium

"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT

MochaCharok said:
"MOD EDIT: Always use the Stock CWM5 recovery for anything you want to flash. Do not use the recovery that comes with this rom to flash or do anything with. "
You kind of set your self up there. The thread states that AOKP B39 doesn't come with a safe recovery. Either way, have fun with your new E4GT
Click to expand...
Click to collapse
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.

dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
Boom. Looks like you're right -- oh well. Sorry OP.

Same thing happened here

sbeekman said:
So yesterday I flashed the new aokp build 39 know all the risks of bricking but i thought my phone was immuned lmao no jk but i have been flashing for a few months now sometimes going back to el26 and sometimes i just flashed using ics recoveries wiped data and all and since i never bricked I thought it was safe, but yesterday i was not so lucky like i said i was on aokp 39 and wanted to go back to wicked so instead of going back to el26 i used the included cwm recovery and went to restore my backup and to stop this story from dragging on it restored but when it booted back up it would not go past samsung screen i cld get into recovery and odin mode tried sfhub one click same thing stuck at samsung logo everything i tried nothing worked brought it to sprint today I was honest told em i was rooted and explained i already tried to flash back to stock their guy said' "i'll be able to get it." Lol i said okay but I knew he could not he came bck said he couldnt i have tep and he ordered me a new one and i can get it tomorrow with no charge... Just an fyi u can get ur phone replaced for nothing even if u brick so i have my tablet to get me by til tomorrow so the cwm included in aokp 39 is not safe...
Sent from my K1 using xda premium
Click to expand...
Click to collapse
Don't feel too bad. I did something similar the other day and experienced a brick myself. I now have a new E4GT, free of charge. I made an elementary mistake, but I knew the risks.

I do not believe the new AOKP posted has a safe updater binary (since they did not say so) which makes it a bad deal to flash in ICS recovery still even a safe one.

Hate to hear this. But seriously OP. Thanks for actually owning up to it. When I bricked mine I did just like you. Sbrissen got me on Gtalk and apologized for bricking my device. I told him that I had not been aware that he had come to my house and flashed my phone for me. He said he hadn't and so I said then how is it your fault. I've seen so many times where someone bricks their phone and blames the dev. So props for being a stand up guy. Also. It is amazing what you can get with sprint reps when you just shoot straight with em isn't it. Glad you got it worked out.

Yea same here bricked mine and was titally my fault did it the same day I got the device and have no insurance really liked this device from the little I got to use it maybe one day I can afford another and nit be so stupid next time but least I know I'm not alone
sent from my Verizon Wireless HTC EVO 3D

@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.

Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium

dafluke24 said:
I believe Jay added the MOD EDIT after he had bricked his phone. There was no warning about not using that recovery prior to that. There was a long discussion about that in the thread.
Click to expand...
Click to collapse
same... second brick too. Should've been more careful though.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Make sure you odin to a stock samsung rom(it will fail at data.img, so just unplug it there. This most hints that youre on a non stock rom such as the warning icon.) and then use a usb jig(~$20) This gets rid of all binary flashes in download mode.

That's if you can turn the phone on. Some can and some can't

garwynn said:
@ruffneckZeVo,
First off no need to post the same thing in 3 threads. You'll get a reply.
Even though you didn't have insurance did you try taking it in to get it to Sprint for replacement? Samsung should also cover it but Sprint will probably be the easier solution if possible.
As for modified .PIT files we don't have one for the E4GT - it was quickly recommended not for long term use, so replacement has been the recommended solution. I don't believe anyone has been outright denied one yet - but I could be wrong.
Click to expand...
Click to collapse
Sorry just anxious to get this fixed I had the device one day and really liked it its not on sprint I got it from cl and flashed to vzw so sprint isn't an option to fix it ill find another asc thanks for the info
sent from my Verizon Wireless HTC EVO 3D

For what it's worth....
I've had my SG2 E4GT since the middle of april. Rooted it about 3 days after having bought it. And have been using Blue Kuban's Rom ever since.
Sadly, for some dumb reason, I decided to try out the new AOKP build -.-
Ironically I think I bricked it trying to flash from Blue Kuban back into a Gingerbread EL29 build...... But it had Team Rogue's CWM 5.1.0 or 5.0.1 one of them -.-
Either way, after flashing AOKP went to reboot and black screen, only blue blinking LCD light of doom.
I've ordered a USB Jig so I can try to use that to reboot into recovery... but I'm prolly messed eh?
Should probably try going to the sprint store where I got it? I do have T.E.P.

anti-up said:
Anybody without insurance that bricks there phone (b.l.o.d.) just go to an a.s.c. location (authorized service center) and tell them your phone won't turn on and you don't know why....you pay $35 and they order you a replacement that will be delivered next business day unless its back ordered. Then you have the option of adding T.E.P. going forward. They will also give you the option of a white or black device. (Unless the tech is a d.bag)
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I did the same thing. I felt bad but well you know. Anyway it worked great, they even had it in stock.

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