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?

How I (accidentally) got into download mode on my Bell i9000m

This is not the kind of recipe you'd want to follow to get download mode on a phone with 3 button recovery disabled, but this might clue someone in as to how to make it accessible under simpler circumstances.
This worked for me, dont assume anything:
- Got brand new Bell Samsung Galaxy S from store this morning.
- Tested general funcs, installed nothing.
- Tested every possible way of getting into Recovery or Download mode. None worked.
- Loaded up Kies
- Plugged in phone
- Clicked upgrade firmware
- Started the firwmare update process
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
- Popped and re-inserted battery.
- Came back with "disconnted" graphic (phone-warning-pc)
- Held HOME, then VOLUME-DOWN, then power (with usb plugged in)
- Held till it came back in download mode.
- Voila!
I then used Odin to flash JH2 onto my phone. Phone works fine now. Impossible to get into recovery or download mode again.
Conclusions:
- If you are completely mad, you could try this technique to get into download mode.
- The blocking of the mechanism is clearly software, not hardware.
- Erasing or damaging the firmware erases the block.
- You may not be able to get into download mode voluntarily, but when you need it most (ie phone bricked) it's there for you.
I hope this somehow ever so slightly advances us toward a hack or fix for this problem. Good luck all.

davidke said:
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
Click to expand...
Click to collapse
Glad you got it working. I'm able to boot into recovery/download mode when my phone is warmish. Try explaining that!

risky stuff good job

mInes saying device cannot be updated

taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
Because you already have the latest....
Smart to test that method when brand new. In an emergency that isn't a bad thing to try. But they need to fix that, we bought the phone in good faith that it was complete and it might kill warranty but we should be able to get into download mode as designed. If we do then there isn't an issue with people wanting to exchange them cause we can fix our mistakes. Isn't that the better less evil way?...

taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
God I hate that angry face emoticon. It's like QQ more red face dude!
Anyway, mine says that too. Who cares. Just use odin.

my phone will only go into download mode if the back is warm. i flashed it 4 or 5 times yesterday and each time it would not go into download mode until i left it plugged in long enough for the back to become a little warm, then i could enter download mode at will

I have to sacrifice the lives of 1000 virgins to get mine into recovery/download mode Pain in the ass...
[/sarcasm]
Actually mine works fine. Mind you, I've had a locked out one. It Bricked

it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you

AllGamer said:
it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you
Click to expand...
Click to collapse
I had that picture on my screen yesterday and I almost swallowed my tongue! I was able to get it into download mode and flash with odin. Pretty scary as I mentioned earlier that my phone needs to be warm for it to have any chance of entering download mode.

from what i can gather, people that are able to to get into download mode, it was because it was working fine to begin with, just not hittings the buttons in the correct time or sequence
because if the heat mode worked, or the usb plugged mode worked, then it should have worked as well on the one i sent back for repair, but it didn't work because i tried those methods already

I definately cannot get back into download mode. I tried 100 times. Yet, yesterday, when I had the black screen of death, I could do it at will easily.
So there are circumstances that will let you in and others that wont.
For some it's "warmth", for me it's when it's bricked. Or maybe I killed a virgin that day... not sure.

i like the new term "Black Screen of Death"
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe

I can't get mine into d/l mode for the life of me.
question: I've had my phone for about a month now. Is it too late? I'm not even sure if I have the receipt (although my buddy is a manager at the bell store)
Should I replace mine? and if so, how do I go about doing it ?
Is it really necessary?
Can't you get into download mode via ADB ?????????????

i'll say wait for froyo to be out
then see if Samsung includes a fix for the 3 button issue.
if they don't or if the froyo upgrade dies half way
then you can comment it all here
http://www.facebook.com/samsungmobilecanada

AllGamer said:
i like the new term "Black Screen of Death
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe
Click to expand...
Click to collapse
plz help to bass this problem

I dont think you can "brick" an android device. I've had customers come in with all sorts of failed atemps of rooting and hacking and have fixed them all.
Device list:
Samsung Galaxy s
Samsung Galaxy
Samsung Apollo
HTC Wildfire
HTC Desire
Sony X10
Sony X10 Mini Pro
LG Intouch Max
T-Mobile G2
T-Mobile G1
There are a few things like when people dont make back ups of there efs folder etc but that is just user "school boy" errors by people who would play Russian roulette with a fully loaded gun and go first.
Why do people jump into things without thinking and expect others to fix it when they f**k it up. My advice is that if you cant afford to buy a new one when you brake it then leave it alone.

Flashing the software shouldn't "brake" it. It shouldn't break it either. Point is, the phones have a method of recovering from a bad flash, and that isn't working for some of us. We shouldn't have to be ready to buy a whole new phone, just to try different software.
Sent from my GT-I9000M using XDA App

Galaxy Nexus freeze after unlock **UNROOTED** troubleshooting

Alright, so here is what's going on.
I had my alarm go off earlier today, got up, unplugged my phone like normal. I swiped off the notifications I didn't care about like a tapatalk message etc. I noticed that Google Current's automatically updated. I'm sure that's no huge deal.
I locked the screen and went about my day. I tried to swipe to unlock, and the phone freezes and reboots. The phone is responsive until you unlock it, then it just freezes and reboots.
Tried safe mode once, and it worked fine. I then turned it off, and tried normally booting again, same freezing and rebooting. So I went to go back to safe mode, and now safe mode is doing the same thing, which means that a factory reset is now out of the question.
What the hell man.
Specs:
- Samsung Galaxy Nexus
- All stock apps except added Facebook and Tapatalk
- Jellybean 4.2.2 software I believe. I'd double check if I could.
- Still locked and unrooted
Any ideas on where to go from here? No warranty, so any ideas would help
It turns on, goes to lock screen. Then freezes when I try to get anywhere from that lock screen. Even on safe mode.
Then it will reboot automatically after about 30 seconds.
I should note I received a text in this time, and thought maybe just pulling the notification bar down and going straight to the text would work. The notification bar works, but when I hit the text, it froze the same way.
This must be some sort of self check or some Android process crashing. But I can't utilize safe mode to fix it.
Any ideas on what to do? I know there are threads with this problem, but this involves an unrooted phone, of which I have seen no threads, or threads with answers. I am not experienced with getting too far into Android, so just a direction to go, or something to try when I get home would be awesome. (At work currently)
The only options I have right now are the options upon booting with the volume down, which are Start - Restart bootloader - Recovery Mode and Turn off. In this screen, here is my info:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro 16GB
HW VERSION - 9
BOOTLOADER VERSION - PRIMELA03
BASEBAND VERSION I9250UGLL1
CARRIER INFO - NONE
SERIAL NUMBER - xxxxxxx
SIGNING - production
LOCK STATE - LOCKED
In recovery mode, I see a dead android guy with a red triangle and an exclamation mark in it.
I realize you guys probably get a lot of dumb questions so I tried unloading all the information I could. My replies will be 5 minutes apart, as I'm new and I see that's a restriction on being here.
Thanks in advance

You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.

Daedalus93 said:
You can try unlock the bootloader (it'll erase your data so be careful) and then try flashing the oficial google image via fastboot and see if it solves it.
EDIT: in that screen of red triangle press up and power at the same time to show the options. There you can do a factory reset to see if it solves it. No need to unlock the bootloader that way.
Click to expand...
Click to collapse
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.

slipstreamconversion said:
Got it. It works now, but curious, is this a common occurrance? I have no idea what caused it, which worries me. But it seems to be working fine.
Wasn't worried about data loss, I haven't had the phone for too long yet. I plan on just installing the minimum apps. The point of me not unlocking it was to avoid issues, but I had more luck with unlocking it than leaving it locked.
That said, I wasn't aware you had to hold the vol up and power button to get to the options from the dead Android screen. That was an oversight on my part when I was looking up for data.
Words cannot explain how thankful I am, so thank you
Moderators can close this thread if needed.
Click to expand...
Click to collapse
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme

Daedalus93 said:
No problem everything should work as intended now. What happened was a bit strange indeed. It it happens again with everything in stock then there is a possibility that it is faulty hardware and you should replace it. Maybe it was some configuration bug and nothing extreme
Click to expand...
Click to collapse
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again

slipstreamconversion said:
Fauly hardware can cause this issue? I baby this phone, has yet to be dropped (let's admit, it's inevitable), the only thing it's seen is three drops of water that fell off my sunroof onto it. I immediately grabbed my phone and wiped it off, but it was all on the screen, not in the speaker or anything.
Either way, I'll keep an eye on it. Thanks again
Click to expand...
Click to collapse
Yes. My phone recently was stuck on a bootloop and I've already sent it for repair. Yeah drops are never good
No problem

[Q] touch screen issues after update

Hi all,
My Zenwatch had issues with a recent update basically it failed mid-update, the watch rebooted & seems to have partially loaded the OS.
The screen is not responding to touch but works on tilt, notifications etc all were working ok too.
Unfortunately i didn't turn ADB debugging on so i can't access it via PC/ADB either, now its lost my phone pairing too and as mentioned i cant access the swipe to do anything helpful on the watch.
As i bought the watch on holiday Asus UK aren't entertaining any help under warranty & can't suggest a repair shop either (though as i cant turn on ADB im not sure what they can do anyway!).
Have i now got a paperweight or is there a way of reflashing the Zenwatch without ADB turned on on the watch?
James

I got the same problem with touchscreen so i send it back to asus

Would love to but got the watch on holiday in the usa and now back in the UK..
Asus are saying return it to where you bought it.
Not much of a warranty if that's the case :-S
Sent from my D6603 using XDA mobile app

call Asus us

If you can get into recovery mode, you might be able to re-flash the update zip. It shouldn't matter that you don't have debugging turned on to do that, I think. There's some information on how to get to recovery mode here:
http://www.tomsguide.com/faq/id-2411652/reset-android-wear-watch-factory-settings.html

darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James

Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
Click to expand...
Click to collapse
I don't think that matters. It should work the same on the Asus. I've used recovery mode to sideload updates on mine in the past.

Don't send your watch across the pond!
Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James
Click to expand...
Click to collapse
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.

Doc Ames said:
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.
Click to expand...
Click to collapse
Tried to get to Fastboot, sadly didn't notice any difference in bootup - might indicate more of a hardware issue than software.
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James

Jamesb4uk said:
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James
Click to expand...
Click to collapse
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.

Doc Ames said:
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.
Click to expand...
Click to collapse
Yep firmware mismatch sounds about right. Sadly no luck with the fastboot at all.
Might give the jumping a go - got nothing else to loose, then i'll ask a friend of mine to return it.
Thanks for your help here Andy.
James

When you get the new one I bet I know the first thing that you're going to do

again, why not call Asus us? I had an issue with mine and they quickly sent me an rma label

Lenovo P2 display black after recovering from a bootloop

Hey guys.
I am posting this particular issue because while I could find something similar to this issue (recovering from a bootloop for this very device), I couldn't find much in case your screen remained black afterwards.
I know why the bootloop took place (or at least I'm almost sure I know why):
-Via dr.fone, I chose the root option. This is a naïve move, as I know that one-click rooting options basically never work. Well, I know this now at least. However, the root never happened, as my device didn't even have OEM activated (there are some issues happening in this regard with lenovo). The program just couldn't continue, telling me that my phone wasn't registered in the data base or something like that. I was honestly just messing around because I didn't have OEM access, just wanted to see what error would pop up.
-The bootloop happened the day after, about 16 hours later. It also happened randomly, while the phone was idle without being connected to the PC. The screen was black, but I knew it was bootlooped because it would vibrate consistently every 10 seconds or so.
-If I pressed the Up+down+power buttons simultaneously, the blue LED in the top right corner would light up and a very long vibration would happen. There's a thread on this issue already, and adding a new firmware solved this.
-I tried to solve this by using ADB to add the stock firmware again. The bootloop stopped after this and the phone would charge. It didn't while bootlooping.
-I tried to factory reset and nothing happened. Except that my USB debugging option is now turned off, which makes things harder because I can't find a way to turn it on without having access to my phone.
I was wondering if there'd be a solution for this very situation. It's also worth noting that my screen is basically shattered, but I don't think it's an LCD issue because these two things happened at the same time. I find it too much of a coincidence.
Do you guys know what could be going on? I also wiped the cache data, even though my phone was factory reset just to give it a shot.
I very much appreciate your attention.
PS: this is literally only the display and the touch screen. Even the fingerprint sensor works.

Did you unlocked bootloader before root ?

Shreyash01 said:
Did you unlocked bootloader before root ?
Click to expand...
Click to collapse
No, the root didn't even take place. I tried to unlock the bootloader, but the Lenovo servers are down for that. So my bootloader is not unlocked.

I think that is the reason..
Your bootloader is not unlocked. You must have to ask someone before doing..
I think costumer care is the only option.