I own an MTK6735 phone with locked bootloader running Android Lollipop 5.1 64-bit.
I have access to the original rom and I am able to edit system files by mounting system.img in linux, make changes, rebuild and finally flash the new system with mtk flash tool. I was able to add opengapps to my phone by extracting it and putting everything in the correct folders manually. I have however had no such luck with superSU. I tried putting the "su" and "supolicy" binary in both bin and xbin and adding libsupol.so to lib and lib64 folders.
I would greatly appreciate it if anyone can point me in the right direction.
Related
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting
Flashing Issues | Will not pass Android Logo
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
RockyCaballero said:
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
Click to expand...
Click to collapse
Here download this https://www.androidfilehost.com/?fid=24052804347782219
Extract and Add whatever directories/folders you want inside the system folder and flash. The script just extracts the system folder as a whole so as long as you make the correct folders, file names, directories etc it'll flash everything to the right spot.
Delete the jar file out of system/framework/ tho since it's a 5.1.1 jar file I did
Much obliged sir, worked perfectly. I'm sure it was the coding. [emoji2]
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
Hello guys!
I have Lenovo Tab 3 [TB3-850M], unfortuantely I am trying to deodex the ROM but both methods in SuperR Kitchen failed.
1st Method using oat2dex: It fails and not fully deodex the ROM and gives a list of failed files [look at pictures]
2nd Method using baksmali/smali: It says it "succeeded" but it doesn't as when flashing the ROM it is unbootable as I got (While deodexing) Java Exception error that it couldn't find classes.dex in all the ROM files!
Please I tried all Marshmallow deodexers available on XDA but nothing seems to work, the most about-successful attempt was with SuperR oat2dex and Fulmics Deodexer but I got com.android.phone has stopped working message error loop and other apps such as Maps and Keyboard.
Thanks in advance!
P.S: If you want the system.img.ext4 and boot.img I will upload them on request as my internet is not that fast and you most probably need one from me because the one online doesn't seem to extract [I made mine by flashing the unextractable system.img using SP Flash Tool and make System Image Backup using TWRP and copied it to my PC]
Regards!
Troubleshooting
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
addas4 said:
What Kitchen version?
1.1.5.9
What environment are you running the kitchen in (OS, 32/64-bit, cygwin, Bash on Windows, etc.)?
Bash on Windows x64
What device are you working on (make/model)?
Lenovo Tab 3 LTE TB3-850M arm64
What was the source you started from (system.img, system.ext4.tar, rom.zip, etc.)
system.img.ext4 from TWRP Backup
What Android version?
Marshmallow 6.0
What perm method (set_perm, set_metadata, sparse_dat, raw_img)?
set_metadata
What did you do after extracting and before building?
Didn't mess with the files before and after building/extracting, just used the commands on SuperR and flashed the finished zip file to the tablet.
Were there errors on the screen if you scroll up in the terminal?
Mentioned the errors on the first post
Send a recovery.log after flashing if you have problems flashing the ROM.
No need because TWRP flash successfully
Send a link that does not require registration to the files you started with (nandroid, system.img, boot.img, etc)
http://www.mediafire.com/file/r2p6hos5k73f161/TB3-850M-System.7z
Use the support option in the Misc Tools menu and attach the support.zip to your post.
I am not sure but looks like SuperR isn't making the support.zip, I will upload the project files instead (I think both are the same)
Click to expand...
Click to collapse
I can't do anything about this. You would need to create an issue on the smali/baksmali github repo. Once it is fixed there, I can compile new jar files and update them in the kitchen. Check your deodex log for the smali/baksmali errors you will need to post when you create the issue/s