Hello, everyone. Before guide this, I am not a English speaker. so if I incorrected grammars, please comment.
So first, we need twrp. (please backup before install.)
For install twrp, it needs bootloader unlock. (Enable OEM unlock and power off your device. And hold volume + and volume -, then connect cable to pc or laptop.
If done, The device shows warning for download mode, hold volume +. then the device tries reset, just wait. and when device turned on, set up and check OEM Unlock.
next, power off the device again. and enter the download mode same way.) Now let's go to twrp installation.
1. download twrp for galaxy a53 5G. I used this thread. https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a53-5g-exynos.4467443/
Thank you afaneh92.
Also please download pixel gsi img. I used this thread. https://forum.xda-developers.com/t/gsi-pixel-experience-plus-aosp-based-android-12-1-12l.4532373/
Thank you AleksB.46.
And insert twrp file in AP and vbmeta file in USERDATA.
2. start and if it shows pass, holding press volume + and power button. then, enters to twrp. (If stuck in setup connection, try other cables or enter again to download mode.)
3. download GSI img of pixel experience plus. (I recommand ab version.) also download a53x kernel from twrp link.
4. move they to device.
5. Go to Advanced tab and enter to terminal, type: "multidisabler" . (Without quotation mark.) When log says "finished", go to home.
6. Tap to wipe and do format data to typing "YES".
7. Flash the img for system file image.
8. Flash magisk.
9. Flash A53x kernel.
10. Reboot system.
11. It's end, Enjoy!
Thanks Again to afaneh92 and Alike.46
*Your Knox warranty is will void if try this! Think again before install.
*Issues : Adaptive brightness Not work. 5G not work (Kernel not supports yet.) NFC card mode not working (But read works well.) Gcam not work (Can solve via Gcam GO.) 120hz not work basically (You can solve via dynamic refresh rate module or smarthertz.
{
"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"
}
goodmoning1101 said:
Всем привет. Прежде чем вести это, я не говорю по-английски. поэтому, если я исправил грамматику, пожалуйста, прокомментируйте.
Итак, во-первых, нам нужен twrp. (пожалуйста, выполните резервную регистрацию перед установкой.)
Для установки twrp нужна разблокировка загрузчика. (Включите OEM-разблокировку и выключите устройство. Уберите громкость + и громкость -, затем подключите кабель к ПК или ноутбуку.
Если все сделано, то обнаруживаются признаки предупреждения о заражении, у понижения громкости +. затем устройство добывается с броском, просто подождите. и когда устройство включено, настройте и проверьте разблокировку OEM.
затем снова выключите устройство. и таким же образом войдите в режим загрузки.) Теперь приступим к установке twrp.
1. скачать twrp для галакси а53 5г. Я использую эту нить. https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a53-5g-exynos.4467443/
Спасибо afaneh92.
Также загрузите пиксель gsi img. Я использую эту нить. https://forum.xda-developers.com/t/gsi-pixel-experience-plus-aosp-based-android-12-1-12l.4532373/
Спасибо АлексБ.46.
Вставьте файл twrp в AP и файл vbmeta в USERDATA.
2. запустите и если он покажет проход, размер настройки + и параметр питания. потом входит в twrp. (Если застрял в установочном подключении, попробуйте другие кабели или снова войдите в режим загрузки.)
3. Загрузите GSI img или Pixel Experience Plus. (Я рекомендую версию ab.) Также загрузите ядро a53x по ссылке twrp.
4. переместите их на устройство.
5. Перейдите на вкладку «Дополнительно» и войдите в терминал, нажмите «multidisabler». (Без кавычек.) Когда в журнале написано «готово», идите домой.
6. Нажмите, чтобы стереть и отформатировать данные, набрав «ДА».
7. Прошить img системного файла.
8. Флэш магиск.
9. Прошить ядра A53x.
10. Перезагрузите систему.
11. Это конец, наслаждайтесь!
Еще раз спасибо afaneh92 и AleksB.46
Click to expand...
Click to collapse
Will not work if the person has updated their phone to Android 13! Need PE from A13!
https://github.com/ponces/treble_build_pe/релизы
any bugs?
Gadji12344 said:
Will not work if the person has updated their phone to Android 13! Need PE from A13!
https://github.com/ponces/treble_build_pe/релизы
Click to expand...
Click to collapse
I did update one ui 5, but even android 13 works install pixel experience 12.
The system image isn't affect by Android version.
Ferchurito said:
any bugs?
Click to expand...
Click to collapse
I found two bugs. They are face unlock can't cognize face. and Can't use dolby atmos. If install module, It keeps setting max volume even sounds off.
goodmoning1101 said:
I found two bugs. They are face unlock can't cognize face. and Can't use dolby atmos. If install module, It keeps setting max volume even sounds off.
Click to expand...
Click to collapse
But if I dont use the dolby atmos module, does the sound work fine?
And does wifi and 4g/5g work?
Ferchurito said:
But if I dont use the dolby atmos module, does the sound work fine?
And does wifi and 4g/5g work?
Click to expand...
Click to collapse
5G not work cause of the kernel not added the feature yet. But 4G works well. even mobile data, call, message. (But message and call works little of bit slower. So, not that problem to use.)And sound works well. But kinda not as good as like Dolby Atmos.
Related
PATCHED BOOT.IMG for MERLIN by VD171
For what do I need it ?
At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom recovery.
Keep attention, it is not pre-rooted.
Works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Firmware Versions:
- (Engineering) AL2522-Merlin-V039-Q-0513
- (Engineering) AL2522-Merlin-V044-Q-0920
- V12.5.1.0.RJOMIXM
- V12.0.1.0.RJOMIXM
- V12.0.8.0.QJOMIXM
- V12.0.7.0.QJOMIXM
- V12.0.6.0.QJOMIXM
- V12.0.5.0.QJOMIXM
- V12.0.4.0.QJOMIXM
- (India) V12.0.4.0.QJOINXM
- V11.0.5.0.QJOMIXM
- V11.0.4.0.QJOMIXM
How to flash it?
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot_vd171.img
MD5 hashes:
AL2522-Merlin-V039-Q-0513: a04fdd922f5e5dd49c7772e75defa06e
AL2522-Merlin-V044-Q-0920: 9239a1fc45ba5be6ea83527eeddb2728
V12.5.1.0.RJOMIXM: e172cfa9c96c5f829170db671baadba3
V12.0.1.0.RJOMIXM: a446c9d747247c4ce8016da83cbdc932
V12.0.8.0.QJOMIXM: dd3e581fc2ee1e2ef7b56a843bdd4d9d
V12.0.7.0.QJOMIXM: 884ea8c8798c594db58359796fa14f30
V12.0.6.0.QJOMIXM: 146f1254604bf9b57335eae1cd60dd03
V12.0.5.0.QJOMIXM: 3a46568b0e3d2aafc607a8d2add1bf40
V12.0.4.0.QJOMIXM: be2f0c391b22dcc9ed8d4dbbb7900cd8
(India) V12.0.4.0.QJOINXM: 416a03273045e616d67f76e3b3c50807
V11.0.5.0.QJOMIXM: 262ec3ba40c53add7f651188920618b8
V11.0.4.0.QJOMIXM: 48b568eddcd1a888fe0286beb2ed4f4a
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
my devices is lost fastboot, please help me?
p233 said:
my devices is lost fastboot, please help me?
Click to expand...
Click to collapse
What is happening exactly?
Does your device keep in a black frozen screen?
VD171 said:
What is happening exactly?
Does your device keep in a black frozen screen?
Click to expand...
Click to collapse
Yes, my device keep in a black frozen screen. Because, when i use SPFT, I have tick Auto Format, and brick.
p233 said:
Yes, my device keep in a black frozen screen. Because, when i use SPFT, I have tick Auto Format, and brick.
Click to expand...
Click to collapse
So, probably you need to re-flash the whole rom again.
help me!
p233 said:
help me!
Click to expand...
Click to collapse
Just flash the whole original stock rom using sp flash tool and you will have your device back.
VD171 said:
Just flash the whole original stock rom using sp flash tool and you will have your device back.
Click to expand...
Click to collapse
I tried but the SPFT got an error
p233 said:
I tried but the SPFT got an error
Click to expand...
Click to collapse
Attach the screenshot, please.
[QUOTE = "VD171, bài: 84544637, thành viên: 4699873"]
Vui lòng đính kèm ảnh chụp màn hình.
[/TRÍCH DẪN]
View attachment 5230409
p233 said:
[QUOTE = "VD171, bài: 84544637, thành viên: 4699873"]
Vui lòng đính kèm ảnh chụp màn hình.
[/TRÍCH DẪN]
View attachment 5230409
Click to expand...
Click to collapse
I'd never heard of this error.
Did the sp tool send the DA file before this error??
Are you using the same scatter file used before?
You can skip the usage of the auth file.
If you are using any of the DA filles attached on XDA by me, the auth file is not required.
And:
{
"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"
}
p233 said:
And:
Click to expand...
Click to collapse
MTK_AllInOne_DA.bin does NOT work for MERLIN devices.
I changed your file, and still there is the error, I have tried bypassing the authorization account authentication but with no success.
Các bác sĩ cho biết thêm:
p233 said:
Tôi đã thay đổi tệp của bạn và vẫn còn lỗi, tôi đã thử bỏ qua các quyền kiểm tra tài khoản nhưng không thành công.
Các bác sĩ cho biết thêm:View attachment 5230425
Click to expand...
Click to collapse
Please, use english my dear son of Ganesh.
Reboot your device (or just try to boot) before to try to flash again.
It will refresh the download mode.
VD171 said:
Please, use english my dear son of Ganesh.
Reboot your device (or just try to boot) before to try to flash again.
It will refresh the download mode.
Click to expand...
Click to collapse
no change, still the same errors.
Do I need to rent an authorized account?
p233 said:
no change, still the same errors.
Do I need to rent an authorized account?
Click to expand...
Click to collapse
No, it is nomore required.
But, if you are on miui V12.0.5.0 or higher already installed, you need to bypass the authorization and flash using EDL mode.
Read this: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229679/
{
"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"
}
Rec-Boot Bot
What's is Rec-Boot Bot?
• Rec-Boot Bot is a powerful shell script that can unpack,repack boot & recovery images,Can automatically port boot & Recovery images, can flash boot & recovery & everything(;
Stable version 3.0 released!
Hey i made a tool for porting,managing,flashing,unpacking,repacking Boot & Recovery.
What it can do?
•Can Unpack Recovery & boot imagqtes
•Can repack recovery & boot images
•Can automatically port boot images
•Can automatically port TWRP
•Can port LOS based boot images
•Can flash recovery & boot images
•All in one.
My Little creature yet powerful enough to do these work in only 9 seconds.
• Rec-boot Bot supports 64/32bit. and must be android 5.0 or higher But can port for all the latest android recovery.
•Auto port normal boot images:
It can automatically port normal boot images super quickly in just 9 seconds:3
•LOS based boot images:
It can automatically port LOS based boot images automatically.
• Auto port TWRP 3.0.2-7:
It can port all the TWRP recoveries(also latest)
> TWRP supports all chipset
Snapdragon,Mediatek,Spreadtrum,exynos,broadcom & kirin.
•Manually Port section
| Support all SOC,Use your Brain|
jk
in manual port menu you can
>UNPACK BOOT
>REPACK BOOT
>UNPACK RECOVERY
>REPACK RECOVERY
•FLASH TOOL
>Supports flash boot & recovery
>Supports 32bit &64bit
How to install it?
•if you have TWRP Recovery, you can easily install this with it. Download the zip & flash.
If you don't TWRP recovery,you can install it manually with Mixplorer. Extract my zip file, copy the the folder name Xenon54 from the bin folder & paste it to system/bin & set permission to 751(rwx r-x--x), now copy the file from data/local (Xenon54) & paste it to data/local & set the permission to 755(rwx r-x r-x). Then reboot your phone:V
How to Use it?
•Open any termial app( i suggest terminal emulator)
•type "su" & click enter
•Then type "Xenon54" & click enter.
A preview will be popped up.
•Go to data/local,there you'll see two folders stock & port. Put your stock recovery/boot in it, in port folder, put your port recovery/boot.
Bugs: Nothing, if you find any,Lemme know
Rec-Boot Bot preview:
First Section:
Auto Port section:
Manual Port section:
Flash Tool section:
Downloads:
Version 1.0
Version 2.0
Version 3.0
3.0 is fully stable & has nice UI. I recommend V3.0
You can make my day if you use it & get benefitted
Thanks for reading,This is XenonTheInertG,See you around
Great tool
Rana78160 said:
Great tool
Click to expand...
Click to collapse
Ah,Thanks bro
Mahin bro,
Can i use this tool without root permission?
Я не знаю английский учить можно мне 61 через почту не могу общаться она не переводить язык .вот в такой я ситуации.Извените,за отнятоеу Вас время.Очень сожалею.
I sent my tablet back to china for basically a reflash of zui 13..as we don't have access to it..still
It came back with the serial number still wrong (even though I said that was one of the issues)
I know there's a post from user van about the solution but I'm worried that way is by loading up the zui 12.5 IMG and changing a file..has anyone done this method whilst using the latest firmware..thankyou
russy23 said:
I sent my tablet back to china for basically a reflash of zui 13..as we don't have access to it..still
It came back with the serial number still wrong (even though I said that was one of the issues)
I know there's a post from user van about the solution but I'm worried that way is by loading up the zui 12.5 IMG and changing a file..has anyone done this method whilst using the latest firmware..thankyou
Click to expand...
Click to collapse
hey russy,
i updated to latest firmware zui13 and corrected my serial number. yes you can restore SN even with old stock zui 12.5.
step done here :
1) i flashed to latest zui 13
2) i loaded qfil with stock zui 12.5
3) reboot to edl by adb reboot edl and connect to pc
4) go to tools --> partition manager
5) go to fppartition and read data/partition
6) go to %AppData%\Qualcomm\<port number of your QDLoader port>\something-like-current-date.bin
7) edit with hex reader or HxD
8) insert serial number under decoded text, read from purchased box or back of your tab
9) save file and remember the file location
10) go to qfil and load image by using the saved/modified serial number
11) reboot to fastboot to see the result or go to tab setting status
credit to @van40 for method to restore serial number
{
"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"
}
gunalarix8 said:
hey russy,
i updated to latest firmware zui13 and corrected my serial number. yes you can restore SN even with old stock zui 12.5.
step done here :
1) i flashed to latest zui 13
2) i loaded qfil with stock zui 12.5
3) reboot to edl by adb reboot edl and connect to pc
4) go to tools --> partition manager
5) go to fppartition and read data/partition
6) go to %AppData%\Qualcomm\<port number of your QDLoader port>\something-like-current-date.bin
7) edit with hex reader or HxD
8) insert serial number under decoded text, read from purchased box or back of your tab
9) save file and remember the file location
10) go to qfil and load image by using the saved/modified serial number
11) reboot to fastboot to see the result or go to tab setting status
credit to @van40 for method to restore serial number
View attachment 5529427
Click to expand...
Click to collapse
Thankyou will give it a go later..was avoiding doing it as didn't want to somehow brick it .but now you have said it's ok I'll do it..thanks
gunalarix8 said:
hey russy,
i updated to latest firmware zui13 and corrected my serial number. yes you can restore SN even with old stock zui 12.5.
step done here :
1) i flashed to latest zui 13
2) i loaded qfil with stock zui 12.5
3) reboot to edl by adb reboot edl and connect to pc
4) go to tools --> partition manager
5) go to fppartition and read data/partition
6) go to %AppData%\Qualcomm\<port number of your QDLoader port>\something-like-current-date.bin
7) edit with hex reader or HxD
8) insert serial number under decoded text, read from purchased box or back of your tab
9) save file and remember the file location
10) go to qfil and load image by using the saved/modified serial number
11) reboot to fastboot to see the result or go to tab setting status
credit to @van40 for method to restore serial number
View attachment 5529427
Click to expand...
Click to collapse
Nice work, thanks for sharing.
for some reason i get a black warning saying the system cannot find the specified file
gunalarix8 said:
hey russy,
i updated to latest firmware zui13 and corrected my serial number. yes you can restore SN even with old stock zui 12.5.
step done here :
1) i flashed to latest zui 13
2) i loaded qfil with stock zui 12.5
3) reboot to edl by adb reboot edl and connect to pc
4) go to tools --> partition manager
5) go to fppartition and read data/partition
6) go to %AppData%\Qualcomm\<port number of your QDLoader port>\something-like-current-date.bin
7) edit with hex reader or HxD
8) insert serial number under decoded text, read from purchased box or back of your tab
9) save file and remember the file location
10) go to qfil and load image by using the saved/modified serial number
11) reboot to fastboot to see the result or go to tab setting status
credit to @van40 for method to restore serial number
View attachment 5529427
Click to expand...
Click to collapse
Thankyou very much, i have recovered the serial, must admit got nervous doing it but all went well after the sahara fail went away, thanks..was on very latest firmware and it worked fine
Hi, friend.
I lost my serial number to 0123456789ABCDEF
In the file I changed it to my own bootloader, but nothing has changed in
and it hasn’t changed either. I have bootloader 60 and it’s 0
Maybe somehow you can restore the backup QCN through Partition Manager Qfil?
Passattikk said:
Hi, friend.
I lost my serial number to 0123456789ABCDEF
In the file I changed it to my own bootloader, but nothing has changed in
and it hasn’t changed either. I have bootloader 60 and it’s 0
Click to expand...
Click to collapse
as far as i know this only works for the j716f model, sorry
russy23 said:
насколько я знаю, это работает только для модели j716f, извините
Click to expand...
Click to collapse
но как насчет j606f ?
можно ли поменять серийник?
или восстановить резервную копию QCN?
в режиме 9008?
Passattikk said:
но как насчет j606f ?
можно ли поменять серийник?
Click to expand...
Click to collapse
I have no idea sorry
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* Syberia Team not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications.
*/
Read the whole OP! Be respectful to each other and don't ask for ETAs, it's considered as being rude!
Syberia Project (aka Syberia OS) is a custom ROM for OnePlus9 that implements various features. This project was designed by our "Syberia Team" from scratch based on AOSP source code with some CAF fixes and improvements. Our team: @DennySPB, @blinoff82, @alexxxdev. Also many thanks to our designer @rlshukhov for logos, wallpapers and bootanimations.
If you like our work you can buy us a cup of coffee or a glass of beer
Here
Code:
VoLTE, VoWiFi
LineageOS LiveDisplay
Game Space
Pitchblack theme
Monet tunables
App Lock feature
Dt2s on statusbar and lockscreen option
Advanced restart
QS columns count configurable
reTicker feature
Edge lights
Quick QS pulldown
Lockscreen quick unlock
Volume key cursor control
Prevent accidental wake-up
Statusbar battery customization
Wake up on charge
Pulse flash on incoming call
In-call vibration options
Screen-off animations
Statusbar items switches
Statusbar network traffic
Three finger swipe to screenshot
Power button torch
Double tap gestures
Extended powermenu
Playback control
Volume rocker wake
VoLTE and VoWiFi icons support
Icon pack support
Fonts support
...and some other usefull features
Settings and features will be gradually added.
SyberiaOS ROM DownloadsOnePlus9 firmwareOnePlus9 Recovery bootMagisk Downloads
First time clean installation:
Code:
- Unlocked bootloader is required
- Backup all your important files to PC!
- Download ROM, vendor_boot, boot, dtbo images from Downlonad section (optional Magisk, Firmware)
- Reboot into bootloader
- Flash vendor_boot.img, boot.img, dtbo.img via fastboot:
fastboot flash boot boot.img
fastboot flash vendor_boot.img
fastboot flash dtbo.img
- Reboot into recovery
- Select 'apply update' via sideload
- Flash ROM via ADB sideload:
adb sideload
- Flash ROM syberia_lemonade-v6.x-xxxxxxxx-xxx.zip
- Wipe Data (format)
- If Magisk or firmware install is not needed - reboot system,
otherwise reboot into recovery again (for slot swapping)
- Select apply update
- flash magisk or firmware zip files via adb sideload
- Reboot system and enjoy.
Updating:
Code:
Manual install from sideload:
- Reboot into recovery
- Flash ROM
- Reboot into system if magisk is not needed, otherwise reboot into recovery again
- Flash Magisk zip
- Reboot into system
OTA update:
- Install OTA update and reboot into system
OTA update with Magisk:
- Install update (DO NOT REBOOT at this stage), flash magisk into inactive slot from magisk manager
- Reboot
Code:
- - You tell me only with logcat (screenshots)
Attention! We are not responsible for the operability of your device if you use third-party kernel, Xposed Framework or unverified Magisk modules.
Official website Syberia Project GithubSyberia Project GerritSyberia Project Kernel SourceOfficial Telegram GroupAnnouncements Telegram GroupDevelopment Telegram Group
Code:
- LineageOS
- AOSPA (aka Paranoid Android)
- crDroid Android
- Evolution X
- PixelExperience
- Nitrogen Project
Kernel notes:
- WALT was completely removed
- Scheduler upstreamed to 5.15 kernel
- Implemented Google's Pixel 6 scheduler based on tracepoints hooks
- Backported DAMON process reclaim
- Kernel alway upstreamed up to latest linux tags
- Added SSG Samsung multiqueue io scheduler (default)
- Lots of other backports
Device notes:
- QTI PowerHal was replaced by Google's libperfmrg
- Adapted PowerHints for lahaina
- Enabled ADPF (Android dynamic performace)
reserved
Greetings. Unexpected meeting after Mi5)))
valerii12 said:
Greetings. Unexpected meeting after Mi5)))
Click to expand...
Click to collapse
LoL))) It's nice to see that someone is still with us from the time of Mi5.
does it have quick settings tiles for;
adaptive brightness &
sync.
thanks in advance
Excited to try this.
Phoenix47 said:
Firmware is included in rom ?
Click to expand...
Click to collapse
It's included in the instructions . Hey developers, will be testing this rom today, as it feature list looks exciting. Thanks for your work .
Can i install on oos 11 fireware with avoiding vendor,dtdo img .....just recovery and side load does it work ?
I'm currently on PEX 13, do i need to flash firmware files?
BadAssBeach772 said:
I'm currently on PEX 13, do i need to flash firmware files?
Click to expand...
Click to collapse
I wanted to ask that too.
@DennySPB
does it support T-mobile OP 9?
@DuongNguyenVN
Dude don't quote the entire Op please. Read the directions. There is firmware included to flash separately if need be. My assumption is if your not on C-63 you need to be and it also has to be on both slots. Then flash dtbo,boot,vendor. Reboot recovery. Side load build
mattie_49 said:
Dude don't quote the entire Op please. Read the directions. There is firmware included to flash separately if need be. My assumption is if your not on C-63 you need to be and it also has to be on both slots. Then flash dtbo,boot,vendor. Reboot recovery. Side load build
Click to expand...
Click to collapse
thank you
I'm getting fastboot error cannot determine image filename for vendor_boot img after flashing boot please help me guys I'm on oos c.63 version
Vijayakumari said:
Я получаю сообщение об ошибке fastboot, не могу определить имя файла изображения для vendor_boot img после прошивки загрузки, пожалуйста, помогите мне, ребята, у меня версия oos c.63
Click to expand...
Click to collapse
у меня была такая же проблема. Я решил это, введя команды правильно.
[КОД] fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img[/CODE]
Vijayakumari said:
Я получаю сообщение об ошибке fastboot, не могу определить имя файла изображения для vendor_boot img после прошивки загрузки, пожалуйста, помогите мне, ребята, у меня версия oos c.63
Click to expand...
Click to collapse
I had the same problem. I solved this by entering the commands correctly.
Code:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
I want to warn gamers playing COD this accidental device reboots
Just flashed really great work superb rom of op9 but I don't like gcam doesn't support aux lens very disappointing rest of them is fine
imv_9 said:
I had the same problem. I solved this by entering the commands correctly.
Code:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
Click to expand...
Click to collapse
Bro give me magisk module aux lens support I tried everything but won't work ......
Hello everyone, it's me again!
Today I will share more Android 5.1.1 Lollipop ROM for Galaxy Y
This is not real Android 5.1.1 guys, it's still Android 4.4.4, I'm fake like 99%, ROM will be available in CH Play without installing more Gapp, Have Lollipop Theme like real Android 5.1.1 and have Bootanimation and last The same ROM will have a lollipop-style lock screen and a built-in keyboard, if you like you can install labankey
Link ROM : https://1drv.ms/f/s!Ap7WCG32b-IAg3OriUMxZPYzURgO
How to Upgrade ROM :
- download all the files in the link
- copy to an external memory card
- then go to settings
- select phone info
- press the build number several times
(if you want to use SIM)
- then turn off the power
- Hold down the Home button, Power button and the volume up key
(if it's on the "Samsung" logo, release the 3 keys, To control recovery, use the (+) button to go up, (-) to go down and the Home button to select )
- Select wipe data and press Yes
- then select Wipe cache
- choose apply form SD Card
- Select the CWM file and press Yes
( if you want to access more files )
- When entering CWM, select Apply form SDCard
- choose file form sd card
- select the TWRP 3.0.2.1 file and click Yes
- After selecting, select Advanced
- choose reboot recovery
(when entering TWRP, everyone can use that recovery to make it easy to use)
- Once you have entered TWRP, select Wipe
- drag the blue bar to the right
- exit and select data
- check all cells
- exit select install
- press the Android 5.1.1 file and drag the blue bar to the right
- when it says done, just press Reboot system and enjoy
Note: I am not responsible for uploading the wrong model or uploading the wrong way
Wished everyone success
ROM 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"
}
Sources: {
Base ROM: https://forum.xda-developers.com/t/...mized-rom-for-totoro-gt-s5360-s5360l.3438809/
Kernel: https://github.com/thedeadfish59/samurai-kernel
@nnt1709 Once again, you are required to post the source used to build your kernel. Please do this immediately.
If you have any questions about this requirement, please read the XDA GPL Policy.
If you continue to ignore these warnings, your ROMs will be taken down.
V0latyle said:
@nnt1709 Một lần nữa, bạn được yêu cầu đăng nguồn được sử dụng để xây dựng nhân của mình. Hãy làm điều này ngay lập tức.
Nếu bạn có bất kỳ câu hỏi nào về yêu cầu này, vui lòng đọc Chính sách XDA GPL .
Nếu bạn tiếp tục bỏ qua những cảnh báo này, ROM của bạn sẽ bị gỡ xuống.
Click to expand...
Click to collapse
I have finished recording the kernel source, not sure if it is the right kernel source?
nnt1709 said:
I have finished recording the kernel source, not sure if it is the right kernel source?
Click to expand...
Click to collapse
As long as that is the kernel included with this ROM, yes.