so i recently got my opo. unlocked the boor loader, couldn't flash anything tho cuz of on a terp error. after some researching i flashed a new modem, everything worked, flashed cm12.1 nightly, got boot loop + couldn't get into recovery, got into fast boot tho so i installed the cm 12 modem., got the battery loading screen, decided to let it boot for some time, came back after 4 hours, screen was off, couldn't get into fast boot + to get to the booting screen i need to long press power button,
anybody knows what to do?
robinkomenda said:
so i recently got my opo. unlocked the boor loader, couldn't flash anything tho cuz of on a terp error. after some researching i flashed a new modem, everything worked, flashed cm12.1 nightly, got boot loop + couldn't get into recovery, got into fast boot tho so i installed the cm 12 modem., got the battery loading screen, decided to let it boot for some time, came back after 4 hours, screen was off, couldn't get into fast boot + to get to the booting screen i need to long press power button,
anybody knows what to do?
Click to expand...
Click to collapse
Can you not get into fastboot at all now?
Heisenberg said:
Can you not get into fastboot at all now?
Click to expand...
Click to collapse
i let it rest 12+ i_m getting the charging screen again so that's a good thing. gonna try to get into fast boot when i'm on 100%. i didn't try yet.
robinkomenda said:
i let it rest 12+ i_m getting the charging screen again so that's a good thing. gonna try to get into fast boot when i'm on 100%. i didn't try yet.
Click to expand...
Click to collapse
If you can get to fastboot then flash the stock images. Instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Related
Hey all, first time posting here,
So, I rooted my phone a few days ago and flashed Invisiblek's CM10(Running the August 10th build), using the instructions found here. Haven't had any problems at all until now. I had to reboot my phone, and now it's stuck in a boot loop. The CWMR screen is missing the background, and it won't let me boot into ODIN mode. What do I do?
Thank you for any help!
Krog216 said:
Hey all, first time posting here,
So, I rooted my phone a few days ago and flashed Invisiblek's CM10(Running the August 10th build), using the instructions found here. Haven't had any problems at all until now. I had to reboot my phone, and now it's stuck in a boot loop. The CWMR screen is missing the background, and it won't let me boot into ODIN mode. What do I do?
Thank you for any help!
Click to expand...
Click to collapse
You should be able to boot into odin by taking the battery out, and then putting it back in while holding Volume Down + Home + Power at the same time. And then just flash a stock or stock rooted image in odin.
There we go. Thank you very much!
Flashed the ROM linked from here. Now I'm stuck on the 4G LTE screen. Suggestions?
Flashed it again. Still nothing. Did I brick it?
If you can get into Odin mode, I suggest flashing back go stock and starting over. If you can't get Odin to work, or even enter download mode then you might have other problems.
Sent from my SCH-I535 using Tapatalk 2
I am (thankfully) able to get into odin mode. Where can I get the stock ROM for the US VZW version? I haven't been able to find that anywhere, and the thread on here only has dead links.
Flashed again, still nothing. I get stuck at the 4G LTE loading screen.
Found a stock ROM and flashed back to it. Still stuck at that screen. Did I brick it?
dont forget to wipe data/cache...
it happens
you can do this by booting into stock recovery
Volume UP + Home + power.
vega04 said:
dont forget to wipe data/cache...
it happens
you can do this by booting into stock clock work
Volume UP + Home + power.
Click to expand...
Click to collapse
Oh my god I love you.
It works!!!
Krog216 said:
Oh my god I love you.
Click to expand...
Click to collapse
i love you too.. lol ive been there..
So, I've got it worked out so that I have a recovery image made of a rooted version of the stock ROM. However, I SWEAR a kitten dies every time I look at the TouchPiss interface, but whenever I try to flash Invisiblek's CM10 I get stuck in a boot loop. Any ideas as to what's causing it? I've tried clearing data/cache/davlik cache before flashing the ROM, after flashing the ROM...
Would there be any way at all that I could flash it through ODIN?
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.
I installed Liquid Smooth ROM last night and stuck in boot loop now. I can't even boot into TWRP recovery. When I boot to recovery from bootloader, Teamwin logo flashes few times, then I see Liquid Smooth animation for few seconds and phone reboots.
What can be done to fix this?
UPDATE: Was unable to push twrp recovery, finally restored the phone by following this link http://forum.xda-developers.com/showthread.php?t=2727831 and back to normal now.
dadmi said:
I installed Liquid Smooth ROM last night and stuck in boot loop now. I can't even boot into TWRP recovery. When I boot to recovery from bootloader, Teamwin logo flashes few times, then I see Liquid Smooth animation for few seconds and phone reboots.
What can be done to fix this?
Click to expand...
Click to collapse
Try to re-push the TWRP recovery and boot to it again.
Was unable to push twrp recovery, finally restored the phone by following this link http://forum.xda-developers.com/showthread.php?t=2727831 and back to normal now.
sfreemanoh said:
Try to re-push the TWRP recovery and boot to it again.
Click to expand...
Click to collapse
dadmi said:
I installed Liquid Smooth ROM last night and stuck in boot loop now. I can't even boot into TWRP recovery. When I boot to recovery from bootloader, Teamwin logo flashes few times, then I see Liquid Smooth animation for few seconds and phone reboots.
What can be done to fix this?
Click to expand...
Click to collapse
Weird.. This sounds like what happened to my phone the other night. I updated AdAway hosts file, did a reboot, walked away came back a few mins and saw the Liquid boot animation, then noticed it reboot then try to boot up, then reboot again, so I tried booting into TWRP and it did the same, tried to do a flash of a ROM and it rebooted within a few seconds. So I decided the only option was to try the RUU and luckily after that everything is back to normal. But with all the weird-ness going on in these threads with peoples phones, it was a true scare.
So many weird things with root on this phone that I've never heard/encountered before. I'm just gonna chill on clean ROM with sense 6 toolbox and lay low for a while w/o flashing hoping an explanation is made.
Sent from my HTC6525LVW using Tapatalk
Try fastboot erase cache?
lucky_strike33 said:
Try fastboot erase cache?
Click to expand...
Click to collapse
That didn't help
Try taking out your Sim card
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
So many weird things with root on this phone that I've never heard/encountered before. I'm just gonna chill on clean ROM with sense 6 toolbox and lay low for a while w/o flashing hoping an explanation is made.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I really couldn't agree more! I feel like the carriers especially Verizon want total control of any device that's on their network.
Before long we are all going to be waiting for a jailbreak team to give us root on each update.:crying:
pjim said:
I feel like the carriers especially Verizon want total control of any device that's on their network.
Click to expand...
Click to collapse
Maybe because they do? That's not exactly a secret... To varying degrees of course, with T-Mobile caring the least, and Verizon caring the most.
I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?
DaElderGeek said:
I have a sinking feeling that the same failure that killed my first tablet, an HP Touchpad (NAND Lock/Failure) has killed my Galaxy Note N8013. All was fine until a few days ago. I was running TWRP 2..8.0.1. and alternating between CM12.1 and BliisRom with no problems. I connected it to charge overnight and went to bed. The next morning it was stuck on the CM12.1 boot animation. It would never boot, just run the animation until the battery drained. I can put it in download mode and it appears to successfully flash stock/custom roms/recoveries (I've tried them all) but as soon as it reboots it goes back to the CM boot animation. If I try to put in recovery (power + Volume up) the TWRP splash screen appears but quickly disappears and is replaced by CM boot animation. Since I can't get into recovery is there another way to do a factory reset/wipe? Any ideas or suggestions?
Click to expand...
Click to collapse
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.
Pupskartoffel said:
did you tryed with odin or abd, try to flash newest twrp from the site and flash it via odin3.
Click to expand...
Click to collapse
Only with Odin. My understanding is that ADB isn't available if you can't boot into recovery. I haven't found anyway to make it boot into recovery.
Reflash/recovery
Have you tryed to flash twrp 2.8.7.0 or cwm or, try to reflash the boot.img.
Sorry for bad english i'm only 12
Today I had a strange issue with my Oneplus 7 pro GM1913 running OOS 9.5.5, device unlocked, twrp and rooted. My device ran out of charge and was turned off. When I plugged into the charger, it boots up and for a few second the oneplus logo and charge the device for some time page came in and then the bootloader unlocked screen came in. I haven't charged the device offline after the battery ran out, it was my first time and i thought it was supposed to be like that. But after some time also it was on the same page. Then i plugged out the device and it was stuck on that page. I tired hard reboot, tried to connect to computer. Nothing was successful. Computer showed unknown device and failed to successfully connect. Not recognised as adb device shown nor fastboot device. Then atleast I tried entering into fastboot mode by pressing power button + volume up. At that time it rebooted into system and then everything was okay. But then i noticed i also lost the twrp recovery. Then i had to flash twrp through magisk manager.
Anyone has any idea what happened? Thanks in advance
You have to flash magisk again after flashing TWRP.
deborok said:
You have to flash magisk again after flashing TWRP.
Click to expand...
Click to collapse
Yeah I did everything and it was working properly for a week amd then this happened
sachinkjohn1 said:
Yeah I did everything and it was working properly for a week amd then this happened
Click to expand...
Click to collapse
flash stock boot. img
zams85 said:
flash stock boot. img
Click to expand...
Click to collapse
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
sachinkjohn1 said:
It's working now.. But I just want to know whether this happened to anyone else? Or the reason for this?
Click to expand...
Click to collapse
I got stuck there once I was trying to flash twrp somehow. Same fix
Stuck at the bootlogo
Hey guys, i hope i get some help from here.. tried to root my one plus 7 pro international version installed twrp everything worked fine... and after that i tried to reboot in system mode.. now im stuck at the bootlogo with the red middle dot and the 2 white ones. i cant even turn it of now.. no command are working... can anybody help me to fix this pls?
Thanks!!!
I had exactly the same problem. System was running fine with just Magisk installed (I boot TWRP with fastboot on a computer).
Then I ran completely out of charge, and the OP7Pro wouldn't boot anymore: at power on, it shows briefly the OnePlus logo, then displays the boot loader unlocked warning for a very long time (a few minutes), then goes to the bootloader menu.
I can boot TWRP and unlock the data partition. I will try flashing the stock boot and see what happens (and report).
Edit: I had to reflash stock boot and system to have the device boot again.
hi guys,please need help;I have just unlock bootloader on my one plus 7 pro and i was fastboot it with twrp img but i didn't install the twrp recovery one my phone so now the phone blocked on de bootloader unlock screen, I tried to switched of but always back on the same screen, please need help how to do ,thanks
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
saransh186 said:
whenever i boot i am stuck at this screen. I flashed the wrong boot.img. How to fix this?
Click to expand...
Click to collapse
Enter fastboot and flash the correct boot.
@soka said:
Enter fastboot and flash the correct boot.
Click to expand...
Click to collapse
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
saransh186 said:
Unable to enter fastboot
Everytime i switch on the device this is the only screen i see
Click to expand...
Click to collapse
I figured it out. basically when i get to the above attached image I was required to hold volume up+down+power key until the fastmode doesn't comes up. It will take 20-25 seconds. So you will be required to hold it for that long.