Develop Bugs

T-Mobile Dash doesn't want to boot

Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
Take out the memory card and try to boot her up. If that does not work.. call T-Mo and get a new one

To get past the error 270, download the SDA Unlock app. That should get you past the error there. As for not getting past the Windows screen, I had that problem too. You should be able to get it working by hooking it up to the charger. I found that my Dash was not reading the battery as having a charge. I am not sure if I have solved the overall problem yet but, just in case, you might avoid using the USB as a charger and go with the wall charger. Just keep it on the USB long enough to sync and unplug.
Hope that helps

hacktek said:
Hey guys, i just got a new T-Mobile Dash and it's started acting up from day 2. Turned it on today and it doesn't work, it doesn't get past the Windows Mobile screen (from what i've seen this looks like a fairly common issue). After reading around i've tried to flash to numerous roms but only 2 of the official t-mobile roms have worked (others gave error 270, wrong vendor, wrong device, etc) but still the phone doesn't get past that screen. I've tried to do the hard-reset trick a bunch of times and still no go, any clues? Thank you.
Click to expand...
Click to collapse
do a hard reset hold da 2 soft keys and press the on button keep holdin da soft keys until u see a screen asking u do u want to do a hard reset hope dat works

Thanks for the responses guys but i've already tried all that. The only thing i haven't been able to try is do a hard reset with the wall charger plugged in, for some reason it doesn't matter how many times i do the steps it never shows me the black screen. I might be on the same boat as you because the battery i got with the phone is some cheap counterfeit chinese crap. I'll keep trying to get to the black screen with the phone plugged in but any other help would be greatly appreciated.
Btw, i can't do anything with T-Mobile because this is an unlocked phone i got somewhere else and can't return it so i'm stuck trying to make it work.

Check sticky to make sure doing correctly
Hard-Reset & Bootloader there is 2 x options there.

I was doing it right.
So after a million retries i got the phone to boot and do the cold boot thing. Then, i did the usual steps for putting a newer rom with WM6.1 on it (RUU_Excalibur_WM61_Kavana_080408_WWE). It worked, rebooted and went into the home menu, i thought i had brought it back from the dead until i inserted the sim. I got the sim failure message and when i pressed done it crashed. Now it won't go into the home menu no matter if the sim is inserted or not. Already tried to see if the sim was making good contact by putting pressure on it, no change.
This is too frustrating.

Ok so i've semi gotten it to work by booting it up without a sim, turning flight mode on, inserting the sim and then turning flight mode off. I get asked for my pin, the phone registers and i can make/receive calls. The problem is that a) it eventually loses the connection and b) i don't want to be doing this every time i turn the phone on.
Any ideas?

[Q] AT&T i747 stuck on logo

Could use some help here. I got an i747 last night, rooted just fine, used triangle away no problem. When attempting to resolve a status 7 error I could not get anything to flash in CWM and now it is sitting on the Samsung logo. I can get it to download mode but that's about it. ANY advice would be greatly appreciated.

NJD316 said:
Could use some help here. I got an i747 last night, rooted just fine, used triangle away no problem. When attempting to resolve a status 7 error I could not get anything to flash in CWM and now it is sitting on the Samsung logo. I can get it to download mode but that's about it. ANY advice would be greatly appreciated.
Click to expand...
Click to collapse
What did you try to flash? The more detail you give, the easier it'll be to find out.

Unlocked AT&T S3 dead after frozen logo screen
drx895 said:
What did you try to flash? The more detail you give, the easier it'll be to find out.
Click to expand...
Click to collapse
Mine is an AT&T locked i747 phone which I unlocked in India, but haven't rooted.
I had the same problem as above; I charged it all night as usual, but in the morning it was frozen on the logo splash screen. Tried restarting a few times, but it would again freeze on the same screen. So I removed the battery and let it rest a bit, but the same thing continued. Eventually during the course of the day, it stopped booting and now nothing happens when I restart it, it just wont boot.
When I insert another S3 battery, the flash "flashes" for a second and disappears, but the phone still doesnt turn on. Any idea what could be wrong? Battery is probably not the problem, since a working battery from another phone is not helping.
Any help will be much appreciated

jadeadly said:
Mine is an AT&T locked i747 phone which I unlocked in India, but haven't rooted.
I had the same problem as above; I charged it all night as usual, but in the morning it was frozen on the logo splash screen. Tried restarting a few times, but it would again freeze on the same screen. So I removed the battery and let it rest a bit, but the same thing continued. Eventually during the course of the day, it stopped booting and now nothing happens when I restart it, it just wont boot.
When I insert another S3 battery, the flash "flashes" for a second and disappears, but the phone still doesnt turn on. Any idea what could be wrong? Battery is probably not the problem, since a working battery from another phone is not helping.
Any help will be much appreciated
Click to expand...
Click to collapse
That's really weird. Unfortunately, I don't know much about how to fix it unless it was a custom ROM, sorry that I can't help . I beleive it was in General there was a "No question too noobish" or something of that nature. I had several issues before and OP has pulled through for me, so maybe it's worth a shot. Sorry again
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Picked up another S3 and got it working perfectly (rooted and on 4.3.1). Appreciate those that tried to help, could've been just a faulty phone.
Sent from my SGH-I747 using xda app-developers app

Bootstrap failed

Phone was on 20% battery. I put it on the original charger and activated the sync with my laptop. I noticed from the laptop that it stopped responding. I went in to find it off and very warm. It wouldn't come on so I help the power button down and it finally came on. Once it did I got an alert that said bootstrap failed. It kept coming up every so often. I shut it back off . Anyone know what causes this?

2ewGunnCiz said:
Phone was on 20% battery. I put it on the original charger and activated the sync with my laptop. I noticed from the laptop that it stopped responding. I went in to find it off and very warm. It wouldn't come on so I help the power button down and it finally came on. Once it did I got an alert that said bootstrap failed. It kept coming up every so often. I shut it back off . Anyone know what causes this?
Click to expand...
Click to collapse
There is no bootstrap for this device.
bootstrap is only for locked bootloaders.
Twrp is in my sig.

I am getting this too. I got one of the wireless fast chargers and charged from around 30% and now I'm getting the "Bootstrap failed" popular at the bottom of my screen every so often. It's really weird. 3 day old edge+ and not rooted or anything.

2ewGunnCiz said:
Phone was on 20% battery. I put it on the original charger and activated the sync with my laptop. I noticed from the laptop that it stopped responding. I went in to find it off and very warm. It wouldn't come on so I help the power button down and it finally came on. Once it did I got an alert that said bootstrap failed. It kept coming up every so often. I shut it back off . Anyone know what causes this?
Click to expand...
Click to collapse
Ok, So if were not supposed to get them, why are we? because im also getting it as well. Point is how do we fix this or is this something thats just going to happen from time to time?

I updated my Samsung pay and the bootstrap failed message stopped appearing. Perhaps it could be the culprit?

But it won't let me; it keeps saying "unable to download". I guess reset to factory settings will fix?

no I tried resetting to factory and it still comes up along with a pink line down the left side of the screen

I just started getting bootstrap failed popup from time to time on my moto g3. Does anybody here know what this really really means???

sw3 stuck on the four symbols

Hi,
yesterday while using the watch I got the message "shutting down". The battery was flat and after charging the watch got stuck on the four moving boot symbols. To cure this I have tried both software repair and update using the Experia companion. I have as well tried resetting to factory settings using the watch own recovery but all to no avail. Can anyone please help me how to proceed from here?

baronimus said:
Hi,
yesterday while using the watch I got the message "shutting down". The battery was flat and after charging the watch got stuck on the four moving boot symbols. To cure this I have tried both software repair and update using the Experia companion. I have as well tried resetting to factory settings using the watch own recovery but all to no avail. Can anyone please help me how to proceed from here?
Click to expand...
Click to collapse
In the recovery log it says in the beginning: couldn't find tzdata for local time, GMT!, posixrules!

baronimus said:
In the recovery log it says in the beginning: couldn't find tzdata for local time, GMT!, posixrules!
Click to expand...
Click to collapse
I now installed twrp and flashed SWR50_6.0.1_MWD49B This was successful but the watch is still stuck on the four symbols. I'm outta clues please help anyone

baronimus said:
I now installed twrp and flashed SWR50_6.0.1_MWD49B This was successful but the watch is still stuck on the four symbols. I'm outta clues please help anyone
Click to expand...
Click to collapse
I had the same issue and responded on your partition likeness. I can only get mine back to LP. I have tried the above ROM and several others to no avail. If you happen to get yours going again, please advise the steps you took...and I'll do the same.

Will do

baronimus said:
Will do
Click to expand...
Click to collapse
Did you ever get yours to fully boot to MM? I have since tried other methods and am still stuck on the 4 dots / symbols. LP still runs fine, but would like to get it to MM.

I did not unfortunately. Mine works fine on LL except for gestures. It does not update automaticly which is good, since MM gives four dots. Why it doesn't work beats me.
All the best

baronimus said:
I did not unfortunately. Mine works fine on LL except for gestures. It does not update automaticly which is good, since MM gives four dots. Why it doesn't work beats me.
All the best
Click to expand...
Click to collapse
Same here. Thanks for the response. I was wondering if you somehow got it to work. I have tried a couple other ROMs to no avail. I'm quite sure if the experts had the watch, they could figure it out, but when theirs do not act like mine (ours), it may be hard for them to reproduce a fix. Anyway, LP works fine and does quite well with the battery also...so, it is fine.

golfnut22 said:
Same here. Thanks for the response. I was wondering if you somehow got it to work. I have tried a couple other ROMs to no avail. I'm quite sure if the experts had the watch, they could figure it out, but when theirs do not act like mine (ours), it may be hard for them to reproduce a fix. Anyway, LP works fine and does quite well with the battery also...so, it is fine.
Click to expand...
Click to collapse
Hmmm right now I believe my watch is fatally damaged. It rapidly loses power (100% to 0% in a couple of minutes) when connecting to the smartphone. I think my (perhaps your) problems arise from a physically damaged watch. I think the battery is damaged and perhaps also the HDD probably due to moist having entered the watch. My problem started after a swim.
Best of luck with your watch, I think mine goes to scrap

baronimus said:
Hmmm right now I believe my watch is fatally damaged. It rapidly loses power (100% to 0% in a couple of minutes) when connecting to the smartphone. I think my (perhaps your) problems arise from a physically damaged watch. I think the battery is damaged and perhaps also the HDD probably due to moist having entered the watch. My problem started after a swim.
Best of luck with your watch, I think mine goes to scrap
Click to expand...
Click to collapse
Oh, sorry to hear that. Right now, I can get a solid 2 days of battery life with just having bt and reviewing notifications. I hope it does not go your route, but thanks for the heads up. Several times I had to wait until mine fully discharged before I could get it going again when I was playing around with flashing files. Anyway, I figured I was sort of lucky not bricking in since I had no clue what I was doing. So, I have just decided to let it be for now and concede to running it on LP.

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.