Database Info

[Q] No recovery available on Nexus one?

Help, please.
My rooted Nexus one will enter bootloader, but not recovery. When I choose recovery, it hangs at the Nexus One "X" screen.
Using the passimg method from bootloader loads the PASSIMG.zip but after loading does not ask if I want to flash the image, it just returns to bootloader. If I reboot, it just hangs at the Nexus "X" screen
If I use ADB, and flash a recovery, it says ... sending... OK, then... writing... OK, but if I reboot, its just hangs at the Nexus "X". If after flashing a recovery I try to go from bootloader to recovery, it just hangs at the Nexus X.
I've tried flashing both recovery-clockwork-5.0.2.0-passion.img and recovery-RA-passion-v2.2.1-CM.img with no success. The file used for the passimg method was signed-passion-img-FRG83_0923.zip renamed as PASSIMG.zip.
Before the current problem, I was running CM nightlies and used Rom Manager. I have a few backups, but can't get to recovery to restore.
Any suggestions?

Is your bootloader unlocked? I don't think you can use ADB to flash a recovery img without doing so. If it is unlocked you need to enter fastboot and then use ADB to flash what you need. In that case you could flash an entire ROM by it's constituent .img components.
There's a wealth of info on the N1 forum. Start with the wiki:
http://forum.xda-developers.com/showthread.php?t=746544

Thanks, yes the bootloader is unlocked.
Using fastboot, I flash the recovery (see above) .. fastboot flash recovery [relevant recovery filename] , but afterwards, when I choose recovery from the menu, the phone just hangs at the Nexus "X" screen. I also tried flashing boot and system (from the unzipped signed-passion-img-FRG83_0923.zip file), but still no success - I can not get to recovery.

Oneplus one not installing TWRP after COS13.1 update

I reset my Oneplus one and installed the COS13.1 update.... But now after installing I'm not able to flash twrp through fastboot... Even tho it shows successful on the PC, it wing boot into TWRP

Go to the developer options (tapping on the build number first ofcourse) and then go to the option: "update Cyanogen-recovery". set it to off.
I think that should do it. Haven't installed the update yet, but there is an option like that in the normal CM-13.
edit:
If that doesn't work you can try to flash it through flashify (requires root). If that still doesn't work you can also boot TWRP through fastboot and then install the IMG through TWRP itself (like updating your recovery)
You can boot TWRP via fastboot with using the boot command instead of the flash command:
fastboot boot "image.img"

Still showing that it's failed

Could you boot TWRP without flashing via fastboot? Because if you can do that it means that the system is automatically reflashing the stock recovery at startup.

How did you installed (tried to install) the recovery?
fastboot?

Follow this. TWRP 3.0.2 can be installed this way. 2.8.6 sometimes doesn't.
1. Turn off option to Update Cyanogen Recovery from Developer Options.
2. Flash Recovery via fastboot, the put command to clear cache from fastboot only. DONT REBOOT NOW.
3. Disconnect phone and turn it off.
4. Try booting to recovery. If it fails, dont worry let the phone boot normally then try again. It should work.

Getting a mistake when I try to flash the recovery via fastboot on my Nexus 4

Hey. I just flashed a stock rom and re-locked the bootloader, in order to unlock it, get twrp, get a custom rom (likely lineage) and root with magisk (it seems better than superSU, no?) without any toolkit, because i want to get some knowledge about android.
I downloaded adb and fastboot, enabled USB debugging, booted my nexus 4 on bootloader mode, and I used 3 commands after opening the command prompt from the folder containing fastboot. I also downloaded the latest img of TWRP for nexus 4 and renamed it "twrp" and put it on the folder.
The 3 commands I used are : "fastboot OEM unlock", "fastboot erase recovery", "fastboot flash recovery twrp.img"
But when the phone tries to boot the recovery, I get this : puu.sh/wWTjC/6cf11a9a32.jpg
and it doesnt work ofc.
Furthermore, I can't boot the ROM, I can only boot the recovery and the bootloader. When I try to boot the Rom, i get the recovery.
can someone help me please?
thanks

Hello,
The problem is that the recovery is unable to mount the /data partition, what you need to do is repair it by the following steps
1.Go to TWRP main screen
2.Press wipe
3.press advanced wipe
4.tick data
5.press repair and change file system
6.press repair
7.wipe the arrow
NOTE: this will format the data partition
now reboot to recovery again and check if the problem is fixed

Hello, the problem is I cant reach the main menu of TWRP, after getting what I screened, my phone reboots on TWRP again, and again...
I also tried the command "fastboot boot twrp.img" and i get the same result.

where did you get the twrp from ?
i would in such case as twrp is having troubles first try to find a working version of it, and it it didn't work i would reflash to stock stock and start from scratch

I got twrp there : dl.twrp.me/mako/
i took the latest version.

Get the cwm recovery for your device, wipe data , then try reflashing the twrp recovery

It's ok, thanks

nublord said:
It's ok, thanks
Click to expand...
Click to collapse
did that help ? hopefully?

hmm, I thought it did, but i actually get the same problem, and I can't launch neither cwm nor twrp..

Once yo reinstall twrp
Go to wipe the format data to remove encryption
You can also use cwm to flash the ROM

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Need help needed with fastboot(loop)

I've decided to upgrade to OOS11 stable and patch the boot before going into the rom. What I did was:
1. Flash latest TWRP (3.5.2_9-0)
2. Reboot to recovery
3. Flash ONLY OOS11 boot.img
4. Flash TWRP again
5. Install Magisk and Kirisakura-R 1.1.1 kernal (for f2fs support)
6. Reboot to recovery
Here I was going to do the same on other partition but TWRP failed to boot and screen kept flashing but I noticed that ADB was connected so I rebooted to fastboot and flash stock boot I've previously extracted from stock ROM. Now I face another problem, phone doesn't boot anywhere else but fastboot.
I've tried a few stuff to get it back.
# There were some cases where the phone won't boot with bootloader unlocked and stock boot so I managed to patch boot.img with Magisk using an emulator and then flash it.
# Tried booting into TWRP but phone phone would get stuck in "Fastboot mode" screen with fastboot still connected (And taking commands from PC).
# Tried flashing TWRP to boot partition which worked previously but this time the problem stayed and kept booting into fastboot.
A few more points that I should mention,
# I've backed up my entire phone using TWRP so I can unbrick it if I somehow manage to get into TWRP
# I don't have the backup on my computer. It's on the phone.
I absolutely can't lose those data. Yeah, mistake on my side for not backing up on my computer but to my defense, this never happened before so I let my guard down this time.
What options do I have left? Any hint would be appreciated. Thanks for reading