Xiaomi EU Rom based on MIUI 12
ONLY FOR GRAM
By:- Bhavesh saini aka Banom
Pre-Requisite
1)-Download the Stock recovery for Gram.
2)-Make sure you have installed drivers for adb and fastboot
3)- Install these drivers too and Install them via this method
Instructions::-
1)-Format is must , Reboot into Recovery and format your data and wipe it too.
2)-Now Reboot into fastboot mode
3)-Now flash the Stock recovery of gram .yes you heared it right , Flash stock recovery from fastboot
4)-Now turn off your device and start it again in fastboot
5)-Connect your devices to PC
6)- Extract the Downloaded ROM and Run the file named as gram force wipe.bat
7)-Just sit back and let the process Complete.
Additional Stuffs:-
1)- I made an Fastboot flashable rom this time as Many people are facing reboot to fastboot bugs due to Recovery which is unstable.
BUGS:-
1)-No Pro colour mode in camera.:crying:
2)-Vibrations does not work sometime, Most of the time it works.:angel:
3)-Hotspot does not work:crying:
4)- You tell me, I got no testers for the build so can't comment more
But remember you phone name will be changed to redmi note 9s after flashing this but dont worry it will not cause any problem
Mirrors are welcome, tag/quote me if you mirror, thank you
Support:Telegram @Banomgram
Downloads
New Build :- Here
Thanks to
Xiaomi Eu team
Bhavesh saini (for Porting it and fixing bugs)
XDAevDB Information
Eugram, ROM for the Poco M2 Pro
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: MIUI 12
Version Information
Status: Experimental
Stable Release Date: 2020-09-05
Created 2020-09-05
Updated 2020-09-05
-Reserved-
Simply Amazing!
Hey. The ROM works amazingly well!
Everything seems to work, and animations are beyond smooth.
I haven't really tested the camera yet, but apart from reading mode (for which one can install an app from play store eg. Night Light), everything is perfect. SUPER Smooth!
I was waiting very very eagerly for this ROM. I literally downloaded it the moment you made the links available.
Thanks so much for making this ROM. Cheers
bluesy_kush said:
Hey. The ROM works amazingly well!
Everything seems to work, and animations are beyond smooth.
I haven't really tested the camera yet, but apart from reading mode (for which one can install an app from play store eg. Night Light), everything is perfect. SUPER Smooth!
I was waiting very very eagerly for this ROM. I literally downloaded it the moment you made the links available.
Thanks so much for making this ROM. Cheers
Click to expand...
Click to collapse
Bro can you share some screenshots including notification and control centre?
MIUI 12 for Poco M2 Pro Flasher Designed and created by Bhavesh saini a.k.a BANOM
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.044s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.023s
Erasing 'userdata' OKAY [ 0.187s]
F2FS-tools: mkfs.f2fs Ver: 1.13.0 (2019-09-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 219573912 (107213 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 556] Filling sit area at offset 0x00600000
D:\POCO M2 Pro\ROMS\MIUI 12 For Poco M2 Pro\win_tools/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting into Dynamic Fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
PLEASE HELP
harigavara said:
MIUI 12 for Poco M2 Pro Flasher Designed and created by Bhavesh saini a.k.a BANOM
Make sure that Your phone is connected to Your PC and is in fastboot mode!
Flashing can take around 10-15 minutes
Disabling VBMETA..
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.044s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.023s
Erasing 'userdata' OKAY [ 0.187s]
F2FS-tools: mkfs.f2fs Ver: 1.13.0 (2019-09-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 219573912 (107213 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 556] Filling sit area at offset 0x00600000
D:\POCO M2 Pro\ROMS\MIUI 12 For Poco M2 Pro\win_tools/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting into Dynamic Fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
PLEASE HELP
Click to expand...
Click to collapse
Make sure you have installed the fastboot drivers 9 mentioned in my xda post and installed stock recovery
bhanu saini said:
Xiaomi EU Rom based on MIUI 12
ONLY FOR GRAM
By:- Bhavesh saini aka Banom
Pre-Requisite
1)-Download the Stock recovery for Gram.
2)-Make sure you have installed drivers for adb and fastboot
3)- Install these drivers too and Install them via this method
Instructions::-
1)-Format is must , Reboot into Recovery and format your data and wipe it too.
2)-Now Reboot into fastboot mode
3)-Now flash the Stock recovery of gram .yes you heared it right , Flash stock recovery from fastboot
4)-Now turn off your device and start it again in fastboot
5)-Connect your devices to PC
6)- Extract the Downloaded ROM and Run the file named as gram force wipe.bat
7)-Just sit back and let the process Complete.
Additional Stuffs:-
1)- I made an Fastboot flashable rom this time as Many people are facing reboot to fastboot bugs due to Recovery which is unstable.
BUGS:-
1)-No Pro colour mode in camera.:crying:
2)-Vibrations does not work sometime, Most of the time it works.
3)-Hotspot does not work:crying:
4)- You tell me, I got no testers for the build so can't comment more
But remember you phone name will be changed to redmi note 9s after flashing this but dont worry it will not cause any problem
Mirrors are welcome, tag/quote me if you mirror, thank you
Support:Telegram @Banomgram
Downloads
New Build :- Here
Thanks to
Xiaomi Eu team
Bhavesh saini (for Porting it and fixing bugs)
XDAevDB Information
Eugram, ROM for the Poco M2 Pro
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: MIUI 12
Version Information
Status: Experimental
Stable Release Date: 2020-09-05
Created 2020-09-05
Updated 2020-09-05
Click to expand...
Click to collapse
Great rom no bug here
Thanks alot. Bro plz
Update 12.6 gram
Related
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features
All Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Updated with 3.1.0.0 (And works for any 4X)
panchovix said:
Updated with 3.1.0.0 (And works for any 4X)
Click to expand...
Click to collapse
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
Weird, che1 or che2?
Enviado desde mi 6045B mediante Tapatalk
G620s-lO1
@andrejicd it is rare since the twrp itself was made to the g620s/che1, but it just worked on che2 too, well thanks for the info then
Yes, FAILED (remote: size too large)
It is 24.5M, really too large???
And the twrp-3.0.2-0-cherry.img has the same problem.
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Kireto00 said:
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Click to expand...
Click to collapse
It will work.
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
raven731 said:
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
Click to expand...
Click to collapse
What exactly u did?
Hi,
I have the exactly same problem. This is what I did.
My phone: Che2-L11
1. unlooked bootloader
2. flashed twrp-3.1.1-0-cherry.img and twrp-3.0.2-0-cherry.img from dl.twrp.me/cherry/
3. power of an boot to recovery ends in stucking with "honor" bootlogo.
thanks for any hints
panchovix said:
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features
All Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Click to expand...
Click to collapse
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Lballarini said:
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Click to expand...
Click to collapse
Yup same with me( che1-l04). In adb it says file is too large.
Hi Guys,
I am trying to push it and install but I have this error below. BTW, the phone is per-unlocked. It already has a warning red sign "PHONE Unlocked"
target reported max download size of 471859200 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.594s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.594s
.
Enviado do meu ALE-L21 através de Tapatalk
size of image is larger than target device.
G620s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
use minimal ADB program for flashing
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Marcyvee said:
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Click to expand...
Click to collapse
The same here
# fastboot flash recovery twrp-3.2.3-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25136 KB)...
OKAY [ 0.796s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.810s
At the end power and vol+ but and stock "Huawei eRecovery" start and not twrp. I'm using Che2-L11_V100R001C432B310.
Hi everyone !
I'm a little stuck now, so i really need your help !
I want to install LineageOS on my Xiaomi redmi note 4. So i followed the installation instructions on official Lineage website.
At the step "Install TWRP recovery" i'm stuck.
Here are the logs :
Code:
> $ fastboot flash recovery twrp-3.1.0-0-mido.img
target reported max download size of 134217728 bytes
sending 'recovery' (26840 KB)...
OKAY [ 1.328s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.331s
So after searching on the web I tried splitting img into chunks with the following command :
Code:
> $ fastboot flash -S 20M recovery twrp-3.1.0-0-mido.img
Invalid sparse file format at header magi
sending sparse 'recovery' (20476 KB)...
OKAY [ 1.015s]
writing 'recovery'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 1.019s
I choosed 20M for my chunks randomly (inferior to recovery image of 26840KB).
Other informations :
I can't boot to origin system
I can access to fastboot
I can use adb but my device is in sideload mode
Please feel free to answer if you have any idea.
You're great! Thanks.
Did you already unlock the bootloader? It seems not yet..
crok.bic said:
Did you already unlock the bootloader? It seems not yet..
Click to expand...
Click to collapse
Yes I did !
Code:
> $ fastboot getvar all
...
(bootloader) unlocked: yes
...
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
crok.bic said:
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
Click to expand...
Click to collapse
I'm not sure if it's Mido or Nikel.
Do you have a link for Nikel ? Because it doesn't appear in twrp list :\
For adb i've downloaded with
Code:
sudo apt-get install android-tools-adb
I've tried with 3.1.1-0-mido and same error than 3.1.0 :\
@crok you really rock !
I've tried with this link of Nikel : https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/
And I'm having the recovery mode!
I continue the tutorial !
Great news. Please mark the thread [solved] just to help people who has the same trouble and seeking for info/solution.
Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly
How to download Android 13 for Google Pixel and other Android devices
Google has officially kicked off the Android 13 QPR2 rollout via the beta channel. You can download the release right now and give it a try!
www.xda-developers.com
Android 13 reaches Platform Stability milestone with Beta 3 release
Google today released the third beta build of Android 13. With Android 13 Beta 3, the new release had finally hit the Platform Stability milestone.
www.xda-developers.com
I am on 13 beta 2.1 but every time I upgrade my device gets wiped or corrupted.
I am rooted with no Magisk modules.
A simple upgrade process that will not require a wipe (and stay rooted if possible) will be appreciated. Thanks.
I'm waiting till someone's tires the ota method with new magisk before I update
I took 13 off on beta 1 because Verizon voicemail was lost. Can anyone confirm that voicemail does.qotk from Verizon now?
bturkel said:
I took 13 off on beta 1 because Verizon voicemail was lost. Can anyone confirm that voicemail does.qotk from Verizon now?
Click to expand...
Click to collapse
I was having issues with voicemail too but on TMobile. Latest beta fixed it for me. So far this update seems really solid
Inthonk when it comes to wipe you need to untick w to then not wipe not sure though just from what I read from others so take what I say woth pinch of salt
Im on beta 3.
So far im considering return to 12 stable , i dont have fast charge anymore.
It took 20 min to charge from 50 to 60%
I'm running it (unrooted) with no issues. Much another than 12/12L.
For me root does not work..
While flashing update , the phone does not enter fastbootd when I used from magisk (v25) patched boot.img
(using Pixelflasher or flashing with manual commands)
So I flashed without patched boot.img and flashing worked with loosing root.
Booting patched boot.img with fastboot does work... I get root and Magisk.
But: I cannot patch the boot.img of the device directly... I can do so, but it will never boot again...
(else I boot from fastboot again patched boot.img)
So I cannot get my Pixel 6 pro to boot with patched boot image...
All running fine for me.
Rooted straight away - I patched the boot.img with Magisk 25001 before dirty flashing the factory image (removed the -w flag on the flash.bat), then flashed the patched img
Had no issues whatsoever.
krs360 said:
All running fine for me.
Rooted straight away - I patched the boot.img with Magisk 25001 before dirty flashing the factory image (removed the -w flag on the flash.bat), then flashed the patched img
Had no issues whatsoever.
Click to expand...
Click to collapse
Tried also this way....
That´s what happens:
Spoiler
c:\Pixel 6 flash\raven>flash-all
< waiting for any device >
Sending 'bootloader_b' (13386 KB) OKAY [ 0.303s]
Writing 'bootloader_b' (bootloader) Flashing pack version slider-1.2-8552708
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 3.362s]
Finished. Total time: 3.678s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
Sending 'radio_b' (82740 KB) OKAY [ 1.870s]
Writing 'radio_b' (bootloader) Flashing pack version g5123b-101858-220505-M-8545669
(bootloader) Flashing partition modem_b
OKAY [ 0.109s]
Finished. Total time: 1.991s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.004s
< waiting for any device >
--------------------------------------------
Bootloader Version...: slider-1.2-8552708
Baseband Version.....: g5123b-101858-220505-B-8545669
Serial Number........: 1C211FDEE003Y7
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.000s]
Checking 'version-bootloader' OKAY [ 0.000s]
Checking 'version-baseband' OKAY [ 0.001s]
Setting current slot to 'b' OKAY [ 0.080s]
extracting boot.img (64 MB) to disk... took 0.191s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.482s]
Writing 'boot_b' OKAY [ 0.078s]
extracting dtbo.img (16 MB) to disk... took 0.028s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.375s]
Writing 'dtbo_b' OKAY [ 0.022s]
archive does not contain 'dt.img'
extracting pvmfw.img (1 MB) to disk... took 0.003s
archive does not contain 'pvmfw.sig'
Sending 'pvmfw_b' (1024 KB) OKAY [ 0.024s]
Writing 'pvmfw_b' OKAY [ 0.003s]
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (12 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.003s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor_b' OKAY [ 0.002s]
extracting vendor_boot.img (64 MB) to disk... took 0.210s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (65536 KB) OKAY [ 1.493s]
Writing 'vendor_boot_b' OKAY [ 0.076s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
So it reboots and reboots and reboots, but does not get into fastbootd
If i use volume down button I will only get into normal fastboot and so it exits installation:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Press any key to exit..
Found a solution for me....
I did as above...
flash bootloader and reboot to fastboot
flash radio and reboot to fastboot
And then before flashing the zip file I tried to enter fastbootd with: fastboot reboot fastboot
Then I was in fastbootd
Now I started the: fastboot update ..... (with the patched boot.img)
And it started to flash and does not try to enter fastbootd during the flash, because I am already there...
Mike
I'm on 13b3 rooted and it's working just fine, even better than 13 i find it faster with some extra features that I've find good
On latest beta not rooted, and visual voicemail is working for me, overall stability seems better and so far everything seems like the best this phone has been since launch.
Have they added the ability to connect to multiple bluetooth devices simultaneously yet?
J0nhy said:
I'm on 13b3 rooted and it's working just fine, even better than 13 i find it faster with some extra features that I've find good
Click to expand...
Click to collapse
How did you get yours running? Mine just sits at the "pixel is starting" indefinitely.
I'm a bit confused. Does 13 have other features than 12, or the same features plus more? Shouldn't 13 be a fork off 11 when 12 isn't even finished yet?
RobbyRobbb said:
I'm a bit confused. Does 13 have other features than 12, or the same features plus more? Shouldn't 13 be a fork off 11 when 12 isn't even finished yet?
Click to expand...
Click to collapse
12 was finished and released in October last year, 12.1 (with new features and fixes for big screen devices) released with march feature drop and 13 gonna release this summer/fall with new animations in various places, bug fixes and smaller tweaks etc.
I'll be sticking with 13 beta until it goes stable. FPR is much better and phone seems much smoother and faster.
I downgraded from 13 beta 3 because i thought i lost fast charge ( downgraded and it went on fastboot bootloop, had to flash ota through adb).
Now my phone seems slower , when taking a photo , the camera moves like in slow mo.
Beta 3 still have issues ( like when in landscape mode , to turn wifi on/off i had to scroll the notificaton panel down twice to be able to press the button) but android 12 is way more buggy
mitchst2 said:
I'll be sticking with 13 beta until it goes stable. FPR is much better and phone seems much smoother and faster.
Click to expand...
Click to collapse
I couldn't agree more. The only things I've noticed of course is what everyone's complaining about. Viper won't install. The Xbox app lags out really bad. Haven't noticed any other major problems.
But holy **** is it smoother and faster - with roughly equal battery life.
I want to install lineage on my device and followed the steps from the lineage site.
Redirecting…
The LineageOS is for " Xiaomi Redmi 7A / 8 / 8A / 8A Dual"
Info about Mi439 variants | LineageOS Wiki
wiki.lineageos.org
The download hash was verified and the commands are executed successfully. I am now stuck at "Installing a custom recovery" point 8. The recovery.img was send, but the device is not booting into recovery with power and +, it is not even booting info fastboot with power and -.
The device is showing the Redmi writing and is going dark.
fastboot flash dtbo dtbo.img
Sending 'dtbo' (8192 KB) OKAY [ 0.301s]
Writing 'dtbo' OKAY [ 0.080s]
Finished. Total time: 0.562s
fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.011s
fastboot wipe-super super_empty.img
< waiting for any device >
Sending 'system' (264 KB) OKAY [ 0.012s]
Writing 'system' OKAY [ 0.006s]
Sending 'cust' (0 KB) OKAY [ 0.004s]
Writing 'cust' OKAY [ 0.002s]
Sending 'vendor' (0 KB) OKAY [ 0.004s]
Writing 'vendor' OKAY [ 0.002s]
Finished. Total time: 0.046s
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 2.247s]
Writing 'recovery' OKAY [ 0.713s]
Finished. Total time: 2.994s
Click to expand...
Click to collapse
What went wrong and how can I rescue the device?
ok, after numerous tries with power and -, the device booted into lineage recovery. The USB cable was connected, if it matters.
I am now running lineage 20 on the olivelite.
Nevertheless, I don't understand why it booted in recovery after countless attempts. In addition, I had given up on recovery and only tried to come back to fastboot.
After flash recovery in the instructions I would try fastboot boot next time to avoid the problem.
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
[GUIDE] No Auth Xiaomi Redmi 8A, Redmi 8A Dual and Redmi 7A EDL Flashing using Mi Flash Tool.
[GUIDE] Xiaomi Redmi 8A EDL Flashing using Mi Flash Tool. (Also works for Redmi 7A). This tutorial has been successfully tested with Redmi 8A, Redmi 8A Dual and Redmi 7A all featuring a Qualcomm SDM439 Chipset. WARNING: DO NOT SHORT THE TEST...
forum.xda-developers.com