Hello,
First, sorry for my english
So, I had a S2 for a while, and one day, when trying to get another ROM etc, I unplugged the phone at a wrong moment, and I think the motherboard was dead. I bought a new motherboard on Internet, but the power button was broken (and I don't have tools to repair tiny things)
And when I try to boot him (the tricky thing to plug usb, remove battery and get her back quickly), it boot up normally, and the screen become unresponsive after 10 sec. I think all other buttons works, I have the vibration. And after 10 other seconds, it restart.
Another strange thing : if I plug a mouse with OTG, I can move the mouse, but after these 10 sec I can't click anywhere, but still move. And it restart.
(It's not 10 sec perfectly, it's less)
Like it's a new motherboard (occasional, so it's the configuration of the man who sell me the motherboard) the usb debugging is off, and I don't have the time to set it on.
So I can't use ODIN, I can't get to recovery or dowload mode.
Any advice ? Thanks
Related
I have a Cingular 3125, working fine for weeks, happened that two days ago, I was charging the phone and transferring files to my computer via Bluetooth, nothing unusual, then it just got frozen, nothing responding, so I just took out the battery to manual reset the device and reinserted it, then tried to turn on the device, but it refuses to boot, no lights at all, also when I attach the phone charger, it doesnt show the usual orange led when charging, but I can feel that the phone gets warmer because the charger is attached and then after a while it gets a bit cooler, just like when it finishes charging, the usual behavior, but again, no lights at all trying to boot it or even attaching the charger, I've tried taking the battery off for hours and nothing also, and I wasnt overclocking the phone... would you say it just died? or maybe someone had same issues and solved it someway? thanks.
try this
OK, I don't remember where I read this, or the exact procedure, but give this a try.
remove the battery, press and hold the red call end key (power key) for 30-45 seconds. insert battery and do a hard reset, IE.. power on holding the 2 top soft keys while powering on the phone.
this method is supposed to clear any mother board issues and reset the phone. It has been a couple of years since I read the procedure so I am not sure if this is the correct way, if it does not work, try the same thing, only try taking the battery out, then put it back in and press and hold the power key for 30 - 45 seconds.
may or may not work, but can't hurt to try.
i had the same problem with startrek which i had bought from eBay
one more advice - try to hold record (notes) and camera buttons and insert an USB cable to your PC, it should enter to Bootloader mode
well, I have dissasembled the whole thing, I havent reached anything, even disconnected the backup battery, nothing, have checked battery with a multimeter and is full loaded... in short, someway the cell phone seems has just died, Erofich, to enter bootloader mode, the phone must turn on, it just doesnt want to start at all, no lights when connecting charger or USB cable... I'm sad because it was working fine with no problems for three months and more sad because it's the end for me to windows cellphones for a long time, I've invested a lot in this phone, accesories, unlocking, and even the same day it died also bought more memory and a neat skin cover and I'm not in mood to invest more in a cell phone so I'll use a spare crappy feature phone.
Thanks for your support.
one last effort
You could try one last thing, this has worked for me with a couple of startreks,
take the phone apart, and take the motherboard out, use a hair dryer to heat the motherboard, don't get crazy with it, but using the hair dryer on the high setting for about 30 to 45 seconds at about 3-5 inches, might revive the phone. (don't heat the battery, just the motherboard)
Put the phone back together while it is still hot (but not so hot that it will burn your fingers) and try to fire it up.
This has worker for me in 3 cases (phones that I bought off eBay that had the same symptoms as you have described)
good luck
big problem!!!!!!!!
I have been struggling to flash (again) the great pro V2 rom, but I always used my VMWare based XP windows version on my Vista laptop. Today I could use a genuine XP Laptop and I could make a connection and start the upgrade!
Sounds good? That's what I thought too, until the upgrade stopped at 70% (and I didn't touch anything), because of a connection error. I followed the text on my PC screen and I finally it started flashing again for a few seconds and then my startrek suddenly restarted, but it stops at the first splash screen! I tried to get my device back to bootloader mode (push 2 soft buttons and start), but no bootloader mode, only the 1st splash.
I solved the problem.
Hi guys, Today my X10 black running on android 2.1 firmware suddenly dead. I was on a call and suddenly the touchscreen is not responding at all. I can not get it to silde to unlock or what so ever. I've tried take out the battery to turn it off and put it back to turn on and tired to Put it on computer with the sony software to repair it. But none of those works. The touch screen seems to respond once after i touch it a thirty or forthy times. But still i have no way to silde to unlock the phone. Is that means my phone is brick or just the touch screen is broken i have to buy a new one to replace it? anyone has the same problem and any solution for it?
If you can try booting into recovery turn phone off then on while holding the vol up down keys see I'f you load in If you do then use volume keys to navigate and do a restore
Sent from my PC36100 using XDA App
I just tired your way, but the point is i can not use my touch screen, i have no way to turn off the phone. WHen i press the power button it shows me the turn off phone option, since the phone is locked, no matter how many times i press it still not respond to me at all. I can't get phone into recovery mode. The only way to turn it off is by take out the battery. THanks anyway.
So.. take out the battery and try to boot it up in recovery mode.
Still got not luck. Its not working
When you've pulled the battery.. and you re-insert it and try SEUS...
Are you holding the back button whilst you insert the USB cable? (at the prompt when SEUS tells you too)??
Your other option would be to download flashtool from here and try to install a ROM that way (also uses the "Flash mode" boot up..)
"When you've pulled the battery.. and you re-insert it and try SEUS...
Are you holding the back button whilst you insert the USB cable? (at the prompt when SEUS tells you too)?? "
I did this, tried 2 times it gives me a fresh firmware after i install it, But the result is the same. When my phone started up, it ask me to change language, and no where how I touch it just rarely responds to my touch. Just like the touch screen is not responding it. But it super rarely respond once after thirty keep continoues touches.
If new firmware isn't helping its probably a loose connection or worst case a bad component. Might warranty if its covered. If you don't still have warranty you might try disassembling it and checking connections. Someone just posted a video on x10 tear down. Was it dropped at any point?
Sent from my Delorean using a flux capacitor!
yyhua
This sounds exactly like the way my screen is behaving. Did you ever find a solution?
Hello,
A friend give me a bricked Archos 101 G9. It was bricked when he tried to update it. The tablet switched off when he was updating and right now it doest work.
When you press the power button the power led blink (green) for a second, and nothing more.
I tried to connect to a PC and nothing. Any idea?
Thanks a lot!!!
Can you see archos logo on the screen? If not, it might be totally bricked. First thing is to try to boot to recovery. This can be done by holding powerbutton and volume -, until you see white screen and some text. If you don't see anything, I can't help.
No, I cant see anything is TOTALLY BRICKED.
And It's Impossible to boot to recovery.
Thanks anyway!
Try charge the battery for 2-3 hours then try in recovery mode
Sent from my ARCHOS 101G9 using XDA Premium HD app
rioni said:
Try charge the battery for 2-3 hours then try in recovery mode
Sent from my ARCHOS 101G9 using XDA Premium HD app
Click to expand...
Click to collapse
Tried It. It didnt work. Its completely brick.
the_jako said:
Tried It. It didnt work. Its completely brick.
Click to expand...
Click to collapse
Did you unplug everything? By that I main not only unplugging the charging cable, but also pull out any USB device(s) from the rear 3G USB port, also any microSD card, headphone, HDMI, etc.? I mean unplug EVERYTHING from every connector!
Then, press and hold the power button for over 10 seconds (I'd suggest holding for at least 20 seconds).
After doing the above... then plug in the Archos supplied USB cable, plug that into the Archos supplied charger, and then plug the charger into the wall power outlet. Notice I said "Archos supplied" USB cable and charger!
Do NOT do anything else, and do NOT mess around with pressing the power button or anything else!!!
If the device is working at all it should do one of the below:
1) If the battery is to low to start up the power LED may not light up at all, or it may blink quickly. If the screen does not light up and show the Archos logo at this point then just leave it sit until it gets enough charge to do so... and then leave it sit another 4 or 5 hours to completely charge.
2) If the power LED lights, but is not blinking, and the screen show the Archos logo and goes on through to a normal "lock" screen, then leave it alone until it is fully charged and the LED starts blinking.
[NOTE: The power LED blinks (although a bit differently) when the battery is to low, or when it it fully charged. Pretty stupid eh?]
3) The screen lights up and goes from the Archos logo right into the (white) Recovery screen with various options to fix things.
If it does this last one, then you should be able to get back to install firmware by connecting it to your computer. Of course, you have to have downloaded the Archos firmware .aos file with your computer first, and then copy it to the tablet.
If it does NOT do any of the above... well, then I guess you did totally brick it. Don't know how, but I do know that certain 101 G9's that installed the very early 4.0.24 firmware did get bricked by that "official" Archos firmware release. It was pulled from their servers as soon as they found out about it.
If you are still stuck in the last part of what I've mentioned... then the best thing to do is contact Archos and get an RMA to return you device for a replacement.
In all honesty, it's really pretty hard to brick an Archos G9 by accident unless there is something seriously with the device to start with.
I was on the latest MIUI (9.something), boot-loader unlocked, redwolf recovery (v27), last seen battery was ~50% charged (before going off).
And, I was using my phone. Suddenly screen goes off and nothing comes up. I tried to restart, it doesn't work.
Finally I googled the problem and tried these things:
1) Press power button 5 times, then try to start the phone by long pressing power button.
Result: Screen open up, that initial screen with MIUI logo, I keep the button pressed, screen goes off and instantly starts again with booting started. Now, as soon as boot finishes, that *low-power* sound comes and it switches off.
2) Press power button 5 times, then try to start the phone by long pressing power button. This time when the screen comes up first time, I press (vol-up + power) to boot to recovery.
Result: As expected. That screen goes off and instantly another screen comes up with the recovery splash screen. Recovery comes up. There on the top, it shows two weird stats: (CPU temp 105 deg C, battery 0%).
3) Press power button 5 times, then try to start the phone by long pressing power button. This time don't press anything on the first screen.
Result: The screen goes off and that's it.
Some weird symptoms worth knowing:
1) Whenever I plug the charging cable (either with charger or, laptop) it just do not boot, neither to system nor to recovery.
2) The micro-USB port is damaged I guess. Last time (a day before all this), I tried to connect phone to my laptop but the socked seemed lose. It was just not connecting, rather fluctuating a bit.
3) Whenever I plug the charging/data cable (either with charger or, laptop) while booting or, while in recovery it suddenly switches off.
either your battery got badly damaged, or your device got fried.
First, I'd agree on the first commenter and support you taking the device to any android service center to check whether your battery or phone got fried. If it's done and proved nothing is wrong with my battery/phone I'd buy an EDL deep flash cable (I bought one for dirt cheap, 5 dollars) and try to solve my problem via deep flash, edl emergency download mode. There are tons of how to do tutorials on the official Xiaomi forums. Good luck with that, my friend!
I've updated something. Please see it.
How would I use edl if port is not working properly? See the original ques. again. I've updated it.
My S9+ was acting quite weird this morning. Some apps continuously crashed or wouldn't start.
So i rebooted my phone (just from the normal power button menu) and then it went completely black.
It doesn't charge (or at least, it doesn't show it charging), it doesn't respond to forced resets and the screen is completely black.
The only thing it does, is briefly show a USB device when connecting it to a PC.
I've connected it to a Linux dev computer i have laying around and i see the following device connected briefly:
VID: 0x04e8
PID: 0x1234
It stays connecting longer if i hold the power button (about 8 seconds before power cycling).
The only things i could find online were some very old threads about Samsung's DNW mode, but nothing from this decade.
I think my Flash chip might be cooked, but i hope i'm wrong.
Anyone got any experience with this?
Update
I've sent it back to Samsung for repair under warranty.
The flash chip was gone. It started corrupting writes and finally it was so far gone that it couldn't load the bootloader.
They've replaced the main board and battery (probably because they tested it and saw it was going bad), that fixed it.