I'm trying to boot a Oneplus 6T into linage recovery-mode, so I can install latest version of Linage.
I can boot into fastboot, but I am unable the boot the recovery image (or any recovery, also tired with TWRP). When I run "fastboot boot [recovery-image-nam-and-version].zip", I get no errors, all looks good, but the phone then just immediately reboots/switches into a screen showing the OnePlus logo + "Fastboot Mode", and then just hangs there forever.
If I boot normally I am greeted with the "The boot loader is unlocked" warning-screen. It also just hangs there, nothing happens. Nothing is booted.
I am running latest version of Fastboot. OEM is unlocked. When I boot into fastboot, I get this content:
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [redacted]
SECURE BOOT - yes
Solved. Turned out I was a fool and had somehow missed the big red blinking WARNING only to try to install Lineage on Android 11. (I will never do that again, I promise)
SOLUTION that worked:
Getting out of the fastboot-loop: Seems like everything needed to go back to the outdated Android 9 to work, as this was what was originally installed. So: re-install Android 9, upgrade to 10, upgrade to 11, install Lineage. In more detail:
re-partitioned the device, using this guide (selecting an older version, going back to Android 9. I chose the olderst of the 9s, maybe a newer would have done the trick too): https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/
on Linux I had to poke around in the zip-file a bit, but the quick fix was to copy all the commands in the "Fastboot Partitions" section into a textfile and create a script out of it ("#!/bin/bash" in the top, and search/replace "fastboot" to "~/Downloads/location-to-downloaded-gsuite-tools/fastboot"
first boot launched a very simple recovery system. Chose clear all cache and wipe all. After a couple of failed reboot-cycles, it succesfully booted Android 9
(Unsuccesfully tried to upgrade to Android 10 using system dialogues)
Managed to boot into TWRP recovery after fastbooting it:
From TWRP:
Sideloaded TWRW-install into boot to make it persistent recovery. (Pay careful attention to version-numbers, all you install have to fit Android 9)
Sideloaded "copy-partitions.. .zip" as recommenden by Lineage
Sideloaded Android 10 .zip
Booted into Android 10
ran system update successfully to Android 11 (takes some time, appr. 20)
Booted Lineage recovery via Fastboot, this time it ran
Followed the Lineage install-guide through to sideload Lineage 18
Thanx to the people in Lineage IRC to point a lot of this out.
Related
Hey all.
I've looked far and wide and cannot find a solution for my phone. I was following this tutorial (Sorry can't post links)(Unlock Bootloader, Install TWRP and Root ZTE Axon 7 (A2017G) Droidviews) and got all the way to unlocking my bootloader. Did all the steps correctly but when I clicked start on my unlocked bootloader it went to the ZTE logo and never actually started. I then held the power button down until the device restarted and went into twrp and tried installing lineage and gapps because somewhere I read that someone fixed this problem by installing an update.zip file for nougat 7.0. I used this tutorial (Again cannot post links)(How to Install Lineage OS 14.1 on ZTE Axon 7 Droidviews) to install lineage. Needless to say that did not work and my device was stick stuck in the ZTE logo so I went back into twrp and tried installing the update.zip file for B11. Now my device goes past the ZTE logo but then goes to the bootloader. When I click the power button to boot a Linux symbol appears on my screen and will not leave until I hold the power button for 20 seconds or so, then it goes into what I assume is the default axon 7 recovery. It has a few options such as; reboot device, reboot into bootloader, update via microSD card, update via ADB. When I try to reboot noramlly or to bootloader the previous Linux screen happens. I can't use any commands on ADB aside from sideload and am kinda stuck. Any help would be very much thanked...
P.S. all this has happened on my A2017G that was running Nougat 7.0 B11.
FOUND A SOLUTION!!!
Because I wasn't able to use adb or fastboot in the bootloader or the recovery mode that inbuilt into the phone, I had to instead go into factory test mode by powering on the device whilst holding the power down button, it took a few tries and I kept accidently going into the bootloader instead but eventually I got it. Then you can connect your phone to adb and run the command "adb reboot edl" after that use "axon7tools -w recovery". This didn't work at first for me because I was using an older version of TWRP. After a heap of frustration I finally tried downloading the newest version and voila! It worked. From there I was able to go into TWRP recovery and unlock my bootloader and then finally reboot my phone. Lots of stress but glad I found a solution.
I don't think anyone has posted that adb works in the test menu. good to know.
I've been trying to boot my Honor 5A to TWRP so that I can install LineageOS. A variety of threads say that this or that version of TWRP should work, but none seem to. The phone keeps popping back into EMUI.
-- I've unlocked the bootloader.
-- ADB and Fastboot seem to be working find -- I can flash TWRP to recovery and get the "OK Finished"
-- I've tried different versions including, among others, TWRP for Honor 6 Mogolia, Honor 4x Cherry, and P8 Lite. They reboot to the screen that says "Your device is booting now" then after 15 secs or so it boots back to EMUI.
-- Last attempt was the TWRP3.0.2.img for P8 Lite. I copied the img file to recovery.img and then to the phone.
-- When I issued the command to boot to recovery I got:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.856s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.856s
Oh, the "Official TWRP App" doesn't work either. It will say the image is downloaded, but won't "Reboot to Recovery"
Any suggestions?
[GUIDE] Success! Wiped Emui and loaded LineageOS on Honor 5A
Well, I finally made it through the process with the help of bits and pieces of other threads. To summarize, the problem was that there is no "Enable OEM unlock" in the settings on this phone. I had to enable USB Debugging and turn off all other developer options, then remove my google account and finally reboot into recovery, whereupon I saw the TWRP page.
For those who want it, the whole process was this:
-- Used DC-Unlocker to get my unlock bootloader code. The Huawei site just gave me the "haven't logged in for 14 days" error again and again for a month, and their help lines just tell you not to unlock your phone.
-- From Linux, used adb and fastboot to unlock the bootloader.
-- Kept flashing TWRP for various devices onto the phone, but whatever I did, Emui kept reloading.
-- Removed Google account from phone and screen lock.
-- Used fastboot to load TWRP 3.0.2 Recovery for P8 Lite Marshmallow (renamed as recovery.img) onto the phone. See https://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162
-- Booted into recovery by pushing volume up and power at same time.
-- Jumped for joy when TWRP came up.
-- Used TWRP to install LineageOS 14.1 for P8Lite (lineage-14.1-20170418-unofficial-hi6210sft.zip found at https://www.gizrom.com/lineage-os-14-1-p8-lite-honor-4c-honor-4x-model[/URL]) which I had downloaded to SDCard on the phone.
-- Booted to the dreaded "Password required screen" so I had to go back and wipe the data directory using TWRP (see https://community.zteusa.com/thread/14780)
-- Installed LineageOS for hi6210sft via TWRP
-- Immediately (before any reboot) installed OpenGapps full version for arm64 from SDCard: open_gapps-arm64-7.1-full-20170614.zip from http://opengapps.org/
-- Restarted the phone and .... OMG this time it all worked.
Good luck.
Mark this thread as solved pls, and do share your guide in the guides section
raboucher said:
Well, I finally made it through the process with the help of bits and pieces of other threads. To summarize, the problem was that there is no "Enable OEM unlock" in the settings on this phone. I had to enable USB Debugging and turn off all other developer options, then remove my google account and finally reboot into recovery, whereupon I saw the TWRP page.
For those who want it, the whole process was this:
-- Used DC-Unlocker to get my unlock bootloader code. The Huawei site just gave me the "haven't logged in for 14 days" error again and again for a month, and their help lines just tell you not to unlock your phone.
-- From Linux, used adb and fastboot to unlock the bootloader.
-- Kept flashing TWRP for various devices onto the phone, but whatever I did, Emui kept reloading.
-- Removed Google account from phone and screen lock.
-- Used fastboot to load TWRP 3.0.2 Recovery for P8 Lite Marshmallow (renamed as recovery.img) onto the phone. See https://forum.xda-developers.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162
-- Booted into recovery by pushing volume up and power at same time.
-- Jumped for joy when TWRP came up.
-- Used TWRP to install LineageOS 14.1 for P8Lite (lineage-14.1-20170418-unofficial-hi6210sft.zip found at https://www.gizrom.com/lineage-os-14-1-p8-lite-honor-4c-honor-4x-model[/URL]) which I had downloaded to SDCard on the phone.
-- Booted to the dreaded "Password required screen" so I had to go back and wipe the data directory using TWRP (see https://community.zteusa.com/thread/14780)
-- Installed LineageOS for hi6210sft via TWRP
-- Immediately (before any reboot) installed OpenGapps full version for arm64 from SDCard: open_gapps-arm64-7.1-full-20170614.zip from http://opengapps.org/
-- Restarted the phone and .... OMG this time it all worked.
Good luck.
Click to expand...
Click to collapse
Will it work for CAM-UL00
GokulDas01 said:
Will it work for CAM-UL00
Click to expand...
Click to collapse
It should work.
Sent from my Honor 8 Pro using XDA Labs
GokulDas01 said:
Will it work for CAM-UL00
Click to expand...
Click to collapse
Is it honor 8 lite? Can flash the same recovery or use the one available in 6X section
I have been following the instructions here: https://wiki.lineageos.org/devices/YTX703L/install as I want to install Lineage OS.
I have successfully got as far as this command: fastboot flash recovery twrp-3.2.3-0-yt_x703l.img which seems to complete successfully, albeit fairly quickly.
When I reboot and go into recovery mode though all I get is the standard Lenovo recovery:
Android Recovery
Lenovo/YT-X703X/YT-X703X
7.1.1/S100/YT-X703X_S000973_180524_ROW
etc
Any suggestions?
Thanks
<sigh...> If I'd waited 2 more minutes.
The secret was to use the keys to boot into recovery rather than allowing a normal reboot.
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.
I tried "fastboot boot" almost all of KizuYuna's .imgs, tried fastboot boot the lineagerecovery.img. All I get is the fastboot logo and the phone just restarts into OOS... TWRP is same.
About to MSM downgrade to OOS 10 to get recovery working like I did before. Thought it would be better to flash a rom from OOS 11 to get better firmware compatibility but just wont work.
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
bpambrose said:
Simply go back to OS 10.3.5 using the MSM Download Tool. Upgrade via OTA to 11..1.1.1, fastboot flash boot magisk_patched-23000_11.1.1.1 from XDA 235Sanders15 post. (you are now rooted with Magisk. Via Magisk install TWRP-Installer-3.5.2_9-0 you are now unrooted but have TWRP installed. Using TWRP flash Magisk v23.0.You are now rooted on OS 11.1.1.1 with TWRP installed. Do not change the Kernel it will cause a Bootloop.
Click to expand...
Click to collapse
So you are saying MSM to 10 and then flash official 11.1.1.1 or fastboot flash boot magisk_patched-23000_11.1.1.1 (this is a full 11.1.11.1 OS flash? No need to use twrp from 10?)
Thanks
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Fenopy said:
So I just went thru an Android 10 to 11.1.1.1 upgrade, and it was a bit frustrating. So I'll throw out what I learned along the way.
Note, I have a T-Mobile Variant, so sometimes you need different files/steps for T-Mo.
I flashed the full OTA via Settings > Update > Local Upgrade, which ended up boot-looping.
Via Fastboot, I did fastboot flash boot magisk_patched-23000_11.1.1.1.img; followed by fastboot reboot;
This was still boot-looping, so I shutdown the phone, and booted into recovery, which was now PBRP.
via PBRP, I flashed the full OTA again from my SDCard; then installed PBRP zip;
Reboot to System and got a Successful Boot. Yey.
Reboot to Recovery; Backup Boot.
Reboot to System
Install Magisk App; within Magisk > Install > select my Boot Backup to Patch (per Magisk instructions); I used a file manager to copy to my PC from my phone
Reboot to Fastboot; fastboot flash boot magisk_patched-23000_rJoA.img (the file Magisk created)
Reboot to System; Success!
I guess my morale of the story is, get a clean boot working, go from there. Patch your own boot, don't rely on someone else's.
Click to expand...
Click to collapse
So you had to go through all the trouble because you had a bootloop issue when OTA updating to 11? I already got to 11 but am trying to fastboot boot a recovery because I want to flash a custom ROM... When I fastboot boot TWRP.img or LOS Recovery .img it just shows fastboot logo and restarts the phone with no recovery shown..