Database Develop

[Q] Problem Installing a Custom Recovery

I'm trying to install TWRP recovery via CMD but I'm having problems. As of now, I've done the following:
Downloaded TWRP 2.5.0.0
Placed the file in the same folder used to unlock the phone that also contains fastboot
With the phone connected, i run the following command
Code:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
In the prompt window, I received the following results "< waiting for device >" but i don't see anything progress thereafter on the phone or prompt window
I tried to reboot into recovery and now receive a red exclamation point within a triangle that's over a phone. See attached photo.
Thereafter, I have to force restart
Does anyone have any advice?

UPDATE
I was finally able to write the recovery on the phone. However, now when I try to boot into recovery, it fails to load recovery and boots as a normal restart.

UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?

I read that it helps to erase the recovery partition prior to flashing over an existing recovery. I tired the command
Code:
fastboot erase recovery
But I receive the following results
Code:
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
If erasing the recovery partition is good practice, how do I go about doing it?

I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.

Ok... I had some issues when installing recovery so this is what I did...
Be advised that next steps are highly risky and that it might have worked for me but I take no responsibility if you break your device
After following almost all the instructions, I read that someone flashed the recovery to the boot partition. So I did that.
fastboot flash boot recovery.img
Now, after this, the device went to a constant bootloop and suddenly the recovery appeared.
Also, I erased the cache from fastboot with next command:
fastboot erase cache
I'm planning to post the procedure I've followed but I don't have much time lately.
Will try to do it as soon as possible.
Best regards.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
brianhill1980 said:
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Click to expand...
Click to collapse
For you mate, go into fastboot run:
fastboot erase cache
Then try again.

:No-Frost: said:
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
Click to expand...
Click to collapse
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.

brianhill1980 said:
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
Click to expand...
Click to collapse
Glad to help mate and glad to know you can go into recovery now

pwr2wh8 said:
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
Click to expand...
Click to collapse
Do you have the Sprint version? I have Sprint and I was running into the same issue. After searching everywhere for this issue, I came across this post: http://forum.xda-developers.com/showpost.php?p=40828046&postcount=240
Here's the link to the file you need: http://techerrata.com/browse/twrp2/m7wls
I flashed this recovery img and it finally worked after all the other ones failed in the same way you described.
Hope it works for you!

Bricked phone, urgent help requested!

So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?

NowhereOutThere said:
So earlier I was flashing TrickDroid, and Aroma froze and crashed the phone while it was installing... CWM showed a screen that said root may have been lost, and offered to fix root. I touched it, and this got the phone stuck in a continual boot loop. I've managed to get into the bootloader, but this is after clearing the cache with the terminal command "fastboot clear cache", and I have to type "fastboot reboot bootloader" when the phone boots up (at the HTC logo) in order to even get into the boot loader... otherwise, the phone will try to enter recovery (to no avail). I really hope I did not brick the phone... any help would be great. Can I fastboot a stock image?
Click to expand...
Click to collapse
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).

unremarked said:
Reboot into fastboot and try to fastboot erase cache then fastboot flash recovery again. If you can get into recovery, just try to reflash your ROM or do a NAND restore. Otherwise, use the All-in-One toolkit to help you adb sideload a ROM(this will bypass Aroma's epic failure rate, too, btw).
Click to expand...
Click to collapse
Great, worked like a charm. I flashed a different version of CWM this time, that might have been the problem? Oh well. Thanks!

[Q] - HTC One softbricked, all options found have failed

Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.

Sidkain said:
Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.
Click to expand...
Click to collapse
U can use a USB OTG cable. Download ARHD(or any rom of ur choice), copy it to a USB. then using the OTG cable, u can flash the rom from TWRP. Once u have a working OS, continue with the RUU process

One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

Sidkain said:
One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what version number of TWRP you're using

your probably just using an outdated twrp version, flash 2.6.3.3 and then retry sideloading

I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...

glaringradio said:
I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...
Click to expand...
Click to collapse
have you tried to fastboot erase cache after flashing recovery

xnknown said:
have you tried to fastboot erase cache after flashing recovery
Click to expand...
Click to collapse
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now

glaringradio said:
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now
Click to expand...
Click to collapse
then you may want to try flashing an older version of twrp

xnknown said:
then you may want to try flashing an older version of twrp
Click to expand...
Click to collapse
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"

glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
try all three
fastboot erase cache
fastboot erase system
fastboot erase data

glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
1- are you sure you're using the correct recovery for your phone (e.g. M7_U/UL vs Sprint!!)
2- have you checked MD5 of the download, to make sure it's not corrupt; TWRP site doesn't play nice with download managers, so please check MD5

xnknown said:
try all three
fastboot erase cache
fastboot erase system
fastboot erase data
Click to expand...
Click to collapse
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop

glaringradio said:
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop
Click to expand...
Click to collapse
nkk is right is ur phone a sprint or verizon?

xnknown said:
nkk is right is ur phone a sprint or verizon?
Click to expand...
Click to collapse
It's an international (I'm with the operator 3 in the UK)

glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
have you checked MD5?

glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache

xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
i hate to be insistent, but has he checked MD5?

nkk71 said:
have you checked MD5?
Click to expand...
Click to collapse
I have, I literally have no idea as to why they aren't working...
xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
When I try to flash a different hboot, I get the error "FAILED (remote: 99 unknown fail)".
Again, MD5s on the TWRP files I downloaded are fine. All I can do is use fastboot to varying degrees of success, and nothing works when I try to use RUU... It's a soft brick, but it's completely and utterly broken and I can't see any way to recover it (and I can't send it for repair since it is now marked as tampered)

glaringradio said:
I have, I literally have no idea as to why they aren't working...
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
Click to expand...
Click to collapse
and 1 more try: have you checked MD5?

Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"

Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance

You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.

1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot

You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.

Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.

Solved with Corrections: Unable to flash TWRP, Failed (Remote: command not allowed)

Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s

Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?

So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.

OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.

Oops duplicated post.

OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff

I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.

I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.