Develop Bugs

[Q] Yet another bricked Defy: no response at all

Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.

I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.

Try reinstall usb drivers, rsdlite, different usb port, and different pc.

@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.

If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.

im having the same issue, did you solve it?

im having the same issue, did you solve it?

try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...

You have tried the McGyver-trick?

I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.

Ok. At least you have the time now to enjoy your sunny weather in Brazil...

RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help

First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx

Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again

i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before

Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App

Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan

hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..

USB Issues

I was running Leedroid on my Desire and all was fine.
I seen these Sense 2.1+3.0 ROMS and decided to give one a go.
I tried to get into recovery before doing anything to take a NAND Backup, but it just refused to go into recovery. I finally got it in there and tried to apply to update.zip but it kept saying something could not be found, I forgot what, and failed after 10 tries.
I booted mu phone up and I'd lost all my data. It's like the phone had been wiped.
I tried reseating the SD Card and checking it was all ok, but then I got stuck in a bootloop. In the mean time, my Alienware Laptop decided to die, followed by my backup Dell laptop! lol
I messed around for ages trying to get various things to work, but couldn't do it. In the end, I downloaded the old root method and flashed Cyanomod 7 which seemed to work and I got it booted, but I couldn't mount the SD card and it would rarely pick up that the USB was connected.
I then flashed AceSMod007 which also seemed to go well minus 2 things.
The first, Text messages seem to show my contacts picture, but also it only shows their Number rather than the contact name. This is VERY annoying and I can't find a way to resolve it.
The second issue, and possibly the most worrying is that it won't pick up USB connection AT ALL. This includes when it's plugged into the Wall to charge.
I tried the USB Brick fix, but that didn't work at all.
I shutdown the phone, removed the battery, plugged in the charger, inserted the battery and booted up the phone and it started charging, but as soon as I unplugged the charger and put it in again, same problem.
I'm currently trying another ROM to see if that resolves the issue, but I suspect that it won't tbh.
Has anyone came across this before and/or knows how to fix it?
Other things I've tried:
Wiping all data, cache and Battery data.
Using different USB cables
Thanks
UPDATE:
Flashing a different ROM didn't seem to resolve it.

Quick update.
I flashed Insertcoin rom onto the phone and it's resolved my text message issue.
Also, when I plugged the phone into the PC, it didn't give me any options for mount SD or anything like that, but said it was charging. However, an hour later and the battery had only gone down.
Since charging by USB has always been slow for me, I plugged in into the wall socket for an hour but it wouldn't pick up that I'd plugged it in. I turned the phone off and I got the LED to say it's charging.
Left it, then booted it up and still has the same battery level.
I don't expect it's the battery otherwise it would pick up fine when plugging into the PC.

Could be an usb brick:
http://forum.xda-developers.com/showthread.php?t=691639

Cheers mate, but as I mentioned, I've tried the USB Brick fix a couple of times and still experiencing the same issues.

Can you switch on blue tooth? Does it stay on?
Sent from my HTC Desire using XDA Premium App

Actually, no. Its says Turning On... Then just goes back to off.

you DO have USB-Brick
you gotta fix it
if S-OFF do:
fastboot oem enable qxdm 0
fastboot oem eraseconfig
if S-ON there are a few threads on xda on how-to do it, if you still get no USB-connectivity you just didnt do it right
good luck

Ah, I did try it a few times. I'll just keep trying then.
Cheers

Are you S-Off or S-On and are you still ROOTED?
This thread for USB Brick
See for my post here
if you are S-off or tried to flash a RUU and lost ROOT!
This thread has a flasher with built in USB Brick fix

I'd already followed the USB Brick guide and it didn't help.
Now, is I were to have missed the step that says to run '/data/flash_image misc /data/mtd0.img', I'd be a bit of a tit.
So let's just say that I tried the guide again and now I have full USB functionality back
I was going to S-OFF my phone, but I'll hopefully get a Sensation soon and I don't want to fubar anything in the mean time.
Thanks for the help and pointers though guys. It's nice to be a member of some forums that aren't full of people who want to cry at you for not understanding everything 100%.
Cheers again

just use the thanks button
glad we (or at least I) could help.

[Q] [HELP] Desire messed up after alpharev

Hi there,
I had a very nice trip with my rooted desire with a miui rom on it for now maybe, 1 year smthg.
Recently, i bought a new µSD and wanted to prepare it for my phone ; i downloaded rom manager, and tried the "partition SD" functionality, which told me that i would have to update my clockworkmod, which i tried with the "update recovery" in it, which failed.
After a while, i found that i forgot to S-OFF my phone, and that was the reason why i couldn't update the recovery. So i decided to S-OFF. Unfortunately, my phone didn't went to the last step, and stayed stuck at the boot screen until its battery died, maybe an hour after.
I began a long journey trying to figure out if my phone was bricked or not, since i wasn't able to boot it up ; only the hboot was responding. I tried MANY ways, MANY posts, i tried to flash with a nand backup without success ('access denied'), i tried to flash just the recovery (same or 'signature failed'). I tried to put a PB99IMG.zip file from alpharev into my phone without any success...
BUT. I succeed in recovering my phone with putting a stock PB99IMG.zip from shipped-roms and it boots up very well on a crappy sense rom.
From that, i tried hard to root it again since i want to try again to S-OFF it, and after that, return back to my beloved miui rom. I'm stuck because of a mysterious problem into my phone. It looks like it doesn't like the third step which (i guess) requires a boot script. So nothing happens to it, it freezes to the bootscreen, while unrevoked says "waiting for reboot..." endlessly.
I succeeded once (only) in passing this step, but then unrevoked said to me something like : "Internal error: failed to unlock NAND flash?" which seems crazy since i'm in a 0.93 HBOOT (since the RUU reset). I hadn't any Superuser app nor signs of rooting ("su" command failed in terminal).
For now, i'm trying to root it via the Visionary app, but i don't think it will work.
If anyone has any suggestion in making things better, i'll be pleased to hear !
PS : I'm writing this post because i feel it could be full of useful infos for anyone else stuck with a "bricked" phone.

use this guide to S-OFF, install custom recovery and root.
read all the instructions, several times.
oh and rom manager is often not recommended for this phone as it can often cause usb bricks. once s-off you can flash different recoveries via fastboot or android flasher.
use gparted or 4EXT recovery to partition your sd card.

Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !

ynk said:
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
Click to expand...
Click to collapse
don't just go flashing RUU's randomly, you may get amoled/slcd incompatibility for instance, which is what this might be.
try reading the troubleshooting guide, you can probably save your phone.
read carefully before you do anything in future...this situation could probably have been avoided

Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.

ynk said:
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
Click to expand...
Click to collapse
that problem sounds different as that was posted ages ago, and they weren't messing around with rooting and RUUs...
i don't think you should 'wait and pray, try another battery, or let it dead'
can you get to recovery/bootloader/fastboot at all? please post more details. if you can then it's probably not bricked.
i'm unsure of whether you've actually tried anything in the troubleshooting guide. try [2] advanced boot problems, S-ON. create a goldcard and try the WWE RUU
if none of it makes sense ask directly in that thread
and if you get the RUU to boot, don't use unrevoked...follow my 1st reply...

I stopped all the things i was doing when i had your reply, trust me !
As i said, i can't get the device to be powered on ; since, i'm not able to have any access to hboot, fastboot, nor adb. The phone does not charge when plugged to a charger neither to a computer. The led stays black, and the battery doesn't get warm (which normally does when charging).
Since the phone doesn't turn on, the guide you gave me is useless (but i learnt a lot from it, so thanks for that). The only section which *could* have been useful was the one talking about wrong RUU flashing with SLCD off ; but since my screen was working, and the symptoms are different (my phone is not recognized by the computer), this is not describing my problem definitly.
Be sure that if i can boot that phone once again, i'll follow your 1st reply and won't use unrevoked on it ever...
I'm trying now to find an other battery, to know which from the battery xor the mobo of the phone is dead. If battery, i'll just buy a new one ; if mobo, i'll buy a Desire S, since my phone reached the warranty limit, and i would have to pay to repair it...

Please help!

Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.

simon211175 said:
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
Click to expand...
Click to collapse
ok mate
right the mcgyver trick works a treat and is surprisingly easy. i wasnt keen on it but it works and is not hard although it is fiddly and if you are anything like me it will take a few attempts to peel back the shielding and expose the wires and then get them in place.
i found the best way to get the wires in place was not put them under the battery as the guide suggests but instead just put the battery in as normal and have the wires in at the very end. you will understand what i mean when you start but i have decided to take a photo and you can see what i mean here
http://sdrv.ms/OPDczX
everything you need for that this section of the recovery is here.
http://forum.xda-developers.com/showthread.php?t=892026
then you need to flash the sbf again. the one you have already flashed is fine and is the one you need so use that. (if for some reason it doesnt work after what i am going to tell you then ask again on here before you choose another).
next follow the guide to un-bricking your phone (linked below). if the phone wont boot and gets stuck after you have flashed the sbf you need to boot into recovery and wipe the data/ cache. reboot and all should be ok.
so follow the guide to the letter but when/ if (the phone wont boot past the moto logo) follow step 8. however you will find that when you press power on/ volume down that instead of motorola recovery you get a droid with an exclamation mark (this is ok so dont panic). to get into stock recovery from this position you need to press and hold down both up and down volume buttons at the same time for about three seconds and viola. then you can wipe and you should (fingers crossed) be good to go. if you dont understand anything then ask but it is relatively straightforward and if you do what i suggest above then you should have a working phone in next to no time.
http://forum.xda-developers.com/showthread.php?t=1828639
good luck

Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.

simon211175 said:
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
Click to expand...
Click to collapse
did you wipe the cache/ data after you flashed the sbf? if you didnt you may want to give it a go before you send it off. it may spring to life once you have done that.

I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.

simon211175 said:
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
Click to expand...
Click to collapse
It looks real bad. You sure the battery didn't die in the flashing process.?
Also try booting into recovery and do a wipe.

It's entirely possible that the battery died during the flash.
I cannot boot in to recovery - the phone doesn't get that far!
I've sent it back to be repaired. hopefully they'll do it under warranty, but if not it's only going to cost around £60 to buy out the remainder of my contract so if the repair costs more I've got that as a backup option.
Thanks for all your help guys.

You can cut an old wall charger but if you can't measure the voltage to know what wire have 5 volts and 0 Volts , and you can hold the wires 5V to plus on akku and 0 to minus and the supply would load..... you can left the batt out of the device...
Wait 10 till 15 min ,for save check if batt getting hot, boot into stock recovery and factory reset your phone
If you can't enter recovery you should be able to enter boatloader
If there is battery low can not program ..load akku.. or ready to program which means .... flash rom with rsd, factory reset , reboot, have fun
i did this two times, flash with low batt one of with not loading batt in dev - i charged with Nokia wall charger cable
If only battery is too empt and briked batt loader.......
If boot loader is briked by bad flashing search Google......
But i mean ciao loved defy
And don't forget : factory reset is always after you changed your rom....
Wiping cache/dalvik cache in only installing new nightly
Sent from my MB526 using xda app-developers app

so, here's my update.
You will recall (see two posts up) that I gave my phone back to T-Mobile on 20th August for a repair. I got my phone back today (+18 days). Here's how it went:
Day 1
Took phone to T-Mobile store. Informed them my battery had a strange lump, which I suspect had fried my phone somewhere. They advised they would send it to the repair centre the following day. No courtesy phones available so I'd be living in the 1980s for a while.
Day 10.
Phone actually arrives a the repair centre. I have no idea where the repair centre is, but I'm guessing really really far away.
Day 15.
Repair centre advise my battery is faulty and to replace would cost me £26.40 for a genuine Motorola battery. Advised repair centre that I told them my battery was broken, and asked why it took them 15 days to repeat that back to me. Also advised them I would rather by my genuine Motorola battery from Amazon for £11.95. Gave them a link in case they want to update their price lists.
Day 17.
Repair started on actual phone.
Repair finished. Yep - the repair took less than 24 hours.
Day 18.
Phone returned to store. it took 24 hours to get there, so I'm assuming the post travels down hill only on the way back.
Picked up phone from store, all set to complain about poor service etc. Noticed brand new battery I hadn't paid for sitting in the returns package. Kept quiet. Left store promptly.
So now I have a working Defy once more (Hurrah).
Obviously I've rooted it already in order to get Titanium Backup to restore all my apps.
Now I have stock 2.2 Blur running on my phone (Boo!), and with only a few months remaining on my contract, I'm not sure if I want to risk loading a new ROM again (I'll reread this once I've loaded a new ROM next week, for sure).

[Q] I need help. My s3 i747M shows zero signs of life.

So I wanted to install a new custom ROM and I all ready had one. It wasn't the first time. So, like usual I download the files needed and put them on my phone, boot into recovery and flash them ( but I didn't factory reset or anything because with the ROM I had I didn't need to for it to work I could just fix the not responding errors) Then i go to reboot and I wait. Nothing, nothing at all. Now I try to remove the battery and try again and now none of my buttons do ANYTHING the only sign of life there is, is when I remove the battery and plug my phone to a usb cable and attempt to charge it, all that happens is a red LED comes up. It's probably due to one of the things i installed on my phone that flashes a red LED when battery is low. Please help me with this. My last resort is to give my phone to rogers for them to fix it because I still have a warranty.
Specs: S3 i1747M Rogers
I had aokp jellybean 4.3 as my ROM
I do have a nandroid but its on my phone's sd card
Thank you for your time and I hope we get this to work.

Can you get into recovery mode or download mode?

FoxTrotz said:
Can you get into recovery mode or download mode?
Click to expand...
Click to collapse
No there's litteraly nothing I can do. pressing all the buttons does absolutely nothing. Just stays black and no signs of life

bump. I need help fast with this.

Not sure exactly what you did but I hate to say its sounds hard bricked. Mine was exactly the same, with only the red light coming on for about a minute when cord was plugged in with no battery. I screwed mine up with a file I grabbed without reading properly what it was for and in my haste I installed it. After I rebooted it never came back until I got it back from warranty with a replaced control board. Im guessing they didnt even check the internal memory or they would haven known what a dumbass i was since i voided the warranty doing stuff i had done before that mistake. Glad I had made a nandroid before i pooched it so i didnt lose anything after i got it back.

Yeah after some research I found out I hardbricked it but this isn't the first time and I had a warranty for both( different phones btw )times so I guess I'll just send it out. :c

could just be out of juice, leave it on the charger for around an hour then try and go into download mode.