Database Info

[Q] Yet Another Potential Brick

Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You

coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?

cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on

coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.

Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.

redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.

coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.

redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able

When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash

coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2

Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!

coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium

Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks

coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.

pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?

coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.

The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen

coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.

exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up

coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.

TWRP crashing

Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.

Tim3worx said:
Well, after trying to install a ROM through TWRP the phone rebooted and froze on the HTC screen. I then go back into bootloader and try to get into recovery but the splash screen pops up and then the phone reboots. I can get into CWM however when trying to sideload any .zips there I get an error. Not really sure what to do at this point. I probably should have stopped playing with it when I fixed it the first time, ha.
Edit: I fixed my problems! Very happy, ended up restoring some of the firmware from the OTA's and TWRP started working again. Just flashed ROM and fully functionally.
Click to expand...
Click to collapse
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?

tr1gg3r84 said:
which ota did you flash? what network provider you on? im having same problems, did you flash ota in twrp?
Click to expand...
Click to collapse
My provider is AT&T. I used the UK OTA from this link http://db.tt/LrIEemZ4 . Its part of this thread in general http://forum.xda-developers.com/showthread.php?t=2422885. Basically what was happening is that I had flashed a ROM which didn't work out and so it would just hang on the white HTC screen. I figured no big deal I'll just go into recovery and flash another one I know works. That didn't work out. Any time I tried to go into recovery the TWRP splash screen would pop up for a second then the phone would reboot. Which kind of had me puzzled because I flashed ClockWorkMod for recovery and it would at least get me into recovery but still adb sideload was giving me errors so I flashed TWRP again even though it wasn't working either.. I pulled the boot.img out of the Firmware.zip in the OTA and flashed that with fastboot. At that point I had tried just about everything and was about to give up but to my surprise that seemed to fix it. I was able to go into recovery no problem. Sideloaded the ROM and everything went great. I'll probably not be messing with my phone like that for a bit haha. It was the second night in a row that I had wiped an OS off the phone and struggled to figure out how to get it working. Glad its all good now though. Good luck to you!

cant change recovery / device rebooting
Hi, i have a similar problem,
I've unlocked with htcdev everything is fine.
Then I installed Twrp-2.6.0.0.img as recovary.
I'm not able to mount the internal storage, so I had to push the ROMs via ADB.
starting a ROM 1st time seems to be ok.
restart is also ok.
shutdown and power on is rebooting every ~15sec.
I tried to change my bootloader.
fastboot flash recovery recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are responding
fastboot boot recovery-clockwork-touch-6.0.3.6-m7ul.img -> volume keys are NOT responding
recovery isn't starting until i run following commands:
fastboot flash recovery Twrp-2.6.0.0.img -> volume keys are responding
fastboot boot Twrp-2.6.0.0.img -> volume keys are NOT responding
but after resetting the device + entering recovery it's there
thanks for your ideas/help

[Q] Can't reboot system without going through fast boot.

Like the title says, my Nexus 5 won't boot unless I manually plug it in, hold down volume buttons and power, then wait 15 seconds for fast boot to appear, and then select "start."
Thats the problem. Now for some more information:
1. Nexus 5 32 gb
2. ROM: CM 11 Dec 13s Nightly
3. Kernel: Bricked 3.4.0
4. The phone is totally functional. The only thing wrong with it is that it can't reboot. From the system, TWRP recover, or anything, it simply will not reboot. Every time I must go into fast boot then press the power button when it says "start." After this, the phone works just as I would expect it to. I can still flash kernels and backups through recovery, it just must be restarted manually through the fast boot. This is a problem for me because I don't always want to have to plug it in when I want to reboot it.
When did it start:
Let me start off by saying that I thing the root of all my problems was the TouchControl app that allows the knock to wake function to work. I downloaded the app and was told to install the developers custom kernel. I did and not only did the app not work, it also seemed to brick my phone. I was scared, but, after doing some research, I found the method of plugging it in and holding down all buttons for about 15 seconds and my phone was saved. Ever since then there has been the problem. I must always do this to reboot my phone. Since the app didn't work I decided to install the Bricked Kernel and everything went fine except that I wasn't prompted with the interactive installer. The kernel works fine and I am now using the Knock to wake feature built into the kernel and am very happy.
Seems to be caused by swipe2wake aka knock 2 wake aka knock knock (but not totally sure)
What I've Tried (don't assume I've tried something I haven't. I could have missed something obvious.):
1. Resetting permissions through TWRP (just thought I'd try)
2. Putting back CM 11 Kernel
3. Restoring to a time when my phone did restart
Any help would be greatly appreciated. I will try to keep the original post updated with everything I try.
FIXED with the help of jd1639 and meangreenie
------------------------------------------------------------------
1.Follow jd1639's link in 3rd comment to the page and
A. Install adb and flashboot drivers
B. Install your version of factory images from google (if you are running 4.4.2 get the image for 4.4.2)
2. Plug in phone to AC CHARGER and hold down power and volume buttons for up to 20 seconds. This should put it into fast boot mode
3. After getting phone in fast boot mode, plug it into your mac or pc.
4. Out of all the instructions in the "How to flash a factory image" thread go to method 2 and ONLY DO THE FIRST TWO LINES OF CODE. All that needs to be flashed is the bootloader.img
5. After it says complete and your phone restarts you should be able to push "start" on your phone and be good!

I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.

jd1639 said:
I would try and fastboot flash boot boot.img. where boot.img is the boot image from the factory image.
Click to expand...
Click to collapse
So that's essentially flashing the stock ROM?

benaside said:
So that's essentially flashing the stock ROM?
Click to expand...
Click to collapse
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064

jd1639 said:
No just the boot.img
Edit, look at method #2 but only flash the boot.img nothing else http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.

benaside said:
Thanks so much for trying to help. I installed all the things and flashed Boot.img from fast boot, but once I restarted my phone everything was messed up (booted to home screen but basically the system started failing). After this, I retried but deleted my cache and delvik cache. This time the system simply wouldn't boot. Luckily I backed up and restored to my previous version. Thanks for trying, but this did not work.
Click to expand...
Click to collapse
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4

jd1639 said:
Were you on 4.4 or 4.4.2. Sounds like 4.4.2. The factory image in the link was 4.4
Click to expand...
Click to collapse
I downloaded the folder for 4.4.2 from the link developers.google .com/android/nexus/images#hammerhead

try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too

meangreenie said:
try reflashing via custom recovery or fastboot.. bootloader, recovery and suitable boot.img for your rom, maybe give the radio a reflash too
Click to expand...
Click to collapse
Will this'd elite all my files and unroot?
Btw thanks so much for the help

benaside said:
Will this'd elite all my files and unroot?
Btw thanks so much for the help
Click to expand...
Click to collapse
no it won't delete your data.. but please triple check your files and fastboot commands before executing
the last resort is to format data if all else fails

Thank you both so much. I have (with both of your help fixed it). I will post how in the original post. Thanks again.

[Q] I might have hard bricked my nexus

I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.

Just wait it takes awhile

@bigglongruler

bigglongruler said:
I have a nexus 5.
16GB model.
5.1.1
Rooted.
TWRP 2.8.6.1
I was about to flash CM 12.1 .
I pressed wipe but it froze, I left it that way for about an hour and decided to research about what is happening. A lot of comments on some thread I read said that turning it off and then on worked for them and I did the same. Now all I get is a flashing Teamwin logo. The only accessible feature of the phone is the Power off/Start/Bootloader/Restart Bootloader thing-y. Whichever of them I press I get the flashing Teamwin logo.
Click to expand...
Click to collapse
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.

davehasninjas said:
Well you still have access to the bootloader luckily. Best part about a Nexus is that they're difficult to actually brick. Boot your phone into the bootloader and either fastboot flash recovery to reinstall twrp or use fastboot to reflash the stock system images.
Click to expand...
Click to collapse
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.

bigglongruler said:
Thanks man, that's exactly what I needed. I tried to re-flash TWRP but had the same problem but when I flashed the stock system images everything went back to normal.
Click to expand...
Click to collapse
Glad I could help, and that your phone is up and running again.
Take care.

Only recovery

Hello! I recently dropped my OPO and the screen cracked. The touch also stopped working. But except that, everything looked fine, to me at least. I ordered a new display and replaced it some days ago. Everything went alright, except when I reconnected the antenna cable... It was too short, so I tried to pull a little bit, and then the cable popped off. I'm going to find a solution to this, I'll see if it is possible to replace the antenna cable. Anyway, I put everything else together and started the phone. I was surprised to find out that I ended up in the recovery. I rebooted and I ended up in the recovery AGAIN! So I formatted the internal memory, transferred CM13 + stock Gapps to the phone, installed and booted. I ended up in my recovery, again. I began thinking that the recovery might be corrupt or something like that (TWRP). I tried booting to the bootloader, but ended up in the recovery, once again. These are the different methods I used, trying to reach the bootloader:
- Volume up + power button
- Recovery reboot options
- adb reboot bootloader
All of these methods brought me to the recovery. My goal is to reach the bootloader so fastboot works, and then use this tool to reset my phone. Do you guys have any ideas? Thanks in advance!

What recovery ? Twrp or stock ?
If you are in twrp there is option to boot into bootloader ,then you can flash firmware via fastboot or use otg port,
If you in stock , I think otg port can be used .

drmuruga said:
What recovery ? Twrp or stock ?
If you are in twrp there is option to boot into bootloader ,then you can flash firmware via fastboot or use otg port,
If you in stock , I think otg port can be used .
Click to expand...
Click to collapse
This is the problem... I am using TWRP, but even if I use the reboot options, which is booting into bootloader, I will only end up in the recovery anyway...
Any other idea?

There is no OS, so not booting. Use any compatible ROM via otg preferably COS 13 TWRP signed ROM ( no gapps needed ).