Question Stuck on Bootloader after Miui13 Update (India) - Xiaomi 11T Pro

Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions

djkrish5610 said:
Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions
Click to expand...
Click to collapse
You have to update it from fastboot as you are already rooted.
Boot it to fastboot and flash the fastboot ROM. I will go with MMX ROM as it's already rooted and debloated further from xiaomi.eu. Have been using for a day and works very well!
XIAOMI 11T PRO | UPDATES
#MIUI #MMX #MIUI #S #Vili #ROM MiuiMix V13.0.2.0 [MIUI 13] | Android 12 Updated:18/03/2022 ▪️Download: AFH | SF ▪️Flashing instructions By MMX Team Follow @Xiomi11TProUpdates Join @mi_11t
t.me

djkrish5610 said:
Stuck on Bootloader after Miui13 Update (India)
Stock Rom-12.5+Magisk 24.3, After update is received installed & flashed magisk on other slot to restart & stuck on MI Logo
Stock miui13 Recovery noticed, Twrp can be loaded but touch is not working
Any suggestions
Click to expand...
Click to collapse
Start to restore the phone to its original configuration:https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Then install a custom rom .

It Shows me as flashing done on both roms A11 & A12
{
"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"
}
MiFlash Logs as below:
[23:05:05 4b9da9b0]:MiFlash 2021.2.26.0
[23:05:05 4b9da9b0]:vboytest index:1
[23:05:05 4b9da9b0]:Thread id:13 Thread name:
[23:05:05 4b9da9b0]:image path:\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global
[23:05:05 4b9da9b0]:env android path:"C:\MiFlash\Source\ThirdParty\Google\Android"
[23:05:05 4b9da9b0]:script :\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global\flash_all.bat
[23:05:05 4b9da9b0]hysical Memory Usage:3936256 Byte
[23:05:05 4b9da9b0]:start process id 6236 name cmd
[23:05:05 4b9da9b0]:begin FlashDone
[23:05:05 4b9da9b0]:errMsg is null
[23:05:05 4b9da9b0]:no need checkPoint
[23:05:05 4b9da9b0]:flash done
[23:05:05 4b9da9b0]rocess exit.
[23:05:10 4b9da9b0]:flashSuccess True
[23:05:10 4b9da9b0]:isFactory False CheckCPUID False
[23:05:10 4b9da9b0]:before:flashSuccess is True set IsUpdate:True set IsDone True
[23:05:10 4b9da9b0]:after:flashSuccess is True set IsUpdate:false set IsDone true
Manual Flash is working fine, but after reboot stuck on fastboot only

djkrish5610 said:
It Shows me as flashing done on both roms A11 & A12
View attachment 5573997
MiFlash Logs as below:
[23:05:05 4b9da9b0]:MiFlash 2021.2.26.0
[23:05:05 4b9da9b0]:vboytest index:1
[23:05:05 4b9da9b0]:Thread id:13 Thread name:
[23:05:05 4b9da9b0]:image path:\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global
[23:05:05 4b9da9b0]:env android path:"C:\MiFlash\Source\ThirdParty\Google\Android"
[23:05:05 4b9da9b0]:script :\Mi11tpro\vili_global_images_V13.0.2.0.SKDMIXM_20220223.0000.00_12.0_global\flash_all.bat
[23:05:05 4b9da9b0]hysical Memory Usage:3936256 Byte
[23:05:05 4b9da9b0]:start process id 6236 name cmd
[23:05:05 4b9da9b0]:begin FlashDone
[23:05:05 4b9da9b0]:errMsg is null
[23:05:05 4b9da9b0]:no need checkPoint
[23:05:05 4b9da9b0]:flash done
[23:05:05 4b9da9b0]rocess exit.
[23:05:10 4b9da9b0]:flashSuccess True
[23:05:10 4b9da9b0]:isFactory False CheckCPUID False
[23:05:10 4b9da9b0]:before:flashSuccess is True set IsUpdate:True set IsDone True
[23:05:10 4b9da9b0]:after:flashSuccess is True set IsUpdate:false set IsDone true
Manual Flash is working fine, but after reboot stuck on fastboot only
Click to expand...
Click to collapse
I see on your post "flash_all.bat" but the flash must end with an error since you don't re-lock the bootloader.
post the Miflash log.
try this rom (fastboot)https://xiaomifirmwareupdater.com/miui/vili/stable/V12.5.2.0.RKDINXM/

Device is still unlocked
Tried V12.5.2.0.RKDINXM (India) & V13.0.2.0.SKDMIXM (Global) Fastboot Rom
For Global V13 Rom everything completed but phone still on fastboot mode
Let me try again for v12 india fastboot rom

djkrish5610 said:
Device is still unlocked
View attachment 5574073
Tried V12.5.2.0.RKDINXM (India) & V13.0.2.0.SKDMIXM (Global) Fastboot Rom
For Global V13 Rom everything completed but phone still on fastboot mode
Let me try again for v12 india fastboot rom
Click to expand...
Click to collapse
Again post your logs for each flash

After V12 rom

Finally MMX OS flashed on fastboot rom & Phone started breathing again
@NOSS8 @RainGater For Helping on this.
I guess flash file need to be followed as MMX rom

djkrish5610 said:
Finally MMX OS flashed on fastboot rom & Phone started breathing again
@NOSS8 @RainGater For Helping on this.
I guess flash file need to be followed as MMX rom
Click to expand...
Click to collapse
That is what I was telling you that flashing MMX is as easy as saying 1-2-3. lol
adb reboot bootloader
windows_fastboot_first_install_with_data_format.bat
Done!

Which recovery will go with mmx rom

Related

Please Guide How to Flash a New ROM (Stock) on ASUS ZENFONE 4 T00I

Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
Bootloader : Could never unlock. Tried the app but never success.
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Final Status: No System on / No firmware on device at all. Can use Droidboot thats all.
Now please help me to give life to the device...
Thank you in advance.
C:\Zenfone>fastboot flash boot boot.img
sending 'boot' (8661 KB)...
OKAY [ 1.375s]
writing 'boot'...
OKAY [ 1.859s]
finished. total time: 3.234s
C:\Zenfone>fastboot flash fastboot droidboot.img
sending 'fastboot' (11253 KB)...
OKAY [ 1.578s]
writing 'fastboot'...
OKAY [ 2.156s]
finished. total time: 3.734s
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-9.9.9.0-user.zip
sending 'update' (825100 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
==================================================
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-7.4.4.0-user.zip
sending 'update' (837024 KB)...
OKAY [ 37.469s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 37.578s
==================================================
AFT not detecting device and showing this error everytime I connect or disconnect device (in droidboot mode)
{
"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"
}
Maybe you can search this files on google :
1. 6.5.35 system.img.gz file
2. 6.5.35 boot.img file
3. 6.5.35 fastboot img file
Should be the same version, then flash it..
Ok, I will try that.
Although I wanted to know whats d fault and where did I go wrong on procedures? I could not unlock bootloader so will fastboot allow me to flash the mentioned firmware images?
Why AFT dint worked for me and. Lot of questions around.. I AINT NOOB FOR ANDROID but. Dis device does not hv anything similar to axnormal android.
Sorry for behaving noob.
Thnkyou for help
Help me please
the AFT i installed on my pc doesnt detect the raw file i have
i've spend two weeks to solve this still no luck
please give me some advice how do i fixed my zenfone 4 its stuck on ASUS LOGO
Fix it already but got a new problem
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
u guys can use this method
http://forum.xda-developers.com/zenfone-4/general/guide-how-to-flash-stock-rom-relock-t3302917

[ROM][10.0.0][UNOFFICIAL] exTHmUI for XPERIA 1 II

What's This?
exTHmUI is an open source Android project with Touhou element, based LineageOS.
WARNING!!
0 . YOU NEED TO FLASH VBMETA AND DTBO BEFORE YOU FLASH IT ! YOU CAN FIND IT IN SJll'S ROM !
Important Information​1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 or Lineage OS 17.1 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
exThm UI10.0:
Unofficial-build: Links (Upload in MEGA)
Sorry, I don't have AFH account
Google Applications (optional):
OpenGapps: Already Prebuilt.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
Code:
fastboot reboot fastboot
4. Flash exTHM UI:
Code:
Code:
fastboot set_active a
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash Pixel Experience Plus, Wipe the old userdata:
Code:
Code:
fastboot erase userdata
6. Root And Xposed:
Use Pixel Experience or Lineage's Recovery to flash Magisk.
Code:
Code:
adb sideload magisk.zip
If you need Xposed Framework. Maybe you need to flash Edxposed with riru-core in Magisk.
Big Thanks
LineageOS Team
exTHmUI Team
Device Tree: Just use Lineage OS 's Device tree by Sjll
Contributors
baolong24
cjybyjk
Sjll
Cramfs28
exTHmUI Team
Screenshot:
{
"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"
}
Thread closed at OP request

Redmi Note9 Codename Merlin -- Cant find the Testpoints for EDL - see Picture

Hello, i need some Help for the EDL Flash on Redmi Note9 Codename Merlin.
Fastboot and Recovery does not work. Reboot after Redmi Sign.
Bootloader is open, Backcover is open. What must i do now?
Please help me for finding Testpoint.
{
"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"
}
First, close your device and keep it untouched.
Next, follow this guide:
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
VD171 said:
First, close your device and keep it untouched.
Next, follow this guide:
Click to expand...
Click to collapse
Thanks but i have a mistake at the end from the bat.
[2021-08-05 06:32:01.748392] Waiting for device
[2021-08-05 06:32:19.245436] Found port = COM9
[2021-08-05 06:32:19.429782] Device hw code: 0x707
[2021-08-05 06:32:19.429782] Device hw sub code: 0x8a00
[2021-08-05 06:32:19.429782] Device hw version: 0xca00
[2021-08-05 06:32:19.429782] Device sw version: 0x0
[2021-08-05 06:32:19.429782] Device secure boot: True
[2021-08-05 06:32:19.438464] Device serial link authorization: True
[2021-08-05 06:32:19.438464] Device download agent authorization: True
[2021-08-05 06:32:19.438464] Disabling watchdog timer
[2021-08-05 06:32:19.438464] Disabling protection
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 36, in exploit
udev._ctx.managed_claim_interface = lambda *args, **kwargs: None
AttributeError: 'NoneType' object has no attribute '_ctx'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 213, in <module>
main()
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 58, in main
result = exploit(device, config.watchdog_address, config.payload_address, config.var_0, config.var_1, payload)
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 38, in exploit
raise RuntimeError("libusb is not installed for port {}".format(device.dev.port)) from e
RuntimeError: libusb is not installed for port COM9
Drücken Sie eine beliebige Taste . . .
Frettchen-Kalle said:
Thanks but i have a mistake at the end from the bat.
[2021-08-05 06:32:01.748392] Waiting for device
[2021-08-05 06:32:19.245436] Found port = COM9
[2021-08-05 06:32:19.429782] Device hw code: 0x707
[2021-08-05 06:32:19.429782] Device hw sub code: 0x8a00
[2021-08-05 06:32:19.429782] Device hw version: 0xca00
[2021-08-05 06:32:19.429782] Device sw version: 0x0
[2021-08-05 06:32:19.429782] Device secure boot: True
[2021-08-05 06:32:19.438464] Device serial link authorization: True
[2021-08-05 06:32:19.438464] Device download agent authorization: True
[2021-08-05 06:32:19.438464] Disabling watchdog timer
[2021-08-05 06:32:19.438464] Disabling protection
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 36, in exploit
udev._ctx.managed_claim_interface = lambda *args, **kwargs: None
AttributeError: 'NoneType' object has no attribute '_ctx'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 213, in <module>
main()
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\main.py", line 58, in main
result = exploit(device, config.watchdog_address, config.payload_address, config.var_0, config.var_1, payload)
File "C:\Users\COMPAKT17\Downloads\VD171_MTK-bypass-v1.5\VD171_MTK-bypass-v1.5\Bypass\src\exploit.py", line 38, in exploit
raise RuntimeError("libusb is not installed for port {}".format(device.dev.port)) from e
RuntimeError: libusb is not installed for port COM9
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Did you install the python module pyusb?
Did you try to run as administrator?
thank you VD171
it works perfektly now.
i trie it with 12.04 global, then auto update to 12.08 und at last auto update to 12.01 (android11)
bootloader is 2nd time open now .-)
it try 3.41 recovery with admin fastboot command and all seen fine - but not so is.
Cant boot in twrp - there is no twrp? and now?
//edit
i think this was it (no twrp) that me brick the phone the first time flash custom rom ;-)
Frettchen-Kalle said:
thank you VD171
it works perfektly now.
i trie it with 12.04 global, then auto update to 12.08 und at last auto update to 12.01 (android11)
bootloader is 2nd time open now .-)
it try 3.41 recovery with admin fastboot command and all seen fine - but not so is.
Cant boot in twrp - there is no twrp? and now?
//edit
i think this was it (no twrp) that me brick the phone the first time flash custom rom ;-)
Click to expand...
Click to collapse
Good work, my friend.
I suggest you to try all recovery project you can, and then you can choose one:
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN (Redmi Note 9 / Redmi 10X 4G)
Works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Warnings: - This is not a development thread. This is a help thread. - I didn't build any of them. Use at your own risk. - I don't have the source code for any of them. Use at your own...
forum.xda-developers.com
Traceback (most recent call last):
File "main.py", line 3, in <module>
from src.exploit import exploit
ImportError: No module named src.exploit
Для продолжения нажмите любую клавишу . . .

[ROM][UNOFFICIAL][Phoenix][11] OctaviOS 2.8

{
"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"
}
OctaviOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. OctaviOS is a reborn of pie based PearlOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH :
Ask to get your bootloader unlocked first! - t.me/NokiaX7
(All your data including the one in internal storage will be removed, so proceed with a caution! Or a backup )
MAKE SURE TO BE ON THE LATEST FIRMWARE/UPDATE BEFORE FLASHING
Also download vbmeta.img
Use the following command in fastboot to boot TWRP-
Code:
fastboot erase system
fastboot erase userdata
fastboot erase vendor
fastboot erase boot
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash boot twrp.img
*Now hold down the Vol+ button and Power button* while at the same time you enter this command-
fastboot reboot
*When the phone vibrates or androidone screen comes for 1-2 sec, leave the buttons*
After phone boots to TWRP, enter the password if encrypted.
Transfer boot.img to phone and flash it to both slots
Flash Magisk(optional)
Format Data
Reboot
:DOWNLOAD ROM
:DOWNLOAD TWRP
-Lineage OS
-AOSP
-Superior OS
-Pixel Experience
-Extended UI
-Havoc OS
-CrDroid ROM
-Fluid OS
@zskynet_09 for trees and help
@sei for testing
Bugs
All incl. banking apps working rest you tell
OctaviOS Source
Kernel Source
OctaviOS Telegram Group
Nokia 8.1/X7 Support Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS​
OctaviOS for Nokia 8.1/X7
Device: PNX_sprout of your device
Maintainer: DS1884
Build Type: Unofficial
Kernel Source: Prebuilt
ROM OS Version: 11.0
ROM Kernel: Linux 4.19
ROM Firmware Required: Must be on Latest Firmware
Based On: AOSP
Version Information
Status: Stable
SELinux Status: Enforced
Release Date: 2021-09-02
Changelog-
===== 13.08.2021 =====
- initial build
===== 02.09.2021 =====
- Notch cut-out fixed
- Added Google Camera by default(gapps required to open else, snap is present too)
- Fixed battery drain
- Modified tree for more stability

[ROM][A12] Awaken OS v2.4 [8T/9R] [02/22]

{
"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"
}
AOSP based ROM with minimal customizations.
​Installation:
- Download ROM zip file.
- Download recovery.img from downloads page and flash:
Code:
fastboot reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot recovery
- Reboot to recovery (command above)
- Format data if coming from different ROM
- ADB sideload zip file in recovery
- Reboot
OR
- Download ROM zip file and extract payload.bin
- Use a payload dumper to extract imgs from payload.bin file
- Now, run these commands from the folder with the extracted imgs and with fastboot:
Code:
fastboot reboot bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot - (NOTE: enter recovery and format data if coming from different ROM then continue in fastboot)
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash system_ext system_ext.img
fastboot flash odm odm.img
fastboot flash vendor vendor.img
fastboot reboot
Downloads:
- https://sourceforge.net/projects/azoll-8t-projects/files/Awaken-OS-12/
Sources/Groups:
- Telegram Support Group: @Azollr Projects/Support OP8T (9R)
- Awaken OS Announcements: @AwakenOSNews
- ROM Source - https://github.com/Project-Awaken
- Kernel Source - https://github.com/azoller1/kernel_sm8250
New build, 02/17 (Version 2.4). No need to wipe data.
Changes:
- Added alert slider UI
- Fix center clock padding
- Switched to DaxUI Dolby (OP8 apk)
- Switched to illusionX kernel
- Cleaned up old overlays in DT
- Better BurnIn for AOD (if this even works..)
- Other small changes, unimportant
New Update, 2/22 (v2.4). Clean flash ok. Sideloading should work in future updates following this one.
Feb 22nd
- Update newer Dolby/DaxUI, added APK
- Better statusbar padding
- Fix adb sideloading for future updates (hopefully)
- Added more DeviceExtras, No limit for edge touch
- Latest upstream linux 4.19.230
Does this rom have the hold the back button to kill current application?
rockysready said:
Does this rom have the hold the back button to kill current application?
Click to expand...
Click to collapse
This must be an extremely important feature for you...

Categories

Resources