Custom Recovery's won't install - ONE Q&A, Help & Troubleshooting

Other than CM Recovery I cannot get anything to install, not even the stock or TWRP. They all install fine and say that it is all flashed fine regardless of how I flash the recovery, but then when booting into recover I get the boot screen for around 5-10 seconds a brief flash of a plain black screen with some text (though sometimes not even this shows up) and then nothing, the phone is still on however as I have to turn it off before turning it back on again, there is just nothing displayed on the screen.
Also my boot image still shows as FreedomOS however since freedom I have had Paranoid and CM installed so not sure (the boot animation is CM but the image shown with the one plus logo has FreedomOS at the bottom)
Any help would be wonderful
Thank you

Never heard of that rom. What device do you have?
Sent from my A0001 using XDA-Developers mobile app

Did you Root before ?

DerRomtester said:
Never heard of that rom. What device do you have?
Click to expand...
Click to collapse
I have a OnePlus 3

Cholerabob said:
Did you Root before ?
Click to expand...
Click to collapse
I did root yes

McreativeH said:
I have a OnePlus 3
Click to expand...
Click to collapse
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.

shubhaemk said:
Wrong forum bro. Search for OnePlus 3 in search bar. You may get some help on freedom os is there.
It seems like you had a Firmware flash. You can try flashing recovery using a "PC with adb".
Secondly Google and download Firmware for one plus 3 . And flash it using recovery.
Again. Try booting into recovery, if you can't , you have lost recovery while flashing Firmware. Flash the recovery again using "PC with adb".
Hope it helps. Thanks.
Click to expand...
Click to collapse
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One

McreativeH said:
I see... I clicked the my device section via the XDA app and for some reason it said I have a OnePlus One
Click to expand...
Click to collapse
Hope your phone didn't turned into OnePlus One.
Regards! Delete the thread and start over there. See you

Related

[Q] CWM isn't working

I've recently unlocked bootloader, rooted my one x, but i CWM does not work. I've tried to reflash different recoveries many times via fastboot, and everytime i got the message that image was flashed succesfully, but once i reboot and select recovery, my phone freezes everytime on HTC logo time. What else can be done to install and run recovery sucesfully ? thanks in advance
berkis2 said:
I've recently unlocked bootloader, rooted my one x, but i CWM does not work. I've tried to reflash different recoveries many times via fastboot, and everytime i got the message that image was flashed succesfully, but once i reboot and select recovery, my phone freezes everytime on HTC logo time. What else can be done to install and run recovery sucesfully ? thanks in advance
Click to expand...
Click to collapse
You can download the app goo manager and from there hit menu and then flash recover via the app. Then reboot into recover
Sent from my HTC One X using Tapatalk 2
berkis2 said:
I've recently unlocked bootloader, rooted my one x, but i CWM does not work. I've tried to reflash different recoveries many times via fastboot, and everytime i got the message that image was flashed succesfully, but once i reboot and select recovery, my phone freezes everytime on HTC logo time. What else can be done to install and run recovery sucesfully ? thanks in advance
Click to expand...
Click to collapse
Have you tried using the 1-click solutions in the dev forum?
CWM: http://forum.xda-developers.com/showthread.php?t=1671873
Or alternatively, you can download GooManager Beta (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) from the Play Store and use it to install TWRP
stnguyen09 said:
Have you tried using the 1-click solutions in the dev forum?
CWM: http://forum.xda-developers.com/showthread.php?t=1671873
Or alternatively, you can download GooManager Beta (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) from the Play Store and use it to install TWRP
Click to expand...
Click to collapse
1-click solution - tried it at very first time, and many times after. the same freeze result.
5 min ago ive tried goomanager and flashed twrp, got the same freeze on recovery...
Any more ideas ?
berkis2 said:
1-click solution - tried it at very first time, and many times after. the same freeze result.
5 min ago ive tried goomanager and flashed twrp, got the same freeze on recovery...
Any more ideas ?
Click to expand...
Click to collapse
This is just me being cautious, but are you on the AT&T/Rogers/Telstra One X? I know quite a few international One X users stumbled onto this forum thinking it was theirs.
stnguyen09 said:
This is just me being cautious, but are you on the AT&T/Rogers/Telstra One X? I know quite a few international One X users stumbled onto this forum thinking it was theirs.
Click to expand...
Click to collapse
good question . No, mine is orange UK
berkis2 said:
good question . No, mine is orange UK
Click to expand...
Click to collapse
Ah, you belong over here then: http://forum.xda-developers.com/forumdisplay.php?f=1533
This explains why the recoveries weren't working. Our devices can actually be considered completely different even though they share the same name. Just for reference, your device is called the Endeavor while ours is the Evita
Edit: Here's the sticky in their dev forum that has links to recoveries and such http://forum.xda-developers.com/showthread.php?t=1603905
thank you, I thought its the same device

Problem with huawei vision

Hi!I have a problem with my huawei vision.I wanted to install android 4.2.1 jelly bean from another phone and now my phone start and stuck at huawei logo....PC dont recognized him......No recovery No fastboot No nothing.....What should i do?:|
Someone help me?please?
You should never install ROMs or flash kernels which are made for another phone to your own phone. Each ROM is made specificaly for one device making it hardly possible to work properly on others.
If you have an unlocked bootloader then you could simply flash a kernel with CWM recovery and flash another supported ROM.
If you have a locked bootloader (also if you don't know what that is, then this is probably what you have) and if you haven't flashed any custom kernels (if you don't know what those are then you probably haven't) then your only hope is to find and flash the stock ROM back on it.
EDIT: If you're phone is the Huawei U8850 aka Vision then this is a stock ROM you can use:
https://mega.co.nz/#!hxIEDTrZ!ejEk1AC5f6S4aJ0iLx2rIkB0gMJIUMY5-_8iPDIZcfI
Probaly i have locked bootloader ....but how i unlock bootloader because my pc don recognized my phone nothing....
Download the U8850 Upgrade package from here. Unpack it and install SUT L3 and the USB drivers from the unpacked files. With SUT L3 you will flash this firmware which will enable CWM recovery on your device which you can access by pressing Vol- and Power button at the same time when you turn your phone on (you don't have to enter it after flashing this firmware I gave you because it should work fine).
First boot will take a while, but if it takes more than aprox. 15 minutes than something's wrong again.
EDIT: If everything goes fine and you want an ICS ROM than you can hop to this thread/tutorial. BUT DO THIS ONLY IF AND AFTER YOU HAVE SUCCESSFULLY INSTALLED AND BOOTED THE ABOVE FIRMWARE!
Dont work....Pc dont recognized him......
If SUT L3 is not detecting your phone when you connect it, neither turned off nor turned on, then I'm afraid you just bricked your phone.
Thank you! I finish problem:*!
Now ...i have a problem...when i want to install firmware .....error : task 2 of 2 ,download image fail error=device_not_configure
Glad to hear that! Just remember to never use ROMs which are not made specifically for your device!
Sent from my Xperia X10 using xda app-developers app
But ....with error?.....i cant install android:|.....error appear in sut l3..
Did you install the required USB drivers from the upgrade tools I gave you?
Sent from my Xperia X10 using xda app-developers app
Yes i install.....now boot recovery .....but i cant select anything..
Use the volume hard keys.
Sent from my Xperia X10 using xda app-developers app
i use.....but when i click on "install zip from sdcard" nothing
How?
U must first transfer a ROM in zip format to your SD card and then select it via recovery.
But I lost you there a little. Was the recovery there before or did you successfully install the firmware via SUT L3? Because if you have, than you should be able to boot the Gingerbread ROM from the firmware.
Sent from my Xperia X10 using xda app-developers app
CCVader13 said:
First boot will take a while, but if it takes more than aprox. 15 minutes than something's wrong again.
Click to expand...
Click to collapse
Hi CCVader,
I've got a similar problem with my Huawei Vision that I bought/bricked yesterday. I managed to download an image file to my phone that was rooted and allowed me to boot to cwm. From the CWM Recovery screen I installed jellybean.zip, but after restart the phone hangs on the red Huawei screen. Every minute or so the screen goes black then comes right back to the red logo. Is this the 'first boot' you are describing above? Shall I just leave it doing this for 15 mins?
Thanks.
James.
jamesprocha said:
Hi CCVader,
I've got a similar problem with my Huawei Vision that I bought/bricked yesterday. I managed to download an image file to my phone that was rooted and allowed me to boot to cwm. From the CWM Recovery screen I installed jellybean.zip, but after restart the phone hangs on the red Huawei screen. Every minute or so the screen goes black then comes right back to the red logo. Is this the 'first boot' you are describing above? Shall I just leave it doing this for 15 mins?
Thanks.
James.
Click to expand...
Click to collapse
You can't just flash ROMs without the appropriate kernel istalled. U8850 comes with Gingerbread and with the GB kernel.
Flash this.
CCVader13 said:
You can't just flash ROMs without the appropriate kernel istalled. U8850 comes with Gingerbread and with the GB kernel.
Flash this
Click to expand...
Click to collapse
OK, I'll give that a go when I get home. The firmware you've linked me to - is this GB?
One thing that concerns me - the Software Update Tool detects my phone if I attach it while it is on CWM, but if I try to install the original image it keeps failing. Equally, trying to install a tested nb0 file from the stock recovery tool also now fails.
The little bit of home I have is that I can still get to CWM Recovery - as long as I can do this, does that mean there is a chance I can unbrick my phone?
Many thanks for the quick response.

[Q] Clockwork Mod Recovery Failure

I have searched and can't find out anything about this, but for some reason I can flash recovery-clockwork-6.0.4.5-hammerhead.img through fastboot and then get into CM recovery. However, if I leave recovery and try to boot into it again, I get the dead droid picture. I can flash CM again and it'll work, but again, for a single use. I've never had this problem before on any Droid I've owned and I can't seem to find anyone dealing with it in this forum. Any help would be greatly appreciated.
No this phone is not rooted. I have unsuccessfully attempted this with CM (upon exiting recovery mode, you are prompted to root your phone if it hasn't been rooted).
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
You should also search the rules and list in he correct forum. This is not for questions only development
Sent from my Nexus 5 using XDA Free mobile app
also, clockwork mod recovery is long discontinued and provides no support anymore.
EddyOS said:
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
Click to expand...
Click to collapse
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
strakajagr said:
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
Click to expand...
Click to collapse
In any case, I can flash something else since CM is no longer supported. Thanks.
strakajagr said:
In any case, I can flash something else since CM is no longer supported. Thanks.
Click to expand...
Click to collapse
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How do I go about locking the bootloader after it's unlocked?
strakajagr said:
How do I go about locking the bootloader after it's unlocked?
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
BirchBarlow said:
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
Click to expand...
Click to collapse
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
strakajagr said:
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
Click to expand...
Click to collapse
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
simms22 said:
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
Click to expand...
Click to collapse
Word. Thanks.
Next order of business is figuring why there is so much lag when I text/gchat in 5.0. This is the whole reason I got into this mess. I couldn't wait 3 more weeks. Sadly, when I type, the keyboard freezes constantly. I figure I'll install a recovery mode correctly and then try to tackle that problem.

[Q&A] [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]

Q&A for [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][hammerhead] TWRP 2.8.1.0 touch recovery [2014-10-29]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Touchscreen Issues
I have tried to use TWRP as my recovery option but whenever i go into recovery mode the touchscreen ceases to work. and i have to do a hard reboot. On everyday use the screen works flawlessly and the issue only presents itself when using TWRP. My question is if there is anyway to use TWRP with the physical buttons instead of the touch interface.
Any help will be appreciated.
glm0025 said:
I have tried to use TWRP as my recovery option but whenever i go into recovery mode the touchscreen ceases to work. and i have to do a hard reboot. On everyday use the screen works flawlessly and the issue only presents itself when using TWRP. My question is if there is anyway to use TWRP with the physical buttons instead of the touch interface.
Any help will be appreciated.
Click to expand...
Click to collapse
No only touchscreen. You should check the way you install TWRP on your Nexus 5.
I upgrade twrp with this zip http://forum.xda-developers.com/google-nexus-5/general/recovery-zip-collection-t2636279
it's normally that after flash zip into twrp , reboot system and then stuck on teamwin logo for 2 seconds after twrp starts?
tnx
ironia. said:
I upgrade twrp with this zip http://forum.xda-developers.com/google-nexus-5/general/recovery-zip-collection-t2636279
it's normally that after flash zip into twrp , reboot system and then stuck on teamwin logo for 2 seconds after twrp starts?
tnx
Click to expand...
Click to collapse
Fastboot flash back to stock recovery, boot into recovery. Fastboot flash latest TWRP recovery. Test
So the latest TWRP works with the official release LRX21O?
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Yeah, same here
siddlv said:
So the latest TWRP works with the official release LRX21O?
Click to expand...
Click to collapse
Yep
BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Did you use chainfire root method?
Sent from my Android 5.0 Nexus 5
Ben36 said:
Yep
Did you use chainfire root method?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
I flashed lollipop image using flash-all script and then I flashed the recovery manually using fastboot with the phone in bootloader mode
BabboDemonio said:
I flashed lollipop image using flash-all script and then I flashed the recovery manually using fastboot with the phone in bootloader mode
Click to expand...
Click to collapse
Weird... Mine works but I fastboot'd just boot and system img and then booted into recovery and wiped caches before booting up
Sent from my Android 5.0 Nexus 5
Ben36 said:
Weird... Mine works but I fastboot'd just boot and system img and then booted into recovery and wiped caches before booting up
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
A friend of mine has the same problem
On that first time it works, did you flash supersu 2.19?
Sent from my Android 5.0 Nexus 5
Ben36 said:
On that first time it works, did you flash supersu 2.19?
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Yes.. But then it stopped working again
BabboDemonio said:
Hi, I have this problem.. I flashed the official lollipop image yesterday and after that, TWRP,all using fastboot commands. The fact is that TWRP works the first time after I Install it.. But then it stops working, and instead of booting into recovery, it display the Android symbol with a red exclamation mark over it. Anyone has the same problem?
Click to expand...
Click to collapse
Same problem, I don t know why
Could it be linked to AOSP branch? http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512
Primokorn said:
Could it be linked to AOSP branch? http://forum.xda-developers.com/google-nexus-5/general/warning-lollipop-aosp-roms-broken-t2930512
Click to expand...
Click to collapse
The fact is that it didn't happen while I had dev preview.. But my recovery at the time was Phil'z
BabboDemonio said:
The fact is that it didn't happen while I had dev preview.. But my recovery at the time was Phil'z
Click to expand...
Click to collapse
There are obviously differences between the previews and the final factory imgs but I don't think it depends on the recovery you had/have.
Primokorn said:
There are obviously differences between the previews and the final factory imgs but I don't think it depends on the recovery you had/have.
Click to expand...
Click to collapse
Unfortunately the problem seems to be random, a user said that he flashed the recovery a second time and it didn't happen again (I tried that without success) another one didn't experience the problem... Don't know
BabboDemonio said:
Unfortunately the problem seems to be random, a user said that he flashed the recovery a second time and it didn't happen again (I tried that without success) another one didn't experience the problem... Don't know
Click to expand...
Click to collapse
Found a solution. Install with adb CF auto root by chainfire (on his thread) and then put recovery.IMG always with adb. All work now

can't update to the lase update (xnph44s)

hi,
i just received the lastest update of the oneplus one (my one is rooted and i have twerp recovery) and when i click on "install update", the phone reboot to recovery and then a window open like when i flash a zip and it fails and i get redirected to the twerp menu and then i don't know what to do. i tried to find the file and to flash it and it still didn't work.
do you have an idea?
thank you
bigben14 said:
hi,
i just received the lastest update of the oneplus one (my one is rooted and i have twerp recovery) and when i click on "install update", the phone reboot to recovery and then a window open like when i flash a zip and it fails and i get redirected to the twerp menu and then i don't know what to do. i tried to find the file and to flash it and it still didn't work.
do you have an idea?
thank you
Click to expand...
Click to collapse
where did you get this file from? what Rom?
gd6noob said:
where did you get this file from? what Rom?
Click to expand...
Click to collapse
i used the file from oneplus, the one i got from the over the air update
https://www.dropbox.com/s/1x5qr4xgto4276u/Screenshot_2014-11-16-13-07-39%5B1%5D.png?dl=0
bigben14 said:
i used the file from oneplus, the one i got from the over the air update
Click to expand...
Click to collapse
I flashed the stock recovery to get the update to install. Then just flash twrp again after that. It is easy and fast.
tech_baggie said:
I flashed the stock recovery to get the update to install. Then just flash twrp again after that. It is easy and fast.
Click to expand...
Click to collapse
still doesn't work, i get the same fail as the one from twerp (i put a picture of it in the last post
bigben14 said:
still doesn't work, i get the same fail as the one from twerp (i put a picture of it in the last post
Click to expand...
Click to collapse
That is weird, hmmm. Maybe if you return to stock via fastboot? There is a how-to thread explaining how to do that. Otherwise I am not sure. It worked when I did it. Will check if there is another way.
i did get back to stock recovery via flashboot and with OPO Toolbox
i'd love it if you can find a solution, i'll try to look for one too on my side
thank you
try the lastest TWRP v2.8.1.0?
I went back to stock recovery so there shouldn't be any problem of update of the recovery right?

Categories

Resources