Develop Bugs

Phone bricked, unbricking TUT not working.

I was updating my Dash the other day to Ookba's latest rom when I received an error message. It gave me instructions on how to fix it (loading it in bootloader etc.), and I received a message saying it was successful and the rom would continue updating. I received another error message saying the rom was corrupt, and the program shutdown. My phone will not power up now. It was at(or near) full charge while reflashing, but will not turn on regardless of the button combination I hold while attempting to power it on.
Any ideas? Thanks!

what rom did you attempt to load in the bootloader? it should have been the factory rom..if not, then that is probably the root of the problem....as far as it not powering on now...I leave that open to the forum...cuz' I have no relevant advice on that one....

when trying to do the gold card method to unbrick my phone, it say Invalid certificate ..? wats this and how to fix it.

I was trying the "[ROM][EXCA][WWE][* 3VOLUTION SERIES *][WM6.5 STD 21854][Build 3VO.3.00.112509]" when it locked up on me, and still hasn't been able to power up.
Today when plugging it in after a week of letting sit, a red led light showed where the normal orange/green led would normally light up when charging/charged. The light stayed on for a few seconds, then shut off. Nothing else though. Any other suggestions?

allthrottle said:
I was trying the "[ROM][EXCA][WWE][* 3VOLUTION SERIES *][WM6.5 STD 21854][Build 3VO.3.00.112509]" when it locked up on me, and still hasn't been able to power up.
Today when plugging it in after a week of letting sit, a red led light showed where the normal orange/green led would normally light up when charging/charged. The light stayed on for a few seconds, then shut off. Nothing else though. Any other suggestions?
Click to expand...
Click to collapse
Red light my friend means your battery is gone, probably your phone is not bricked maybe it just needs a battery replacement

I am having the same issue, except that I can place the battery in another Dash and it boots up just fine, so I am assuming it is not the battery. I will buy another one to double check. My problem is the same as which is stated above. Can anyone help? Thank you.

Just an update to see if I can get anymore suggestions. Hadn't touched the phone since the last post. Bought a new battery for it this weekend and it's still dead as ever. Won't boot at all. Not into bootloader, nothing. I get absolutely no response holding power+cam or softkeys+power.
Any advice? I don't absolutely need the phone as I've picked up a G1, but it would be nice to have this working, or at least trash it if it's junk.
Thanks!

Everyone else stumped too?

Have you connected to the wall charger to see if you get some response with your new battery?.

Just unbricked mine after being dropped again by the girlfriend. Try this, plus usb cable into device, press the camera button only. See if that gets you into the bootloader screen. If so, flash the oem build and go from there.

Tried it plugged into a wall charger for 3-4 hours, car charger for another hour, and computer/usb for another hour. No response anytime.
I'll try the camera only method when I get home later.
Thanks!

Just tried plugging it into the computer and holding only the camera. Didn't work. Tried that, tried holding power+cam, power+soft keys etc.. What's weird is I had the battery cover off while doing this, and the battery slipped out while I was holding cam+pwr, it actually loaded into the multicolor(bootloader?) screen twice, but would shutoff within a few seconds. Now I'm back to no response from it.

Finally got it to stay on the boot screen without turning off, but can't get it to establish an activesync with the computer so I can't flash it. The computer is obviously detecting it though, because I see an icon that says "remove smartphone usb sync".

The phone's FINALLY working again! Thanks again guys! I was a couple of days away from junking the thing! I couldn't get Ookba's rom to flash it, so I went back to the unbricking tutorial and saw that he recommended grabbing the factory rom to flash it. I did, it worked, and I just flashed it again using Ookba's rom.
Took quite a few months, but it's back! Thanks!

[Q] Phone turned off/crashed

My phone had about 60% battery last time I checked but I just went to unlock it and the phone didn't respond. I tried to turn it on by holding the power button wasn't getting any response from the phone
I've plugged it into the charger and didn't get any charging light so again I held in the power button and nothing! I kept trying and eventually the buttons lit up and it started to boot...
I've had the phone for 2/3 days now and this is the first problem I've had but it's still a little worrying!
Just wondering if anyone else has experienced anything like this? I'm on the 1.26 software.

I had this on one occasion when adding the messages widget to the home screen. When I powered the phone back on I got a request to send HTC a bug report.

Arthur Hucksake said:
I had this on one occasion when adding the messages widget to the home screen. When I powered the phone back on I got a request to send HTC a bug report.
Click to expand...
Click to collapse
Interesting. I didn't get the bug report.
I'm hoping it was just a software bug but I haven't seen any other complaints on the forum yet.

I have just noticed a problem with my phone too, turned it off for the first time last night, on start up this morning it started ok but did not load completely and froze for about 30 seconds on the home screen with no app icons showing. It then rebooted and started up ok with the bug report. I then turned off the fast boot and tried again, it booted correctly first time. Would there be any particular apps which would cause this to happen on fast boot?

Hey mate, currently having the same problem as you. Have no clue what to do. My battery was at about 50% and it just crashed when i was playing riptide. Now it wont turn on or anything. Even when the phone charger is plugged it, it wont budge. Have you found a fix?

[Q] Help!! a100 Blackscreen

i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible

wondering if anyone can help me...

frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.

pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged

frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.

Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.

i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen

same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks

A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!

Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia

same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.

If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.

This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.

I highly doubt they even CARE when sending these in. They will void for physical damage most likely.

tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.

Note 2 Rogers Canada acting very very strange

Hey Guys,
So i've done some research all evening here and I've done nothing different than i'd do any other day with the phone and all of a sudden today around 6 PM eastern the phone started acting up. I came home from work plugged it in and it started to lag and then froze, finally unfroze and got that error " Unfortunately, %1$S %2$S has stopped running. I only have the option to click (ok) So I would do that and I thought all was well, turns out this is not the case. When this error pops up it also disables the phone from charging. I unplug and plug back in, the phone starts to freeze and the error comes back. I've been doing some online re-search some people say it's a synch issue with google and to turn synch of, did so, still same error. Some people have said unplug charger, power off phone wait 10 seconds, plug charger back on and boot up, this also did not resolve my issue. I will say that if the power cable is not in the device, it works fine. After about 2 hours of trying different things, I plugged it back into the charger and the phone started acting out really strange, changing from screen to screen and indicating " The dock is connected" I don't own a dock and the phone has never been into dock. I'm using the stock charger that came with the Note 2.
I will say I have TWRP installed and I've been using the JEDI X Rom for this phone without any problems. I thought, okay well none of this is working maybe it's the rom acting up, so I decided to go into recovery wipe all cache & system and re-installed the rom, same thing. The dock is connected, phone freezing and Unfortunately, %1$S %2$S has stopped running. So, I re-did everything again, wiped all cache systems, fixed permission and put the stock rom back on the phone. Now the phone is indicating in stock mode that the "dock is connected" when really it's just the charger. The phone is going into the time out then pops back on automatically all by it's self. Not getting the Unfortunately, %1$S %2$S has stopped running anymore though. the phone is 3 weeks old, and i'm at a loss here as to what I should do next.
Any suggestions, if not, Is there away to erase the phone "call" time so I can get it down to below 30 minutes so I can return this one for a new one?
Thanks,

Well, after hours of reading, I came across this post for an Android EVO phone and it mentioned something about a connect point of the charging port in the phone and said slightly bend the charger cable when it's attached inside, I tried this at a last cause and everything fixed itself, I re-flashed Jedi X and all errors have cleared itself. I find it strange because I'm very gentle with inserting/disconnecting these cables...
Thanks,

I'm not surprised. I've had similar issues with a S2 and other Sammy phones. In fact my brothers Galaxy S as well. He had to get the whole board replaced. I hate MicroUsb. Although its nice to have a generic sync port that is the same across almost all Android devices, this port needs to change.
Just my $0.02. Glad to see you figured it out. Knock on wood my Note2 hasent had these issues yet.
Sent from my SGH-I317 using xda app-developers app

Random Reboots?

I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?

I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.

I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:

have you downgraded?
and can you help me with my problem?[

AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.

ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic

I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.

Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app

adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)

Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.

My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.

Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.

Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.

k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.

Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.