Hello everybody,
I tried to install the unofficial Lineage OS 19.1 ROM through this link and by building it myself, both using the TWRP recovery and the Lineage OS recovery. While old signed nightlies (eg. lineage-18.1-20210411-nightly-channel-signed.zip) of Lineage OS 18 get installed without any issues, both the downloaded and the built zip files (lineage-19.1-20220527-UNOFFICIAL-channel.zip) fail at step 1/2 with the message:
error applying update 28 error - Updater Process ended with ERROR: 1
The steps I've tried to follow many times with the lineage OS 19:
- adb sideload copy-partitions-20210323_1922.zip -> success
- TWRP (twrp-3.5.2_10-0-channel.img)
Wipe: selected all options
ADB Sideload file (e.g. lineage-19.1-20220407-UNOFFICIAL-channel.zip) -> error 28
ADB Push file, then Install file -> error 28
- LINEAGE OS RECOVERY
Wipe data \ Factory reset
Activated Sideload from ADB
ADB Sideload file (e.g. lineage-19.1-20220407-UNOFFICIAL-channel.zip) -> error 28
ADB Sideload the old Lineage 18 file (lineage-18.1-20210411-nightly-channel-signed.zip) -> goes to step 2/2 and installs successfully.
As I'm relatively inexperienced with modding (all I ever did was to just unlock the bootloader and install the roms), I wonder if anyone had the same issue or can help. The USB cable appears not to be the issue, as it always fails with Lineage OS 19 but succeeds with 18. Might it be an issue related to the system partition space?
Thanks in advance
Check installer script and find why installation break.
I can check for you. Find fail and send issue.
Thank you! From the computer terminal the loading process appeared to be fine:
~/Downloads seekhey$ adb sideload lineage-19.1-20220407-UNOFFICIAL-channel.zip
Total xfer: 0.87x
From TWPR (sorry for the bad quality, I couldn't take a screenshot for some reason);
{
"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"
}
Unfortunately, I coundn't gather any significant info from that.
I found the issue, as usual it was just under my eyes.
Since the channel build for Lineage OS 19 uses part of the blobs and settings used for the ocean device (Moto G7 Power), the partitions table should have been rewritten as in the Moto G7 Power, for which the ocean_gpt.bin file was provided in the same folder of the lineage-19.1-20220407-UNOFFICIAL-channel.zip file. So the command:
fastboot flash partition ocean_gpt.bin
let the builds be flashed correctly. Unfortunately my own build bootloops (not surprised, as it was my first build using some ocean blobs I found on GitLab) but SyberHexen's one works fine!
Assalamu Alykm Everyone! I'm using official Linage 19.1. How I report any issue to the developer? I.e. MOTO ACTIONS are not workning.
Related
Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"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"
}
I can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!
flash stock system.img
I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.
did you find a solution
Try method 2 unbrick tool as per what they said, again. No other choice.
Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Instructions
Download TWRP-3.5.2-RMX182X.img from the download link
Place the file in adb folder
Power off your device
Go to fastboot mode by holding Power and Volume Down buttons
Connect your phone to PC
Flash recovery by typing this command
Code:
fastboot flash recovery TWRP-3.5.2-RMX182X.img
Boot into recovery by typing this command
Code:
fastboot reboot recovery
Requirements
Realme 3 Device
PC with fastboot drivers installed or bugjager in another android device
Recovery image
Download
TWRP-3.5.2-RMX182X.img
What's Working?
Decryption
MTP
Flashing images and zips
Backup and Restore
Wiping and Formating
Everything else
Bugs
None
Tell me if you find any
Sources
Recovery Source : https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-10.0
Device Tree : https://github.com/Maanush2004/android_device_realme_RMX1821/tree/twrp-10.0
Screenshots
Spoiler
Thanks to testers
Spoiler
Their Telegram usernames are given below
HELLINFIX
ct_world
Omkarv
TrueTech21
S11K4M4K4N
supremacy_kraken
azharmansoori22
What your custom Rom work? Or you recommend ?
Geri:) said:
What your custom Rom work? Or you recommend ?
Click to expand...
Click to collapse
I am also wondering which ROM I can use as a daily driver too..
Agent Lu said:
I am also wondering which ROM I can use as a daily driver too..
Click to expand...
Click to collapse
Yeah me too, base on your flashing which one is good for gaming and stable? im flashing my realme 3 so i can give the phone to my son.
Will it work on Android 10? If not , can u make one that can be flashed on Android 10. Thnx.
Hello Guys,
I was trying to install Nethunter On my OnePlus 7T Europe with Android 10
10.0.9-EUROPE-OnePlus7TOxygen_14.E.11_OTA_011_all_2003271950_b7c5bfe612-FASTBOOT.zip using following instruction:
Installing NetHunter On the OnePlus 7 | Kali Linux Documentation
From a reset to running NetHunter in 4 steps: Flash latest Android 10 with the unbrick tool Flash TWRP and Magisk Disable force encryption of data partition Install NetHunter Disable OnePlus update service 1. Flash latest stock (OOS) Android 10 1.01. Download and unzip...
www.kali.org
But I had used:
Twrp:
Download TWRP for hotdog
Download TWRP Open Recovery for hotdog
eu.dl.twrp.me
Magisk:
Release Magisk v23.0 · topjohnwu/Magisk
This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...
github.com
I am unable to install with error from screen:
{
"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"
}
Error Failed to mount /system_ext also appears on Magisk and decrypt tool installation.
I saw that a lot of people have seen this, but no one has commented, so I'll just throw you a few guesses. 1. Possibly a bad download of either Kali or your Recovery. 2. However, you said it happens with Magisk too, so I'm thinking it also might be the wrong recovery, are you sure that you have the right recovery.img for your model number? And if so, is it a reliable recovery.img? I know that there is guacamole, guacamoleb, hotdog and hotdogb and there were a handful of unstable TWRP builds due to the force encryption. More information about your device and resources would help, what's your model number, what version of platform tools are you on?
P.s. I'm also assuming that the photo of the log isn't of an instance where you were flashing it through Magisk as a module because you said it happens with Magisk too.
P.s.2 I know you said your phone is the Europe variant, but I'd assume not to many people memorize every model number for devices that they don't own, I'd say that's why we have codenames like guacamole, lol.
{
"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"
}
Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
First firmware with a separate vendor. Non TREBLE.
updated all vendor libs, many changes in DT firmware.
Steps:
1. Install TWRP specifying the vendor section.
2. Cleaning / dalvik / system / cache / data partitions, reboot into recovery;
3. Flash a patch "Patch Vendor"
4. Reboot into recovery;
5. Cleaning / dalvik / system / cache / data partitions / vendor, reboot into recovery;
6. Install firmware + kernel + gapps
7. Reboot to the system
Android Version : 11.0
Security Patch : 5 March 2021
Google Play System Update: 11
kernel version : 3.10.108
Build number: 11.0-20211017
Status : Stable
Downloads:
TWRP
PATCH VENDOR
ROMs + New Kernel
NikGapps
Audio path
Patch for rollback, for the 6th markup
Source codeDiscussion
Big Thanks:
Ampir-nn
how is the stability/battery etc?
also any step by step guide?
wpjohn13 said:
how is the stability/battery etc?
also any step by step guide?
Click to expand...
Click to collapse
Everything is as usual, but now the vendor is separate from the firmware.
Read more here point 1-2.
Rozetkkaa said:
Everything is as usual, but now the vendor is separate from the firmware.
Read more here point 1-2.
Click to expand...
Click to collapse
Thanks i tried another rom and for the moment im testing it out.
bug: Fingerprint, Camera.
Missing Feature: Infrared.
can i apply to myCp3504l ?
this has android 10
@Rozetkkaa keep getting errors and stuck in recovery can you help bit more?
Edit: nvm got it working..have no sound will try sound patch..also noticed battery while flashing it was around 48% when finished setup etc was showing 97% and after a while dropped to 4%. If it cant show battery % correctly then its going to be a problem for me
EDIT2: sound fixed with patch. Again battery percentage seems to be problematic..adding sound patch was around 24% after reboot it was 54%.it also gets very hot on the back as well on the front
Can anyone tell me wich adb drivers do i need for my device cp3504l i have tried so many without luck... i can get adb devices but when i try to backup something i cant pass from 'waiting for device'
Would anyone know the adb drivers I need for my CP3504L? Many have failed... I can get adb devices but can't get past the 'waiting for device' stage when backing up.
Hi Peeps,
Further to my issue within thread >> https://forum.xda-developers.com/t/bricked-oneplus9-pro-unlocked-options-for-newbie.4577539
Listed below is how I/we overcame the fastboot constant boot issue. A little background in case someone comes against the same issues.
I bought a OnePlus 9 Pro in the hope to have a degoogled phone. Following the lineageOS instructions I somehow corrupted my device and when issuing Volume Down & Power got stuck in a fastboot loop.
Failed Resolutions:
1/ MSM
Part of the resolutions mentioned usiing the MSM tool (windows only) However in my case, My windows vm only recognised my phone has a Android Phone nothing else. I should also point out it couldn't go into edl(Both volumes+power) either. Probably why not recognised as OnePlus 9 Pro by windows.
{
"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"
}
2/ Fastboot & Extract payload.bin .img files) & Fastboot Enhanced tool
a/ https://droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
b/ https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/
Both methods needed to reboot in fastbootd mode unfortunately my phone failed with both methods. Got a message regarding failing to boot into userspace
These methods possible would work if windows could recognise the phone/edl is functional.
(Thanks to @TheGhost1951)
Successful Resolution Below - Big thanks goes to @immortalwon
TWRP Method:
[RECOVERY][3.7.0-12.1][UNOFFICIAL][UNIFIED] TWRP with A12/A13 encryption support
This is an unofficial build of TWRP, based on the Android 12.1 branch, that supports encryption used by Android 12 and 13 ROMs. This build is tested on OP9 pro, but it was confirmed to work on regular OP9 too. As always I'm not responsible for...
forum.xda-developers.com
Download link: https://drive.google.com/drive/folders/1MXANZupY0c08n3AZsmqmLJ-isbRYev6m Download from the latest folder.
Official Firmware OnePlus 9 Pro Link: https://oxygenos.oneplus.net/OnePlus9ProOxygen_22.E.13_OTA_0130_all_2111112110_8b4d5c8737d04612.zip
Prerequisites:1/ platform tools installed & path set. (works both on windows/linux) I finished mine on linux due to vm usb issues.
2/ fastboot devices recognises your device,
Initially not entirely sure if this next step was still required or maybe the 2nd option(renaming & moving .img into platform-tools folder) will suffice? maybe someone can advise? I just know it worked for me
1/ Extract zip from above download link to folder.
2/ Issue fastboot boot boot-oos13-firmware.img
After completion my phone had the below options
After clicking reboot & sliding to confirm as advised went into fastboot mode,
Final Successful Method:
1/ Rename file boot-oos13-firmware.img to twrp.img
2/ Place twrp.img inside your platform tools folder.
3/ Now from the command prompt, type this exactly: fastboot boot twrp.img
After completion we had a lot more options within TWRP as below:
1 Now click on advanced, adb sideload and swipe right. If you see options Wipe Dalvik Cache & Wipe Cache DO NOT SELECT!
2/ Move official OnePlus 9 Pro firmware into platform-tools folder & rename to a shorter name, I renamed to twpr.zip
3/ Issue adb sideload twrp.zip (During this stage I moved to my local linux machine as vm wasn't playing nicely with usb.
May see some errors on successful completion.
Upon Reboot Happy Days!
Sorry not really a writer as you can probably tell Thanks for all the guys who assisted me. Happy to report I now have a fully functional LineageOS de-ggogled phone I hope this helps someone in the future. Thanks Daz
Glad you got a functioning phone!