Related
Hello everyone,
I'm currently on the latest 'stable' cyanogenmod custom rom (cm-12.1-20150901-SNAPSHOT-YOG4PAO236-bacon.zip)
Now I want to switch to the latest oxygen OS version.
I found on the official site the 1.0.0 Version as a zip file.
I wantes to flash it via twrp - but it fails every time.
Does anyone got a real noob friendly tutorial how to switch from cyanogenmod to oxygen os?
jolle-pe said:
Hello everyone,
I'm currently on the latest 'stable' cyanogenmod custom rom (cm-12.1-20150901-SNAPSHOT-YOG4PAO236-bacon.zip)
Now I want to switch to the latest oxygen OS version.
I found on the official site the 1.0.0 Version as a zip file.
I wantes to flash it via twrp - but it fails every time.
Does anyone got a real noob friendly tutorial how to switch from cyanogenmod to oxygen os?
Click to expand...
Click to collapse
Do a full wipe and just flash OxygenOS. There's no reason why it'll fail. I've been hoping around OxygenOS and other ROM for a number of months and I never had that issue. Use TWRP 2.8.6.0 to flash
OKay my fault. I missed to unzip the downloaded zip file.
Now I got it
Recently I decided to play around with my retired xiaomi 4c which I bought in 2016/2017.
Firstly, I unlocked my phone and installed TWRP recovery. (the version I installed is twrp-3.1.1-0-libra), the link I used is here: https://dl.twrp.me/libra, the reason why I did not install version 3.1.1-1 is that It won't load in recovery mode.
Secondly, I tried to install lineage 14.1, 15.1,16.1, 17.1 (none of them worked), It gave me this error
E3004 the packge is for device 4c,libra, this device is .
After searching on google, I deleted the first line (the assert statement) in META-INF\com\google\android\updater-script.
I guess it managed to be installed (no error pop out).
the log displayed while it is installing:
detected filesystem ext4 for /dev/block/bootdevice/by-name/system
packing system image unconditionally
However, when I click boot to system, it stuck on the mi logo.
I need some suggestions on how to make this work.
Thanks in advance!
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Gourcuff14 said:
Flash the latest available official miui (currently V10.1.1.0), via mi flash tools
Flash twrp or orangefox, via ADB. twrp official site has an old version, androidfilehost has a newer version TWRP-20190528-3.3.1.0-libra. orangefox official site has taken down libra files but sourceforge has OrangeFox -R10.0-1-Stable-libra.
Then try again
Click to expand...
Click to collapse
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
momocraft said:
I experienced "this device is ." problem before.
From I read somewhere in XDA, sometimes a ROM may require certain recovery images to flash. So if the image is published with some recovery, you may want to try them together.
The last time I flashed my mi4c successfully, the LineageOS build and TWRP are both from this post: https://forum.xda-developers.com/t/rom-android-8-9-10-unofficial-lineageos-for-mi-4c-mi-4s.4008625/ .
Good luck
Click to expand...
Click to collapse
Thank you, I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird.
Haha but now I failed to bypass the ssl pinning through sslunpinning and frida ><, frida says Bad access due to invalid address
Any idea how to fix this?
Try the boot image included in this build package and post your findings in that thread for assistance.
[ROM][8.1/9/10/11][Unofficial][EOL] LineageOS for Mi-4c/Mi-4s
DESCRIPTION Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download. FEATURE The following items may not be available for...
forum.xda-developers.com
you need orangefox for mi4c
yanzifan021 said:
Thank you! I finally managed to install lineage 14.1, but not 15.1, 16.1 or 17.1, weird
Click to expand...
Click to collapse
Hi friend, could you share the download link 14.1, thanks
timsg said:
Hi friend, could you share the download link 14.1, thanks
Click to expand...
Click to collapse
Here there are some builds https://androidfilehost.com/?w=search&s=libra&type=files&page=19
Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP.
Hi!
There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android versions.
I'll keep this updated as long as i think it should be.
The boot images are patched with latest Magisk Canary.
OxygenOS
Android 11 & 12
11.2.6.6 - DA/BA
11.2.7.7 - DA/BA
11.2.8.8 - DA only
11.2.9.9 - DA/BA
12.C36 - Global only
12.C44 - Global only
12.C47 - EU only
12.C48 - Global only
12.C60 - DA only
12.C62 - Global only
12.C64 - EU only
12.C65 - EU only
Android 13
13.F16 - Global/EU/India
Paranoid Android
Android 11 & 12
Ruby Alpha 1
Ruby Alpha 2
Sapphire Alpha 1
Sapphire Beta 1
Sapphire Beta 1 (2022.06.11 build)
Sapphire Beta 1 (2022.06.17 build)
Unofficial Sapphire (2022.07.27 build)
Unofficial Sapphire (2022.08.18 build)
Android 13
Topaz Beta 1
Topaz Beta 1 unofficial (2022.11.20 build)
LineageOS 19.1 and PEX users: You can flash Magisk in recovery, you don't need to patch/flash the images. (probably same for crDroid)
[=HIDE]
Just tested 11.2.7.7, works without any issue.
Thanks for awesome work!
Added PA Ruby Alpha 2 images
Added 11.2.7.7BA images
Added crDroid images
EDIT: Now removed from the list, pretty outdated
oops
Added 11.2.9.9DA/BA images.
Not sure it really matters, but here's a Magisk-patched 11299AA boot img:
boot11299AAmagisk.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks, guys just rooted!
q
reaper000 said:
Not sure it really matters, but here's a Magisk-patched 11299AA boot img:
boot11299AAmagisk.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
hello, do u have stock boot img?
qqroza said:
hello, do u have stock boot img?
Click to expand...
Click to collapse
Here you go:
boot11299AAstock.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
reaper000 said:
Here you go:
boot11299AAstock.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
thx, dude, u are a saint
Added 12.C36 images.
EDIT: Flashing these should work for C39 too, but to be sure here are the steps to get latest image rooted:
1. Install latest Magisk Canary
2. Reboot to fastboot mode
3. Type fastboot boot patched_image.img (DON'T FLASH, JUST BOOT)
4. Now the booted image is rooted, but the one on the device is not, so now we have to patch it. Go to Magisk Manager and Install > Direct Install.
5. Reboot
_MartyMan_ said:
Added 12.C36 images.
EDIT: Flashing these should work for C39 too, but to be sure here are the steps to get latest image rooted:
1. Install latest Magisk Canary
2. Reboot to fastboot mode
3. Type fastboot boot patched_image.img (DON'T FLASH, JUST BOOT)
4. Now the booted image is rooted, but the one on the device is not, so now we have to patch it. Go to Magisk Manager and Install > Direct Install.
5. Reboot
Click to expand...
Click to collapse
Thx Marty, it's working for me. I tried with some methods and yours its perfect and functionally
No mirrors found for OOS 12, patched nor stock.
Add: LE2111_12.C.36 12.C36 / DA - Patched and Stock
franko_m19 said:
Add: LE2111_12.C.36 12.C36 / DA - Patched and Stock
Click to expand...
Click to collapse
Has anyone tried to flash the C36 magisk over C39 and obtained root?
avid_droid said:
Has anyone tried to flash the C36 magisk over C39 and obtained root?
Click to expand...
Click to collapse
+1
C39 file boot doesnt find it?
avid_droid said:
Has anyone tried to flash the C36 magisk over C39 and obtained root?
Click to expand...
Click to collapse
It´s the same boot file. Now it´s working for me but only with Magisk Canary.
iaio72 said:
+1
C39 file boot doesnt find it?
Click to expand...
Click to collapse
Not, but it´s working with C36.
I am using my poco x3 pro with mi eu as my daily driver; however, duplicate apps still reign supreme and the default mi music app doesn't get recognized in Android Auto.
I have dabbled in custom roms before, a couple times but most of them have stopped me from completely using the phone normally, namely broken camera support with drive doesn't recognizing the camera (even with gcam, don't @ me), slow document viewer and so on. As such, I generally refrained from using them, until I saw Crdroid 8 with MIUI cam, which seems like the best of both world for me.
The guides on the thread are too vague? And Im not sure about updating (the rom required a custom recovery image, however, my recovery is too old and i don't want to risk my phone getting bricked)
Can someone help? Thanks a lot!
bump
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
AmmarHaseeb said:
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
Click to expand...
Click to collapse
Does this erase the internal storage? I don't have an SD card and a usb otg
BreadGyarados said:
Does this erase the internal storage? I don't have an SD card and a usb otg
Click to expand...
Click to collapse
I already got that figured out
BreadGyarados said:
I already got that fig
Click to expand...
Click to collapse
BreadGyarados said:
I already got that figured out
Click to expand...
Click to collapse
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
irmas5 said:
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
Click to expand...
Click to collapse
I see!
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
BreadGyarados said:
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
Click to expand...
Click to collapse
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
pl1992aw said:
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
Click to expand...
Click to collapse
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
BreadGyarados said:
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
Click to expand...
Click to collapse
The deciding matter is the Android system currently installed in the phone.
Your example is MIUI.eu with Android 11, in custom recoveries should be able to see internal storage.
[Phone is now Android 11]
After you install CrDroid Android 12 and boot, then custom recoveries cannot see internal storage if it's encrypted.
[Phone is now Android 12]
If you revert from CrDroid Android 12 to MIUI.eu Android 11 and boot, then custom recoveries should be able to see internal storage again.
[Phone is now Android 11]
If your phone is now Android 12, when you want to install something or flash/update a ROM in custom recoveries, it will be a bit complicated as mentioned earlier. You have to sideload with commands.
If you have microSD cards in the phone or USB OTG, then custom recoveries should be able to read them even under when phone is Android 12.
Whether ROMs can dirty flash or not, you have to read the ROM thread and replies (or Telegram if there is no XDA thread), especially replies by the developer.
Some version cannot be dirty flashed, even if it's by the same developer.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.