Database Info

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"

Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"
I'm rooting my HTC One S the first time. And I was stupid and thought that HTC One X Clockworkmod flash would work.
Now I know how flashing and clockworkmod installing works but before that I accidentally flashed the One X command: "fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img" and now when I go to recovery it gives me a red text and nothing works.
I searched everywhere for a guide to remove it and did not found. So I thought I could flash it over with an One S flash, but then when I entered the command: "fastboot flash recovery r1-modaco-recovery-clockwork-touch-ville.img" It gave me this: "error: cannot load 'recovery r1-modaco-recovery-clockwork-touch-ville.img'. My phone is connected perfectly, when I type 'fastboot devices' it shows me my phone is there.
So I think this is not a big problem for developers. Can anyone tell me what to flash or do to get rid of the One X recovery? Otherwise I just have to live with a phone with unlocked Bootloader and no access to root

Do you have the IMG I the directory from which you are running fast boot?

edscholl said:
Do you have the IMG I the directory from which you are running fast boot?
Click to expand...
Click to collapse
Ofcourse

rixrasta said:
Ofcourse
Click to expand...
Click to collapse
mabey I should just do a factory reset :/

Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
http://www.clockworkmod.com/rommanager
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--

rugmankc said:
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
Click to expand...
Click to collapse
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.

rixrasta said:
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
Click to expand...
Click to collapse
Try this twrp .img
http://teamw.in/project/twrp2/100
The red text will stay till you relock, I believe, or flash stock recovery--

twrp recovery is the way to go. Me too I couldn't install the clockwork one!

rugmankc said:
Try this twrp .img
h ttp://team w. in/projec t/twrp 2/100
The red text will stay till you relock, I believe, or flash stock recovery--
Click to expand...
Click to collapse
I flashed the "openrecovery-twrp-2.2.2.0-ville.img". Didnnt change anything :/

sorry to hear that, not sure what else to do, so you still have onex recovery?
even if you run an ruu, i think you still have to flash the stock recovery first. haven't read up on that much, as never needed to run one
Don't know if trying to flash the stock recovery will help. I have the original one at home, but not sure if that is what they still call stock recovery with new ota's having come out

If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)

usaff22 said:
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
Click to expand...
Click to collapse
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img

the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2

stunner2002 said:
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
fastboot ->reboot bootloader ->bootloader ->recovery. Absolutely no change, It took half a second to bring up the "HTC quietly brilliant" logo and about two seconds for the red text to appear under it. No buttons work after that and I just have to hold the power button down to shut it down.
And by bootloader is unlocked!

As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".

If this is the thing where you go int recovery for a millisecond and then back to the 'red text' screen (you have to watch carefully to notice), you should try erasing your cache in fastboot mode.
fastboot erase cache
Click to expand...
Click to collapse
-Jobo

It's gotten a little confusing and some suggestions are being repeated. I wonder if the android icon you are describing is the stock recovery symbol. At that screen have you tried to press vol+ or maybe volume-. I forget which one takes you to stock recovery. May want to check on that.
Also, have you tried typing "fastboot boot recovery" to go straight to recovery, bypassing htc restrictions
Here is very early stock recovery--not sure if it is still considered "stock" with new versions out now--I did mention that earlier--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
I did have issues fastbooting recovery before. You can as mentioned try fastboot erase cache before fastbooting recovery. And change the name of your recovery to just recovery.img before you fastboot.
I assume you have nandroid backup on phone and copies of it and sdcard backup on pc.
I think when I had issues with recovery sticking it was my N1 and I typed "fastboot erase system" first, then fastbooted recovery. Then wiped all and restored nandroid. I am not sure we can do that on the 1s with no s-off. Someone else may know.
Can you access sdcard where you could reformat it fat32 thru a windows formatter program. Of course copy all to pc first. Sometimes sdcard formats help things you wouldn't expect it to.
Some folks have reported formatting works better thru phone on the 1s, maybe because it is an internal card. I did it once and think I had to redo it thru phone. But, if it gets recovery working, no big deal.
All these are suggestions and as the devs say--at your own risk--
I thought you said you said in first post, phone works, just no root capabilty. If that is true it should be fixable--I hope.
---------- Post added at 05:06 PM ---------- Previous post was at 04:32 PM ----------
rixrasta said:
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
Click to expand...
Click to collapse
you should also have adb.exe if you are using adb--

frdd said:
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
Click to expand...
Click to collapse
Okay I waited for 10 minutes, nothing happens. I've even tried to hold down all the button combinations(with the three buttons) for a few minutes.
I've tried flashing everything and fastboot boot just takes me directly to the recovery with the red text. I flashed both the recoveries in the all-in-one tool.
As I know absolutely nothing about RUU(only what the letters stand for) then I'd rather not do that because I read from some threads that RUU has quite a high chance to mess up your phone. Or if you direct me to a tutorial that u insure me that is 100% good then I could give it a go : D

[
I think I have made ​​the same mistake of flash recovery, but I can not get into cwm recovery, I only appear for 1 second the recovery, then restarts and returns to the operating system. SD card, all changes are discarded when you restart the phone, which is also only if I try to install or remove some utility. Can not install any recovery, even if fastboot works well and looks real mind install the recovery but when I reboot, it returns to its previous behavior, with recovery not working. I tried to install the recovery in every way, from fastboot, from All in one with quickroot, but none of these operations has changed the state of the system.
Unfortunately you can not install a Stock RUU because the bootloader unlocked and the recovery is not the stock, and especially not when there is no tutorial to follow to bring this situation to the ONE S, to its original state
Hopefully someone will be able to find a solution to your and my problem.

One option you guys may need to entertain, if applicable, would be to exchange phones with Carrier. Worth a shot--
I have not heard of this exact issue, but most comments say if you can't boot to recovery you are bricked--
Has anyone tried "fastboot boot recovery" command in terminal window?

[Q] Can`t flash recovery

Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?

n.N.n. said:
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
Click to expand...
Click to collapse
do you reboot into recovery when done or straight to OS

playya said:
do you reboot into recovery when done or straight to OS
Click to expand...
Click to collapse
The guide says to unlock bootloader, reboot to os, change settings, flash recovery, reboot, root.
But after your input, I did try it without the complete reboot and it worked. But shouldn`t a flashed recovery be persistant?
Edit: Did a second reboot, now there is the stock recovery again =/ But the root persisted.

[Q] Cannot enter recovery after flash of TWRP
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?

Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon

Have tried several recovery images
timmaaa said:
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, I have tried both TWRP 2.7.1.0 and 2.7.1.1 and Stock-recovery.img from 2008-12-31 - they all freeze in Android prompt when I try to boot in recovery mode. The only difference being, that only TWRP 2.8.0.1 causes the prompt to tyrn blue and then fade away.

The device just displays the Android [1+ said:
logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.

Trie advanced reboot to recove - no luck
habnzrot said:
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Click to expand...
Click to collapse
When I select reboot - recovery, I just get a brief message that 1+1 is rebooting and then it freezes in the Android prompt as before.

Re: can't flash a recovery that will work
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.

Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....

Success, finally
driftt said:
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Click to expand...
Click to collapse
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
Thanks milesman, but as you can see from the post above, the using the Philz image was successful. However, your suggestions may help other people, since the process really seems not to be robust.

had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go

TorkelJensen said:
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
I've had my OPO for a couple of weeks now and have had this problem all along. It took until today that i found this thread with someone having the exact same problem as me. After flashing a LOT of different recoveries (and different versions) I too noticed the only recovery I could successfully enter is Philz (although not all versions). I would prefer TWRP as recovery, but as long as I have one that is working that's good enough! It does however annoy me that almost nobody else has this problem. It makes me believe there is something wrong with the device. Flashing recovery in fastboot is always successful according to the logs. Erasing recovery in fastboot before flashing new one did not solve the problem either.
Before unlocking the bootloader, installing recovery and rooting, I updated the device from 33R to 38R. I now regret not doing that before updating...
I uploaded two videos showing the artifacts. The videos were recorded right after installing openrecovery-twrp-2.8.1.0-bacon.img from goo.im.
Since I haven't posted that much on XDA before I wasn't allowed to post links, please copy and paste.
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
As written in the first post by n.N.n. this problem is not related to this option. The checkbox is unticked and recovery doesn't get replaced by CMs stock, it fails to boot.

Couldn't flash any recovery until I unchecked the "update CM recovery" option in the developper, thanks for the tip ! I didn't think this was also protecting the recovery !

I've had same exact probem when flashing twrp 2.8.x.x from fastboot or twrp. As a last resort I gave Flashify a go and to my surprise, it worked.

I had the same problem, but PhilZ's lastest (6.58.8 as of now) worked for me. I wonder why this is happening to some of us, but I'm glad I sorted it.

Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
Thanks, that solved the problem for me! I've flashed TWRP and CWM, but after rebooting into recovery mode there was always the CM stock recovery. After unchecking this in the dev settings it worked as it should.

milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This worked for me thanks.

milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This doesn't work for me.
erasing 'recovery'...
OKAY [ 0.026s]
finished. total time: 0.026s
Still stock recovery after flashing TWRP. Why is this so weird?
The Update thing in Developer is unchecked.
My other OPO was perfect
---------- Post added at 02:32 PM ---------- Previous post was at 02:19 PM ----------
TorkelJensen said:
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
This works for me.
Click to expand...
Click to collapse

After installing Custom Recovery (mine id TWRP), turn off the handphone. After that, do directly the boot to recovery (On/Off Button + Volume Down). DO NOT do the normal start, since the system will erase the custom recovery (and instal the "standard" recovery)

Stuck at "...unlocked...booting now..." Bricked?

Solved.
AL10, NXT-C900B133, rescue0.3, NEXT
I unlocked bootloader, installed TWRP, and rooted using SuperSU with no problem by following these directions:
http://forum.xda-developers.com/mate-8/general/guide-unlock-bootloader-root-install-t3301371
I then formatted data using TWRP wipe, then tried to install Stock Rooted No Encrypted Boot from
http://forum.xda-developers.com/mate-8/development/rom-stock-rooted-encrypted-boot-t3303606
The phone never gets past "...unlocked...booting now...." (I did not install insecure_boot because I had trouble finding it---it is not in Mate 8 Android Development, only in Mate 8 Original Android Development.)
I can get to fastboot and to the Huawei recovery in Chinese (which doesn't work---wifi downloading stops with an exclamation point), but TWRP is gone, and I can't get it back by reflashing it. I've tried HiSuite recovery, unbricking using the Italian knife following these instructions:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
with various roms, and I've tried force flashing an UPDATE.APP from /sdcard/dload. No joy.
I caused the problem by installing a B331 rom when I was at B133—dyslexic much? Once I got TWRP back, flashing a B180 rom worked fine.
The difficulty was getting TWRP back. To do that, I flashed the following files using fastboot—it may be overkill:
TWRP-2.8.7.0-ENG.img,
insecure_boot_b331.img,
and the files in
L29Fastboot.rar.
TWRP

Hey ho!
I had exactly the same problem yesterday.
I figured out my system only was able to boot when I hold down [vol-]&[power].
Then the "not trusted message" had a few more lines and the phone booted up.
When it's up again, you can use adb to reboot to fastboot: adb reboot bootloader
You can also try to go directly to recovery if you alrteady flashed it: adb reboot recovery
From threre you can try again.
btw: I had to use a complete different TWRP version. 3.x somewhat. I think it was from here: http://forum.xda-developers.com/mate-8/development/recovery-twrp-huawei-mate-8-t3298567
Info: I was NOT able to use [vol+]&[power] for Recovery, eRecovery or anything else. I was just stuck.
I hope it helps.

I recommend after getting your device back on track to use twrp to make a recovery on your microsd card. That way u have a sure chance of getting bwck to working order

Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?

iAngus said:
Same problem here, but when I try to flash recovery or boot image using fastboot, I get the message "FAILED <Remote: command not allowed> ".
Any idea?
Click to expand...
Click to collapse
Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".

Make sure you have turned on debugging mode and that your device is listed with "fastboot devices".
Click to expand...
Click to collapse
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".

iAngus said:
The debugging mode is on since I unlocked and rooted the phone and the device is listed in "fastboot devices".
Click to expand...
Click to collapse
you could fix the same problem I have is not to do help me

Moto g xt1033 black screen

My Moto G won't startup,the screen turns black after the Motorola symbol.I've tried to flash some ROMs,tried to upgrade the bootloader(to some recent version,i think) to 41.1A.
Everything i do in Fastboot seems to work fine,but,when i try to use the feature,it continues the same.I've flashed TWRP recovery,but when i try to use it,the standard recovery open,if i do "fastboot erase userdata" and "fastboot erase cache" the console says its ok, but nothing has been erased.
Everything i try to do,won't work.I thought there was a problem with battery,cause i let it discharge fully,but now i'm seeing that is firmware problem.
I've tried everything on the internet,nothing worked.

I suppose you have an unlocked bootloader, right? If not, unlock it.
I had the problem with the stock recovery popping again after flashing TWRP. The solution is going to recovery exactly after flashing TWRP:
0.- Download TWRP again just to discard the possibility of a bad download.
1.- Boot the phone into fastboot mode.
2.- Flash the recovery .img file
PHP:
(mfastboot flash recovery twrp_file.img)
see if it says "OK" in the computer's console. In the phone screen a pink text line should appear saying something like "file size mismatch OK".
3.- Without rebooting the phone, press vol- button until "Recovery" option is selected. After a couple minutes the TWRP screen will appear and will ask for permission for modify your filesystem.
If you reboot the phone before going into TWRP, stock recovery will be re-installed and TWRP will be lost.

moralesnery said:
I suppose you have an unlocked bootloader, right? If not, unlock it.
I had the problem with the stock recovery popping again after flashing TWRP. The solution is going to recovery exactly after flashing TWRP:
0.- Download TWRP again just to discard the possibility of a bad download.
1.- Boot the phone into fastboot mode.
2.- Flash the recovery .img file
PHP:
(mfastboot flash recovery twrp_file.img)
see if it says "OK" in the computer's console. In the phone screen a pink text line should appear saying something like "file size mismatch OK".
3.- Without rebooting the phone, press vol- button until "Recovery" option is selected. After a couple minutes the TWRP screen will appear and will ask for permission for modify your filesystem.
If you reboot the phone before going into TWRP, stock recovery will be re-installed and TWRP will be lost.
Click to expand...
Click to collapse
Thx for reply,
Yes,i've unlocked bootloader.
Yesterday i've tried to flash a custom recovery using
PHP:
mfastboot flash boot twrp_file.img
Worked once,the next time i booted my phone,it booted normally.
When i've gained acess in the custom recovery,i tried to copy a cm12 ROM to phone's memory,but,without sucess,the progress doesnt moved a bit.
I Will try the way you Said and Post the results here :fingers-crossed:

moralesnery said:
I suppose you have an unlocked bootloader, right? If not, unlock it.
I had the problem with the stock recovery popping again after flashing TWRP. The solution is going to recovery exactly after flashing TWRP:
0.- Download TWRP again just to discard the possibility of a bad download.
1.- Boot the phone into fastboot mode.
2.- Flash the recovery .img file
PHP:
(mfastboot flash recovery twrp_file.img)
see if it says "OK" in the computer's console. In the phone screen a pink text line should appear saying something like "file size mismatch OK".
3.- Without rebooting the phone, press vol- button until "Recovery" option is selected. After a couple minutes the TWRP screen will appear and will ask for permission for modify your filesystem.
If you reboot the phone before going into TWRP, stock recovery will be re-installed and TWRP will be lost.
Click to expand...
Click to collapse
Again,i've tried to flash TWRP recovery,the message "Missmatched partition size OK" appears in the phone,when i try to open Recovery,the Android logo appears with a !.
I don't know what to do,nothing works , even if i don't reboot the phone,the stock recovery had been re-installed.

All commands fail in fastboot

Hello everyone,
after unlocking my bootloader (on a Realme 5 Pro) to install TWRP and custom ROM, I am now stuck at trying to make fastboot do anything.
No matter which fastboot command I try, the phone won't execute it. I instantly get a "FAILED" and "(No error)" returned and the phone exits fastboot, showing some logo with a chinese message, as well as "press any key to shutdown" in the top left corner.
The only excpetions to that behaviour:
1. "fastboot devices" works as expected and recognizes the phone.
2. "fastboot boot [path to TWRP .img file]" sometimes gets stuck at "downloading boot.img..." indefinitely, sometimes it fails like all the other commands
3. "fastboot flash recovery [path to TWRP .img file]" gives an instant "FAILED", but the error message is "requested download size is more than max allowed"
I've tried re-locking and unlocking the bootloader, when unlocked both colorOS and fastboot recognize the bootloader as being unlocked.
I have no clue what to try at this point, hopefully someone can help me out?

Same problem here.
Mine is Realme 3 pro with the new version of realme UI, RMX1851, C.04, I have unlocked bootloader without downgrading it to color os 6, but now I cannot flash twrp in my device. After going into fastboot mode, after applying the commands, it says "FAILED" (remote: GetVar variable not found) and sometimes directly "ERROR"

The fix was an incredibly easy one, but I only found it/got the idea through a lot of googling... simply used a different PC (that I never used adb and fastboot with before), let windows search for drivers online, and BAM, it works!
Hopefully this will help someone in the future.
If you don't have more than one PC, I guess the best bet would be uninstalling all adb and fastboot related drivers.