Related
Hello Viewers! I am Rohan Taneja, here with completely re-written guide to Port MTK65xx Roms.
I had left MTK development since a year and I finally got another MTK device to carry with it again.
{
"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"
}
So, Many Of You May be MTK Device User than you are at right place to fill your device with many awesome roms!
Note: Android ONE devices (MT6582 SoC) use Google's device tree, meaning they differ on everything with all the other MediaTek devices (even the ones with the same SoC , MT6582), as per @superdragonpt told us
Requirements:
A MTK powered device
USB Cable
Usable Brains :cyclops:
Knowledge about Flashing & Taking Logs :angel:
Stock Firmware (from manufacturer) & Port Firmware (matching specification of your device)
Custom Recovery installed on device
Porting Tips
Choose Custom ROM from a device matching same resolution to reduce App Size related bugs
This Guide Applies to
MT6577 to MT6577, vice-versa
MT6589 to MT6589, vice-versa
MT6572 to MT6572, vice-versa
MT6582 to MT6582, vice-versa
Note: Try it at your own risk, and don't complaint any developer or XDA if any mishap takes place. :good:
TUTORIAL:Starting with the tutorial, I request you to follow every single step written below to prevent any kind of problem in flashing and causing bootloop. I also dare you to take a nandroid backup of your current rom you are using.
Get. Set. Go.
Step 1 : Patching System Folder for the port patch.First of all make a folder named "Port_Patch" and setup all the folder as shown in the images below.
Now, in Port_Patch make system folder in which make folders, "bin" "etc" "lib" "usr" "vendor" "xbin" (without ")
In folder "bin" copy pq & vold from your stock rom
In folder "etc" copy "bluetooth" "firmware" "wifi" "apns-conf.xml" "vold.fstab" "vold.fstab.nand"
In folder "lib" copy files as shown in the image
In folder "usr" copy usr/keylayout/Generic.kl
In folder "vendor" all the files
In folder "xbin" copy "libmnlp_mt662x" (x - '0' or '8') from stock
System has been patched, copy this /system to patch the /system of port ROM.
Step 2: Patching the boot.img of the port rom.This is bit tricky but can be done easily.
So, first of download this little tool, to unpack & repack your boot.img - MTKbootimg.zip - tested on Windows 7 & above platform
Extract the Tool and you will get two folders named "stock" & "port"
Copy boot.img's respectively from stock rom in "stock" folder & from port rom to "port"
Unpack both boot.img repectively and they may look like this.
From stock copy "kernel" to port folder and just replace it.
Now, repack it, new file named "boot-new.img" will be generated.
Copy "boot-new.img" to port Rom Folder.
Delete existing "boot.img" and rename "boot-new.img" to "boot.img"
Now, your boot.img is patched, proceed to last step.
Step 3: Modifying updater-script to install ROM accordingly.
So, it's the last step before flashing the rom. Now lets fix it.
First, you have to know your device mount points, that can be tracked using MTKDroid Tool or check them in stock rom updater-script.
I have my flashable stock rom so I will get mount points from it.
As show in the image, my stock updater have different mount point for system & data while port have different.
Now, replace "mmcblk0pX" (X - no. for the mount) from stock to port as designated for the partition.
Now Save the updater-script.
Finally, the ROM is ready to flashed.
Step 4: Compressing & Flashing the ROM.
Now, the rom is ready to be packed and flashed.
Simply get to the main directory with META-INF, system, boot.img, etc files.
Select all the files and compress them to zip. Select the compression ratio as you want.
After compressing copy the ROM into root of sdcard
Enter Custom Recovery, wipe data & Cache
Flash the ROM.zip wait till it completes.
Wait till it boots, or else take log using ADB logcat. (Hint: If LED light blinks, the rom is booting)
FOR Fixes Proceed to next post and find out the way to tackle and fix the bugs.
Fixing ROM issues
Finally Ported a Custom ROM. Now, time to kill out some bugs.
Its all about making the build stable for personal as well as others to use it.
Leave the files if not there in your System
Let's get started:
Bootloop? :crying:
Replace following files(from stock to port):
Code:
[LIST]
[*]libandroid_runtime.so
[*]libandroid_servers.so
[*]libmedia_jni.so
[*]libsync.so
[*]If possible try modifying framework.jar "\smali\com\android\server" (copy from stock)
[/LIST]
Camera Not Working?
Replace following files(from stock to port):
Code:
[HIDE][LIST]
[*]lib3a.so
[*]liba3m.so
[*]libacdk.so
[*]libaudioflinger.so
[*]libc.so
[*]libcam.camadapter.so
[*]libcam.campipe.so
[*]libcam.camshot.so
[*]libcam.client.so
[*]libcam.paramsmgr.so
[*]libcam.utils.so
[*]libcam_camera_exif.so
[*]libcamalgo.so
[*]libcamdrv.so
[*]libcamera_client.so
[*]libcamera_jni_eglfence.so
[*]libcamera_metadata.so
[*]libcameracustom.so
[*]libcameraservice.so
[*]libgn_camera_feature.so
[*]libexif
[*]libfeatureio.so
[*]libfrsdk.so
[*]libft.so
[*]libgcomm_jni.so
[*]libgoggles_clientvision.so
[*]libgui.so
[*]libimageio.so
[*]libja3m.so
[*]libjni_mosaic.so
[/LIST]
Thanks To [I]Shikar A[/I][/HIDE]
[B]Init.rc Fix:[/B]
[HIDE]Init.rc(present in the ramdisk of boot.img), find for code #Camera in stock boot.img. Copy it and replace from stock init.rc and replace in the port init.rc
[IMG]http://s27.postimg.org/4ucj34cwj/initrc_cam.png[/IMG][/HIDE]
Wlan not working properly?
Code:
Check wlan.chip in stock like:
[HIDE][IMG]http://s30.postimg.org/myaya0sxt/Untitled.png[/IMG]
fmradio.driver.chip=x (if mt6620 then x=1, if mt6628 then x=3)
Change the above codes accordingly in updater-script
Replace the version in port from the one in stock[/HIDE]
(Replace from stock to port)
libbluetooth_mtk.so
libbluetoothem_mtk.so
GPS, unstable or not working?
(Replace from stock to port)
Code:
xbin/libmnlp
Media Player problem?
(Replace from stock to port)
Code:
libdpframework.so
libcodecvdrv.so
Sensors not working properly?
(Replace from stock to port)
Code:
libsensorservice.so
SD Card not working or mounting?
Code:
In the framework-res.apk of your port, replace /res/xml/storage_list.xml from stock one.
USB not mounting your device?
Code:
Unpack your boot.img replace init.usb.rc from ramdisk by stock boot.img init.usb.rc
This tutorial worked for porting MIUI, Baidu, Vibe UI, LeWa OS, AOSP based rom from different device to my MT6589 of same hardware.
Credits:
Special Thanks to @yuweng (for starting his main MTK porting thread and his great works)
XDA-Developers being one of the best place for Android Development
Other Developers for helping in fixing most the issues.
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
iel0000 said:
just wanna ask..is it ok if i dont copy the srec folder cause i cant find it..also yhe meta-inf folder as i only have the system.img of my base rom
Click to expand...
Click to collapse
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
A N D Y said:
If You Don't Have "srec" folder no need to worry but for system.img you need to extract the img by ext4 method:
http://forum.xda-developers.com/showthread.php?t=2285831
Click to expand...
Click to collapse
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
iel0000 said:
how about theses files?
CERT.RSA
CERT.SF
MANIFEST.MF
i dont have them cause i dont have a flashable stock rom..
Click to expand...
Click to collapse
Don't Worry Try The one in the Ported Rom!
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
xjammetx said:
it worked!
i ported an miui from newman n1, the ics 4.0.4 with no bugs to my cherry mobile blaze / Ming Ren A2 clone.
btw, this is not a dual sim display miui, i need to go to settings anytime i wan to use the other sim.
anyone who knows where to get a dual sim display miui?
Click to expand...
Click to collapse
what boot.img did you use? stock from cherry mobile?
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
iel0000 said:
cant also find these
com.google.android.media.effects.jar
com.google.android.media.effects.xml
sorry for the noob questions..i just want to port a rom to my device as we dont have developers
Click to expand...
Click to collapse
Those Files You Can't Find In port just leave that!
A N D Y said:
Don't Try boot.img(Kernel) from the port rom or you'll brick your device!
Click to expand...
Click to collapse
can i use stock boot.img from my phone?or do i have to modify it?
Very nice thread, for beginners that want to learn
tried porting miui v5 base on jb 4.1.2
always stock on boot animation
iel0000 said:
can i use stock boot.img from my phone?or do i have to modify it?
Click to expand...
Click to collapse
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
iel0000 said:
what boot.img did you use? stock from cherry mobile?
Click to expand...
Click to collapse
Yep. Dont worry, ill upload it sometime.
A N D Y said:
You Can Use Stock BOOT.IMG or try changing the ramdisk with stock from the port kernel!
Tool: http://d-h.st/BVz
Click to expand...
Click to collapse
how to use the tool?
How to from STOCK
iel0000 said:
how to use the tool?
Click to expand...
Click to collapse
Do you know procedure to Port a STOCK ROM(SP Flash tool format not a CWM) of X device to Y device?
Both are mostly same in specifications except the resolution.
I read in some threads that we can not port a rom from a device which has different resolution ?
Thanks in Advance
iel0000 said:
i give up porting miui to my phone and tried porting another rom from amoi n820..it boot but the home key is not working..i already used Generic.kl from my device stock rom but it still dont work can you help me plss?
edit : i finally got it working..thanks for the tut it really help me....
Click to expand...
Click to collapse
what phone do you have btw?
yo kumpare!
Hi everyone, I am a RMX2071 owner and I was experimenting with GSI images, I have installed the AOSP 10 GSI (AOSP 10.0 v222) Source: https://github.com/phhusson/treble_experimentations/releases/tag/v222
Seems like it works except for the fingerprint (it doesn't work) and the camera that could be better. I'm not a developer nor I'm familiar with Android modding. I have bricked my phone several times during the attempt. This is not an advice or guide, everything you do is at your own risk.
I had unlocked bootloader and TWRP (Source: https://forum.xda-developers.com/realme-x50-pro/how-to/recovery-lr-team-twrp-3-4-1b-0616-t4123353)
This is what I did:
I have downloaded the latest firmware for my device from realmeupdater (https://realmeupdater.com/)
It was an OZIP file, I have unpacked with this tool (https://github.com/bkerler/oppo_ozip_decrypt)
Now I have a zip file
I have downloaded a GSI .img image (I have tried many, the one listed is the one that works best for now)
I have used this tool (https://github.com/xpirt/img2sdat) to convert .img to three .dat files: system.new.dat, system.patch.dat, system.transfer.list
I have used this other tool (https://github.com/VarunSaiTeja/Brotli-Rom-Manager) to convert system.new.dat into system.new.dat.br
I have deleted this three files from the the official rom zip, using 7zip: system.new.dat.br, system.patch.dat, system.transfer.list
I have added to the official rom zip the files just created: system.new.dat.br, system.patch.dat, system.transfer.list
I have put the zip on a flash drive. I have booted in recovery, wiped everything, flashed the zip, closed AVB2.0 from advanced menu, booted into system.
There could be many bugs I have only tested for some hours, I'm sharing this because some expert could find a way to make fingerprint work, modify the top bar to accommodate the camera hole and find a better camera app.
I'm uploading the zip I have created, I'll post it soon.
Pic: https://mega.nz/file/8ApUXYBJ#kYBqwpDfMEF_MdxLCnTQCtITA8rV6YlENWCkkPzMM1E
link to the modified zip: https://mega.nz/file/gN5gjKTB#pkQHQotBhY7IocGZWj9iwwWEoTM9x5APSVYsTgH4Pak
You flash this gsi zip with twrp ?
I did try before to install GSIs on this phone without success, if thats it, ill try it and see what i can do
Just wondering again; What either in theory or practice prevents from using an Android 11 GSI with this phone?
I don't understand the Project Treble/GSI mechanism enough.
Shouldn't every device from Android 9 (shipped with, that is) able to run a stock android image? i.e. why would this not work - https://developer.android.com/topic/generic-system-image
Saitb said:
Pic: https://mega.nz/file/8ApUXYBJ#kYBqwpDfMEF_MdxLCnTQCtITA8rV6YlENWCkkPzMM1E
link to the modified zip: https://mega.nz/file/gN5gjKTB#pkQHQotBhY7IocGZWj9iwwWEoTM9x5APSVYsTgH4Pak
Click to expand...
Click to collapse
Any update?
after return x50 pro in service center they bring it broken. cán someone help me run unblock bootloader on android 11 , downgrade to android 10 with https://c.realme.com/in/post-details/1294219896854413312
in only work for android 10. i find reverse engineer maybe hacker can change it to work in android https://bgzashtita.es/android/Downloads.rar it is reverse engineer that need to be made work for abdroid 11.
here my friend yestarday call realme and put livestream on youtube. realme lie it is for indian
here photos:
Jordi Ba
https://bgzashtita.es/android/photo/IMG2...035605.jpg
https://bgzashtita.es/android/photo/IMG2...040043.jpg
https://bgzashtita.es/android/photo/IMG2...040100.jpg
https://bgzashtita.es/android/photo/IMG2...040300.jpg
https://bgzashtita.es/android/photo/IMG2...052200.jpg
https://bgzashtita.es/android/photo/IMG2...052208.jpg
https://bgzashtita.es/android/photo/IMG2...052223.jpg
https://bgzashtita.es/android/photo/IMG2...052244.jpg
HI EVERYONE!
I want to flash new rom for my phone (Wiko View Max). But it isn't support twrp or cwm. Is there any way that I can flash my new rom for my phone?
Besides, I also wanna convert my file rom: .xz (.img.xz) to .zip file.
That it's.
Thanks for reading this!
thailinh.bui said:
Besides, I also wanna convert my file rom: .xz (.img.xz) to .zip file.
Click to expand...
Click to collapse
It exists free-of-charge online converters.
jwoegerbauer said:
It exists free-of-charge online converters.
Click to expand...
Click to collapse
but my file is over 900 mb =))
You may try this tool:
GitHub - jamflux/SUR: Simple Unpack & Repack Tool - Kitchen for Windows supporting Android 10
Simple Unpack & Repack Tool - Kitchen for Windows supporting Android 10 - GitHub - jamflux/SUR: Simple Unpack & Repack Tool - Kitchen for Windows supporting Android 10
github.com
Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?
If Android's Linux kernel is version 5.10+ you can try to root device's Android at your own via
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
xXx yYy said:
If Android's Linux kernel is version 5.10+ you can try to root device's Android at your own via
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
If you read my post you would see the kernel version.
{
"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"
}
Moxiipc said:
Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?
Click to expand...
Click to collapse
Moxiipc said:
Hello,
Theres no Samsung Galaxy A14 5G forum to post this in since it's somewhat a new phone. I have the SM-A146U One UI 5.0 Android 13, baseband ver A146USQU1AVL2
Kernel version 4.19.191-25583387-abA146USQU1AVL2 #1 Sun Dec 4 16:04 KST 2022
SE Enforcing SEPF_SM-A146U_12_0001
Sun Dec 4 16:15:21 2022
Service Provider Software Version SAOMC_SM-A146U_OYN_CHA_13_0011 CHA/CHA/CHA
Security Software Version
ASKS v5.8 release 20221121
ADP v3.0 release 20191001
SMR Nov-2022 Release 1
Android Security Patch level
November 1st 2022
Is there a root avaliable for this phone & has anyone sucessfully done it?
Click to expand...
Click to collapse
device galaxy a146p 5G
Download firmware update + ODIN(new method) from:
SamMobile - Your source for all Samsung news
SamMobile.com is the leading source for the latest Samsung news, firmware, product reviews, tutorials, tips, opinions, polls, and podcasts.
www.sammobile.com
"A146PXXU1AWAA_A146POJM1AWB1.....zip"
Then extract ... to five md5 files
Rename the file :
AP_...................OS13.tar.md5 "5.5 Gb"
To
AP_...................OS13.tar
Then i made image by :
Magisk [25.2].apk
Rename the extension .img to .tar
Finally flash this file using ODIN
Additional important steps like : OEM unlock ... bootloader ....
check page :
Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs
Galaxy A14 SM-A145P 4g and SM-A146P 5g Custom Kernels Kernel source code https://github.com/physwizz?tab=repositories NOTE: TWRPs in posts 3, 4 & 5
forum.xda-developers.com
lmrdy said:
device galaxy a146p 5G
Download firmware update + ODIN(new method) from:
SamMobile - Your source for all Samsung news
SamMobile.com is the leading source for the latest Samsung news, firmware, product reviews, tutorials, tips, opinions, polls, and podcasts.
www.sammobile.com
"A146PXXU1AWAA_A146POJM1AWB1.....zip"
Then extract ... to five md5 files
Rename the file :
AP_...................OS13.tar.md5 "5.5 Gb"
To
AP_...................OS13.tar
Then i made image by :
Magisk [25.2].apk
Rename the extension .img to .tar
Finally flash this file using ODIN
Additional important steps like : OEM unlock ... bootloader ....
check page :
Galaxy A14 (SM-A145 and SM-A146) Custom Kernels and TWRPs
Galaxy A14 SM-A145P 4g and SM-A146P 5g Custom Kernels Kernel source code https://github.com/physwizz?tab=repositories NOTE: TWRPs in posts 3, 4 & 5
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for this I will look into it & this works for 146U?
Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..
exnfox said:
Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..
Click to expand...
Click to collapse
I'm exactly on the same situation. I just could get a MTK rom (scatter rom) that flashes only the preloader (after that, sp flash tool keeps saying me "status_partiton_not_found 0xc0040006"), But despite it flashes successfully the given preloader, the phone wont get alive (not even want to enter into download mode). You can get your own scatter files, by using android utility (tab Android>Firmware utils, option "Extract samsung rom". You just need to have available an unzipped unencrypted Odin rom) the issue is that generated scatter supposedly belongs to a MT6853 instead of a MT6833, but changing all references of 6853, to 6833, it works, but as i say you, just enough to flash the preloader. If I get more advances, i will say you. But if you can to unbrick your phone before mines, please tell me how.
Camilo Gil said:
I'm exactly on the same situation. I just could get a MTK rom (scatter rom) that flashes only the preloader (after that, sp flash tool keeps saying me "status_partiton_not_found 0xc0040006"), But despite it flashes successfully the given preloader, the phone wont get alive (not even want to enter into download mode). You can get your own scatter files, by using android utility (tab Android>Firmware utils, option "Extract samsung rom". You just need to have available an unzipped unencrypted Odin rom) the issue is that generated scatter supposedly belongs to a MT6853 instead of a MT6833, but changing all references of 6853, to 6833, it works, but as i say you, just enough to flash the preloader. If I get more advances, i will say you. But if you can to unbrick your phone before mines, please tell me how.
Click to expand...
Click to collapse
yes i will let you know however ive tried many things including what you mentioned... i even went as far as paying 5 dollars to download a dead boot repair file from some site all it was just the firmware extracted like with mtk utliity... i wonder whats going on here. with the scatter file saying its mt6853 when the phones chipset is mt6833 and how do we flash it when we try to just change the value in notepad but it still fails everything except preloader?
preloader_s96902aa1.bin
preloader.img
im thinking the bin might be something differnt than whats suppose to be on the preloader partition? idk still expirmenting
exnfox said:
Does anyone by any chance have a scatterfile for this device? or preloader.bin ? i was on A146USQU1AWA7 before i completly messed up by using metkutility (android utility) now stuck on it only showing as mediatek usb port or mediatek da agent or mediatek preloader in device manager... ive tried various things to restore it but get errors when trying to use sp flash tool..
Click to expand...
Click to collapse
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.
mvikrant97 said:
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.
Click to expand...
Click to collapse
Okay want me to pm you my teamviewer Id?
exnfox said:
yes i will let you know however ive tried many things including what you mentioned... i even went as far as paying 5 dollars to download a dead boot repair file from some site all it was just the firmware extracted like with mtk utliity... i wonder whats going on here. with the scatter file saying its mt6853 when the phones chipset is mt6833 and how do we flash it when we try to just change the value in notepad but it still fails everything except preloader?
preloader_s96902aa1.bin
preloader.img
im thinking the bin might be something differnt than whats suppose to be on the preloader partition? idk still expirmenting
Click to expand...
Click to collapse
My friend, I also found this site that assures to have available for download, a SM-A146U scatter rom. The issue (at least to me), is that it charges for its download (and you have to sign up to this site). So I'll share you the link, and if you decide to invest on that download, please test it and, if you can bring back to life your Samsung, please share it (or at least its scatter file). Have a good luck with it.
SM-A146U Scatter Firmware
Camilo Gil said:
My friend, I also found this site that assures to have available for download, a SM-A146U scatter rom. The issue (at least to me), is that it charges for its download (and you have to sign up to this site). So I'll share you the link, and if you decide to invest on that download, please test it and, if you can bring back to life your Samsung, please share it (or at least its scatter file). Have a good luck with it.
SM-A146U Scatter Firmware
Click to expand...
Click to collapse
No need to pay anyone. We can make our own file.
exnfox said:
Okay want me to pm you my teamviewer Id?
Click to expand...
Click to collapse
Hey there,
Yes please PM me your ID. I will available in an hour from now.
mvikrant97 said:
I want you guys to conduct an experiment with me in flashing your device.
The phone has Mediatek MT6833 or Dimensity 700.
I wil use different set of tools to have it fixed for you.
Let me know if we can do that. I will use Anydesk or Teamviewer to do it and then if your device is fixed we can make a tutorial to help out others.
Click to expand...
Click to collapse
I have the file already the scatter doesn’t work so nevermind my initial request for that
exnfox said:
I have the file already the scatter doesn’t work so nevermind my initial request for that
Click to expand...
Click to collapse
I can make it work
mvikrant97 said:
I can make it work
Click to expand...
Click to collapse
I sent you my details
I also written to android utility's developer exposing the issue, to see if it's an android utility's issue or if i'm doing something wrong. I think is more probably is an issue of that program, and I cannot blame to the developer, because according to as i know, this phone's model is very recent; so i don't think it has yet many compatibility with many current softwares, including this one.
So, based on this hypothesis, also for that i think i informed to the developer, to he can fix that issue, on an upgrade of his program (which is currently on 108 version)
As aditional info, his webpage is https://www.androidutility.com/
Another thing that I knew by experimentation was, that even on Brom mode, the device won't let downgrade its firmware. I tried with an earlier samsung firmware, turned into scatter firmware; and sp flash tool showed me this warning: "status_sec_violate_anti_rollback 0xc0020021" that supposedly means that the device is rejecting the loaded firmware by being an old one.
Hi everyone,
I'm currently having trouble finding the device tree blob (.dtb) file on my Motorola phone running Android 12. I've tried unpacking the boot image file using various tools, but I haven't been able to locate the .dtb file.
Here are the steps I've taken so far:
I've rooted my phone and have access to all system files.
I've unpacked the boot image using the Android Image Kitchen and other tools, but I can't seem to find the .dtb file.
I've checked the "firmware" and "by-name" folders, but I couldn't find the .dtb file there either.
I've even tried using the dtc (Device Tree Compiler) utility to convert the device tree blob to a human-readable text file, but the resulting file was empty.
I'm at a loss as to what to do next. I need the .dtb file to make some modifications to the device tree information, but I can't seem to find it anywhere.
Has anyone else experienced this issue with a Motorola phone running Android 12? Does anyone know where the .dtb file might be located, or have any suggestions for other tools or techniques I could try?
Thanks in advanced for any help or advice you can provide!
afaik separate dtbo partition
alecxs said:
afaik separate dtbo partition
Click to expand...
Click to collapse
Isn't dtbo just an overlay?
@FiniteCode post the boot image and I'll check it for DTB.
I'm really sorry but i don't get what you guys wanna say, Actually it's my first time developing rom so you see...
Renate said:
Isn't dtbo just an overlay?
@FiniteCode post the boot image and I'll check it for DTB.
Click to expand...
Click to collapse
Thank you a lot for your support!
Thank you everyone saw your answers put them to ChatGPT understood some New Concepts and Voila! Thank you a lot everyone.... Special Thanks to @alecxs.7285913 and @renate.4474482
FiniteCode said:
Thank you everyone saw your answers put them to ChatGPT understood some New Concepts and Voila! Thank you a lot everyone.... Special Thanks to @alecxs.7285913 and @renate.4474482
Click to expand...
Click to collapse
Hmmm...
That's an Android header version 4 which only has a kernel and a ramdisk.
See: https://source.android.com/docs/core/architecture/bootloader/boot-image-header#header-v4
There appears to be no DTB tacked onto the kernel.
Also weird, the ramdisk is CPIO, but they didn't even bother to gzip it.
That dtbo has three DTBs in it, preceeded by that new 128 byte header.
It appears to all be overlays. I don't know much about that.
Code:
000000 Android header
000080 Header
0000b8 / {
0000c0 [email protected] {
0000d8 target-path = "/";
0000e8 __overlay__ {
Edit: If you want the kallsysms (using my tools):
Code:
C:\>imgutil /x boot.img payload
C:\>kallsyms /b8 payload boot.sym
Renate said:
Hmmm...
That's an Android header version 4 which only has a kernel and a ramdisk.
See: https://source.android.com/docs/core/architecture/bootloader/boot-image-header#header-v4
There appears to be no DTB tacked onto the kernel.
Also weird, the ramdisk is CPIO, but they didn't even bother to gzip it.
That dtbo has three DTBs in it, preceeded by that new 128 byte header.
It appears to all be overlays. I don't know much about that.
Code:
000000 Android header
000080 Header
0000b8 / {
0000c0 [email protected] {
0000d8 target-path = "/";
0000e8 __overlay__ {
Edit: If you want the kallsysms (using my tools):
Code:
C:\>imgutil /x boot.img payload
C:\>kallsyms /b8 payload boot.sym
Click to expand...
Click to collapse
yup... i tried to open the dtbo.img i came up with one error on every software/method i tried (bad magic number)
FiniteCode said:
yup... i tried to open the dtbo.img i came up with one error on every software/method i tried (bad magic number)
Click to expand...
Click to collapse
Lop off the first 128 (0x80) bytes (of the Android non-standard header) and you'll see the signature, bigend 0xd00dfeed.
There are three concatenated DTB(O)s.
Renate said:
Lop off the first 128 (0x80) bytes (of the Android non-standard header) and you'll see the signature, bigend 0xd00dfeed.
There are three concatenated DTB(O)s.
Click to expand...
Click to collapse
Could you attach them If possible. I've been having a hard time with getting them
@FiniteCode Oh, alright.
Renate said:
@FiniteCode Oh, alright.
Click to expand...
Click to collapse
Thank you so much can't explain my happiness like seriously thank you a lot
FiniteCode said:
Thank you so much can't explain my happiness like seriously thank you a lot
Click to expand...
Click to collapse
Don't get too excited. Each of those dtbo's are only ~100k.
A real dtb is more like 300k and upwards.
Moreover, those three are all variants of each other, they are 75%+ the same.
And since they are all actually overlays we still don't know where the base dtb is.
Edit: Oh, I forgot that I had posted my dtbview.exe (in the sig).
If you do Windows it can dump dtb & dtbo (also wacky Android header).
Code:
C:\>dtbview dtbo.img > big.txt
Some new devices with header version 4 has more in the vendor_boot.img like kernel-dt so that not in the boot.img (only kernel).
But I made attempt to extract dtbo.img & dtb. Not know if help.
UPD
Okay. Again my friend @lopestom updated me on Header V4 information.
I used the correct tools on Linux and now it seems to be much better than before. Well it looks like you have a Mediatek phone.
Attached pictures "dddd".png and unziped_dtbo.zip
Thank you all for help I'll try if this works in my custom rom
FiniteCode said:
Thank you all for help I'll try if this works in my custom rom
Click to expand...
Click to collapse
Or else, the last resort might be contacting Motorola which I don't think should help out, I don't have any hopes from Motorola...
FiniteCode said:
Or else, the last resort might be contacting Motorola which I don't think should help out, I don't have any hopes from Motorola...
Click to expand...
Click to collapse
I not search in total but has very dts and dtc files.
GitHub - AbzRaider/kernel_moto_vicky: Kernel Tree for MediaTek MT6789 Based Motorola G72 ( Vicky )
Kernel Tree for MediaTek MT6789 Based Motorola G72 ( Vicky ) - GitHub - AbzRaider/kernel_moto_vicky: Kernel Tree for MediaTek MT6789 Based Motorola G72 ( Vicky )
github.com
GitHub - theh0riz0n/android_kernel_motorola_vicky: Kernel sources for Motorola G72 DS XT2255-1
Kernel sources for Motorola G72 DS XT2255-1. Contribute to theh0riz0n/android_kernel_motorola_vicky development by creating an account on GitHub.
github.com
Kernel sources for Motorola G72 DS XT2255-1
Using which tools were you guys able to extract the boot.img I'm unable to do that actually I need to extract the ramdisk and kernel please do attach if you can
AIK is the only tool I use. maybe you have separate vendor_boot partition