Alright so I've been running UKB and Cubed kernel for the last 6 days without issue. I've had some random reboots and the phone locking up, but I was just going to deal with it until ViperDNA came out. So this morning comes and I unlock my phone and the phone reboots within 2 minutes. Comes to the lock screen and is completely stuck... Alright it happens. I hard reboot the phone (holding down power and volume down buttom) and reboot the phone. Still, it is frozen at the lock screen. Phone is coming up in ADB devices, but it cannot accept any commands. I reboot into recovery (CWM 6.0.2.1) and try to clear cache/dalvik. Reboot the phone and it's still stuck at the lock screen. I go into fastboot and push the stock kernel, phone boots gets to the lock screen, starts of fine and then locks again. I don't have any earlier restores to go to on the phone as I shifted them to my HDD to save a little space. I feel like an idiot now. Any help would be appreciated.
I also tried to sideload ViperDNA via CWM and it isn't showing up the device in ADB.
EDIT: Also while in Fastboot the computer shows the device as attached via Removable hardware as Android 1.0 it just wont let me sideload or push anything other than a kernel.
This happened to me at one point.. I had to re lock the phone in the all in one tool and reunlock and start fresh.. No problem since
With help from Dr_demento on the IRC channel I was able to get the phone booting again. For future reference of people running into this issue, formatting data helps. You'll unfortunately lose everything, but it's better than locking the phone and then unlocking it again.
Related
Hey guys, Today I just finished downgrading to HBOOT 1.4 and got up and running fine on TWRP 1.1.1 and ViperRom's new ICS build. I wasn't having any issues at all. I started reading about TWRP2 though, and felt like checking it out. So I downloaded GooManager and searched for TWRP and got openrecovery-twrp-2.1.3.blob. I touched it to download and it immediately went into recovery to install. However, as soon as it rebooted, it came up with TWRP 1.1.1's logo and a scrolling status bar. This lasted about 2 seconds and then the phone shut off. I left it as is hoping it would come back for about 10 min but nothing. I removed the battery and put it back in and tried to reboot. Booting to system and booting to recovery give zero response and ADB controls don't seem to recognize the device when plugged into USB. Can anybody help? TWRP2 doesn't seem to have a thread here and their site has limited resources for help.
thanks.
Can you boot into the bootloader (hold power and down on startup)?
no I cannot. Phone is completely unresponsive. I didn't think trying to flash a recovery would cause complete system failure.. wth
Just to be clear, before you call it a brick, did you remover battery for 10 seconds and then try to get to the bootloader. Hold down the volume first then the power button and keep holding both until the bootloader pops up. Just making sure...
yeah I did. Pulled the battery, left it out while I went and ate something, then plugged in the HTC charger and tried to reboot and nothing. Tried putting the battery back in and doing the same thing. I guess It's time to go to sprint and beg for mercy
Same thing happened to me. My phone is completely unresponsive after I tried to update to TWRP 2.1. I was on AOKP milestone 5a. The computer responds when I connect the USB, but the phone will not boot at all.
EDIT: Computer doesn't respond either. Think I'm headed to the nearest Sprint store ASAP.
Connect your device to your computer then go into your adb directory in cmd and type. "adb reboot-bootloader" (without the quotation marks)
Are you s-off ? And does the phone show up as qhusb_dload in device manager ? If it does it is bricked. If you still have s-on it can be fixed if you are s-off i am sorry to say you have to get a new phone. I have a phone now that is s-off and bricked and i cant recover it as of now but i am working on it, if i succeed i will post how to do it.
I would recommend trying to keep the bricked phone in case there is a way to unbrick eventually then you have another phone to play with. I just claimed my insurance and told them i dropped the phone in a porta-john at work and i wasn't about to fish it out. So they told me dont worry about sending the bricked phone in and i got my new one next day.
Here's my situation, maybe someone will find it interesting or know what's going on. I was running the EOS Jelly Bean (EOS-tf201-20120728-31.zip). Everything was running pretty well for a few days, then yesterday the device simply powered off. When I rebooted it got to the splash screen then shut off before it could get any farther. I figured it was a power issue, so I plugged it in and charged it for a while but get the same response. Around this point I started to get suspicious and tried to boot into recovery. It got to "Booting Recovery Kernel Image" then powers off the same way.
So then I proceed to go into fastboot and fastboot works great no power offs. Through that I am able to flash openrecovery-twrp-2.2.1-tf201.blob and the virtuous packaged boot as per this thread http://forum.xda-developers.com/showthread.php?t=1773280 as well as factory reset. I also tried a few other boot/recovery combinations and was able to make it into recovery. In twrp recovery I was able to install the latest Virtuous rom which got me back to stock and I thought good case closed. I even made it all the way into the OS and was able to install apps, wifi worked great, run the apps etc. Eventually the screen went blank though and I was stuck back in the same shutdown on boot scenario as described above. Now I'm able to fairly consistently flash openrecovery-twrp-2.2.1-tf201.blob, reboot, get into teamwin recovery, but now even that appears to be randomly powering off.
So now I'm guessing that it may just be bricked and is probably a hardware issue since the reboots appear so random, the unit was refurbished. At the same time I'm still holding out some hope that it's simply some boot code somewhere that was corrupted and I can flash something and get things back to normal again since I can still access fastboot and occasionally ADB and recovery. I've flashed from fastboot system/recovery/boot, any other thoughts or potential combinations I could try? Also anything I can do with those tools to debug it further and get more data on what may be the root cause?
My phone restarted one day and just wouldn't boot up. At first it was just stuck on the SAMSUNG logo, but after trying to boot into recovery, it now sits at the boot animation. When I try to boot into recovery, the CWM screen will come up, but no menu will show up, and then the phone will restart after a few minutes and go back to being stuck on the boot animation.
I can enter Download Mode, but USB Debugging must be disabled since ADB won't recognize the device and I can't send any commands (yes, drivers are installed).
First of all, is there any way I can recover the data on the phone? That is more important than getting the phone working, since I was just about ready to get a new phone anyway.
What can I do to get the phone working? Everything involving flashing a new kernel, or resetting the phone back to factory seem to require a working recovery or the ability to send commands through ADB, but I'm probably missing something, since there must something else that I can do.
Any help is greatly appreciated. Thanks.
**Not sure if this is related or not, but the reason why the phone restarted before this issue occurred is because the power button on the phone is a bit faulty. Over the past couple months I've been having issues with the power button; it seems overly sensitive so when I push it sometimes the screen will turn on and off and other times the phone will just restart as if I held the button down for too long. This is the main reason why I was ready to get a new phone.
Hello, I have an HTC Amaze for over a year now. It was working fine, I rooted it CWM 5. and I installed Android revolution custom ROM. Until 2 weeks ago my battery was giving me some trouble, so i put away the phone for a bit, I bought a new battery then I notice the phone wasn't coming on. SO i charge for an entire day it still wasn't charging. I carried it to the shop. They said, that they don't know whats wrong with the phone.
I came home and decide am going to fix it my self i tried powering it into recovery mode, hard reset. screen is still blank, at lease that is what I thought. I look closely and then i notice the phone was in recovery mode but no lights were on in the screen. So normally I thought what anyone would of thought, the bulb in the screen or some kind of wiring went bad. The i tried wiping cache davlik install new new rom. Nothing worked. and this was defficult because I had to use a flash light to see on the screen. Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
keronmat said:
Lastly, i just click reboot and then the phone lights up perfectly and HTC logo comes up and then it blanks off again. So can anyone help? any advise
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Find the way to install adb and communicate with the phone via adb and fastboot. If you can do that, you will be able to install anything necessary to get the phone working again.
First however, remove the battery, wait a few seconds, reinsert the battery and charge the phone overnight. Next day, try and start phone usual way--see what happens.
If NOTHING happens and you get a black screen, remove battery again for a few seconds, reinsert, and this time hold the power button in for AT LEAST 20 seconds.
See if that starts the phone.
If you get absolutely nothing again, find the "Unbricking Project" thread, but if you get any kind of screen, see if you can boot to recovery and restore anything. If you get a screen but can't do any kind of restore at all, find instructions for adb and fastboot I mentioned earlier, so you can install a new recovery and flash a new rom..
I did everything you said. Except I complete forget how to flash recovery and custom rom from my pc but when I type command in fastboot "adb devices" it was successful.
However, I charge the phone and I got into the recovery mode again and the wipe everything and then click backup and recovery. I rebooted the phone and it came on as if its a brand new HTC Amaze. I had the phone working i rejoice for a bit and then I realize I forget to put in my sim card. So i turn the phone off, put in the sim card. The same problem again. No led, no light in the screen, the phone atomatically boots into recovery mood.
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
keronmat said:
One more thing. when booting into recovery mode. the phone doesn't go where I see the 3 android at the bottom and you see, fastboot, reset etc. It goes straight to cwm screen.
Click to expand...
Click to collapse
I think that is what you should see when you boot into recovery.
Do whatever you did before to get the phone lit up again, then change the display settings to maybe 3/4 brightness for instance. Reboot the phone normal reboot and see if it comes back with light.
If it does, maybe you are fixed enough to install the sim.
Do you possibly have a nandroid backup saved somewhere, you could put it back in the phone via recovery?
The phone is lit up again like you asked me to do. It was hard to see in recovery mode. But i used a flashlight to look on the screen of the AMAZE then i flash a new custom rom. After multiple tries I got it up. SO its up and the brightness is at its highest point. But I dont believe thats the problem. I just need to figure out how the light stays off when in recovery mood but comes on when booted normally. Its as though the recovery is broken. How do I fix it? if its broken
I was on my phone when suddenly it just booted off for no reason, weird right? So now it just stays on the "LG" boot up screen and now do anything. I've tried everything and done everything right (as far as I know) before I get into that let me tell you what my device can do as of now:
Devices DOES have fastboot oem unlock done
Phone was rooted as well and working perfectly (or so I thought until this happened)
ADB doesn't seem to work, but fastboot when connected to the computer does.
Ex: ADB devices (blank)
but fastboot devices (shows phone connected)
I've tried rebooting into recovery (Power + down) doesn't do anything, however, {Power + down} then finger off power then {Power + down} again takes me to "factory reset" option, if done so the phone just hangs and removing battery on way to take it back to fastboot on pc, or bootloop again.
I've done the following steps using [LG-H901] Stock .img Files (Boot, System, and Recovery)
Code:
fastboot flash system system.img
then
fastboot flash boot boot.img
and finally
fastboot flash recovery recovery.img
I've tried booting the phone and still gets me stuck on bootloop, and doing the same {Power + down} gets to the same "factory reset" option only then freezes my phone if I agree to do so.
Is there something I've done wrong or incorrect? I will provide as much info as requested.
Thanks guys!
Update: Phone booted up to lockscreen after finishing "Android is starting..." procedures, then kept bootlooping and it is now doing "Android is starting.." procedures again. I'll keep it updated if it keeps doing so or anything of the sort.
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Double0EK said:
Did you reply YES when trying to enter recovery? It will ask 2 times and bith times answer YES ... And if you DO have TWRP installed it will boot into twrp recovery.
Click to expand...
Click to collapse
This is the weirdest thing, phone worked for a bit then shuts off and does the same thing. all files and everyhing was in tact. ANy main reason behind this? I am desperate not to delete everything because i have important photos on there that were still there when it re-started again right now.
So to recap: At the moment doing the {factory reset} got me as far as using phone for like 2 minutes before ****ting out and sending me on a bootloop yet again.
Important Questions:
On all my other devices I am able to connect via usb and read devices, but on this phone I get the message when connecting to my computer "LGE Android MTP Device: Failed" whats this about?
Is there any way to save internal photo album images other than getting this to boot up and pray it stays on long enough to transfer data?
UPDATE 2: Phone has booted up and not froze (yet)? Testing to see if it will keep working so far so good. Unfortunately all my **** was deleted which bummed me out, would have honestly prefered to lose a $600 phone than all the family, friend, ext photos I had on my phone I made the huge mistake of saving to internal memory and never backing up. Smh.
Update 3: Phone is back at it again with the bootloop. I have no idea what is wrong, I've repeated the steps twice and phone doesn't seem to let up. It's fine until I hit that restart or shutdown button then it goes into bootloop heaven. I'm guessing this phone is done for? On an unrelated note it did fall on me, but worked fine afterwards, it was just sudden when it started doing this. Unless anyone has more suggestions I'd be glad to hear them. As of right now, this phone is toast.
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Double0EK said:
You tube how to bake phones in the oven.
It could fix some potentially loose solders..or since everything was already wiped you should get a warranty replacement.. Should still be under factory warranty.
Click to expand...
Click to collapse
I am thinking the warranty route. Is there anything specific I should do before doing so? I hear having "fastboot oem unlock" {Bootloader Unlocked} voids the warranty. Is this true that you might know of? Either way thanks I appreciate the information.
Sorry so late..
But you can try to fastboot oem lock it.