Hello, how the root Color OS 12.1 A08? Magisk patch stable 24.1 not working, heve a bootloop
You can't right now. Because magisk didn't released for Color OS
FardinIslam said:
You can't right now. Because magisk didn't released for Color OS
Click to expand...
Click to collapse
Strange, there is a lot of information on the net about root oneplus 10 pro
I tried Daxiaamu , but program don't start
VovaHouse said:
I tried Daxiaamu , but program don't start
Click to expand...
Click to collapse
maybe you need try to change another PC, or I think my tool need Chinese language package be installed
daxiaamu said:
maybe you need try to change another PC, or I think my tool need Chinese language package be installed
Click to expand...
Click to collapse
Hello Daxiaamu, I try chenge PC and Chinese language,but program don't start. Program try start but force closed,this is what it shows.
Video
What you Chinese language in PC?
Chinese have many modifications
{
"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"
}
Yaahoo, I just got root.
But, questions why dont start the program Daxiaamu.
If anyone is interested in how to get root, you should patch boot using magisk and then try fastboot boot boot.img (magisk) and then press automatic installation in the magis application.
Boot.zip (magisk) Color OS 12.1 A08
Here's the file Color OS 12.1 A08 5cd574edfd2740cd86bde59f378ede06 convert from payload to IMG file for fastboot.
Sorry files is big i will try and give link
Now when i try and fastboot flash system_a or b it says
Sending 'system_a' (570364 KB) OKAY [ 13.297s]
Writing 'system_a' FAILED (remote: '(system_a_b) No such partition')
fastboot: error: Command failed
sorry i posted my last two post in wrong post...sorry
Root OnePlus 10 Pro running ColorOS 12 *almost* the same as every other device. However, you should patch the vendor_boot.img along with the boot.img and don't specify the slot, just do this
fastboot flash vendor_boot magisk_patched-vb.img
fastboot flash boot magisk_patched-bt.img
If you get any errors then flash vbmeta.img with disable verity/verification command
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then flash the patched images again
( As you can see by the time in the screenshot, it's getting a little late here, so if I don't get back to you soon I'll check back tomorrow and see how you got on with it )
Related
i am trying to upgrade from ginger bread to jellybean
jelly bean needs a 250mb internal memory for the system so what i did is partition my internal memory using blackrose i did partition it and wipe all the data except the SD after that i notice that the OS is gone so i search for a solution and found this one http://forum.xda-developers.com/wiki/HTC_Nexus_One/Recovery_Images but when i try to command adb devices in cmd ,it didnt displays my device serial or something and if i command adb shell it says error device not found,so i look for another solution,i found solution on fastboot mode,
screenshot of my device when i select bootloader
{
"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 tried
fastboot device
fastboot oem unlock but error occured again it says command error
i tried another
like booting or flashing boot.img and recovery.img
but it both says cannot open boot.img or recovery.img
i think i got my device bricked,anyone can help me please? i cant use my phone now :crying:
If you have blackrose than you have s-off/unlocked bootloader
So you now need to flash a recovery via fastboot and then boot to the new recovery and then flash ROM of choice, do not flash any stock firmware (may have a radio in it which could result in a brick)
http://forum.xda-developers.com/showthread.php?t=2277112
Here are some tips on how to use fastboot properly, if you get stuck and need further help be sure to copy and paste all input/output from cmd/terminal here
Best of luck
Sent from my Nexus 7 using Tapatalk 2
i got this error when trying to unlock bootloader
<bootloader> [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.16s
Click to expand...
Click to collapse
Again, you have black rose, you do not need to run unlocked command - you have s-off
What you need to do is flash a recovery through fastboot and then boot to new recovery and then flash ROM of choice
Do not run fastboot oem unlock - this will do nothing for you
Do not flash factory firmware with out being sure what you are flashing or this can result in a brick, just flash recovery then ROM
Sent from my Nexus 7 using Tapatalk 2
ok thanks got it fix
{
"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 previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.
So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.
Hi,
I don't have a vbmeta.img at hand, but I have a "vbmeta_a" and "vbmeta_b" partition checked by the command written in the install instructions.
So how can I continue with this?
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Click to expand...
Click to collapse
So the question is where do I get vbmeta.img from?
And just to be sure:
I'm on LineageOS18.1, unlocked bootloader. The install instructions of Magisk tell me to patch a "boot image". But which one?
The LineageOS installl instructions mention a "vendor boot img", this one: https://wiki.lineageos.org/devices/sake/install#flashing-the-vendor-boot-partition
Is this correct?
Or otherwise, where to get the boot image out of https://download.lineageos.org/sake ? I just see this inside the zip:
{
"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"
}
Or is boot image = recovery image? LineageOS does provide a recovery image:
that is flashed into boot partition like this:
fastboot flash boot <recovery_filename>.img
So is this the one I need to take to patch?
Ok, I found out that you actually can extract the boot.img from the payload.bin using this instructions: https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas
So now I have a boot.img from there. Is this the correct one?
I am still a bit puzzled because LineageOS install instructions let me install the recovery into the boot partition, acting as a de-facto boot image:
fastboot flash boot <recovery_filename>.img
Yes, they actually let me do this and it worked fine, see https://wiki.lineageos.org/devices/sake/install#temporarily-booting-a-custom-recovery-using-fastboot
So then which should I choose? <recovery_filename>.img? boot.img? Or sake_vendor_boot.img? It's so confusing...
And I found out that boot.img and the <recovery_filename>.img are actually almost the same files. Only like a few ~50 bytes differ. So in LineageOS terms, <recovery_filename> is actually a boot image.
But still sometimes a few bytes can make a difference between working phone and brickwall. So I will still wait for a conformation which one I should choose.
Also still open question about vbmeta.img?
Mario545 said:
where do I get vbmeta.img from?
Click to expand...
Click to collapse
usually inside rom.zip :
loopypalm said:
usually inside rom.zip :
Click to expand...
Click to collapse
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?
Mario545 said:
Yes, indeed, thanks. After extracting the payload.bin, a vbmeta.img was present.
But, and maybe I am a bit overcautious here, what is the purpose of flashing the unmodified stock vbmeta.img again? I mean I didn't see any instructions to acutually modify the vbmeta.img. Did I miss something?
Click to expand...
Click to collapse
use the one present in custom roms
vbmeta is flashed to prevent the system from restoring the default recovery
It worked! I didn't brick my phone! Thank you so much for your answer.
To summarize, if you are on ASUS Zenfone 8 + LineageOS 18.1, and you are confused which image to patch:
Recovery image NO!
Vendor boot image NO!
boot.img extracted from the LineageOS zip by following https://wiki.lineageos.org/extracti...ing-proprietary-blobs-from-payload-based-otas YES!
And this extraction process also gives you the vbmeta.img you need to flash (unmodified!).
Mario545 said:
ASUS Zenfone 8
Click to expand...
Click to collapse
twrp is available for that phone
no need to complicate the simple tasks ^......^
A12.1Flashing instructionsadb reboot bootloader
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
fastboot reboot recovery
in recovery wipe data(factory reset)
then select apply update from adb
and from pc sideload rom.zip and reboot
DOWNLOAD
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina
{
"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"
}
Others AOSP ROM
https://forum.xda-developers.com/t/shared-aosp-rom-a13-by-ipsbhangu.4483171/
https://forum.xda-developers.com/t/aosp-shared-evolutionx-v6-7-unofficial-by-preet0608.4486623/
why this rom isn't in the developement thread?
Is it because it's shared?
Edmondo Occhipinti said:
why this rom isn't in the developement thread?
Is it because it's shared?
Click to expand...
Click to collapse
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.
NOSS8 said:
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.
Click to expand...
Click to collapse
So shared roms go on the General section?
Edmondo Occhipinti said:
So shared roms go on the General section?
Click to expand...
Click to collapse
yeap ,because i am not a developer.
Hello.
Someone try it ?
I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img
Cengiz67 said:
I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img
Click to expand...
Click to collapse
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced - flash current TWRP.
So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img
Cengiz67 said:
So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img
Click to expand...
Click to collapse
Img must be in the same folder as the command.
try to install platform tools and put the img inside.
check syntax.
I did it but doesnt work
Cengiz67 said:
I did it but doesnt work
Click to expand...
Click to collapse
Post a screenshot of the CMD
Install with commands or with the TWRP but not both.
OK when i try again i ll post it
Does screen mirror work properly in this rom?
Or what are the current and known bugs?
Anyone use this ROM as a daily driver?
Update
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Senior Moderator
Hello all,
I recently got my motherboard replaced after the pixel 5a died. The problem was covered under the extended warranty. Phone works just fine when I received it back. I tried rooting it using magisk to patch the boot.img file. After fastboot flash boot file.img, my phone would say device is corrupt and unable to start.
I downloaded the factory image from google. Tried using flash-all to completely restart the process. Used latest platform-tools (downloaded today). Bootloader is unlocked. I keep getting this error during the flash-all process and my phone is unable to boot. I'm still able to access fastboot. Where am I going wrong?
{
"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"
}
Here is larger screen shot of the entire flash-all process.
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
flash stock rom via chrome browser , then patch boot.img and flash again to root , i am in lastest version a13 and root work fine
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This is the fix, download platform-tools 34.0.0
Typhus_ said:
The issue is a known bug with latest SDK platform tools. Download and install platform-tools ver 33.x and you'll be fine.
Cheers!
Click to expand...
Click to collapse
This was my problem. I used 33 and it worked fine, thanks. Anyone know when it'll get fixed for 34?
when flash patched boot.img and is corrupt!!! Than Patch the recovery.img and flash it to Recovery Partition, you must start the device with Buttons-Combo in Recovery-Mode to start the System with Root!!! think you have no Recovery-Mode on this Method, you must Flash recovery.img new to use Recovery-Mode!!!