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!

[SOLVED] [Q] HTC One Doesn't boot, Can't Get Into Bootloader, only Fastboot

Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?

bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)

superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."

I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?

If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..

SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."

OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.

SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.

bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.

Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..

clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!

SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!

Thanks for posting back. Edit your title to [SOLVED]! and enjoy!

While upgrading from 6.01-7.0 crashed at 83% Now Stuck at Google logo image w/Unlock

Any help appreciated here, I have been searching the forums all morning, but haven't found the same issue as mine (lots of stuck at google ?'s but none from failed upgrade) last night I decided to take the plunge and update my N6 from build 6.0.1 (MOB31H, Oct 2016) to 7.0.0 (NBD90Z, Oct 2016)
I typically use the WugFresh NRT to upgrade via factory image. Last night I decided to give the OTA images a try.
Everything was going smoothly until I bumped my keyboard tray and my phone became disconnected while still flashing. It was almost done too.....it was at the point of flashing the system image and was interrupted at 83% and it failed install.
I then attempted to recover from this by flashing entire factory image for 7.0 but it doesn't seem to want to mount my device. I then tried to go back and flash 6.01 to device using the softbrick/bootloop function from the NRT toolkit. It seemed to partially work as the size of the word google on the screen changed during boot went smaller (so I assume the boot.img was able to flash?) but I am still stuck at the google logo with the unlock at the bottom. Bright side is device is bootloader unlocked.
If I try the recover from bootloop function on the NRT it seems to have trouble sending files to phone (goes through all the process just doesn't take it looks like it sending files but before each at beginning it doesn't seem to connect to device.
I can access bootloader, and recovery. In recovery I tried to wipe/cache (wipes but doesn't help), tried factory reset (wipes but still stuck at Google), tried to mount system through selecting via recovery and it fails.
Not sure which image I should try to flash now to recover 6.01 or 7.0 or if I can even recover from this? Any suggestions are appreciated.
When I first got my phone I did create a backup using the NRT but that was on I think 5.0 or 5.01 and I no longer have twrp installed, should I try putting twrp on it and restoring that back up? It was a long time ago and I am not sure if it will cause radio or boot img issues...since I have upgraded so far past without making another backup with a newer version.
I have read that some others with similar issues that were told to use the N beta to get a clean flash.....only issue is there is no longer a N beta for Nexus 6......it now only shows 7.01 for 6p, 5x, and pixel.
Should I try flashing twrp and a ROM? And after see if I can get to load that way then go back and flash stock image?
Any help or suggestions are appreciated.

On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
just a silly question really , can this work on on a locked bootloader /not rooted device ?

touns_j said:
just a silly question really , can this work on on a locked bootloader /not rooted device ?
Click to expand...
Click to collapse
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.

wavechapter said:
This requires you unlock your bootloader. You will be installing a custom recovery. Root is not needed though.
Click to expand...
Click to collapse
alright , i thought twrp could be replaced with stock recovery

Dirty_Jerz said:
On PC:
Download most recent from Google factory images page.
Download most recent twrp
Unzip file
Unzip image-shamu-______.zip
From phone:
Boot to bootloader (power+vol down)
Plug in phone
From PC:
Fastboot flash bootloader <name of bootloader file>.IMG
Fastboot reboot bootloader
Fastboot flash radio <name of radio>.IMG
Fastboot reboot bootloader
Fastboot flash recovery twrp.img
Fastboot flash system system.img
Fastboot flash boot boot.img
Boot into twrp recovery and wipe cache and dalvik
Reboot
Profit
Click to expand...
Click to collapse
Thank You Dirty_Jerz! I really appreciate the help.
I am now back up and running on 7.0!

Can't Access Recovery or Device, only Fastboot

Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?

same problem here... were you able to fix it?

You might have to use the QFIL method to get your phone going again. Remember you MUST backup the EFS partition and anything associated with your phones imei and SN

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
flash the boot partition then flash stock recovery then try to flash twrp then try to flash a custom or stock rom what you want.

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Anyone solve this problem?

Juninalilla said:
有人解决这个问题吗？
Click to expand...
Click to collapse
这两个可怕的重锁码吓了我一跳，以为手机没电了。幸运的是，我找到了解决方案。你可能需要找个老股rec，跟着视频操作，不用拆机，重点解压。进入adb文件夹，生效

Lirimaer said:
Hello,
I deciden to install Android 10 Beta 3 then install a custom rom. I succesfully installed Android 10 Beta 3, and tried to install Magisk as told in here. After the patched boot.img step, my device stopped booting.
When I press Power+Volume Up or Down, it always goes to fastboot mode. I can't boot into recovery from fastboot, I can't boot TWRP from fastboot. I tried:
fastboot oem reboot-recovery
fastboot boot twrp.img
fastboot flash recovery twrp.img
As shown in the image rebooting into recovery always failing. What can I do?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...

Help| Can't boot

Hi,
I have Carbon ROM with Android 10,
I wanted to flash Bliss ROM, and it says that I need a rooted device,
So I've downloaded Magisk and follow the instruction, created a boot.img and flashed it in fastboot, then I did the same only with twrp recovery & Magisk, flashed it and now it is wiered and I'm not sure what is the problem,
I have fastboot BUT when I try to perform any command, it shutsdown and preety useless, I've tried from PC, if I try from MAC, I can boot into twrp but every operation is causing the tablet to reboot.. So I can't even flash a stock ROM,
In PC, the recognized Android device (When in fastboot mode) I update it's driver to Android bootloader device
Now, fastboot says: "fastboot: error: cannot get boot partition size"
tried:
fastboot flash:raw boot boot.img
fastboot flash:raw recovery twrp.img
How can I solve it?
Thanks !!!

Did you also try
Code:
fastboot flash boot boot.img
?
I can boot into twrp but every operation is causing the tablet to reboot
Click to expand...
Click to collapse
I didn't understand the problem, I think.
You flashed a patched boot.img and your twrp recovery isn't working? Like if you press a button, it just reboots?
I have fastboot BUT when I try to perform any command, it shutsdown and preety useless
Click to expand...
Click to collapse
If you do
Code:
fastboot devices
it also doesn't work?
Or only if you flash a img?