So I picked up my phone, wouldnt turn on. No biggie, battery must be gone (stupid custom rom sucking all the power) plugged it in, let it charge for a bit, I came back to it and tried to turn it on. I got 3 vibrations and an orange light but no screen. I attempted to access the bootloader, got 5 vibrations I think and a green light but no screen. I started searching for ruu and img.zip files to attempt to reflash, backed up my sd card and then went back to the phone and tried once more to turn it on and it started up? I had the battery removed for a few minutes. However, it worries me that this happened and I'm wondering if the guys here that know about more technical stuff can explain why this was only temporary when it seemed like a serious corruption in the boot sequence? most vibrate bricks are permanent in that they have to be reflashed. And finally, how can I prevent this from happening again? Sorry for the book I just typed <--- But if it happens anyone else, its nice to know they have someone else who was in the same boat.
Edit:
HTC Desire S
Europe-Factory Unlocked
Custom Rom: Andromadus - CM10... Has a few small things to be fixed but atleast its Jelly Bean
Clock Speed before brick: 245-806, interactive governer. (was trying to save battery, usuall on about 1.2-1.4)
Unsure of hboot
Solved
I apologise to moderators if this thread messes with any rules but I managed to figure out the problem, So this thread may be handy to someone else. Most HTC phones are similar in the way they boot and how the buttons are set up with the board. So i believe my up volume buttton was stuck due to some dirt which caused it to be held down. This caused either a boot error or it was the backup download thing (fastboot or something along that road). So dont panic guys if you get the vibrate brick. It might just be as simple as some dust. Thank fully my phone is in working order again.
Related
Hi all... and sorry for my bad English ;-)
I've got an HTC G1. When I try to start it, nothing happens. Only the backlight turns on ... What can I do?
do you have a rooted g1 with recovery and engineering SPL?
No, it isn't rooted...
Is it brand new? I think you should be able to exchange it, if you got it from a store that is; unless you got it from online then you will have to contact the website and see where that goes.
No, it isn't brand new. Someone gave it to me... So i can't exchange it.
Try to boot it thru camera+power holding. Wont help you if success but at least will tell you where the problem.
if he can go to recover mode screen wont remain completely black as far as i know. Because splashscreen appear before recover (or other) mode starts. I might be wrong of course.
If I try to go into the recovery mode thru camera + power button, nothing happens. Only the backlight turns on (black screen with backlight & keyboard backlight...)
Follow first 6 steps in this form...
http://forum.xda-developers.com/showthread.php?t=442480
tihs should boot your G1.... then if you want go on ahead with other rooting steps to root your g1..
I tried the first 6 steps, but it won't work. I think I can't entry bootloader mode. On step #4 (...)You should see a gray/white screen with instructions(...)
nothing happens on my Phone. :S
Isn't it possible, to flash the bootloader/firmware over USB or something like that?
*push* no solution?
are you sure the phone does not boot? Does it rumble when you first turn it on?
I have a similar problemb, but my phone will completely boot and work, but the lcd does not work it stays black. i can move apps around (they rumble when you pick one up), and i can recieve calls.
I was able to get it to occasionally boot with the lcd working by rebooting the phone with call+menu+power. It worked long enough to reflash the rom to rc29, and boot into it. Then it died shortly after.
mine is going to htc.
Yes, it does rumble when I turn it on, but I think it doesn't boot. So I can't "move apps around" or "recieve calls"
And I can't use the warranty, because I'm swiss.
another way to tell if it actually boots is plug it into a pc after giviing it enough time to boot, and listen for the usb connection notification sound your phone should make.
just trying to help you narrow it down. When i am contacted by HTC i will be sure to try and get as much info from then as possible. hopefully ill get something that might help you.
Since you wont have to worry about voiding your warranty, I also suggest snagging the factory service manual and make sure all the flex cables/connectors pertaining to the lcd are properly connected. This, of course, is under the idea that you have the same problem as me.
good luck
When I plug the phone over usb into a PC, the pc find it as "HTC Android Phone USB Device".
Hmm I don't think, that the LCD is broken, because the backlight turns on... If the lcd is broken, the backlight won't turn on, right?
the backlight on mine would also stay on. then again my lcd worked intermittenly at first and proceded to work less and less, but the backlight would remain on. However, I think your problem differs from what I encountered.
The fact that your pc recognizes the phone means the usb controller is working, but thats about it... I am just trying to find out for sure if you phone boots or not. That will help narrow down the problem for sure.
Have you tried calling it from another number?
It also never hurts to take a peek at the factory service manual... if you havent already
thank you. hmm... I think I can't recieve phonecalls.. but I'm not sure. (I tried it, but yeah i don't know. xD it doesn't rumble or something like that...) Is it possible to have "remote" on the phone? So I can use it over the PC?
They have shipped my phone back. Apparently the screen dying was a side effect of the keyboard going bad...The keypad did not give me any problems though. I was told they replaced the keypad FPC (part no: 73H20137-41M, pg#102 in the service manual). They replaced nothing else.
Unforutnately they did not have any more info to give me. In your case, i would suggest opening it up and checking all the flex cable connections to ensure they are properly and fully attached. of course this check is not really for the faint of heart technically speaking, but it shouldnt be too bad with the service manual as a disassembly/assembly guide.
are there any tutorials how to open the g1? =)
http://www.youtube.com/watch?v=27inpgouXII (part I)
http://www.youtube.com/watch?v=HIg_3EgrgGY (part II)
My Tornado behaves a bit strange - after flashing it boots in way that I can't understand: first time into SPL, second time - normal boot and again - SPL, nd boot normal... What's going on? I've flashed a few different ROMs and it's still happening.
In addition, something is wrong with keys - I've blown joystick and it was working correctly for a while. Later, it started to point only right and down, neither all other directions nor push. I can't start camera, use other side buttons (except power).
May anyone give me a tip what should I do for now? Should I buy new joystick and solder it instead old one, don't I? I thought so firstly but side buttons don't work too...
U did some bad work to phone?
or it is just happening abrupt ?
try to install an official update then redo the installation procedure from karhoe's website for WM6/6.1/6.5 and report back. dont go for hardware replacement yet if u havent done any thing harming to ur phone. Just install official update and report back whether u r still having same issues or not?
You will never believe what was wrong.
Accidential boot failure was associated within dirty side buttons. There must be such an combination which enters into SPL during boot. And because of button malfuction they (or it?) probably has been pressed continously which often prevented to boot.
Now, with distilled water and hair dryer I was able to fight with dust and everything became operational. :]
Thanks for interesting.
Glad that you worked it out urself
happy tornadoing
Hello XDA friends. This is my first official posting on the XDA site and I'm in need of serious help.
I've noticed that intense research and development has been put into this phone. With so many rom selections available for the MT4GS I decided to try out several different roms kind of playing around. Many of the roms available were very well put together.
I decided to try out the Doubleshot MIUI v0.3 as I have used on other devices in the past and liked its customization. After installing the rom I made some adjustments in the settings to personalize my phone. Everything was working fine until I rebooted my phone and now it is hard-bricked. My device is S-Off with bootloader unlocked, and prior to installing MIUI I formatted all data, Dalvik, and system. I don't know what I did to brick my device and I can't find similar issues among others.
Issue Details:
When I have the phone powered off then hit the power button my backlight will slightly light up (very dim with no splash or image), and it will vibrate (Like on a normal boot). What else is crazy is every 37 seconds it will vibrate, and this is ongoing if I let the phone sit in that state.
If I have the phone off and plug it in a power source I get no love.
I'm unable to access HBOOT or Recovery mode, and the phone is not detected when connected to PC.
Please help me.......
that looks like a screen/digitizer problem. I don't think you're even bricked seeing as you didn't mess with any partitions according to what you did above. Also if the phone vibrates and the backlight turns on then it's still alive.
Thanks for the response. I'm sure the screen is fine. I performed the reboot when the issue first happened. This phone is driving me crazy.
wait u said you phone isn't connecting to adb right?
Did you try Fastboot?
I'm not able to bring up the HBOOT menu to enter fastboot mode.
have you tried a battery pull?
Thanks for the reply. I have tried pulling/replacing the battery and didn't have any luck. I also have two spares and the issue continues........
I can't figure it out, or figure what I did exactly to cause this.
Any other ideas?
does adb recognize it when it is plugged in?
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.