I am in the process of installing LineageOS 18.1 onto a Pixel 3 XL (I have done a Pixel 3 before with no issues). I am following the instructions from lineageos.org (https://wiki.lineageos.org/devices/crosshatch/install). It is specific instruction for the Pixel 3 XL. I have successfully completed the first number of steps but got stuck on the last one noted below:
Unlocking Bootloader (ALL COMPLETE)
enable OEM unlock
connect device to PC
adb reboot bootloader
fastboot devices
fastboot flashing unlock
reboot
re-enable usb debugging
Temporarily Booting a Custom Recovery
download a custom recover (lineage-18.1-20210803-recovery-crosshatch.img) - COMPLETE
connect device to PC - COMPLETE
adb reboot bootloader - COMPLETE
fastboot devices - COMPLETE
fastboot flash boot lineage-18.1-20210803-recover-crosshatch.img - COMPLETE (received msg that sending and writing to boot_a is okay)
reboot into recovery - INCOMPLETE
will not reboot into recovery, stays in fastboot mode
last line on fastboot mode screen says "no valid slot to boot" at one point it also said "error booting boot.img"
Any idea/suggestions on what would be the problem? I did try redoing the fastboot flash boot command an additional time and again it said it sent and wrote ok, however, still unable to reboot into recovery. I did not check the version of android on the phone before i flashed the lineage 18.1 recovery - could that be the problem? Might it be that the phone cannot run LIneage 18.1 because it is on android 10? (which I'm not sure how to check at this point). If this is the problem what would be the best solution - reflash with a lineage 17.1? Or, is there a way at this point to check and upgrade the android on the phone? Perhaps there is another problem entirely.
Related
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076
Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers
Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance
Hi
given this is my first thread here, please redirect me, if my search-fu did not lead me to the correct post.
I'm trying to install a custom ROM on my 5T but after successful flashing it is simply displaying the boot animation of Lineage and nothing else happens and no connection with ADB is possible at that time. Steps I did (following this guide):
updated to stock OxygenOS (A5010_43_180223), reboot, ...
enable dev options
enable USB debugging, advanced reboot, OEM unlock
reboot into bootloader
fastboot oem unlock
enable dev options, USB debugging, advanced reboot, OEM unlock again
reboot into bootloader
fastboot flash recovery twrp-3.2.1-x_blu_spark_v8.73-op5_op5t.img (also tried twrp-3.2.1-0-universal-codeworkx-dumpling.img and twrp-3.2.1-2-dumpling.img)
boot into recovery
swipe to allow system changes (no change detected when not doing this)
adb push lineage-15.1-20180402-microG-dumpling.zip /sdcard/ (also tried older images or standard lineage build)
install this via TWRP
when done, wipe cache/dalvik
reboot system
boot animation for a very, very long time (longest waiting time > 45 minutes)
Initially, I had magisk v16 also thrown into the mix, but to reduce complexity I don't at the moment.
Interestingly, once I'm at this stage and the boot fails (also not on second or third try after force-reboot), I cannot get stock (OnePlus5TOxygen_43_OTA_030_all_1802230142_ebdb8bfbc359405a.zip ) to boot anymore, it also is stuck in boot animation. The only way to get back to working stock ROM found so far is flashing original recovery and firmware (sideloading) and locking of boot loader again.
Does this sound familiar to anyone, as I'm running out of ideas what I did wrong and where.
Thanks a lot in advance for any pointers!
Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.
Hello everyone! So I have a OP7T 1907 TMobile variant, and I've been following this guide to convert it. I have done it successfully a long time ago. I went to update to android 11 and after a while my flashing stopped working, I finally figured out the problem. I was getting the error. "fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
I was stuck here for a while so I deleted the adb folder and went to bed last night. I woke up and it suddenly was working again. I tried to update to Android 11 and it bootlooped my phone, I tried to reflash but I had already relocked the bootloader, and the command "fastboot flashing unlock_critical" would return the error I had to flip the enable oem unlock switch. So I plugged into the MSM tool and hit start. I am now stuck at the same fastboot error. Any ideas?
After trying a bunch of different stuff, flashing the international rom and it stopped. I guess that put back some files that I was missing. I was then stuck with the tmo splash screen that goes nowhere, I then restarted and I finally go to the fastbootd screen. I wiped all data. After that fastboot reboot fastboot worked, idk if I just once again got lucky or not. But It worked
having same problem, can anyone explain how to enable fastbootd for oneplus 7t indian variant?
You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)
HueyT said:
You need stock recovery (not twrp, los recovery, etc) for fastboot reboot fastboot to enter fastbootD mode (looks like stock recovery mode with 2 lines of Chinese and 1 line of English)
Click to expand...
Click to collapse
Not entirely true, though.
Both LOS recovery (like the one from StatixOS or Pixel Expierience) and TWRP (the unofficial 3.5.1_10) have working fastbootd.
I don't think the same can be said about the Chinese TWRP, or mauronofrio's version, however.
Good 2 know. Thanks
open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error
ecompton59 said:
open platform tools zip (fastboot&adb) place everything you want to flash in same folder as open zip (it can be whole payload extracted) and that will fix fastboot error
Click to expand...
Click to collapse
I don't think this is true.
Hi Team,
I have an spare Nokia 6.1 (2018) smartphone (Model # - TA -1089)) at my home which I wasn't using since 2-3 years.
Today, I got hands on it, and tried to use it for my development needs.
To begin with, I unlocked its boot-loader using this guide to unlock Nokia 6.1 (2018)
and within "Developer Options", I can see that the "OEM Unlocking" option reads - "Bootloader is already unlocked."
Now, as a next step, I am trying to install TWRP recovery, but nothing seems to be working. No matter which image I try, I get stuck on the TWRP splash screen.
I have tried TWRP Images from the following websites and many more:
TWRP.me
Get Droid Tips - Here when I click on the "Download" option, I get redirected to the "TWRP.me" website only, whose images are not working.
In addition, I have ensured that "ADB and Fastboot" + "Nokia USB Drivers" & other contingencies are properly installed on my system & are not the underlying issue.
I tried running the code
Code:
fastboot flash recovery twrp.img
and my phone got stuck on the TWRP splash screen. Ultimately, I had to use OSA tool and flash the STOCK ROM to get my device working again.
Many websites suggested to simply boot the TWRP and so I used this command:
Code:
fastboot boot twrp.img
in the "Download" mode and then again, nothing happened and I got stuck on the TWRP splash screen.
Note: The only difference between above two commands being - my stock recovery worked fine after executing the 2nd command, and I could boot into my device without much trouble.
Here's my Device Overview:
Device Name - Nokia 6.1
Model & hardware = TA-1089
OS version - Android 10
Security Patch Level - May 1, 2020
Build Number - 00WW_4_15c
Can someone now please suggest where I could be going wrong?
What's my goal:
Root Nokia 6.1 & to be able to install Custom ROM's on Nokia 6.1 and use that device for development purposes
and in case anything goes wrong,
Flash the STOCK ROM again using OSA Tool and bring the device back to its current state.
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
And also not fla#h
It is a/b partition so only boot done your goals and boom
Everytime you need to temporarily boot twrp
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
Hi @White_devil_04200
Thank you for redirecting me to this Telegram channel.
However, let me share that - On the channel, I found "twrp-3.3.1-1-PL2.img" listed as the TWRP image that works.
The conflict is that - I downloaded this version only from multiple sites & after flashing it, got stuck on TWRP splash screen. I had to use OSA tool to reflash Android OS & restore the stock recovery.
And, when I ran the code -
Code:
fastboot boot twrp.img
, then also I got stuck on the splash screen, but was able to reboot into the OS successfully.
Note: Also, I tried switching the slots too (from 'a' to 'b' or vice versa') but then also, nothing worked for me.
I hope you get my problem, and would now assist me accordingly.
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
For potential readers of this thread, I would like to explain one thing here.
"fastboot flash recovery twrp.img" does NOT change your stock recovery on Nokia 6.1. Because this phone has "A/B system updates" and due to that the recovery RAM disk is now contained in the boot.img file. So Nokia 6.1 has not recovery partition so if you execute the "fastboot flash recovery twrp.img" command it only shows an error message and nothing is changed on your device.
Common issue on Nokia 6.1 is that when you execute only this one command "fastboot boot twrp.img" then it stucks on androidone logo.
But for some special reason, if you execute "fastboot flash recovery twrp.img" and then "fastboot boot twrp.img" it successfully boots into TWRP recovery.
Really there is nothing to worry about. This procedure is safe and really works.
White_devil_04200 said:
Telegram: Contact @nokia_pl2_2018
t.me
Join this
In this a twrp mod version is updated
And also a full guide
Give q chack
Am here
Click to expand...
Click to collapse
And also wipe data with help of fastboot ! Yes it is important if you facing stuck on twrp logo
mAnN14 said:
Thanks @Bảo Dora for sharing your TWRP file and for the instructions.
I was finally able to boot into TWRP (used another file, of course), and then successfully get "root" access on my device.
Also, I read that if you execute the command:
you shall permanently install TWRP on your device, which may or may not be the first preference of many users.
Having said that, am glad that it worked out for you. However, I still prefer to use just the "boot" command to avoid changing my stock recovery.
Thanks for your help again.
Cheers,
Manu
Click to expand...
Click to collapse
Hi,
which file did you use at the end? i have the same problem..
AndreaMariaBono said:
Hi,
which file did you use at the end? i have the same problem..
Click to expand...
Click to collapse
Let me try and find that file link again bro. It's been time I performed the root process, so I will have to search for it.
Will share it with you at the earliest.
Till then, stay calm and be safe.
Bảo Dora said:
this is how i use twrp on nokia 6 2018 (since i unlocked it):
1. connect my phone with download mode to my pc:
2. run 2 code lines:
fastboot flash recovery twrp.img
fastboot boot twrp.img
3. and done.
The only disadvantage of this way is that every time I go to twrp, I have to run those 2 code lines with my pc. Still, it worked (at least for me).
You can try my twrp version.
Click to expand...
Click to collapse
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
sayanmitra753 said:
I accidentally found a way to permanently install twrp on nokia 6.1..you don't have to temp boot it every time
Click to expand...
Click to collapse
I don't think it works...
MricCall said:
I don't think it works...
Click to expand...
Click to collapse
Bro it works in real..i am using it on my device
use comand
adb erase userdata
then
adb erase system
adb arase vendor
then fastboot reboot
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
N0t3xx_A said:
Hello,
i have nearly the same problem atm.
I successfully unlocked the device.
When i do to 'fastboot boot twrp.img' in 8 of 10 cases it stucks on Android One screen but sometimes it stucks at twrp boot screen.
I have tried multible twrp versions for Nokia 6.1 PL2.
I also tried 'fastboot flash recovery twrp.img' but here comes a adb error that says:
Sending 'recovery' (38592 KB) OKAY [ 1.064s]
Writing 'recovery' FAILED (remote: '(recovery_a) No such partition')
fastboot: error: Command failed
On Galaxy S6 this works fine for installing permanently but here i event cant boot into twrb.
Any advices pls?
Click to expand...
Click to collapse
"fastboot flash boot recovery.img" and reboot into recover using Vol+ & Power.