Database Info

recovery.IMG not found

OP Junior MemberThanks: 0
2 posts Joined: Sep 2014
I have a Motog 1040 tx.
I have unlocked the boot loader through Motorola's website
I have SuperSU installed. I have verified using an app the phone is rooted.
This my problem installing clockword mod...
When I go through the commands in terminal manager. It says recovery. IMG not found.
I've downloaded clockwordmod recovery peregrine for my phone model and renamed
it recovery.IMG and placed it in the sdcard memory card root.
I've tried placing flash image in my sdcard root as well and used that method as well.
Anyone know what I'm doing wrong? The sd card is listed as sdcard1 on my device. I've also noticed that there is an emulated sdcard listed.

You can flash recovery in fastboot mode by using the command fastboot flash recovery nameoffile.img

How do I go about doing that?

Make sure the phone is not connected to a USB cable. Press and hold both volume buttons, press and hold power for a few seconds, release all buttons and you should be in fastboot mode.

What do I do once in fastboot mode? Where do I enter the command and where do I place the recovery.img

Have a look here: http://forum.xda-developers.com/showthread.php?t=2577043

I need confirmation that you've placed adb and fastboot in the platform tools folder?
Fastboot doesn't work in command prompt. Is this due to windows 8.1 64 bit...?

Fastboot and mfastboot should work in Win7 by installing drivers.
Win8 is a little trickier: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/

OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?

Very good

deltadiesel said:
OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?
Click to expand...
Click to collapse
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.

audit13 said:
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.
Click to expand...
Click to collapse
Awesome it worked. Here's my other issue now though. Because I edited a file and inputted a string incorrectly in the root folder I had to install my stock ROM. Since reinstalling the stock ROM I have next to no memory left on my device. When I used mfastboot I did not clearvuser data so I wouldn't loose everything on my phone. What can I do about this. Will installing the custom ROM for my device clear this up?

I don't think a custom ROM is going to help you get back your memory.
Install Titanium backup. Backup your apps and data, do a full wipe of data, cache, and Dalvik and check memory usage. If that doesn't help, do a full wipe of everything, install the ROM, and restore from your Titanium backup. Just make sure to save your titanium backup folder to your PC before doing the full system wipe.

Oneplus One TWRP Bootloop

Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.

Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?

This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?

[HELP] Remove boot loop without root & USB debugging?

Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk

Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?

[Q] [Locked OP6] Bootloop after upgrading to 10.3.0 - how to recover without format

My dad got the OTA update to 10.3.0 on xmas day and installed it. However the phone is now stuck on boot logo. He has a locked phone just as it came out of the box (ie no TWRP, no OEM unlock, no root).
I am quite experienced with installing custom ROMs but with locked phones I am lost. Is there anyway to recover the device without deleting data / factory reset? This is because my dad has quite a lot of pics on the device that are not backed up (yeah I know...).
Things I've tried so far:
- reboot holding power button + volume up
- boot flash twrp from fastboot - no permission due to phone being locked
- in stock recovery I do not get access to device via cable
- installed Tool all in One - it sees phone via fastboot
I always use the Stock Fastboot ROMs for OnePlus 6 myself to recover from soft bricks but this wipes data so no option here. Unless there is a way to install parts of ROM? Any other tips or ideas from the awesome XDA community? :good:
Btw this is the update he installed:
Screenshot of update that was installed

If you boot on twrp, it does not ask for the pin code to access the data?
Maybe try the last twrp for OOS 10.3.0 : ( https://androidfilehost.com/?fid=4349826312261678088 )
Use command : fastboot flash boot twrp-3.3.1-16-enchilada-Q-mauronofrio.img
Try flash a new boot img :
Stock boot 10.3 img
https://drive.google.com/open?id=1w44cUg815g-H1h_6gObUVPLDTc_dtiMX

The phone is not unlocked and therefore has no TWRP recovery. This is my problem, if it was unlocked I would have figured out a way to fix it.
PS it does ask for pincode when accessing stock recovery

I'm not sure if this works on locked bootloaders but try switching boot slots using fastboot.

Couple of weird things:
-you don't need an unlocked bootloader for fastboot to boot back into the system
-the dual partition was designed precisely to prevent things like this from happening. When an update fails, you are supposed to roll back to the old slot you were on previously.
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?

Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try

awaiz said:
Hey
You can try to change the boot slot using fastboot mode
It can help uh maybe
Its worth to try
Click to expand...
Click to collapse
When I try to set it to slot A (it's B now) it says device does not support slots which is weird as 'fastboot getvar current-slot' does show it using slot B right now.
When I try to set it to B (ie current slot) it says: FAILED (remote: 'Slot Change is not allowed in Lock State').

awaiz said:
Anyway, since you are able to boot to fastboot, can you try to get to stock recovery again from fastboot and see if you can boot up to system from there?
Click to expand...
Click to collapse
When I reboot to stock recovery it gives two options:
- Wipe Data and Cache
- Advanced
There are two reboot options under Advanced:
1. Reboot to fastboot
2. Reboot to recovery
2nd option just boots it back to this same recovery. Boot to fastboot works as well. So there is no option to reboot the device.
Perhaps I can try to flash the stock ROM (kinda of dirty flash) but again not sure if that works on locked phone.

https://www.androidexplained.com/change-active-partition-slot/

JagDave said:
https://www.androidexplained.com/change-active-partition-slot/
Click to expand...
Click to collapse
This doesn't work unfortunately on a locked device.

I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end

help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..

Alamin4736 said:
help me.. my op6 stuck in bootlogo.. how can i run my phone back. it is still locked never rooted..
Click to expand...
Click to collapse
Bro..Use the Msm tool to get recover coz you have the locked bootloader

roel1976 said:
I found the fix and it was very simple: in Recovery under Wipe Data and Cache it has the option to delete 1. System Settings 2. Cache 3. Wipe all (incl Data).
I choose option 1 (System Settings) and after that it booted and I had to set up phone again as with a new install but all data on sd card had remained. I did lose all apps but that is a very minor thing.
Thanks for everyone who thought along with me. We got there in the end
Click to expand...
Click to collapse
I am facing similar problem with my OP5. When I boot in recovery, it asks for pattern to unlock. But does not accept any pattern. In the absence of pin, it gives option to Wipe Data. Will I get similar options like you did ? I am hoping to save my data.

TWRP shows internal storage folders named as random letters.

I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help

does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)

User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password

#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.

the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.

User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though

Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse

Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully

Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD

#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!

#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?

you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.

I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine