Related
can someone tell me if is possible port Android on this amazing device??
someone is working on this???
I wuold like a lot if someone port Andoid on oHD!!!
lukas_ita said:
can someone tell me if is possible port Android on this amazing device??
someone is working on this???
I wuold like a lot if someone port Andoid on oHD!!!
Click to expand...
Click to collapse
I was working on it for a long time. Unfortunately it is impossible, due to limited bootloader space (not enough for an android one) and no recovery partition. Also it would need a totally new partition layout (as it only has two accessable internal and one external drive, so no cache, recovery access, nor swap.
And also do not forget about the hardware incompatibility. Even if we manage to boot it, you will hardly be able to even make a phone call. Not to say use WiFi, or GPS, BT, or anything.
hi i joined because of some interest in this,
first of all let met tell you that i own a samsoung i8320 (vodafone h1).
this in some way helps because we now have a 'working' limo kernel, in my opinion it might help us out here.
the problem i have is that i never ever yet have been able to do 'any of the work here under' - the fact that i know howto doesn't make me capable of doing, (its like the fact that you know a plain fly's because of big wings and an engine, doesn't make you a pilot)
---------
the H1 uses a rather standard linux kernel as far as i can tell from the source could, though i havn't been able to run it inside quemu yet..
some guys allready interested in porting android say that they got android running but without functions like phone or wifi. this is because thay used an android kernel rather than the samsung one.
step 1:
so what if you would strip the samsung rom from all 'userland' software, keeping only the kernel, its drivers and busybox stuf.
creating a root shell only - you may even be able to make it mount as /boot rather than /
step 2:
now ad ad adtional filesystem on the internal phone memory or an external sdcard ... format it as you like (ext3 with noadtime could do, but other options are also availible).
this should now be where the remaining of the android rom should be. you could now always update most of your your android and apps exept for your linux kernel or drivers. without reflashing. this idea is largely based on apps-2-sd so we all know its been done before.
fonix232 said:
I was working on it for a long time. Unfortunately it is impossible, due to limited bootloader space (not enough for an android one) and no recovery partition. Also it would need a totally new partition layout (as it only has two accessable internal and one external drive, so no cache, recovery access, nor swap.
And also do not forget about the hardware incompatibility. Even if we manage to boot it, you will hardly be able to even make a phone call. Not to say use WiFi, or GPS, BT, or anything.
Click to expand...
Click to collapse
The i8910 community is great....this phone is great...a porting of android on this phone wuold mean a great number of donations!
cannot you use E\ (massmemory...8Gb or 16Gb) like partition?
Hi All.
It's my thread - port Android on Wave S8500(also S8530).
Wellcome developers and designers.
Last state of project:
06/13/2011 Now working on Android 2.3.3 (Source GB for GT-I9000 and M130K)
not working - modem and GPS.
04/04/2011 Memory allocation now is correct!
05/11/2011 I have full schematic for phone
and we're ready to get a fully working kernel.
Full decriptions of GPIO is attached.
source for kernel and initramfs here:
github.com/Oleg-k/S8500_Kernel_2.6.32
github.com/Oleg-k/initramfs_2.6.32_S8500
(real shame if you ask me)
Click to expand...
Click to collapse
Please expect not too much from me.
1.
My other handsets are from 2006... NEVER hold Android handset in my own Hand...
2.
I'm Windows User.
Linux/Unix ... I know only 1 or 2 Commands
I've never formated my SD Card nor any Harddrive with Linux ext4, JFS, ReiserFS or XFS
3.
I NEVER worked with IDA or something similar.
Installed yes, but then my Head exploded
Brain too small.
4.
Many missing parts...
Why I should kill my alive handset, as I have no real chance to reanimate it...
- no Riff Box
- no PCB to play with
I AM NOT the right man to port Android nor to find Security hole
You can make this post sticky.
NO joke, expect not too much from me. We can learn together... but this takes time.
Many time. Months, maybe years...
Best Regards
after many many variant, i found the right boot+sbl+param.lsf for kernel message output.
this is my last bootlogo.
how it can be seen, there is a problem with memory allocation.
oleg_k said:
after many many variant, i found the right boot+sbl+param.lsf for kernel message output.
this is my last bootlogo.
how it can be seen, there is a problem with memory allocation.
Click to expand...
Click to collapse
Great of you to keep us posted! \o/
hmmm... as a matter of interest - I noticed you're using kernel 2.6.35.7, when I look at the original I9000 source that's 2.6.29....
what does that source say as to why it failed in bootmem.c @ line 341?
Not enough memory, permissions, wrong offset?
oleg_k said:
not yet( Starting but don't finish.
Click to expand...
Click to collapse
Whats not happening? Oleg_k would you be able to PM me with a copy of your work, files and so forth i might be able to help you out.
t0mm13b said:
+1 for bootloaders - abso-frickin-lutely....there should be a standard bootloader... meh.... not sure about meteor - haven't seen it...
Click to expand...
Click to collapse
Well I'm holding a meteor wave here, bought around christmas. How much onboard storage does you device have? mine says it only has 512 i think... stupid meteor thinking i wouldn't notice....
sabianadmin said:
Well I'm holding a meteor wave here, bought around christmas. How much onboard storage does you device have? mine says it only has 512 i think... stupid meteor thinking i wouldn't notice....
Click to expand...
Click to collapse
You mean to tell me that Meteor bundled a 512Mb memory card?
I have 4Gb on mine...this memory thing is a bit mystifying dontcha think, despite the discussion on another thread about the nand chipset.... on the one hand some say its 256Mb, others say 512Mb...
I tried the versions 2.6.32 and 2.6.35.
I post sbl+boot+param.lfs and config file for kernel making.
Last time u had problem with lcd_rst pin..did u figure that out?
t0mm13b said:
You mean to tell me that Meteor bundled a 512Mb memory card?
I have 4Gb on mine...this memory thing is a bit mystifying dontcha think, despite the discussion on another thread about the nand chipset.... on the one hand some say its 256Mb, others say 512Mb...
Click to expand...
Click to collapse
No i mean Meteor gave me some (seeminly non existant) version of the wave that has 512 internal storage. Im pretty sure its meant to have 2-4gb at the minimum.
sabianadmin said:
No i mean Meteor gave me some (seeminly non existant) version of the wave that has 512 internal storage. Im pretty sure its meant to have 2-4gb at the minimum.
Click to expand...
Click to collapse
Wave have 2gb of internal storage, but only 512mb are free for the user.
Otacon_ahs said:
Wave have 2gb of internal storage, but only 512mb are free for the user.
Click to expand...
Click to collapse
Wave S8500 have 2Gb of internal storage which are partitioned (bada 1.0.2):
-about 512Mb for messages (mail+sms);
-about 420Mb for user files;
-about 1Gb for system files (os+apps+widget+java)
You can find it in: Setting-->Memory-->Memory Status-->Common Memory
@ oleg_k
1.
How to bypass to write/overwrite Boot without JTAG?
I stuck in problems with Multiloader to write decrypted unmodified Original Boot. See here:
http://forum.xda-developers.com/showpost.php?p=12607344&postcount=34
2.
How to build valid Bootimage for JTAG or file(s) to use your uploaded files.
Maybe you could please upload your working Bootimage from S8500?
So we had something to start with...
3.
You have working fallback/recovery plan? To get back to working bada S8500.
Or only JTAG...
4.
Anyway. Thanx for uploading files for study.
Best Regards
To adfree,
1)now the steps bada->android or android->bada is only via JTAG.
i'm don't know any other way.
2)i posted full working bootloader files in first message of my thread.
3)i will post full jtag image with semi-working android in 2 hours.
Regards
my friend
Thank you oleg_k
Last Question for today.
So I should use simple Flashtool from I9000 to flash these Boot Files into S8500 ?
Sorry for stupid Question. But I'm totally Android Noob.
Thank you for uploading files.
Best Regards
oleg_k said:
To adfree,
1)now the steps bada->android or android->bada is only via JTAG.
i'm don't know any other way.
2)i posted full working bootloader files in first message of my thread.
3)i will post full jtag image with semi-working android in 2 hours.
Regards
my friend
Click to expand...
Click to collapse
We can think about running SBL or any other bootloader (anybody with sources for that?) through the FOTA hole as I described in the thread:
http://forum.xda-developers.com/showthread.php?t=1020444
This way we don't need JTAG for initial flashing. It'd be also good to perform testing without touching BADA in the NAND, but we either need to reorganize partitions or boot from SD card
Best Regards,
mijoma
I think an combination will lead to success... so work together.
At this status it is maybe tooo risky to play without JTAG.
As we not know, how Android will handle Memory...
Okay, correction. I don't know.
In worst case scenario you need JTAG to reanimate Wave...
We have 2 steps/parts.
Android part.
Display, Kernel, Memory, etc...
This part is mandatory in my opinion.
Then second part, how to start Android. Then there are several theories...
BootLoader, No BootLoader, FOTA... inject via JTAG into RAM...
internal Memory or Dual Boot from SD Card...
Anyway, without proper modified Android part we can't use all our Security Holes.
As more infos we have, better, as more working solution we have.
So more chance to improve something.
At the moment we can only improve Video Quality.
Best Regards
Mijoma,
I totally agree with you,maybe this is the way to deploying android on S8500.
But now,i think about build working kernel for our s8500.
Maybe you helping with analize memory init on original bootloader?
like this - http://code.google.com/p/jetdroid/wiki/OriginalDramInit
Regards
Seems like using mijoma's discovery you should be able to replace booting and maybe make it to boot from SD card using a open source booter a compatible android kernel with selfmade drivers.
Maybe that could be the way, sadly we'd lose internal storage since we wouldn't be touching bada partition, anyway Android should be working fine from a SD card, It does properly on other handsets which internal storage is nothing more than a microSD card instead of flash memory.
I think losing 2GB on internal and XMB on microSD is a good deal for having android on our handsets. Happily I got 16GB SD on my wave xP. Anyway once you achieved that we could gather to use the internal flash memory partition
Jioma I suggest you to work with adfree (along your knowledge) and oleg_k they're our wave masters, baybe you together could gather to achieve this great project. I require you to work on this oh please jioma=(
Ok thats great news! Finally we have a method of booting other platforms on the Wave. What we need is as much information on the s5800 chipset as we can get so we know exactly what to compile and what drivers are needed in the linux kernel for android. Someone get in touch with Cyanogen mod and ask him for help and offer him a wave or something ha.
Since the bootloader is bypasased, is it possible to change the partition layout of the internal storage?
Shaumux said:
Since the bootloader is bypasased, is it possible to change the partition layout of the internal storage?
Click to expand...
Click to collapse
may i ask why exactly?
btw... wrong section...
why is not a good question, for android,
a partial answer would be because its possible on other phones.
i thought this is related to android devlopment and the bootloader dev so this would be the right section
i'm sorry if its not.
anyway the question is still unanswered
Shaumux said:
why is not a good question, for android,
a partial answer would be because its possible on other phones.
i thought this is related to android devlopment and the bootloader dev so this would be the right section
i'm sorry if its not.
anyway the question is still unanswered
Click to expand...
Click to collapse
i am not sure if it will work... are u thinking about changing sizes of internal partitions or something like that?
can u guide me to the links where they have changed partition layout on other androids? will read up on the advantages/etc...
Here http://alpharev.nl/ and
here http://forum.cyanogenmod.com/topic/10726-how-to-increase-desire-internal-storage/
The biggest advantage i can think of would be to reallocate wasted space to where its really need, which will depend on the user i guess.
This brings up another interesting thing to my mind.
Changing the filesystem.
It is possible in android, can't say about X10 though.
maybe just for the fun of it or maybe another filesystem may give better performance.
What about support for ext2 filesystem ? That would help wont it ?
Sent from my X10 TripNMiUI
Shaumux said:
Here http://alpharev.nl/ and
here http://forum.cyanogenmod.com/topic/10726-how-to-increase-desire-internal-storage/
The biggest advantage i can think of would be to reallocate wasted space to where its really need, which will depend on the user i guess.
This brings up another interesting thing to my mind.
Changing the filesystem.
It is possible in android, can't say about X10 though.
maybe just for the fun of it or maybe another filesystem may give better performance.
Click to expand...
Click to collapse
Just became a little slow on fs ques. I hope it is possible.
Sent from my X10 TripNMiUI
@realunited123: well i can't say if ext2 will really help or not, its quite outdated now and i also don't think that it would be a good choice for fs on flash.
But btrfs or ext4 would be different.
btrfs specially has many features for flash memory.
But the main question is can these things be really done since the bootloader isn't cracked just bypassed, so would it still search the original partitions?
Lol i meant ext4. Damn swiftkey changes it automatically.
Sent from my X10 TripNMiUI
And also certain parts of nand can not be accessed/written without bricking the device. So there is a big chance it is not possible.
Sent from my X10 TripNMiUI
ext4
Shaumux said:
Since the bootloader is bypasased, is it possible to change the partition layout of the internal storage?
Click to expand...
Click to collapse
that would be big performance boost for our device.
with samsung galaxy s my mate using ext4, and file system performance went hight!
i am waiting for a sollution to change from ext2 (old very old) to ext4 !
anyway : i am using linux as desktop, and server , and PHONE! and only my pgone is locked to ext2....
actually currently we are on yaffs2 and not ext2
tiborprogmed said:
that would be big performance boost for our device.
with samsung galaxy s my mate using ext4, and file system performance went hight!
i am waiting for a sollution to change from ext2 (old very old) to ext4 !
anyway : i am using linux as desktop, and server , and PHONE! and only my pgone is locked to ext2....
Click to expand...
Click to collapse
We are not on ext2. The reason the SGS sees such an improvement is because the original filesystem sucks. The X10's is yaffs2, which is good to begin with, so we would only see minimal gains, if any. zdzihu has had those modules for a long time and doesn't waste our time with them for that reason.
ext4 is not a good idea. While performance under ext4 may be better, yaffs2 is optimized for wear leveling and error correction under flash memory. Those people running ext4 on their internal flash are wearing out their NAND storage at up to twice as fast, possibly faster. Their phone will die much quicker.
This is possible yes. But we would need to have a modified flashtool to support it, and we would need a modified recovery build and some other firmware files for the modified flashtool to use. This is because we cannot access the boot partition or the kernel via recovery, so we can't run a fancy script like the brilliant CustomMTD script/patcher (for example - mainly for HTC phones if I remember correctly).
While I'm nearly certain that's the rough idea of what has to be done, I could still be wrong because it's beyond my ability.
jonusc said:
ext4 is not a good idea. While performance under ext4 may be better, yaffs2 is optimized for wear leveling and error correction under flash memory. Those people running ext4 on their internal flash are wearing out their NAND storage at up to twice as fast, possibly faster. Their phone will die much quicker.
This is possible yes. But we would need to have a modified flashtool to support it, and we would need a modified recovery build and some other firmware files for the modified flashtool to use. This is because we cannot access the boot partition or the kernel via recovery, so we can't run a fancy script like the brilliant CustomMTD script/patcher (for example - mainly for HTC phones if I remember correctly).
While I'm nearly certain that's the rough idea of what has to be done, I could still be wrong because it's beyond my ability.
Click to expand...
Click to collapse
Yeah but we may still use UBIFS or whatever.
The main thing here is that the users gets a choice and i don't see any problem if its through flashtool atleast for now.
and i think the ability to resize the partitions would also be a very useful thing since the rom partiitons seems to be excessively sized than required especially with custom roms.
Disclaimers :
#i am no-developer.im just a geek xperian..like many of u.i have created this ,my first ever thread typing on my mob keypad.so forgive me for short words and untidy post.
#links included below is noway related to me.respective links are included as per my findings to support the main moto of this thread.im thankfull to all of them who have tried to scratch on this through their posts and threads
#with all do respect,this thread is intended for our devs who can take this as pre-requsites for development.
#its a humble request for devs to put there effort on this.
#i request all xperians...from devs to simple users...whoever thinks this post worth discussing/developing,ur valueable words on this are highly appreciated.
#and please no trollers
Click to expand...
Click to collapse
I was doodling around today,i got my eyes poped-up wen i encounterd this
[samsung kernel flashing from cwm zip] -> http://forum.xda-developers.com/showthread.php?t=1301756 and this
[samsung general cwm kernel updater] ->http://forum.xda-developers.com/showthread.php?t=2132208
It all began then when i had to be far from my pc.then flashing new kernls for new custom roms began to be a problem.i presume their are a lot of users like me who cant access pc with as ease as many can.or simply to them who dont want to connect to pc just to flash kernels.if this would be success,just imagine how ease it would be?
But before starting to dream lets put together what i have come across till now.
Then i started digging more...on google & found this Tutorial [many devs might be intrestd &could help xperia users& start to run xperiment in our xperia ] --> http://www.modaco.com/topic/360180-howto-build-and-update-kernel-using-cwm/
In my findings i did aknowledge that this matter has/have/had been left out in corner just for some taboos/nerms like our xperia doesnt ship with normal recovery partition or like our custm recovry doesnt support some disk formats.
But whatsoever, i was little arosed by above things....then came a point whereafter i was too excited,wen i found this in our very xperia forum,xperia p forum ->> http://forum.xda-developers.com/showthread.php?t=2409021
Here the dev has created a zip with updatr script writng the kernel image,which stays inside the boot.img file .i couldnt dig more on this zip,as it was not so popular thread.i dont even know for it works or not,all i know is there are devs wanting to build,which is the main moto of this thread to let devs rethink the possibilty.
And yes, its a convincing reason for acceptance that our xperia doesnt have recovry partition like as other vendors device..and what we get as a recovry is hard coded to ramdisk.but like as ,A xperia s user,i too want to question an enlightning point on this...like using recovry fota partition,wich gets blokd and remains unusable aftr bootloader unlockd....why not use that...if not what about repartitioning empty space in device for recovry usage partition... http://forum.xda-developers.com/showthread.php?t=2163643
i too presume, even though we dont have that heavy intrnl space,but i guess we have enough for just a recovry partition.i guess so.correct me.
FOTA partition :
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Kernel changes : extract_elf_ramdisk setup in kernel
if some body wants a detailed info it can be found here (( **thanks to @officiallysonyrebel ,for the supportive conversation.above words are his ** )) -- http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
*** Summing up in total ***
It may b a horizon-touching dream..but as a geek user, like me,we dream of it.
Our charming devs can unlock bootloaders/root/giv us custm roms/give us a taste with unimaginable upgrowing ever, android version updates in roms/ ports.these all would also be impossible without their immense hardwork/researchs/xperimnts...i do aknowledge its a lot to ask for this.but with all do respect i wish devs get ther hands on it.
I predict most of xda-ians might already know abt all this,if yes do enlighten us more...ur comments and findings are most needed thing currently.
but truely saying i really dream of using cwm @ its maximum capacity,as of its easeness,isnt it? Different vendors like samsung,zte,etc evn can get rooted simply from cwm only...even most htc can. So why cant our xperia?is it coz of less devs in our xperia?i humbly request all devs to put some work on this so that me,like users who cant access pc with ease/dont want to,can easily get the work done.i also presume there r a lot of xperians,who want this.it cant be more handy than this...can it?
Hope in near future ,we xperians could getwith like these features as others.(rootng/flashng kernels from cwm).
Cheers!!
Xperia-lover!!
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
officiallysonyrebel said:
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
Click to expand...
Click to collapse
Ya i had read in the link u dirctd...i got to know that aftr unlockng bootloadr, that partition becomes unusuable/inaccessble.if that could be attained...then we can hope...isnt it?if i undrstud... wish devs could wave their magicstick soon.
Sent from my Xperia Ray using xda premium
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Nope...You are still using the same kernel....just booting from different ramdisk when "installed in /system"...
We need to boot from a "second" kernel which can be used to flash the primary kernel ...Most other phone can boot into two kernels ,one stock and one recovery ,hence they can be used to flash kernels via recovery and use flash_image to install recovery in system ...
The problem is not where kernel/recovery is installed
The problem is how to boot the secondary kernel after installation ...It's very difficult to do that ...
lets say I dd the recovery.img to /mmcblk0p4 which is the fourth partition in an SD card
How do I instruct the bootloader to boot the device from /mmcblk0p4(or fota 1 or whatever) instead of /boot ...Thats the problem ...
Okay that's sad
But what about checking the partitions and if we know which blocks contain the Fota partition, could we try to mount it?
The problem would be how to tell the bootloader to boot the recovery or the 2nd kernel right?
Sent from my Nexus 4 running Android 4.3
Still the same problem ,how to instruct the bootloader to boot from fota 1 instead of /boot !!
Check that. It's exactly the same what we want to do, right?
Okay not exactly but we could use that too. But I'm not sure if he is able to install another kernel in the recovery...
Sent from my Nexus 4 running Android 4.3
mihahn said:
Check that. It's exactly the same what we want to do, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
karandpr said:
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
Click to expand...
Click to collapse
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
mihahn said:
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
karandpr said:
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
Click to expand...
Click to collapse
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
mihahn said:
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
karandpr said:
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
Click to expand...
Click to collapse
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
mihahn said:
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
karandpr said:
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
Click to expand...
Click to collapse
Yes the HTC HD2 has great development support and I already worked with a HD2 of a friend, but I have actually no idea how to use the method they are using for the HD2 for our devices. I think I will dive into it when I'm back at home from my vacation trip
Sent from my Nexus 4 running Android 4.3
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
officiallysonyrebel said:
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
Click to expand...
Click to collapse
Ehh...no it won't work ...the S1boot boots only from /boot...
The thread you cited is too old and worked probably due to an exploit in nook color ...
I think something like LK should work ,provided it waits for sd card to mount...
officiallysonyrebel said:
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
Click to expand...
Click to collapse
Correct me if i m wrong.its a noobish thought.
Can we access fota partition before bootloader is unlocked?if we can so what r we waiting for?
lets rehearse for the magick show,do what u have thought of.
(I presume when device is still locked....or if we revert back to locked state from unlocked... we could acces that partition.. .we get space for secondry kernel...if still quesn is letting bootloader know we want to boot from that,then again we r far behind)
Sent from my Xperia Ray using xda premium
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!