Ok.... So i unlocked my bootloader on a verizon pixel and installed magisk with a patch boot image. no problem
I just tried to install TWRP (3.2.2). I booted the image first, the flashed the TWRP zip in the booted image. Then TWRP would boot, but only TWRP would boot. it would never progress to booting up the rom.
So i found a thread that suggested flashing the magisk patched boot image.... that just made it worse. It would only boot to recovery... and NO FASTBOOT. I was able to get to the menu and use adb to side load the latest OTA. Now i can boot into the ROM and use the phone as usual
However, I still don't have fastboot in recovery mode. I don't think its drivers. I must have mucked up recovery. It gotta be related to the TWRP snafu. I can boot into the stock boot loader and my PC beeps and recognizes the phone, when i use the arrows to go to recovery, my pc loses the device. My PC just can't see the pixel in recovery mode.
Not sure how to proceed
Can I side load the factory image after removing the wipe tag (-w)? Do i need to factory reset?
Am an idiot.... fastboot works in bootloader.... please delete
Related
Hi,
I hope this question wasn't asked before, I couldn't find a solution to my problem yet.
I tried using the toolbox to flash Philz and later TWRP recovery. the phone booted normaly and not to the custom recovery.
When I tried to boot to custom recovery the stock recovery loaded instead.
I even tried the command prompt method.
Eventually I used the command m=prompt method and immediately manually booted to recovery and the custom recovery (Philz this time) loaded. I though I was done, but right after I set up the phone as I like it and wanted to make a backup of it, the stock recovery loaded instead of the custom recovery.
any ideas?
what as I doing wrong?
Thanks
Unlock bootloader amd ise the fastboot commands to flash tje recovery permanently. Guides in the general section.
I see I need to elaborate
I will tell you what I did step by step.
1. Using the toolbox (V6), I unlocked the bootloader, the phone booted as if it was just got out of the store (all my data was erased)
2. Entered the gmail account and basically went through the entire initial setup process.
3. Booted to fastboot again and flashed TWRP recovery (using the toolbox).
4. The phone automatically booted normally (not to custom recovery)
5. I tried booting to custom recovery and I got the stock recovery instead
6. Booted to fastboot again and flashed Philz recovery this time (using the toolbox).
7. The phone automatically booted normally (not to custom recovery)
8. I tried booting to custom recovery and I got the stock recovery instead
9. I opened command prompt and used the "fastboot flash recovery recovery.img" command, the recovery.img I got from the "philz_touch_6.59.2-bacon" zip file.
10. I immediately forced boot to recovery and got Philz
11. I set up my phone as I like it (app + settings)
12 tried booting to recovery again (from power off of course) and got the stock recovery again !!!!
Any ideas?
I tried again and partially succeeded
Hi,
I decided to do all using the command prompt.
This time I disabled the CM Recovery Protection (though I clearly remember doing so before but might have done it before unlocking the bootloader).
I tried flashing using "fastboot flash recovery" command TWRP recovery but when I tried booting to the recovery I got one vibration (the one supposed to be before the recovery loads) and after a few seconds (+1 logo on screen) I got another vibration and the system normally booted (not to recovery).
I did it again with Philz and it worked, I booted twice to recovery and it holds.
The only difference was that Philz recovery was named recovery.img and TWRP was named TWRP.img, I don;t think that matters.
I really wanted TWRP. don't know why it didn't work.
This question has been asked several times, see the FAQ thread:
http://forum.xda-developers.com/showthread.php?t=2839471
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?
I wanted to root my OP6 and entered fastboot mode.
I successfully flashed the bluespark img from Terminal and installed the Bluespark ZIP file from this link
After rebooting, it got stuck on the bluespark logo and when I tried to reboot the system, the phone got stuck on the Bootloader unlocked screen.
I tried to repeat the process and this time flashed the TWRP lastest version. Now its stuck on the TWRP logo screen.
Then I browsed around and found these stock boot recovery img files,
After flashing the latest one, the phone got started properly but everytime I restart the phone, its getting stuck on the Bootloader warning screen and the recovery options are still stuck at TWRP image.
If nothing works, have a look here
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .
i don't know how else to describe this, i was flashing a custom ROM, then flashed magisk and now my phone is stuck in bootloop unable to go to recovery or system, the phone boots then black screen, etc etc, the same goes for recovery except it is faster (i reflashed recovery and it still happens) unable to do basically anything other than stay in fastboot mode.
what should i do?
edit 1: i can reboot to recovery and only be able to access shell.
Enter fastboot and flash recovery again. Brigudav's TWRP is the most used one. Gringo80's TWRP is new but seems to be working as others have written. (Both are unofficial and a take or leave, we don't have their source code, unfortunately.)
Right after flashing reboot to RECOVERY (not system). Can do with fastboot command or by holding button as usual. Alternative: reboot to recovery image file itself.
Once in recovery, format data (the option that has to type "yes" ). Reboot to RECOVERY again. Wipe cache, dalvik.
Reboot to system. Probably will work if your custom ROM was flashed properly.
Otherwise you can do everything again and also reflash ROM.
EDIT: I missed the Magisk part. So, while in recovery, dirty flash same custom ROM again. Or alternative: rename the Magisk file to uninstall.zip and flash it....this will restore your original boot and completely clean Magisk.
After you properly booting to system, then you can again try install Magisk.
why does flashing TWRP and booting to it directly work? i don't know! but it worked!
it seems that the custom ROM i installed is probably corrupt and flashed anyway ( i reflashed dirty/clean to make sure ) thanks for your help.