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
Related
Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.
Error
Can't flash the zip, says "Unable to execute"
falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!
iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"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"
}
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Hi,
Followed the guide but getting this error. I unlocked boot loader but when tried to flash magisk boot. This error comes. I am on latest Build .Is that be a problem ?
{
"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"
}
alwynjoshy said:
Hi,
Followed the guide but getting this error. I unlocked boot loader but when tried to flash magisk boot. This error comes. I am on latest Build .Is that be a problem ?
Click to expand...
Click to collapse
Put the patched.img in your platform-tools folder. If it still doesn't work with..fastboot flash boot magisk_patched.img.....then try using command prompt instead of power shell :good:
Badger50 said:
Put the patched.img in your platform-tools folder. If it still doesn't work with..fastboot flash boot magisk_patched.img.....then try using command prompt instead of power shell :good:
Click to expand...
Click to collapse
I tried putting in the folder, still the same error, Will try with using CMD
alwynjoshy said:
I tried putting in the folder, still the same error, Will try with using CMD
Click to expand...
Click to collapse
Your doing this in bootloader mode as well correct?? ?
Yea bro, you see the command, "fastboot devices"
Only thing I can think of at the moment is make sure your fastboot/adb files are the latest ones.
In case you need to download them
https://developer.android.com/studio/releases/platform-tools
alwynjoshy said:
Yea bro, you see the command, "fastboot devices"
Click to expand...
Click to collapse
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
Thanks buddy. It worked for me. Also found one more command, but didn't try, posting just for the info.
fastboot flash —slot=all boot magisk_patched.img
Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
Deleted
Jiggs82 said:
You need to type in cmd - fastboot flash boot_(whatever slot ur in a or b) magisk_patched.img
Click to expand...
Click to collapse
I only flash slot a, So is there any downside if I didn't flash B slot?
Hello,
I have a mi A2 device that I unlocked it and flashed TWRP on it. I flashed TWRP on both slots and everything was ok.
After that, my USB board or charging board damaged for unknown reasons and the repairman could not fix it, Also, its charging board is very rare in my area and I can't find it.
So, my phone is never detected by PC but it can be charged, and I can't use fastboot commands.
A few days ago without knowing that DotOS has dedicated recovery, I flashed it with TWRP on slot A, and now I can't use TWRP on slot A anymore. But I think the TWRP is still installed on the slot B.
I really need root my device, so please help me.
1- Is there anyway to change slots without fastboot?
2- Can I install TWRP from anyway other than fastboot?
I tried to install TWRP zip file from DotOS recovery but it does not accept any file except DotOs official updates.
I can use adb commands with wireless debugging feature in android 11.
DotOS recovery options (Advanced option Does not include a useful option, just include reboot options and view logs)
{
"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"
}
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
LR7875 said:
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
Click to expand...
Click to collapse
DotOS not include recovery.img in zip file, but it installed recovery too.
Does this solution still works?
DotOS zip file:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
LR7875 said:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
Click to expand...
Click to collapse
Not works, can't flash
So can you boot into system
And did you adb sideload?
LR7875 said:
And did you adb sideload?
Click to expand...
Click to collapse
I can't use adb sideload in recovery, because of damaged usb, I can boot system but can't use sideload command in system
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/A13
-----------------------
{
"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"
}
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
or
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
--------------------------------------------------------------------------------------------------------
REC VERSION
Install with TWRP or fastboot***
flash recovery_ab twrp.img(cmd)
or
./flash recovery_ab twrp.img(Power Shell)
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
---------------------------------------------------------------------------------------------------------
DOWNLOAD
REC VERSION
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/zeus/
__________________________________________________________________________________
Boot version A13
https://mega.nz/folder/7g0EUAxK#HYD-Wl65HCYKa8PiwSsLKQ
Spoiler: Change the language.
woohooo!
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
me to
alpaca2333 said:
hi, i ran `fastboot flash` and i got this error:
```
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
```.
Click to expand...
Click to collapse
bootloader must be unlocked
What command did you use?
NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
i unlocked bl, and i even had magisk installed, maybe magisk's the reason?
command i use:
fastboot flash recovery twrp-3.6.2_12-v3.8.2_A12-zeus-skkk.img
NOSS8 said:
bootloader must be unlocked
What command did you use?
Click to expand...
Click to collapse
flash recovery twrp.img
Bootloader Open
ttistvn said:
flash recovery twrp.img
Bootloader Open
Click to expand...
Click to collapse
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/
NOSS8 said:
You cant flash with this command(A/B partition)
Use this command https://forum.xda-developers.com/t/install-twrp-for-xiaomi-11t-pro.4398007/
Click to expand...
Click to collapse
worked like charm. i was being noob. thx
Working on the a partition
Command :
fastboot flash boot_a twrp.img
Thank you very much
NOSS8. He works
Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?
karkiankit said:
Working super fine, btw there's no system partition listed on Advance wipe. Any idea? and can i now directly flash miui recovery rom (official) using twrp?
Click to expand...
Click to collapse
Normally yes
updated today
dont flash TWRP.
TWRP A12 flashing instructions:
1. boot your device in Fastboot mode
2. fastboot boot recovery_finename.img
This will temporary boot your device to TWRP
3. From TWRP go to Advanced and choose "Flash curent TWRP" - this will permanently install TWRP but will overwrite magisk scripts, so root will be lost.
4. Flash magisk from TWRP - this will fix root.
Very nice.....waiting for updated zip rom....
updated today
new update...very nice working..
new update 3.6.2_12-v3.9 working fine no issues as of now
trinadhchinna7 said:
new update 3.6.2_12-v3.9 working fine no issues as of now
Click to expand...
Click to collapse
Me too