Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
DaiMinzz said:
Today I wanted to flash a CM12 lollipop ROM
I unlocked the bootloader with succes, adb commands said that the recovery .img was flashed okay!,
So i got the following issue,
My oneplus one won't boot in to recovery, or is stuck at the Oneplus logo, or the 1+ logo just disappears and the screen goes crazy with green and blue lines... and i see weird things on screen. a normal boot and fastboot is fine everything is just ok, but not recovery,
I tried TWRP, PHILZ TOUCH,CWM, even to stock CM recovery doesn't flash anymore
i did many tutorials and followed step by step im sure thats not the problem.
I tried with the oneplus one toolbox and command window but nothing
Need help!
Click to expand...
Click to collapse
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
stevekind said:
Hi, maybe your recovery images are corrupt. Had that once, thought I was going crazy. Redownload, compare md5 sums (I know it sucks...), perhaps use a different browser to download, then flash again. Good luck!
Click to expand...
Click to collapse
Still the same problem didn't work
Im sure everthing on the pc went ok, but my Oneplus has recovery bug
Related
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
jwt98 said:
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
Click to expand...
Click to collapse
Reflash the previous version you were running.
jwt98 said:
Just used TWRP manager to flash the new 2.8.0.1 wlv build to my m8 and now it just bootloops into recovery everytime I reboot. What do I need to do to resolve this issue. thanks
Click to expand...
Click to collapse
Do not use TWRP manager to install recovery. Use Flashify.
TWRP manager flashes to the wrong block. It flashes to mmcblk0p43 where as you need to have it on mmcblk0p44.
What version of firmware are you on. You will need to update your boot image.
To get out on the bootloop I had to install a Rom which was viper Rom 2.4. When I boot my phone, it still shows the twrp splash screen with the red text at the bottom. Doesn't even show boot animation. Seems like it freezes then home screen pops up like nothing's wrong. Any way I can get my HTC splash and aninmation back. Tried flashing a new boot animation but won't take. Is it still trying to boot to twrp.
jwt98 said:
To get out on the bootloop I had to install a Rom which was viper Rom 2.4. When I boot my phone, it still shows the twrp splash screen with the red text at the bottom. Doesn't even show boot animation. Seems like it freezes then home screen pops up like nothing's wrong. Any way I can get my HTC splash and aninmation back. Tried flashing a new boot animation but won't take. Is it still trying to boot to twrp.
Click to expand...
Click to collapse
Like other person said. You flashed your recovery to your system. You need to go to boot loader an fastboot recovery so it goes where it is supposed to. Then enter recovery via bootloader so you r really in recovery then flash your ROM an it will take care of your issue. Always fastboot recovery to avoid these problems.
I did the same thing through TWRP manager, and reflashed recovery through fastboot, restored, works fine. Thanks for the fix
greydelta38 said:
I did the same thing through TWRP manager, and reflashed recovery through fastboot, restored, works fine. Thanks for the fix
Click to expand...
Click to collapse
Glad to hear I could help.
Hey, so I have a problem with my pico. For some months I didn't use it much. I had install cm11 which was experiencing some bugs. Anyways yesterday I tried to flash the miuiv5 ROM however the device didn't boot up. It got stuck in the bootscreen. I found out that I hadn't made an SD-EXT Partition needed for miui. So, I made it and tried to flash miui again. But now the phone doesn't even get to the bootscreen. When I boot my phone the HTC screen comes followed by a black screen. After a few seconds the black screen is gone and again the HTC screen comes booting up the recovery
I tried to flash other ROMS with no success at all. I have TWRP v2.2.2.1 and tried installing CM,AOKP as well as PAC ROMS with no success. Any solutions???
TAOprajjwal said:
Hey, so I have a problem with my pico. For some months I didn't use it much. I had install cm11 which was experiencing some bugs. Anyways yesterday I tried to flash the miuiv5 ROM however the device didn't boot up. It got stuck in the bootscreen. I found out that I hadn't made an SD-EXT Partition needed for miui. So, I made it and tried to flash miui again. But now the phone doesn't even get to the bootscreen. When I boot my phone the HTC screen comes followed by a black screen. After a few seconds the black screen is gone and again the HTC screen comes booting up the recovery
I tried to flash other ROMS with no success at all. I have TWRP v2.2.2.1 and tried installing CM,AOKP as well as PAC ROMS with no success. Any solutions???
Click to expand...
Click to collapse
LOL brother in which year you live
It's simple brother all you need is to upgrade your TWRP recovery
TWRP 2.8 (it may not flash all ROMS but test it if it works let me know): http://www.mediafire.com/download/3q7jz01f2ynqrlc/twrp_11_sep_2014.img
TWRP 2.7 (tested by me though i'm currently using it):
Recovery is attached below
Click to expand...
Click to collapse
Flashing Method (If you forgot how to flash it. Well then here it is )
1) Download the recovery.img..
2) Place the recovery.img someplace safe (for eg, C:/TWRP)..
3) Open the command prompt, and navigate to the folder in which you extracted the files..
4) Boot your phone into Fastboot mode, and connect it to the computer.. It should show "Fastboot USB"
5) In the command prompt, type :
Code:
fastboot flash recovery recovery.img && pause
If I helped ya! Press thanks
Hey guys,
recently I unlocked my bootloader without problems. Now I tried to install twrp 2.8.2.0 on my phone. I am full stock on 4.4.4.
I downloaded the file (http://techerrata.com/browse/twrp2/hammerhead) and I renamed it to recovery.img.
With the command "fastboot flash recovery recovery.img" I successfully flashed the new recovery. After that I chose "restart Bootloader" and after that I tried to select "Recovery mode".. Now the "teamwin" gets on my screen and suddenly my device boot up. I can't get into the recovery mode.
As I tried the second time, I tapped on the screen while "teamwin" stood there and suddenly my device vibrated like hell.
What I did wrong there guys? Was it a corrupt file or something?
Every answer would be very appreciated. =)
Oh damn, I think i got it now.
As it seems I am too stupid to inform myself before flashing the TWRP 2.8.2.0, which doesn't boot.
Sorry for this unecessary thread! I'll flash a previous version then! :3
2.8.1.0 works flawlessly. I still haven't been able to get 2.8.2.0 to work, I've given up trying.
Sent from my Nexus 5
It's a known bug with TWRP 2.8.2. For some reason it works for a handful people but I and others haven't been able to get it to work once, and I know I've tried everything you could possibly think of. Stick with 2.8.1 for now.
HTC One M7 GSM Recovery Update Problems]
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:
JacobHaze24 said:
HTC One M7 GSM Recovery Update Problems]
So I flashed TWRP 2.6.3.0 through adb fastboot on my HTC One M7 International version and it worked but when trying to install a custom ROM it had the status 7 error. So I thought updating TWRP to the latest version 2.8.5.0 would help but here is where the problem is, I update and flash it using adb fastboot and when I try to enter recovery mode it shows "entering recovery" in pink letters at the top then the screen goes black for a few seconds then back to the same "entering recovery" screen again, I've tried clearing the cache before and after flashing and also tried not clearing it at all with the same result. I've also tried flashing different versions of it and still the same, the funny thing is I can flash TWRP 2.6.3.0 again and it works fine just when I try to update it that's when the problems begin, the exact same thing happens with CWM 6.0.3.1 it works fine but when I try to update I get the same results, this also happens when trying to update through flashify and Rom manager. if someone could help me out with this it would be much appreciated :good:
Click to expand...
Click to collapse
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.
enigmaamit said:
I assume you have unlocked your bootloader from HTCDev.
Sometimes, flashing recovery after rebooting from from adb fastboot may fail to write recovery. My advice would be to boot manually into bootloader with power and volume down buttons, enter fastboot usb from there and then flash recovery.img.
Lemme know if that worked.
Best of luck.
Click to expand...
Click to collapse
yes I have already unlocked the bootloader through the htcdev site and adb never fails to write the recoveries its just only the TWRP and CWM recoveries i mentioned seem to work on my device i cant update to a newer one because it gets stuck on the "entering recovery" screen when i try to boot into recovery, im not quite sure why its happening
Okay I just tried what you said and the result is the same, I cant be the only one with this problem
JacobHaze24 said:
I cant be the only one with this problem
Click to expand...
Click to collapse
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!
enigmaamit said:
Hi Jacob. Sorry that you seem to be stuck at that step.
However, what you said above could be true and I would recommend asking this question in your device specific thread to get more accurate answers regarding your particular device. http://forum.xda-developers.com/htc-one/help
Best of luck!
Click to expand...
Click to collapse
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:
JacobHaze24 said:
Thank you for your help, I finally figured it out and am now running ViperOne 7.0.2 :good:
Click to expand...
Click to collapse
Glad you made it, and learnt some valuable skills along the way.
Thread closed.
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
divvykev said:
Have some experience in flashing Rom's in my time but tried to flash Carbon Rom on my 6 yesterday and got myself into a pickle.
Unlocked and installed TWRP Blue Spark and Root using the Toolkit.
When I was back in Twrp I installed the Rom and TWRP again and rebooted.
That's where the problem started. When it rebooted into TWRP I could not find where the GAPPS was. The directory structed seemed very strange. SDCARD was there but nothing in it. Could not find the user directory at all.
Carbon would not come out of bootloop.
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Only the MSM unbrick tool helped me out.
Can someone see what I did wrong here in not being able to find the gapps?
Thanks
K
Click to expand...
Click to collapse
Likely the phone was encrypted
divvykev said:
Tried to fastboot stock and then was left with a blank screen and a blue light only.
Click to expand...
Click to collapse
For me this happened a few times, including when I tried to 'fastboot boot' a wrong image or some latest bluespask Twrps. This is the state when the the phone has hung trying to execute something. The remedy is to hold the power button pressed for something like 10 seconds and the phone will switch off (this is a hardware feature so shlould not fail). After that I go to fastboot normally - press volUp+Power for a few seconds till the fastboot message. Also, make sure that you are not charging, as this seems to have prevented me going to fastboot once.