Develop Bugs

[Q] Phone won't power on. Bricked?

Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA

Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app

Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.

These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..

All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!

[Q] Phone won't charge nor Fastboot / Flashmode

Hey everyone,
after dropping my S3 two days ago which lead to a highly damaged screen (not working anymore) like two days ago, I got a new Arc S from a friend. As I said, the phone is new, and unused.
I've been trying to update to Android 4.3 yesterday, followed some tutorials I found here. I installed the Dark Kernel trough fastboot, then tried to flash the Dark JB rom. But nevermind, this didn't work, so I decided to flash back to stock kernel + rom.
I succeded in doing this, but had the, as I see, common 100% battery problem. Didn't think about one thing. The phone won't charge when the battery is on 100%. So my battery went empty, but whenever I want to charge it, it doesn't because the phone kinda thinks it is on 100%.
Now, I wanted to wipe the battery cache, which isn't possible because I cannot load fastboot mode, and what I've been trying aswell, cannot load flashmode neither.
I don't know what to do to be honest, I hope some of you guys can help me out!
regards

The battery issue can usually be solved by flashing new kernel(s), then returning to the original one.
If you have another Arc (S) available, charge the battery there, then put the battery back and then try to connect. Phone can not be detected due to no power at that moment.

Someguyfromhell said:
The battery issue can usually be solved by flashing new kernel(s), then returning to the original one.
If you have another Arc (S) available, charge the battery there, then put the battery back and then try to connect. Phone can not be detected due to no power at that moment.
Click to expand...
Click to collapse
At first, I'm sorry for those awful grammar mistakes I made in my first post
I do not have another SE mobile available to be honest, but I understood what you mean. Thanks for answering me this fast.
I charged the phone for like an hour when it was turned of completely, so now it is up again (idk for how long). Trying to enter fastboot now.

[Q] Sprint Phone boots up only when plugged in. If unplugged it goes into a bootloop.

A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.

bkjay78 said:
A few days ago, I flashed a 4.4.2 rom and kernel. I noticed that it was randomly rebooting so I went ahead and flashed another rom, this time without a new kernel. Everytime I flashed I did a wipe of the device. When I did this the Galaxy Note 2 splash screen would come up then the rom boot logo. But then it would go back to the splash screen and the boot loop would continue. I ultimately discovered that the phone would get past the boot loop sequence if either plugged in via USB or AC. I set up my phone thinking it was cool but once I unplug it, and start using the phone, it reboots itself and starts up the boot loop cycle again. I've gotten fed up to the point that I unrooted the phone back to a stock 4.3 rom thinking that might solve the problem but even with the stock rom the boot issue persisted. I've since then used Odin to put new recoveries in hopes that this could be the issue but still the same problem persists. I've had to start carrying around my laptop with me to and from work just to have the phone plugged in because otherwise it will eventually shutoff and start the bootloop. I'm usually pretty good at solving these issues but right now I'm without any answers. I haven't checked to see if possibly it could be a battery issue but I haven't had an opportunity to find someone with a Note 2 to try out this theory...has anyone had somewhat remotely close to a similar issue and if you have, did you solve it? Someone help...lol otherwise my Note 2 may have seen it's final days although I'm not in the market of finding another phone right now.
Click to expand...
Click to collapse
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.

jlmancuso said:
I would suggest that you try another battery. Kinda sounds like an issue with the device not getting proper power supply. If I were you I would try finding a friend or coworker who has the same device and try using theirs. If it boots and runs then a replacement battery is all you need. I have had this issue with a previous phone (HTC 3d) but not this device.
Click to expand...
Click to collapse
Thank you for the reply..I will check to see whom may have a Note 2 at work. The ones who did have other phones now I believe. I know of one co-worker who has a Note 3 but not sure if that would be something that I could try..I'll report back tomorrow with my findings...

Yeah I doubt the N3 has the same battery but hopefully you can find someone.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Random bootloop, Can't find a fix

Good morning guys,
Last night, i was just using my phone like normal when it froze, crashed, and began to bootloop.
I've tried battery pulls, I've tried to factory reset using the volume down + power combo, I've tried to wipe cache and enter safe mode but none of this worked
I was on 10b firmware but since none of the above worked, I tried to KDZ to a stock 11a which still keeps my phone at a bootloop. All I see if the LG logo at startup and a crash.
do you have any suggestions on how I can try to fix this? according to reddit this random bootloop has been happening to multiple people
thanks in advance for your help

It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.

Katmeat said:
It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.
Click to expand...
Click to collapse
yeah it's definitely weird. I was rooted on 10b holding out for a bootloader exploit down the line.
I called up verizon and theyre shipping me a new g4 since it was still under the 1 year warranty. I hope it's still rootable with the firmware it'll ship with

Same here
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis

I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.

Katmeat said:
I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.
Click to expand...
Click to collapse
yup, i kdzed up to 11a and it went from modified status to official so hopefully that wiped everything on my phone too. My new one will be coming in tomorrow

I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.

Katmeat said:
I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.
Click to expand...
Click to collapse
Is there any downside to refurbished devices?

pfizzle said:
Is there any downside to refurbished devices?
Click to expand...
Click to collapse
I think not, and I actually prefer buying factory refurbs in most cases when possible because you are assured of the product being carefully inspected. In this case, my phone looks brand new and is performing just fine. The initial heat concern has gone away as the phone has settled in.

Please Help!!!!!
I'm trying to help my sister out who is in Ecuador right now. Her phone was a little slow today and kept going to the red verizon sign - so she turned it off and took the battery out.... when she turned it on it said the SD card is blank. She has 800 pics on it from her trip and is wondering if there is anything to get them back???? Please help!!!! Any suggestions would be helpful!

weird i had the same thing happen a few days ago also...using new phone now.

This issue happened to me out of no where last week and had a replaement sent. Wasn't rooted
Sent from my VS986 using Tapatalk

same problem here ...
rooted device. nothing special today .. and then: bootloops.
When i remove the battery for a longer time, sometimes the g4 boots properly. But after a few minutes it'll bootloop again.
Any ideas?

FootballFan141 said:
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis
Click to expand...
Click to collapse
What's the manufacturing date of the phone that failed? I'm trying to figure out if it's just a matter of time (the May ones failed first, then June), or if it's only May boards with the issue.

Dead AQ4501

Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(

Saad6459 said:
Nearly At the end of every month my my phone gets into some kinda software problem (example : Google has stopped working then process.android has stopped working and some other random **** which is quite annoying) whenever this happens the phone restarts on its own and never turns on,i mean it does but is stuck on loading screen.(note: I dont do anything stupid which might harm my phone. )So i have to flash my phone with spflashtool it.This time when i flashed the phone it didnt turn, i held the button for long but it was of no use, so i thought it might be the low on battery,but when i put it on charge nothing popped up... it wasnt charging. Then I thought it was the battery but my battery wasnt swollen and the day before I flashed it,it was running fine with full charge. , there was no sign of battery problem anytime i used it the consumption was normal.
Please help me fix this problem, and I also want a permanent fix to the software problem too.
Any senior member please help..
TIA
:fingers-crossed:
Update:I flashed the phone with new files but results were the same :'(
Click to expand...
Click to collapse
same happens to me bro my android one is also dead same problem as yours when i tried with sp flash tool its end up with this error..... scr shot attached

☹
Bro,I flashed it thrice after but it didn't give any errors,but sadly it just wont turn on
If it were permanently bricked then it wouldn't have detected the phone...and bro lemme give you a suggestion,try changing it to firmware upgrade instead of download only.
Thanks for the reply

simmilar issue
same problem pls help in my case when i charge not charging the battery indicator just pops up and out i think its a battery error put in a new battery try to boot up nothing try to go in recovery nothing i have nothing to boot up from i think ill still try using fastboot and/or flashing and reporting back(ima try dead usb flash using spflash tool)

okay flashing works perfectly now i just need for figure out if the problem is with the charging/battery or the phone is dead

Same Problem
Bro, i have run into exact same problem. I even went to gallery and gave them the phone, they said they will charge 1500 as motherboard is dead but after one month they returned to me the phone saying that motherboard is not available. They are taking almost 14 days to return money so i have to visit again on 3rd june. But coming back to problem i have tried flasing with and without battery for 3-4 times. every times it shows success but the phone wont start. Even memory test was all fine. cant figure out what's the problem. i have tried both download only and format+download mode but nothing seems to work, If anyone finds a way to fix the phone please tell ASAP.

Same problem as the OP, mine's bricked as well after it began showing random FCs. Flashed KK and LP firmwares using SP Flash Tool but to no avail. The flash was successful tho but the phone never booted up

I'm kinda stuck in a similar situation. Let's start from the beginning -
When I got my Redmi Note 3 I stopped using my Canvas A1 and vaguely i remember that it was having software issues, rather than fixing it I just kept it away for a lot of months, and vaguely I remember that it just needed some flashing of rom and it would've gotten fixed.
And after all these months i'm need of this phone again. I don't remember much in depth details of the processes involved with it like flashing stuff etc. But I gathered as much knowledge as I could from the docs I had stored as backup & from the internet.
And IMO I think the flashing process was successful, but the screen is not turning on. Only once when I connected it to PC, the charging battery sign appeared(flashing thrice) but that was it. Nothing after that. And whenever I connect it to PC it detects the phone.
For now I've given it to a repair guy but I don't have much hope. He was saying that it could be just software problem, but I don't agree. If a smart person could comment on this thread so that we all could get some benefit out of it, in order to solve the situation or at least in my case I could research on something specific in the meantime.