• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

[Q] re partitioning of internal memory?

18 posts in this topic

Posted · Report post

hi folks,

just wondering if anyone has tried to repartition the internal memory of the G300? it would be nice to be able to use some of the spare system space to increase data partition.

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

The modaco rom is the only rom I know which has done this. The only downside with it (IMO) is that it makes some serious low level changes so it makes testing other roms a bit of a pain because you can't simply make a nandroid and flash back later because you have to revert the partition changes first.

An alternative (and less drastic) way of turning that 2GB internal storage to usable app storage is by using my Link2Int mod.

Edited by Cyda
0

Share this post


Link to post
Share on other sites

Posted · Report post

The modaco rom is the only rom I know which has done this. The only downside with it (IMO) is that it makes some serious low level changes so it makes testing other roms a bit of a pain because you can't simply make a nandroid and flash back later because you have to revert the partition changes first.

An alternative (and less drastic) way of turning that 2GB internal storage to usable app storage is by using my Link2Int mod.

cheers, I'm aware of the partition swap in the modaco Rom. is that not just setting the default data storage to the internal 2 gig card? I meant something along the lines of what amphoras used to do with the ZTE phones. (TPT method). I haven't got a lack of storage problem I just wondered if it was possible. I'm on cm9 at the minute and it just pains me to see all the free space in the system Rom partition sitting there unused. Cheers for the reply :-)

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

No, I've not seen anyone brave enough attempt a complete re-size of the partitions. Paul's method switched the /dev/block/mmcblk0p13 and /dev/block/mmcblk0p19 mount points around but that is as far as anyone has taken it that I know of.

Edited by Cyda
0

Share this post


Link to post
Share on other sites

Posted · Report post

okidoke, thank you. If I manage and don't brick I will post the results XD

1

Share this post


Link to post
Share on other sites

Posted · Report post

okidoke, thank you. If I manage and don't brick I will post the results XD

Fingers crossed. Lot's of people would love to see this... :)

0

Share this post


Link to post
Share on other sites

Posted · Report post

I have tested it, in terminal as root (su), manualy, fdisk type to 83 mmcblk0p19, mkfs ext4, connect to PC, copy data/data to new partition, disconect, mount to data/data.

Is posible do script to init.d, not tested. Because a did small mistake when reverting back i typed mkfs.vfat mmcblk0 instead mmcblk0p19, so, phone died :-), i was realy surprised because no way to recover it, is not posible to reflash chip over JTAG/RS232 or if flash programmer. Autorized service swapped whole mainboard.

1

Share this post


Link to post
Share on other sites

Posted · Report post

mmcblk0 ! :(

Glad you got a new board!

Great info on partitioning. Wouldn't blame you if you don't want to try again... :ph34r:

0

Share this post


Link to post
Share on other sites

Posted · Report post

I have tested it, in terminal as root (su), manualy, fdisk type to 83 mmcblk0p19, mkfs ext4, connect to PC, copy data/data to new partition, disconect, mount to data/data.

Is posible do script to init.d, not tested. Because a did small mistake when reverting back i typed mkfs.vfat mmcblk0 instead mmcblk0p19, so, phone died :-), i was realy surprised because no way to recover it, is not posible to reflash chip over JTAG/RS232 or if flash programmer. Autorized service swapped whole mainboard.

Ouch...Sorry for your loss lol. I'm just going to see if i can edit the files that define the partition sizes when you TPT your phone. On the ZTE phones i used to use these files came with every official update. Im just hoping they will be present in the b952 firmware i'm downloading now. Downside being that the ROM needs to be re-flashed after. But if i can figure it out thats a small price to pay for the extra 170mb of app space IMO. Ofcourse if all bricking my phone in the process would be a big price to pay....... I proceed with caution.

0

Share this post


Link to post
Share on other sites

Posted · Report post

speak to tillaz. He did something like this in the early days of the g300.

0

Share this post


Link to post
Share on other sites

Posted · Report post

if you do a search on modaco, you will see a discussion about update.app disassembly. There is a tool for doing it in that thread, but I'm not sure if its only for GB. It splits out the individual components in the rom. While we don't have the keys to resign it, if you can extract the 'tpt' process from it, we may get somewhere.

Pretty sure Tillaz method bricked a device but it was a test so people knew the risks. I'm not sure what method he used so if we can find out his process, it may help eliminate or perfect another method.

0

Share this post


Link to post
Share on other sites

Posted · Report post

0

Share this post


Link to post
Share on other sites

Posted · Report post

if you do a search on modaco, you will see a discussion about update.app disassembly. There is a tool for doing it in that thread, but I'm not sure if its only for GB. It splits out the individual components in the rom. While we don't have the keys to resign it, if you can extract the 'tpt' process from it, we may get somewhere.

Pretty sure Tillaz method bricked a device but it was a test so people knew the risks. I'm not sure what method he used so if we can find out his process, it may help eliminate or perfect another method.

Yer the perl script struggles to split the update. and although the files im after may be there, like you say we have no way of putting it back together to flash it via the download mode.... That sucks man. I was hoping it was going to be as simple as for the blade.

@davidoff:

Now that you say it, i faintly remember that someone else tried their hand at this and the conclusion was pretty much "unless we obtain the software to do so from huawei it's a no go"

Bowlocks....

0

Share this post


Link to post
Share on other sites

Posted · Report post

So is it the memory board itself which is locked down and we need the keys for?

0

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

afaik the update.app needs to be signed and we haven't found a way to disable that requirement.

I've extracted update.apps without a problem using the perl script. I think it needed renaming to updata.app first. Also there are a couple of versions floating around.

Edit: Attached the one I used

split_updata.zip

Edited by tcpaulh
0

Share this post


Link to post
Share on other sites

Posted · Report post

So is it the memory board itself which is locked down and we need the keys for?

It's the update.app that we cant rebuild. So in essence yes. Unless anyone has the tool and are just keeping realy quiet about it lol. But thats only half of the problem. The other half is that with the garbled output that script is giving me I cant even identify the files that would need modding should we ever manage to put an update.app together. The system came out fine but it looks like the script auto names the files it doesn't recognise to file1,file2,file3 etc and im not much of a script kiddie.

Conclusion: Not going to happen.

0

Share this post


Link to post
Share on other sites

Posted · Report post

AMSSMBN.img 22,760,448 AMSS modem binary image

appsboothd.mbn 40 lk bootloader binary

boot.img 4,462,592 Kernel, ramdisk and boot config

boot_versions.txt 40 Encoded list of roms?

cust.img 41,943,040 Huawei custom settings eg toggles, boot animation, locale, language

file01.mbn 80 HD-file

file02.mbn 40 HD-file

file04.mbn 9,508 could be QCSBL_CFGDATA

file05.mbn 641,424 extracting / flashing / controlling program

file07.mbn 40 HD-File

file18.mbn 128 MD5_RSA

file20.mbn 40 HD-File

file21.mbn 38,962 ADSP ?

recovery.img 5,146,624 The recovery and update environment’s kernel and ramdisk. Similar to BOOT.

system.img 396,361,728 The OS partition, static and read-only.

unknown_file.0 405 OEMSBL_Version-List

unknown_file.1 24,576 Config-File (?)

unknown_file.10 20 AMSS-Version

unknown_file.2 145,844 qcsbl.mbn(?) Qualcomm Secondary Bootloader (?)

unknown_file.3 25 OEMSBL_Version

unknown_file.4 3,145,728 MODEM_ST1

unknown_file.5 3,145,728 MODEM_ST2

unknown_file.6 768,000 Boot-Splashlogo (RAW565 480x800)

unknown_file.7 3,864,000 Install-Pictures (Updateing 1/2, Installing 2/2, one RAW565, 480 width, 4025 height)

unknown_file.8 205,108 fastboot (?)

unknown_file.9 330 AMSS_Version_List

userdata.img 155,189,248 default /data/app applications?

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.