noob help!
so i was just charging my phone. then all of a sudden my phone froze.
restarted it, then its just stuck at the htc logo. then the jetplane sound from the at&t intro.
tried doing a hard reset or entering recovery but after it reboots, still gets stuck at the htc logo.
(MORE INFO: im not sure if my phone is still rooted because i restored it my at&ts factory rom,cant change settings for usb debugging coz i ant get inside my phone,i still have my nandroid backups in my memory card from before)
is there anyway i could fix this? thanks in advance.
Try booting into recovery and deleting cache, reboot. If it still gets stuck, then try again, this time deleting user settings. If all else fails, restore your nandroid backup or restore the factory rom. If the problem is the rom, try flashing the RUU.
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
if u flashed the factory rom back on it, then clockwork is gone is probably gone now. It most definitely is not rooted anymore either. Have you tried to reroot the phone?
rcmmartinez said:
phone gets stuck at the htc screen when i choose recovery mode. also when i clear data.
tried re-flashing the phone with the stock rom from htc's website. it says its successful but still.. stuck at the htc startup screen.
Click to expand...
Click to collapse
That was an un-wise decision to put the stock rom back on. Like stated above. Try a Re-Root. Then flash a CUSTOM ROM to your phone. If this doesn't work. Sounds like you are S.O.L.
Related
In an effort to get back to stock I took things a step too far and now have a phone that won't power on. I had successfully rooted the phone and installed Rom Manager and flashed the clockwork recovery and immediately created a nandroid backup. Sometime later my phone started acting funny... usb connected/disconnected events when it was not plugged in, crashes, etc. I felt confident that this was a hardware issue (started after my daughter chewed on it when I wasn't looking). Anyway, I followed the instructions here in the dev forum (True Stock 2.1 firmware for vibrant) for the vibrant to get back to stock ( I apparently can't post the link because I'm new...) . So that I'd be able to try and get it replaced. I kept noticing that no matter how hard I tried clockwork was still installed... then I did the bad thing. I should have known better, but I made the rookie mistake and deleted the clockwork folder from the internal flash. I don't know what possessed me to do it, but I did. Since then the phone doesn't seem to boot. I can get it into download mode to flash images from odin (battery out, battery in, volume up + volume down, connect usb and download comes on). And after a successful download it seems to restart ok. But if it crashes (which it is now prone to do) or is powered off it won't boot after that. Worse I can't get to the stock recovery either.
I'm hoping that someone who has a nice rooted stock phone with clockwork installed can just help me get a copy of that folder back and everything will be fine... if not I may just have to see if playing dumb with tmobile will get the phone replaced as is...
Thanks in advance for any help.
Are you talking about stuff in /sdcard? If so, that won't effect the boot. You could delete everything in there and not change anything. Some apps might not work as you will have deleted their data, but if you're flashing a stock ROM with Odin, that's fine.
Enable debug mode in the settings and use "adb reboot recovery" at a command prompt. That should get you to the stock recovery. Try a factory reset from there, that might help. If not, delete anything in /sdcard that's not supposed to be there and swap with TMobile as it sounds a hardware issue at that point. Don't forget to keep your external SD card if you've replaced it.
Is USB debugging on?
When you get the phone up, can you connect to it via ADB and then adb reboot recovery or adb reboot download?
Thanks for the suggestions. I did get the sdk installed and used adb to reboot into normal recovery, so it's not completely boned. Since I could use adb for resets I went ahead and followed the rooting process again and reflashed clockwork. The phone still won't boot on it's own. I'm starting to think whatever was going south with the hardware has continued to get worse. I'm going to use odin to get back to "true stock" again and try to use adb to reboot into recovery and do a factory reset suggested above and see if that helps.
Thanks again.
I went back to stock with odin, ran the factory reset, and still can't power up normally or into recovery. I can get into download though, load with odin, come up normally after the reset. I'm going to try giving it back to Tmobile in it's refusing to power up state and see if I can get them to swap it. It's as stock as I can make it so the problem should not be mine.
Thanks again for the help.
FWIW - i just installed Rom manager this morning, the premium version, and today experienced 5 force closures, one on google maps
before this i've had maybe one FC some 2-3 weeks ago - and like you i did a clockworkrecovery backup or nandroid backup
Alright well I've just recently rooted my Shift an am experiencing a bit of a problem...
All was well, I created a backup of the current (stock) ROM, went into recovery, saw it there. I tried to load it, said it was a success, but when I went to reboot the phone it shows the HTC white screen, blinks off, shows it again and goes back into recovery. I've tried creating an alternate backup and whne rebooting with that it just shows the white HTC screen and stays on it. Any help would be appreciated.
Avivator said:
Alright well I've just recently rooted my Shift an am experiencing a bit of a problem...
All was well, I created a backup of the current (stock) ROM, went into recovery, saw it there. I tried to load it, said it was a success, but when I went to reboot the phone it shows the HTC white screen, blinks off, shows it again and goes back into recovery. I've tried creating an alternate backup and whne rebooting with that it just shows the white HTC screen and stays on it. Any help would be appreciated.
Click to expand...
Click to collapse
Did you download the clockwork from rom manager?
If not, then most likely you'll HAVE to flash a new rom now. Though there are stock roms available. And an RUU if necessary.
Sent from my HTC Speedy (Gonzalez)
Yes, I did.
I rooted my G2 about two months ago. I'm currently using MIUI, not the latest but the one before it. Somehow, my phone got turned off and when I tried to turn it back on, it was stuck in a bootloop. I have a custom recovery image so I don't know if that affects anything. I tried to reboot into recovery by pressing volume down and power, nothing happened. I then did volume up and power. It vibrated three times and the orange light started flashing. I pulled the battery and now when I try to turn it on, nothing happens. So how do I reboot into recovery and so I can restore my backup? Any help/suggestions would be greatly appreciated.
Never pull the battery during something like that. It sounds like your bricked. Someone else confirm?
I don't think it's bricked. I plugged it up and then Clockwork came up so I selected reboot now. Clockwork came up again so I tried to restore my latest backup and the screen went black. I'm going to let it charge and then give it another try.
Ok good. That's lucky because whenever you pull on a boot like that, it usually bricks. If you have the option, try to re-flash your ROM. Maybe even try stock. If you were getting a black screen, it's most likely you flashed incorrectly.
Ok, I was able to boot into recovery and now I'm restoring my backup. I don't think I had a custom recovery image with this one so hopefully I won't get stuck in a bootloop. When you say stock, do you mean before I flashed MIUI (it was the first rom I flashed)? Thank you for your suggestions and all of your help.
first install adb on you PC, it helps a lot in these kind of cases.
1. try "adb logcat", it would tell you about what's going on in your machine.
2. once you get your adb working, try "adb reboot recovery" to see if it could boot your phone in recovery.
3. if after doing everything you fail to boot either your phone or in recovery then try using PC10IMG to boot a stock rom and then re-root your phone.
I got it back working. For some reason, I'm just starting to think that it needed charging (the battery had been out for about a day or two). I do have adb installed and configured on my computer since I needed it to root. Thank you for your suggestions, I will definitely rember them if this happens again.
lol of course when you get black screen and led blnking means your battery begging for juice, you're lucky that when the phone booted back in recovery and you tried to restore a backup the phone went off before actually starting to restore, that would've bricked your phone
DO NOT FLASH ANYTHING WITHOUT AT LEAST 40% OF JUICE LEFT
well my dad was having problems with his defy, running a stock us 2.2.1. I looked at his phone, and after a few minutes, it would freeze up, and go into a bootloop, or still screen of the motorola logo.
First thing i tried is the stock recovery, which would freeze as soon as i started to wipe cache, and or data reset. After that, it gets stuck on the motorola logo no matter what.
I thought flashing a different .sbf would work, tried it, and finally got it to load to the "Welcome to android - please touch to continue" screen, as soon as i touched it, it froze.
flashed - JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF
went into recovery again to try to hard reset, but once again it freezes when it starts to clear cache/data factory reset.
Reflashed, now its still stuck on the motorola logo.
Any help is appreciated, thanks
DH
The phone seems absolutely messed up.. can you send it back to service?
Motorola Defy, CM7 @ 1Ghz + CM9 multiboot
[Guide] Install double boot CM7 + CM9
[Guide][Root needed] Unsimlock your Defy
No I can't sadly, any recommendations?
Found a fix for anyone having this problem.v
Flash any sbf , and
Once its says "restart phone manually', exit the program, and unplug your phone, plug in your phone while in boot loader, them start the program,.and it should. Finish
the process, now you can clear cache and factory reset. Sorry I drank a little, the program is to install sbf's I can't think of the name
dyinghero27 said:
Found a fix for anyone having this problem.v
Flash any sbf , and
Once its says "restart phone manually', exit the program, and unplug your phone, plug in your phone while in boot loader, them start the program,.and it should. Finish
the process, now you can clear cache and factory reset. Sorry I drank a little, the program is to install sbf's I can't think of the name
Click to expand...
Click to collapse
Is the program RSDlite?
if yes the n how come when i was flashing a rom it never asks me to restart phone manually. and when i do quit the app any way and restart the phone in bootloader it does nothing.
Yesterday I installed a custom rom
Today I flashed the verizon stock rom to see if that solves the problem (I've done before without any problem, first making a wipe data). But when the process is complete, the phone is stuck at bootscreen logo droid (not at M logo).
I rebooted the phone into recovery mode and did a wipe data.
Then the phone does nothing. I clicked on the Android but nothing happens. I´ve tried making wipe data lot of times but nothing happens. I´ve also tried to flash with 2.3.3 rom (I have 2.3.4) but nothing hapens too.
I can´t turn on debbuging usb mode because of this, so I can´t run a full wipe with ADB. Also, I don´t have any recovery mod or something like that.
Bootloader and stock recovery work both fine. So I think that this an exclusively software issue, but I don´t know how to resolve it.
There is any way to turn on the debbuging usb mode without using Android? Or there is any way to make a full wipe with ADB in this condition? Or what else could I try?
PD: Also tried to make an update of kernel and rom via SDcard, but I always get a signature error.