Develop Bugs

Failed to flash

Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak

Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/

jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.

jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:

I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device

I can't install any custom ROM

I have bootloader unlocked and TWRP 3.2 installed.
Normally most ROM's are not finished installing always stuck in patching system image unconditionally.
LineageOS 14.1 it was installed but the screen was black with the blue LED on.
I have the stock S251 firmware version of P2a42 with Lenovo P2c72 model.
I tried to format data to EXT4 but doesn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kalmas77 said:
I have bootloader unlock and TWRP 3.2 installed.
Normally most ROM's are not finished installing always stuck in patching system image unconditionally.
LineageOS 14.1 it was installed but the screen was black with the blue LED on.
I have the stock S251 firmware version of P2a42 with Lenovo P2c72 model.
I tried to format data to EXT4 but does't work.
Click to expand...
Click to collapse
Are you 100% sure the bootloader is unlocked ? Did you unlock the bootloader via fastboot or you just waited until the 14 days countdown ended ?

medwatt said:
Are you 100% sure the bootloader is unlocked ? Did you unlock the bootloader via fastboot or you just waited until the 14 days countdown ended ?
Click to expand...
Click to collapse
Yes, I'm 100% sure. I unlocked via fastboot with your thread :good: https://forum.xda-developers.com/lenovo-p2/how-to/lenovo-p2-owners-click-t3668029

kalmas77 said:
Yes, I'm 100% sure. I unlocked via fastboot with your thread :good: https://forum.xda-developers.com/lenovo-p2/how-to/lenovo-p2-owners-click-t3668029
Click to expand...
Click to collapse
What version of Android are/were you on ? You need to be on at least Android 7 S244 to be able to flash LOS 14.1.
What I'd suggest you to do is flash the stock ROM all over again. See this. I have the c72 version myself and I've never encountered the issue you mentioned.

medwatt said:
What version of Android are/were you on ? You need to be on at least Android 7 S244 to be able to flash LOS 14.1.
What I'd suggest you to do is flash the stock ROM all over again. See this. I have the c72 version myself and I've never encountered the issue you mentioned.
Click to expand...
Click to collapse
Yes, I installed 5. P2a42_S244_170725_ROW_fastboot.7z manually through fastboot and updated later to S251 through OTA. LineageOS 14.1 it is and example, which ROMs works for you? I am looking a Android 8 Oreo custom ROM. Do you have to change partion data to EXT4 or something else? I thought it was because I have the C72 version.

kalmas77 said:
Yes, I installed 5. P2a42_S244_170725_ROW_fastboot.7z manually through fastboot and updated later to S251 through OTA. LineageOS 14.1 it is and example, which ROMs works for you? I am looking a Android 8 Oreo custom ROM. Do you have to change partion data to EXT4 or something else? I thought it was because I have the C72 version.
Click to expand...
Click to collapse
I've tried most of the ROMs here and they all work.

I had the same issue while trying to install new AOSiP 8.1 rom, I have unlocked bootloader, latest TWRP but now I am stuck with this error:
failed to mount /data device or resource busy
I cannot install any rom nor wipe data anymore. Stuck on LENOVO blue logo with the android with the lock in the belly! Help please!
PS: I can reboot to fastboot or TWRP
EDIT: i solved the issue rebooting twice from TWRP to TWRP again and making it permanent on the system, now rom is doing first boot.

Thanks, I always making permanent but apparently it was not enough. Now it's working. Probably I only need to boot TWRP through buttons instead of using fastboot commands to making permanent.

[ROM][WIP][ALPHA]Ubuntu Touch 16.04 for Xiaomi Mi5 (gemini)

Hello everyone, today i'm here to share my work with you!
It is based on android 7.1 and on halium 7.1 (Thanks to halium and ubports team!).
I am not responsible for any damage or malfunctions!
Requirements
-You can use which operating system you want.
-Adb & Fastboot tools, you can download it here.
-The phone needs to be updated to android 7 or higher.
-TWRP recovery, you can found it here.
IMPORTANT THINGS
-- If your data partition is encrypted, you need to format it or ubuntu will not boot!
-- If your data partition is f2fs ubuntu will not work so you need to format it in ext4.
-- If your device is stuck on mi logo, flash miui 10 and then repeat the procedure.
Here's the instruction to install it on your device:
1- Download halium-boot.img, system.img and rootfs.img from here.
2- Reboot your device in TWRP, connect it to the computer, open terminal and run these 2 commands
3- adb push system.img /data/system.img
4- adb push rootfs.img /data/rootfs.img
5- Reboot your device to fastboot and run
6- fastboot flash boot halium-boot.img
7- Reboot the device and you'll see ubuntu touch running
Things to be noticed:
-- Default password is: "12345". You can change it by opening terminal on the phone and run "sudo passwd phablet" and insert your new password 2 times.
-- When you disable wifi from settings you aren't able to turn it on (i'm working on it). If you want to enable it open terminal on the phone and run "sudo -i" and "echo sta > /sys/module/wlan/parameters/fwpath".
-- Bluetooth, vibration, camera don't work.
-- Calls and messages are not tested.
-- If you want anbox (android app support) run the following commands on terminal: "wget https://raw.githubusercontent.com/halium-gemini/Ubuntu-touch/master/anbox.sh" "chmod +x anbox.sh" "./anbox.sh". When it will finish read the last line.
-- If you want to use apt to install new binaries you need to mount / as rw: "sudo mount -o remount,rw /" and first run an "sudo apt update".
If you want to tell me something like bugs, ideas or something else you can find me here or on telegram.
Source code: www.github.com/halium-gemini
If you want to offer me a coffe here.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Reserved

It there any way to boot on K20P. Its a dump question. But I really want to use it.

oh thank you.
Downloading right now. will update how it works

where is the download link?
it is better if Bluetooth, vibration, camera cloud work, hope that Bluetooth, vibration, camera cloud work

great

For sure i will always keep my eyes and follow this development. thanks for your work.

Really ubuntu on my Mi 5 ! WoWW
I' ll try

Hello all,
Stuck on Mi boot logo screen nothing happend trying to flash again. I was using pixel experience 10...

Hi,
After flashing miui 10 and then repeat the procedure again but still stuck on Mi logo? please help.
BR

Hello all,
After reformatting data partition worked and running perfect !
Some of using my phone;
-wifi running if you activate on nmtui tool, but cellular is not working actually calling okey but no voice ?
phone call is not working finally, how can I fix
I tried to sudo apt update not fixed
Thanks

Hello !
wow this is the best thing i've seen but it needs some improvement !
Not for daily use, many thanks for your effort and work man !
BR

I've never seen anything like it before.

Hello all,
any update for this image gsm not working
BR

Does it support arm64 software? If so, how to enable?

zengxianxi said:
Does it support arm64 software? If so, how to enable?
Click to expand...
Click to collapse
Right now it is based on armhf (arm 32 bit) because the 64bit version has lot of bugs and there are few applications.

Hello all,
any update for this image gsm not working
BR

Hello all,
any update for this image gsm not working
BR

Can you create halium 9.0 for android 9? I will try gsi ubports.

harris123424 said:
Can you create halium 9.0 for android 9? I will try gsi ubports.
Click to expand...
Click to collapse
Yeah, i could try but right now i have no free time. I'm sorry

V350AWM30e ATT_US stock & rooted partitions

V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.

Thank you for this!

amazing
let's hope something useful comes to the end user

Thanks so much for putting this together. Should I anticipate any issues doing TWRP ADB sideload coming from a Korean rom?

Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

smir_ant said:
Hi! Yesterday I tried to download from the link, but the following error popped up on Mac OS. On Windows, the link just doesn't open. In short, it just can't download...
Click to expand...
Click to collapse
I can download it on windows, it's just extremely slow at 0.5 Mb/s

ghylander said:
I can download it on windows, it's just extremely slow at 0.5 Mb/s
Click to expand...
Click to collapse
yeap, from sative safari (without addblock and another addons) i download too, slow, but success,
thanks for reply

jacob019 said:
V350AWM30e.zip (3.7GB)
I pulled the stock unmodified slot partitions from a fully updated AT&T V35.
I modified them with Magisk and TWRP, and disabled Dm-Verity and ForceEncrypt
I flashed them to another V35AWM that had previously been crossflashed with V350ULM 20f.
Now I stock rooted Android 10 working nicely on my main driver.
I can think of several ways to flash the partitions:
• Using ADB in TWRP (what I did)
• Using ADP from a running rooted system
• One by one with QFIL
The archive includes the unmodified partions, the modified partitions, the packages that I used to modify the partions, some notes, and a script that I used to flash them in TWRP.
If I were doing it again from the start, I would not cross flash, because there are differences in the partition tables. Despite what the guides say, I think that the bootloader can be unlocked from Android 9 or 10, using QFIL. I think that this would work: enable bootloader unlock in developer settings,, flash the engineering bootloader with QFIL, wipe laf, unlock with fastboot, flash the modified boot.img with QFIL, boot into recovery, flash the other partitions from there.
These files are for developers only. You can easily brick your phone and I won't help.
Click to expand...
Click to collapse
Could you reporst the download? I just installed windows 11, so maybe that's the issue, but I keep getting "v350awm30e.zip cannot be downloaded securely." and it refuses to even start the download. Any help would be appreciated.

Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip

jacob019 said:
Working fine for me. Try using https instead of http:
https://jacobstoner.com/V350AWM30e.zip
Click to expand...
Click to collapse
Thanks for the fast reply here and in a DM. For anyone new to windows 11 like me, if you try to download from any website that doesn't have that S in it (http vs https), it will not let you download. After a quick google, you can still download from places like this by right-clicking on the download and selecting "keep this".
You can also click on the lock icon in the url bar and then going to permissions and selecting the option to download unsecure content from this website.
Cheers.

Hi everyone. Do you know where can I download a stock ATT firmware for lg v35? Mine is network locked and I have the code to unlock it but I have to be on original firmware. Please help me if you can. Thanks

[Q] I can't root my xiaomi redmi note 8 pro

Hi, i have a xiaomi redmi note 8 pro (64gb), with the bootloader unlocked, MIUI 12.5.7 global, debug enabled
Using Google Platform-Tools, after entering fastboot (with "adb reboot bootloader") and flashing the twrp recovery (with "fastboot flash recovery twrp.img") I cannot enter the custom recovery, whether I use the combination of button, whether you use the command "fasbtoot boot recovery/twrp.img"
I tried to change the USB port of the PC but I always get the same error: FAILED (Status read failed (Too many links))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know how to fix this error? I don't mind having to format the phone.

Have you tried this ?
Write to device failed (no link / unknown error / too many links) - Sample Code and Directory of libraries for Android Developers - AndroidHiro.com
Write to device failed (no link / unknown error / too many links).I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.Device is already wiped and bootloader unlocked.I am in fastboot mode, I also get some unknown error in...
androidhiro.com

Fytdyh said:
Have you tried this ?
Write to device failed (no link / unknown error / too many links) - Sample Code and Directory of libraries for Android Developers - AndroidHiro.com
Write to device failed (no link / unknown error / too many links).I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.Device is already wiped and bootloader unlocked.I am in fastboot mode, I also get some unknown error in...
androidhiro.com
Click to expand...
Click to collapse
Soo should i use a USB hub?
Because I have already tried to use the method that modifies the registry but it didn't help

umbi027 said:
Soo should i use a USB hub?
Because I have already tried to use the method that modifies the registry but it didn't help
Click to expand...
Click to collapse
Have you tried uninstall ing your device existing drivers, shutting down and turning on you computer and reconnecting your phone again ? This can work in some cases

Fytdyh said:
Have you tried uninstall ing your device existing drivers, shutting down and turning on you computer and reconnecting your phone again ? This can work in some cases
Click to expand...
Click to collapse
I tried and it didn't work, but I tried to install a different recobery (so not the twrp) and it worked
thanks so much, for the help anyway

umbi027 said:
I tried and it didn't work, but I tried to install a different recobery (so not the twrp) and it worked
thanks so much, for the help anyway
Click to expand...
Click to collapse
What recovery have you used that works?

Lucz0xxZ said:
What recovery have you used that works?
Click to expand...
Click to collapse
I followed this tutorial:
I followed the tutorial until the custom recovery was installed and then I used the latest version of magisk downloaded from the official GitHub

umbi027 said:
I followed this tutorial:
I followed the tutorial until the custom recovery was installed and then I used the latest version of magisk downloaded from the official GitHub
Click to expand...
Click to collapse
Thanks!