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.
so i just flashed 2.8.7.0 with flashify (probably my culprit) at work ... no way to a usb cable/cannot hook phone to a work PC (gov)
now phone boots into bootloader, power down and recovery only, i can perform functions within recovery, but everytime i reboot it goes to recovery
anyone have any ideas? Im dead in the water now
-4ndr01d- said:
so i just flashed 2.8.7.0 with flashify (probably my culprit) at work ... no way to a usb cable/cannot hook phone to a work PC (gov)
now phone boots into bootloader, power down and recovery only, i can perform functions within recovery, but everytime i reboot it goes to recovery
anyone have any ideas? Im dead in the water now
Click to expand...
Click to collapse
I don't see a 2.8.7.0 on the TWRP site.
I do however see a 2.8.5.0
are you sure you are using the correct one?
their could be a M8 2.8.7.0 I just can't find it.
EDIT: nvm sorry, I see it now here:
http://forum.xda-developers.com/showthread.php?t=2717928
Wish I could be of help, sorry friend.
I fixed myslef. luckily I had a few versions of the kernel i was runnning. so i flashed one of those and everything worked fine.
Im sure its flashify's fault. seems like it flashed to both the boot and recovery partition
need to stay away from apps to flash recovery lol. just use fastboot
-4ndr01d- said:
I fixed myslef. luckily I had a few versions of the kernel i was runnning. so i flashed one of those and everything worked fine.
Im sure its flashify's fault. seems like it flashed to both the boot and recovery partition
need to stay away from apps to flash recovery lol. just use fastboot
Click to expand...
Click to collapse
Glad you got it fixed!
I agree, I only use fastboot when it comes to things such as recovery
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
tirtha2shredder said:
So I received my Yuphoria about a week ago. Decided to attempt rooting, unlocked the bootloader but I cannot seem to get a custom recovery to run on it, be it CWM or TWRP.
When I try to hotboot the image in fastboot mode, as soon as I enter the fastboot boot recovery command, my PC loses connection to the phone and a message pops up saying "USB device not recognised".
When I try to flash the recovery images, it is always successful. However, when I boot into the recovery, it always loads up the stock recovery, which is strange since the flash was successful.
Any solutions to this problem?
EDIT 1: Tried it with multiple PCs. Same problem for each one.
Click to expand...
Click to collapse
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
enrique_fire said:
its not strange. its the way it works. after flashing custom recovery DO NOT REBOOT THROUGH FASTBOOT. just pull out the usb cord. remove and reinsert the battery and then press the volume down and power button together. You will boot into recovery. I will recommend twrp.
Click to expand...
Click to collapse
Thank you! that worked perfect!
Hi which method did you use to root yu50101a? if possible can you share a link as well
:crying:I am also facing the same problem . i also have yu5010a but cannot root it . twrp or cwm not correctly flashing.just tell me if anyone have any solution .
Event 1 : My oneplus one got stuck within TWRP recovery, have tried flashing other custom ROMs but while rebooting to system it rebooted back to TWRP recovery every time. Tried to reboot the phone to bootloader mode, even that resulted to rebooting to TWRP.
Event 2 : After this I've replaced the TWRP recovery with stock recovery, then connected to my computer through adb sideload via the OTA update option in stock recovery menu. But since I do not have the OTA update file can not test either it will boot or not. Here I require the whole zip file not just the new update portion.
Now, is there anyway to get to twrp recovery again or boot the stock rom in the phone.
Any form of help is much appreciated...
Raj_at said:
Event 1 : My oneplus one got stuck within TWRP recovery, have tried flashing other custom ROMs but while rebooting to system it rebooted back to TWRP recovery every time. Tried to reboot the phone to bootloader mode, even that resulted to rebooting to TWRP.
Event 2 : After this I've replaced the TWRP recovery with stock recovery, then connected to my computer through adb sideload via the OTA update option in stock recovery menu. But since I do not have the OTA update file can not test either it will boot or not. Here I require the whole zip file not just the new update portion.
Now, is there anyway to get to twrp recovery again or boot the stock rom in the phone.
Any form of help is much appreciated...
Click to expand...
Click to collapse
I guess I know what caused the rebooting of twrp everytime.
It's because of the vol - button is getting pressed
automatically. Just open the back over and clean the vol button strips then reattach the back cover properly,your issue of twrp rebooting should be solved.
And you can flash the twrp using fastboot then flash any rom you want to.
The issue got figured out..thanks a lot sir..your effort is much appreciated..
Mr.Ak said:
I guess I know what caused the rebooting of twrp everytime.
It's because of the vol - button is getting pressed
automatically. Just open the back over and clean the vol button strips then reattach the back cover properly,your issue of twrp rebooting should be solved.
And you can flash the twrp using fastboot then flash any rom you want to.
Click to expand...
Click to collapse
:good::good::good::good:
Thanks a lot sir..I checked out the phone and found the same fault to be present there...Thereafter everything was easy as usual..
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
fully shutdown your device and then press the volume up while connecting your phone to pc and see if it can boot into fastboot or not...
just.befa said:
Hi guys,
I have a OPO bricked in a very weird way... It's booting straight to TWRP (v3.0.2-0) and nothing else. It is impossible to boot into bootloader (Vol. Up + Power), it still goes to TWRP. And when it is plugged on a computer, it's also booting straight to TWRP...
First a little recap :
- The OPO has (had) an unlocked bootloader and was updated from COS13 to Oxygen OS a while ago.
- The screen was smashed, touch screen not working anymore, and I had it replaced
- Then this problem occured (before screen change, it was booting to Android without a problem)
What I tried :
- Tried to reboot into bootloader, from TWRP via the reboot menu, nope.
- Tried to reboot into bootloader, from TWRP with "adb reboot bootloader", nope.
- Hard Reset from TWRP, nothing.
- Flash latest COS from TWRP (cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip) found here, nothing.
- I wanted to try this last chance unbrick "OnePlus Recovery Tool", but for that the OPO has to be OFF while plugged on a computer, and mine automatically boots on TWRP when plugged , so it's not bricked enough to use it, f***!
Since I can't access the bootlader, I can't do a proper clean/flash
I'm really out of ideas here. I'm starting to think that the problem isn't software but hardware...
Has anyone ever encountered such a brick, or has another idea?
Thanks in advance for your help.
Click to expand...
Click to collapse
Open the back panel of your device and clean it properly with isopropyl alcohol and microfiber cloth.Also clean the power and volume buttons strips.
Reattach it correctly and then try booting into system or fastboot.
Thank you guys for your help.
So, what happened is that the volume buttons connector was dead, and that the volume down signal was "permanent", that is why the device was systematically booting in recovery mode, no matter what I tried.
Replacing it worked just fine