All MT6577 android phones are 'STILL' plagued by low internal memory issue...
{
"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"
}
Credits to X-Dron from russia, now you'll have 2GB of internal storage instead of 512MB with this mod ! :good:
I've included a google direct translated version for the help file, some sentence doesn't make sense but i'm sure you'll figure it out on how to use it...
X-Dron claim his mod is universal & it can be use on all MT6577... :good:
You can follow the original thread here...
Added on Oct 04, 2012 - SdCard Swap
What the f... , you have use up your 2GB Internal Memory & you can't install any more apps...
Credits to EMF, he found this hack & it is working well on my MT6577... :good:
Originally, this hack by 神族-bpok which install .smssecurity to app folder which is meant for V970 so attach copy here, i've deleted it so that it can be use on any MT6577 via cwmr...
Having said that, it is best that you copy your original vold.fstab before installing this hack so that, if anything were to go wrong, you can still revert it back to original state... Just open revert2ori.zip with 7zip but don't extract it, drag & drop your original vold.fstab into it & flash via cwmr... :good:
What this hack did is that it swap the mount points at vold.fstab...
Original
Code:
dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
It is also possible to manual edit vold.fstab as confirmed working by other thread...if it doesn't then power off, take out the battery, wait few sec then put it back & reboot...
If it still doesn't work, you can try manual edit & add 2 to vold.fstab.nand
Original
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard[COLOR="Blue"]2[/COLOR] /mnt/sdcard[COLOR="Blue"][B]2[/B][/COLOR] auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Some report that this works well with 32GB SdCard too ! But make sure to use minimum Class 4 & above...
Bravo to the original developer/ hacker...
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
--------------------------------------
Added on Dec 02, 2012 - INT2EXT on MT6575 / 77 for the extreme gamers !
Finally found a way to install 200 over games on my MT6577 & i'm sure it will work on MT6575 too... :fingers-crossed:
So here is the updated tut to do that... Works on ext 2, 3 or 4... :good:
As usual the credits, without these Master Shifu's sharing, this mod would not be here...
croniccorey
mastermind1024
KarmaToBurn
--------------------------------------
Added on Jan 03, 2013 - Data Repartition APK for MT6577
Full credits to jaydvn, he has found it, translated it & share with us this super easy to use app...
Refer to this post here onwards...
--------------------------------------
Added on Feb 25, 2013 - Operation to Support & Reward our MTK SoC Developers
Head up to here & show your support...
--------------------------------------
Added on June 26, 2013 - How to use your 64GB Micro SDXC for Android-powered smartphone that supports only up to 32GB
Found an interesting article here but i haven't try it b'cos i don't have a 64GB Micro SDXC...
Its in Russian so use Google Chrome built-in translations, it makes more sense... :laugh:
Its for people who already had a 64GB SDXC to try out, anyone care enough to report back whether it works... :fingers-crossed:
--------------------------------------
Added on Dec 12, 2013 - MT6589 MBR, EBR1, EBR2 explained
MT6589 MBR, EBR1, EBR2 are the least explained thanks to Master Shifu nightcraw for the detail explanations, i'm a complete zero when it comes to Hex calculations...
Original idea by JohnnyInBriz i've requested Master Shifu nightcraw to edit it so here it is, all formula already setup so you can resize cache, android system, usrdata, fat & it will let you know what to edit to the MBR & EBR....
Hopefully it will be useful to those DYI'er who wants to resize partition themselves & mod at your own risk... :laugh:
--------------------------------------
Added on Dec 25, 2013 - MoreApp.apk
This mod was shared at another forum but under constant spamming...
Not to waste a good mod by Master Shifu Michfood here is the link... :good:
WARNING : Make a backup first. This mod will shift all apps to sdcard ./android_secure & therefore freeing all internal space & CWMR/ TWRP does backup it too...
Wow another great guide here. I'll try and report back once it finish.
Hi yuweng
Nice trick, though not new to me. The reason I did not describe this in my thread is because in Settings->Storage, you can simply choose which SD card is used, internal or external. (internal one is called USB). No hacking of fstab needed
But I see soo many people doing this, or other tricks, I start to wonder: Maybe the settings->storage choice is only on Lenovo? Do you not have this on other MT657x phones? Or are people just looking passed the build in selection?
PS: your other tutorial, on retrieving a scatter file and recovery image from a phone, is really good. I will use that if I ever get a phone for which there is no ROM yet.
Wow,
Master Shifu cybermaus dropping by to my thread, really honor to have you here...
Haha, i'm one of those who like to keep all my games all at the phone & this is where this hack comes in... :good: So far that i've tried, even it is set to SD card, the internal memory will keep on decreasing, while with this sdswap hack, preferred install location set to Phone Storage(its swap now), i've installed more than 2GB games & internal storage stay the same size... :laugh: Kudos to the developers of android games, Wow, those recent games graphics are really amazing & some are really addictive too...
Learn that trick from Master Shifu bgcngm blogspot, discovered it can be use on MT6577 too, however its start address is offset for MT6577...
It's work!
I managed to successfully root my EASTCOM W5500 One X with this tutorial. But, 7z.exe needed to be updated to latest version (for my case, Windows 7 64bit). Other run well. Superuser reported working well. Adfree works as expected. So, I deleted all Chinese apps and make it feel stock.
Next step: create a custom rom for my device :fingers-crossed:
update (22/10/2012) : Error flashing zip file, back to kitchen..
But, 7z.exe needed to be updated to latest version (for my case, Windows 7 64bit).
update (22/10/2012) : Error flashing zip file, back to kitchen..
Click to expand...
Click to collapse
haha, been using x86 earlier b'cos of driver compatibility issue but now also lazy to upgrade...
Yeoh bro, for Android Kitchen to work on MT6577, you'll need 'curi ayam' patching...
There are so many MT6577 out there, to update edify_defs for all model is crazy...
After extraction at AK, go to ADVANCED OPTIONS -> Convert update-script or updater-script -> Convert update-script to updater-script (Edify)
Then go to AK -> tools\update_files folder, copy emmc-update-binary to WORKING folder \META-INF\com\google\android, delete existing copy & rename emmc-update-binary to update-binary
Open updater-script with Notepad++ & delete the 2nd & 3rd line & add the following to the 2nd line & save it...
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
Build ROM from working folder & Voila, you'll have Android Kitchen working on MT6577 & i believe it will work on MT6575 too... :fingers-crossed:
If you need to add apps/ games to WORKING folder /data/app then you will need the below...
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p5");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(0, 0, 0777, 0777, "/data");
format("ext4", "EMMC", "/dev/block/mmcblk0p3");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
AK will works with either system.img or system.ext4.tar but *.tar will take a longer time to decode symlink...
As usual, wipe data/ factory reset first before installing ur newly created update.zip...
Actually you don't need to format statement also at updater-script since you already manually done it...
Thanks for the guide but still got no time to continue the custom rom. Will update once I got time
Sent from my W5500 using xda premium
---------- Post added at 10:29 PM ---------- Previous post was at 09:48 PM ----------
cybermaus said:
Hi yuweng
Nice trick, though not new to me. The reason I did not describe this in my thread is because in Settings->Storage, you can simply choose which SD card is used, internal or external. (internal one is called USB). No hacking of fstab needed
But I see soo many people doing this, or other tricks, I start to wonder: Maybe the settings->storage choice is only on Lenovo? Do you not have this on other MT657x phones? Or are people just looking passed the build in selection?
PS: your other tutorial, on retrieving a scatter file and recovery image from a phone, is really good. I will use that if I ever get a phone for which there is no ROM yet.
Click to expand...
Click to collapse
I can confirm that this option is not working on my MTK6577 One X. tried few time, but still store on phone storage instead of sd card
yuweng said:
All MT6577 android phones are 'STILL' plagued by low internal memory issue...
Credits to X-Dron from russia, now you'll have 2GB of internal storage instead of 512MB with this mod ! :good:
I've included a google direct translated version for the help file, some sentence doesn't make sense but i'm sure you'll figure it out on how to use it...
X-Dron claim his mod is universal & it can be use on all MT6577... :good:
You can follow the original thread here...
Added on Oct 04, 2012 - SdCard Swap
What the f... , you have use up your 2GB Internal Memory & you can't install any more apps...
Credits to EMF, he found this hack & it is working well on my MT6577... :good:
Originally, this hack by 神族-bpok which install .smssecurity to app folder which is meant for V970 so attach copy here, i've deleted it so that it can be use on any MT6577 via cwmr...
Having said that, it is best that you copy your original vold.fstab before installing this hack so that, if anything were to go wrong, you can still revert it back to original state... Just open revert2ori.zip with 7zip but don't extract it, drag & drop your original vold.fstab into it & flash via cwmr... :good:
What this hack did is that it swap the mount points at vold.fstab...
Original
Code:
dev_mount sdcard /mnt/sdcard [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard /mnt/sdcard[COLOR="blue"]2[/COLOR] [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.0/mmc_host
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-sd.1/mmc_host
It is also possible to manual edit vold.fstab as confirmed working by other thread...if it doesn't then power off, take out the battery, wait few sec then put it back & reboot...
If it still doesn't work, you can try manual edit & add 2 to vold.fstab.nand
Original
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Hack
Code:
dev_mount sdcard[COLOR="Blue"]2[/COLOR] /mnt/sdcard[COLOR="Blue"][B]2[/B][/COLOR] auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-sd.1/mmc_host
Some report that this works well with 32GB SdCard too ! But make sure to use minimum Class 4 & above...
Bravo to the original developer/ hacker...
--------------------------------------
Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
awesome, i was looking for this tutorial, to repartition my umi x1 mtk6577 , thanks, but i don't want the sdcard swap, only want to delete emmc partition
so its only the first file needed to flash using cmw right? or i can edit the vold.fstab on my own rom
yuweng said:
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
Just to let you know...
I have a GooPhone Y5 .. and I have actually tried to flash my phone with the Zopo Z100 or Z200 (I don't remember) ..
The phone went dead.. BUT.. After installing the preloader driver for the Zopo device (just like a did for the GooPhone before first use of FlashTool) I was able to use FlashTool again.. and back on GooPhone ROM
@androidnyubi
Yes, just use the MTK6577_Data_Repartition.7z by X-Dron. However, found out lately, most users doesn't have factory ROM & they started modding this & that which is very dangerous... Use MTK Droid Tool by russian Master Shifu rua1 to backup your whole ROM with it... :good: There is an option there to create scatter.txt so you can revert it back when needed... :good:
@whitetigerdk
Wow, this is a good find... :good: it means MT6575/ 77 is 'unbrickable' after all...
thanks yuweng, this umi x1 actualy my 1st mtk based android, confusing which hack compatible with this chip hehe..
Sent from my HTC Desire V using xda app-developers app
Repartition APP for MT657x (Need root)
This app helps you have up to 3GB internal storage (Data Partition) <DOWNLOAD>
*Phone must me rooted.
*Run the app > Choose the size of data partition you want (I choosed 3GB ("Bộ nhớ 3GB, bỏ thẻ SD trong" in app's menu) because after swap sdcard, i feel internal SDcard is useless).
*Then Reboot to Recovery ("Khởi động máy vào Recovery" in menu).
*Once rebooted to Recovery> wipe data/factory reset.
*After reboot, you will have the size of data partition you want.
-Good luck!
-Sorry for my bad English!
-App's language is in Vietnamese
Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...
yuweng said:
Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...
Click to expand...
Click to collapse
Ok bro, i think this app does the same way with yours, just replace ebr1, i'll ask them to translate it to english then share after.
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
yuweng said:
Yeoh bro, i've unpack it & notice it is actually replacing the EBR1 & MBR...
i suggest that you get Sir.nguyenhaiduongbk or phi.long to translate it to English first before sharing it here as no one else will benefit from it... :laugh:
And please include an English Readme.txt on how to use it too...
Click to expand...
Click to collapse
Can i ask you one more question, i use android kitchen to make update.zip of rom, but after flash the zip file, my wifi can't be turned on, do you know it because of boot.img or updater-script?
Translated Repartition APP
I've translated Data Repartition Tool to English <DOWNLOAD>
Hope you enjoy it!
Yeoh Bro, did a full test & it is working great, thank you so much for sharing...
[Original Size] [500MB] [1GB] [2GB] [2.5GB] [3GB]
However, Factory Reset at TWRP show error but it works after reboot. CWMR Wipe Data/ Factory Reset no error...
jaydvn said:
Can i ask you one more question, i use android kitchen to make update.zip of rom, but after flash the zip file, my wifi can't be turned on, do you know it because of boot.img or updater-script?
Click to expand...
Click to collapse
That problem was solved by Master Shifu dsixda since version 2.14 b'cos of symlink problem, refer to Release Notes here...
Success bro thanks..
yuweng said:
[Added on Oct 17, 2012 WARNING : MEDIATEK SMART PHONE FLASH TOOL
i've seen far too many times that fellow xda member make this same mistake over & over again, including myself...
So pls pls people, don't use SP Flash Tool & download ROM not meant for your phone, it will brick it & there is no way to revive it back ! After you have download wrong PRELOADER, your phone will be completely dead, cannot power on, no charging, no recovery, no USB vcom detection & you can say
to it...
Here is the WARNING again :
NEVER DOWNLOAD ROM NOT MEANT FOR YOUR PHONE. IT WILL BRICK IT !
Click to expand...
Click to collapse
Does this mean that if I want to try a new ROM it is better to leave the original PRELOADER in its place or am I saying something stupid now....
I tried to find what exactly is the function of each part of the firmware but cannot find an easy to understand description.
I guess some of the parts of a ROM are very machine dependent and others are more general.
It would be nice if somebody could describe relations and dependencies of the different parts.
Luit
yuweng said:
Yeoh Bro, did a full test & it is working great, thank you so much for sharing...
[Original Size] [500MB] [1GB] [2GB] [2.5GB] [3GB]
However, Factory Reset at TWRP show error but it works after reboot. CWMR Wipe Data/ Factory Reset no error...
That problem was solved by Master Shifu dsixda since version 2.14 b'cos of symlink problem, refer to Release Notes here...
Click to expand...
Click to collapse
I've already updated kitchen to 2.18 but still no wifi after flash update.zip. my device's board is 'signal77_ics2', maybe I'll try to rename some files in edify_defs folder to make kitchen define my device. Thanks.
it doesnt sink in to me yet
could someone explain further.
i have
1gb rom internal mem
16gb internal sd
2gb external micro sd (the removable one)
what will happen to them?
i cannot figure out a way to open the phone to replace the external sd.
thank you!:good:
Related
This is just a relay thread but, please, full read it and then, if you dare, jump to the master one!
{
"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"
}
Doc_cheilvenerdi.org said:
Free Memory to > 1Gb!
How to Increase your Internal Memory Size with very low effort!
NOTICE: This method works both on Rooted and NOT Rooted Phones!
You simply need to meet three easy requirements:
Stock Firmware installed on the Phone (custom ROMS not supported ...They don't need to!)
A microSD with two primary formatted partitions inside (the former 'to FAT32' and the latter 'to EXT4' filesystems)
Ready to Flash to your Galaxy Mini via Odin
NOTICE: The following Black Box Howto is explained deep inside in post n. 2 and from post n. 52 to post 54!
...
Click to expand...
Click to collapse
Last Year, on December 18, I started the quoted thread for Galaxy Mini, showing a tweak useful to Increase the Internal Memory Size on Stock ROMs simply switching the data filesystem to the second partition of the microSD...
Benefits and disadvantages of this tweak are fully explained and discussed in the quoted Thread.
Question: Why I'm posting here, then?
Answer:
I received requests about tweaking the FIT boot images too...
I studied the FIT kernel vs Mini one and figured out that they are pretty equals (actually they full-match each other but only few stuffs related to post boot hardware detection)
I tried and made few images for FIT, which are shared in post n. 56 of the quoted thread, but - owning a Galaxy Mini - I was not able to test them...
...till now...
...
Angry about that and waiting for beta testers for them, I compared deep inside Galaxy Mini and Galaxy FIT...
Surprise: If I call them TWINS, the mistake is not so a mistake:
...At Kernel Layer they match each other...
...the bootloaders call the kernel at same memory address...
...boot sequences via ramdisk completely equal...
...system libraries are exactly the same...
...system software and leftovers too...
The only hardware differences don't really need to modify the boot sequence!
THAT'S ALL: I simply tested the FIT images on my Mini and they ends up and running...
THEY WORK!
What's Now?
I'll not repeat the Flashing procedure with Odin - you can read it on the quoted thread - but here are the FIT boot images actually modded and shared:
PDA=S5670DDKT3
PDA=S5670DXKPB
PDA=S5670DXKT4
PDA=S5670JPKQ7
PDA=S5670LUBKP6
PDA=S5670LUBKPI
PDA=S5670XWKTI
PDA=S5670XXKPQ
Your firmware is not listed? ...let me know!
Obviously you need Odin and Ops file ready for your phone model and not the Mini one...
- - -
Doc_cheilvenerdi.org said:
How does it Work:
Scenario 1:
I switch on the Phone, without a MicroSD slotted in or with a microSD with a single FAT32 partition (broken or damaged microSD also suite this scenario...); GingerBread boots as usual!
No Difference!
Scenario 2:
I switch on The Phone with a microSD slotted in (with the second partition formatted as EXT4 filesystem but still EMPTY); Ginger boots acting as if
/data
is completely moved outside to microSD but just WIPED (not true obviously, and the original /data is safe inside the phone), so it resettle it from beginning...
NOTICE:
...If your second partition is 1Gb wide...
...your new Internal Memory will be 1Gb wide...
Scenario 3:
I switch on the Phone with the second partition of the microsd (EXT4) up and running (already resettled up for use and with my userdata on it); Ginger simply boots with
/data
moved outside to microSD with your userdata there and tons of apps just installed from the market...
Click to expand...
Click to collapse
- - -
Doc_cheilvenerdi.org said:
NOTICES & ADVICES:
If I want to remove the microSD from the slot, FIRST I NEED TO SWITCH OFF THE PHONE!
When I install apps from the Market, Ginger Misunderstands the actual new Internal Memory SIZE and puts the apk files to External Storage anyway! I simply need to move them "to the phone" via "Settings menu" immediately after!
When I switch on the Phone without the microSD, I boot using the original /data inside the phone, actually loosing all the apps installed onto the external one untill next boot with SDcard; and, of course, loosing my sms stored there and others personal userdata too.
Unfortunately this boot image heavy conflicts with Link2SD (great app anyway!), so you must choose one: This Boot image or Link2SD... not both... sorry!
Click to expand...
Click to collapse
- - -
Don't You Like the boot image just installed and You want to revert without flashing the full firmware to the Phone?
Here are the original images ready for Odin:
PDA=S5670DDKT3
PDA=S5670DXKPB
PDA=S5670DXKT4
PDA=S5670JPKQ7
PDA=S5670LUBKP6
PDA=S5670LUBKPI
PDA=S5670XWKTI
PDA=S5670XXKPQ
Thread News!
Have you got an "unsigned update.zip capable recovery"?
Here a list of update.zip files ready to flash without Odin:
PDA=update-S5670JPKQ7.zip
PDA=update-S5670XWKTI.zip
I'm from Europe. I have installed S5670XXKPQ. Can something be done for this firmware?
Nice! Thank you, you made it for latin america version
Enviado desde mi GT-S5670L usando Tapatalk
New Image Added!
ZmisiS said:
I'm from Europe. I have installed S5670XXKPQ. Can something be done for this firmware?
Click to expand...
Click to collapse
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670XXKPQ (2.3.6)
Doc_cheilvenerdi.org said:
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670XXKPQ (2.3.6)
Click to expand...
Click to collapse
Thanks for this.
I forgot to mention that I have installed OC 844 MHz Kernel. Because it does not work for me. I have to reinstall and then try.
Don't work for me.
SD Make-up!
When you get true internal memory size even after tweak, something went wrong while making 2nd partition on SD...
You should first check How you made the second partition on your SD Card...
You can resize the first one (FAT32) or start from scratch (two new empty partitions); anyway, They both must be primary and the 2nd must be EXT4 newly formatted (mandatory).
If you feel you've done right, you could check what's happened with an app I just wrote to check the 2nd filesystem for errors. You can find it here; it's a Beta Version but fully working...
Read carefully the post and, eventually, give it a try.
P.S. It seems, otherwise, that you shoud partition your SD out of the phone (USB or MMC adapter needed). Actually Everybody who asked me for the same troubleshooting, solved it using Minitool Partition Wizard on Windows or GParted on Linux, BUT acting on the SD outside of the Phone!
P.S.2 No need to flash again! If the phone booted, the image is up and running fine...
I used USB, opened Mini Tool Partition Wizard, wiped all the SD, Apple, made a primary FAT32 partition, created a primary ext4 partition, Apple, waited till everything is over and that's it.
The problem remains the same.
Again flashed PDA S5670XXKPQ = (2.3.6) and same problem again.
apple style partition?
---------- Post added at 02:42 PM ---------- Previous post was at 02:42 PM ----------
MBR/GUID wont work?
Thanks! Gud work!
Doc_cheilvenerdi.org said:
When you get true internal memory size even after tweak, something went wrong while making 2nd partition on SD...
You should first check How you made the second partition on your SD Card...
You can resize the first one (FAT32) or start from scratch (two new empty partitions); anyway, They both must be primary and the 2nd must be EXT4 newly formatted (mandatory).
If you feel you've done right, you could check what's happened with an app I just wrote to check the 2nd filesystem for errors. You can find it here; it's a Beta Version but fully working...
Read carefully the post and, eventually, give it a try.
P.S. It seems, otherwise, that you shoud partition your SD out of the phone (USB or MMC adapter needed). Actually Everybody who asked me for the same troubleshooting, solved it using Minitool Partition Wizard on Windows or GParted on Linux, BUT acting on the SD outside of the Phone!
P.S.2 No need to flash again! If the phone booted, the image is up and running fine...
Click to expand...
Click to collapse
Now work. Thanks.
Doc_cheilvenerdi.org said:
This is just a relay thread but, please, full read it and then, if you dare, jump to the master one!
- - -
- - -
- - -
Click to expand...
Click to collapse
thnx for your thread..
Btw can u tell me wat lines or files should v add in boot.img to have this memory hack ..??
using G FIT
Everything shared!
amn_grg said:
... wat lines or files should v add in boot.img to have this memory hack ..??
Click to expand...
Click to collapse
It's all explained in post n. 2 and, deep inside, from post n. 52 to post 54 of the master thread referenced in the beginning.
There you can find links to scripts, source codes and binaries that I used...
...Everything you need to do it on your own!
i m from indonesia S5670DXKPB
Is this true?? Add more size my internal memory or......???
Sent from my GT-S5670 using XDA App
Added Image and Thanks!
NEW BOOT IMAGE ADDED!
Just added this boot.img (First Post for downloads):
S5670DXKPB (2.3.4)
CREDITS:
And many Thanks to Maleficus90 cool who helped me out, while testing SDcard's performance on LUBKP6 PDA boot image!
i m from romania S5670XWKQ(2.3.4)
spaga said:
i m from romania S5670XWKQ(2.3.4)
Click to expand...
Click to collapse
I think that you can use S5670XXKPQ (2.3.6) and S5670XWKT2 (2.3.6). It is for Europe.
S5670XXKPQ is official firmware. I checked on the KIES Samsung.
New images...
NEW BOOT IMAGES ADDED!
Just added this boot.img (First Post for downloads):
S5670DDKT3 (2.3.6)
i am using cyanogenmode 7.2 and my baseband version is ddkt2...so can i use ddkt3 boot.image?
Old Tool
Added on Mar 05, 2014
Updated CTR v2.2 for MTK devices with ubifs ONLY
And Thanks to dhinesh77 for countless beta-testing & most importantly, Master Shifu carliv for looking into those ubifs source code to make it work on MTK devices....
{
"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"
}
Download link here...
Solution to cannot see whole sdcard is here by Master Shifu himself, it is actually a new feature/ function... :laugh:
----------------------------------------------------------
Added on Jan 27, 2014
Updated CTR v2.2 Recovery for MT6575,15, 77, 17, 89, 82, 88, 92
MT6572 (ext4 only, ubifs not supported)
Pls support by donation or at least drop your thanks here to encourage Master Shifu for further development...
Download link here
----------------------------------------------------------
Added on June 02, 2014
New Porting Tool CTRv-1.4 for ext4 devices ONLY. . .
Known problems : Touch not working on some MTK devices . . .
Any bugs report here . . .
----------------------------------------------------------
Added on June 10, 2014
New AIO Porting Tool Easy Magic CTR v2.4 Installer for MTK for ALL MTK Cortex-A9/ A7 devices ONLY with either mtd, emmc, ubifs or custpack partition . . .
Any bugs report here . . .
Updates
Thanks to surfturtle for reporting . . .
Workaround : Use Manual mode & select 720x1024 that is the screen res for 720x1280 . . .
This is an AIO porting tool so go ahead & try the differrent res at Manual mode, the unpack/ repack feature, play around with it & you'll learn what is needed for porting custom recoveries . . .
----------------------------------------------------------
Added on June 17, 2014
Users using XP & 720x1280 MTK devices use this fix . . .
----------------------------------------------------------
Added on July 01, 2014
CTRv2.5 refer to here . . .
----------------------------------------------------------
Notice to annoying n00bs & newbies
Most of your questions are already answered on this thread so pls read it...
1) Either your MTK is still ro.secure=1 then use this method here then EXIT/ CLOSE it first then re-start the porting tool...
2) i've already put in alot of error checking to make sure this porting tool works, either the Auto or Manual port, it will leave behind Ported-CTR folder then manually install it via SPFT when it fail to auto install.... Most probably why it fail to install is b'cos you use SuperSu did you bother to look at your MTK device & grant access to Root Shell... There has been cases where the stock recovery is already corrupted then this tool will also port a corrupted CTR too. Re-install your stock 3e recovery.img & make sure you can boot into it then only use the porting tool again or just use the manual port... The differences is Auto will upload whatever recovery already at your device be it older CWM or TWRP & it will repack it with CTR ramdisk. While Manual will use whatever at your stock 3e -> factory_init.project.rc, meta_init.modem.rc, ueventd.rc & etc... Refer to this by Master Shifu carliv... :good: This tool has no log b'cos it is actually a simple copy & paste program, thats what it actually do.... :laugh:
3) Pls bear in mind that this porting tool has been downloaded by many & confirmed working BUT i can't guarantee that it will work flawlessly on your MTK device so continue trying & report back the solution if you found one...
4) This has been mentioned many times on this thread, if you really can't get it to work then don't just say your porting tool doesn't work...
Instead list out everything then it'll be easier to trouble-shoot
a) What OS you are using on the PC & your MTK...
b) Did you disable UAC & Anti-Virus on your PC
c) Did you execute the porting tool at C:\ drive if you're using XP else then at your Desktop READ what the porting tool says & it will ask you to wait then wait for it to continue without pressing the OK button...
As said many times, this porting tool uses Russian Master Shifu Michfood Repack Utils Huge Credits to him, it is actually DOS program with cygwin dll working at the back so all DOS limitation still applies such as it will ONLY operate properly when it is executed at the Desktop on latest OS... Tested working on XP to 8.1
As much info as possible then it'll be easy to identify where it goes wrong & did you bother to read 5 to 10 pages from the back then you would have know what is the latest story...
Last but not least, i didn't compile CTR so any features not working / bugs found pls report it here BUT again, read the whole thread first as most already answered at that thread...
Q&A
1) Touch not working, refer to here...
2) MTK Alcatel devices refer to here & here... Supported on CTRv2.4
3) All MTK devices supported except this...
4) Inverted screen solutions -> Compile your own
5) CTRv2.5
Nice one bro.....will be helpful for many.......!!:good:
Good to see you back......!
--------------------
P.S: Thinking of creating a Multi-tool for MTK6573.......what are features that can be added bro ??
Yo, Bala bro, been quite busy with work, until now only manage to finish this tut...
Yeah, i was thinking about that too, to mod dsixda's android kitchen just for MT6573 platform that includes Bruno Martins's unpack/ repack boot.img, unpack/ repack recovery & port it to CWMR like this tut, replace a2sd with data2ext or ad2sdx; only this two mod stable on MT6573 platform so far that i have tested...
actually did try but give up half way as my scripting skill is still at novice level...
did read it on some other forum that someone is actually doing that too but i never see it got release though...
Well i guess we need dsixda expertise to be able to do that but he is retired now...
Added on Sept 04, 2012 Info Update
Dark Tremor's a2sd/ Apps2sd works well on MT6573 platform after all...
i was using the last version 2.7.5.3 Beta 04 all this while & i always use a2sd datasd all the time & it FC all apps after a few weeks of using/ sometimes a few days even after a fresh install...
After all, DT_a2sd/ apps2sd is actually apps to sd & i always push it as data2sd...
Only until recently that i play with Android Kitchen, use it to extract my system.img & update it with its built-in Darktremor Apps2SD version 2.7.5.2, it works extremely well because 2.7.5.2 doesn't support a2sd datasd feature...
So guys, if you are using DT_a2sd beta 4, don't use the command a2sd data2sd instead use a2sd cachesd...
You can checkout my other post here
great tools and description
hello y2yu,
Glad you find it informative...
According to this site, there will be another 2 new cpu after MT6575/ MT6577... (use google chrome for translation)
This means MT6573 is 5 generation behind MT6588 & it is still unexploit with all info/ tools scattered all over the web...
Thats where i decided to compile all these info & put it here... :good:
Now that i check, i've bought my first mediatek back in 2008...( never knew it until i check it just now ) :silly: It has serve me well for almost 2 years in spite of dropping, a few times from 8 feet height when i was on a ladder & it still works ! It was the last drop that spoilt the mic & render it unuseful. It can still make & receive call to date but the other side can't hear what i say...
At that time, made in china phone was famous for its extra loud speaker/ ringtone but doesn't support android back then...
haha, enough of history, have you manage to port CWMR to your MT6573 ? In fact, i have manage to create a plugin for dsixda's Android Kitchen which can port CWMR to any MT6573 with a few copy & paste features just like Android Kitchen... :good:
Still testing it, may be you would like to be the first beta tester...
Thank you so much for this. I managed to "port" cwmr to my phone without going through the build hassle. Thanks also go to koush for the builder. I had downloaded the source but hadn't managed to completely set up my build environment as there are a couple of gotchas to iron out for ROM development.
Anyway, this serves as a good precursor to actually porting a custom recovery to new devices. Just one problem - cwmr does not recognise any of the hardware buttons for the select action. I can only scroll. The phone has 2 side buttons for volume control, 1 power button on top, and at the bottom on the home row there is a home button, the menu (these 2 also scroll, in stock recovery the home button selects), the previous, and the search. [1][2]
Do you happen to have any cure for this? Is there some place I could remap hardware buttons? One more thing. I made sure root shell access was configured but adb shell will not work (insufficient permissions). Also, adb devices, as is the case for stock recovery, will return question marks. Any idea?
edit: It is important to mention that the flashing had some errors:
Code:
/mnt/sdcard # flash_image recovery recovery.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: recovery successfully wrote block at 0x00000000
mtd: recovery successfully wrote block at 0x00020000
mtd: recovery successfully wrote block at 0x00040000
mtd: recovery successfully wrote block at 0x00060000
... <snip>
... <snip>
... <snip>
mtd: recovery successfully wrote block at 0x00420000
mtd: recovery successfully wrote block at 0x00000000
The flash of the stock recovery goes without any error.
[1] http://symphony-mobile.com/index.php?route=product/product&path=63&product_id=75
[2] http://www.tinno.com/en/productinfo.aspx?proid=128
u r most welcome, jason...
i think the button key map is actually built inside /sbin/recovery so there is nothing much you can do about it unless you build the whole recovery from sources & change it from there...
i do have feedback from fellow xda member that has the same problem flashing recovery with error however he reported back, all menu options at cwm works fine...why don't you use mobileuncle tools, its easier that way...found another flashing tool for ZTE, reported unknown image but it works fine on MT6573 platform too...
As for the adb shell at cwmr, it should work by default & if it doesn't then you have the check default.prop & make sure ro.secure=0 As for stock recovery, mine doesn't work at all...
i think after 6.0.0.3 version, ported cwmr has the camera button as enter key for MT6573 if you built it from koush builder...
yuweng said:
u r most welcome, jason...
i think the button key map is actually built inside /sbin/recovery so there is nothing much you can do about it unless you build the whole recovery from sources & change it from there...
i do have feedback from fellow xda member that has the same problem flashing recovery with error however he reported back, all menu options at cwm works fine...why don't you use mobileuncle tools, its easier that way...found another flashing tool for ZTE, reported unknown image but it works fine on MT6573 platform too...
As for the adb shell at cwmr, it should work by default & if it doesn't then you have the check default.prop & make sure ro.secure=0 As for stock recovery, mine doesn't work at all...
i think after 6.0.0.3 version, ported cwmr has the camera button as enter key for MT6573 if you built it from koush builder...
Click to expand...
Click to collapse
Crap, then I have to dig through the sources really hard. This phone has no camera button.
If I'm not wrong the last time I checked "mobileuncletools" uses flash_image. Either that, or nandwrite, or failing that, dd. Coming from a Linux and UNIX background I'm more comfortable with the simpler underlying commands rather than a complex front-end wrapper around those commands. NAND images have some peculiarities so we kinda have to deal with it I guess.
I had triple-checked that ro.secure != 1 I think this is probably a hardware issue where during recovery there is no bridging interface exposed.
Anyway a couple of other things related to the documentation side of this:
* Why not just upload your own recovery.fstab to the builder instead of editing it later?
* Changing the fstab is only needed for those who have an ext-sd, i.e. a second partition for the memory card
* The bin/ folder is empty, and the lib/ folder only contains the ext2 module, so if above not needed, this is also not needed
So in the end, I think we can simply advocate use of the builder as-is. What do you think of putting up a list/database of MTK phones and some details? Like rootable or not, cwmr available or not, etc. I think RootzWiki would be a good place for that?
AFAIK, most readers at xda are non-registered, only when they are stuck somewhere or they really needed help then only they'll register & start posting; that is including me !
You can see my other post where it is nearing to 300 over downloads while the MTK phones list feedback from users is less than 10 !
AFAIK, all MT6573 are root-able & all needs data2sd mod. There are so many apps & games at google play, MT6573's 256 or 512MB internal memory gets filled up pretty fast !
On adb shell, did you have all the three adb files (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll) & on linux, i use ./adb shell to get it to work...
yuweng said:
AFAIK, most readers at xda are non-registered, only when they are stuck somewhere or they really needed help then only they'll register & start posting; that is including me !
Click to expand...
Click to collapse
Very true.
AFAIK, all MT6573 are root-able & all needs data2sd mod. There are so many apps & games at google play, MT6573's 256 or 512MB internal memory gets filled up pretty fast !
Click to expand...
Click to collapse
Indeed. I actually want to try just bind-mounting data to a second partition, but I don't know whether init scripts are supported on this phone (would be better instead of editing the init itself). But I will also try this data2sd mod, haven't looked at it yet. After clearing out loads of preincluded apps I was happy for a while, but am now running out of space again!
On adb shell, did you have all the three adb files (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll) & on linux, i use ./adb shell to get it to work...
Click to expand...
Click to collapse
Actually I have the Android SDK set up already on my system, so everything is conveniently there including adb. I will have to find some other day to troubleshoot why the bridge would not work during recovery.
re-packing error
Now I am doing this on Xubuntu so maybe that's why it doesn't work:
I get the following when trying to repack:
MTK-Tools by Bruno Martins
MT65xx repack script (last update: 31-07-2012)
Repacking recovery image...
Ramdisk size: gzip: unpack/ramdisk-repack.cpio.gz: No such file or directory
Could not open ramdisk file: ramdisk-repack.cpio.gz
Any ideas?
Unpacking is no problem.
This Android Kitchen plugins only work with cygwin...
Even unpacking shouldn't have work because mkbootimg & 7z is windows exe...
i'm in the mid of modding it so that it can work on linux too...
Thanks for your reply yuweng. 7z is available as a plugin for Ubuntu too.
In the mean time I will try another website which I already posted a link before.
http://www.slatedroid.com/topic/32450-how-to-unpack-repack-systemimg-properly-using-linux/
breaky9973 said:
Now I am doing this on Xubuntu so maybe that's why it doesn't work:
I get the following when trying to repack:
MTK-Tools by Bruno Martins
MT65xx repack script (last update: 31-07-2012)
Repacking recovery image...
Ramdisk size: gzip: unpack/ramdisk-repack.cpio.gz: No such file or directory
Could not open ramdisk file: ramdisk-repack.cpio.gz
Any ideas?
Unpacking is no problem.
Click to expand...
Click to collapse
It will work on any GNU/Linux as long as you have the proper tools installed. Almost all tutorials for Android "modding" are Cygwin-based, which basically emulates a GNU system on Windows (so you can skip all parts about "setting up" anything). Here your file does not exist, please double-check that it does. This is a perl script which utilizes gzip, gunzip, and cpio. Make sure these are available as well.
Btw, this is independent of Android Kitchen. You don't need that if you're using the builder. Android Kitchen is just a front-end to modifying ROMs. So skip the Kitchen for now and do this manually.
Again, the "another website" you link to is about backing up real filesystems (which the boot and recovery partitions are not). See: http://forum.xda-developers.com/showthread.php?t=1744265&page=2
yuweng: What benefit does using the Android Kitchen have over simply using the builder? All you need is a rebuilt /sbin/recovery along with the resources in /res, and optionally an ext2.ko if it does not exist on the phone itself.
This is just a simple tool for n00b/ newbie...
i was a n00b six months ago & even now my android knowledge is still half empty...
As the first post says, there are hundreds if not thousands of android phone based on MT6573 SoC design, each with their own recovery.img-kernel.img & AFAIK, non is compatible for use on others...
i simply provided a plugins based on Android Kitchen so that even a n00b/ newbie can port cwmr to their MT6573 simply by just drag & drop files to it... You are a programmer by profession i presume, so this is chicken feet to you but to a n00b/ newbie they don't no even where to start, like i did... :laugh:
you'll be surprise if i tell you the top download of my tuts is rooting & installing busybox !
As for the builder, you still need to unpack it, copy few files over & repack it with bgcngm's MTK-tools for it to work on MT6573...not alot of n00b/ newbie know how to do that !
the intention of this plugins is to be able to port cwmr to any mt6573 based android phone...
yuweng said:
This is just a simple tool for n00b/ newbie...
i was a n00b six months ago & even now my android knowledge is still half empty...
As the first post says, there are hundreds if not thousands of android phone based on MT6573 SoC design, each with their own recovery.img-kernel.img & AFAIK, non is compatible for use on others...
i simply provided a plugins based on Android Kitchen so that even a n00b/ newbie can port cwmr to their MT6573 simply by just drag & drop files to it... You are a programmer by profession i presume, so this is chicken feet to you but to a n00b/ newbie they don't no even where to start, like i did... :laugh:
you'll be surprise if i tell you the top download of my tuts is rooting & installing busybox !
As for the builder, you still need to unpack it, copy few files over & repack it with bgcngm's MTK-tools for it to work on MT6573...not alot of n00b/ newbie know how to do that !
the intention of this plugins is to be able to port cwmr to any mt6573 based android phone...
Click to expand...
Click to collapse
yuweng, and I thought you were the programmer! (other than bgcngm I see you as our local MTK expert)
Seriously, we are all noobs. That was my main concern :silly: Android Kitchen interface is command-based whereas the builder you just need to upload an image and you will get an image in return.
So do you mean using Android Kitchen there is no need to go through setting up Cygwin, repack, unpack, etc.? Just download the Kitchen, enter some commands, and you will have a recovery.img which you can flash directly?
i'm a half-cook programmer...
yaya, but you need to setup java, Android Kitchen & the plugins scripts will do everything... :laugh: That is for linux...For windows, you already know...
As for the builder, it works on major brands where it can be flash directly but not on mt65xx...
Ahh OK in that case I do suppose the Kitchen would be much simpler.
Ya, the MTK partitions and images are not the same as those of other devices. That's why Bruno wrote the script to help us
jason_cheng said:
yuweng, and I thought you were the programmer! (other than bgcngm I see you as our local MTK expert)
Seriously, we are all noobs. That was my main concern :silly: Android Kitchen interface is command-based whereas the builder you just need to upload an image and you will get an image in return.
So do you mean using Android Kitchen there is no need to go through setting up Cygwin, repack, unpack, etc.? Just download the Kitchen, enter some commands, and you will have a recovery.img which you can flash directly?
Click to expand...
Click to collapse
Hi Jason,
I have cpio and can execute perl scripts. gzip and gunzip are setup too. The script just cannot find the file ramdisk-repack.cpio.gz and I cannot find it anywhere.
Maybe the dump of the recovery.img was not good. I will try again.
*UPDATE*
The mkbootimg executabe I download was not correctly installed. Now the script finishes without error.
However the recovery.img doesn't do anything. I think I have to look for another mkbootimg or compile one from source myself...
For people who are interested to try the Ubuntu way:
Unpacking:
sudo perl ./unpack-MT65xx.pl recovery.img
Re-packing:
sudo perl ./repack-MT65xx.pl -recovery ./recovery.img-kernel.img ./recovery.img-ramdisk ./recovery.img
I will attach the mkbootimg once I succeed
Star B943 (B94M) MTK6589 Quad Core 4.5Inch 1GB RAM 4GB ROM Dual Camera 5.0MP+12MP WCDMA 3G Dual SIM Card SmartpPhone
{
"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"
}
Please pay attention, there are two versions of this devices on the Market!!!
One is with Dualcore and the other one is with Quadcore MTK6589.
So be carefully with Flashing and Rooting the devices.
There is already some progress with CWM and Root on German chinamobiles.org Forum.
-------------------------------------------------------- Testing LeWa Port Rom -------------------------------------------------------------------------------
Update 07.05.2013: LeWaport_Star_B94M_22.05.13_cm08
My friends here comes a new LeWaport (cmod08) based on the stable release for Amoi N828.
If your already on lewa simple make backup, install cmod08.zip, wipe dalvik and cache after install, all others look instructions below.
Known bugs: Wifi nvrambug, with my fix bluetooh is only working after factory reset or resore data.
Update 07.05.2013: LeWaport_Star_B94M_08.05.13_cm04
Dear friends of LeWa here is a Test version based on LeWa Amoi N828
This version is rooted with gapps, no need to load these.
Hints for install:
1. Boot to CWM or TWRP Recovery
2. Make backup including boot and recovery ( TWRP 2.5.0.0 will be installed )
3. Wipe System partition
4. Install LeWaport_Star_B94M_07.05.13_cm03.zip
6. Reboot and be happy
Known errors: some chinese apps and strings, noLED patch still needed
Further steps: bugfixing, try to port multilanguage support (don´t hesitate to help )
New logo needed
-------------------------------------------------------- Hints for 4.2.1 -------------------------------------------------------------------------------
Update 03.05.2013: Batterylive improvement
User slein has submitted selfcoded apk for LED Fix ! Thanks to him!!!!
There are a lot of activities to fix sporadical battery drain. Following APK seems to be workaround install the app and disable LED notification with widget. Thx to all testers!
Good Batterytool
Update 26.04.2013: Japanese 4.2.1 JB-image from needrom
Well running 4.2.1 from needrom
for most users, please read carefully instructions, do backup (Titanium and/or CWM/TWRP) before update
and make Factory reset as described, to avoid most problems!
Howto Root 4.2.1 and GPS-Fix by JBrandtner
---------------------------- Hints for 4.1.2. --------------------------------------------------------
Update 18.04.2013: Wifi Mac change Fix ( Thx to okupka )
- use these file (make backup before!!!) with this guide and you are done
Update 12.04.2013: Different Sound improvements
People who have problems with sound try this link from Zopo-Forum
or from Patchworkoftips
Update 11.04.2013: Data Resize partition to 2.74GB Detailed description from here
1. We backup with recovery.
2. Unloaded and 2.74GB decompressed data (Thx to spanish friends! ).
3. SP Open Flashtool and as we have done before installing the recovery in scatter-loading MT6589_Android_scatter_emmc.txt select the file in the folder where we unzipped 2.74GB Data
4. We ensure that only EBR1 and EBR2 are marked.
5. We Give to Download, accept the prompt, connect via USB the phone off the PC. As with the recovery if the process fails, disconnect the cable, remove and put the battery and repeat this step.
6. If all goes well, will back the green circle. Disconnect the phone from the PC.
7. Now we go back to recovery (Turn on the phone by holding the power key + volume +).
8. In the recovery do wipe data / factory reset.
9. Optionally if you want to restore the data and installed applications we advance restore, choose the backup you made in step 1, and finally we give to Restore data.
10. Reboot from recovery. In this first boot after repartitioning we may see a notification saying the phone storage is damaged, then click in it. It will show a dialog box asking if you want to format the SD card, does not refer to the External SD but the phone's internal memory, so we do not fear clicking on Format. After doing the latter, voila, you have the Data partition (where apps are installed) extended to 2.74GB
Update 08.04.2013: 3G improvement
if phone is already root
Install from market the mobileuncle tools.
-> enter engineer mode (MTK).
-in modemtestactivity change "factory" for "telephone".
-in "band mode" GSM mode uncheck the "PCS1900."
New TWRP 2.4.4.0 Recovery available here
Update 03.04.2013: Networklocation Fix
by radekfor: i think i solved cell location problem.
Simply install latest Gapps for JB 4.1.2
Click to expand...
Click to collapse
http://goo.im/gapps/gapps-jb-20121011-signed.zip
-> boot to Recovery ( Mobileuncle Tools, or Quickboot,.... ) -> Install zip from SD-Card , ....
Update 28.03.2013: Working on JB 4.1.2
Here you go at your own risk
Drivers;
CWM 5504 and Root here;
German instruction here
New SP_Flash_Tool_v3.1304.0.119
After extracting the zip file:
1. Debug Mode in the Developer Tools Switch
2. Install the drivers ( others may work better, e.g. pdanet )
3. The superuser-313-arm-signed.zip from third copy to the external SD card
4. Phone off and take out battery
5. using the SPFTools load in directory 2. Scatterdatei -> load and Recovery.img, boot.img and flash (press download and then return battery back)
6. Disconnect the data cable after green OK
7. When switching power and Vol + hold when the Green Man comes release Power and Vol + hold on.
8. In CWM now make complete backup, after this install zip from SDcard install the superuser zip ... JB 4.2.1 may need other tools look here found by #90
9. skip step 7 +8 and install superuser using the MTKdroidtools and make backup (but it takes a relatively long time)
10. You can now delete with MTK Droidtool some China-apps."
PS: Backup Rom made with SPFtools->readback
Thanks for the alert.
I've got a quad core 6589 version, so far cannot find a way to root it..
And it's NetworkLocation.apk is missing, i tried a couple of NetworkLocation.apk from JellyBean gapps zip files, no one seems to work, either not installable, crash on boot or not working.
3G connection seems to be dodgy, H/H+ is shown on the top bar but data is not coming down normally, during 1 minute, only less than 100k data come down and not able to load even 1 page...
Anyone has the same problem?
Cheers,
Fish
star b943 (mtk6589 b94m)
could someone translate recovery menu from Chinese Language
Yes the baseband or antennas seems to be crap.
Start download and remove your hands from the device or take it only with two fingers on the upper side, then my downlads finish and downloads show normal values. Speedtest with upload is seems to be fine,...
If someone needs root or cwm write me pm, or give me public upload location I´m not so experienced with this,...
Best regards
Thanks for the advice
radekfor said:
could someone translate recovery menu from Chinese Language
Click to expand...
Click to collapse
Translate into:
-Factory Reset
-Auto (Overall?) Test
-Manual (Overall?) Test
-Single Function Test
-Test report
-Clear eMMC
-Version Info
-Reboot
Hope this helping.:laugh:
how do you think about the Star N9589?
with same quad core cpu mt6589
haisir said:
how do you think about the Star N9589?
with same quad core cpu mt6589
Click to expand...
Click to collapse
The MT6589 is really good stuff, for me its my personal Favorite , but I would prefer smaller devices with 4-4,7" max screensize.
5,5" and higher does not really fit in any shirt pocket. If I ever have to carry a bag for my phone I would prefer a tablet with much better screens and battery life.
So i´m looking forward to Jiayu G4, G5, UMI X1S, or something similar screensize
cmoegele said:
Update 28.03.2013:
Here you go at your own risk CWM 5504 and Root
Best regards
Click to expand...
Click to collapse
That's great!!!!
Thanks, it worked!
Now I still have two problems:
- amazon app-shop doesn't start (it remains black with amazon logo)
- doesn't vibrate on call in vibration mode
does someone else have the same problems?
Thanks
B94M/B943 quad
Thank you everyone for your hard work and time. I have very little experience (twice with well established models)
I was wondering if someone could clean up the txt instruction translation so someone like me can avoid brick making. Even adding better detail would be sweet. I will copy below. Thanks in advance.
"ATTENTION: The Star B94M is available as dual and quad core version!
The tools here refer exclusively to Star B94M MTK6589 or B943 quadcore devices!
After extracting the zip file:
1. Debug Mode in the Developer Tools Switch
2. Install the drivers
3. The superuser-313-arm-signed.zip from third copy to the external SD card
4. Phone off and take out battery
5. using the SPFTools load in directory 2. Scatterdatei -> load and Recovery.img, boot.img and flash (press download and then return battery back)
6. Disconnect the data cable after green OK
7. When switching power and Vol + hold when the Green Man comes release Power and Vol + hold on.
8. In CWM now either only make complete backup, or install zip from SDcard install the superuser zip ...
9. skip step 7 +8 and install superuser using the MTKdroidtools and make backup (but it takes a relatively long time)
10. You can now delete with MTK Droidtool some China-apps."
bradstallion said:
That's great!!!!
Thanks, it worked!
Now I still have two problems:
- amazon app-shop doesn't start (it remains black with amazon logo)
- doesn't vibrate on call in vibration mode
does someone else have the same problems?
Thanks
Click to expand...
Click to collapse
vibration problem was a wrong setting by my side... still have problems with amazon app-shop (very strange, I've it installed on many devices and different versions of android, jelly bean included)
angryfish99 said:
Thanks for the alert.
I've got a quad core 6589 version, so far cannot find a way to root it..
And it's NetworkLocation.apk is missing, i tried a couple of NetworkLocation.apk from JellyBean gapps zip files, no one seems to work, either not installable, crash on boot or not working.
3G connection seems to be dodgy, H/H+ is shown on the top bar but data is not coming down normally, during 1 minute, only less than 100k data come down and not able to load even 1 page...
Anyone has the same problem?
Cheers,
Fish
Click to expand...
Click to collapse
The MTK chipsets have always been weak on data connection starting from the MTK6573. It's so bad that connection can be lost while my Samsung right beside it has a good connection.
Anybody knows what is wrong with this China made phones?
Star
I managed to root. Thanks for the help guys (sarcasm).......The files that "cmoegele" posted worked except for the usb driver files. I had to use PdAnet for connection. I'll be watching to see what other members find on the camera focus and poor data comms.
Thank You
Data upload is stable, and downlad has good values for a while, but slows down from time to time. So I think the device is not doing completly wrong. There needs to be still some finetuning in Baseband and Rom like man other devices always need.
The performance and quality is really good, even +2 days Batter lifetime is a good value for this powerful device.
I´m waiting for new Roms
fmehrtens said:
I managed to root. Thanks for the help guys (sarcasm).......The files that "cmoegele" posted worked except for the usb driver files. I had to use PdAnet for connection. I'll be watching to see what other members find on the camera focus and poor data comms.
Thank You
Click to expand...
Click to collapse
Hi fmehrtens, may I know the RAM and ROM capacity of your phone model? I am wondering if 8GB ROM and 1GB RAM model can be rooted using same method, thanks.
Spec says 8GB ROM and 1GB RAM, however AnTuTu shows only 1GB ROM and 1GB RAM. Am I missing anything here?
Hello,
I've ordered this new phone Star One B943 Quad core, and i want to thank u for the rooting method ^^
I'm searching for the ROM stock, does anyone have the idea where i can find it ?
And i found that the Miz Z1 is the same phone, but with Android 4.2.1 installed. Do u think it's possible to upgrade the Star OS version with the Miz Z1 firmware ?
B934
windwaver said:
Hi fmehrtens, may I know the RAM and ROM capacity of your phone model? I am wondering if 8GB ROM and 1GB RAM model can be rooted using same method, thanks.
Click to expand...
Click to collapse
It is a 4G ROM and 1G RAM. Just FYI, the first time I tried to root it did not root, I had to try it a couple of times, and then I also loaded the ZIP file on the ROM memory along with the SD card. It worked that time. Not sure if that's what helped or not. The phone is a really nice phone ecpecially after rooting. I am also having trouble with Amazon App store app, Netflix playing too slow and the camera focus.
Good Luck and Thanks!
Neodragon12 said:
Hello,
I've ordered this new phone Star One B943 Quad core, and i want to thank u for the rooting method ^^
I'm searching for the ROM stock, does anyone have the idea where i can find it ?
And i found that the Miz Z1 is the same phone, but with Android 4.2.1 installed. Do u think it's possible to upgrade the Star OS version with the Miz Z1 firmware ?
Click to expand...
Click to collapse
I have got a Copy of the origin Rom done with SPFTools. If it is needed. You also can use the Scatterfile from the zip-file.
Do you have a link for the 4.2.1 Miz Z1 firmware ? Perhaps its a fake,...
Otherwise I will flash it to our device except the Preloader, so if it fails I could go back to stock.
cmoegele said:
Data upload is stable, and downlad has good values for a while, but slows down from time to time. So I think the device is not doing completly wrong. There needs to be still some finetuning in Baseband and Rom like man other devices always need.
The performance and quality is really good, even +2 days Batter lifetime is a good value for this powerful device.
I´m waiting for new Roms
Click to expand...
Click to collapse
May I know the country you using the phone in? I have very bad experience with MTK chipsets with regards to data transfer. Other phones e.g. Samsung, LG do not give me this problem.
How to improve the data performance?
*/Haters gonna hate/*
ROM currently "DISCONTINUED". But, the init.rc tweak remains :fingers-crossed:
Hi to all those who are reading this! Lemme answer a few questions before I get started.
First of all, What kinda name is this???
TBH, I haven't yet thinked of a name for this... So, I just named it Stock ROM MOD
And, the name has been thought of! The name is... CyanicSense! Why this name? More details later
What does this do?
Though this is gonna be as stock as possible, the major feature that I had planned out for this is reversed-mount. As you might know, stock ROMs definitely do have mounts2sd (which might give some trouble in setting up), but, complete reversed-mount (i.e. the /sd-ext partition mounted as the /data partition as the int2ext script does, hasn't been achieved yet (on stock ROM). So, practically, this does that stuff.
How is this even possible?
Believe me. This ain’t no magic. Simple init.rc tweak… Mounting the mtdblk0p2 partition, which is basically the sd-ext partition as we better know it, in the /data folder does the trick. In CyanogenMod, this is done via the famous int2ext script…This is a more or less similar command, done during startup. Just make some changes to init.rc, and Voila!!! Your sd-ext is mounted in the /data partition.
So, why make a new thread for this???
Erm, but that ain’t the end of story here. I am planning on some more features. Current features are minimal, reversed-mount, and updated apps. Yep. Updated apps, not one but all of them. I can assure you that you will have every single update including Google Play Store v4.0.xx in this ROM. Also, applications which were basically “stub’s” have also been updated, so that you wouldn’t have to download any more apps. P.S. I have added a small file explorer, named “Explorer”, by Speed Software, the same people who brought about “Root Explorer”. Planning to replace it with OI File Manager in next build, if people prefer it
So, those were the two features of this ROM. Also, I am planning to work on some other features, which mainly include, init.d script support, and, removing bloatware. Currently, there are around 10 apps which I don’t use, and presume that most other users wouldn’t be using it either. So, I am gonna either make them uninstallable, or remove them completely, so that one can get more /system space More features might come up too. You can request new features, but… be reasonable
Is it safe???
I can’t answer that question, but, I am guessing the answer is yes. Why I think so??? Because I am using this as my daily driver for the past few days. Also, “reverse-mount” via scripts like int2ext, and mounts2sd do the same thing, so, I don’t think its gonna create problems
Will it make my phone laggy?
Not sure. Works fine in my Class 4, 8 GB memory card. Anything Class 4 and above, I assure you it wouldn’t “visibly” lag.
What about gaming?
Well, this is the part where you come in. I don’t use my phone for gaming, so, I can’t be sure whether Temple Run 2 is lagging, or its I who can’t play it properly But, one fact can be sure that Stock ROM isn’t always the best choice for gaming.
Anything else left?
Yeah… This build is… kinda heavy. 160+ MB is definitely too big for the “stock” ROM. It is because of all the updated apps which were included. I will try to make subsequent builds lighter, and more bloatware free
Now that Q&A Section is over, let’s get back to business. The simple init.rc tweak is explained in the next post.
Instructions:
Pretty basic. Wipe everything, except SD-Card, and flash the ROM.
The following video might give you a slight idea
P.S.: Recovery used: TWRP 2.5.0.0 (http://forum.xda-developers.com/showthread.php?t=2123503)
Bugs:
I need help with that If you encounter any bugs, please report immediately in this thread.
Downloads:
Link: http://www.mediafire.com/?8grcxx1rbngr6g2
Here is the link… 162 MB approx. Why so big? You are the typical TLDR case. Read the Q&A section above.
Beta Link: http://forum.xda-developers.com/showpost.php?p=41966646&postcount=19
Any issues, please post in this thread. I will try to fix it, ASAP
init.rc tweak that I used:
First of all, get a stock boot.img, and boot_img tools from here: https://github.com/sakindia123/boot-image-tools
Unpack it to some location safe, and, copy-paste the boot.img into this folder.
Then, run the following commands:
Code:
mkdir -p unpack
Code:
./unpackbootimg -i ./boot.img -o unpack
Code:
mkdir -p boot
Code:
cd boot
Code:
gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
Code:
cd ../
Thus, you will have the ramdisk of your boot.img in the "boot" folder. Open up that folder, and open "init.rc" with any of your favourite editor.
Now, search for this line:
Code:
mount yaffs2 [email protected] /data
Replace that line with this:
Code:
mount ext3 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue
Now, I know you are confused... I too was, at first. So, let me make things clearer for you...
This is basically a mount command, which is executed in this order
mount [type of partition] [partition] [mount directory] [options]
So, the partition type is ext3, to be made more compatible with most devices.
/dev/block/mmcblk0p2 is the sd-ext partition.
/data is the folder we are going to mount the partition in.
nosuid and nodev: Allow an ordinary (i.e., non-root) user to mount the filesystem if one of his groups matches the group of the device.
noatime and nodiratime: Access timestamps are not updated when a file is read. So, there is no writing on the partition everytime the disk is read.
barrier=0
This enables/disables barriers. barrier=0 disables it, barrier=1 enables it. Write barriers enforce proper on-disk ordering of journal commits, making volatile disk write caches safe to use, at some performance penalty. The ext3 filesystem enables write barriers by default. Be sure to enable barriers unless your disks are battery-backed one way or another. Otherwise you risk filesystem corruption in case of power failure.
data=ordered
Specifies the journalling mode for file data. Metadata is always journaled.
commit=15
Sync all data and metadata every 15 seconds.
noauto_da_alloc
does give a slight performance increase, especially when working with databases..
nouser_xattr
Support "user." extended attributes (or not).
errors=continue
Define the behaviour when an error is encountered.
Reserved, for screenshots
Yo, screenshots will occupy this post
Reserved,
in case i forgot anything to say
i admit, i typed this in a hurry...
credits are yet to be given, so... please don't flame here
Nice work bro.
For I understand it, is a stock ROM with memory script by you only, yes?
Sorry my english lvl xDDD....
Good job
Edit: well.. must say brother you did good work..
Rom is purely stock with only this tiny mod..
No bugs till now
This ain't no memory script.
TBH, I haven't even enabled init.d support yet. This is solely related to boot.img's init.rc... Which initiates reverse mount when you start your phone.
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Yes.
@rcane said:
Nice tut. One thing that the rom is 1.43.xx based, right?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Stock ROM, version: 1.43.720.2
Brother.. here's a big problem..
The data folder of the Rom is now empty and all the app's apk files and app data installed can't be accessed using the root explorer..
And it is no where.. o can't find them..
Did you make a link to the data folder while mounting the ext partition to data..??
Sent from noob machines
I recommend using another application.
P.s. you will find it in the data folder only. It won't be in the sd-ext folder.
P.s. sorry for the short reply. I ain't at home currently
Sent from my HTC Explorer A310e using xda app-developers app
I used solid explorer..
I got them.. but on es file explorer.. the folder is still empty..
And also there is no sd-ext folder in root... Because you didn't make one..
Sent from noob machines
Did you enable Root Explorer or so...
AFAIK, even in the latest update, root exploration should be first enabled.
Press menu key, and in tools option, there will be the "root explorer" option, or a similar option.
Enable that, and then, you will be able to browse the data partition.
P.S.: if you don't get a superuser request, it will not work.
OK got it...
Thanks brother...
I got my mistake... it works now..:good:
Ohk, tiny flashable zip's coming up!!! HELP NEEDED!
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
me..
vineethraj49 said:
These zips will be of this kind:
Flash ROM.
Flash custom zip
This will be made for stock ROM myself...
Meanwhile, need help for other ROMs. Anyone interested, please reply in thread.
Click to expand...
Click to collapse
if u find something i can do , feel free to tell..
Thanks
artistaditya said:
if u find something i can do , feel free to tell..
Click to expand...
Click to collapse
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
I have this..
vineethraj49 said:
Need help for NextGEN, Xenon, Ateeq, and Explode, and any other sense based ROM that I missed :silly:
I need some info about these ROMs, preferably in the following format:
init.d support: yes/no
mounts2sd used?
If yes, application included or not?
Post this information along with boot.img of those ROMs
Not a stable internet, so, can't possibly download all those files.
Click to expand...
Click to collapse
Sorry i dont have access to all the roms but i can give you information on Nextgen and jaggyrom..
--JaggyRom [specific version 3.2.1 lite]
1.) init.d support - yes
2.) apps2sd script used [without gui]
boot.img here- jaggyrom_boot.img
--NextGen [specific version 1.5]
1.) init.d support - yes
2.) mounts2sd script used [without gui]
boot.img here- nextgen_boot.img
Note to Beta testers! Cyanic Sense Beta is out!
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Screenshots
vineethraj49 said:
What you need to test for:
Bugs.
Overlay issues.
Unreadable text.
That's it!
How to report:
Name of Application.
What you were trying to do.
A screenshot, if it is about overlay issues or unreadable text, along with the name of the application.
Link: http://www.mediafire.com/download/a4c74u6tk8c34wx/cyanic_sense_beta_v001.zip
Click to expand...
Click to collapse
Seems the OP forgot to add the "obligatory" screenshots
No worries here I am xD
{
"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"
}
Click to expand...
Click to collapse
Seems OP is working great,waiting for future updates!
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!