Help! Creating Updater Script is driving me INSANE - Android Q&A, Help & Troubleshooting

Hi all. New to ROM cooking, so be patient with me please
I am working on a creating a CWM flashable "custom" ROM (actually it's stock ROM with updated preloader, EBR files, performance scripts that is pre-rooted) for a device that currently has no flashable zip ROMS (I can currently only flash stock via SP Flashtool). It uses an Octa core Mediatek MTK8392 chipset, which is basically the tablet version of the 6592 (they are in fact mostly the same processor, and scatter file even shows it as a 6592).
I have got the device rooted, CWM installed (generated with MTK Droid Tools) busybox intalled, everything deodexed, and zipaligned via dsixda kitchen, and the ROM itself is packaged and ready to go. But..after multiple Status 0 attempts in CWM, I realize that my updater script is the issue. I have used kitchen to modify "update" script to "updater", but still no luck. I have attempted to use other updater scripts from similar devices, but even after 1 or 2 of those stated "installation successful", it was clear that the ROM actually wasn't flashed.
I have tried soooo many combinations, and this tool on XDA to generate a working script, but apparently I am just too stupid to get this done (using a master script also didnt work for me). After literally 11 hours of working on this yesterday and trying this method repeatedly, I thought I should ask the pros here on XDA.
I have attached the script from the ROM I recently compiled, and the blocks map file for my device generated from MTK Droid Tools. Could anyone point me in the right direction to FINALLY get this ROM booting? I would greatly appreciate some help.
Also, I have used modded EBR files to extend the internal system storage (1gb for installing apps is a joke). Partition was extended to around 9gb and is working fine, but could it be causing me issues? I basically used EBRs (attached..im using 10GB 1 and 2) to reduce the 12gb USB storage down to around 2.5, and extend internal memory to around 10gb.

@moderators - Sorry, I put this in the wrong section. Could you kindly move it to the Q&A Troubleshooting section?
EDIT: Thanks mods

So I just flashed stock ROM with original EBRs and will try to compile this way. I dont think it will make a difference, but it's worth trying. Maybe the new partitions negatively effected the blocks that need to be written to?

Bump.
Ah common guys. Surely someone here can give a little assistance with an updater script?

Related

[Q] Parallel File Systems / ROM hacks

I had an odd thought. A lot of us like to test out other ROMs, but NANDROID backups and restores result in significant downtime. I'm curious if it would be possible to nest a fully installed ROM inside a subdirectory of the current running one and then swap them out in Recovery by rewriting the pertinent directory paths.
Obviously, there would be a requirement that both ROMs be compatible with the file system in question (Ext4 , etc.)
I mention all this because I would like to be able to quickly boot into Cyanogen 7 every now and then for the bluetooth stack and some of the other features here and there, but my daily driver is Bionix.
Obviously, a nice chunk of space would be "wasted" having duplicate copies of lots of files for apps and such (in addition to the space used having a second ROM) but I think the Galaxy S series NAND space is sufficient to try something like this.
Holy crap that's an amazing idea!!!
Theres already a way to do this its called dual booting and uses your internal memory.
Complicated though.
Are there any guides?
Yes, their in the android section (lol)
http://forum.xda-developers.com/showthread.php?t=847423
work in progress.....close to alpha release
Aww I thought it could already be readily available .
Nice though can't wait .
edit nevermind

[Q&A] Lenovo phones / Cybermaus ROM's (A750, A789, P700i, A660)

Hi all
I am opening up this Q&A thread as extension to my ROM threads, for the simple reason that ever since there is a limitation preventing new users from posting in development threads, I get flooded with PM's. So I intent to move any Q&A, help requests, as well as free and open discussions between users here.
Since the A750 and A789 are so similar, and I put the same stuff in them, I extent both into this one Q&A thread, and in fact, much of it knowledge applies to other Lenovo's like the P700, P700i, S880, A660 which are again very similar and I even use them as basis of my ROM.
Also, I am not intending to be topic police. Like in my other threads, I do not mind if you guys share knowledge about APKHOT or Smileyvvv or Etotalk ROM. As long as it is helpful. Also, I may not always reply myself, so feel free to help each other.
Link to the original threads:
[ROM][2012.xx.xx] Lenovo A750 custom ROM (GB&ICS). <last page>
[ROM][2012.xx.xx] Lenovo A789,P700i,A660 factory&custom ROM (ICS). <last page>
Other related threads (not all mine):
CWM flashing tutorial (update using recovery)
MT6575 flashing tutorial (update using flash utility
Lenovo Original recovery tutorial
[SCRIPTS] Unpack / repack MT65xx boot.img, recovery.img or logo.bin
[REF] Unpacking and repacking stock rom .img files
[UTIL][APP]Lenovo Security / LeSec app (anti-virus/spam/theft/firewall)
[TOOL][TUT]Backup and Restore Mediatek based phone's IMEI
How to DIY : Self root/gapps/playstore/locationfix/clean my ROM
This is a guide on how to root & cleanup your China ROM yourself. It will probably work on all ICS China phones. But it requires & starts with the availability of a recovery image for your phone
There are in fact a few steps:
- Get a proper recovery image for your phone.
- Root it by installing Chainfire's root package
- Install Google GMS ('GAPPS') to get Play Store and Localisation to work
And optionally
- Install Mobile UncleToolset
- Install an extra small fix with location services
- Install an extra small fix with latest APN list
- Install an extra fix to remove well known Chinese system apps
Recovery image
The Recovery Image allows you to boot into an alternative small Linux that you can then use to update the main Android. Updates usually come in "update.zip" scripted files. And the recovery has some other utilities like backup or wipe the entire phone. Getting a working recovery for your phone is step number one, because if you have a recovery, you can do everything else.
To check if you already have a recovery: Well, try to boot into it. The boot sequence may vary with the phone, but on MediaTek phones it is usually to replace the battery and then press&hold both volume buttons while powering up. I have seen it where you need to actually press the power button a split second before pressing both volume buttons. Try a few times, replacing the battery each time.
If you get to a screen that reads CWMR or CWMR Touch (short for ClockWorkModRecovery), you are all set and can continue with rooting. CWMR it is the most common open recovery image. If your recovery is closed, then you need to search the web for a working recovery for your specific model. Each brand and model needs its own recovery, because screen drivers, buttons and partition tables may differ.
Search the web is the best advise. Search wide and search deep. If you cannot find any recovery, then see if you can find a full ROM for your phone. If you have a working ROM image, then there are people on XDA that can make a recovery for you, but typically you need to show/prove that you have really tried to find one yourself.
Flashing a recovery
If you do find a recovery, that you suspect is the correct one for your ROM, then comes the scary part: Flashing the recovery to the phone.
This paragraph is specific to Mediatek based phones. On different hardware you also need a recovery, and once you have a recovery, you can use the other parts of this post, but how to flash other hardware, I do not know, sorry
Flashing using the flash tool is scary to new users. Because new users suspect that if they mess it up, the phone dies. And this is correct! But if you only flash the recovery.img part, you should be fairly safe. Read this manual on flashing. Getting the USB driver installed is sometimes a bit tricky, you may also want to read post #21 and post #25 for help.
I have seen several people asking 'where to find the scatter file'. Well, it comes with the ROM you want to flash. If your ROM file does not come with a scatter file, then is not a ROM file that can be flashed with the flash utility, but with an open recovery.
Rooting
Once you have a working recovery, the rest is simple. For rooting, simply install (from inside the recovery) chainfire's "CMW installable ZIP"
Link to his post: (ignore his big red 'requires root' warning). The file you need is labeled "CWM installable ZIP" at the bottom. Direct link to the file you need to install via recovery update.zip
This usually works by putting the zip file on the SD card (its name can be anything, though for some limited recoveries it sometimes must be named 'update.zip'), booting into recovery, and selecting the zip file to update.
Google GMS (Market/Play Store, Location, etc)
Simply install the latest Google Mobile Services (better known as GAPPS) from CyanogenMod V9. This is their explaining wiki from CyanogenMod
The file you need is called gapps-ics-20120429-signed.zip for ICS and gapps-jb-20121212-signed.zip for JB and can be found here. You probably also want to wipe your cache partition after doing this.
Mobile Uncle toolset
Just install this program apk (so not through the recovery, just install it normally). Or search the web for the latest one.
Fix location services
If location services does not work, do apply Google GMS (GAPPS) above. If it still does not work, it may be because the phone is programmed to use Chinese location services. This patch will tell it to use GMS. The patch will apply, and probably even work, on all ICS phones. But was originally made&tested on a Lenovo A750 ICS. Its called V1.3 because many people have downloaded the A750 v1.3 patch and used it on many MT6575 phones. It is still the same patch, except the update.zip is tweaked to work on any ICS phone, not only MT6575 ones.
Sometimes you also need to go into MobileUncle tool, the MTK Engineer mode, and in location settings. Depending on your exact model, somewhere in there is a NetLoc or NetLocation and a GeoCoding setting, with options of MEDIATEK and GOOGLE. Ensure they are set to GOOGLE.
After messing with location settings, it is best to also wipe cache.
Fix APN list (or My 3G does not connect!)
You can always add your own APN (Access Point Names) from the settings menu. Just add your own, and select that over the pre-build one. But this package will update with the latest list as maintained by CyanogenMod 9. The update.zip was made in such a way it should work on all ICS phones, Mediatek or other.
Clean well known Chinese system apps
<patch still coming>
==========================================
List of known recovery images for Mediatek Flash tool:
Lenovo A750 : 592zn : See also this post #607, nandroid backup does not work.
Lenovo A789 : 592zn or APKHOT
Lenovo P700i : My own, based on APKHOT with CWM.
Lenovo P700 : My own, based on CWMT / 592zn. nandroid backup will not work.
Lenovo A660 : My own, based on APKHOT with CWM
Lenovo S560 : My own, based on APKHOT with CWM (as yet untested)
Additional Recovery Images in this post.
If you feel you searched all over the web, and could not find a recovery for your model, and you next feel you should ask me or one of the other people on XDA to make you one (which I am not encouraging), than please be aware we need at least a 'standard ROM' for your phone to start from. Without it, I can do nothing. So go back out there, and find a standard ROM, does not matter what language, as long as it is for your specific phone model and known to work.
Also, as an extra warning : If you are flashing, and you experiment with 'suspicious' ROM sources, *never ever* flash the preloader, mbr, ebr uboot. Only flash those from a trusted source and if they belong to your exact brand and model phone.
One more reserved
lolo250612 said:
Hello from France,
Just a little message to thank you very much for your very useful "Lenovo A789 factory&custom ROM (ICS)" thread. I have just bought a A789 from etotalk, and your posts really help to master the beast.
I can't participate to the thread because I am a new member and consequently can't post message to this development thread. And this very sad, because I have discovered a shortcoming of this phone. Apparently, the ICS entire phone encryption does not work and, according to some information I have gathered around the web, it may be due to the fact that the internal sd partition is not ext4 which seems to be required.
It may be due to the fact that the kernel does not support ext4. If this was the case, I would be very pleased to activate the option, recompile it and share the result with other people at xda. I have done it for two types of Samsung Galaxy phones.
In this case, the two problems I would be faced with are:
1) Getting the kernel sources. For Samsung it is quite easy. For Lenovo, I am not able to find them (I can't read Chinese).
2) The process to package the new compiled kernel to a zip, compatible with cwm.
Anyway, thanks for your help and to share your knowledge.
Sheers,
Laurent
Click to expand...
Click to collapse
cybermaus said:
well, not sure about encryption, but I can *assure* you that the phone supports ext4, because in fact the root; system; cache; secro and data partitions are all in ext4 . I know that quite certain, because to unpack/repack, I need to recreate an ext4 loop device.
Internal SD is indeed FAT partition. But it is normal for SD to be FAT
Click to expand...
Click to collapse
It is possible the encryption fails on the FAT of the SD card. It is an internal device, if that encryption utility tries to parse all the internal partitions, it may fail on FAT, but I am guessing here. However, then it would fail on pretty much all recent china phones, they all seem to have this internal SD card. You could try to simply format the internal SD as ext4.
I do not think it would fail on the recovery or boot sections. Those are all nicely wrapped up in the first partition of the emmc chip (emmc0p0 or something) in a proprietary filesystem, as I suspect true for all Androids. So your tool would know to exclude that the first one. However, if you want, you can get the original recovery you asked about from the original A789 ROM in my Dev-Host.
Edit: Encryption issue solved, see post#9 below
I already managed to build a multilang framework-res.apk for the A789 ROM. But now there are all those apps that need to be made multilang also - settings.apk and more... a lot of work.
Is it possible to take a P700 ROM with A750 kernel and flash it to the A750? Or a P700i ROM and A789 kernel for the A789? They seem to be almost identical.
Any plans to integrate the long press home button function in A750_ROW_S114_cybermaus_ICS_V3.1? Would like to test this rom but this missing feature is essentail for me...and onother question: V3.1 is also for A789, right? Same problem with long press home feature?
@oz42
Well, I am a little disappointed about that question. Putting the P700_ROW on the A750 is *exactly* what my V3 series is. Works wonderful. It's the reason I have been updating this thread for the last two weeks. Problem is that the only extra language is Vietnamese. You may want to re-read posts #2 and #585 in the A750 thread.
I suspect the same is true for P700i and A789, but I did not find a P700i_ROW rom yet. I did find a S880_ROW, and when I have time (later this weekend) I will check if that has proper multilanguage (edit: No. It adds ru, vi, id to en and zh. Not quite what I had hoped for)
@metzner
Yes. When I know how. But I do not have a clue at this moment. I am very pleased about the V3.1, but the missing long press is annoying me at times.
No, V3.1 is not for A789 (yet). They have different partitions, different schreen driver. YOU CANNOT flash a A750 on A789 (or any MT6575 on MT7577) without 'porting' the ROM. I do have a Frankenstein ROM, using p700_ROW with kernel/partition/modules/baseband from A789. But it was not tried out yet.
A789: Encryption problem
I have installed aLogcat to determine what could block the encryption service on the different ROMS I have tested on my A789. The interesting part revealed to be:
E/Cryptfs ( 87): Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
Googling for this problem, it appears that there is a strong probability that the culprit is CWMR that I have installed almost right after getting my phone. See: http://forum.xda-developers.com/showthread.php?t=1792101 or http://rootzwiki.com/topic/25652-fixing-galaxy-tab-2-encryption/.
So if somebody has a package that can be safely used with mt6575-flashing tools, to recover the stock recovery or, much better, to install a "clean" version of CWMR, I would be glad to test it and see if it is actually the origin of the encryption problem.
Edit:
@Cybermaus: I have just noticed that you have already addressed part of this message. I have already tried to format the internal sd as ext4 with Minitool partition Wizard on Windows. This fails also. Moreover, the system reports a failure on this partition and ask to reformat it as vfat. I will try by putting back the original recovery from your 4shared. Thanks a lot.
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
That means replacing it with factory recovery will not help, unless if you then also wipe using that factory recovery, and that factory recovery does leave 16KB. You could also try wiping it from the settings menu.
After you have tried the factory , let me know. I think I can make an empty /data for you that is 16KB shorter than the partition, but you would have to apply it using the flash-utility method.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Hi cybermaus
Thanks for your contribution. Please help me if you've free time.
Does this custom ROM support traditional Chinese character?? I'm sure Chinese support would include simplified Chinese.....
@loimlo
The A750 V1 and A789 V2has two forms of Chinese, which I cannot read, but I suspect are traditional and simplified. The A750 V3 has one form of Chinese, which I still cannot read, so I am not sure which of the two, but here is a screenshot of it, let me know which it is.
Amadis223 said:
Hi, I wrote with yuweng on this subject. And it is very strange. He says, that mt6575 has only ext4 filesystem, but I,am sure,that I have mt6575 and yaffs filesystem. What do you think ?
Click to expand...
Click to collapse
Well, all the MT6575 and MT6577 based ROM's that I have dissected have ext4. This is probably because mediatek provides ext4 in their development kit. So yeah, I think all mt6575 are on ext4, and not yaffs. I think maybe the mt6573 has yaffs.
cybermaus said:
@lolo250612
If I read that post you found, the problem is not so much CWMR or CWMRT itself, but the fact it wipes and formats /data completely, without leaving 16KB of unused space at the end of the partition.
Click to expand...
Click to collapse
I agree with you.
Edit: checking, I found that the userdata.img that is inside the original S228 factory flash ROM is already 1024K short of 768M. So 767M. No need to build one with only 16K short, just use the one you already have.
Click to expand...
Click to collapse
I have flashed userdata.img. That WORKS :victory:. The phone reboots and then encryption starts. Done in less than 5 minutes. Great. Now, just have to tried one of the utility around that allows to have an encryption password different from the lock one. Many thanks for your help :good:.
hi there,
I just got a Lenovo A789 and i just installed A789_S228_cybermaus_V2.1 and it works perfecly...
i'm new to android and i can't get cellular data to work ( i have reason to believe that it worked in original ETOTALK rom, but im not sure ).
1) i do have a data plan
2) cellular data / mobile data is turned on
3) 3G card with cellular data plan is in slot 1
wrong basebands or apn settings (Portugal, Vodafone) ? ( i can see them in mobileuncletools but i cant change them )
help?
note: i cant follow most of android tips that i googled because some of the menus to edit APN settings do not exist on this rom :\
@spinal2k
Well, the simply solution would be to try and apply the A750 V1.4 as listed in post#2. It only applies location fix and new APN list, so its safe on the A789, even if it was originally for A750.
Second option would be to Google for the keyword APN together with your provider and country names.
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
cybermaus said:
Last option is to tell us the mcc/mnc that mobile uncle found, as well as your current APN settings, and maybe we can figure it out.
Edit: you can change APN in Settings->Wireless->More->MobileNetworks->AccessPointNames
Click to expand...
Click to collapse
ok, thanks for the tip... how can i see mmc/mnc on mobileuncle tools?
According to that wikipedia page, my MMC/MNC is 268/01 and that it uses GSM 900 / GSM 1800 / UMTS 2100.... On mobile uncle engineer mode i can see that on the 1st sim card UMTS 2100 doesn't exist ( only UMTS 2000 )... :\
acoording to the "you can change APN in..." i can't changed them, just see them... they look fine to me, they're not wrong...
:\
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
cybermaus said:
@spinal2k
Don't tell me the ones from that Wiki page, but the ones you find in the APN settings. And then also the "market name" of the service you have. You cannot change, but you can add a new APN, and then select that to use.
But simply applying the V1.3 may be easier, it has the APN list maintained by Cyanogenmod, and will probably solve it anyway.
Click to expand...
Click to collapse
oh, i couldn't see that i could add new.... Now i added an optional apn ( even though the one listed was on official carriers page ) ... now its working...
Thank you for the tips... keep them updates coming
note: i did update with A750 v1.3 and i saw no changed in apn list...
A750 V3.1 battery life
I have been using the cybermaus V1.3 ICS for ages, and it works really well. Recently tried the V3.1 ICS.
Also seems to work really well as well, and a definite plus is the 3G signal strength - I see a definite improvement.
There is a dealbreaker problem for me, though - the battery life is noticeably worse than the excellent life on the V1.3 rom. I'm a noob - tried clearing user cache/dalvik, but not reset (I want to keep my apps/data).
Any suggestions before I go back to V1.3 - thanks.
zapzog said:
Any suggestions before I go back to V1.3 - thanks.
Click to expand...
Click to collapse
Well, a request more than a suggestion: your battery is now a few months old, so slightly less good then when new, but you got used to it. But now, due to the flashing of a new ROM, you are playing on it more, and it is in your attention very much.
I cannot properly test myself, I have to tether it daily for data access. So please try to get a proper test of it:
Stay with V3.1 a few bit longer, at least 2 battery cycles extra. (you can barely have had one) so you get a better baseline. Charge the same method as before (I find that charger works better than PC-USB) After two more cycles, when you have a proper idea on the life, go back, and get a renewed baseline on V1.3 also. And then report your results

[Q] Mlais MX28 mounting /system read-write

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!!

[Q&A] [MOD][GUIDE]Partition your internal memory for better App management (Pit File

[Q&A] [MOD][GUIDE]Partition your internal memory for better App management (Pit File
Q&A for [MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [MOD][GUIDE]Partition your internal memory for better App management (Pit Files). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
some help, maybe?
metalgearhathaway said:
It's been brought to my attention that some people may have the 32GB model of the i9100, if so and you are interested in this mod please PM me!
Click to expand...
Click to collapse
Hiya, MGH!..well i can't pm you but i'd like to take you upon this so if you could provide me with the 32GB pit files, please. i'd be very grateful!
in case it matters i'm running on a Resurrection Remix KitKat 4.4.2 - v5.1.5-20140609 Rom.
Thanks!
Pit file
Here's the file you requested.
sam788 said:
Here's the file you requested.
Click to expand...
Click to collapse
Hi Sam,
That looks like a proper 32gb pit, unlike some others I have been sent!
So, I can have a play with this one.
But, how big are you looking for your data partition to be? i.e. the area that apps are installed? I reckon somewhere between 8-12gb, but you know better than me how many apps you want installed
Let me know what you are looking for and I will make a test file for you.
Of course, like anyone submitting pit files to me, you take the risk in testing, I don't have one of these devices myself so I cannot verify at my risk, unlike how I did for the 16gb variant back in the day
Look forward to hearing back from you, make sure you either reply quoting this message or mention me in the post (@metalgearhathaway) otherwise I won't get a notification that you have replied.
Take care,
Chris
metalgearhathaway said:
Hi Sam,
That looks like a proper 32gb pit, unlike some others I have been sent!
So, I can have a play with this one.
But, how big are you looking for your data partition to be? i.e. the area that apps are installed? I reckon somewhere between 8-12gb, but you know better than me how many apps you want installed
Let me know what you are looking for and I will make a test file for you.
Of course, like anyone submitting pit files to me, you take the risk in testing, I don't have one of these devices myself so I cannot verify at my risk, unlike how I did for the 16gb variant back in the day
Look forward to hearing back from you, make sure you either reply quoting this message or mention me in the post (@metalgearhathaway) otherwise I won't get a notification that you have replied.
Take care,
Chris
Click to expand...
Click to collapse
Hey Chris,
so a bit of progress -possibly- on this, i have been looking around since and it seems like that whole command thing i mentioned in my PM seems to affect the PIT
so per suggestion i used a tool called EFS Professional found here:
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
Which outputs the PIT file after EFS partition backup ( which should be useful later). I attached the original file, Also i think i got the concept of how to edit it so i used PIT Magic and edited that file with a 1GB for the system partition and 8GB for the Apps and the usual pre-load size ( doesn't bother me). I'm attaching this as well so, please take a look at it and tell me if my alteration is correct.
There's also the signature issue which as i understand is the last bit of the file, i did checked with a HEX editor and it sure wasn't the same after the edit so i went ahead and added again that last lost bit so it matches the original stock PIT file ( it went from 2KB to 3KB ). So, let me know if that's an issue or if the SII isn't affected by this as it was suggested elsewhere ( i also assume by your PIT files sizes).
Other than that i think 8GB is a good place to start, i wont fill it up for a bit or would i!? we'll see.
And yes, i understand the risk and was wondering if there's anything else i should do to minimize it other than making backup for the EFS partition, backup the internal SD and have a fresh CWM backup on the external SD? btw i should i do something about the apps that's already moved to the SD? i'm already running out of space so i wont be able to move them back to the phone..if that's a problem then should i backup one by one through Titanium Backup and uninstall then restore when i restore the ROM after the New PIT or all that would take care of itself as long as i restore the internal SD as it was before i restore the ROM?
EDIT: i know you go over this in step 10, i'm just not sure how if it's gonna prompt to format SD anyway.
Sorry, too much questions but i don't wanna be left high and dry in the middle of this
Thanks,
Sam.
sam788 said:
Hey Chris,
so a bit of progress -possibly- on this, i have been looking around since and it seems like that whole command thing i mentioned in my PM seems to affect the PIT
so per suggestion i used a tool called EFS Professional found here:
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
Which outputs the PIT file after EFS partition backup ( which should be useful later). I attached the original file, Also i think i got the concept of how to edit it so i used PIT Magic and edited that file with a 1GB for the system partition and 8GB for the Apps and the usual pre-load size ( doesn't bother me). I'm attaching this as well so, please take a look at it and tell me if my alteration is correct.
There's also the signature issue which as i understand is the last bit of the file, i did checked with a HEX editor and it sure wasn't the same after the edit so i went ahead and added again that last lost bit so it matches the original stock PIT file ( it went from 2KB to 3KB ). So, let me know if that's an issue or if the SII isn't affected by this as it was suggested elsewhere ( i also assume by your PIT files sizes).
Other than that i think 8GB is a good place to start, i wont fill it up for a bit or would i!? we'll see.
And yes, i understand the risk and was wondering if there's anything else i should do to minimize it other than making backup for the EFS partition, backup the internal SD and have a fresh CWM backup on the external SD? btw i should i do something about the apps that's already moved to the SD? i'm already running out of space so i wont be able to move them back to the phone..if that's a problem then should i backup one by one through Titanium Backup and uninstall then restore when i restore the ROM after the New PIT or all that would take care of itself as long as i restore the internal SD as it was before i restore the ROM?
EDIT: i know you go over this in step 10, i'm just not sure how if it's gonna prompt to format SD anyway.
Sorry, too much questions but i don't wanna be left high and dry in the middle of this
Thanks,
Sam.
Click to expand...
Click to collapse
Hi Sam,
All looks good to me!
As for precautions, all I can say is have your stock pit file ready if it does not work out! Nandroids do not contain pit information! But I reckon you have guessed that already
I find that flashing the pit file together with a sammy stock rom works best, then root and install your prefered os build!
Let me know how you get on! All the best, Chris
can i increase /system to 1Gb by reducing internal SD?some rom like miui or color os need /preload.is it possible?thankyou
Help me pls with galaxy s2
HI!
I have been using galaxy s2 from 2 years and 4 months now.
Recently (1 month ago) used root genius to root my phone.
I want to use that tut to increase apps space (4-5gb) and get kit kat update.
how to use?
tell me as if I were a 10 yr old. because I don't understand a thing, pls give me a step by step guide.
metalgearhathaway said:
Hi Sam,
All looks good to me!
As for precautions, all I can say is have your stock pit file ready if it does not work out! Nandroids do not contain pit information! But I reckon you have guessed that already
I find that flashing the pit file together with a sammy stock rom works best, then root and install your prefered os build!
Let me know how you get on! All the best, Chris
Click to expand...
Click to collapse
Hey Chris!
sorry, bit distracted these days but wanted to give u a quick update. i actually couldn't wait for your reply and went ahead and did it!! all worked perfectly
the only odd thing is that the battery is acting funny now and i already calibrated the chip again, that was the one odd thing but i cant see how this would have affected it.
now it seems like 8GB might have been bit much for my usage but i'll just leave it now plus i know the how-to now anyway are you going to update the files with the 32 version or you dont think it's worth it being just me who asked? anyway, u have a legit stock PIT now, so your call
thanks again
Sam.
partition worked, not enough storage?
Hi!
I've applied the Pre-load 45mb / 8GB pit to my S2 (i9100) (and CM kernel stock 06.02.14) and flashed CM11 M11 ...
For some reason, when i want to install the latest Gapps stock package from http://forum.xda-developers.com/showthread.php?t=2397942 through CWM it gives me the error that there isn't enough space ...
to be precice:
Insufficient storage space available in System partition. blah blah
You need 350236 KB system free space.
You only have 164636 KB available.
I wonder why this is happening ... i should have enough space now, shouldn't i?
Here is the log of the PAgapps installation attempt:
# begin pa gapps properties
# This file contains information needed to flash PA GApps
current_gapps_version=none
current_gapps_type=none
installing_gapps_version=20141103
installing_gapps_type=stock
total_system_size_kb=0 9 516040
used_system_size_kb=351404
free_system_size_kb=164636
free_space_reqd_kb=350236
total_gapps_size_kb=402344
install.chrome=false
install.faceunlock=true
install.camera=true
install.gallery=false
gallery.device=none
replace.launcher=true
replace.mms=true
replace.browser=false
replace.picotts=true
device.name=GT-I9100
# end pa gapps properties
Big problem
Hi
I'm new on the forum.
Yesterday I tried to expand the partition of my GT-I9100 phone but with the wrong files :
I used those downloadable on this link : http://forum.xda-developers.com/gal...-pit-files-creating-larger-partition-t2552738 instead of those of this thread : http://forum.xda-developers.com/gal...es/mod-partition-internal-memory-app-t2538947.
I thought nothing had happened at first place so in order to exit the download mode I removed the battery.
Since then my phone doesn't boot anymore : no light, no sound, only the dark screen.
Is there something I can do to get back my phone ?
Thanks a lot !
TheCrusader1985 said:
Insufficient storage space available in System partition. blah blah
You need 350236 KB system free space.
You only have 164636 KB available.
I wonder why this is hap
Click to expand...
Click to collapse
You used a PIT file which maintains the original 512MB system partition size. This is not enough to install Full or even medium apps.
Flash a PIT file with 768MB or 1 GB (i recommend 768MB) system and this will be enough for almost any ROM with Full Gapps.
SGS2 Repartition in fewest steps using Heimdall (not Odin)
Hello all,
My GT-i9100/GalaxyS2 runs CyanogenMod 11M12 & ClockworkRecovery 6.0.x.x;
All works fine except for the limited size of the default 2GB partition (insufficient space to update Apps); plenty of space on the rest of the internal storage.
What is the best way to repartition this? Can I *just* apply a new PIT file using Heimdall?
Heimdall-frontend asks for files for lots of partitions -- what's the minimum I need to supply (for which partitions: GANG, DATAFS, ...) & where do they come from?
Or indeed if I have to supply them all, where to they come from?
- there are loads of how-to guides on XDA and elsewhere, I've spend many hours looking at them, but they don't seem (to my eyes at least) to address the Q's above.
- I realise it'll wipe & reset the phone: not a problem to re-cyanogenmod & set it all up again once repartitioning done 'safely'.
- I don't have access to a Windows/Odin box, so I set it up ages ago using Heimdall following set up following wiki.cyanogenmod.org/w/Install_CM_for_i9100, but that doesn't mention changing partition sizes
- obviously I already have a selection of PITs to try, plus downloads of GAPPs, CyanogenMod, ClockworkRecovery etc -- I just need some guidance and background on how to apply them without bricking the device.
Many thanks in advance.
Hi guys, complete noob here. I have been lurking this forum since I got flashed my S2 last year and have been updating from CM 10 to now CM12.
Today I have used CWM to upgrade my S2 to CM12 5.0.2 Beta and installed Pico gapps. Turns out I need the Nano gapps for Exchange support but without sufficient space it's not going to work.
Can someone help me with the appropriate PIT and Kernel files? I don't have an original JB image and I don't have a RIL file (Belgium). The FP is very detailed but I have no idea what the exact files are to use.
Any help appreciated.
Hope for korean SGS2
is there a way for me to increase my korean version of SGS2 storage, i really love this, thanks
DaNarni said:
Hi guys, complete noob here. I have been lurking this forum since I got flashed my S2 last year and have been updating from CM 10 to now CM12.
Today I have used CWM to upgrade my S2 to CM12 5.0.2 Beta and installed Pico gapps. Turns out I need the Nano gapps for Exchange support but without sufficient space it's not going to work.
Can someone help me with the appropriate PIT and Kernel files? I don't have an original JB image and I don't have a RIL file (Belgium). The FP is very detailed but I have no idea what the exact files are to use.
Any help appreciated.
Click to expand...
Click to collapse
In the CM12 thread a rar file with instructions was posted: http://forum.xda-developers.com/showpost.php?p=57788683&postcount=967
Mr/Islam Abdelhafez
Dear All,
Is this thread applied to my Galaxy S2 GT-1900 ??
and if not how can I repartition my S2 GT-1900 ?
Thanks
Sii gt-i9100
Dear All,
Is that thread applies on my SGS II GT-I9100 or not?
Thanks
islamabdelhafez said:
Dear All,
Is that thread applies on my SGS II GT-I9100 or not?
Thanks
Click to expand...
Click to collapse
Yes, this is the I9100 forum. Read The FP carefully.
New Pit file with 2 GB system for Stock GAPPS
Hi all,
after losing almost a day because of a faulty pit file I created my own.
Goal: upgrade S2 to Android 5 with Google Stock package ( biggest one from here http://forum.xda-developers.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900 ) and have more data space
Find attached a new .pit file with :
- 2 GB system
- 6 GB Data
- 3GB internal SD
- hidden partition 45 MB
If I did some miss calculation , feel free to report. It was the first .pit with which Android 5 + stock gapps could be flashed and which booted so I thought I'd share.

[Q] Lenovo Note 8 (A936) Golden Warrior ROM

Hi !
Just picked up this big phone from Aliexpress and I want to put a custom ROM on it (preferrably Lollipop). I've searched the forums but can not find anyone that is doing anything related to this phone.. The specs are as below:
Processor - Octa-core 1.7 GHz Cortex-A53, Mediatek MT6752
GPU: Mali-T760
RAM: 2 GB
Internal Memory: 8 GB
It seems there are a couple of other models running on this processor (HTC Desire 626, 526G, 820s)...
Anyone working on anything related to this phone that I could try out ?
Kind rgds
beetlezap
There's only one stock rom for this model now and I think it's for variant with 1GB RAM. It can be found on n e e d r o m . com
No custom roms yet.
beetlezap said:
Hi !
Just picked up this big phone from Aliexpress and I want to put a custom ROM on it (preferrably Lollipop). I've searched the forums but can not find anyone that is doing anything related to this phone.. The specs are as below:
Processor - Octa-core 1.7 GHz Cortex-A53, Mediatek MT6752
GPU: Mali-T760
RAM: 2 GB
Internal Memory: 8 GB
It seems there are a couple of other models running on this processor (HTC Desire 626, 526G, 820s)...
Anyone working on anything related to this phone that I could try out ?
Kind rgds
beetlezap
Click to expand...
Click to collapse
No lollipop yet. But they have Flyme OS from Meizu as well as some other stuff in the link below. Be warned that most of the ROMS there are for the 1GB RAM version. And the whole forum is in Chinese. Have fun.
http://bbs.ydss.cn/forum-lenovo_note8-1.html
Hi
Ive got the same phone
Managed to root but thats it
Cant find any custom recoveries etc
Nash
Thank you ! Since my chinese is a bit rusty I'll wait and see if someone picks it up in the western hemisphere
Can someone do for me backup of the stock rom from this 2GB Ram Version? I bricked my phone because I used this rom from needrom which is only for 1GB RAM version (there is no information about this on the top, after this I posted this info).
Please help me to get my phone working
Probably I need only A936 GW 2+8GB scatter file called MT6752_Android_scatter.txt extracted by "MtkDroidTools"- but to get this somebody need to backup the rom…
pavllo1980 said:
Can someone do for me backup of the stock rom from this 2GB Ram Version? I bricked my phone because I used this rom from needrom which is only for 1GB RAM version (there is no information about this on the top, after this I posted this info).
Please help me to get my phone working
Probably I need only A936 GW 2+8GB scatter file called MT6752_Android_scatter.txt extracted by "MtkDroidTools"- but to get this somebody need to backup the rom…
Click to expand...
Click to collapse
Found this on chinese Lenovo forum:
pan.baidu.com/s/1hqBZKf6
nashpb said:
Found this on chinese Lenovo forum:
pan.baidu.com/s/1hqBZKf6
Click to expand...
Click to collapse
the link doesn`t work on my computer
I can`t download nothing...could you give me the link to the forum/post ?
pavllo1980 said:
the link doesn`t work on my computer
I can`t download nothing...could you give me the link to the forum/post ?
Click to expand...
Click to collapse
i cant post links coz im new
bbs.lenovo.com/forum.php?mod=forumdisplay&fid=918
pavllo1980 said:
Can someone do for me backup of the stock rom from this 2GB Ram Version? I bricked my phone because I used this rom from needrom which is only for 1GB RAM version (there is no information about this on the top, after this I posted this info).
Please help me to get my phone working
Probably I need only A936 GW 2+8GB scatter file called MT6752_Android_scatter.txt extracted by "MtkDroidTools"- but to get this somebody need to backup the rom…
Click to expand...
Click to collapse
Hi Pavillo, all,
any luck with getting the 2g ROM?
I just received the device yesterday - it came somehow rooted with tons of CN bloatware, while MTK droid tools 2.5.3 was unable to access the root shell to make a backup. After few tweaks I made the su working (reinstate the superuser using the chanfire SuperSU + adbd insecure shell v2.0, but I'm not able to Create scatter file (button greyed out, probably unknown to the tool), what I see on the list is within attached jpg. Backup is I believe incomplete - console log>
50330-205606\
--- In phone files will remain in the folder: /mnt/sdcard/clockworkmod/backup/150330-205606/
--- We keep blocks:
- nodl_proinfo - ERROR : Zero file, no space left on device!
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: D:\temp\Lenovo\MtkDroidTools\backups\Lenovo-A936_141127_backup_150330-205606.zip
--- task end with ERROR ---
--- task is complete ---
I'm happy to create the dump, however seems I'm not savvy enough to prepare it using mtk droid tools.
I contacted the supplier to provide stock rom for this device, because with mine I'm not sure it wasn't somehow modified.
Regards, xPeca
I backup the firmware (VIBEUI_V2.0_1450_5.9.1_ST_A936_CU)
https://mega.co.nz/#!mcRyBIrK!Q1ejyd41muUgLuJK9mXUxW0h2qh4ZrbIpmnOP_2UdHE
FYI
xpeca1 said:
Hi Pavillo, all,
any luck with getting the 2g ROM?
I just received the device yesterday - it came somehow rooted with tons of CN bloatware, while MTK droid tools 2.5.3 was unable to access the root shell to make a backup. After few tweaks I made the su working (reinstate the superuser using the chanfire SuperSU + adbd insecure shell v2.0, but I'm not able to Create scatter file (button greyed out, probably unknown to the tool), what I see on the list is within attached jpg. Backup is I believe incomplete - console log>
50330-205606\
--- In phone files will remain in the folder: /mnt/sdcard/clockworkmod/backup/150330-205606/
--- We keep blocks:
- nodl_proinfo - ERROR : Zero file, no space left on device!
--- We keep folders contents copying on PC
- /data/nvram
- /system
--- We pack everything kept in archive: D:\temp\Lenovo\MtkDroidTools\backups\Lenovo-A936_141127_backup_150330-205606.zip
--- task end with ERROR ---
--- task is complete ---
I'm happy to create the dump, however seems I'm not savvy enough to prepare it using mtk droid tools.
I contacted the supplier to provide stock rom for this device, because with mine I'm not sure it wasn't somehow modified.
Regards, xPeca
Click to expand...
Click to collapse
Thanks Yiminghung!
Edit:
I checked the scatter file against my partinfo and it seems to fit my 2g ram / 8g rom version!
Created a dd backup of my partitions to get the courage to replace the system partition from your dump - and it worked!
However the dump is CN version (no google play, no root, ton of bloatware) so I reverted successfully back to my original version..
I found this on the web, it's in three parts, but I was a bit loathed to fulfill the advert criteria before downloading it, so it's untested. I did message the dev to check it was dual SIM and he answered so it sounds legit. Would be good if someone could download the rom, combine the three parts and post it here?
http://www.lollipop-rom.club/2014/12/Lenovo-4331-Golden-Warrior-Note-8-A936.html
modelman1968 said:
I found this on the web, it's in three parts, but I was a bit loathed to fulfill the advert criteria before downloading it, so it's untested. I did message the dev to check it was dual SIM and he answered so it sounds legit. Would be good if someone could download the rom, combine the three parts and post it here?
Click to expand...
Click to collapse
Hi, imho this is a fake to earn money using the surveys, the whole page looks weird. I cross-checked the CN forum bbs.ydss.cn/forum-lenovo_note8-1.html and there is no lollipop rom, and I guess these guys are in front of the ROW.
Yeah, I was suspicious myself, could definitely be fake but I was very surprised to get a reply from the dev when I emailed him to ask if it would support dual SIM. That said I wasn't brave enough to fill in the ads! I'm just hoping someone can access those downloads without the ads.
What to do to download
nashpb said:
i cant post links coz im new
bbs.lenovo.com/forum.php?mod=forumdisplay&fid=918
Click to expand...
Click to collapse
Well, I finally got an account to the forum without any idear of the language.
I have to post or answer to see the links, but how.
I found no way to manage it, please help!!!
muckelmaus said:
Well, I finally got an account to the forum without any idear of the language.
I have to post or answer to see the links, but how.
I found no way to manage it, please help!!!
Click to expand...
Click to collapse
Hi, use translate function in google chrome as I did . I managed myself to reply to some of the topics - just a single reply enables the download link- so ultimately got to the download; usually it points somewhere to pan.baidu.com ... but honestly not too much of a use unless we will get a recovery in other than CN language. I've posted the request for cwm also in that forum. However I suspect these ROMs will be CN only, while we need ROW version.
Regards xPeca
---------- Post added at 03:10 PM ---------- Previous post was at 02:27 PM ----------
Hi all,
just to share my enthusiasm - I just got my Lenovo A936 (2g RAM/8g ROM) loaded with EN CWM recovery.
Prereq is rooted device (mine came rooted, I just switched the su app with my favorite SuperSU from chainfire) and adb (e.g. adb-setup-1.4.2.exe, could be found on xda forum).
Afterwards I used PhilZ Touch 6 Recovery executable v7 - it requested only to provide boot.img and recovery.img from my device that I created simply by adb & dd command.
After completing the setup automatically by the executable, voilla it rebooted into EN CWM recovery. Very simple!
I can dump my recovery and boot.img that might be of a good use to others.
Credit goes to yuweng!
xPeca
It's the CWM recovery V6.0.5.1 that I port from PhilZ CWM recovery, It's the English version
download link: https://mega.co.nz/#!WMpCSayQ!Gwsrw5Fs2SEkcSNzQWukr9DeiUFIFmSWie9srod72FY
into recovery method: vol up+vol down + power button ,
flash the Google package : https://mega.co.nz/#!TF5zGApL!WIzyGOz2iH340gwfDYN0_Es5jOLi7TuPFfVptIuI-7s
Good luck~
---------- Post added at 08:03 AM ---------- Previous post was at 07:58 AM ----------
Custom ROM for Lenovo A936(2GB RAM Version) (port from Dakele OS)
Download Link:https://mega.co.nz/#!HdAyDDqC!JBiNfzabP8JTljY7WmOBEW2_sST2Rxkr-exJcxpZRmw
Flash procedure:
1. Copy the zip to TF card
2. into CWM recovery (the vol key is up/down select , power key is enter key during cwm recovery mode)
3. Wipe menu- wipe data + wipe cache + wipe dalvik cache
4. Install the rom -> install the zip from /storage/sdcard1
5. Found the zip rom and confirm
6. The phone will auto reboot after the zip rom flashed.
7. Good luck and enjoy it !
I just flashed the Philz recovery, works great! I used Philz auto installer from his post on the forum, all automatic and worked like a dream. Now going to install his recovery to my other mtk devices just so I have them all the same. Hoping someone will being out a lollipop ROM for the 1gb A936 soon, it can get a but laggy.
Sent from my Nexus 7 2013 using XDA Free mobile app
Lollipop Rom
I Have the 2g -8g model the phone is awesome, running google launcher as thats my preference, But i would love to have the latest Lollipop, is there any developers out there looking at a custom rom for this device ?. If not please look at it, make ppl happy .....
Many thanks
Mick :laugh::good:

Categories

Resources